Post-Merger Finance Integration: The 100-Day Plan for Combining Finance Functions

Why Finance Integration Determines Deal Outcomes

M&A integration failure is well documented. Studies consistently find that between 50% and 70% of mergers and acquisitions fail to deliver their expected value, and a significant proportion of those failures trace back to integration execution rather than deal logic. The finance function is both the most important integration workstream and the one most commonly under-resourced. While commercial teams focus on cross-selling, product teams focus on platform integration, and HR focuses on culture, the finance function is expected to simultaneously close the month, produce the first combined management accounts, begin the IFRS 3 purchase price allocation process, and manage the uncertainty and anxiety of a combined finance team.

The 100-day framework provides structure for this period. It is not a rigid schedule but a prioritised sequence of milestones that ensures the most critical foundations are in place before less urgent activities begin. The specific timing of each milestone will depend on the complexity of the transaction, the relative sizes of the combining entities, and the state of each company's finance function at the point of close.

Day One Readiness: What Must Be in Place at Close

Day one readiness is the list of items that must be functional at the exact moment the deal closes. These are not targets for the first week; they are mandatory pre-conditions for operating as a combined entity. Failure to prepare any of them creates an immediate operational problem that is visible to employees, suppliers, and customers.

• Banking mandates updated: signatories to the acquired company's bank accounts must be updated to reflect the new ownership structure. This requires advance notice to banks (typically 2 to 4 weeks) and should be coordinated during the pre-close preparation period.
• Accounts payable cut-over agreed: a clear decision must be made about whether AP will continue to be processed through the acquired company's systems or will be cut over immediately to the acquirer's systems. Ambiguity here results in invoices not being paid.
• Payroll confirmed for the first pay date: what is the next payroll run date for each entity, and how will it be processed? Payroll failure in the first month post-close is one of the most damaging integration failures from an employee relations perspective.
• Basic financial controls documented: who has authorisation to spend money on behalf of the combined entity, up to what limits, and through which approval process? This must be communicated to all budget holders before day one.
• Insurance updated: the combined entity's insurance policies (Directors and Officers, professional indemnity, property, cyber) must be reviewed and updated to reflect the new group structure.
• Emergency contacts established: key contacts at material suppliers, the acquirer's audit firm, external legal counsel, and key banking relationships must be documented and distributed to the relevant members of the combined finance team.
• Communication to the acquired company's finance team: a clear, honest communication from the CFO or Finance Director to the acquired finance team on day one, covering what has changed, what has not changed, who their line manager is, and what the integration plan is for the coming weeks.

Days 1–30: Financial Reporting Alignment

The first thirty days are focused on the minimum viable reporting infrastructure: getting to a point where the combined entity can produce management accounts that the board can read and act on. This does not mean perfect, fully integrated reporting. It means a coherent consolidated view of trading performance, cash, and headcount that allows the leadership team to make decisions.

The most important early decision is the chart of accounts. The two entities almost certainly use different account codes, different cost centre structures, and different nominal account classifications. Mapping both to a single, agreed chart of accounts is the prerequisite for any combined reporting. This sounds administrative; it is actually the foundation of every subsequent financial analysis. Do it wrong, and every management account for the next eighteen months will be unreliable.

The first combined management accounts should be produced within the first thirty days, even if they are rough. The ideal outcome is management accounts for the first full calendar month post-close that show: consolidated revenue by business unit; consolidated P&L with costs mapped to the agreed chart of accounts; consolidated cash position; and a brief narrative explaining material variances from forecast. These accounts will not be perfect. They will contain classification anomalies, timing differences, and items that require further analysis. Produce them anyway. Perfect is the enemy of done, and the board needs financial visibility immediately.

The IFRS 3 purchase price allocation (PPA) process must begin in the first thirty days, even though it will not be completed for several months. IFRS 3 requires the acquirer to identify and measure the fair value of all identifiable assets and liabilities acquired, and to allocate any excess purchase consideration to goodwill. The clock starts at the acquisition date, and the PPA must be completed within twelve months. Beginning early allows adequate time to engage a specialist valuer for intangible asset identification (customer relationships, technology, brand) and to resolve any contentious valuation questions before they become an audit issue.

Days 30–60: ERP Integration Planning

The question of whether to consolidate onto a single ERP system, and if so which one and when, is one of the most consequential decisions of the integration. It is also one of the most frequently rushed. A poorly executed ERP migration in the middle of a business integration is one of the most reliable ways to create a financial reporting crisis.

The first step is an honest assessment of each system's capabilities. The acquirer's ERP may be materially more capable than the acquired company's, which would suggest a migration. Alternatively, the acquired company may be running a more modern system. In many cases, particularly where the acquired company is significantly smaller, the correct answer for the first twelve to eighteen months is to maintain two separate systems, produce consolidated accounts through a consolidation layer or spreadsheet, and plan a proper ERP migration for a later, more stable phase of the integration.

If a migration is planned, the data migration is the most complex element. Chart of accounts mapping, opening balance migration, historical transaction data (critical for audit trail and management reporting), customer and supplier master data, and any system-specific configurations must all be carefully planned, tested in a parallel run environment, and validated before go-live. A realistic ERP migration for a business of any size takes six to twelve months from decision to go-live, assuming competent project management and adequate resourcing.

