Multi-entity reporting
that reconciles.

Define a common reporting contract

Different ledgers can feed the same management report, provided the inputs have consistent boundaries and are reconciled. Before building the group workbook, agree what every entity must submit and what each number means.

Write a short reporting contract that covers the period, entity identifier, currency, sign convention, account definitions, organizational dimensions and expected level of detail. Include a submission deadline, review owner and exception route. Specify which data is sourced from the ledger and which comes from another system.

Keep actual results, budget, forecast and illustrative pro forma information identifiable. Combining those views without a clear label can make a technically correct total misleading. For acquisition comparisons, explain the ownership-period boundary and the basis of any historical combined presentation.

Treat chart mapping as governed data

A mapping is a reporting decision. An acquired entity’s “other expenses” account may need different treatment from the similarly named group account. Review the transactions and the intended reporting definition before assuming names imply equivalence.

Deloitte describes the chart of accounts as part of a finance data model that should support how the organization manages and reports, with consistent definitions and room to scale.[1] Apply that principle by assigning ownership to your mapping register.

Before combining submissions, check for unmapped accounts, duplicate mappings and inconsistent signs. Reconcile the source totals to the mapped totals. Where one source account needs to split across reporting lines, document the allocation basis and the evidence supporting it.

A mapping change that moves costs between departments may leave total earnings unchanged while changing a manager’s reported performance. Review the effect on both totals and the dimensions used for decisions.

Make both sides of intercompany visible

Group totals are not a simple addition exercise when entities trade or fund one another. Design the submission so reviewers can identify counterparties and investigate differences. Keep intercompany activity distinguishable from external activity and document the review steps.

Deloitte identifies mismatched systems, charts of accounts and insufficient detail as causes of intercompany reconciliation difficulty after acquisitions. It describes interim information-sharing processes as one way to improve transparency while systems integration is still underway.[2]

A practical exception list can capture the two entities, the balance or transaction category, the reported amount on each side, the difference, the likely cause and the responsible owners. Separate timing differences from missing entries, classification issues and other explanations. Each requires an explicit resolution, not a plug that disappears into the group report.

Accounting, treasury and tax teams may all have responsibilities in this area. Use the appropriate specialists to determine required accounting, eliminations, settlement and jurisdiction-specific treatment. The workplan tracks the action and owner; it does not prescribe those technical conclusions.

Build bridges that explain the difference

A useful group report lets the reviewer move from each entity’s submitted results to the final management view. Show the adjustments between those points in an identifiable bridge with a description and owner. Keep reported results and management adjustments separately visible.

For a fictional example, suppose the group receives three entity submissions and a central-cost ledger. A reviewable report keeps those four sources identifiable, adds the approved consolidation or management adjustments in separate columns, and reconciles the resulting total. If management wants an organic-versus-acquired view, document the classification and maintain it consistently.

Do the same for performance explanations. Distinguish movements driven by the acquired business, existing operations, central costs and approved adjustments. A change in the reporting perimeter should not be casually described as organic growth.

Pro Forma Financials is a related resource for exploring a combined financial picture. Use Value Creation Plans to track whether the initiatives behind that picture are delivering their intended benefits.

Close the loop with ownership and evidence

For each entity submission, record who prepared it, who reviewed it and what remains unresolved. The first group close often exposes capacity or data gaps. Make those visible in the integration workplan and give recurring responsibilities a home in the close process.

• At submission: confirm the reporting period, entity scope, source totals and key reconciliations.
• At group review: inspect mapping exceptions, intercompany differences and material changes from the prior period or plan.
• Before distribution: confirm approved adjustments, known limitations and the explanation of major movements.
• After distribution: log corrections and process changes so the next cycle improves.

Systems consolidation can reduce repeated work, but it should follow a clear understanding of reporting requirements. The immediate objective is a repeatable report that management can reconcile and use. The longer-term objective is an operating model that can absorb the next acquisition without rebuilding the process.