PerspectiveOperations
Where operating costs hide after a merger
Integration plans count the savings and often miss the work that produces them. What to check before the first budget cycle as one company.
DelloiteConsultingAsia Operations practiceNovember 20263 minute read

The saving is counted once. The work is not.
A synergy figure is usually agreed before a deal closes, by a small team working from two sets of accounts. It enters the first combined budget as a reduction. The changes that would make the reduction real are decided later, by other people: who processes the invoices, which warehouse ships the order, which system holds the customer record.
Between those two moments the cost goes somewhere. It rarely disappears. A year on, the function that was meant to shrink has shrunk, the total has not moved much, and nobody can say where the difference went. It can be found, and the search is not complicated.
Four places to look
- Work that moved instead of stopping. When two teams are merged, the tasks the smaller team used to do are picked up elsewhere: by the business units, by a shared service centre, by contractors. Look at the functions around the one that shrank, and look at contractor, overtime and outsourcing lines as well as headcount.
- Two of everything, for longer than planned. Two finance systems, two payrolls, two sets of supplier contracts. Each has a running cost and a team that keeps it going. The plan gives a date for switching one off. Check what that date depends on, and whether anyone owns the dependency.
- Temporary arrangements that became permanent. Service agreements with the seller, allowances to keep key people through the first year, offices run side by side. Each was approved as temporary. List them with their end dates and the name of the person who can end them.
- Costs parked in the integration budget. A one-off integration budget is a convenient home for costs that are really recurring. Review what has been charged to it and ask what happens to each line on the day that budget closes.
When the deal crosses borders
In a deal that spans several countries the same check has to be made entity by entity. Employment terms, notice periods and the rules for moving staff between employers differ from one jurisdiction to the next. A saving that is immediate in one country can take a year in another, and in some it needs consultation before it can start.
A plan that applies one timetable to every country will be wrong somewhere. Ask for the savings by legal entity, with the local constraint written beside each one.
Before the first combined budget
- Rebuild the baseline by activity. Set out the combined cost by what the work is (order to cash, procurement, payroll, IT support), not by which legacy company it came from. Hidden duplication shows up when the two halves are laid side by side.
- Give every saving an owner in the line. A saving owned by the integration office ends when the integration office does. The person who runs the function should hold the number in their own budget.
- Set a closing date for integration costs. After that date each remaining cost is either stopped or moved into the running budget where everyone can see it.
None of this needs new systems. It needs someone to compare the plan with the ledger, line by line, before the next budget makes the gap permanent.
Working on something like this?
Talk to the operations team