Implementing Cloud Financials: From Empty Pod to Go-Live · Module 9 · Receivables
Transaction types and sources
Lesson 89 of 153 · 11 min
Two objects, and learners merge them into one when they should not. Transaction type is what the document is: invoice, credit memo, debit memo, chargeback. It carries the receivable and revenue account defaults, the open and closed behaviour, whether it posts to the general ledger, and whether it allows freight or tax. Transaction source is where the document came from: manual, imported, a specific feeder system. It controls numbering and validation on import. Why the split matters: one type — invoice — can arrive from several sources, each numbered differently. And numbering by source is how clients get separate sequences for manual and system-generated documents, which several countries require. One more thing worth knowing: transaction type drives whether the document affects the customer balance, and a type that does not post to the general ledger still shows on the account. Useful, and confusing the first time you meet it. Then…
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.