A consolidation pack is a shared reporting language for group companies. Its purpose is to collect information that can be combined and reviewed consistently, not to ask every subsidiary for an unstructured collection of spreadsheets. Begin with the consolidation perimeter, reporting framework and required outputs. Then define the schedules and explanations needed to support those outputs, with instructions that local teams can actually follow and verify.
Request a trial balance mapped to the group chart, supporting balance details and information for disclosures. Identify the reporting period, currency and status of the figures. Distinguish final accounts from provisional management information. Where local policies differ from group requirements, ask for the data needed to calculate adjustments. Simply changing an account label does not resolve a difference in recognition or measurement between the local and consolidated reporting basis.
Give intercompany reporting its own structure. Each balance and transaction should identify the counterparty, nature, currency and relevant period. Set a reconciliation process so differences are discussed before group closing. Include loans, interest, management charges, goods and other applicable transactions. A single net intercompany number may hide several mismatches and cannot always support the eliminations or disclosures required for a reliable consolidated reporting process.
Imagine a hypothetical group of service businesses using different accounting systems. One subsidiary records group charges in general expenses while another reports them separately. The pack requires a counterparty schedule with a reconciliation to the ledger, allowing the consolidation team to identify equivalent transactions without changing local systems immediately. Clear definitions and a worked instruction can resolve the reporting gap more effectively than repeatedly asking for a better spreadsheet.
Allocate responsibility for preparation, review and submission at each entity. Keep version control and a log of questions, adjustments and approvals. Build validation checks connecting totals and movements, but do not rely on automated checks to prove that classifications are correct. Ask for explanations of unusual transactions and changes in estimates. A mathematically balanced pack can still omit a significant event that affects the group's reporting assessment.
Pilot the pack with one entity and revise unclear requests before rolling it out. Preserve the connection between submitted data, consolidation adjustments and final accounts. A reporting pack review can reduce repeated questions and late corrections, giving the group a practical collection process while making data quality, unresolved differences and responsibility visible throughout the closing cycle.