Interim CFO financial integration after acquisition: 4 checks

Interim CFO financial integration after acquisition fails most often because the buyer treats it as a reporting exercise instead of a decision exercise. The new finance lead inherits two charts of accounts, two close calendars, and two sets of habits, then spends the first quarter reconciling history rather than setting priorities. The consequence shows up later: cash forecasts nobody trusts, investor reports that need three rounds of explanation, and a permanent hire who walks into a mess that was never sorted out.

Starting with the wrong mandate

The most common mistake is hiring an interim CFO to « fix the numbers » without defining what fixing means. That phrase can cover a dozen different jobs, and the person you bring in will pick the interpretation that matches their own background. If you wanted a clean consolidation and they deliver a cash forecasting overhaul, both of you will feel like the engagement failed.

Write the mandate as a short list of decisions the interim CFO owns, decisions they influence, and decisions that stay with you. Ownership is the part people skip. An interim finance lead who cannot approve a journal entry policy or sign off on a forecast assumption is really an advisor, and the work will stall every time a judgment call lands on your desk.

Consider a concrete situation. A company buys a smaller competitor and wants consolidated reporting within one quarter. The interim CFO needs authority over the consolidation method, the mapping between the two charts of accounts, and the close calendar. They do not need authority over headcount or pricing. Naming that boundary up front prevents a slow drift into territory that belongs to the operating team.

Check the underlying detail of your own expectations before the first call. If you cannot say what a good outcome looks like in ninety days, the interim CFO will define it for you, and their definition may be narrower than what you actually need.

One more trap: treating the mandate as fixed. Acquisitions move. A deal that looked like a simple bolt-on can reveal a deferred revenue problem or a lease portfolio nobody mapped. Build in a review point where the mandate can be adjusted, and say who has the authority to adjust it.

Put the mandate in a document that names the decision rights explicitly. A table with three columns works better than a paragraph, because it forces you to place each recurring decision somewhere. When a question comes up that is not on the list, the default should be that it goes to the operating leader, not to the interim CFO by habit.

Assuming the two finance functions will merge on their own

They will not. Two finance teams that report to different leaders, use different systems, and close on different schedules do not converge because someone sent an email about alignment. Integration is a project with owners, dates, and a definition of done.

The mistake is delegating that project to whoever has the most bandwidth. Usually that is a controller who is already closing the books, or an FP&A manager who is already rebuilding the budget. Integration work loses every conflict with recurring work, because recurring work has a deadline and integration does not.

Give the interim CFO explicit ownership of the integration plan, and give the plan a visible place in the operating rhythm. A short weekly review with the people who touch the numbers beats a monthly steering committee that only hears status updates.

Watch for the quiet version of this problem. The two teams do merge on paper, but one side’s practices simply disappear. The acquired company’s revenue recognition approach gets overwritten by the buyer’s, even where the acquired contracts call for something different. Nobody notices until an auditor asks why the treatment changed.

Map the differences before you resolve them. List the areas where the two finance functions do things differently, then decide case by case whether to standardize, keep both, or build a bridge. That list is more useful than a general commitment to best practices, which usually means the buyer’s practices.

Give the integration plan a simple status that anyone can read. Each open item needs an owner, a target period, and a note on what is blocking it. If an item has been open for two closes with no movement, that is a signal the owner does not have the authority or the time to finish it.

Rebuilding the cash forecast too late

Cash is where integration problems surface first and loudest. A combined company has new payment terms, new payroll dates, new debt service, and often a new lender covenant to satisfy. If the cash forecast is still two spreadsheets stapled together, you are managing by surprise.

The common mistake is waiting for the consolidated accounting to be clean before touching the forecast. That order is backwards. Cash forecasting can be rebuilt from bank data and known commitments long before the general ledger is tidy, and the forecast is what tells you whether you have time to fix the ledger properly.

Start with the direct method: actual cash in, actual cash out, by week, for the next quarter. Then layer the known changes from the transaction. This is unglamorous work, and it is the fastest way to find the gaps that matter.

