When acquisition is the operating model, finance integration stops being a project and becomes a capability
THE SHORT VERSION
Buy and build finance integration is the work of making each acquired company’s numbers reliable and consolidated into the group, done repeatedly and to a repeatable standard. In a buy and build strategy the acquisition is not the exception, it is how the group grows, so the same integration work returns every few months.
The risk is not any single deal. It is accumulation: an unmapped chart of accounts here, an unreconciled intercompany balance there, a subsidiary that never made a group deadline, all carried forward until the consolidation no longer closes cleanly.
The fix is to standardise four things once, the account mapping, the reporting package, the closing calendar and the data quality bar, and apply them to every bolt-on from day one rather than retrofitting them at year three.
Buy and build finance integration is the discipline of turning every newly acquired company into a subsidiary the group can report on, repeated deal after deal without the effort growing each time. In a buy and build strategy the acquisition is the growth engine, not a one off event, so the finance function is never integrating a single company. It is running a line of them. That changes the job. This article sets out how finance integration behaves differently when it happens on repeat, where the accounting debt quietly accumulates across a platform, and how a Group Finance team turns integration from a series of rescues into a standing capability with a fixed method.
On this page
What Buy and Build Changes About Finance Integration
In a buy and build strategy, finance integration is a recurring process rather than a one time event, so it has to be designed as a repeatable method instead of solved fresh for each deal. Integrating one acquisition well is a project with a start and an end. Integrating the fourth, seventh and tenth is a production line, and a production line fails differently: not on any single unit, but on the variation between units and the backlog that builds when the line runs faster than the team.
Three shifts follow from that:
- Cadence. A standalone integration can absorb a slow start. In a buy and build, the next deal often closes before the last one has made a clean group submission, so integrations overlap and compete for the same finance people.
- Consistency. If each subsidiary is mapped to the group chart of accounts by a different person using a different judgement, the consolidation carries ten different interpretations of the same reporting line.
- Compounding. Every shortcut taken to hit a deadline stays in the numbers. Unlike a single deal, there is no quiet year afterwards to clean it up, because the next acquisition is already in the pipeline.
Where the Accounting Debt Accumulates
Accounting debt is the group’s equivalent of technical debt: work deferred under deadline pressure that has to be repaid later, with interest, usually at the worst possible moment. In a buy and build it collects in a few predictable places.
- Chart of accounts mapping. A bolt-on is mapped roughly to hit the first close, with several local accounts pushed into a group “other” line. That mapping is never revisited, so a material cost sits in a catch-all account for years and no one can explain the movement when the auditor asks.
- Intercompany balances. Once a platform trades between its own entities, mismatches appear. If a new subsidiary is not brought into the group’s intercompany process on entry, its balances drift, and the elimination at consolidation leaves a residual that grows each month. The mechanics of clearing that are covered in how to reconcile intercompany balances after an acquisition.
- Opening balances that were never substantiated. A subsidiary is consolidated on trust because there was no time to test its opening balance sheet. Two years on, an accrual booked at acquisition is still there, and no one knows whether it should be released.
- Closing calendars that were agreed but never enforced. The subsidiary submits late every month. The group works around it every month. The workaround becomes the process, and it does not scale to the next five deals.
THE FAILURE MODE TO WATCH
The classic buy and build failure is a consolidation that stops tying out. Each individual subsidiary looks fine on its own trial balance, but the group’s intercompany eliminations leave a residual of, say, 180,000 euros that no one can trace, because three different bolt-ons booked the same cross charge three different ways. It is never one big error. It is a dozen small, consistent-looking ones that only conflict when they meet in the consolidation.
The Four Things to Standardise Once
The point of a buy and build integration method is that these four decisions are made once, written down, and applied to every deal, so the eleventh integration is not re-litigating what the second one already settled.
| Standard | What it fixes | Set before the first close |
|---|---|---|
| Group chart of accounts and mapping template | Ten interpretations of the same reporting line | A fixed mapping table each subsidiary completes, reviewed centrally, not left to local judgement |
| Standard reporting package | Every subsidiary sending a different spreadsheet | One package format, same tabs, same subtotals, same validation checks |
| Group closing calendar | Late submissions worked around by hand | A published timetable with a working day 4 to 6 subsidiary deadline, rehearsed on prior period data |
| Data quality bar | Unsubstantiated balances carried forward | A minimum standard: every material balance supported, before the entity counts as integrated |
Getting a subsidiary to where it can submit at all is a defined piece of work, set out in how to prepare a subsidiary that is ready for group reporting. A serial acquirer runs that same sequence on every entity rather than improvising it.
Standardisation does not mean replacing every local system on day one. That is slow, risky and rarely necessary. It means the group defines the output it needs and the standard the numbers must meet, and lets the local system feed it until a migration is genuinely worth the disruption.
A Worked Example: The Third Bolt-On
The figures below are illustrative, not a real engagement, and are used only to show how the numbers behave.
A group has a platform company and two prior bolt-ons. It acquires a third, a distributor with about 45 million euros of revenue and a small finance team of 4 people. Using a standard method rather than starting from scratch, the integration runs like this:
- Week 1. The standard data request pack goes out. The subsidiary returns its trial balance, its accounts receivable aging and its fixed asset register in the group’s template, because the template is pre-built.
- Weeks 2 to 4. The mapping template is completed and reviewed centrally. Of about 320 local accounts, roughly 290 map cleanly and 30 need a decision. Because the group has settled these decisions on two prior deals, 24 of the 30 are answered by precedent in a day.
- Week 4. A trial close is run on the prior month. It surfaces a 60,000 euro intercompany mismatch on management charges, found and fixed before the first live close rather than during it.
- Weeks 5 to 6. First live submission into the group package, on the group deadline, with a residual small enough to clear inside the close window.
The first bolt-on took this group about 12 weeks to a clean submission. The third took 6, not because the company was simpler, but because the method already existed. That compression is the entire return on treating integration as a capability.
When a One Off Integration Is Still the Right Call
The standard method has a boundary. It assumes the acquired company keeps recognisable accounting records: a trial balance that ties, sub-ledgers that reconcile to control accounts, and a finance person who can answer questions. When that assumption breaks, forcing the standard timeline does more harm than good.
- If a target has no monthly close and no sub-ledger detail, only an annual statutory position, the first job is to rebuild basic records, not to map it into the group package. Treat it as a remediation project on its own clock, then bring it onto the standard method once it can produce a monthly trial balance.
- If a carve-out has no standalone financial history, its opening balance sheet has to be constructed before any mapping is meaningful.
- If the local finance manager leaves at closing, knowledge transfer becomes the critical path, and no template compensates for it.
The method is what makes the normal case fast. Recognising which deals are not the normal case is what keeps the method from breaking. What a Group CFO should check on entry, to tell the two apart quickly, is covered in what to review immediately after an acquisition.
Who Owns Integration Across the Platform
In a one off deal, finance integration can be run by whoever has capacity. Across a buy and build it needs a named owner, because the value is in consistency across deals and consistency has to be held by someone.
Integration owner
Group level
Owns the method, the templates and the standard. Decides the mapping precedents so they are not re-argued each deal.
Deal integration lead
Per acquisition
Runs one integration to the standard, from data request to first clean close, and hands the entity to business as usual.
Local finance
Subsidiary
Produces the numbers to the group standard once trained. The aim is to make them self sufficient, not dependent.
Consolidated accounts are a legal requirement for the parent, and listed groups must prepare them using EU endorsed IFRS under Regulation 1606/2002, which requires uniform accounting policies across the group. A buy and build makes that harder with every deal, which is why the method has to hold. The full sequence is set out in the guide to the first 100 days of finance integration.
NEXT STEP
A buy and build only stays fast if each integration is done properly and on time, and that lands on a finance team already closing its own books. If you need additional capacity to run a bolt-on integration to your group standard, our post acquisition data check covers the entry review, and you can discuss your finance integration project with our team.
Frequently Asked Questions
What is buy and build finance integration?
Buy and build finance integration is the repeatable work of making each acquired company’s financial data reliable and consolidated into the group. Because a buy and build strategy grows through many acquisitions, integration recurs constantly, so it is run as a standard method with fixed templates rather than solved fresh for each deal.
Why is finance integration harder in a buy and build than in a single acquisition?
Because the integrations overlap and compound. The next deal often closes before the last one reports cleanly, so they compete for the same finance people. Shortcuts taken to hit a deadline stay in the numbers, and there is no quiet year afterwards to fix them, because another acquisition is already in the pipeline.
Should a serial acquirer put every subsidiary on the same accounting system?
Rarely at first. Replacing a live accounting system during integration risks the local close and the audit trail. Most groups standardise the output instead: one reporting package, one mapping standard, one closing calendar, and defer any system migration until the entity has produced two or three clean closes.
How do you stop accounting debt building up across a platform?
Set a data quality bar as a gate: an entity does not count as integrated until every material balance is supported and its intercompany balances reconcile. Enforcing the bar per deal, rather than deferring it, is what stops small unresolved items accumulating into a consolidation that no longer ties out.
Brahim Rami | Member of institute of chartered accountants in Morocco
He is a CPA and tax advisor, founder of NeoExpertise.net, a Legal and Tax firm helping foreign companies with business setup, due diligence, payroll, and tax compliance in Morocco and Africa.
