Implementing Cloud Financials: From Empty Pod to Go-Live · Module 8 · Payables and Payments
Invoice approval workflow
Lesson 83 of 153 · 12 min
Enable invoice approval, build an amount-based rule routing to a manager, add a second rule with a higher threshold and a second approver, then submit an invoice, view the approval notification and approve it. Show rejection and the resubmission path, and show the approval history on the invoice. Approval rules are where clients over-engineer. Start with two or three tiers; you can always add. A seven-tier matrix designed in week two becomes the thing nobody can change in year two. Every rule needs a defined escalation and a defined delegate, or invoices sit in a leaver's queue forever — and nobody notices until a supplier calls. And the approval hierarchy usually depends on HR data. If HR is not implemented, you need a supervisory hierarchy from somewhere — flag that as a project dependency early, because it is somebody else's work and it will not appear on its own.
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.
In this module: Module 8 · Payables and Payments
- 1The procure-to-pay picture
- 2Common options and invoice options
- 3Payment terms and distribution sets
- 4The supplier model
- 5Creating suppliersFree preview
- 6The payments engine
- 7Payment methods, profiles, documents
- 8Invoice approval workflow
- 9End to end: invoice to payment to accounting
- 10What breaks
- 11Lab: full procure-to-pay
