Post-Acquisition Finance Integration: First 90 Days

In the first 90 days after acquisition, finance integration should expose fragile workflows fast, not bury them under a longer reporting cycle.

In the first 90 days after acquisition, finance integration should make workflow fragility visible fast. The point is not to rebuild everything at once. It is to identify which finance processes are weakening board visibility, slowing cash and EBITDA decisions, or depending on local memory that will not scale.

Many acquired companies look functional in week one. The ERP is live. The management pack exists. The controller can explain the month-end cadence. Then the operating partner starts asking sharper questions: how many manual handoffs sit between source data and sign-off, where do exceptions disappear, what would break if the controller took leave next month, and why does the board pack still need to be assembled manually at the end of every cycle?

In Short

• Post-acquisition finance integration should expose fragile workflow first, not just merge reporting calendars.
• The first 90 days are best used to map ownership, handoffs, exceptions, approvals, and evidence paths.
• The goal is comparability and control, not a cosmetic standardisation exercise.
• The first intervention should be narrow enough to prove value and governed enough to hold.
• A PE operating partner needs visibility into what is fragile, what is stable, and what can wait.

What should finance integration achieve in the first 90 days?

By day 90, the operating partner should know which finance workflows are fragile, which are stable enough to support, and which can be left alone for now. That is the practical threshold. If the team still cannot explain where the workflow leaves the ERP, who owns the manual steps, or which exceptions recur each cycle, the integration effort is still too abstract.

The first 90 days should create operating clarity. It should not just create a combined reporting timetable. A timetable without workflow visibility gives the sponsor a neater calendar and the same underlying risk.

Why does finance integration often stall after acquisition?

It stalls because the team standardises the outputs before understanding the path that produces them. The board pack format gets aligned. The KPI list gets cleaned up. Reporting deadlines are reset. Meanwhile, the manual work underneath remains untouched.

That is why newly acquired companies can look aligned on paper while still carrying different close routines, different exception practices, and different sign-off paths. The output is comparable only at the surface. Underneath, the finance work is still uneven.

In my experience, the sponsor usually feels this before it can name it. One portco closes "fine" but takes too much intervention. Another reports on time but rebuilds every pack manually. Another looks stable until the first real exception appears and nobody can show who owns the path to resolution. Those are not small defects. They are the beginning of portfolio inconsistency.

What should the operating partner map first?

Start with the workflow between source data and signed-off reporting. That path is where portfolio comparability either becomes possible or fails early.

The first map should cover:

• source data and extraction routines
• task owners and backup coverage
• exception queues and escalation paths
• approval gates and evidence records
• board-pack assembly steps

That is the same lens behind a PE portfolio finance diagnostic. The goal is not to document every finance activity in the company. It is to isolate the workflows that drive board visibility, close reliability, and decision speed.

Which finance processes matter most in the first 90 days?

Five areas usually matter first.

1. Close ownership and timing

The operating partner needs to know how the period-end close actually finishes, not how it is meant to finish. Who owns the close calendar, where does timing slip, and how many steps still depend on ad hoc follow-up?

If the close relies on local workarounds, every other reporting promise sits on weak footing. That is why this stage often links directly back to questions raised in Why Private Equity Portcos Stay Manual After ERP Go-Live. The pattern is the same: the ERP is live, but the control layer above it is still manual.

2. Management accounts and board-pack assembly

The board pack should not be the first place finance integration problems become visible. Yet that is often where the sponsor sees the weakness. Commentary is late. Version control is unclear. The same figures are being copied through multiple files before the final pack is ready.

Map the path from final ledger output to board-ready reporting. If the pack is still an assembly process, that is a workflow risk, not just a reporting nuisance.

3. Exception handling

Exceptions tell you whether control is real or informal. If a reconciliation break, late accrual, or reporting mismatch sits in email without a visible owner and deadline, the acquired company may be operating on trust rather than process.

The first 90 days should surface where exceptions go, who owns them, how they escalate, and what evidence remains after they are cleared.

4. Key-person risk

Some acquired finance teams are stable because one person is carrying the logic. That is not stability. It is concentration risk.

Ask a simple question: if the controller or finance manager were unavailable next month, could a capable replacement follow the workflow without rebuilding it from memory? If the answer is no, the integration effort has found one of its real priorities.

5. Portfolio comparability

The sponsor does not need every portco to run the exact same process on day 90. It does need a comparable way to judge where the fragility sits. That means assessing close speed, exception visibility, reporting assembly, approval discipline, and evidence quality through the same lens across companies.

Without that shared lens, the sponsor ends up managing stories instead of finance signals.

What should wait until after the first 90 days?

Anything that looks tidy but does not improve visibility or control should wait.

That includes broad documentation drives, cosmetic template redesigns, and tool evaluations that start before the operating team can describe the actual workflow break. If the finance team still cannot explain how the close or board pack gets from source data to sign-off, a new tool will only sit on top of the same ambiguity.

The first 90 days are for diagnosis, ordering, and selection. The build comes after the path is clear.

How should the first intervention be chosen?

Choose the first intervention based on three tests:

1. Does the workflow matter to board visibility, cash, margin, or control?
2. Is the process stable enough to support without hardening confusion?
3. Can the result be proven within one operating cycle?

That usually leads to one narrow pilot. A close exception queue. A recurring extraction routine. A governed board-pack input path. Something that can show the portfolio team whether the workflow becomes faster and clearer when the manual assembly is reduced.

The first move should not be the loudest problem. It should be the most governable problem that still matters.

What It Looks Like When You've Won

By day 90, the operating partner can point to the fragile workflows instead of describing finance risk as a vague concern. The portfolio CFO knows which routines are stable, which approvals are weak, and which reporting steps still depend on manual assembly. Leadership can choose the next intervention based on operating evidence, not on whoever is arguing hardest in the room.

That is the win in this article. Not a full finance redesign. Not a new reporting layer everywhere. A sponsor who can tell, with confidence, what needs work first and what can be left alone without hiding risk.

Frequently Asked Questions

What is post-acquisition finance integration?

Post-acquisition finance integration is the work of making finance processes visible, controlled, and decision-ready after a deal closes. In the first 90 days, that usually means mapping ownership, handoffs, exceptions, approvals, and reporting assembly before choosing what to change.

What should an operating partner focus on in the first 90 days?

Focus on the workflows that affect close reliability, board visibility, cash awareness, and control. The aim is to identify fragility quickly, not to standardise every finance activity at once.

Why do acquired companies still feel manual after the ERP is live?

Because the ERP records transactions but does not redesign the workflow around extraction, reconciliation, exception handling, approvals, and board-pack assembly. That manual control layer often survives the deal untouched.

What is the best first finance intervention after acquisition?

The best first intervention is the workflow that matters to decision quality, is stable enough to support safely, and can prove an outcome within one operating cycle.

What should always stay human in finance integration?

Material judgment, policy decisions, and final sign-off should stay with named people. Workflow support should reduce assembly work and improve visibility, not remove accountability.