Toto smaže stránku "Interim CFO data governance responsibilities: who decides". Buďte si prosím jisti.
Interim CFO data governance responsibilities belong to whoever holds the pen on the numbers, and that is a decision the board or owner makes before the engagement starts. If the interim CFO owns the definitions, they also own the reconciliation and the sign-off. If they only advise, the permanent finance lead keeps that authority. The criterion is simple: decide whether you are buying a decision-maker or a reviewer, then write it down.
Start by separating decision rights from advisory input
Two different mandates get called the same thing in most conversations. One gives the interim CFO authority to approve a definition, lock a reporting calendar, or reject a number that does not reconcile. The other gives them a seat at the table and a strong opinion, but the permanent controller or finance director still signs. Both are legitimate. They produce very different engagements.
Before you interview anyone, write down which decisions currently stall. If month-end close keeps slipping because nobody will commit to a revenue recognition position, you need a decision-maker. If the numbers close on time and the problem is that nobody has time to build a forecast, you need capacity and judgment, not authority.
The distinction matters most in the first weeks. An interim CFO with decision rights will start changing definitions and calendars early, because that is the only way to make the close predictable. An advisor will document what exists and recommend changes, which is slower but leaves the permanent team owning the outcome.
Ask directly in the interview: which decisions would you expect to make alone, which would you bring to me, and which would you never touch? A candidate who cannot answer that cleanly will create friction later, usually at the worst moment, when a lender or an investor is asking for a number.
Put the answer in the engagement letter. Not a long legal document, just a short section listing the decisions the interim CFO owns, the ones they recommend on, and the ones that stay with the board or the owner. Review it after the first month, because the real boundary is usually different from the imagined one.
One more test before you commit: name the last three decisions that waited more than a week for a signature. If those decisions are the ones you want the interim CFO to take over, say so explicitly. If they are decisions you want to keep, say that too. Ambiguity here is what turns a six-month engagement into a series of small arguments.
Define what data governance means in your finance function
In a finance team, data governance is narrower than the phrase suggests. It covers who defines a metric, where the source of truth lives, who can change a definition, how changes get communicated, and who signs off before a number leaves the building. That is the whole scope. Everything else is a tool or a habit.
Most growing companies have this implicitly. The person who has been there longest decides what "net revenue" means, and everyone else adapts. It works until that person leaves, or until two reports use the same word for different things and a board member notices.
An interim CFO's job here is to make the implicit explicit without turning it into a project. A short definitions document, a named owner for each key metric, and a rule that changes get logged is usually enough. The value is not the document. It is that the next person can find the answer without asking around.
Be careful about scope creep. Data governance in finance touches the general ledger, the reporting layer, and whatever system feeds the forecast. It does not need to reach into every operational system in the company. If the interim CFO starts proposing a company-wide data program, that is a different mandate and a different budget.
One practical test: pick three metrics that appear in your investor or lender reporting. For each one, ask who owns the definition, where the number comes from, and what happens if it changes. If any of those three questions has no clear answer, that is the work.
Write the definitions in plain language, not in accounting shorthand. A definition that only the person who wrote it can interpret is not a control. It should be readable by a new hire, an auditor, or a buyer's analyst without a translation layer.
Map the records a transaction will actually require
Transaction readiness is mostly a records exercise. Buyers and lenders ask for the same categories of support again and again, and the companies that respond quickly are the ones that organized the files before anyone asked. The interim CFO's role is to know what will be requested and to check that it exists.
The categories are predictable. Historical financial statements, monthly management accounts, the general ledger and supporting schedules, revenue contracts and the accounting positions taken on them, payroll and benefits records, tax filings and correspondence, debt agreements and covenant calculations, Web site and the working capital detail behind the balance sheet.
Under ASC 606, revenue recognition deserves particular attention. If your contracts have variable consideration, multiple performance obligations, or significant judgment, the support behind those positions needs to be traceable. A buyer's accountant will ask how you got to the number, not just what the number is.
Quality of earnings work sits on top of this. It separates recurring from non-recurring items and tests whether the reported results reflect the underlying business. You do not need to run a full exercise yourself, but you should be able to explain any large adjustment without going back to rebuild it.
The interim CFO should walk the file room, physical or digital, before anyone else does. Gaps found internally are a scheduling problem. Gaps found during diligence are a credibility problem, and they cost you time you may not have.
Build the index before the request arrives. A single list of what exists, where it lives, and who maintains it turns a two-week scramble into a two-day response. The list itself is not the deliverable. The ability to answer a follow-up question in the same conversation is.
Set the reporting calendar and hold it
A reporting calendar is the backbone of everything else. It says what closes when, who prepares it, who reviews it, and when it goes out. Without one, every month is a negotiation, and the interim CFO spends their time chasing rather than analyzing.
Build it backward from the audience. If the board meets on a fixed date, the package is due a set number of days before. If a lender requires monthly compliance certificates, those have their own deadline. Work back from each external commitment to the internal close tasks.
Then decide what the close actually requires. A full close every month is expensive for a small team. Many growing companies run a lighter monthly close with a fuller quarterly one, as long as the monthly numbers are reliable enough for the decisions being made with them.
The interim CFO owns the calendar during the engagement, which means they own the escalation when something slips. That is a real authority and it should be stated. If a department head misses a deadline and nothing happens, the calendar is decorative.
Track two things: whether the close finished on the planned date, and how many adjustments came after the initial review. The first tells you about discipline. The second tells you about the quality of the underlying work, which is the part that matters to a buyer.
Publish the calendar where the whole team can see it, not in a private folder. Visibility is most of the enforcement. When a deadline is public, the conversation about a missed task happens before the close, not after.
Decide who owns each metric and each adjustment
Ownership is where most governance efforts fail. A definitions document with no named owner is a reference, not a control. For each metric that appears in external reporting, one person should be able to explain how it is calculated and why the definition is what it is.
Adjustments need the same treatment. When someone proposes a reclassification or a non-recurring treatment, the question is who approves it and where it gets recorded. In a small team this is often informal, which is fine until the same adjustment gets made twice, or reversed without anyone noticing.
A simple log works. Date, what changed, who approved it, and the reason. It does not need software. It needs to exist and to be reviewed at close, so that the interim CFO can see the pattern of adjustments over time.
Watch for the metrics that get defined differently in different places. Revenue is the usual suspect, but working capital and EBITDA cause just as much trouble. If the forecast uses one definition and the board package uses another, someone will eventually reconcile them in front of an audience.
The interim CFO should be able to name the owner of every metric in the board package from memory. If they have to look it up, the ownership is not real yet.
Ownership also needs a backup. If the named owner is on leave during a close, someone else should be able to pick up the task without a handover meeting. Name the backup in the same document, and rotate the task occasionally so the knowledge stays alive.
Connect the governance work to the forecast and the cash view
Governance sounds administrative until you connect it to the forecast. A cash forecast is only as good as the definitions underneath it. If "collections" means something different in the forecast than in the ledger, the variance analysis is meaningless and the forecast loses credibility fast.
The interim CFO's contribution here is to make the forecast traceable. Each line should tie back to a source: the sales pipeline, the contract terms, the payment history, the payroll calendar. When the actual comes in different from the plan, you should be able to say which assumption was wrong.
Working capital deserves its own attention. The gap between when you pay and when you get paid is where most growing companies run into trouble, and it is also where a buyer looks first. Days sales outstanding, days payable outstanding, and inventory turns all depend on consistent definitions to be comparable over time.
Investor and lender reporting sits on the same foundation. If the numbers you send out are built on definitions that change quietly, the relationship erodes. If they are stable and the variances are explained, the conversation stays about the business.
Ask the interim CFO to show you one forecast line traced all the way back to its source. If that takes more than a few minutes, the governance work is not finished.
Set a rhythm for the forecast itself. A rolling view updated on a fixed schedule, with the assumptions reviewed alongside the numbers, keeps the model honest. A forecast that only gets rebuilt when someone asks is a snapshot, not a tool.
Plan the knowledge transfer before the engagement ends
An interim engagement has a defined end, and the transfer should be designed from the start rather than assembled in the last two weeks. The permanent finance lead needs to inherit not just the files but the reasoning behind the decisions.
What transfers well: the definitions document with owners named, the reporting calendar with the escalation path, the adjustment log, the forecast model with its assumptions documented, and a short list of open items with the reasoning behind each one.
What transfers badly: a folder of spreadsheets with no explanation, a verbal handover in a single meeting, and any arrangement where the interim CFO is the only person who knows why a number is what it is. That last one is the failure mode to watch for.
Build the transfer into the routine. Have the permanent lead prepare part of the close while the interim CFO reviews, then swap roles. Have them present a section of the board package. The point is repetition while there is still someone to correct them.
Set a date for the transfer and work backward. If the engagement is six months, the last month should be mostly review, not discovery. If it is three months, the transfer starts in month two.
Keep a running list of questions the permanent lead asks during the engagement. Each one points to a gap in the documentation. Answering the question is not enough; the answer should end up in the file so the next person does not have to ask it again.
Review progress without assuming the outcome
You cannot measure an interim CFO by whether a transaction closes or a financing succeeds. Those depend on the market, the buyer, and factors outside anyone's control. What you can measure is whether the finance function is more orderly than it was.
Useful indicators: the close finishes on the planned date, the number of post-review adjustments falls, the forecast variance narrows, external requests get answered without a scramble, and the permanent team can explain the key metrics without help.
None of these guarantee a particular result. They describe whether the work is being done. A company can have clean records and still not sell, and a company with messy records can still find a buyer. The governance work changes the cost and the credibility of the process, not the outcome.
Review these indicators monthly with the interim CFO, in the same meeting where you review the numbers. Keep it short. The point is to catch drift early, not to build a scorecard.
If the indicators are not moving after two months, that is worth a direct conversation. It may be a scope problem, a decision-rights problem, or a fit problem. All three are easier to fix early.
Compare the indicators against where you started, not against an ideal. A team that closes in twelve days instead of twenty has made progress even if the target was ten. The direction matters more than the absolute number in the first months.
Adjust the mandate when the company stage changes
The right scope depends on where the company is, and that can shift during the engagement. A business preparing for a financing round needs different work than one that just closed a round and is building the reporting routine that follows. The interim CFO should say when the mandate no longer fits.
Early-stage companies usually need the basics: a close that happens on time, a cash view that is roughly right, and definitions that hold still long enough to compare months. The governance work is light because there is less history to reconcile.
Companies in the middle of a growth phase need more. Multiple revenue streams, a larger team, and external reporting all create pressure on definitions. This is where the ownership work and the adjustment log earn their keep, because the volume of transactions makes informal habits expensive.
Companies heading into a transaction need the records work to be finished and the story behind the numbers to be consistent. The interim CFO's attention shifts from building the routine to proving that it holds under scrutiny.
Ask at each monthly review whether the original scope still matches the situation. A mandate written for a financing that has since closed may need to be rewritten, and it is better to rewrite it deliberately than to let it drift.
What to confirm with a professional before you decide
Before you sign an engagement or extend one, confirm a short list of things in writing. These are the items that determine whether the mandate will work, and they are all answerable in a single conversation.
Which decisions the interim CFO owns alone, which they recommend on, and which stay with the board or owner. Who owns each metric in external reporting, and where the definitions are recorded. What the reporting calendar is, who escalates a missed deadline, and what happens when one slips. Which records a buyer or lender would request, and whether they exist in a form someone else could follow. How the forecast ties back to source data, and who maintains the assumptions. What the knowledge transfer looks like, when it starts, and who receives it. How progress will be reviewed, and what happens if the indicators do not move.
Ask for the answers in writing, even if they are short. A one-page summary of decision rights and transfer expectations is more useful than a long proposal, because it is the document you will actually refer back to when a question comes up in month three.
If any answer is vague, treat that as information. The scope of an interim CFO engagement is defined at the start, and the parts left undefined are the parts that cause friction later. Getting clarity before you commit costs an hour. Getting it afterward costs a quarter.
Toto smaže stránku "Interim CFO data governance responsibilities: who decides". Buďte si prosím jisti.