Why the First 72 Hours and the CFO’s Accountability Decide Success
Category: Interim Management | Finance | Controlling | Reading time: ca. 25 min
There is a moment in every interim mandate that decides everything else. Not the first meeting. Not the first reporting cycle. Not the first close.
It is the moment when an interim manager understands for the first time what is really going on.
Not what they were told. Not what was in the briefing. But what the numbers actually say, where the real risks lie, what hasn’t been working for weeks or months, and what must be addressed immediately.
This moment decides whether a mandate becomes successful or whether an interim manager spends weeks trying to make decisions based on assumptions.
The instrument that brings about this moment is no meeting and no workshop. It is a KPI dashboard built in the first 72 hours of a mandate that turns the moment when assumptions become facts into one of the most powerful leadership instruments an interim manager has.
This article explains how that concretely works, which KPIs are decisive in a finance and accounting mandate, and why all of this does not work without CFO accountability.
The Central Paradox of the Interim Mandate
A company brings in an interim manager because it has a problem requiring immediate attention. A leadership role is vacant, a close is going off the rails, an ERP migration is creating data chaos, an audit has produced findings that need to be resolved, or a team is overloaded and needs operational leadership.
The interim manager is supposed to deliver fast. That is the explicit expectation.
What almost always is missing is the precondition for fast delivery: transparency about the actual state of the organization.
In practice that means: the interim manager begins in an environment in which KPIs either don’t exist, are fragmented across various systems and Excel files, are defined differently by different people, or simply don’t correspond to what is needed to truly understand the state of the organization.
That is the central paradox of the interim mandate. The company expects immediate results and at the same time delivers no immediate transparency.
An experienced interim manager doesn’t solve this paradox through longer onboarding or more meetings. They solve it through the systematic building of a KPI dashboard that, in the first 72 hours, makes the most relevant facts visible.
The CFO Accountability: Why the Dashboard Doesn’t Work Without It
Here is an uncomfortable sentence: a KPI dashboard is only as good as the CFO’s willingness to take it seriously.
That sounds banal. It is not. In practice there is an astonishing number of situations in which an interim manager builds a dashboard, makes the right numbers visible, identifies the right risks, and then finds that the insights from it have no consequences. Because the CFO views the dashboard as a reporting instrument and not as a leadership instrument. Because they see the traffic lights and make no decisions. Because they perceive the escalations and don’t escalate.
In this scenario, the best dashboard is worthless.
What CFO accountability concretely means
The first responsibility of the CFO begins even before the start of the mandate. It consists of creating the preconditions for fast and effective dashboard build-up.
That means: ensuring system access before the interim manager begins. Instructing key persons in the team to give the interim manager full information access. Making clear that data collection has priority over the day-to-day. And signaling that the dashboard’s results are taken seriously.
When an interim manager finds in the first 48 hours that they have no system access, that people evade when they request data, or that no one knows where certain numbers can be found, that is no operational problem. It is a signal about CFO leadership. It shows that the organization’s transparency-readiness is low and that this is not actively demanded by the CFO.
The threshold decision as CFO task
The traffic-light logic of a dashboard is only effective if the thresholds defining when green turns yellow and yellow turns red are sensibly calibrated. This calibration is no technical task. It is a leadership decision.
A CFO who says “I don’t decide that, the interim manager decides that” hands over a leadership responsibility they cannot transfer. Because thresholds reflect risk appetite. How many days of close delay are acceptable before escalation? From what share of overdue payables must action be taken? How many open audit findings are tolerable?
These questions have no universal answers. They have company-specific answers that the CFO knows and must decide.
The willingness to escalate
The most critical element of CFO accountability is the willingness to react to escalations. A dashboard that shows red traffic lights and has no consequences becomes a farce within two to three weeks. The team learns that the red lights have no relevance. The interim manager learns that their diagnoses are not heard. And the dashboard degenerates into a reporting tool that no one takes seriously anymore.
The willingness to escalate does not mean intervening immediately at every red KPI. It means creating a framework in which escalations have a defined path and in which the CFO is reachable and decision-ready as the last escalation level.
This willingness must be visible. It must be communicated. And it must be confirmed through concrete action, not through promises.
The resource decision
A dashboard shows problems. Solving problems requires resources. The CFO decides about resources.
That is a trivial observation that regularly leads to problems in practice. An interim manager identifies a structural bottleneck. They recommend a measure that requires a certain investment, whether in technology, personnel, or external support. The CFO nods, postpones the decision, and two weeks later the situation is the same.
CFO accountability in the context of a KPI dashboard also means: making resource decisions quickly when the data justifies them. Not all decisions. But those driven by the dashboard.
The First Structural Diagnosis: What’s Missing When Controllers Prepare Closes
There is a constellation in finance organizations that at first glance functions and yet carries a structural risk. The closes come on time. The numbers add up. The auditors have no material objections. And yet something isn’t right.
This constellation arises when monthly closes are not prepared by GL accountants but by controllers.
That is more frequent in practice than it should be. Reasons are many: vacancies in accounting, grown structures in which the line between controlling and accounting was never clearly drawn, or a leadership decision that placed efficiency above role clarity.
The result is a finance organization that functions but is not optimally set up. And a risk that no KPI directly makes visible.
The different lens
A controller thinks in variances. They analyze why the result deviates from plan, what the drivers are, what that means for steering. That is their core competence and it is valuable.
A GL accountant thinks in transactions. They ask: Is this business event correctly recorded? Is the valuation rule-compliant? What tax implications does this booking have? Which changes in EStG, UStG, KStG, or GewStG (German tax law) are relevant since the last close and must be considered?
Those are fundamentally different ways of thinking. Both are necessary. But they are not interchangeable.
Where the gaps arise
The gaps that arise when controllers prepare closes are rarely visible at first glance. They arise not in the numbers that are there, but in the questions that are not asked.
The most critical question concerns ongoing tax currency. A GL accountant who deals daily with accounting and tax compliance has the current changes in tax law present in mind. They know which changes are relevant since the last close and how they affect valuations, provisions, or tax disclosure.
A controller who does not apply this expertise daily may not have it in the necessary depth. They will prepare the close on the same principles as always. They will make no obvious mistakes. But they may not consider changes they don’t even know about.
That is no accusation against controllers. It is a structural reality. Tax expertise ages when it is not continuously applied.
Concrete areas where these gaps can arise:
Changes in the valuation of provisions under tax discounting rules
Updates to the VAT treatment of certain service types, especially relevant in international structures
Changes in trade tax add-backs that affect the effective tax rate
New documentation duties or evidence requirements that become relevant in tax audits
Changes in the treatment of certain expense types under corporate tax law
What a KPI dashboard can deliver and what not
A KPI dashboard cannot directly measure these gaps. There is no KPI saying: tax currency 73 percent.
What the dashboard can deliver is indirect diagnosis. It shows patterns indicating structural weaknesses.
An above-average post-close booking rate can be an indicator. When corrections are regularly necessary after the closing, the question arises whether they are triggered by tax matters not considered when preparing the close.
A rising number of auditor questions about valuation decisions is another signal. When auditors regularly question the derivation of valuations, that can be a hint that the justifications are not at the current tax state.
Anomalies in the development of deferred taxes over multiple periods are a third indicator. When the movement of deferred taxes cannot be explained by known tax matters, that is a signal for possible gaps in tax treatment.
What CFOs must do
The CFO accountability in this constellation is clear and not delegable.
First: ask the question. Who in my organization has the tax currency necessary for preparing closes? This question is never explicitly asked in many organizations because the closes come on time and no one inquires about what exactly is behind them.
Second: establish role clarity. Closes should be prepared by GL accountants who keep their tax expertise continuously up to date. Controllers deliver the analysis and the business interpretation. The accounting and tax substance of the close belongs in the hands of professionals whose core competence is exactly that.
Third: ask the direct question. Not as control, but as leadership instrument: Which changes in EStG, UStG, KStG, and GewStG have you considered since the last close? What effects do they have on our balance sheet? The answer to this question is often more revealing than any dashboard.
An interim manager who finds in the first 72 hours that controllers prepare closes will make this constellation visible in the dashboard. Not as accusation, but as a structural finding requiring CFO attention.
Why the First 72 Hours Are Decisive
In the first three days of a mandate, the perception that the team and management have of the interim manager is fundamentally shaped. Whoever observes and asks in this phase without delivering loses momentum. Whoever in this phase acts without a data basis risks wrong priorities and thus loss of trust.
Whoever in this phase presents a structured picture of the situation, based on real data and clearly naming the most important risks and action fields, immediately gains credibility.
The 72-hour logic also applies for another reason: in the first three days, access to people, systems, and information is most open. Everyone wants to help the new interim manager, everyone answers questions, everyone is willing to invest time. This open phase ends quickly when the day-to-day moves back to the foreground. Whoever uses the first 72 hours to systematically collect and structure data exploits this time window optimally.
What a KPI Dashboard in the Interim Mandate Must Deliver
A KPI dashboard in the interim mandate has four specific functions that distinguish it from other reporting instruments.
Function 1: Immediate situational awareness
The dashboard must, in the first 72 hours, make the most important facts about the state of the finance organization visible. Not all facts, but the decisive ones. Where are the biggest risks? What doesn’t work? What burns immediately, what burns in three weeks, what is structural?
Function 2: Diagnosis instead of visualization
A dashboard is in the first weeks of a mandate primarily a diagnostic instrument. It shows not only what the numbers are, but what stands behind the numbers. Data breaks pointing to systemic problems. Inconsistencies suggesting missing process standards. Anomalies raising questions that must be answered.
Function 3: Create a common language
Interim mandates rarely fail due to lacking expertise. They often fail due to lacking alignment between departments, between hierarchy levels, between the interim manager and management. A dashboard creates a common language: same definitions, same numbers, same interpretation. It ends the discussion about which number is right and enables the discussion about what to do.
Function 4: Real-time risk management
In an interim mandate, risk management is not strategic; it is operational and immediate. A dashboard that defines critical thresholds and makes overruns immediately visible enables proactive action instead of reactive firefighting.
The Three-Level Architecture
Level 1: The management view
The management view is the top level of the dashboard. It is designed for the CFO, executive management, and the board. It shows the ten to fifteen most important KPIs in an overview that conveys the overall state of the finance organization at a glance.
This level is deliberately condensed. No CFO wants twenty pages of numbers. They want to know: green, yellow, or red? And if yellow or red: what is to be done?
The effectiveness of this level depends directly on how well the thresholds are defined. That is a CFO decision, not a technical question.
Level 2: The process view
The process view shows the state of the three central finance processes in a typical accounting mandate: order-to-cash, purchase-to-pay, and record-to-report. For each of these processes there are specific KPIs that show how well the process functions, where bottlenecks arise, and which risks are visible.
Level 3: The root-cause analysis
The lowest level is the most analytical. It shows not only what a deviation is, but why it arises. It is the working instrument of the interim manager themselves and documents the analysis steps, hypotheses, and conclusions leading to the recommendations on the higher levels.
The Concrete KPI Set for a GL Mandate
A general ledger mandate has specific KPI requirements that distinguish it from other finance mandates. The following describes the most important KPI categories and the concrete metrics relevant from day one in such a mandate.
Category 1: Closing metrics
Closing metrics measure the efficiency and quality of the month-end close process. They are in every accounting mandate the first priority because the close is the most important regular deliverable of the finance organization.
Days to Close
How many working days does the monthly close take from day 1 of the following month to completion? A benchmark for mid-sized companies lies at three to five working days. Anything beyond that signals structural inefficiencies that need to be analyzed.
Closing quality score
How many errors, post-closing entries, or corrections are there after the formal close? A high post-closing entry effort is an indicator of inadequate controls in the closing process. And a possible signal that the tax currency of the close-preparing persons is insufficient.
Task completion rate
What share of closing tasks is completed by the defined deadline? A low rate signals either unclear responsibilities, unrealistic timelines, or insufficient capacity.
Number of open reconciliations at the closing date
How many account reconciliations are still open at the time of the formal close? Every open reconciliation is a potential risk for close quality. In a well-set-up accounting team this number at the closing date should be zero or near zero.
Category 2: Account reconciliation and balance quality
Aged Items in Balance Sheet Accounts
How many positions in balance sheet accounts are older than 90 days, older than 180 days, older than one year? Old unresolved positions in balance sheet accounts are one of the surest signs of structural weaknesses in the accounting organization. In many mandates, the analysis of aged items is one of the first and most revealing activities.
Clearing rate on suspense accounts
What share of bookings on suspense accounts like GR/IR is cleared within 30 days? A low clearing rate on GR/IR accounts is a classic symptom for poor coordination between accounting and procurement or for systemic problems in invoice processing.
Manual booking rate
What share of bookings in the general ledger is performed manually? A high manual booking rate is a risk factor for errors and an indicator of insufficient automation. In a well-set-up system the share of manual bookings should be below 20 percent.
Journal entry review rate
What share of manual journal entries is reviewed and approved by a second person? A low review rate signals control weaknesses that will be flagged in the next audit.
Category 3: Accounts Payable
Days Payable Outstanding (DPO)
How many days pass on average between invoice receipt and payment? DPO is a primary liquidity KPI. Too low a DPO signals that payment terms are not optimally used. Too high a DPO signals payment delays that strain supplier relationships.
Invoice processing time
How many days pass between invoice receipt and booking? High processing time creates risks for cash discount losses, late fees, and untimely closes.
Cash discount rate
What share of available cash discounts is actually utilized? Cash discounts are risk-free returns. A low cash discount rate signals either slow invoice processing or missing systematic monitoring of payment terms.
Three-way-match rate
What share of incoming invoices is successfully matched against purchase order and goods receipt without manual intervention? The three-way-match rate is a direct indicator of the quality of system integration between procurement, goods receipt, and accounting.
Category 4: Accounts Receivable
Days Sales Outstanding (DSO)
How many days pass on average between invoicing and payment receipt? DSO is the central efficiency indicator for the AR process. A rising DSO signals problems in dunning, invoice quality, or customer relationships.
Receivables aging
How are open receivables distributed by age: under 30 days, 30 to 60 days, 60 to 90 days, over 90 days? A growing shift toward older receivables is an early warning signal for rising default risk.
Bad-debt provision rate
What share of receivables is provisioned? A rising bad-debt provision rate signals either deteriorated customer creditworthiness or overly optimistic receivable valuations in the past.
Category 5: Intercompany
For mandates in group structures, intercompany KPIs are indispensable. They are often the first indicators of structural problems in the finance organization.
Number of open intercompany differences
How many unresolved differences exist between entities? This number is a direct indicator of the quality of intercompany processes.
Average resolution time
How long does it take on average to resolve an intercompany difference? A high resolution time signals either unclear responsibilities, poor communication between entities, or missing systemic support.
Intercompany differences at the closing date
What is the total amount of unresolved intercompany differences at the time of the formal close? This KPI is a direct indicator of consolidation risk.
Category 6: Compliance and Controls
SOX/ICS compliance rate
What share of the defined controls is executed and documented on time and completely? A low compliance rate is a direct audit risk.
Number of open audit findings
How many findings from the last internal or external audit are still open? The trend of this number over time is more important than the absolute value.
Segregation of Duties Violations
How many cases exist in which persons have rights incompatible with their tasks? SoD violations are a classic audit finding ignored in many organizations until auditors escalate.
How the Dashboard Is Built in the First 72 Hours
Phase 1: Data collection (hours 1 to 24)
The first phase is fully dedicated to data collection. No analysis, no conclusions, no recommendations. Just collecting data.
That means: ensuring access to all relevant systems — ERP, BI tools, reporting platforms, and if necessary also Excel files. Conducting conversations with the key persons in the team. Not to gather opinions, but to understand what data exists, where it lies, and how reliable it is.
In this phase a key diagnostic result already shows: how hard is it to obtain the basic data? When simple KPIs like DPO or Days to Close aren’t available within hours, that itself is a finding. It signals missing data transparency as a structural problem.
Phase 2: Structuring and first analysis (hours 24 to 48)
In the second phase, the collected data is structured and first analyses are performed. The first dashboard will be incomplete. That is normal and no problem. An incomplete dashboard showing the most important available facts is more valuable than a complete dashboard ready in three weeks.
Phase 3: Presentation and calibration (hours 48 to 72)
The third phase is the presentation of the first dashboard state to the CFO and the calibration of thresholds and priorities based on their feedback.
This phase is decisive. It validates the data basis, establishes a common ground for communication, and sends a signal: this interim manager has, in 72 hours, created a structured picture of the situation. That builds trust that becomes capital in the following weeks.
A CFO who has no time in this phase sends a different signal. They signal that the dashboard is not a leadership instrument for them. That is the fastest way to undermine the value of an interim manager.
What Data Quality Reveals About the Organization
What data quality reveals about the organization is at least as valuable as the data itself.
In the first 72 hours of a mandate, an experienced interim manager makes the following observations that allow direct conclusions about the state of the finance organization.
When simple basic metrics aren’t available, a culture of data transparency is missing. When different people define the same metric differently, uniform standards are missing. When the data exists but is distributed across many different sources, an integrated reporting system is missing.
And when it is found that closes are prepared by controllers instead of GL accountants, that is also a data finding. Not via a KPI, but via the process structure. The consequence for the CFO is clear: this constellation requires their attention, no delegation decision.
What CFOs Can Expect from an Interim Manager with Dashboard Competence
An interim manager who builds and uses a professional KPI dashboard delivers to the CFO three concrete added values that go beyond operational performance.
First, they deliver transparency that didn’t exist before. The dashboard makes structural problems visible that without transparency are not addressable.
Second, they deliver a scalable foundation. A dashboard built in a mandate is still present after the end of the mandate. It is a lasting investment in the steering capability of the finance organization.
Third, they deliver a standard. In many finance organizations, a defined standard is missing for which KPIs should be regularly reported, how they are defined, and who is responsible for their maintenance. An interim manager who establishes this standard in their mandate leaves behind something that has effect beyond their engagement.
But none of these values unfolds without a CFO who treats the dashboard as a leadership instrument. Who defines thresholds. Who reacts to escalations. Who makes resource decisions when the data justifies them. And who invests the time to validate the first situation picture together with the interim manager in the first 72 hours.
A KPI dashboard is as good as the CFO standing behind it.
What I Bring
I am Nicole Vekonj, interim manager for finance & controlling. In every one of my mandates, building a structured KPI dashboard is one of the first activities. Not because it looks nice, but because it is the foundation for everything else.
My approach: in the first 72 hours, create a situation picture based on real data. Name the most important risks and action fields. And build a steering foundation that remains in the organization beyond the mandate.
That is no operational overhead. It is the precondition for operational work to be effective.
You are facing an interim mandate and want to ensure that the interim manager steers in a structured way from day one instead of navigating blindly?
Let’s talk for 30 minutes.
Nicole Vekonj | Interim Manager Finance & Controlling | zahlenkompetenz.de
