Implementing Cloud Financials: From Empty Pod to Go-Live · Module 9 · Receivables
The customer model
Lesson 91 of 153 · 1 min
Four levels: party → customer account → account site → site use, deliberately parallel to the supplier model from the previous module. Notice the parallel; it transfers. Site uses are bill-to, ship-to and others, and one physical site can hold several uses. A bill-to and a ship-to can differ — which is what drives tax place-of-supply from the tax module, and it is the reason the customer lab asks you to build one. Where things attach: payment terms, tax profile, statements, dunning. Each attaches at a specific level, and knowing which level is the practical skill — along with the account-versus-site default override hierarchy. As with suppliers: minimise sites. The reasoning is identical, and so is the cost of ignoring it.
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.