Implementing Cloud Financials: From Empty Pod to Go-Live · Module 8 · Payables and Payments
What breaks
Lesson 85 of 153 · 2 min
Six failures, and the last one is not a software failure at all. Invoice will not validate — distribution variance. The line total does not match the distributions, usually because of a tax line the enterer did not expect. Supplier site does not appear. The site is not assigned to the business unit. Payment run selects nothing. Terms not due, or invoices unapproved, or the payment method is not assigned to the supplier. Three items, and check them in that order. Bank rejected the payment file. Format mismatch. Prevention: a bank-validated test file, a month before go-live. Accounting created but the journal is wrong. Subledger Accounting rules, or default account configuration — a different layer from validation, and knowing the difference is the whole diagnosis. We paid a fraudulent supplier bank account. Not a software failure: no independent verification control. Prevention is the control from the supplier lesson, and this…
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