Finance Integration After an Acquisition: The First 100 Days

The hard part of an acquisition isn't closing the deal. It's the morning after, when you wake up owning two of everything: two charts of accounts, two ERPs, two close processes, two ways of recognizing revenue, two finance teams with different habits and possibly different definitions of the same metric. The synergies that justified the deal live on the other side of integration, and integration is where a surprising number of acquisitions quietly underperform their thesis.

The first 100 days set the trajectory. Here's how to use them.

Stabilize before you integrate

The first instinct is to start merging immediately—one chart of accounts, one system, one process, fast. Resist it. The first priority is making sure the acquired entity keeps running and keeps producing reliable numbers while you figure out the integration. A botched rush to consolidate that scrambles the acquired company's reporting is far worse than a deliberate pace that keeps both sides stable.

So the first phase is understanding and stabilizing. Get the acquired finance function producing numbers you trust on its existing systems. Understand their close, their estimates, their reconciliations—the same ground-truth assessment you'd do walking into any new function, now applied to a business you just bought and may not fully understand yet. You can't integrate what you don't understand.

The chart of accounts is the first real battle

The single most consequential integration decision is the chart of accounts, because everything downstream depends on it. The two companies almost certainly define accounts, cost centers, and dimensions differently, and until you reconcile them you can't produce meaningful consolidated reporting. This is tedious, unglamorous mapping work, and it's the foundation of everything.

The decision isn't just "which chart wins." It's designing the combined structure that serves the merged business going forward, then mapping both legacy structures into it. Rushing this—or letting the two charts coexist indefinitely with a manual bridge—creates a consolidation mess that haunts every close for years. It's worth doing carefully and early.

Consolidate the reporting before you consolidate the systems

A useful sequencing principle: you can produce consolidated reporting long before you merge the underlying systems, and you should. Merging ERPs is a major project that takes many months; you can't wait that long to report on the combined business. The interim answer is a consolidation layer that takes data from both systems, maps it to the unified chart, and produces combined reporting—while each entity continues running on its own system underneath.

This decouples the urgent need (consolidated numbers for the board and lenders) from the long project (system integration), letting you deliver the first without rushing the second. It's the same decoupling principle that applies to ERP modernization generally: separate the system of record from the system of insight, and you buy yourself room.

Don't lose the people who hold the knowledge

The acquired finance team holds knowledge that exists nowhere else—why an estimate is made the way it is, which customer relationships are fragile, where the acquired company's own bodies are buried. Integration anxiety drives good people to leave exactly when you need them most, taking irreplaceable context with them. Identify the people who hold critical knowledge early and give them reasons to stay through the integration, even if the long-term org design eventually has fewer roles. Losing the institutional memory mid-integration is a self-inflicted wound that shows up as errors and surprises for years.

Capture the synergies you underwrote—and measure them

The deal was justified by specific synergies. The integration is where they're captured or lost, and the discipline most often missing is measuring whether they actually materialize. Just as a technology business case deserves an after-action review, the deal's synergy assumptions deserve tracking against reality. Which cost synergies actually landed? Which revenue synergies were optimistic? This isn't just accountability—it's how the organization gets better at underwriting the next deal.

The 100-day arc

A sensible arc: spend the first stretch understanding and stabilizing both finance functions, then design the unified chart of accounts and stand up a consolidation layer for combined reporting, then begin the longer system integration on a deliberate timeline while tracking synergy capture throughout. Stabilize, unify the reporting foundation, integrate the systems methodically, measure the results.

The deal made the headlines. The integration makes the returns. Spend the first 100 days building the foundation—trusted numbers, a unified chart, consolidated reporting, retained knowledge—and the synergies you paid for have a chance to actually show up. Rush it, and you'll spend years cleaning up an integration that broke things it didn't need to.