Post-Acquisition Synergy Tracking: Where Did the Promised Savings Go?

The acquisition is complete.

The announcement has gone out. The leadership team has congratulated everyone involved. The deal presentation has a very attractive slide showing $8 million in annual synergies.

Excellent.

Now I’d like to see the $8 million.

Not the slide.

The money.

And before anyone starts looking uncomfortable, I’m not suggesting the acquisition was a mistake. The business may have bought a terrific company for perfectly sound strategic reasons.

But a successful transaction and a successful integration are two different accomplishments.

One gets announced.

The other has to be delivered.

That’s where I think FP&A has a particularly important job.

The Deal Model Isn’t an Operating Forecast

When a company acquires another business, the deal model typically includes expected financial benefits.

Some are straightforward in theory: eliminating duplicated costs, consolidating facilities, renegotiating vendor contracts, or reducing overlapping software expenses.

Others are more ambitious: cross-selling products, expanding distribution, improving pricing, or using the combined company’s capabilities to win new customers.

All of these may be legitimate.

But there’s a difference between identifying a potential synergy and actually realizing it.

I would want the finance team to preserve the original deal assumptions while building a separate, operationally grounded forecast of what the combined business can deliver.

Reviewing the financial model helps establish what the numbers can support.

The original deal model tells us what management expected when it approved the acquisition.

The current forecast tells us what management now expects to happen.

And actual results tell us what has happened so far.

Those three views should be connected.

They should not be interchangeable.

Otherwise, an integration team can spend months revising assumptions until the forecast looks perfectly reasonable, while nobody remembers what the acquisition was originally supposed to achieve.

That’s a very tidy way to lose the plot.

Let’s Follow an $8 Million Synergy Commitment

Consider a hypothetical U.S. company that acquires a complementary business.

The acquisition case includes $8 million in expected annual recurring cost synergies once integration is complete.

The original plan looks like this:

Synergy initiative	Expected annual run-rate savings
Consolidate overlapping functions	$3.0M
Renegotiate supplier contracts	$2.0M
Consolidate technology systems	$1.5M
Optimize facilities	$1.5M
Total expected annual synergies	$8.0M

Every initiative has a business rationale.

The estimates may be reasonable.

But I wouldn’t treat this table as evidence that the company has achieved anything.

It’s a commitment.

The interesting work starts when we ask what actually changed.

An Initiative Can Be Complete Without Delivering Its Savings

Suppose the integration team reports that the supplier renegotiation is complete.

The contract has been signed.

The new pricing is effective.

The project status is green.

Wonderful.

But the savings calculation assumes the company will purchase the same quantities as before, at the same product mix.

Meanwhile, operations has changed suppliers for part of the business, and volume has fallen.

The company may still be saving money.

But it might not be saving the $2 million promised.

A signed contract is an operational milestone.

A lower cost, measured against a defensible baseline and adjusted for relevant business changes, is a financial result.

I want both.

But I don’t want to confuse them.

This is where the cheerful green status indicators can become a little too enthusiastic.

I Would Build a Synergy Bridge, Not Just a Tracker

A traditional tracker might show initiative name, owner, target, status, and completion date.

Useful information.

Not enough.

I would also want to understand how the original synergy commitment reconciles to the current expected financial benefit.

Let’s imagine the integration team has completed its latest review.

Synergy initiative	Original annual target	Current validated annual run rate	Difference
Overlapping functions	$3.0M	$2.6M	-$0.4M
Supplier contracts	$2.0M	$1.7M	-$0.3M
Technology systems	$1.5M	$1.1M	-$0.4M
Facilities	$1.5M	$1.4M	-$0.1M
Total	$8.0M	$6.8M	-$1.2M

All figures are hypothetical. Annual run rate is not the same as cash savings or cumulative savings recognized to date.

The company now expects $6.8 million in annual recurring savings from the identified initiatives.

That is $1.2 million below the original target.

I wouldn’t automatically call that a failed integration.

I’d ask why.

Perhaps some savings are delayed.

Perhaps some initiatives were deliberately redesigned to protect customer service.

Perhaps the original baseline was wrong.

Or perhaps the organization has discovered that removing a cost is harder than identifying it in a presentation.

Shocking, I know.

But these explanations have different financial implications.

And they deserve different management responses.

The Five Questions I’d Ask About Every Synergy

1. What was the original baseline?

Suppose the acquired company spent $5 million annually on a category of services.

