How Can New CFOs Quickly Secure a Company's Spending After a Major Acquisition?

The ink is barely dry on a $40 million acquisition, and the new CFO has a problem. The acquired company has 200 employees, three offices, a roster of vendors that nobody has fully catalogued, and an approval process that consists of the former owner saying yes to things in the hallway. There is no delegation of authority matrix. There is no structured approval workflow. There is no clear picture of what has been committed, what has been paid, and what is still pending.

This is the reality of post-acquisition integration from a finance perspective. The deal team spent months on due diligence, valuation models, and synergy projections. But the moment the transaction closes, the CFO inherits an operating environment where the financial controls may be non-existent, inconsistent, or incompatible with the acquiring company’s standards. The first 90 days after close are when the greatest financial risk sits, and they are also when the new CFO has the least visibility into how money is being spent.

Why Post-Acquisition Spending Is the Biggest Integration Risk

Most post-acquisition integration discussions focus on culture, technology systems, and organisational structure. These are important. But the immediate financial risk is simpler and more urgent: money is leaving the company through spending channels that the new leadership does not control, does not fully see, and cannot verify.

The acquired company has existing vendor relationships, subscription commitments, and purchase patterns that were established under the previous ownership’s standards. Some of these commitments are essential. Some are redundant. Some may have been favourable arrangements for the former owner that do not serve the combined entity. Without structured controls, all of these continue to operate on autopilot.

Employees in the acquired company continue to submit expenses, approve invoices, and commit to new purchases based on the authority they had before the acquisition. Unless someone explicitly redefines those authorities, the old rules apply by default. A department head who previously had unlimited approval authority does not lose that authority simply because the company was sold. They keep spending until someone tells them otherwise.

The CFO’s challenge is to establish control quickly without disrupting operations. Freeze spending entirely and you damage supplier relationships, stall production, and signal to the acquired team that they are not trusted. Change nothing and you accept spending risk that could consume the synergies the deal was built on.

The First 30 Days: Visibility Before Control

The smartest CFOs do not start with restrictions. They start with visibility. Before you can secure spending, you need to see it.

The first step is mapping the acquired company’s spending landscape. Who are the vendors? What are the recurring commitments? Which cost categories carry the highest volume? Who has been approving purchases, and under what authority? This mapping exercise often reveals surprises: duplicate subscriptions, overlapping vendor relationships with the acquiring company, and spending commitments that were not disclosed during due diligence.

The second step is deploying automated approval workflows across the acquired entity’s accounts payable. This does not mean replacing the acquired company’s accounting system on day one. It means adding a structured approval layer on top of whatever system they are using, so that every invoice, purchase order, and expense claim passes through predefined rules before it reaches the accounting system. The workflow captures every spending commitment in real time, giving the CFO immediate visibility into what is being approved, by whom, and against which budget.

This approach achieves two things simultaneously. It provides the data the CFO needs to make informed decisions about where to tighten controls. And it does so without disrupting the acquired team’s day-to-day operations, because the approval workflow operates alongside the existing process rather than replacing it.

Days 30 to 60: Establishing the New Rules

With 30 days of visibility data, the CFO now knows where the risks are. The next step is implementing the spending controls that the combined entity requires.

A new delegation of authority matrix defines who can approve what, at which thresholds. This is the most important governance document in the post-acquisition period. It replaces the informal authorities that existed under the previous ownership with explicit, system-enforced rules. A department head who previously approved unlimited purchases now has a $10,000 threshold. Anything above that routes to the finance director or the CFO.

Segregation of duties is enforced through the approval workflow. The person who creates a vendor record cannot also approve invoices from that vendor. The person who submits a purchase order cannot approve the corresponding payment. These controls prevent the most common forms of procurement fraud, which are statistically more likely during transition periods when oversight is inconsistent and employees know the rules are changing.

Vendor consolidation begins. The visibility data from the first 30 days will have revealed overlapping suppliers, duplicate contracts, and opportunities to consolidate spend across the combined entity. The CFO can now make informed decisions about which vendors to retain, which to renegotiate, and which to terminate, rather than relying on the acquired team’s assertions about which relationships are essential.

Days 60 to 90: Integration and Alignment

By day 60, the acquired company should be operating under the same financial governance framework as the parent. The approval workflows, spending thresholds, and segregation of duties rules should be consistent across both entities. The audit trail should be unified, providing a single view of all spending across the combined organisation.

