By Dylan Harrocks , Founder of PMI Stack · Published 14 July 2026 · 10 min read
When you acquire a company, the finance function is where the deal either becomes real or quietly comes undone. Payroll has to run on the next cycle, cash has to be visible across two organisations, and at some point two sets of books have to close as one. Post-acquisition financial integration is the work of those first 90 days, and it decides whether the close happens on your terms or under deadline.
This piece is for finance leaders and operators at companies growing by acquisition. It maps what post-acquisition financial integration actually looks like across those first 90 days, phase by phase, from Day 1 access through to your first combined close. It stays inside the finance function on purpose: a broad first-100-days integration plan spans every workstream, while this one follows the money, where the deadlines are external and unforgiving.
The stakes are not abstract. KPMG's 2025 analysis of more than 3,000 public deals found that 57.2% of acquirers ultimately destroyed shareholder value , and the same study saw acquirers' returns fall in the two years after close. Integration is where that gap opens, and finance is where it is widest.
What is post-acquisition financial integration? Post-acquisition financial integration is the work of bringing a newly acquired company's finance function into your own: its bank accounts, its ledgers, its close process, its systems, and its people. The goal is one trustworthy set of numbers for the combined group, produced on a shared calendar, without breaking the two businesses that are still running underneath. It spans Day 1 continuity (payroll, cash, and payables that cannot pause), the standardisation of accounting policy and the chart of accounts, a deliberate decision on how the two finance systems will coexist, and a first consolidated close that proves the whole thing holds. The deadlines are external and unforgiving: payroll dates, lender reporting, and a first combined close all arrive whether or not the integration is ready. Done well, the group ends the first 90 days closing as one entity on a shared calendar with numbers the board and the finance team both trust.
Consolidated reporting is one workstream inside this, not the whole of it. Getting to one set of group numbers matters enormously, but it sits alongside treasury, controls, the operating model, and retention of the people who know where the numbers come from. This article covers the whole function; where the reporting workstream needs depth, it links out to it.
What must the finance function have ready on Day 1? On Day 1 the test is continuity, not integration: the acquired business has to keep paying people, collecting cash, and settling invoices without a gap. That means confirmed access to its bank accounts and financial systems, payroll running on schedule, accounts payable under control, and daily cash visibility from the first morning you own it.
Practitioner finance-integration checklists group the early work around reporting and cash management, alongside the payables and receivables that have to stay live from the moment you own the business. None of this is strategic. All of it is the kind of thing that, if it slips, undermines trust with staff and suppliers in the first week.
Day 1 is also when you lock down controls: secure system access, agree who has spending authority, and flag the seller's legacy vendor arrangements before they cause a payment you did not intend. Get continuity right first, because you cannot standardise a finance function that has stopped functioning.
In our experience the payment you did not intend almost always traces to a seller's legacy auto-pay that nobody flagged in week one, which is why we lock vendor authority first. Confirm any lender or covenant reporting the acquired entity owes as well, so the first post-close submission is not a deadline you discover late.
What should finance do in the first 30 days? The first 30 days are for stabilising and seeing clearly, above all seeing the cash. The priority is a consolidated cash view by legal entity, including trapped or restricted balances, overdrafts, and intercompany positions, so you know the true liquidity of the combined group rather than a sum of two dashboards. Practitioner playbooks put securing cash visibility and payment controls in this first 30-day window, before anything else.
Alongside cash, map the acquired company's reporting cycles and close calendars so no deadline is missed while you plan the longer integration. Inventory its systems: the ledger, the consolidation and reporting tools, how data moves between them, and who touches each one.
This is also the month to stand up interim consolidated reporting without waiting for any systems project. Structured exports and a rough mapping between the two charts of accounts will give you a combined view weeks before an ERP consolidation is anywhere near done. A temporary bridge that lets you report as one group is worth more in month one than a perfect architecture you will not have for a year.
Days 31 to 60: harmonise the chart of accounts and decide on ERP The middle month is where standardisation starts, and it turns on two decisions: how the charts of accounts map together, and how the two finance systems will coexist. Harmonising the chart of accounts, mapping each subsidiary's structure to the group's , is the foundation everything downstream depends on, because a consolidated number is only as trustworthy as the account mapping beneath it.
In our experience it is usually a few weeks of focused work, not a few days. Rushing it is how bad mappings get baked in.
Do the policy alignment in the same window. Revenue recognition, capitalisation thresholds, and the definition of the metrics you report all need one agreed treatment across both companies, or your consolidated figures will quietly compare unlike with unlike. The same discipline that governs consolidating a multi-entity group's accounts applies here: define each policy once, and every entity reports it the same way.
The ERP decision belongs in this window too. Practitioner playbooks slot the decision on how the finance systems will consolidate into the Days 31 to 60 stretch: full migration onto one system, federation where each entity keeps its ledger and you consolidate above it, or a hybrid.
The right answer depends on how many more acquisitions are coming. A company planning to buy again should not migrate every target onto one instance, because the migration never ends. What matters is deciding deliberately and early, not drifting into whichever system had the loudest advocate.
Days 61 to 90: your first consolidated close The last month is where integration stops being theoretical and gets tested in a real close. The first consolidated close is the milestone that proves the account mapping, the intercompany eliminations, and the policy alignment actually hold, and it is almost always messy the first time.
Intercompany entries will not tie, and a rev-rec treatment will need interpreting. The acquired company's supporting schedules will not match your parent format.
That is normal, and a messy first close is still a good first close if the problems are visible, owned, and smaller by the next cycle. The failure mode is not an imperfect close; it is a close where nobody can see what broke or who owns fixing it.
Every first close we have sat through has broken on intercompany first, so we plan for that rather than acting surprised by it.
By the end of the 90 days, the goal is a single source of financial truth across the combined group. The CFOmeet playbook holds the last thirty days for locking the target chart-of-accounts path and migration timeline , which is what makes that single view possible.
Stand up the recurring KPI pack the group will run on: revenue, gross margin, cash, and AR and AP days. Add the operational metrics that matter to your sector.
Ninety days does not finish the integration, but it should leave you closing as one group and reporting numbers everyone trusts.
Why does post-acquisition financial integration fail? Financial integration fails when the reporting cannot keep pace with the acquisitions, and the group loses sight of its own numbers. Even experienced acquirers struggle here: Bain finds that more than two thirds of acquisitions fail to create meaningful shareholder value , and the finance function is one of the places that value leaks away when integration slips.
The most common failure is treating the first close as a deadline to survive rather than a system to build. Teams assemble the consolidated numbers by hand under time pressure, the process never gets designed, and the next acquisition lands on top of an integration that was never finished.
The work compounds: consolidation complexity is roughly quadratic, so a group of 10 entities carries about 45 potential intercompany relationships in consolidated reporting , and 20 entities around 190. Manual processes that coped at two entities quietly break at six.
The second failure is losing the people who hold the knowledge. The person who knows why an account is treated a certain way, or where a reconciliation is buried, is often a flight risk in the first months.
There is an upside worth holding onto, though: Bain also reports that 75% of frequent acquirers meet or exceed their synergy targets , because they treat integration as a repeatable capability rather than a one-off scramble. The difference is a defined process, run the same way every deal.
The first-90-days financial integration checklist The 90-day finance integration arc breaks into four phases, each with one clear test of done. It is deliberately about the whole function, not only the reporting workstream, which has its own 90-day reporting milestones if you want to go deeper on that piece.
Phase Finance priority What “done” looks like Day 1 Continuity and control Bank access confirmed, payroll running, AP and cash under control, access secured Days 1 to 30 Stabilise and see the cash Cash visible by entity, close calendars mapped, systems inventoried, interim consolidated reporting standing Days 31 to 60 Standardise and decide Chart of accounts harmonised, accounting policy aligned, ERP path chosen (migrate, federate, or hybrid) Days 61 to 90 Prove it in a close First consolidated close completed, intercompany reconciled, KPI pack live, issues owned
The 90-day window is the finance chapter of a broader first-100-days integration plan . Finance moves faster than most workstreams because the deadlines are external: payroll dates, a first close, lender reporting. That external pressure is useful, if you let it force a real process rather than a heroic one.
How PMI Stack helps acquisitive companies integrate finance The hardest part of the first 90 days is not any single task; it is producing one trustworthy group view while both businesses keep running. That is the problem PMI Stack's consolidated reporting is built to solve for companies growing by acquisition.
We connect each acquired company's accounting systems into one warehouse and normalise them to a group chart of accounts and reporting currency, working with a fractional-CFO partner on the mappings. On top of that we stand up a single dashboard with an embedded assistant your team can ask directly.
The dashboard tracks the integration itself: Day 1, Day 30, Day 100, and Day 365 gates on every acquisition. Alongside those gates it shows the group P&L, cash position, and each deal's actuals against the thesis you underwrote. It is delivered forward-deployed, built on your real data rather than a template you have to fill in.
The number on the screen is the thing we protect. Figures trace to your consolidated source rather than being generated, so the group view you brief your board on is the same one your finance team closes. One operator's account of consolidating the finances of an acquisitive group is worth reading on that point: Pavleta Pavlova on consolidating an acquisitive group's finances .
If you have just closed a deal and the first combined close is on the horizon, that is the right moment to build your post-acquisition financial integration foundation, not the quarter after a messy one.
