Integration progress needs a financial reference point
Post-merger integration brings together two plans with different measures of success. The acquisition case estimates the earnings, cash flow and strategic advantages expected from the transaction. The implementation plan assigns activities, owners and deadlines. The connection between them requires continued attention after completion of the deal, as assumptions about customers, systems and operating capacity are tested.
A supplier agreement, for example, may be signed on schedule while the purchasing savings remain unavailable. Technical approval may still be outstanding, existing inventory may need to be consumed, or local teams may continue ordering under previous arrangements. Reporting the agreement as complete is accurate. Treating that completion as evidence of financial delivery would be premature.
My view is that the handoff between functions deserves explicit treatment in the synergy forecast. A handoff is the point at which one function’s output becomes usable by another: procurement passes an agreement to the teams placing orders; technology provides a system that commercial teams can operate; sales transfers a customer commitment that operations can fulfil. Each transfer has conditions that determine when the expected benefit can begin.
This distinction matters most where a small unresolved decision affects a substantial earnings commitment. The remaining task may occupy one line in the integration plan, yet determine several months of benefit delivery. The analysis below develops a practical way to make that exposure visible, using one illustrative procurement case throughout.
The evidence supports closer attention to execution
Bain reports that 83% of surveyed M&A executives with experience of failed acquisitions identified integration as a primary problem. This describes the responses of that group; it is not an estimate that 83% of all acquisitions fail. Bain’s recommendations include early integration planning and focused attention on consequential decisions across functions. [1]
KPMG’s analysis of more than 3,000 public-company acquisitions above US$100 million, covering 2012–2022, found that 57.2% of acquirers destroyed shareholder value under its market-relative return measure. The result captures the combined effects of deal pricing, strategy, execution and market conditions. It cannot isolate the contribution of integration. [2]
These findings establish the importance of delivery without identifying a single explanation for disappointing outcomes. McKinsey’s work on synergies provides a complementary operating perspective: detailed benefit plans, clear ownership and an integration office with the capacity to support delivery. [3] The argument developed here builds on that foundation. It examines how dependencies between functions affect the timing of earnings, and how that timing should influence management decisions.
A three-month delay reduces first-year savings by one-third
Consider two industrial businesses that combine at the beginning of January. Both buy comparable maintenance components, but they use different specifications and purchasing arrangements. The combined company plans to consolidate suitable purchases under a lower-price supplier agreement. Before sites can use it, engineering must approve the common component specification and site purchasing teams must be ready to order against the new agreement.
This is the single purchasing-cost initiative followed through the sections, diagrams and dashboard below. Procurement negotiates the agreement; engineering approves the components; site purchasing teams implement the buying process. Their responsibilities concern making the saving possible—not three separate deliveries to customers.
The combined company expects to reduce purchasing costs by US$6 million over a full twelve months once a new supplier arrangement is operating. This is the annual run rate: the saving achievable over a year at the intended operating level.
The plan allows January to March for implementation. New prices are expected to apply to eligible purchases from April, producing US$500,000 of savings each month. Nine months of savings would therefore contribute US$4.5 million in the first calendar year. The US$6 million run rate and the US$4.5 million first-year contribution are both valid, but they answer different questions.
Now assume technical approval takes three months longer than planned. The arrangement starts in July. The company still expects US$500,000 of monthly savings once implementation is complete, but only six months fall within the first year. First-year savings decline to US$3 million, leaving a US$1.5 million shortfall against the original plan.
| Measure | Original plan | Delayed case |
|---|---|---|
| Savings begin | April | July |
| Monthly savings after implementation | US$0.5m | US$0.5m |
| Months delivering savings in year one | 9 | 6 |
| First-year savings | US$4.5m | US$3.0m |
| Annual run rate once operating | US$6.0m | US$6.0m |
Starting in July instead of April reduces first-year savings by US$1.5m
By December, both cases report the same annual run rate. A dashboard focused on that measure could suggest the programme had caught up. The first-year earnings record would show a different result: one-third of the planned savings had not been earned. Reaching the intended monthly saving later does not, by itself, recover the savings missed on earlier purchases.
The example assumes constant eligible purchasing volumes, immediate application of the new prices after approval, and no retrospective supplier rebates. Savings are net of recurring delivery costs, before tax and one-off integration expenditure. There is no gradual ramp-up. These simplifying assumptions allow the effect of timing to be examined separately; a transaction forecast would need to reflect actual purchase volumes, contract terms and implementation costs.
The US$1.5 million is a first-year shortfall, not an estimate of the acquisition’s total loss of value. A valuation would also consider later benefits, discounting and the costs of alternative actions. The immediate management implication is narrower and more useful: the start date is a material financial assumption and should be governed accordingly.
Identify what must happen before the purchasing saving can begin
Continuing the same maintenance-component example, the agreement cannot be used merely because procurement has negotiated a lower price. Engineering must confirm that the proposed components meet operating requirements. Site purchasing teams must prepare the supplier records, ordering instructions and any stock transition. Some preparation can proceed in parallel, but placing orders under the new arrangement requires all three conditions to be satisfied. Finance then verifies whether those purchases produce the expected saving.
Suppose technical approval is the issue holding up the July start. Completing it in May will only bring savings forward if supplier capacity and the ordering process are also ready. If either remains unavailable until July, the earlier approval will create schedule flexibility but no immediate earnings improvement. That distinction prevents management from attributing a financial benefit to an accelerated activity that does not change the delivery date.
The assessment should therefore begin with the earliest date at which all necessary conditions can be met. This is an application of critical-path reasoning to benefit delivery. It requires the functions involved to agree which dependency determines the forecast, rather than presenting separate completion dates without reconciling them.
For the procurement initiative, a short acceptance record would identify the approved specification, the supplier’s effective date, the sites authorised to order and the evidence finance needs to recognise savings. The receiving function confirms that it can use the output. A document being issued or a task being closed does not automatically satisfy those conditions.
Readiness should also be assessed at the level at which implementation can occur. If some sites can adopt the arrangement earlier, their volumes can support a separate start date. The saving must then be recalculated for those volumes. Applying the full US$500,000 monthly saving to a partial rollout would overstate the benefit and weaken the case for sequencing.
How a negotiated component discount becomes a verified saving
Same example: consolidate purchases of approved maintenance components under a lower-price agreement.
Required evidence: signed terms covering the eligible items.
Case status: agreed.
Required evidence: technical sign-off.
Case status: outstanding; delaying the start.
Required evidence: sites ready to place compliant orders.
Case status: prepared.
Prioritise decisions by their effect on delivery
An overdue action list provides limited guidance when several initiatives compete for the same specialists. The relevant comparison is the effect that resolving each issue would have on the benefit forecast. A decision affecting a large opportunity may deserve less immediate attention if another dependency prevents that opportunity from starting.
In the example, moving the actual purchasing start from July to June would restore one month of savings, or US$500,000, to the first year. This is the gross financial benefit available from that acceleration under the stated assumptions. Any additional testing, staffing or supplier cost would reduce it. If the delivery date remains July, the first-year saving from the intervention is zero.
The decision should be assessed against the change it can make to this purchasing start date. The proposal should identify the activity to be accelerated, the evidence that it determines the start date, the achievable revised date and the associated cost. Where the schedule remains uncertain, management can review clearly described start-date scenarios rather than a single apparently precise estimate.
There are limits to financial prioritisation. Technical standards, safety requirements and customer commitments remain constraints. A large monthly saving does not justify bypassing an approval or accepting an inadequately tested product. The appropriate response may be to increase testing capacity, reduce the initial scope, or accept a later start and revise the forecast.
Dependencies shared by several initiatives require particular care. Resolving one issue may enable several benefits, but the same benefit cannot be credited repeatedly to different interventions. A consolidated forecast should record the change once, with the underlying decisions attached. This is especially important when functional teams report their own contributions to a common synergy target.
Would faster engineering approval bring the purchasing saving forward?
Separate responsibility for the result from responsibility for the input
Benefit ownership is necessary, but it is incomplete when delivery depends on resources outside the owner’s control. Procurement may be accountable for the saving while the engineering team determines when the specification can be approved. Holding procurement to the target without a corresponding commitment from technical leadership leaves an unresolved management dependency.
A workable arrangement gives one executive responsibility for the overall result and assigns explicit delivery commitments to the contributing functions. It also identifies who can resolve a conflict over capacity or priorities. The integration office maintains the connection between these commitments and the financial forecast, and escalates decisions that exceed the authority of individual workstream leads.
Acceptance criteria help make this accountability specific. Technical approval should state which products and sites are covered. Operations should confirm when orders can use the new arrangement. Finance should define the baseline price and the treatment of changes in volume or product mix. These details determine whether reported savings are attributable to the integration.
The baseline deserves attention before delivery begins. A decline in total purchasing expenditure could reflect lower demand rather than better prices. Conversely, expenditure could rise as volumes increase even while negotiated unit savings are being achieved. Reporting should distinguish the unit-price effect from changes in activity, so that management can assess the initiative on the intended basis.
When an assumption changes, the forecast should change with it. Preserving the original target in operational reporting after the supporting timetable has become unachievable reduces the time available to respond. The original investment case should remain visible for accountability, alongside the current forecast and an explanation of the variance.
Evidence required at each stage of benefit delivery
Sequence integration around operating capacity
The same technical specialists needed for supplier approval may also support customer work, routine maintenance and other integration initiatives. A schedule that assumes their full availability for each programme is infeasible even when every individual task estimate is reasonable. Capacity needs to be reconciled across the combined business.
KPMG’s 2026 study identifies leadership and cultural differences, together with disruption to business momentum, among significant post-merger challenges for corporate respondents. [4] In practical terms, integration planning must account for the work required to sustain existing revenue and service standards while the operating model changes.
I favour sequencing around the operating changes required to deliver the deal’s principal benefits. In a logistics combination, for example, a joint service offer may depend on reliable pricing, capacity confirmation and clear responsibility for the shipment handoff. Full consolidation of back-office systems may have a longer timetable. The initial commercial scope should match what the combined operation can reliably deliver.
Selective sequencing has costs. Separate systems can create duplicate work, reconciliation effort and additional controls. These costs belong in the comparison, with a defined period for maintaining the arrangement. The argument for an earlier, narrower rollout is strongest when the benefit can be evidenced and the operational burden remains manageable.
There will also be cases where waiting is the better decision. A broader implementation may reduce repeated migration costs or avoid service disruption. The procurement example does not establish that speed should always take precedence. It shows the financial consequence of delay so that management can evaluate that consequence against the reasons for accepting it.
Reconcile the operating plan with the financial forecast
An integration review should make the relationship between delivery conditions and expected earnings clear enough to support a decision. For the purchasing initiative, the essential record is compact:
| Review item | Procurement example |
|---|---|
| Expected operating benefit | US$500,000 savings per month after implementation |
| Baseline and current start | April in the original plan; July in the current forecast |
| First-year variance | US$1.5 million below the US$4.5 million plan |
| Dependency determining the date | Technical approval, subject to confirmation that ordering and supply are ready |
| Decision required | Whether a feasible earlier approval can change the actual start date at an acceptable cost |
| Evidence of delivery | Eligible purchases using the new prices, reconciled against the agreed baseline |
This record keeps the original commitment, current expectation and management response together. It also distinguishes progress that reduces implementation risk from progress that changes earnings. Both are valuable, but they should not be reported as the same achievement.
The subsequent review should examine whether the decision produced the forecast improvement. If approval was accelerated but savings did not begin, the team should establish whether a dependency was missed, implementation failed or the commercial assumption was wrong. The finding should inform both the remaining integration and future diligence.
For me, the central discipline is to maintain a traceable connection from the acquisition case to the operating decision and then to the financial result. Handoffs are a useful place to test that connection because they expose the assumptions shared between functions. Making those assumptions explicit improves the quality of the forecast and gives management a clearer basis for deciding where to intervene.
Recommended management view
PMI benefit delivery dashboard
This mockup applies the article’s procurement example. All amounts are US dollars. It shows the information required to decide whether the July implementation date can be improved, while preserving the original commitment for comparison. Figures are illustrative, not company results.
Delivery conditions
- AcceptedSupplier termsCommercial terms agreed; effective date follows technical approval.
- BlockingEngineering approvalApproval outstanding; completion currently supports a July start.
- AcceptedSite purchasing readinessSystems and eligible sites prepared; reconfirm if launch date changes.
Two conditions are accepted, but savings cannot begin until all three are met. “Two of three complete” does not mean two-thirds of the benefit is available.
Decision required
By 8 May: determine whether additional technical review capacity can enable a 1 June start without changing required standards.
- Accountable benefit owner
- Procurement director
- Dependency owner
- Engineering director
- Decision authority
- Integration steering committee
- Potential first-year improvement
- $0.5m before additional costs, only if the actual start moves from July to June
- Forecast treatment
- Keep the $3.0m forecast until the revised date and all delivery conditions are supported. Acceleration costs are not yet assessed.
Benefit register: one line of accountability
| Initiative | Benefit owner | Baseline → forecast start | First-year plan → forecast | Status and next evidence |
|---|---|---|---|---|
| P-01 · Common purchasing terms | Procurement director | 1 Apr → 1 Jul | $4.5m → $3.0m | At risk: technical sign-off and a confirmed effective date required |
Verification and follow-through
| Control | Definition or evidence | Owner / review |
|---|---|---|
| Realised purchasing savings | For comparable eligible items: (agreed baseline unit price − actual unit price) × actual quantity. Adjust for specification, currency and other non-comparable changes; reconcile to the agreed recurring-cost scope. | Finance · monthly |
| Use of the new purchasing agreement | Share of eligible purchasing activity actually using the new terms. Calculate both numerator and denominator at the same baseline prices; see the worked example below. This identifies missed implementation, not the percentage cost saving. | Procurement · monthly after launch |
| Cost to implement | Approved budget, incurred cost and latest forecast, shown separately from recurring savings. No cost assumption supplied in this mockup. | Finance / benefit owner · monthly |
| Operating safeguards | Track supplier service and quality against agreed acceptance limits. Limits must be set before rollout; none are invented here. | Site purchasing / engineering · through rollout |
| Cash effect | Assess payment timing, inventory and working capital separately. Verified operating savings are not automatically cash released. | Finance · monthly |
What the agreement-use metric tells management
Signing an agreement does not ensure that sites use it. This metric checks whether purchases that should benefit from the new terms are actually being placed under them. “Eligible” means the approved components and sites covered by the agreement; unrelated purchases are excluded.
Illustrative diagnostic after launch: a site buys eligible components worth US$100,000 at baseline prices during a month. Purchases worth US$80,000 on that same basis use the new agreement; US$20,000 continue under the old terms. Agreement use is US$80,000 ÷ US$100,000 × 100 = 80%.
The actionable finding is that 20% of eligible purchasing activity has not moved across. Procurement should identify which sites or items are affected, establish whether the cause is ordering setup, supplier availability or an approved exception, and assign corrective action. Finance calculates the actual dollar savings separately from unit-price differences and quantities.
An 80% use rate does not mean an 80% cost reduction, and it need not mean 80% of the forecast saving: discounts can differ by component. This small site-level diagnostic is separate from the main financial case, which assumes full adoption after launch. It does not revise the dashboard’s US$3m forecast. Before launch, show “not yet applicable” rather than presenting this example as an actual KPI result.
How to use the dashboard. Review blocking decisions weekly and reconcile benefits monthly. Each decision should update an owner’s commitment, a delivery date or the forecast. Keep unapproved recovery opportunities outside the committed forecast. After launch, replace readiness reporting with evidence of adoption, verified savings and operating performance.
For a wider programme, add one register row per non-overlapping benefit, retain initiative IDs and reconcile the total with finance. Define status thresholds for the programme before using red/amber/green indicators. This mockup flags a documented date slip and financial shortfall; it does not apply an arbitrary industry threshold.
Method note. The procurement case is illustrative and uses no employer or client data. It applies established financial and project-management principles; it is not an empirical study. Sources are linked inline.