Implementing Cloud Financials: From Empty Pod to Go-Live · Module 10 · Expenses
End to end and what breaks
Lesson 103 of 153 · 8 min
First the run. An employee enters a report with mileage, a meal and an over-limit hotel. The policy violation appears and a justification is entered. Submit, approve, audit. Export to Payables and look at the created invoice. Pay it, create accounting, and read the journal. Then five failures. Employee cannot submit — no payee. The employee is not set up as a payee, or the bank details are missing. Report approved but never paid. The export process is not scheduled. The lesson shows where to schedule it. Mileage calculating wrong. Rate schedule effective dates have lapsed — an annual maintenance failure, which means it happens to everybody exactly once, in January. Everyone's expenses are blocked. Policy set to block rather than warn. Culture, not configuration. Card transactions stopped arriving. The feed is broken, and nobody notices for weeks. Prevention: a monitoring alert, because a feed that stops silently is indistinguishable…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.
