Sub-ledger and general ledger agreement

The migrated sub-ledger must agree with the migrated general ledger, and they are loaded separately, which is where the silence comes from. Open payables are loaded as invoices; the payables control account balance is loaded as a journal. Two loads, two files, two totals — and nothing in either checks the other. They can disagree by a rounding rule, a currency conversion, an excluded status, or a handful of records one file included and the other did not. THE COMMON CAUSES, in order of how often they are the answer. ROUNDING — the sub-ledger sums to the cent per invoice, the GL was extracted as a rounded balance. CURRENCY — the two sides converted at different rates or on different dates. SCOPE — the invoice extract excluded a status, such as on-hold or disputed items, that the GL balance includes. And TIMING — the two extracts were taken hours apart.…

In this module: Module 9 · Migration strategy and reconciliation

1. 1What to migrate, and what to leave behind
2. 2Balances versus transactions
3. 3The cutover sequence
4. 4Reconciliation: proving a migration landedFree preview
5. 5Data cleansing, and who owns it
6. 6Mapping legacy values to Fusion
7. 7Trial loads and the rehearsal nobody schedules
8. 8Sub-ledger and general ledger agreement
9. 9Signing off: what "done" means
10. 10What breaks: the migration that reconciled and was wrong
11. 11Lab briefing · Plan and reconcile a migration