About napoleonshacke

Interim CFO during a merger: what the mandate needs

Hiring an interim CFO during a merger without defining the mandate first is the mistake that creates the most friction. The new leader arrives with general authority but no clear boundaries, which means decisions pile up waiting for approval that was never assigned, or get made in a vacuum that creates problems later. Spelling out the mandate before day one prevents that gap and gives everyone a shared reference for what the interim is expected to handle and what stays with the board or existing leadership.

Starting without a written scope and decision rights

The most common version of this mistake looks innocent: leadership says the interim CFO will ”handle finance” during the merger and assumes that is enough. It never is. The interim shows up and faces a list of questions with no obvious answers. Should they approve vendor contracts above a certain amount? Can they sign off on hiring decisions that affect the budget? Do they have authority to pause a payment or change a process, or does everything still route through the CEO or owner?

The fix is a written scope that answers those questions before the engagement begins. A simple document that names the areas the interim owns outright, the areas that need approval before action, and the areas that stay with existing leadership or the board keeps everyone aligned. For a merger, that document should also name who can commit the company to terms with the other party and who reviews agreements before signature.

This matters because interim leaders move fast. They are not waiting for a months-long onboarding process. If the decision map is not in writing, they will either slow down to ask constantly or move ahead without asking and create friction either way.

A practical way to build this is to start from the specific work the merger requires in the first thirty days. List the decisions that work will surface, then assign each one to a role, not a name. That way the document holds up even as people shift.

Scope documents also protect the organization after the interim leaves. A new permanent CFO can read the document and understand exactly what the interim was authorized to do and where the boundaries sat.

Treating the interim as a temporary visitor instead of a decision-maker

Some organizations hire an interim and then subtly treat them as an outsider who should advise but not decide. The CFO title suggests authority, but the day-to-day behavior tells a different story. The interim is included in meetings but not asked for a position. Recommendations go to the CEO or board for approval when the scope said the interim would handle that area. This creates second-guessing, slow decisions, and an interim who stops investing in the work because their judgment is not being used.

The correction starts with how leadership introduces the interim to the organization. When the announcement email or meeting frames the person as an advisor or consultant, it sets the wrong tone before they walk in the door. The language should match the authority in the written scope: this person can make these decisions and will be making them.

Beyond the introduction, check in after the first two weeks to ask whether the interim is actually operating with decision authority. Are recommendations being routed through unnecessary approvals? Are people waiting for the CEO to confirm what the interim already said? If so, the scope may need to be restated to the team, or leadership needs to examine whether the scope they wrote matches what they actually want.

Interim leaders are most useful when they are free to act on the work they were hired to do. Treating them as a temporary visitor whose judgment requires validation undermines the value of bringing them in at all.

Assuming the interim has full financial authority

Boards and owners sometimes hire an interim and then treat every financial decision as if it now belongs to that person. That is rarely the intent, but without explicit language it is the practical effect. The interim may sign contracts, approve expenditures, or make commitments that bind the company beyond their tenure, and the board finds out after the fact.

The correction is to set approval thresholds in writing from the start. Define the dollar amounts at which the interim can approve independently, amounts that need the CEO or CFO co-sign, and amounts that need board or owner approval. For a company in merger discussions, those thresholds should be lower than they might be during normal operations, because transaction-related commitments carry exposure that routine spending does not.

This does not mean the interim operates in a box. It means the organization has thought through where judgment calls belong and has communicated that clearly. The interim can still raise issues, propose options, and push back on decisions they disagree with, but the approval path is known in advance.

Make the thresholds visible to the interim and to the board simultaneously. A shared understanding at the beginning prevents awkward conversations midway through.

Overlooking financial systems access and data continuity

An interim CFO who cannot get into the accounting system, generate reports, or access historical data is effectively blocked from doing the job for the first days or weeks. This sounds obvious, but organizations routinely underestimate the steps required to grant appropriate access to someone who is not a permanent employee. IT policies, single-sign-on configurations, and licensing restrictions can all create delays that eat into the first thirty days.

Before the interim’s first day, someone should have mapped out which systems they need access to and confirmed that access has been granted or requested. This includes the general ledger, billing systems, payroll, treasury, investor reporting platforms, and any data rooms used for the transaction. For each system, clarify whether the interim gets full admin access or a more limited view, and document that in the scope.

Beyond access, the interim needs a data handoff on the current state. Who maintains the financial model? Where are the bank reconciliations stored? What is the status of the last audit? If the organization uses an external bookkeeper or accounting firm, who is the contact and what are the arrangements? These questions have answers that someone in the organization knows. A structured briefing on the first day saves the interim from discovering gaps in the middle of transaction work.

The practical check is simple: ask the interim in the second week whether they can run any report they need without asking someone else to do it for them. If the answer is no, that is a gap to close before it slows down critical work.

Skipping knowledge transfer until the end

Organizations often think about the handover only when the interim is about to leave. That is the wrong time to start. By then, the interim has built relationships, made calls, and developed context that no document captures fully. The permanent hire arrives to a pile of notes and a list of open questions with no one to answer them confidently.

The better approach starts in the first week. The interim should begin documenting decisions, rationale, and open items from day one. Not a formal manual, but a running record that a new person could read and understand what happened and why. This is especially important during a merger, where the permanent CFO will need to understand not just the numbers but the negotiations, the sensitivities, and the assumptions that shaped them.

Ask the interim to maintain a simple log: what was decided, who made the call, what information drove it, and what is still open. That log becomes the primary handover document and the reference point for the permanent leader.

The interim benefits from this too. A written record forces clarity on their own thinking and protects them if a decision is questioned later.

