Master data versus transactional loads

Suppliers and customers behave differently from invoices and journals, and the difference decides how you may correct a mistake. MASTER DATA IS USUALLY IDEMPOTENT. Load a supplier twice with the same key and the second load updates rather than duplicates — because the object has a natural identity the loader matches on. That makes master data forgiving: you can correct, reload, and converge on the right answer. TRANSACTIONAL DATA IS NOT. An invoice has no natural key; every load creates a new one. Load the same file twice and the supplier is owed the money twice — and it is a real payable that will be paid unless somebody catches it. AND SOME LOADS CANNOT BE UNDONE AT ALL. A posted journal is not deletable; the correction is a reversing entry, which means the wrong load is permanently in the ledger with its reversal beside it. An auditor will see…

In this module: Module 7 · FBDI: the file-based loader end to end

1. 1The FBDI sequence, and why order mattersFree preview
2. 2Finding and reading the right template
3. 3Mandatory columns, and the ones that only look optional
4. 4Preparing the file without corrupting it
5. 5Loading the interface tables
6. 6Running the import and reading the output
7. 7Errors: finding the row that failed
8. 8Correcting and reloading safely
9. 9Master data versus transactional loads
10. 10Volume: loading a hundred thousand rows
11. 11Proving the load landed
12. 12Rollback, and why there usually is not one
13. 13What breaks: six FBDI failures
14. 14Lab briefing · A supplier and invoice load