Once a business runs more than one legal entity, the accounting question stops being “are the numbers right” and becomes “which numbers count.” A group with a UK parent and two subsidiaries doesn’t just need three sets of accurate books. It needs those three books combined into one true picture, with anything traded internally stripped back out before anyone reports on group performance.
That last part is where most spreadsheet-based groups start to strain, and it’s worth understanding properly before deciding whether ERP consolidation is actually the fix.
TL;DR
- Consolidation combines entity-level accounts into one group view, but only after internal trading between entities is removed.
- Skip that elimination step and revenue gets counted twice: once at the selling entity, once at the buying one.
- Currency translation needs two different exchange rates depending on whether you’re translating the balance sheet or the profit and loss account.
- Manual, spreadsheet-based consolidation tends to hold up fine at two entities and starts breaking down past three or four.
- Blue Lotus 360 handles intercompany elimination and consolidation as native functionality, not a bolt-on spreadsheet exercise each month-end.
What actually gets consolidated
A consolidated set of accounts combines revenue, costs, assets, liabilities and equity across every entity in the group, adjusted so the result reads as if the whole group were one company. Four things need attention to get there: aligning each entity’s figures to a common structure, converting anything reported in a different currency, removing transactions between entities in the group, and reviewing the result before anyone relies on it.
That third point is the one that trips people up most often, so it’s worth spelling out properly.
Intercompany elimination, in plain terms
Say your UK parent company sells £80,000 of stock to a subsidiary during the quarter. At entity level, that’s completely legitimate: the parent recognises £80,000 in revenue, the subsidiary records £80,000 in stock purchased. Both entities’ individual accounts are correct.
Roll those two entities up into a group report without adjustment, though, and that £80,000 shows up twice, once as revenue, once as an internal purchase, inflating the group’s reported turnover for something that never actually left the business. An elimination entry reverses both sides, so the group total reflects only what was sold externally.
This is straightforward with one internal transaction. It gets genuinely difficult once you’re tracking recharges for shared services, intercompany loans and interest, and management fees between five or six entities, all needing to be identified, matched, and reversed correctly before the group figures mean anything.
Currency translation, and why one exchange rate isn’t enough
For groups with a subsidiary reporting in a different currency, UK accounting practice applies two separate rates rather than one blanket conversion. Balance sheet items translate at the closing rate on the reporting date. Profit and loss items translate at an average rate across the period.
The distinction matters more than it looks. If sterling strengthens significantly during the quarter, a subsidiary’s euro-denominated revenue will translate to fewer pounds in the group accounts even though nothing changed in the underlying business. That’s a translation effect, not a performance drop, and conflating the two in a board report leads to the wrong conversation entirely.
Why this becomes a spreadsheet problem fast
Two entities, one currency, low transaction volume between them: a well-maintained spreadsheet can genuinely cope with that. Add a third entity, a different currency, or a meaningful volume of intercompany trading, and the manual version starts showing cracks in predictable places.
Account structures drift apart because each entity’s finance lead sets up their chart of accounts slightly differently. Intercompany balances stop matching because one entity posts a transaction on the last day of the month and the other doesn’t record it until the next period opens. Exchange rate references get out of date because nobody’s kept the reference table current. None of these are dramatic failures individually. Collectively, they’re why a month-end close that should take a few days stretches into three weeks of chasing figures and reconciling small discrepancies that shouldn’t exist.
What a working consolidation process actually needs
Getting this right consistently, whether in a spreadsheet or an ERP system, comes down to a handful of disciplines:
- A shared chart of accounts, or at minimum a reliable mapping table, so figures from different entities aggregate cleanly
- A fixed reporting calendar with a real deadline, so one late entity doesn’t hold up the whole group
- Consistently tagged intercompany transactions, so eliminations can be identified quickly rather than hunted for
- A maintained exchange rate reference, updated at each close rather than whenever someone remembers
- A documented audit trail covering source figures, elimination entries and sign-offs, since this is exactly what gets requested at year-end audit
Where an ERP system earns its keep is doing most of this automatically: pulling entity-level figures without a manual export, flagging intercompany transactions as they’re posted rather than reconstructed after the fact, and applying currency translation consistently without someone maintaining a rates tab by hand.
Built for this from the start
Blue Lotus 360 handles multi-entity structures as core functionality rather than a workaround bolted onto single-company accounting. Intercompany transactions get flagged and matched as they’re posted, currency translation applies the correct rate automatically depending on whether it’s a balance sheet or P&L item, and the group view updates without a manual export-and-reconcile exercise every month-end.
For growing UK businesses adding a second entity, or already juggling three or four in a spreadsheet that’s started to strain, a demo is a practical way to see what that close process looks like when it isn’t rebuilt from scratch every period.
FAQ Section
At what point does a business actually need consolidation software rather than a spreadsheet?
There’s no fixed number of entities where this flips, but most groups start feeling real strain once they’re managing three or more entities, especially with a foreign subsidiary or meaningful trading between entities. Two entities in a single currency with light intercompany activity can often hold in a well-maintained spreadsheet for a while longer.
What happens if intercompany transactions aren’t eliminated properly?
Revenue and costs get double-counted at group level, which inflates reported turnover and can distort margin and profitability figures. It also tends to surface as an uncomfortable question during external audit, since auditors specifically check that intercompany balances net to zero.
Do all entities in a group need to use the same accounting software?
No, though it makes consolidation considerably easier if they do, or at least share a common chart of accounts structure. Where entities run different systems, a consolidation layer or ERP that can pull and map data from multiple sources becomes essential rather than optional.
How often should group consolidation actually happen?
Monthly is standard for businesses that want management reporting to mean something in real time. Some groups only formally consolidate quarterly or annually, but that usually means leadership is making decisions on entity-level figures alone in between, without the group-level picture.
