Let's be direct: after your third acquisition, the spreadsheet breaks. Not because of a formula error or a corrupted file, but because the finance function you designed for two entities cannot absorb the complexity of stub-period calculations, intercompany loan interest in three currencies, and goodwill that isn't native to Xero.
Your CFO is chasing month-end close for eighteen days. The PE sponsor wants consolidated management accounts by day ten. HMRC expects Making Tax Digital submissions that reconcile across entities. Companies House filings loom. And somewhere in the chaos, an intercompany recharge sits unreconciled because Entity A uses nominal code 7200 for "Management Fees" while Entity B calls it "Recharges – Head Office."
The brutal reality: most finance teams at roll-ups are still manually consolidating in Excel well beyond acquisition five. Not because they love pivot tables, but because no one paused deal flow long enough to build the financial infrastructure that scales.
This isn't a technology problem. It's an execution problem. Multi-entity accounting consolidation is the unsexy, mission-critical backbone that determines whether your board sees accurate numbers or polite fiction. What follows covers the three consolidation models, the precise point where each breaks, what your PE sponsors actually expect, and a decision framework that matches your approach to portfolio complexity -- not aspiration.
Why Multi-Entity Consolidation Breaks Down After Acquisition Three
Here's the math. Acquisition one: you add a subsidiary to the group structure, map a dozen nominal codes, and produce consolidated management accounts in Excel. Close in twelve days. Uncomfortable but manageable.
Acquisition two: you now have three legal entities (HoldCo, OpCo A, OpCo B). Intercompany transactions emerge-management fees, shared service recharges, intercompany loans. You build an elimination tab in Excel. Close stretches to fifteen days. The FD grumbles but it works.
Acquisition three changes everything. Why? Because complexity doesn't scale linearly-it compounds.
What breaks:
- Stub-period arithmetic. You acquire Entity C on 18 September. Your year-end is 31 December. Now you're consolidating ten months of historical performance under prior ownership (which you don't control or trust) plus two and a half months post-acquisition. The trial balance has to be split, pre-acquisition goodwill calculated, and fair value adjustments reflected. Excel isn't built for this.
- Goodwill and fair value adjustments. Under IFRS 3, you recognise goodwill as the difference between purchase consideration and net identifiable assets. Neither Xero nor QuickBooks track goodwill natively. You're maintaining it in a separate schedule, manually adding amortisation (if you're not applying the impairment-only model), and praying no one asks for a detailed breakdown mid-month.
- Intercompany reconciliation at scale. Three entities mean six potential intercompany relationships (A–B, A–C, B–C, and the inverse). A £50,000 management recharge from HoldCo to OpCo B should appear as income in HoldCo and expense in OpCo B. If it doesn't match to the penny, your consolidated P&L is wrong. One mismatch and you're hunting through email threads at 11 p.m. the night before board.
- Foreign exchange revaluation. If one acquired entity operates in EUR or USD, you're now translating balance sheets at closing rates and P&Ls at average rates, then recognising translation differences in equity. IFRS 10 requires this. Excel does not automate it.
- Different year-ends. IFRS allows subsidiaries to have reporting dates up to three months different from the parent, provided you adjust for material transactions in the gap. If Entity C has a 31 March year-end and HoldCo uses 31 December, you're preparing interim financials for consolidation purposes every month. Manual load increases 30%.
- Control gaps. Entity A depreciates IT equipment over three years. Entity B uses five. One capitalises software development: the other expenses it. Unless you impose group accounting policies and restate prior periods, your consolidated numbers mix apples and hand grenades.
The result: Month-end close drifts past twenty days. The CFO burns weekend hours. Someone builds a "reconciliation of reconciliations" tab. Errors creep in. Auditors flag intercompany mismatches in the year-end pack. The PE sponsor starts asking pointed questions about finance function maturity.
This is when roll-ups start searching for "multi-company accounting software" at 2 a.m. Not when it's convenient. When it's already breaking.
The Three Consolidation Models: Manual, Multi-Company Accounting Software, and Dedicated Platforms
There are three ways to consolidate a group. Each works-until it doesn't. The failure mode is predictable, and it's always a function of entity count, transaction volume, and sponsor reporting expectations.
Excel and Manual Journals: Where Most Roll-Ups Start
You export trial balances from each entity's accounting system (Xero, Sage, QuickBooks), paste them into a consolidation workbook, map nominal codes to a standard chart of accounts, and manually enter elimination journals for intercompany transactions.
When it works: One to three entities, simple structure, low intercompany volume, year-ends aligned, no foreign currency.
When it breaks:
- Beyond three entities, the elimination matrix becomes unmanageable.
- Intercompany mismatches require manual investigation every month.
- Version control fails: someone updates the September pack in October, and no one notices until the auditors arrive.
- No audit trail for who changed what, when.
- FX revaluation and goodwill amortisation live in separate tabs that may or may not feed the consolidated P&L correctly.
The hidden cost: Senior finance time. Your FD or financial controller-who should be analysing variances and supporting operational decisions-spends five days a month copying, pasting, and reconciling. Opportunity cost is brutal.
Multi-Company Accounting Software: Xero, QuickBooks, and NetSuite
These platforms can manage multiple legal entities, but their approaches differ significantly.
Xero sells separate subscriptions per organisation (legal entity). Each org has its own chart of accounts, bank feeds, and VAT return. There is no native consolidation module. To produce group accounts, you either:
- Export trial balances and consolidate in Excel (back to model one), or
- Use a third-party add-on like Fathom, Spotlight Reporting, or Futrli to pull data via API and generate consolidated management reports.
Xero works well for UK SMEs with straightforward structures. It handles Making Tax Digital for VAT, integrates with cloud banking, and accountants love it. But it was never designed for multi-entity roll-ups.
QuickBooks Online Advanced offers a similar model: separate company files, third-party reporting tools for consolidation. Again, no native intercompany elimination or group chart of accounts enforcement.
NetSuite OneWorld is different. It's a true multi-entity ERP. You can:
- Manage multiple subsidiaries in a single instance.
- Define intercompany relationships and automate elimination entries.
- Handle multi-currency, multi-book accounting (UK GAAP, IFRS), and real-time consolidated reporting.
- Enforce a global chart of accounts or allow subsidiary-specific segments.
NetSuite is overkill for a three-entity roll-up turning over £8M. It's right-sized for a ten-entity portfolio doing £50M+ with international operations and PE-grade reporting requirements. Implementation takes four to six months and costs £80K–£200K+ depending on complexity.
The gap: Most UK roll-ups sit between "too complex for Xero" and "not ready for NetSuite." That's where dedicated consolidation tools enter.
Dedicated Consolidation and EPM Tools
Platforms like Accountsiq, Silverfin, Fathom, Spotlight Reporting, and Xledger are purpose-built for group accounting consolidation. They sit on top of your entity-level accounting systems (Xero, Sage, QuickBooks) and automate:
- Multi-entity reporting with drill-down to entity-level detail.
- Intercompany matching and elimination-flag mismatches, suggest journals, automate eliminations on consolidation.
- Chart of accounts mapping-map subsidiary codes to group codes without forcing entity-level change.
- FX translation using live or historical rates.
- Variance analysis, budgeting, and forecasting at group and entity level.
- Audit trail and version control-who changed what, when, and why.
Accountsiq is popular with UK mid-market groups. It's a cloud GL that natively supports multi-entity, intercompany, and consolidation. You migrate entities onto Accountsiq, define group structure, and get real-time consolidated reporting. Cost: £150–£400/month depending on entities and users. Implementation: six to twelve weeks.
Fathom and Spotlight Reporting are BI and reporting layers. They connect to Xero or QuickBooks via API, pull data, and produce management packs. They don't replace your accounting system-they make it reportable. Good for roll-ups that want to keep Xero but need group-level dashboards and KPIs. Cost: £50–£200/month per entity.
Which to choose? If your entity-level accounting works (Xero is fit for purpose, teams are trained, processes are embedded), add a reporting layer. If entity-level accounting is also broken-inconsistent processes, poor data quality, weak controls-consider migrating to a platform like Accountsiq or NetSuite that enforces structure.
Either way, the decision should be made before acquisition four, not after acquisition eight when the problem is compounding faster than revenue growth.
Group Accounting Consolidation Requirements: What Your PE Sponsor Expects
PE sponsors don't care about your software. They care about accurate, timely, decision-useful financial information. Here's what "good" looks like in their eyes:
Monthly management accounts by day ten. Not draft. Not "pending intercompany reconciliation." Final consolidated P&L, balance sheet, cash flow, and variance commentary. Ten working days post-month-end is the benchmark. If you're closing in twenty days, you're behind.
Standardised chart of accounts across the group. Sponsors want to compare like-for-like across entities and time periods. If Entity A calls it "Staff Costs" and Entity B calls it "Payroll," your consolidated reporting is a mess. You need a group CoA with mappings maintained at subsidiary level.
Intercompany reconciliation and elimination. All intercompany balances and transactions must reconcile and be eliminated on consolidation. Mismatches erode trust. If your auditors find unexplained intercompany differences at year-end, expect pointed questions about finance function competence.
Real-time visibility into subsidiary performance. Sponsors want dashboards that show revenue, EBITDA, cash, and KPIs by entity and in aggregate-updated weekly or daily, not monthly. This requires integrated systems and clean data.
Compliance and statutory filings. Each UK subsidiary must file accounts with Companies House and tax returns with HMRC. Group must produce consolidated accounts if it meets statutory thresholds. Missing deadlines or filing incorrect data damages reputation and triggers penalties.
Audit readiness. If your group is audited, auditors will test consolidation mechanics: intercompany eliminations, FX translation, goodwill, non-controlling interests. Weak documentation and manual processes lead to qualified opinions or management letters highlighting control deficiencies.
Budget vs. actual and forecast accuracy. Sponsors expect you to build bottoms-up budgets by entity, consolidate them, and track performance monthly. Variance commentary should explain why Entity C missed EBITDA target by 12% and what you're doing about it.
The unspoken expectation: your finance function should be a source of competitive advantage, not a bottleneck. If the CFO is too buried in month-end close to support strategic decisions, integration planning, or due diligence on the next acquisition, you have a problem.
Most roll-ups underinvest in finance infrastructure relative to deal flow. They'll spend £50K on legal and tax advice for an acquisition, then ask the FD to consolidate it in Excel for free. That's a false economy. The cost of poor financial visibility-missed synergies, delayed decisions, talent attrition, sponsor frustration-far exceeds the cost of fit-for-purpose systems.
Multi-Entity Xero Setup: When It Works and When It Doesn't
Xero dominates UK small business accounting for good reason: intuitive UI, strong Making Tax Digital compliance, excellent bank feed integrations, vast accountant and app ecosystem. Many acquired companies already use it. The question is whether Xero can scale to support group consolidation, or whether you hit a ceiling.
Xero's Multi-Company Capabilities and Limitations
Xero treats each legal entity as a separate organisation. You subscribe once per organisation. Each org has:
- Its own chart of accounts (you can copy a template, but changes don't cascade).
- Its own bank accounts, invoicing, inventory, fixed assets.
- Its own VAT return and Making Tax Digital submission.
- Separate user permissions (though a single Xero login can access multiple orgs via the "Switch Organisation" dropdown).
What Xero does well for multi-entity:
- Subscription economics are reasonable. At £30–£50/month per entity (depending on plan), a five-entity group pays £150–£250/month. Cheaper than NetSuite by an order of magnitude.
- Familiarity and training. If acquired companies already use Xero, you avoid migration pain and retraining.
- VAT and statutory compliance. Each entity files its own VAT return via MTD API. Works smoothly.
What Xero doesn't do:
- No native consolidation. There is no "group reporting" module. You cannot press a button and generate consolidated P&L.
- No intercompany automation. If HoldCo raises a £10K management fee invoice to OpCo A, you manually enter the invoice in HoldCo and the bill in OpCo A. They're separate transactions in separate systems. Reconciliation is manual.
- No enforced group chart of accounts. Each org can drift. Without governance, Entity A renames codes, Entity B adds new ones, and your consolidation mapping breaks.
- No multi-currency consolidation. If Entity C operates in EUR, you'll translate its trial balance in Excel for group reporting. Xero won't do it.
- No goodwill or fair value adjustment tracking. These sit outside Xero in spreadsheets.
When Xero works for multi-entity:
- Two to four UK entities.
- Same currency (GBP).
- Low intercompany transaction volume (under twenty per month).
- Year-ends aligned.
- CFO or financial controller comfortable with Excel-based consolidation.
- No PE sponsor demanding real-time dashboards.
When it doesn't:
- Five-plus entities.
- International subsidiaries (multi-currency).
- High intercompany volume.
- Complex group structure (sub-holdings, non-controlling interests).
- PE reporting requirements.
- Acquisitions happening faster than you can manually consolidate.
Intercompany Elimination and Reporting Workarounds
If you're committed to Xero multi-entity, here's how to make it survivable:
1. Standardise the chart of accounts across all Xero orgs. Build a group CoA in Excel. Roll it out to every entity. Lock it down: no one adds or renames codes without CFO approval. Use Xero's account code import feature to enforce consistency.
2. Tag intercompany transactions. Xero allows custom tracking categories. Create a category called "Intercompany" with values for each entity (HoldCo, OpCo A, OpCo B). Tag every intercompany transaction. This makes reconciliation easier-you can filter and export.
3. Use consistent narrative and reference conventions. Every intercompany invoice should have a reference number that matches the corresponding bill (e.g., "IC-2024-11-001"). Discipline here saves hours at month-end.
4. Export and consolidate in Excel or Google Sheets. At month-end, export trial balances from each Xero org (Reports > Account Transactions). Import into a consolidation workbook. Map codes to group CoA. Sum across entities. Manually enter elimination journals for intercompany balances and transactions.
5. Consider third-party reporting tools. Apps like Fathom, Spotlight Reporting, or Futrli connect to multiple Xero orgs, pull data via API, and generate consolidated management reports and dashboards. They won't automate intercompany elimination, but they reduce copy-paste and improve presentation. Cost: £40–£150/month depending on entity count and features.
Real talk: This is an interim solution, not an end state. If you're doing six acquisitions in eighteen months, Xero + Excel will break. Plan the migration to proper multi-entity software now, execute it between acquisitions four and five, and avoid the crisis at acquisition nine.
The Decision Framework: Matching Consolidation Approach to Portfolio Complexity
Choosing your consolidation model isn't about what's "best." It's about what fits your current complexity, growth trajectory, and finance team capability. Here's a practical framework:
Low complexity: 1–3 entities, <£10M group revenue, single currency, aligned year-ends, no PE sponsor.
- Recommended approach: Xero (or QuickBooks) per entity + Excel consolidation or lightweight reporting tool (Fathom, Spotlight).
- Why it works: Cost-effective, fast to set up, and uses existing skills.
- When to revisit: At entity four, or when PE investment introduces formal reporting requirements.
Medium complexity: 4–8 entities, £10M–£50M revenue, single or dual currency, PE-backed, monthly board reporting required.
- Recommended approach: Dedicated multi-entity platform (Accountsiq, Xledger) or NetSuite if you also need operational ERP (inventory, order management, CRM).
- Why it works: Automates intercompany, enforces group policies, real-time dashboards, audit trail, scalable to 15+ entities.
- Timeline: Three to six months to carry out, including data migration, CoA standardisation, training.
- Cost: £150–£600/month software + £15K–£50K implementation depending on complexity.
High complexity: 9+ entities, £50M+ revenue, multi-currency, international operations, complex group structure, institutional PE or public market aspirations.
- Recommended approach: NetSuite OneWorld, SAP Business One, or Sage Intacct. Potentially add EPM layer (Adaptive Insights, Planful) for FP&A.
- Why it works: Enterprise-grade consolidation, multi-GAAP, intercompany automation, statutory reporting, integration with operational systems.
- Timeline: Six to twelve months implementation.
- Cost: £100K–£300K+ implementation, £3K–£10K/month software.
Key decision factors:
- Acquisition velocity. If you're doing one acquisition per year, you have breathing room. If you're doing one per quarter, you need infrastructure that absorbs new entities fast.
- Finance team maturity. A three-person finance team (FD, management accountant, AP clerk) cannot support a complex ERP implementation while running BAU. Either hire ahead of need, or bring in external support (like us).
- PE sponsor expectations. If your sponsor sits on ten portfolio company boards, they've seen good and bad finance functions. They'll compare you to peers. If peers deliver day-eight management accounts and you deliver day-twenty, you're the problem child.
- Data quality and process maturity. Migrating bad data and broken processes into expensive software doesn't fix anything-it just makes the problems faster and more visible. Clean up first, then migrate.
The trap: Believing software alone solves the problem. It doesn't. Software enables good process. If your intercompany process is "email the FD and hope," no platform will fix that. You need:
- Documented policies (group accounting manual, intercompany pricing, overhead allocation).
- Defined roles (who raises intercompany invoices, who reconciles, who signs off).
- Governance (monthly intercompany reconciliation sign-off before consolidation).
- Training (entity finance teams need to understand why tagging and coding matter).
It's a common pattern: roll-ups buy NetSuite, spend £150K on implementation, then realise no one documented how cost allocations should work. The system is capable: the organisation isn't ready. Execution, not strategy.
Implementation Realities: Timelines, Data Migration, and Chart of Accounts Standardisation
Here's what actually happens when you carry out a multi-entity accounting consolidation project. Not the vendor's slide deck version -- the version where someone has to reconcile three years of intercompany loan history at 9 p.m. on a Thursday.
Typical timeline for a mid-market roll-up (five entities, moving from Xero-per-entity + Excel to Accountsiq or similar):
- Weeks 1–2: Discovery and design. Map current state: entities, intercompany relationships, chart of accounts variance, data quality issues. Define target group CoA. Design intercompany process. Identify integration requirements (bank feeds, payroll, expenses). Document accounting policies that need alignment (depreciation, revenue recognition, accruals).
- Weeks 3–6: Configuration and data migration. Set up group structure in new platform. Build and test group CoA. Map subsidiary codes to group codes. Migrate opening balances (usually one full fiscal year of history minimum, for comparatives). Migrate master data: customers, suppliers, products, cost centres. Configure intercompany accounts and elimination rules.
- Weeks 7–10: Testing and training. Parallel run: process one month in both old and new systems. Reconcile. Fix discrepancies. Train entity finance teams on new processes (how to code intercompany transactions, use tracking categories, run reports). Train head office team on consolidation process, dashboards, month-end checklist.
- Weeks 11–12: Go-live and hypercare. Cut over. First full month-end close in new system. Expect it to take longer than BAU-budget fifteen days instead of ten. Daily standups to triage issues. Document workarounds. Refine processes.
- Weeks 13–16: Stabilisation. Second and third month-end closes. Speed improves. Confidence builds. Reporting becomes routine.
Total elapsed time: Three to four months. That's realistic for a well-scoped, well-supported project. If you're also doing two acquisitions in that window, add six to eight weeks.
The data migration challenge is always underestimated. It's not the volume-it's the variety and the exceptions. Common issues:
- Duplicate suppliers. Entity A has "ABC Ltd" and "ABC Limited" and "ABC." Are they the same? Probably. But someone has to confirm and merge.
- Inconsistent GL coding. One entity capitalises software licences (fixed assets), another expenses them (opex). You can't consolidate until you decide group policy and restate.
- Unreconciled intercompany. Entity A shows a £22,000 receivable from Entity B. Entity B shows a £19,500 payable to Entity A. The difference? An invoice dated 28 March that Entity B coded to April. You have to find it, agree it, and decide which period it belongs in.
- Historical FX gains/losses. If an entity previously operated standalone and has EUR transactions, legacy FX movements might be buried in "miscellaneous income." On migration, you need to reclassify for group reporting consistency.
Chart of accounts standardisation is the foundation. Do this badly and everything else breaks. Our approach:
- Start with a reference CoA. Use a template appropriate to your industry (service businesses don't need twenty inventory codes). Accountsiq and NetSuite provide starter templates: adapt, don't reinvent.
- Define coding principles. How many levels (account code, department, project, intercompany entity)? What's mandatory vs. optional? What's the naming convention?
- Map, don't force-migrate. Let subsidiaries keep their existing codes in their local Xero instance if that's where day-to-day coding happens. Maintain a mapping table that translates local codes to group codes for consolidation. This reduces disruption.
- Lock it down. Once the group CoA is live, changes require CFO approval and a formal change log. Otherwise, drift starts immediately.
- Train and audit. Entity finance teams need to understand how their coding affects group reporting. Spot-check coding monthly for first three months, then quarterly.
The governance and change management piece is harder than the tech. If the acquired FD has been running their business for eight years and you tell them they can't add a new nominal code without head office approval, expect resistance. This is where tone matters. Frame it as "ensuring we can give the board accurate consolidated numbers" not "head office knows best."
Common failure modes we see:
- Trying to do it alongside three other integration projects. The CFO is also migrating email, consolidating insurance, and renegotiating banking. Finance systems get delayed. Do it early or do it standalone-don't bury it in a mega-project.
- Underestimating training needs. Rolling out new software without proper training guarantees poor adoption and bad data. Budget two half-day sessions per entity: one on process, one on system.
- Skipping the parallel run. Going live without a full month of parallel processing is high-risk. You won't discover the edge cases until they bite you at month-end.
- No project manager. The CFO cannot project-manage this while running BAU. Assign a project lead (internal or external) who owns timeline, risks, and decisions.
The pattern across mid-market roll-ups is consistent: if you scope properly, migrate carefully, and train thoroughly, you'll be stable by month three. If you rush, skip steps, or assume "the software will handle it," you'll still be firefighting at month nine.
Stop Collecting Problems: Build the Finance Infrastructure Before Acquisition Four
Multi-entity accounting consolidation isn't a software decision-it's an operating model decision. The platform you choose should follow from the complexity you have and the trajectory you're on, not the other way around.
If you're at acquisition three and still consolidating in Excel, that's fine-for now. But if you're planning acquisitions four, five, and six in the next eighteen months, you're collecting problems. The cost of delay compounds: slower closes, weaker controls, frustrated finance teams, and sponsors questioning your scalability.
The good news: this is a solved problem. Hundreds of roll-ups have walked this path. The tooling exists (Xero + add-ons for simple groups, Accountsiq and Xledger for mid-market, NetSuite for complex international portfolios). The processes are documented. The implementation timelines are predictable.
What's not solved is execution. You need someone to scope it, manage the data migration, standardise the chart of accounts, train the teams, and run the parallel month-end that proves it works before you cut over. That someone is either an internal hire (a finance systems lead or project accountant), a consultancy you'll pay £1,500/day, or a partner who's done this before and knows where the bodies are buried.
We're that partner. We help roll-ups move off Excel, implement the right multi-entity platform, build intercompany processes that actually reconcile, and train finance teams to use them -- all while you keep running the business and closing the next acquisition.
If you're anywhere between "this is starting to hurt" and "this is definitely broken," we should talk. No pressure, no pitch-just a scoping conversation to map where you are, where you need to be, and what the path looks like. Get in touch.
