Implementing Cloud Financials: From Empty Pod to Go-Live · Module 8 · Payables and Payments
The supplier model
Lesson 79 of 153 · 1 min
Four levels, and learners conflate them constantly. Party is the organisation as a legal entity in the world. Supplier is that party in its role as somebody you buy from. Supplier site is a specific location and remit-to combination. Site assignment is which business unit can use that site, and with what defaults. Sites exist because one supplier can have several remit-to addresses, several bank accounts, and different terms per location. Assignments exist because of the business unit segregation you designed two modules ago: a site unassigned to a business unit is invisible to it. Bank accounts sit at supplier level for electronic payment, and the security sensitivity there is the subject of the next lesson — it is the segment of this module people remember. Minimise sites. Every site is maintenance. Create one per genuinely distinct remit-to, not one per building.
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