Customers, suppliers and staff are one record

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can say what a customer record actually is — one row in a shared entity table with four independent flags — predict what the platform stores when you type a code, name the single field that puts every document’s receivable or payable line where it goes and why it is decided once, recognise the Tax tab as a record rather than a setting, and decide whether a pair of duplicates is safe to merge.

Presentations

1. One table, four ticks — about 12 minutes, narrated
2. The code you type is not the code that is stored — about 12 minutes, narrated
3. One record, one control account, decided once — about 13 minutes, narrated
4. The Tax tab on a customer is not where tax comes from — about 13 minutes, narrated
5. Merging repoints, it does not marry — about 13 minutes, narrated

Modules this series draws on

• Core Module
• Financial Accounting Module
• Purchasing Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• Customer Maintenance
• Entity Maintenance
• Supplier
• Tax Configuration

All presentations · Presentations for the whole-system operator