Managing Finance Operations During M&A: The CFO Playbook

M&A creates a special kind of pressure for finance teams. The deal closes, the press release goes out, leadership expects synergy, and suddenly the CFO is responsible for making two finance operations behave like one business.

That work is not glamorous. Chart of accounts mapping. ERP decisions. Bank account cleanup. Payroll timing. Close calendars. Vendor files. Tax structure. Team retention. Controls. Reporting rules. A hundred small things that can quietly become big problems if nobody owns them.

Finance operations during M&A need a clear playbook because integration is not just an accounting exercise. It’s how the company protects cash, reporting quality, compliance, and executive trust while the business is changing shape.

Why CFOs Need to Lead the Finance Integration Early

Finance gets pulled in late on too many deals. That’s a mistake.

By the time the deal is signed, many of the hard operating questions are already waiting. How will the acquired company report into the parent? Which system becomes the source of truth? Are there hidden control gaps? Will the close process slow down? Can leadership actually see combined performance by business unit, product line, or geography?

The CFO doesn’t need to personally run every workstream. But the CFO does need to set the operating rules early. If finance integration starts after close with no sequencing, teams end up patching together reports, reconciling mismatched data, and explaining numbers nobody fully trusts.

That is not integration. That is cleanup.

Start With the Finance Operating Model

The first question is not “Which ERP are we using?” The first question is, “How should finance operate after this deal?”

Some acquisitions are fully absorbed into the parent company. Others remain semi-independent for a period of time. A divestiture may require the opposite: separating shared finance processes without breaking reporting or cash controls. The answer changes everything.

CFOs should define the target operating model around:

• Reporting structure: how the acquired or separated business will report performance

• Close process: timing, ownership, calendar, and consolidation requirements

• Systems strategy: which platforms stay, which migrate, and which are temporary

• Controls: approval authority, segregation of duties, and audit requirements

• Cash management: bank accounts, treasury visibility, payment authority, and working capital oversight

• People model: who stays, who moves, who owns integration, and where knowledge risk sits

Skipping this step is how companies make expensive system choices that don’t match how the business will actually run.

Chart of Accounts Harmonization: Small Labels, Big Consequences

The chart of accounts looks like a technical finance task. It isn’t. It controls how the business sees itself.

During M&A, chart of accounts harmonization decides whether leadership can compare performance cleanly across the combined company. Revenue categories, cost centers, departments, product lines, entities, and intercompany accounts all need consistent logic.

The trouble is that two companies may use similar account names in different ways. “Professional services” might mean delivery labor in one company and outside consultants in another. “Customer success” might sit in sales for one business and operations for the other. Nobody notices until the first combined report looks strange.

What CFOs should require

• A mapping document from legacy accounts to the target chart of accounts

• Clear ownership for ambiguous accounts and business definitions

• Rules for new account creation during the integration period

• Testing against historical periods before leadership reporting goes live

• A plan for handling discontinued, duplicate, or temporary accounts

Do not let the chart mapping become a back-office side project. If the mapping is poor, every downstream report becomes harder to trust.

System Consolidation: Move Fast, But Not Blind

ERP and finance system consolidation gets political quickly. The acquiring company often assumes its system should win. Sometimes that’s right. Sometimes the acquired company has cleaner workflows, better reporting, or fewer custom patches than anyone expected.

A CFO should evaluate systems based on the future operating model, not internal pride.

Key questions:

• Which system gives the cleanest consolidated reporting?

• Which system supports the required entities, currencies, tax rules, and approval flows?

• What integrations depend on each platform?

• How much historical data needs to migrate?

• What breaks if the team migrates too quickly?

• Which system has the stronger controls and audit trail?

There are usually three practical choices: migrate immediately, run systems in parallel for a defined period, or integrate reporting first and migrate operations later. The worst choice is an undefined middle state where both systems live forever and finance becomes the translation layer.

The First Close After the Deal Is a Stress Test

The first monthly close after close is where finance integration stops being theoretical.

Expect problems. Intercompany entries may not tie. Revenue recognition policies may need interpretation. Payroll accruals may land differently. Supporting schedules may not match the parent company’s format. Some numbers will arrive late because the acquired team is still working the old way.

That doesn’t mean the deal is failing. It means the CFO needs a controlled close plan.

First-close checklist

• Publish a combined close calendar before the reporting period ends

• Assign owners for each major schedule and reconciliation

• Identify policy differences before entries are booked

• Set escalation paths for late or disputed items

• Track manual adjustments separately so they don’t become permanent workarounds

• Hold a post-close review focused on fixes before the next cycle

A messy first close can still be a good first close if the issues are visible, owned, and reduced before the next cycle.

Cash, Treasury, and Working Capital Cannot Wait

Cash management deserves early attention because M&A can create confusion around banking, payment authority, collections, credit lines, and supplier obligations.

The CFO should know where cash sits, who can move it, which accounts remain open, and how working capital is trending after the transaction. This is especially important in integrations where customers, vendors, and employees are still adjusting to new ownership.

Focus first on:

• Bank account inventory and signer authority

• Payment approval limits

• Customer remittance instructions

• Vendor payment timing and duplicate vendor risk

• Debt, covenants, and liquidity reporting

• Short-term cash forecast updates

Cash surprises after a deal are rarely caused by one dramatic failure. More often, they come from small timing gaps nobody connected soon enough.

Team Retention: Protect the People Who Know Where the Bodies Are Buried

