An interim CFO during acquisition integration should own the financial coordination the company needs, while the CEO and deal leaders retain decisions that belong to them. The dividing line is authority: the interim leader can organize forecasts, reporting, and finance routines, but should not inherit open-ended control over operating or transaction choices. Put that boundary in writing before the integration work starts.
Define the mandate around integration decisions
Start by naming the financial work that is blocked, not by listing every task a CFO might perform. During an acquisition integration, the immediate need may be a reliable view of cash across both businesses, a common reporting calendar, or a clear process for approving spending. The mandate should connect each priority to a decision someone needs to make.
Use a short written scope that says what the interim CFO will deliver, who will use it, and who has final authority. For example, the interim leader may prepare a combined cash forecast and identify differences between the companies’ assumptions, while the CEO and integration lead decide which operating plans to change. The distinction prevents analysis from quietly turning into approval power.
A commented checklist can make the scope easier to test before work begins:
- Business outcome: What financial question must become easier to answer?
- Deliverable: What report, forecast, control, or decision process will address it?
- Owner: Who supplies inputs, reviews the work, and makes the decision?
- Boundary: What stays with the CEO, board, deal team, or operating leader?
- Handoff: Who will maintain the work after the interim assignment ends?
Each item needs a real name or role, not a vague reference to "the business." If the operating team owns hiring plans, for instance, finance can show how those plans affect cash and budget, but the scope should say whether the CFO can approve a requisition or only flag its financial effect. The next question is whether that authority matches the company’s existing approval rules.
Integration work also varies with the deal and the businesses involved. A company combining similar operations may need consistent accounting definitions and a shared forecast. A business entering a new product line may need tighter review of inventory, deferred revenue, or customer commitments. These are examples of possible priorities, not a standard package; choose based on the transaction’s actual financial and operating risks.
Keep exclusions beside the responsibilities. If the interim CFO is not responsible for negotiating the purchase agreement, setting product strategy, or deciding which teams combine, say so. When a task sits between functions, assign a decision owner and a finance contributor. A mandate that makes these edges visible is easier to adjust than one that assumes everyone shares the same interpretation.
Separate preparation from the first integration decisions
Preparation is the work that lets the interim CFO make useful recommendations without mistaking incomplete records for settled facts. Before changing a forecast or reporting process, identify the systems, account definitions, close calendars, and approval paths each business uses. The purpose is not to standardize everything at once; it is to see where two sets of information cannot yet be compared safely.
Request a focused package from finance and operating leaders: the current cash view, recent management reporting, budget assumptions, significant customer or supplier commitments, and the integration plan’s financial dependencies. Ask who prepared each item and when its inputs were last checked. A spreadsheet without an owner or update routine is evidence to investigate, not automatically a reliable starting point.
Comment on the checklist as findings emerge. "Cash forecast received" is less useful than "forecast excludes the acquired company’s payroll account and uses a different date convention." That note tells the team what is missing and why the gap matters. It also separates confirmed information from a working assumption, which reduces the chance that an early draft becomes an accepted forecast by repetition.
Interview the people who create and use the numbers, not only the finance team. A sales leader may explain why booked revenue does not align with cash receipts; an operations manager may know that supplier terms differ between entities. These conversations help identify which discrepancies are timing, definition, temporary Cfo Services or control problems. Record the answer and its owner so finance does not have to rediscover the same context later.
Then sort the findings by decision urgency. An unresolved bank balance or near-term payment obligation may need attention before the next planning cycle, while a chart-of-accounts redesign can wait if current reporting supports the required decisions. Explain the trade-off: rushing integration can create false consistency, but leaving critical cash and approval gaps unattended can make routine operating choices harder.
The preparation phase should end with a shared view of what is known, what remains uncertain, and which choices are pending. The interim CFO can recommend the order of work, but the CEO or integration lead should confirm priorities that affect operating teams. That checkpoint keeps finance from treating its own work plan as the integration plan.
Set decision rights before the first recommendation
Decision rights determine whether the interim CFO advises, approves, or executes. Spell out the authority for forecast changes, budget transfers, hiring approvals, payment controls, accounting judgments, and investor updates. The right answer depends on the company’s governance and existing controls; the interim title alone does not grant authority over every finance or operating decision.
Use a simple responsibility map for recurring decisions. The CEO might approve changes to integration priorities, while the CFO prepares the financial impact and the relevant functional leader confirms operational assumptions. The board may retain approval over decisions reserved to it. If an existing policy already assigns an approver, the integration should not bypass it just because the team is moving quickly.
Write down thresholds or escalation conditions only when the company has approved them. Do not invent a spending limit to make the chart look precise. If there is no agreed threshold, identify the person who can set one and use the existing approval route until that decision is made. A documented gap is safer than an unofficial rule that staff may treat as binding.
Clarify how disagreements are resolved. If finance believes a synergy assumption is unsupported but the integration team wants to include it, the forecast should show the assumption and its status rather than burying the dispute. The executive responsible for the integration can decide whether to proceed with the plan; finance should make the cost, timing, and uncertainty visible.
Access also needs a boundary. An interim CFO may need access to bank information, payroll data, customer contracts, or board materials, but access should follow the company’s security and confidentiality practices. Assign a sponsor who can authorize what is needed, and agree how sensitive information will be stored and shared. This is especially important when the two businesses have different systems and permissions.
Review the authority map with the people who will use it, including finance staff and temporary cfo services operating leaders. Ask them to walk through a real pending decision: who prepares the numbers, who challenges the assumptions, who signs off, and where the decision is recorded. If the answer changes depending on who is in the room, the map is not ready to guide daily work.
Prioritize cash, working capital, and integration dependencies
Cash deserves an early place on the integration agenda because operating plans can look sound while their timing does not. The interim CFO should establish how each business tracks cash, which accounts and entities are included, and how forecasts reflect receipts, payroll, debt service, and major payments. The immediate deliverable is a view decision-makers can interpret, not a promise about future liquidity.
Bring the two forecasts together only after checking definitions and timing. One team may forecast invoices, another may forecast expected collections; a weekly view in one business may be compared with a monthly view in the other. Reconcile these differences or label them clearly. A combined total can be misleading if the underlying periods or assumptions do not match.
Working capital review should follow the operating reality of the businesses. Look at how customer payment patterns, supplier terms, inventory needs, and billing practices affect cash. Avoid assuming that a policy from one company will fit the other. A change to purchasing or collections may have operational consequences, so finance should quantify the trade-off and involve the leader who owns that process.
Connect integration milestones to their financial dependencies. A system migration may affect billing or payment processing; combining vendors may depend on contract terms; a planned team change may alter payroll timing. The CFO can maintain a dependency log with the owner, expected financial effect, and open question. This lets the integration lead see which items threaten the plan without turning the log into a substitute for execution.
When funding or lender discussions are active, separate a management forecast from any external case. Label assumptions, distinguish committed actions from proposals, and make clear which figures are preliminary. The interim CFO can prepare a consistent explanation of cash needs and integration costs, but should not imply that financing will be available or that a transaction outcome is assured.
Cash priorities will differ by company stage, sector, and transaction design. A business with recurring subscriptions may focus on collections, renewals, and deferred revenue; a company with physical goods may need close attention to inventory and supplier timing. These examples show why the CFO should ask how the business converts plans into cash, rather than import a generic integration checklist unchanged.
Connect finance routines to operating and investor reporting
Finance reporting is useful when it follows the decisions operating leaders actually make. Agree on a calendar for forecasts, close reviews, integration updates, and investor materials, then identify which figures each meeting needs. If a report arrives after the decision window, the team may rely on informal estimates even when finance has produced more careful information.
Standardize definitions before comparing performance across the businesses. Terms such as bookings, revenue, churn, backlog, or integration savings can mean different things in separate teams. Create a concise glossary, record the source for each measure, and flag definitions still under review. Where accounting treatment is involved, the finance team should confirm the relevant policy rather than resolve it by choosing the more convenient number.
Give each recurring report a named preparer and reviewer. The interim CFO may design the reporting pack and explain variances, while functional leaders own the operating inputs behind their forecasts. When an assumption changes, record who made the change and why. That trail helps the team tell a genuine business shift from a spreadsheet edit made to fit a target.
Investor updates need particular care during integration. Align the narrative with approved figures, distinguish actual results from forecasts, and coordinate review with the executives or board members responsible for external communication. The interim CFO can support accurate financial reporting, but should not independently announce a transaction, promise synergies, or present uncertain plans as achieved outcomes.
Use meeting routines to resolve questions, not just circulate slides. A useful review asks what changed since the prior forecast, which assumptions drove the difference, and whether an owner needs to act. Avoid turning every variance into an escalation. Some changes reflect timing or incomplete integration data; others may signal a decision that belongs with the CEO or integration lead.
Keep the reporting design proportionate. A small finance team may need a disciplined cash forecast and a short variance discussion more than a sophisticated dashboard. A larger or more complex integration may require separate views by entity, product, or region, provided each view has a clear user and reliable data source. Add detail when it changes a decision, not just because the systems can produce it.

