Interim CFO financial systems after merger: set roles

Interim CFO financial systems after merger work best when one person owns the transition plan, each finance decision has a named approver, and reporting routines connect the combined business to reliable records. Set those roles before changing processes. This matters when a leadership vacancy overlaps with integration work, financing discussions, or a transaction, because unclear authority can leave operating teams unsure which numbers or instructions to follow.

Define the mandate before assigning authority

Write the interim CFO’s mandate in terms of decisions and deliverables, not a broad instruction to “integrate finance.” A merger can create competing priorities: keeping the close on schedule, understanding cash needs, aligning budgets, and answering questions from owners or lenders. The mandate should say which of these matters the interim leader owns, which they coordinate, and which remain with the CEO, board, or functional leaders.

Start with the reason for the appointment. If the immediate need is a finance leadership vacancy, continuity of reporting may come first. If management is combining operations, the mandate may center on shared definitions, systems access, and a common forecast. For a financing or sale process, the team may need dependable support for reported figures and clear responsibility for responding to diligence requests. These situations can overlap, but the order of work should reflect the actual constraint.

Specify what the interim CFO can approve without additional consent. That may include routine finance procedures or forecast assumptions within agreed boundaries. Separately name decisions that require the CEO, board, lenders, or another designated approver, such as changes to capital commitments or the treatment of a material accounting issue. A title alone does not establish authority, and informal expectations can conflict once a decision affects more than one legacy business.

Ask the executive team to review the mandate together. Identify who sets operating targets, who approves spending, who communicates with investors, and who resolves disagreements over the numbers. If a business unit leader owns a forecast input but the interim CFO owns the consolidated forecast, say how changes move between them. A short written decision-rights record gives employees a reference when two leaders give different instructions.

Make the scope adjustable, but not vague. The company’s stage, sector, reporting requirements, and current systems affect what the interim leader can reasonably take on. A smaller operation may need hands-on oversight of payables and close routines; a more established company may need coordination among finance teams and control owners. Set a regular point to review priorities, then document any change to ownership or approvals before teams begin following it.

Map the people, systems, and reporting routines

Map who creates, reviews, approves, and receives each important financial output. The interim CFO needs to know not only which software holds a number, but also who enters it, what source supports it, and what decision depends on it. Begin with the close, cash reporting, budgeting, and investor updates, then add operational routines where a financial result changes hands between the legacy organizations.

A practical map can be a simple table, but each row should name an owner and a backup. Include the source system, the control or review step, the reporting destination, and the person who can authorize a correction. If the same employee both prepares and approves a payment, note the arrangement and identify whether another review exists. The purpose is to see how work actually moves, rather than to assume that an organization chart describes the process.

Compare the two businesses’ definitions before combining reports. They may use the same label for different things, such as revenue timing, customer status, project costs, or a department’s budget. They may also use different labels for similar activities. Check the underlying detail in the ledgers, contracts, invoices, and operating records before deciding whether a line can be mapped directly or needs a reconciliation note.

Trace a few important items end to end. For a cash receipt, follow the customer payment through bank activity, accounting entry, and the cash forecast. For a payroll expense, see how the source file becomes a ledger entry and then a department result. These checks reveal whether the records support the management view, whether review steps happen on time, and where the combined process depends on one person’s memory.

Keep a list of differences that need a decision, not just a software migration. Some differences reflect a real business choice; others are coding or timing inconsistencies. Assign a decision owner and a date for each open item, with the interim CFO responsible for escalation where appropriate. Until a definition is agreed, preserve enough detail to show how each legacy figure was produced instead of silently forcing it into a combined category.

Set a sequenced plan for the first 30 to 90 days

Prioritize continuity first, visibility second, and redesign only where the facts support it. The first 30 to 90 days are a planning window, not a promise that every integration issue will be resolved. A useful plan gives operating leaders a stable way to report, lets decision-makers see cash and performance on a consistent basis, and leaves room to investigate differences before changing controls or systems.

Put the work in order so that later decisions use dependable inputs:

1. Confirm access, approval authority, close responsibilities, payment controls, and reporting deadlines.
2. Check the cash position, forecast assumptions, major obligations, and near-term funding decisions.
3. Reconcile key management measures to the underlying accounting and operating records.
4. Agree on shared definitions, owners, and a reporting calendar for the combined business.
5. Document unresolved differences, decisions required, and the person responsible for each.

