Preparing a Newly Acquired Subsidiary for Group Reporting

What has to be true before a newly acquired company can submit into the group close

Group reporting integration is usually the point where a Group Finance team discovers how much of an acquired company’s accounting was built for an audience of one. The local team was answering to a statutory filing deadline and a local auditor, not to a consolidation system. Nothing about that is wrong, but almost none of it transfers unchanged. This article sets out what has to be in place before a newly acquired subsidiary’s first submission into group reporting, organised as four workstreams that can run in parallel, with an illustrative six week timeline and a readiness checklist you can use as a gate before the first close.

What Group Reporting Readiness Actually Means

Group reporting readiness is the state in which a subsidiary can produce, on the group’s timetable and in the group’s format, financial data that the consolidation team can use without manual rework. It is a property of four things at once: the account mapping, the package format, the closing calendar, and the reliability of the underlying balances. Weakness in any one of them blocks the other three.

The requirement comes from consolidation itself. Under the EU’s Accounting Directive 2013/34/EU, a parent preparing consolidated financial statements has to present the group as though it were a single entity, which is only possible if every entity’s figures arrive on a common basis. For groups applying IFRS under the IAS Regulation 1606/2002, the EU endorsed standards in Regulation 1126/2008 go further and require uniform accounting policies across the consolidated group, so a subsidiary carrying a different depreciation basis or provision policy has to be restated, not just remapped.

That distinction matters for scoping. Remapping is a data exercise. Restating for policy alignment is an accounting judgement, and it takes longer.

Statutory Reporting and Group Reporting Are Different Jobs

The most common planning error is assuming that a subsidiary which files clean statutory accounts is therefore ready to report into a group. The two outputs answer different questions, on different deadlines, at different levels of detail.

Read those two columns together and the size of the change becomes clear. You are asking a team that produced one detailed report a year to produce a differently structured report twelve times a year, roughly two weeks earlier in the cycle than they have ever closed before. Treating that as an administrative handover is what turns the first three closes into a series of late nights.

The Four Workstreams

Readiness work is best run as four parallel workstreams rather than a single sequential project, because three of them can start before the fourth is finished.

Mapping the local chart of accounts

Every active local account code gets assigned to one group reporting line, with a written rule for any account that could reasonably split across two. The classic case is a single local account holding both trade receivables and other receivables, which the group reports separately. Splitting it needs a rule, not a judgement call repeated differently each month.

Illustratively, for a subsidiary with 150 to 200 active accounts, expect 2 to 3 weeks to build the mapping and a further 1 to 2 weeks to test it by running one closed historic period through the map and agreeing the output back to the subsidiary’s own management accounts. The test is the part people skip, and it is the part that finds the errors.

Rebuilding the reporting package

The package is the standard set of schedules the group needs from every entity: trial balance, intercompany schedule, fixed asset roll forward, provisions and accruals schedule, debt and lease schedules, and whatever segment or KPI data the group discloses externally. A newly acquired company rarely has these in the group’s format on day one, and some it may never have produced at all.

Segment data deserves separate attention because it is the one most likely to be genuinely missing rather than merely differently formatted. A company that reported a single revenue line locally may need that revenue split across 3 to 4 group segments, which depends on transaction level sales data at a granularity the local system was never asked to hold. If that data does not exist historically, decide early whether you are rebuilding it or accepting a prospective start date.

Moving the closing calendar

If the group needs a trial balance on working day 4 and a final package on working day 7, and the subsidiary has historically closed on working day 12 to 15, that eight day gap has to be engineered out. It does not close by asking the local team to work faster during close week.

It closes by moving work out of close week: bringing cut-off procedures forward, pre-calculating recurring accruals, agreeing standing estimates for items that always arrive late, and moving reconciliations that do not depend on the final ledger into the prior month. A close that starts earlier finishes earlier. A close that is merely rushed produces errors that surface in the group’s numbers.

Checking data quality before the first submission

Before a subsidiary’s figures enter a consolidated report for the first time, confirm that the trial balance ties to the last filed local statements, that intercompany balances have been agreed with their counterparty entities, that balance sheet accounts carrying old or unsupported amounts have been reviewed, and that the fixed asset register agrees to the general ledger control account. The receivables ledger usually deserves its own pass, and our guide on how to review accounts receivable after an acquisition covers the aging and provisioning questions in detail.

This is also the workstream with the longest tail. Mapping and formatting are finite tasks. Substantiating balances that nobody has questioned in years is open ended, which is why it should start first even though it finishes last.

A Worked Example: Six Weeks to First Submission

The following timeline is illustrative, not a client engagement. Assume a distribution subsidiary with 45 employees and EUR 22 million of annual revenue, 210 active local accounts mapping to 65 group reporting lines, and a historic local close finishing on working day 12 against a group deadline of working day 5.

