A signed purchase agreement is not a value-creation plan. This acquisition integration case study follows a representative mid-market buyer whose leadership team needed to combine a newly acquired business without losing control of cash, reporting, customers, or key talent. The transaction had a clear strategic rationale. The risk was whether the finance function could turn that rationale into measurable results quickly enough.
The buyer was a $180 million business services company with healthy margins and an experienced management team. It acquired a $55 million regional competitor to gain customer density, specialized talent, and cross-sell opportunities. The deal model projected $6 million in annual run-rate synergies, largely from procurement savings, back-office consolidation, and reduced facility costs.
The first challenge appeared before Day 1. The acquired company closed its books 18 business days after month-end, relied on disconnected spreadsheets for cash forecasting, and had limited documentation around revenue recognition judgments. Its owner-led finance team knew the business well, but several critical processes depended on individual knowledge rather than documented controls.
For the buyer’s CFO, integration was not an administrative follow-up to the deal. It was the point at which the investment case would either become credible or begin to erode.
The acquisition integration case study: the finance problem
The buyer initially planned to migrate the target onto its enterprise resource planning system within 60 days. That goal looked efficient on paper. In practice, it would have introduced unnecessary risk. The target’s customer master data contained duplicate records, its chart of accounts did not map cleanly to the buyer’s reporting structure, and several large contracts had billing terms that required review before a revenue process could be standardized.
A rushed system conversion could have interrupted invoicing, delayed collections, and created management reporting that neither leadership team trusted. It also would have placed the acquired company’s finance staff under pressure at the exact moment the business needed them to explain exceptions, preserve customer knowledge, and maintain daily operations.
The CFO reframed the issue around three decisions: what required immediate control, what could operate in parallel temporarily, and what should not change until the underlying data and process design were ready. This distinction prevented the integration team from treating every difference as a Day 1 emergency.
The resulting program focused first on financial visibility. It established a 13-week cash forecast, daily liquidity reporting, weekly accounts receivable reviews, and a common definition of bookings, revenue, gross margin, and operating expenses. These actions did not create synergies by themselves. They gave leadership a reliable baseline from which to manage them.
Building the first 100-day finance plan
The finance workstream was organized around clear owners, decision rights, and deadlines. The CFO chaired a weekly integration steering meeting with leaders from operations, HR, sales, IT, and legal. Each workstream reported against a simple scorecard: financial impact, operational risk, target date, accountable executive, and decision required.
During the first 30 days, the priority was business continuity. The acquired company retained its existing accounting platform and payroll process, but adopted the buyer’s approval thresholds for spending, banking access, and customer credit exceptions. Treasury centralized visibility over both entities’ bank balances. No account was closed until authorized signatories, payment workflows, and recurring payment requirements had been verified.
This was a deliberate trade-off. Running two accounting environments for a short period added work and cost. It reduced the far greater risk of a poorly controlled cutover. The CFO also required a Day 15 balance sheet review, rather than waiting for the first full month-end close. That review surfaced unrecorded vendor invoices, an outdated fixed-asset register, and customer deposits that had been classified inconsistently.
From Days 31 through 60, the focus shifted to reporting discipline and synergy validation. Finance created a bridge between the target’s legacy accounts and the buyer’s management reporting categories. Instead of forcing an immediate chart-of-accounts replacement, the team built a controlled mapping process and reconciled results in both views. Leadership could then compare actual performance with the deal model without confusing accounting reclassification with operational improvement.
The team also separated announced synergies from bankable savings. A procurement opportunity was not counted as a realized benefit until pricing changed, usage was controlled, and the effect appeared in the income statement or cash flow forecast. A planned facility exit was not recorded as savings until lease obligations, severance, and transition costs were understood.
By Days 61 through 100, the program moved toward process integration. Finance standardized the close calendar, recurring reconciliations, spending authority matrix, and forecast templates. IT and finance completed data cleansing before migrating priority reporting and billing data. The systems conversion was rescheduled to a more realistic date, supported by testing milestones and a contingency plan.
What changed in the financial results
At the end of the first 100 days, the buyer had not completed every planned integration activity. It had, however, established the operating control needed to protect value. The combined organization reduced the close process from 18 business days to nine. Weekly cash forecasting improved visibility into working capital, helping the company release approximately $1.4 million tied up in overdue receivables and excess purchasing.
The finance team identified that $900,000 of projected savings would require longer-term contract negotiations and could not reasonably be delivered in the first year. This was not a failure of the deal. It was a correction to the original assumption set, made early enough for leadership to adjust the operating plan and communicate with confidence.
At the same time, the company secured $2.2 million of annualized procurement and overhead savings, with clear owners and supporting evidence. It also found a revenue opportunity that had not been fully reflected in the investment case: several target customers could adopt the buyer’s higher-margin service line. Finance partnered with sales to track the pipeline separately from cost synergies, avoiding the common mistake of presenting unqualified commercial potential as realized value.
The most significant outcome was credibility. The CEO and board received a clear integration view each month: baseline performance, one-time costs, realized savings, at-risk initiatives, cash impact, and decisions needed. That clarity allowed management to address problems before they became quarter-end surprises.
Lessons CFOs can apply before the next deal
The case highlights a recurring acquisition integration reality: speed matters, but sequencing matters more. Immediate control over cash, authority, customer billing, and reporting definitions should take precedence over a rushed technology migration or wholesale policy rewrite.
CFOs should also challenge the idea that a combined company needs one system on Day 1. A temporary parallel environment can be the right answer when it protects collections, avoids payroll disruption, and gives finance time to validate opening balances. The key is to make the temporary state controlled, time-bound, and visible. Parallel processes become dangerous only when no one owns the exit plan.
Synergies require the same rigor as a forecast. Every initiative should have a baseline, accountable owner, expected timing, implementation cost, dependencies, and a definition of realization. If a savings estimate cannot be traced to a contract, headcount action, spend category, or measurable operating change, it should remain an opportunity rather than a committed result.
Integration also exposes capability gaps that diligence may not fully reveal. A target may have competent people but lack capacity for a compressed close, cash forecasting, purchase accounting support, or systems migration. Bringing in transaction-ready finance leadership and targeted accounting capacity can protect the core team from being overwhelmed by integration tasks while day-to-day operations continue.
For complex transactions, The CFO HQ can provide that combination of CFO leadership, deal support, accounting execution, and transformation capacity without requiring a permanent expansion of the finance organization.
The practical test is simple: after close, can leadership see the combined business clearly enough to make decisions before value leaks away? If the answer is no, the next priority is not another integration presentation. It is establishing the financial controls, operating rhythm, and accountable ownership that let the business move forward with confidence.
