Group consolidation: Why it takes so long and how to fix it
Consolidating hundreds of entities can take a few minutes with the right system—so why does it take most finance teams days? Here’s where the time actually goes, and what changes when it doesn’t have to.
Sage Intacct’s product pages describe consolidating hundreds of entities in minutes rather than days. For a finance team that still spends the best part of a week on group consolidation each period, that claim can sound like marketing exaggeration. It isn’t an exaggeration, but the reason it’s true has more to do with architecture than speed for its own sake, and it’s worth understanding where that time actually goes before looking at what removes it.
This piece is for group finance leaders, FDs and consolidation managers running a manual or semi-manual process across multiple entities: where the time disappears, what changes structurally when it doesn’t have to, and what the finance team’s role looks like once consolidation stops being a manual assembly job.
Key takeaways
- Manual consolidation time concentrates in four places: intercompany eliminations, currency translation, spreadsheet assembly, and chasing entity-level data.
- The architecture matters more than the software brand. A single ledger with real-time intercompany matching removes most of the manual steps outright.
- “Minutes, not days” reflects automated processing on live data, not a faster version of the same manual steps.
- Once consolidation is automated, the finance team’s role shifts from assembling the numbers to reviewing and analysing them.
Here’s what we cover:
Where the time actually goes in a manual consolidation
Consolidation looks like one task from the outside: combine the entities, produce group numbers. In practice, most of the time sits in four distinct steps, each of which is manual by default unless the underlying system is built to automate it.
| Step | Why it’s slow manually |
|---|---|
| Intercompany eliminations | Each intercompany transaction has to be matched and eliminated by hand, entity by entity, and mismatches often aren’t caught until reconciliation. |
| Currency translation | Exchange rates have to be applied consistently across entities and periods, with translation adjustments calculated and tracked manually. |
| Spreadsheet consolidation | Entity-level trial balances are exported, reformatted, and combined outside the ledger, introducing version control risk at every step. |
| Chasing entity-level data | Subsidiary finance teams work to different timetables, so the group close waits on whichever entity reports last. |
Several of these steps compound the same underlying problem covered in why UK finance teams can’t close faster: manual, disconnected processes that scale badly as entity count grows.
A worked example: Consolidating six entities the manual way
Take a UK group with a parent company and five subsidiaries across two currencies, consolidating on a spreadsheet-based process. Days one and two are spent waiting on entity-level trial balances, since each subsidiary closes on a slightly different timetable. Day three is spent identifying and matching intercompany transactions, a step that regularly surfaces mismatches from postings made on only one side of a transaction. Day four covers currency translation and the resulting adjustments. Day five is reserved for reconciliation, review, and fixing whatever didn’t tie out the first time.
None of these five days involves analysis. All of them involve assembling data that, in an automated system, already sits on a single ledger in a consistent format. That’s the gap the architectural decisions below are designed to close.
The architectural decisions that change the maths
Three structural choices account for most of the difference between a week-long consolidation and one measured in minutes.
| Approach | What it looks like |
|---|---|
| Single ledger vs bolt-on tool | Entities sit on one ledger with a shared structure, rather than separate systems feeding a standalone consolidation tool. |
| Real-time intercompany matching | Intercompany transactions are matched and flagged automatically as they’re posted, not batched and reconciled at period end. |
| Standardised chart of accounts | Every entity maps to the same chart of accounts from the outset, removing the manual mapping step before consolidation can even begin. |
A standardised chart of accounts and shared ledger structure become more valuable, not less, as a group adds entities. See multi-entity finance: acquire and expand for how that complexity typically arrives, and how core financials built around a single ledger support it.
What “minutes, not days” actually means
The specific claim, consolidating hundreds of entities in minutes rather than days, comes from how Sage Intacct’s architecture handles the four time-consuming steps above. Because entities sit on a single ledger with a standardised chart of accounts, intercompany transactions are matched as they’re posted rather than reconciled after the fact, and currency translation applies automatically using live rates. None of the manual assembly work in the worked example above needs to happen at all, which is the actual source of the time saved rather than the system simply running the same manual steps faster.
This connects to reporting as much as processing speed. See how Sage Intacct’s platform capabilities support consolidated reporting once the underlying data no longer needs manual assembly.
Final thoughts: What the finance team’s role becomes
When consolidation stops requiring five days of data assembly, the finance team’s time doesn’t disappear, it moves. Instead of matching transactions and chasing subsidiary data, the group finance function spends that time reviewing consolidated numbers for what they actually mean: which entity is under-performing, where working capital is building up, and what the board needs to know before it asks.
Clean account reconciliation practices matter more, not less, in this model, since automated matching still needs a well-maintained ledger behind it. See what is account reconciliation and our guide to accounts payable management best practices for what underpins that shift.
Explore Sage Intacct for how this architecture supports group consolidation as entity count grows.
Group consolidation FAQs
Why does group consolidation take so long for most finance teams?
Most manual consolidation processes lose time to four steps: matching and eliminating intercompany transactions, applying currency translation, assembling entity-level data in spreadsheets, and waiting on subsidiaries that close to different timetables. None of these are inherently slow; they’re slow because they’re done by hand, separately from the core ledger.
What is the difference between a single ledger and a bolt-on consolidation tool?
A single ledger keeps every entity’s data in one system with a shared structure, so consolidation is a matter of processing existing data. A bolt-on tool sits outside the core accounting system, so entity data has to be exported and reformatted before it can be consolidated, which reintroduces manual work at every period end.
Is “consolidate hundreds of entities in minutes” realistic?
It reflects what’s achievable when intercompany matching, currency translation and chart-of-accounts mapping are automated on a single ledger, rather than assembled by hand. The time saved comes from removing manual steps entirely, not from performing the same manual process faster.
What does a finance team do once consolidation is automated?
The role shifts from data assembly to review and analysis: interpreting consolidated numbers, identifying which entities are driving or dragging group performance, and preparing board-level commentary, rather than spending the bulk of the close cycle matching transactions and chasing subsidiary data.
Browse more topics from this article
Explore more wisdom
Is your finance system holding back business growth?
Longer close cycles. More spreadsheet workarounds. Reporting that takes longer every quarter, not less. These are the signs a finance system has stopped supporting growth and started limiting it.
