CE-680 Captain reported a controlled flight toward terrain event during an automated FMC visual approach while conducting IOE. Trainee had incorrectly inserted the runway crossing altitude at the FAF location in the FMC which was missed by the Captain.

Narrative

While conducting IOE on a pic we ferried to sell. While enroute we was favoring a landing on rwy XX [at] ZZZ. I mentioned that things may change and we might want to brief the guided visual procedure for rwy XY just in case things changed we wont be rushed. My partner (the flying pilot) reviewed the company documents in Jeppesen FD and i watched him set up the left traffic guided visual to self rwy XY in the standby flight plan. He briefed the procedure. Once in the terminal area the changed runways to XY just as we had figured. We were cleared for the approach and we activated the standby flight plan and intercepted the left downwind per the guided visual procedure. We captured the vnav and began our decent to the runway. Just as we were abeam the numbers i sensed we were low but we continued on the vnav. As we started the base turn i recognized we were much lower than we should have been and advised the pilot flying to disconnect the automation and hand fly visually to the runway. We were 600-800 agl. Once on final we adjusted to the papi and executed a normal landing. No gpws or other alerts were activated. After landed i reviewed the FMS and realized that the rwy crossing height was placed at the final fix not the runway. We debriefed what had happened and continued the duty day.I was overseeing the input and saw the fix with ZZZ XY and with the other pilots hand in the way had assumed it was the runway fix. I should have been more diligent in verification. Maybe changing the fix name without a rwy number might have helped prevent this.