Each step should produce something people can use. Examples include a close calendar with named reviewers, a cash forecast with visible assumptions, a list of reconciled reporting categories, or a decision log that records unresolved accounting questions. Avoid defining progress as “integration complete” when teams cannot point to a working output or explain who maintains it after the interim Chief financial officer leader leaves.

The order may change with the situation. A company facing an urgent liquidity decision should not wait for a perfect chart of accounts before improving its cash view. A business with stable cash but inconsistent reporting may first need to reconcile definitions and sources. The interim CFO should explain the trade-off to the executive sponsor, including what work will wait and what risk remains while the priority is addressed.

Review the plan with operating leaders, not only the finance team. A new reporting deadline can affect sales, purchasing, payroll, and production routines. Ask whether each owner can supply the needed information in time and in a form that can be checked. If not, adjust the process or make the constraint visible; do not treat a missed input as a finance-only problem when its source sits elsewhere in the business.

Give the combined team one usable cash forecast

A combined cash forecast is useful when its owners can explain the timing assumptions behind inflows and outflows. The interim CFO should set who submits each input, who checks it, how often it is updated, and who acts when the projected position changes. A single total without these details can conceal differences between the two businesses and make it hard to connect a forecast change to an operating decision.

Separate known commitments from estimates. Payroll, scheduled debt payments, and contracted obligations may have records that support their timing, while customer receipts or supplier payments can depend on collection patterns, delivery milestones, or unresolved terms. Mark the source and confidence of each material assumption. Where the two legacy teams use different methods, preserve the distinction long enough to compare them rather than blending inputs without explanation.

Ask operating owners about the events that move cash. Sales leaders can explain the timing between bookings, delivery, invoicing, and collection. Procurement or operations can identify deposits, inventory purchases, and supplier terms. Finance then checks those explanations against transaction history and current records. The purpose is not to treat one department’s estimate as fact, but to make assumptions visible and assign someone to update them when circumstances change.

Connect the forecast to a decision threshold that management has chosen. For example, leaders may agree that a forecasted shortfall, delayed collection, or unusually large payment needs prompt review. The interim CFO should not invent a threshold or imply that a chosen level guarantees safety. Record who receives the alert, who can approve a response, and what information must be checked before management changes spending or funding plans.

When the forecast and actual results differ, record why. A timing variance, an incorrect assumption, a missing invoice, and a change in business activity require different responses. Comparing the forecast with actual bank and ledger activity can reveal which inputs need better ownership. Keep the explanation concise enough for leaders to use in a meeting, with supporting detail available for finance staff who need to trace a specific item.

Connect budgets and investor reports to operating decisions

Budget ownership should follow the people who can explain and influence the underlying activity. The interim CFO can establish a common calendar and format, but operating leaders should confirm their assumptions and own the actions tied to them. If one legacy team uses a different cost structure or planning cycle, document the difference before presenting a combined view as though both sides were built on the same basis.

Choose a small set of measures that support actual decisions. A useful report might show a financial result beside the operational driver that explains it, such as recognized revenue alongside delivery status or labor cost alongside staffing plans. The right pairing varies by sector and business model. If a measure has no clear owner or source, it is not ready to carry the same weight as a reconciled figure.

Investor reporting needs a clear review path. Identify who drafts the report, who confirms accounting figures, who approves explanations, and who is authorized to send it. Keep reported results separate from forecasts and label assumptions plainly. If an investor asks about a variance, the answer should trace back to a record and a named owner, rather than rely on a confident summary that cannot be checked.

Align the reporting calendar with the operating cadence. A monthly finance package may arrive too late to support a decision that happens weekly, while a frequent operational dashboard may not be suitable for investor communication. Set different rhythms where needed and specify how the figures reconcile. Explain which data is preliminary, which has passed review, and what change in the close or operating process could alter a previously shared view.

Budget changes should leave a record of who requested them and why. A transfer between departments, an added commitment, or a revised revenue assumption can affect multiple reports. The interim CFO can define the route for those changes and ensure that approvals match the mandate. This keeps the combined budget useful as a management tool without suggesting that a plan is a guarantee of financial performance.

Preserve controls while making changes

Keep critical controls in place while the combined team changes systems, roles, or reporting definitions. A merger can make an established control unclear if the person who reviewed a transaction has moved roles or if one company’s process is being retired. The interim CFO should identify the control owner, evidence of review, and escalation route before changing a workflow that protects cash, reporting accuracy, or access to sensitive records.

