A subsidiary opens a new freight expense account midway through the year. Its trial balance balances, yet the group reporting pack omits the amount because the new account has no group mapping. A balanced ledger alone cannot establish completeness of the report.
Test for both omission and duplication
List every local account used during the period, including accounts with movement but zero closing balance. Identify the group line and mapping rule for each. Where a local account splits between lines, document the allocation basis and confirm the split reconciles to the original amount.
Retain the reporting version
Record who approved the mapping and the period it applies to. Rerun the comparison after changes and check a sample of local transactions against the resulting group line. Version history helps explain why the same local account may appear differently after a reporting policy or business structure change.
Use the posted local account balances from Accounting360 when testing completeness of the reporting map.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