Finance integration depends heavily on institutional knowledge. The people who understand odd billing rules, legacy reports, vendor histories, local tax details, and customer payment behavior may not have impressive titles. Lose them too early and the integration gets harder overnight.

Retention planning should start before close whenever possible. CFOs need to identify critical finance talent, not just senior finance talent.

Roles to evaluate carefully

• Controller and assistant controller

• Payroll lead

• Billing and collections specialists

• AP lead and vendor master owner

• FP&A analyst who owns recurring management reports

• ERP admin or finance systems power user

• Tax and compliance owner

People leave when the future feels vague. Be direct about roles, reporting lines, timelines, and what will change. If you cannot promise certainty, say what is known and what is still being decided. Silence creates rumors, and rumors slow the work.

Controls and Compliance During the Messy Middle

Post-close finance operations often enter a messy middle. Old processes are still running. New approvals are being introduced. Systems may not be fully integrated. That is exactly when control discipline matters.

CFOs should avoid two extremes. One is freezing everything until the perfect control model exists. The other is letting teams “just get through integration” with weak approvals and undocumented manual work.

Better answer: create temporary controls with clear owners and expiration dates.

• Define approval authority for payments, contracts, write-offs, and journal entries

• Document manual workarounds and review them weekly

• Restrict system access based on current roles, not legacy habits

• Monitor duplicate vendors, unusual payments, and new bank instructions

• Keep audit evidence even if the process is transitional

Temporary does not mean informal. Temporary means controlled until replaced.

Divestitures Need a Different Finance Playbook

Divestitures are not just integrations in reverse. They introduce separation risk.

Finance must decide which systems, people, contracts, data, reports, and controls stay with the parent and which move with the separated business. Shared services become transition service agreements. Historical reporting needs to be carved out. Bank accounts, tax registrations, vendor relationships, and payroll processes may need clean separation.

The CFO should pay close attention to stranded cost. After a divestiture, the parent company may still carry people, systems, leases, or vendor commitments that were previously allocated to the sold business. If those costs are not addressed, the remaining business can look worse than expected.

For divestitures, finance should build a separation checklist around systems, reporting, cash, tax, people, contracts, and post-close service commitments.

A 90-Day CFO Playbook for Finance Integration

Before close or Day 0

• Name finance integration owners and workstream leads

• Define the target finance operating model

• Inventory systems, bank accounts, reporting packages, controls, and critical finance staff

• Identify close calendar differences and major accounting policy gaps

• Build the first version of the integration risk log

Days 1 to 30

• Secure cash visibility and payment controls

• Publish the first combined close calendar

• Begin chart of accounts mapping and reporting alignment

• Confirm finance team roles, retention risks, and communication cadence

• Document temporary controls and manual workarounds

Days 31 to 60

• Complete first-close review and fix the highest-friction issues

• Decide ERP and system consolidation sequencing

• Standardize management reporting definitions

• Reduce duplicate vendor, customer, and account records

• Track synergy, integration cost, and stranded cost separately

Days 61 to 90

• Lock the target chart of accounts path and migration timeline

• Remove unnecessary manual reporting steps

• Finalize long-term finance team structure

• Prepare system cutover plans if consolidation is ready

• Report integration progress to leadership using operational metrics, not vague status updates

A 90-day plan will not finish every finance integration. It should create control, visibility, and momentum. That is the job.

Metrics CFOs Should Track During M&A Finance Integration

Integration progress needs measurement. Otherwise, every update becomes “on track” until something breaks.

• Close cycle timing: days to close before and after the deal

• Manual adjustments: number and value of integration-related adjustments

• Chart mapping completion: percentage of accounts mapped and validated

• Cash visibility coverage: percentage of bank accounts and entities visible to treasury

• System migration readiness: data, controls, testing, and user acceptance status

• Finance retention risk: critical roles identified and retention plans in place

• Control exceptions: unresolved access, approval, or reconciliation issues

• Synergy tracking: actual savings or costs against the deal model

The CFO should insist on facts. Not color-coded optimism.

FAQ: Managing Finance Operations During M&A

What should CFOs prioritize first after an acquisition closes?

Cash visibility, payment controls, close calendar alignment, finance team communication, and reporting continuity should come first. System consolidation matters, but it should not outrank control and visibility during the first few weeks.

How soon should companies consolidate finance systems after M&A?

Only as soon as the business is ready. Some integrations can move quickly. Others need a defined parallel period so reporting, controls, data migration, and users are prepared. A rushed ERP migration can create more risk than running two systems for a short, controlled period.

Why is chart of accounts harmonization so important?

The chart of accounts controls how performance is reported and compared. If account mapping is inconsistent, leadership may see distorted margins, costs, revenue categories, or business unit results.

What finance roles are most important to retain during integration?

Controllers, payroll leads, billing and collections staff, AP owners, FP&A report owners, tax contacts, and finance systems power users often carry the knowledge needed to keep operations moving.

How should CFOs manage controls during the integration period?

Use temporary controls with clear ownership, documentation, and expiration dates. Payment approvals, system access, journal entries, vendor changes, and manual reconciliations should be watched closely while the permanent model is being built.

Finance Integration Is Where the Deal Becomes Real

M&A strategy may start in the deal model, but finance operations prove whether the model can work. The CFO has to turn two sets of systems, people, accounts, controls, and reporting habits into a usable operating structure.

Do that work early. Keep it visible. Protect cash first, reporting second, systems third. And don’t lose the people who understand how the numbers are actually made.

For more CFO leadership topics and executive finance insights, visit the CFOMeet.org homepage.