No defined process for resolving disagreements with existing leadership

During a merger, the interim CFO and the existing CEO or remaining leadership will not always agree. The interim may have a different view on risk tolerance, spending priorities, or the pace of the transaction. Without a defined way to work through those disagreements, they either escalate into friction or get buried until they surface as bigger problems.

The correction is to establish the process in the mandate document. Name who makes the final call when the interim and the CEO disagree on a matter within the interim’s scope. Name what happens when the disagreement is about something outside the interim’s scope but still affects the transaction or the business. This is not about creating bureaucracy; it is about making the process visible so that disagreements get resolved on the merits rather than through awkward power dynamics.

In practice, most disagreements during a merger come down to timing, risk, or information. The interim’s job often involves surfacing information that existing leadership may not have been tracking in the same way. A healthy disagreement process lets that information land without the conversation turning personal or positional.

When a disagreement does arise, document the issue, the positions, and the resolution. That record helps the permanent CFO understand not just what was decided but why, especially for decisions made under time pressure during the transaction process.

Letting transaction work crowd out operational stability

Mergers create intense pressure to focus on deal-related finance: models, diligence, term sheets. An interim that spends all their time on transaction work while the billing cycle breaks down or the payroll team loses its only person is not serving the organization, even if they are doing exactly what felt urgent.

The correction is to map both tracks explicitly. Name the transaction deliverables and their deadlines. Name the operational finance work that keeps the business running and assign accountability for each piece. If the existing team is thin, the interim may need to step into operational gaps or arrange temporary coverage.

This is where the mandate document becomes a living reference. When everything feels urgent, the written priorities keep the work from drifting entirely into transaction mode.

A practical check: review operational finance health weekly even during heavy transaction periods. If cash management has slipped, if invoices are going out late, or if a key reconciliation has not happened, that is a signal to redistribute attention before it becomes a problem.

Failing to establish investor reporting cadence early

Organizations in merger discussions often have investors or lenders who expect regular updates. If the interim arrives and investor reporting falls into irregular patterns, trust erodes even when the underlying numbers are sound. An investor who stops hearing regularly will assume something is wrong and push for information in ways that distract from the work.

The interim should understand the existing reporting schedule and expectations before they begin. If there is no schedule, they should propose one. A simple monthly dashboard with cash position, key metrics, and a brief narrative covers more ground than a long report that only gets produced occasionally.

Mergers add complexity because reporting now has to cover both sides of the transaction and the combined view. The interim is well positioned to design a reporting structure that works for the transaction period and can scale to ongoing operations.

If the company uses external platforms for investor reporting, confirm access and accuracy in the first two weeks. Problems with data feeding into those platforms are easier to fix early than they are to explain away later.

Not addressing internal control gaps proactively

Leadership transitions and mergers both expose control weaknesses that may have gone unnoticed. An interim who focuses purely on strategic finance without understanding the control environment is setting up the permanent leader to discover problems the hard way.

The mandate should include a control assessment. Not a full audit, but a practical review of who approves payments, how journal entries get made, who has access to financial systems, and how discrepancies surface. The interim can do this with the existing team in a few days and produce a short list of gaps and what to do about them.

For companies with investor or lender relationships, this matters for covenant compliance and for the due diligence process itself. The other party’s team will look at controls, and having already assessed them shows preparedness.

If the company operates under standards like ASC 606 for revenue recognition, the interim Cfo responsibilities needs to understand how those are being applied and documented. Revenue recognition under ASC 606 requires consistent treatment and clear documentation, and a gap there is harder to explain than to fix proactively.

Leaving handoff to chance instead of structuring it

The most costly version of this mistake is the quiet one. The interim wraps up, the permanent CFO arrives, and there is no structured transfer of context. The new leader operates from incomplete information and starts making calls that contradict decisions the interim made without realizing it. Relationships with the board, lenders, or the other party’s team reset, sometimes to the company’s disadvantage.

A structured handoff includes at minimum a transition meeting with the board or owners, a briefing on open items and their status, a review of the decision log with the permanent leader, and a documented understanding of what happens next on the transaction work. This meeting should not be a surprise. Schedule it in the final weeks and prepare materials in advance.

The interim should also brief the existing finance team on the transition plan so they are not caught in the middle of conflicting expectations. The people who do the daily work know things that neither the interim nor the permanent leader will learn from a document.

A handoff that feels complete to the person leaving and is genuinely incomplete to the person arriving is the most common and the most costly. The only way to close that gap is to design the handoff with the new person’s needs in mind, not the interim’s comfort.

How to check whether the mandate is working

A written mandate and clear decision rights only deliver value if they actually shape how the engagement runs. Teams that skip the check often discover the gaps only when something goes wrong, interim chief financial officer which in a merger context can mean a decision made without authority, a commitment that surprises the board, or a handoff that leaves the permanent leader starting from zero.

The most useful check is a thirty-day review with the interim, the CEO, and a board representative if applicable. Ask three questions: Are the written decision rights reflecting what is actually happening? Are there decisions surfacing that the scope does not cover? Is the knowledge transfer log being maintained and will it be useful for the permanent leader? If the answer to any of those is unclear, the mandate needs adjustment.

A practical symptom to watch: if the interim is frequently asking for approval on items the scope said they could decide, or if people are going around the interim to the CEO, the written authority and the actual authority are out of sync. Address that directly rather than letting it erode trust on both sides.

The mandate is not a one-time deliverable. It is a reference document that should be reviewed and updated as the merger progresses and as the permanent CFO transition comes into view. An interim who updates the scope as priorities shift is doing the organization a favor, even if it feels like extra work in the moment.