The integration plan promises to reduce that spending to $4 million.

That’s a potential $1 million annual saving.

But what happens if the original $5 million included temporary implementation costs that would have disappeared anyway?

We cannot claim the natural expiration of a temporary expense as a merger synergy.

At least, not if we want the number to mean anything.

I would establish a baseline that identifies the underlying costs, the relevant business activity, and the assumptions used to calculate the savings.

2. What action created the benefit?

A synergy should have an identifiable business action.

A facility was closed.

A vendor contract changed.

A system was retired.

A duplicated activity was eliminated.

If the explanation is simply that the combined company’s costs are lower than expected, I need more information.

Costs can decline for many reasons.

Some have nothing to do with the acquisition.

3. When does the benefit actually begin?

This is one of the easiest places for an otherwise reasonable synergy forecast to go wrong.

A $1.2 million annual run-rate saving doesn’t necessarily produce $1.2 million of savings in the current fiscal year.

If the benefit begins October 1, the current-year saving may be approximately $300,000, assuming a calendar fiscal year and an even monthly benefit.

The remaining annualized amount belongs to a future period.

The timing matters to the earnings forecast.

It matters to cash.

And it matters to the board’s understanding of integration progress.

4. What did we spend to achieve it?

Suppose a technology consolidation produces $1.1 million in annual recurring savings.

Excellent.

But the company also spends $2.4 million on migration, consultants, system implementation, and employee training.

That doesn’t automatically make the project unattractive.

Recurring savings can justify significant upfront investment.

But we need to evaluate the timing and cash consequences.

A synergy number without the cost to achieve it is only half the financial story.

5. Where does the benefit appear in reported performance?

This is the question I’d insist on answering.

If a supplier contract produces $500,000 in validated savings, which financial statement line reflects the benefit?

Which business unit owns it?

Has the saving already been incorporated into the operating forecast?

Could another initiative be claiming the same amount?

And can the controller or finance team reconcile the benefit to the underlying transactions?

I don’t need every saving to appear as a perfectly isolated line item in the general ledger.

That’s often unrealistic.

But I do need a defensible bridge from operational evidence to reported financial performance.

The Difference Between Run Rate and Realized Savings

Let’s take the $6.8 million validated annual run-rate figure.

It’s tempting to report that the company has delivered $6.8 million in synergies.

But that wording could be misleading.

If the initiatives reached their current run rates at different times, the actual benefits recognized during the year could be substantially lower.

For example:

Measure	Illustrative amount
Original annual synergy commitment	$8.0M
Current validated annual run rate	$6.8M
Actual current-year gross savings recognized	$3.2M
Current-year integration costs incurred	$2.1M
Current-year savings less integration costs	$1.1M

These are four different financial measures, plus the original commitment.

They answer different questions.

The $8 million is what the deal case promised.

The $6.8 million is the currently validated annualized benefit.

The $3.2 million is the savings recognized during the current year.

The $2.1 million is the integration expenditure incurred during that year.

And the $1.1 million is the simple difference between current-year gross savings and integration costs.

That last figure is not automatically incremental EBITDA, net income, free cash flow, or acquisition return on investment. Those require appropriate accounting treatment, taxes, capital expenditures, working capital effects, and other relevant items.

I would report these measures separately.

Because combining them into one impressive-looking number doesn’t improve performance.

It just makes the next meeting more interesting than anyone intended.

I’d Be Especially Careful With Revenue Synergies

Cost synergies are often easier to identify than revenue synergies.

If a company eliminates a duplicated software subscription, the cost reduction may be fairly observable.

Revenue synergies are more complicated.

Suppose the acquisition thesis assumes the combined sales organization can cross-sell an additional $5 million of products annually.

How much of that revenue would have occurred without the acquisition?

Did existing customers simply shift purchases between the two businesses?

Was the growth caused by pricing, market demand, or a separate sales initiative?

What incremental gross profit did the additional revenue produce?

And what selling, delivery, or customer-support costs were required?

I would not measure revenue synergy simply by adding up sales attributed to a new cross-selling campaign.

I’d establish a reasonable counterfactual: what we believe would have happened without the transaction.

That estimate will never be perfect.

But a transparent, consistently applied methodology is far more useful than an attribution process that gives every successful sale three different parents.

As any mom knows, everyone wants credit when something goes well.

The enthusiasm can be somewhat less impressive when it’s time to clean up afterward.

Don’t Let Synergies Get Counted Twice

