I've seen post-acquisition finance integration across Central Europe and through a series of bolt-on acquisitions at a PE-backed consultancy. The pattern is always the same. The deal closes, everyone celebrates, and then someone turns to the finance team and says: "Right, when can we have one set of numbers?"
The honest answer is usually "longer than you think." And the reason is almost never the one people expect.
It's not a systems problem
When a business acquires another business, the instinct is to treat finance integration as a technology project. Which ERP wins? How do we migrate the data? Can we just put everyone on the same system?
These are valid questions. They're also the wrong starting point.
At another client, we had multiple legacy systems across several countries, each with its own reporting conventions, its own language (literally), and its own way of interpreting group accounting policies. The natural impulse was to start with systems convergence. We resisted that impulse, and it was the best decision we made.
The real problems in finance integration are human. They're about two teams who've never worked together, who have different definitions of the same terms, who do the same tasks in different ways, and who are frightened about their jobs.
Start with a systems migration before you've addressed those issues and you'll automate the dysfunction.
I've seen it happen. It's expensive and demoralising.
The cultural dimension nobody budgets for
Here's something that never appears in the integration plan: the acquired finance team is terrified.
They don't know if they'll have a job in six months. They don't know if the acquiring company thinks they're competent. They don't know if the way they've been doing things for the last ten years is about to be declared wrong. So they do what any rational person would do. They keep their heads down, protect their processes, and resist change at every opportunity. Not because they're difficult. Because they're human.
Integrating finance teams across Central Europe taught me this lesson the hard way. We had brilliant people in the acquired entities who had deep knowledge of local regulations, customer relationships, and operational nuances. In the first few weeks, we almost lost several of them because the integration felt like an occupation rather than a collaboration.
What changed things was simple. We asked people about their processes before we told them about ours. We identified what the acquired teams did better than us (there's always something) and adopted those practices instead of imposing our own. We made explicit commitments about roles and timelines so people could stop catastrophising and start contributing.
We didn't show the presentations about "the group way." We listened instead. What works well here? What are you proud of? What frustrates you? Those conversations surfaced more useful information than any due diligence report.
The chart of accounts problem
If you're running a buy-and-build strategy, this will be familiar. Every acquired business arrives with its own chart of accounts. Its own cost centre structure. Its own revenue categories. Its own definition of what constitutes an overhead versus a direct cost.
At the PE backed consultancy, after four acquisitions, we had four different charts of accounts. One entity categorised subcontractor costs as direct costs. Another categorised the same costs as cost of sales. A third split them between two categories depending on the contract type. When we tried to produce consolidated management accounts, the numbers were technically correct at entity level and completely meaningless at group level.
This problem compounds over time. The longer you leave each entity on its own chart of accounts, the harder convergence becomes. People build reports, budgets, and KPIs around their local structure. Changing it feels like changing everything.
The solution is to converge early, but converge intelligently. Don't just impose the acquiring company's chart of accounts. Build a group chart that works for all entities, informed by what you find in each one. If the acquired business has a smarter way of categorising project revenue, use that. The goal isn't to make them like you. It's to build a common language that serves the group.
At the PE backed consultancy, we ultimately built a unified chart of accounts that borrowed elements from three of the four entities. It took about eight weeks of detailed work with the finance leads from each business. It was tedious. It was also the single most important thing we did for the integrity of group reporting.
The first 100 days: a practical sequence
Based on what I've learned across multiple integrations, here's the sequence that works. The temptation is to do everything at once. Don't.
Integration is sequential because trust is sequential. You can't standardise processes with people who don't trust you yet.
Days 1-14: Listen and stabilise. Don't change anything. Run listening sessions with every member of the acquired finance team. Understand their processes, their pain points, their concerns. Simultaneously, make sure the basics are working: can you produce management accounts, can you pay suppliers, can you meet payroll. If the acquired business was well-run, the answer is yes. Leave it alone for now.
Days 15-30: Map and compare. Document both finance functions side by side. Every process, every report, every reconciliation. Identify where processes differ and, critically, why they differ. Sometimes the acquired team does something differently because they're wrong. Sometimes they do it differently because they're dealing with a complexity you don't have. You need to know which is which.
Days 30-60: Design the target. Define the target operating model for the integrated finance function. Unified chart of accounts. Standardised close process. Common reporting pack. Agreed KPI definitions. Involve people from both sides in designing this. It takes longer than doing it yourself, but the result is something people will actually follow.
Days 60-90: Implement the foundation. Migrate to the unified chart of accounts. Implement the standardised close process. Run the first integrated month-end. It will be messy. That's fine. You're learning.
Days 90-100: Review and adjust. After the first integrated close, do a thorough retrospective. What worked? What didn't? Where are the remaining pain points? Adjust the plan. You're not done at Day 100, but you should have a functioning integrated finance operation that produces reliable group numbers.
The mistakes I see every time
Waiting too long to start. Every month you delay integration is a month of duplicated effort, inconsistent reporting, and growing divergence between how the two teams work. I've seen businesses wait 12 months before starting finance integration. By that point, the acquired team has settled into their existing processes even more deeply, and the political cost of change has tripled.
Trying to do everything at once. A PE operating partner once asked me to deliver full finance integration, including systems migration, in 60 days. I explained that we could have it fast, or we could have it right, but not both. We agreed on 100 days for process and reporting integration, with systems migration to follow over the next six months. That sequencing worked. The alternative would have been chaos.
Ignoring the human side. This is the most common and most expensive mistake. You can build the perfect target operating model, but if the people who need to operate it feel excluded, unheard, or threatened, it won't work. I've seen finance teams lose their best people within weeks of an acquisition, not because the integration was bad, but because nobody told them they were valued.
Imposing rather than integrating. "We're the acquirer, so we do it our way" is a recipe for passive resistance and talent loss. Integration means finding the best approach from both sides and building something new. Once, some of the most effective processes in the integrated function originated in the acquired entities. If we'd simply imposed the existing corporate way, we'd have lost those improvements and the people who created them.
The real cost of getting it wrong
Let me be specific about what failure looks like, because it's not abstract.
Extended timelines mean the PE sponsor is flying blind. If you can't produce reliable consolidated numbers for six or nine months after an acquisition, the board is making decisions based on incomplete or inconsistent data. I've seen investment decisions delayed and follow-on acquisitions paused because the finance function couldn't provide a credible view of group performance.
Lost talent is permanent damage. A good management accountant who leaves three months after acquisition takes years of institutional knowledge with them. In one integration I observed (not one I ran), the acquired entity lost its entire finance team within four months. The cost of rebuilding, including temporary contractors, recruitment fees, and lost productivity, was roughly £350K. That wasn't in anybody's integration budget.
Unreliable numbers erode trust.
Once a PE sponsor stops trusting the numbers, every board meeting becomes an interrogation rather than a discussion.
I've seen this dynamic take 18 months to repair. The finance team produces good numbers, but the board questions everything because they got burned once. That's a terrible environment for everyone.
What good looks like
The integration programme I led delivered a 70% increase in efficiency across the finance function and a 50% reduction in administrative spend. Those aren't theoretical numbers. That's real headcount optimisation, real process elimination, real time saved. It was enough to win Finance Leader of the Year, which was gratifying, but the real measure of success was simpler: we could produce one set of numbers that everyone trusted.
At another client, we went from four separate finance functions producing four separate sets of accounts to a single integrated team producing consolidated group reporting within 10 days of month end. Each acquisition integration got faster because we had a playbook and, just as importantly, because the team had been through it before and knew what to expect.
The common thread in both cases was the same. We started with people. We built trust before we built processes. We built processes before we changed systems. And we involved the acquired teams in designing the solution rather than imposing one.
Finance integration after acquisition is hard. But it's not complicated. The sequence is straightforward: listen, map, design, implement, review. The discipline is in resisting the urge to skip steps, especially the human ones.
If you're about to close a deal, or you closed one recently and the finance integration is stalling, the first question to ask isn't "which system should we use?" It's "have we actually talked to the people who do the work?"
Start there. The rest follows.
If you've recently closed a deal and the finance integration is stalling — or you're about to close and want to get ahead of it — the Post-Acquisition Finance Integration service covers the full first 100 days and beyond. The Finance Diagnostic is also useful immediately post-close to establish a clear baseline across both entities.