Ask the interim CFO to state the assumptions behind each major line. A forecast without visible assumptions cannot be challenged, and an unchallengeable forecast is a guess with formatting.

Set a review cadence that matches your cash cycle. A company with weekly payroll and monthly customer payments needs a weekly look. A company with quarterly billing can work on a longer rhythm. The cadence should follow the volatility, not the calendar convenience of the finance team.

Finally, decide what triggers action. If the forecast drops below a threshold, who gets called, and what do they decide? A forecast that only produces anxiety is not doing its job.

Separate the forecast into two layers so the team can work on both at once. The first layer is committed cash: payroll, rent, debt service, and signed supplier terms. The second is expected cash: collections, seasonal swings, and the timing of large customer payments. Committed cash is nearly certain and should be right. Expected cash carries the assumptions, and those are the lines worth reviewing line by line.

Letting reporting drift from what investors actually read

After an acquisition, reporting tends to grow. New entities, new segments, new consolidation entries, and a new set of internal consumers who all want their own view. The result is a package that takes longer to produce and answers fewer questions.

The mistake is building the report from the accounting structure rather than from the decisions it supports. If the board wants to know whether the acquired business is tracking to plan, a consolidated income statement does not answer that. A segment view with the plan alongside it does.

Ask the interim CFO to work backwards from the reader. List the three or four questions the board or the lender asks every period, then design the package to answer them on the first page. Everything else goes in an appendix.

Watch the definitions. Revenue, gross margin, and adjusted EBITDA can mean different things in the two legacy reporting packages. Pick one definition for each metric, write it down, and apply it consistently. Changing definitions mid-year creates confusion that takes several periods to clear.

If you report under ASC 606, the acquisition may bring contracts with distinct performance obligations that were not previously separated. That is a reporting question and a forecasting question at the same time, because the timing of recognized revenue affects how the business looks against plan.

Keep the investor narrative short and tied to the numbers. A page of commentary that explains variances in plain language is worth more than a longer document that restates the tables.

Test the package before it goes out. Hand the draft to someone outside finance and ask them to find the answer to one of the board’s standing questions. If they need help, the layout is doing too much work and the reader is doing too little.

Leaving controls and close discipline for later

Integration is the moment when control gaps get expensive. Two approval hierarchies become one, and the interim period is exactly when people are unsure who can sign what. That uncertainty is where errors and, occasionally, fraud live.

The mistake is assuming the buyer’s controls automatically extend to the acquired entity. They extend on paper. In practice, the acquired team may not have access to the same systems, may not know the new thresholds, and may keep using local workarounds because they work.

Walk through the transaction cycle end to end in the first weeks. Who approves a purchase, who releases payment, who reconciles the bank account, who reviews the reconciliation. If any answer is « we are still figuring that out, » that is the priority.

Close discipline matters for the same reason. A combined close that takes longer than either legacy close is a warning sign. Track the number of days to close and the number of adjusting entries after the preliminary close. Both should improve, and if they do not, the integration plan is not working.

Use a simple readiness list to keep this visible:

• Approval thresholds documented and communicated to both teams
• Bank access and payment authority updated for the combined entity
• Reconciliation ownership assigned for every material account
• Close calendar published with named owners for each step
• Adjusting entries reviewed for patterns, not just corrected

None of this guarantees a clean audit, and it is not meant to. The point is to remove the ambiguity that makes ordinary mistakes more likely.

Pay attention to the accounts that only exist because of the transaction. Goodwill, intangibles, and any purchase accounting adjustments need an owner who understands how they will be tested later. If nobody can explain how an opening balance was derived, that gap will surface at the worst possible time.

Confusing the interim role with the permanent hire

An interim CFO and a permanent CFO do different jobs, and treating them as interchangeable creates problems on both ends. The interim lead is there to stabilize, decide, and hand off. The permanent hire is there to run the function for years.

The mistake is hiring an interim CFO who is really looking for the permanent role, or hiring one who has no interest in building something that outlasts them. Both create distortions. The first may shape decisions around their own candidacy. The second may leave documentation thin because they never planned to be around for the consequences.