Treasury consolidation — combining cash pooling, banking relationships, and payment operations — should also be planned in this phase. The primary consideration is whether the combined entity can access a notional or physical cash pool, reducing the total cash held idle across the group. For groups with significant cash balances across multiple entities, treasury consolidation is one of the fastest and most tangible financial synergies available.

Days 60–100: Combined Reporting Live

By day one hundred, the finance function should have delivered on three core milestones. First, combined management accounts on the shared chart of accounts, produced consistently and within the same reporting timetable as the pre-merger acquirer. Second, a synergy tracker that is operational and reporting monthly to the board, showing actual synergy delivery against the deal case. Third, the IFRS 3 purchase price allocation substantially complete, with all significant intangible assets identified, valued, and agreed with the external auditor.

The synergy tracker deserves particular attention. In almost every merger, the deal case includes synergy assumptions that were optimistic in their timeline and sometimes also in their quantum. The finance function's role is not to defend the deal case; it is to provide an honest assessment of which synergies are on track, which are delayed, and which are unlikely to be achieved. A synergy tracker that reports everything as "on track" in month three is performing a public relations function, not a financial management function. Boards should demand specificity: named synergy initiative, responsible owner, committed amount, original timeline, revised timeline, and year-to-date delivery.

Organisational Integration: Managing the Finance Team

Finance integration is not only a systems and processes challenge; it is also a people challenge. The acquired company's finance team faces significant uncertainty: will their roles survive, who will they report to, will their employer change, and how will their experience and institutional knowledge be valued in the new organisation? If this uncertainty is not managed proactively, the risk is attrition of exactly the people whose knowledge of the acquired business is most valuable in the first twelve months.

The CFO of the combined entity should commit to three things in the first week: communicating clearly about what is known and what is not yet decided; establishing a timeline for organisational decisions; and being personally accessible to senior members of the acquired finance team. The worst possible approach is silence. People who do not know their future will decide for themselves and leave.

The organisational design question for the combined finance function is genuinely complex. Some roles will be duplicated, and not all of them will have a place in the combined structure. The CFO should work through the organisational design with the same rigour as any other integration workstream: map the combined function, identify genuine duplication, make decisions, communicate them, and then support the people who are leaving to do so with dignity. Indefinite ambiguity is always worse than a difficult but clear decision.

The Integration Risks Most Commonly Underestimated

After working through multiple integrations, certain recurring patterns of underestimation emerge. Understanding them in advance allows mitigation planning before they crystallise.

• The complexity of IFRS 3: PPA work is consistently more complex and time-consuming than deal teams expect. Intangible asset identification (particularly for software, data assets, and customer relationships) requires specialist valuation expertise and extensive negotiation with the external auditor. Budget twelve to eighteen months, not three.
• Tax group formation: forming a UK corporation tax group (which allows loss relief between entities) requires careful sequencing and advance planning with tax advisers. The filing requirements have strict deadlines. Missing the election window can have material tax consequences.
• The hidden cost of running two systems: maintaining two separate finance systems temporarily feels like the safe option, but it generates significant manual work in the form of reconciliations, duplicate processing, and data validation. Budget this time explicitly rather than assuming it will be absorbed.
• Deferred revenue accounting differences: if the two companies have different revenue recognition policies for similar products (a common occurrence in software-enabled businesses), the impact on the combined P&L can be material and must be identified and resolved before the first combined accounts are published.
• Synergy delivery being slower than modelled: cost synergies that require headcount reduction are subject to UK employment law, including redundancy obligations and consultation requirements that add cost and time to delivery. Revenue synergies almost always take longer than modelled. The deal case should be stress-tested against a scenario in which synergies deliver at 60% of the modelled amount and six months later.

Key Takeaways

• Day one readiness is not optional. Banking mandates, payroll confirmation, AP process, financial controls, and a communication to the acquired finance team must be complete at the exact moment the deal closes.
• The chart of accounts is the foundation of everything that follows. Agree it in the first two weeks and document the mapping rigorously. Changing it after the first management accounts have been produced creates significant remediation work.
• Produce the first combined management accounts within thirty days, even if imperfect. The board needs financial visibility immediately, and a rough combined view is better than separate views from two businesses.
• The IFRS 3 purchase price allocation clock starts at acquisition date and must be completed within twelve months. Begin the process in the first thirty days and budget adequately for specialist intangible asset valuation.
• ERP consolidation decisions should be made in the thirty to sixty day window, with an honest assessment of both systems' capabilities. Do not rush a migration; a poorly executed ERP migration is one of the most reliable ways to create a reporting crisis.
• The synergy tracker must report honestly. A tracker that shows everything "on track" in month three is performing a PR function. Boards deserve specificity: owner, amount, timeline, and actual delivery to date.
• Finance team organisational design should be resolved quickly. Indefinite ambiguity causes the best people to leave first. Communicate a timeline, make decisions, and support those leaving with dignity.