Multi-Entity Consolidation: The Definitive Guide
Most finance teams don't think about multi-entity consolidation until it's already a problem. A second legal entity gets set up for a new subsidiary, a foreign office, or a holding structure ahead of a raise, and the accounting system that worked fine for one entity starts requiring a monthly workaround to produce one set of consolidated numbers. That workaround usually holds for a while. Then the company adds a third entity, or a fourth, and the workaround becomes the least reliable part of the close.
This guide covers what multi-entity consolidation actually requires, where legacy approaches tend to break, and what to evaluate in a platform before you're consolidating under real time pressure.
Multi-entity consolidation is the process of combining the financial results of two or more legal entities, often across different currencies and jurisdictions, into a single, accurate set of group financial statements, with intercompany transactions between those entities eliminated so they don't double-count in the total. That last part, intercompany elimination, is the piece that's hardest to get right and easiest to get wrong manually.
Key takeaways
- Consolidation isn't just addition. Combining entity-level numbers into a group total requires eliminating intercompany transactions, translating currencies, and mapping each entity's chart of accounts to a common structure, not just summing balances.
- Most consolidation problems are invisible until they aren't. A workaround that takes an extra afternoon at two entities can take a week or more at five, and errors compound quietly until an audit or a board question surfaces them.
- The real evaluation question is real-time vs. period-end. Systems that require separate instances per entity and manual export-and-merge push consolidation to a monthly event. Systems built for it natively can show a consolidated view at any point in the month.
- Currency translation and intercompany elimination are the two places manual processes fail most often, not the basic act of adding entities together.
Why this breaks in legacy systems
Separate instances instead of one system
Many general ledger systems that weren't built with multi-entity in mind handle a second entity by standing up an entirely separate instance, its own login, its own chart of accounts, its own database. Getting a consolidated view means someone exports data from each instance and merges it, usually in a spreadsheet, once a month. This is slow, and it's also fragile: the more entities involved, the more manual steps there are for something to go wrong in.
Intercompany eliminations done by hand
When Entity A sells services to Entity B, that transaction needs to be eliminated at the group level, otherwise the same revenue and expense show up twice in the consolidated statements. Done manually, this means someone identifying every intercompany transaction each month, matching it on both sides, and booking an elimination entry. Missed or mismatched eliminations are one of the most common sources of consolidation errors, and they're also one of the hardest for a reviewer to catch without a dedicated process.
Currency translation as a side process
For entities operating in different currencies, consolidation requires translating each entity's local-currency results into a single reporting currency, applying the right rate for the right line item, current rates for balance sheet items, average rates for income statement items, being the common standard. Handled in a spreadsheet, this is a recurring source of small errors that are individually minor but collectively material.
Chart of accounts drift
Over time, entities that started on a shared chart of accounts tend to drift, someone adds a local account for a jurisdiction-specific requirement, someone else names a similar account slightly differently. Without a system enforcing a mapped, consistent structure, this drift makes automated consolidation harder every quarter it goes unaddressed.
What to evaluate in a consolidation platform
| Criterion | Why it matters |
|---|---|
| Real-time vs. batch consolidation | Why it mattersDetermines whether you can see a consolidated view any day of the month, or only after a manual monthly process |
| Automated intercompany eliminations | Why it mattersThe single biggest source of manual error and time in legacy consolidation |
| Multi-currency support | Why it mattersShould apply the right rate to the right line item automatically, not require manual rate lookups |
| Single system vs. separate instances | Why it mattersSeparate instances per entity mean export-and-merge; one system means a native consolidated view |
| Chart of accounts mapping | Why it mattersShould enforce a consistent structure across entities rather than allowing drift over time |
| Audit trail at the entity and group level | Why it mattersNeeded to support both local entity audits and group-level review |
How Campfire approaches consolidation
Campfire consolidates unlimited entities across 180+ currencies in a single real-time view, without requiring separate instances or logins per entity. Intercompany eliminations are handled automatically as transactions occur rather than as a period-end exercise, and Ember, Campfire's accounting AI, monitors intercompany activity on an ongoing basis and flags unusual patterns for review. One customer scaled from $10M to over $200M in ARR on Campfire without growing their accounting team, largely because consolidation stopped being a monthly bottleneck.
If you're evaluating a platform for this specifically, ask for a live demo of consolidation across at least three entities with different currencies, not a slide describing the feature. The difference between "supports multi-entity" and "consolidates without a spreadsheet" tends to show up quickly once you ask to see it.
FAQ
What's the difference between multi-entity accounting and consolidation?
Multi-entity accounting means a system can track separate books for more than one legal entity. Consolidation is the additional step of combining those entities' results into accurate group financial statements, with intercompany transactions eliminated and currencies translated. A system can support the first without doing the second well.
How often should intercompany eliminations happen?
In a real-time consolidation system, eliminations happen continuously as intercompany transactions occur. In systems that rely on a period-end process, eliminations are typically done once per month as part of the close, which is where most manual errors originate.
Does multi-entity consolidation require the same chart of accounts across all entities?
It requires a mapping between each entity's chart of accounts and a common consolidated structure. Entities don't need identical charts of accounts, but without a system enforcing the mapping, charts tend to drift apart over time in ways that make consolidation progressively harder.
What does Campfire cost for a multi-entity company?
Campfire offers tailored pricing based on company size and complexity. Contact the team for a demo and custom quote.