Week	Account mapping	Package and calendar	Data quality
1	Extract trial balance, identify 210 active accounts	Share group package templates, walk through each schedule	Tie trial balance to last filed statutory accounts
2	First pass mapping, flag 18 accounts needing split rules	Map close calendar day by day, find the eight day gap	Request intercompany balances from counterparty entities
3	Agree split rules with Group, complete mapping	Identify which tasks move out of close week	Agree intercompany differences, investigate the exceptions
4	Test map on a closed prior period	Build the fixed asset and provisions schedules	Review aged and unsupported balance sheet items
5	Reconcile test output to local management accounts, fix breaks	Dry run the package on prior period data	Confirm fixed asset register agrees to control account
6	Freeze the mapping, document it	Trial close at the new deadline, no submission	Sign off opening balances, list open items with owners

Two things in that table are easy to underestimate. The week 5 reconciliation of test output to local management accounts is where mapping errors actually surface, and the week 6 trial close is the only honest test of whether the calendar change is real. Skipping either one moves the discovery into the first live submission, where it costs considerably more.

The Readiness Checklist

Use this as a gate before the first live submission rather than a report afterwards. Anything not marked complete is an item somebody will handle manually, under time pressure, during close week.

Item	Evidence that it is done
Account mapping complete	Every active local code assigned to one group line, split rules written down
Mapping tested	One historic period run through the map and agreed to local management accounts
Accounting policy differences identified	Written list of local policies that differ from group policy, with restatement decisions
Reporting package producible	Every required schedule generated from the subsidiary’s own system, not rebuilt by hand
Closing calendar aligned	Trial close completed at the group deadline before the first live submission
Trial balance tied	Agreed to the last filed statutory accounts, differences explained
Intercompany agreed	Balances confirmed with each counterparty entity, exceptions listed with owners
Balance sheet reviewed	Aged and unsupported balances investigated, written conclusion per account
Fixed assets agreed	Register reconciled to the general ledger control account
Segment data available	Revenue and costs mapped to group segments, or a prospective start date agreed
Ownership assigned	Named person for each schedule on both the local and group side

Where First Submissions Usually Go Wrong

The failures are repetitive across deals, which makes them worth naming in advance:

• The mapping was never tested. It looks complete in a spreadsheet and produces a group profit figure that nobody can agree back to the local accounts.
• Policy differences were treated as mapping differences. A depreciation or provisioning basis that differs from group policy cannot be fixed by pointing an account at a different line. It needs restatement.
• The calendar was agreed but never rehearsed. Everyone accepted working day 5 in a meeting. Nobody closed at working day 5 before the month it counted.
• Intercompany was left until after the first submission. It then becomes a consolidation break under deadline, which is the worst possible time to investigate it.
• Segment data was assumed to exist. It usually does not, at least not at the granularity the group discloses.
• One person held the whole thing. Often the local finance manager, who also has a statutory close, an audit, and a day job.

Most of these are visible in the first two weeks if somebody is looking for them, which is the argument for running the readiness review early rather than treating it as pre close housekeeping. It is one of the reviews we would put in the first month of the first 100 days finance integration roadmap, alongside the broader question of what a CFO should review immediately after an acquisition.

Who Owns What

Readiness stalls more often over ownership than over technique. A workable split gives the group side the definitions and the local side the execution, with one named person accountable for each schedule on both sides.

Group Finance owns the target: the reporting chart of accounts, the package format, the policy manual, the calendar, and the decisions on split rules and restatements. The local finance team owns the source: the ledger, the mapping application, the schedules, and the explanations behind the balances. The integration lead owns the gap between them, which is where most of the work actually sits.

The one arrangement that reliably fails is leaving the whole thing with the acquired company’s finance manager on the assumption that they know their own books best. They do, which is exactly why they are already fully occupied. Readiness work is additional capacity, not a reallocation of existing capacity, and treating it otherwise is the most common reason first submissions slip.

Frequently Asked Questions

How long does it take to prepare an acquired subsidiary for group reporting?

For a mid sized subsidiary with a functioning finance team, allow 6 to 10 weeks from kick off to first reliable submission. Account mapping takes 3 to 5 weeks including testing. Data quality work runs longest because substantiating old balances is open ended, so start it first even though it finishes last.

What is the difference between statutory reporting and group reporting?

Statutory reporting serves local authorities and auditors under local GAAP, using local account codes, usually once a year. Group reporting serves the consolidation team monthly, using the group chart of accounts and group policy, on a working day 4 to 7 deadline. A subsidiary can do one well and not the other.

Does an acquired subsidiary have to change its accounting policies?

For consolidation purposes, yes. EU endorsed IFRS requires uniform accounting policies across a consolidated group, so policies that differ from group policy must be restated in the reporting package. The subsidiary usually keeps its local policies for its own statutory accounts, and maintains the restatement as a reporting layer.

Should the local chart of accounts be replaced with the group’s?

Rarely at first. Replacing a live chart of accounts during integration risks the local statutory close and the audit trail. Most groups map the local chart to group reporting lines and defer any system migration until after two or three clean closes, when the mapping is proven and understood.

What is the most common reason a first group submission is late?

An untested mapping combined with a closing calendar that was agreed but never rehearsed. Both look complete on paper. Both fail on the first live close, at the point when there is no time left to investigate. A trial close on prior period data exposes each of them cheaply.