Here’s a problem that can make a synergy tracker look more successful than the business actually is.

The procurement team renegotiates a supplier contract and claims $600,000 in annual savings.

The operations team then reports a $600,000 improvement in its cost-reduction initiative.

Both teams may have contributed to the outcome.

But if they are reporting the same underlying cost reduction, the company has not created $1.2 million in savings.

It has created $600,000.

I would require every synergy initiative to have a unique benefit definition, accountable owner, financial statement mapping, and reconciliation process.

Where multiple teams contribute to the same outcome, recognize the shared contribution without duplicating the financial value.

Recognition is nice.

Arithmetic is still arithmetic.

The Board Doesn’t Need Another Green Dashboard

For an acquisition with material synergy commitments, I would want the board to receive a concise management reporting explanation of progress.

Not a presentation containing 47 green circles.

Something closer to this:

Board-level question	What FP&A should provide
What did the acquisition promise?	Original approved synergy and value-creation case
What has been delivered?	Validated realized savings and current run rate
What’s changed?	Bridge from original commitments to current expectations
What did it cost?	Integration spending and updated cost-to-achieve forecast
What’s at risk?	Delayed initiatives, unsupported assumptions, operational dependencies
What happens next?	Specific management decisions, owners, and revised milestones

The purpose isn’t to embarrass an integration team when the numbers change.

It’s to give leadership an honest view of where the deal stands.

Sometimes the right decision is to accelerate an initiative.

Sometimes it’s to invest more.

Sometimes it’s to abandon an expected saving because pursuing it would damage customer relationships or operating performance.

And sometimes the finance team needs to say that the original business case was too optimistic.

That’s not a comfortable conversation.

But it is considerably more useful than spending another quarter defending an assumption that no longer holds.

Put the Synergies Into the Actual FP&A Process

I wouldn’t want a synergy tracker living permanently in its own spreadsheet, disconnected from the rest of financial planning.

The original acquisition thesis should connect to the combined company’s operating forecast.

Each material initiative should have a defined owner, financial baseline, timing assumptions, and expected financial statement impact.

Actual performance should be reviewed against those assumptions.

The forecast should be updated when evidence changes.

And the board should be able to distinguish between changes in the acquired business’s underlying performance and benefits created by integration.

This is consistent with McKinsey’s guidance on involving CFOs and FP&A leaders directly in post-merger value capture and incorporating synergy targets into normal financial processes.

For me, that’s the point where synergy tracking becomes genuinely useful.

It stops being a separate integration reporting exercise.

It becomes part of how the company manages financial performance.

What I’d Want to Know at the Next Integration Meeting

I would arrive with a relatively short set of questions.

Which synergies have been financially validated?

Which are operationally complete but not yet reflected in results?

Which assumptions have changed?

What is the remaining cost to achieve the benefits?

Where are we double-counting?

Which delays affect this year’s earnings or cash forecast?

And what management decisions would improve the outcome?

Those questions are more valuable than asking whether the integration is 83% complete.

Eighty-three percent of what, exactly?

Systems migrated?

Contracts renegotiated?

People reassigned?

Financial value delivered?

The answer matters.

A business can complete most of its integration tasks while delivering substantially less value than expected.

It can also decide to preserve a strategically important capability instead of capturing every planned cost saving.

The objective is not to win the synergy spreadsheet.

It’s to make the acquisition successful.

The Deal Is Done. The Financial Judgment Isn’t.

I like the strategic possibilities that acquisitions create.

A company can gain capabilities, customers, markets, technology, and scale that would have taken years to develop independently.

That’s exciting.

But the opportunity doesn’t become financial value simply because it was included in the acquisition model.

Somebody has to connect the original thesis to operational actions, financial forecasts, actual results, and the decisions management makes along the way.

That’s the role I want FP&A to play.

Not the department that updates the synergy slide.

The function that helps leadership understand whether the acquisition is delivering what it was supposed to deliver—and what to do when it isn’t.

When the Synergy Report and the Financial Results Don’t Agree

If your company has completed an acquisition and the promised benefits aren’t clearly showing up in the forecast, management reporting, or operating results, I think that’s worth examining before another quarter passes.

My FP&A Services for PE-Backed Companies page explains how I support finance planning and performance visibility in private-equity-backed businesses.

The next step doesn’t have to be another elaborate integration dashboard.

I’d start by finding out which numbers we can actually defend.

Then we can have a much more useful conversation.