Be explicit about the handoff from the start. What will exist when the interim engagement ends? A documented close process, a working cash forecast, a reporting package with defined metrics, and a list of open items with owners. Those are deliverables, interim chief financial officer not aspirations.

Involve the permanent hire before they start, if you can. A week of overlap is worth more than a month of written notes, because the questions a new CFO asks reveal what the documentation missed.

If the permanent search will take a while, say so. An interim CFO who knows the timeline can sequence the work sensibly, front-loading the decisions that need their authority and deferring the ones that can wait for a permanent owner.

Write the handoff as a list of things a new finance lead could pick up without a conversation. Process notes, metric definitions, and the reasoning behind the major decisions. The test is simple: could someone who was not in the room follow the logic six months from now?

Measuring progress by activity instead of readiness

Integration updates tend to report activity: meetings held, systems mapped, policies drafted. None of that tells you whether the finance function is actually ready for the next period close or the next board meeting.

Measure readiness instead. Can you produce a consolidated close on schedule? Can you explain the variance to plan in the acquired business? Can you state your cash position and the next four weeks of commitments without a scramble? Those are yes-or-no questions, and the answers are more informative than a status color.

Pick a small set of indicators and keep them stable. Changing what you measure every month makes trends invisible.

Review these with the interim CFO on a fixed cadence and write down what changed. A short written record makes the handoff easier and gives the permanent hire a starting point.

Resist the urge to declare victory early. The first clean close after an acquisition is encouraging, and it is also the easiest one, because the integration work is still fresh in everyone’s memory. The second and third closes tell you more.

Scope shifts by company stage and sector

The same title covers very different work depending on where the company is. A buyer integrating a small bolt-on needs consolidation and reporting discipline. A buyer absorbing a business of similar size needs a full integration program, including systems, controls, and people.

Sector changes the emphasis too. A software company will spend more time on revenue recognition and deferred revenue. A manufacturer will spend more time on inventory valuation, standard costs, and working capital. A services business will focus on utilization, billing, and collections. The interim CFO’s first task is to identify which of these dominates.

Company stage matters as much as sector. A company that has never had a formal FP&A function will need one built. A company with an established function needs it merged. Those are different projects with different timelines.

Ask the interim CFO to state, in writing, which parts of the mandate are standard for the situation and which are specific to your company. That distinction helps you judge whether the plan is realistic or generic.

Where the scope is uncertain, say so and set a checkpoint. It is better to revisit the mandate after the first close than to pretend the original plan still fits.

Consider how the transaction was financed, because that shapes the finance work as much as the sector does. A debt-funded deal brings covenant reporting and lender questions into the first weeks. An equity-funded deal shifts attention toward investor reporting and the story behind the numbers. Either way, the interim CFO should know which audience is watching before the first close.

What to confirm with a professional before deciding

Before you commit to an interim CFO engagement for post-acquisition integration, get clear answers on a short list of points. The answers tell you whether the person and the mandate fit the work.

1. Which decisions will the interim CFO own, and which stay with the operating leadership?
2. What will exist at the end of the engagement that does not exist now?
3. How will the cash forecast be rebuilt, and on what cadence will it be reviewed?
4. Which reporting metrics will be standardized, and under which accounting definitions?
5. How will the handoff to a permanent finance lead be structured and timed?
6. What are the first three integration items, and who owns each one?

Ask for the answers in writing, even if they are brief. A written mandate is easier to adjust than a verbal understanding, and it gives both sides a reference point when the situation changes.

Confirm the boundaries as well. An interim CFO working on integration is not the same as an Interim chief financial officer CFO running the whole finance function, and the difference affects how much of your team’s time the engagement will consume.

Finally, decide in advance how you will judge whether the engagement is working. Pick two or three readiness questions from the list above, agree on when you will ask them, and let the answers guide the next decision. Preparation does not guarantee a particular outcome, and it does make the questions easier to answer when they come up.