Focus first on processes where an error could be difficult to detect or correct. These often include payment setup and approval, journal entries, access to accounting systems, reconciliations, and changes to customer or supplier records. The specific risks depend on how the company operates. A checklist should prompt investigation, not imply that every business has the same exposure or that one standard process fits all.

Where staffing is limited, separate preparation from approval where practical. If one person must perform more than one step, identify a compensating review and the evidence it leaves. A review that exists only in conversation may be hard for another leader to verify later. Record who performed it, what they checked, and how an exception was resolved, using a process employees can follow without creating unnecessary administrative work.

Do not combine data or retire a legacy process until the team can explain what its records contain and how they reconcile. Preserve the source detail needed to answer later questions about balances, transactions, or reporting changes. If a new chart or system cannot represent an old category cleanly, keep a mapping and reconciliation that shows the relationship. This is especially important when leadership, lenders, investors, or transaction parties need to understand how figures were assembled.

Escalate accounting questions to the appropriate internal or external reviewer when the treatment depends on facts the interim CFO cannot establish alone. For example, revenue timing may depend on contract terms and the company’s accounting framework, not on a desire to make the combined report easier to read. A documented question, relevant support, and a recorded decision are more useful than a quick mapping that obscures uncertainty.

Measure progress by evidence, not by promised outcomes

Assess progress by asking whether finance work is more traceable, timely, and clearly owned. Do not use a promised valuation, financing result, transaction close, or growth figure as a measure of the interim CFO’s performance. Those outcomes depend on factors beyond finance leadership. Instead, check whether decision-makers can obtain a supported cash view, understand material reporting differences, and identify who must resolve an open issue.

At each review, compare the agreed deliverables with evidence that they are in use. A calendar is useful when owners follow it. A forecast is useful when its assumptions have sources and someone updates them. A control is useful when its review leaves evidence. If a document exists but teams still rely on conflicting spreadsheets or informal approvals, treat that gap as unfinished work.

Use a concise status record with four fields: the deliverable, its owner, the evidence of completion, and the remaining dependency. Add a decision date when leaders need to choose between options. This format helps an executive sponsor distinguish a task that is blocked by a business decision from one that finance can complete independently. It also prevents a long activity list from making every item appear equally urgent.

Progress measures should fit the company’s stage and the reason for the appointment. A growing business may need more consistent budget ownership; a company preparing for a financing discussion may need a clearer trail from reported figures to supporting records. Neither situation calls for a universal score. Choose measures that show whether the finance routine supports the decisions the executive team actually needs to make.

When progress stalls, identify the source of the delay before adding more reporting. The bottleneck may be missing data, competing authority, a system limitation, or a decision that leadership has not made. The interim CFO can recommend a response, but should not silently absorb a decision reserved for the CEO or board. Record the consequence of waiting and the person who can resolve it.

Apply the role plan to a merger with a reporting gap

Consider a hypothetical company that has combined two businesses and needs to prepare consistent monthly reporting while its permanent finance leader is still being selected. The interim CFO’s first task is to clarify authority: the CEO approves material spending decisions, operating leaders own their submissions, and the interim CFO coordinates the close and consolidated forecast. These boundaries are written down before teams receive new instructions.

The finance map shows that both businesses can report revenue, but their teams classify some customer and delivery activity differently. Rather than force a single category immediately, the interim CFO assigns owners to reconcile the underlying records and documents which figures remain separate. The reporting package identifies the difference, while the executive team decides which management view it needs for the next planning cycle.

For cash planning, the sales and operations owners submit expected collections and major supplier commitments with supporting detail. Finance compares those inputs with bank activity, invoices, and the ledger. The forecast flags an expected timing gap as an assumption to investigate, not as a guaranteed shortfall. The CEO decides whether any spending response is appropriate under the company’s approval rules.

The handoff plan names the person who will maintain each routine after the interim CFO leaves. The permanent leader receives the reporting calendar, decision log, forecast assumptions, reconciliations, control owners, and unresolved questions. They also review a recent reporting cycle with the people who prepared it, so the process is demonstrated rather than handed over as a folder of files.

In this case, readiness means that leaders can explain the reports, trace important figures to records, and see who owns the next decision. It does not mean every legacy difference is settled or that a financing or sale will follow. If the team cannot reproduce a number or name its approver, keep that gap visible and assign a specific owner before treating the routine as transferred.