Use the first 30 to 90 days to test the mandate
The first 30 to 90 days can be organized around evidence of progress rather than assumed financial results. Early work might establish a cash baseline, surface reporting gaps, clarify approvals, and agree on integration dependencies. These are deliverables the team can inspect; they do not guarantee savings, growth, financing, or temporary cfo services a successful transaction.
Set a baseline for each priority before judging whether work has improved it. For a forecast, note which entities and accounts it covers, the update cadence, and unresolved inputs. For reporting, record which measures have agreed definitions and which remain provisional. Without a baseline, later reviews can confuse a cleaner presentation with better underlying information.
Choose progress signals that the responsible team can verify. Examples include whether forecast owners submit inputs on the agreed cadence, whether material assumptions have named owners, whether the approval map is being followed, and whether open integration dependencies have a decision owner. A signal should reveal a process condition, not disguise an outcome the interim CFO cannot control.
Review the mandate with the CEO and integration lead as facts change. A newly discovered financing constraint or a delayed systems migration can shift the order of work. Update the priorities and explain what will move later as a result. Do not add responsibilities informally while leaving the original deliverables unchanged; that creates an overloaded assignment and makes progress difficult to assess fairly.
Use a status note that distinguishes completed work, decisions made, open questions, and risks. Keep estimates labeled as estimates and show which assumptions could change them. If executives disagree about a forecast, record the disagreement and the decision owner rather than smoothing it into a single figure for convenience. Clarity about uncertainty is part of useful finance work.
At each review, ask whether the interim CFO is working at the right level. If most time goes to entering data, investigate whether the team lacks capacity, system access, or a clear operating owner. If recommendations are waiting for executive decisions, the bottleneck may be authority rather than analysis. Adjusting the role requires identifying that cause, not simply asking for faster delivery.
Plan knowledge transfer while the work is being built
Knowledge transfer should be designed into the assignment from the start, because a forecast or reporting pack is only durable if someone inside the company can maintain it. Name the permanent owner for each recurring deliverable, even if that person is not ready to take it over yet. The interim CFO can then build the process around the skills, access, and time that owner will have.
Document how key numbers are produced, not just where files are saved. A handoff should explain source systems, definitions, timing assumptions, review steps, and known limitations. For a cash forecast, that may include who confirms payroll timing, where collection assumptions come from, and how unusual payments are escalated. A spreadsheet with formulas but no operating context is a fragile handoff.
Have the future owner participate in preparation and review. They can first observe the process, then prepare a portion, and eventually lead the routine while the interim CFO checks exceptions. The pace depends on the person and the complexity of the work; the aim is demonstrated ownership, not a calendar-driven transfer that leaves the company exposed.
Keep a decision log for choices that shaped the integration model or finance process. Record the decision, its owner, the assumptions considered, and any condition that would prompt a review. This is not a transcript of every conversation. It preserves the reasoning behind important choices so the next finance leader can distinguish intentional policy from a temporary cfo services workaround.
Before the assignment ends, review access, open items, reporting commitments, and control responsibilities with the permanent owner and executive sponsor. Confirm who will update each deliverable and who can approve changes. If a task has no successor, identify that gap early enough for leadership to decide whether to reassign it, simplify it, or leave it pending with a named owner.
A clean handoff also includes limits. Point out estimates that remain uncertain, reconciliation items that have not been resolved, and processes that still depend on manual work. Avoid presenting a work-in-progress as a finished control. The permanent leader needs an honest map of what is reliable, what needs attention, and which decisions still belong to executives or the board.
Avoid the costly mistake of leaving authority ambiguous
The most costly mistake is letting responsibility expand while decision rights remain vague. The interim CFO may be held accountable for cash visibility without access to operating inputs, asked to enforce controls without authority to stop a payment, or expected to deliver integration savings without control over the teams making those changes. The result is friction and a misleading sense that finance owns the outcome.
Avoid that mismatch with a written mandate reviewed by the CEO, integration lead, and relevant finance or operating owners. For every major deliverable, identify the person who supplies information, the person who reviews it, and the person who decides. Mark exceptions that require board or lender involvement. If the company cannot agree on an owner, treat that as an unresolved governance issue rather than assigning it silently to the interim CFO.
Test the arrangement against a live decision before relying on it. Use a pending budget change, a forecast assumption, or a payment approval. Ask the participants to follow the documented path. If someone believes the interim CFO can approve while another person expects only a recommendation, correct the scope and communicate the change to everyone affected.
Revisit the map when the transaction moves into a new phase or the permanent finance leader arrives. Some responsibilities may transfer, while others may return to the CEO or operating team. Make the transition explicit, including who can change forecasts, issue reports, and maintain controls. An interim assignment should end with less ambiguity than it began with, even if some business uncertainties remain.
Use a practical go-forward test: can each finance deliverable be traced to a decision, a responsible owner, and a known limit? If not, narrow or clarify the mandate before adding another report or meeting. That discipline will not settle every integration question, but it makes clear who can answer the next one and what evidence the decision should rely on.