The CFO’s focus in this phase shifts from establishing control to optimising the combined finance function. Month-end close processes are aligned so that both entities report on the same timeline. Budget structures are unified so that spending across the combined entity can be tracked against a single plan. Reporting is standardised so that the board receives a consolidated view of financial performance. For organisations navigating how finance leaders maintain control across multiple entities, this phase is where the operational complexity of running two finance teams under one governance framework is resolved.

The approval workflow that was deployed in the first 30 days now serves a different purpose. It is no longer just a visibility tool. It is the operational mechanism that enforces the combined entity’s financial policies, generates the audit trail that auditors and investors require, and provides the real-time spending data that the CFO needs to manage the integration proactively.

The Fraud Window That Nobody Talks About

There is a period during every acquisition when the risk of financial fraud is significantly elevated. The old controls have been disrupted. The new controls have not yet been fully implemented. Employees are uncertain about their future and may be less invested in protecting the company’s interests. And the acquiring company’s attention is divided across dozens of integration workstreams.

This window is when fictitious vendor schemes, duplicate invoice fraud, and expense manipulation are most likely to occur. An employee who knows the company is being integrated may submit inflated expenses, knowing that the finance team is too stretched to review them carefully. A manager may approve payments to a vendor they have a personal relationship with, knowing that the usual oversight is temporarily absent.

Automated approval workflows close this window because they do not have attention limits. The system checks every transaction against the rules, every time, regardless of how busy the integration team is. Duplicate invoices are flagged. Spending above threshold is routed to the correct approver. Bank detail changes trigger verification. These controls operate with the same rigour on day one of the integration as they do on day 365, which is precisely what is needed during a period when human oversight is at its weakest.

Why Speed Matters More Than Perfection

The biggest mistake CFOs make during post-acquisition integration is waiting for the perfect system before implementing controls. They want to migrate the acquired company onto the parent’s ERP first. They want to align the chart of accounts. They want to complete the full vendor audit. These are all important, but they take months. And during those months, spending is uncontrolled.

The pragmatic approach is to deploy lightweight, configurable approval workflows immediately, even before the systems integration is complete. A cloud-based approval platform that connects to the acquired company’s existing accounting software can be operational within days, not months. It does not require an ERP migration. It does not require a chart of accounts alignment. It requires defining the approval rules and turning the system on.

Perfection can follow. ERP consolidation can happen on its own timeline. The chart of accounts can be aligned over the first year. The vendor audit can proceed methodically. But spending control cannot wait. Every week without structured approvals is a week of financial exposure that the acquiring company is paying for.

Synergy Capture Depends on Spending Control

The deal thesis behind most acquisitions includes a cost synergy number. The acquiring company expects to save a defined amount by consolidating vendors, eliminating redundant roles, and streamlining operations. But synergies do not capture themselves. They require active management, and that management depends on knowing exactly where money is being spent across both entities.

Without structured spending controls and real-time visibility, the synergy projections remain theoretical. The CFO cannot consolidate vendor spend if they do not know the total spend per vendor across both companies. They cannot eliminate redundant subscriptions if no one has a centralised view of what both entities are paying for. They cannot reduce procurement costs if approval authorities are unclear and department heads continue to make independent purchasing decisions.

The automated approval layer serves as the data engine for synergy capture. Every transaction is categorised, tagged to a cost centre, and attributed to a vendor. Within weeks, the CFO has a consolidated spending map that reveals exactly where the overlaps are, where the consolidation opportunities sit, and where the projected savings can be realised. Without that data, synergy targets are a line in a spreadsheet. With it, they become an actionable plan.

What Investors and Boards Expect

Investors and board members who approved the acquisition expect the CFO to demonstrate control over the combined entity’s spending within the first quarter. They do not expect the full integration to be complete. They do expect that the CFO can answer three questions at any time: what is the combined entity spending, who is approving it, and is it within the approved budget?

A CFO who can present a structured audit trail showing every approval decision across both entities from day one of the integration builds credibility with the board and sends a clear signal to the acquired team that the new governance standards are real, not aspirational.

Conversely, a CFO who reports at the first quarterly review that spending controls are still being implemented signals that the integration is behind schedule before it has properly begun. In an M&A context, that is a trust problem that can take years to recover from.

The acquisition created value on paper. The integration is where that value is either captured or lost. And the CFO’s ability to secure spending in the first 90 days is the earliest and most visible indicator of whether the integration is on track. The companies that treat post-acquisition financial controls as a day-one priority, not a someday project, are the ones that deliver on the deal thesis. The ones that wait find out what the cost of delayed controls looks like when the first quarterly report lands on the board table.