Guides /AI in Accounting

CFO Reporting: Board Packages, Management Reports, and KPIs

Deepak Anchala

Co-Founder and CEO, Adopt AI

Nov 3, 2026

A CFO reviewing a board package and a trend chart at a desk

The board meets on the 15th. The books closed on the 9th. That leaves six days to turn a trial balance into numbers the CFO can defend, a narrative the directors will read, and a set of KPIs that agree with each other. CFO reporting is the work inside those six days, and most of it has little to do with formatting.

This guide covers what CFO reporting includes, how the board package differs from the management report, which KPIs belong in each, how a package gets reviewed, and why the speed of the close decides the speed of every report downstream. It is written for a CFO who owns the output and the controller and FP&A lead who build it.

What CFO reporting covers

CFO reporting is the set of recurring documents a finance leader produces to tell the business, the board and its investors where the company stands and why. Three audiences read three different documents:

The board and investors read the board package: a monthly or quarterly pack with financial statements, KPIs, a forecast and a narrative.
The executive team and budget owners read the management report: department-level results against plan, with the variances explained.
Lenders, auditors and regulators read compliance and covenant reports, which follow a format set by someone else.

Each document draws on the same ledger. The work lies in keeping the numbers consistent across them, so a director who compares the board package to a budget owner's report finds one revenue figure, not two.

The board package

A board reporting package gives directors enough to govern without making them reconstruct the finance team's work. Most packages hold the same core sections:

A one-page summary. Three to five sentences on the period, the headline numbers and the one or two issues that need a decision.
Financial statements. The income statement, balance sheet and cash flow statement, current period against prior period and against plan.
KPIs. The five to ten metrics that the board tracks every meeting.
The forecast. A rolling forecast that shows where the year lands, with the assumptions behind it.
Variance commentary. An explanation of each material difference from plan.
Risks and open items. Covenant headroom, audit findings, and anything unresolved.

The summary page does the most work. Directors read it first and, on a busy week, read only it. Write it last, after the numbers settle, and test it by asking whether a director could repeat it to someone else.

What belongs in the narrative

A good narrative names the cause of each movement and the person who owns the response. "Gross margin fell 2.1 points because two enterprise renewals closed at a discount, and the sales lead will present a pricing floor next month" tells the board what happened and what comes next. "Margin was pressured by market conditions" tells them nothing.

Every explanation should follow the same standard a variance analysis uses: specific, quantified and traceable to a source a second person can check.

The management report

The management report serves the people who run the business week to week. It is more detailed than the board package and less polished.

A management report typically holds:

Results by department, product line or entity, against budget.
A budget-vs-actual view with variance explanations from each budget owner.
Headcount, spend commitments and open purchase orders.
Working capital detail, including receivables aging and payables timing.

Budget owners write their own variance explanations. The finance team assembles, checks and challenges them. A report where finance writes every explanation hides the information the business needs, which is what the budget owner knows about their own spend.

Board package versus management report

	Board package	Management report
Reader	Directors and investors	Executives and budget owners
Cadence	Monthly or quarterly	Monthly, sometimes weekly
Depth	Summary and trend	Line-item detail
Benchmark	Plan, prior period, forecast	Budget and prior period
Author of explanations	CFO and FP&A	Budget owners, edited by FP&A
Tone	Decision-oriented	Operational

KPIs: which ones, and how many

The most common failure in KPI reporting is length. A dashboard of forty metrics shows the board nothing, because no one can say which five matter. Pick KPIs by the decisions they inform, and cap the board list at ten.

Common choices by area:

Growth. Revenue, bookings, net revenue retention for subscription businesses.
Profitability. Gross margin, operating margin, EBITDA.
Cash. Cash balance, burn, runway, DSO.
Efficiency. Revenue per employee, operating expense as a share of revenue.
Finance operations. Days to close and the number of manual journal entries per close.

Define each KPI once, in writing, with the formula and the data source. When the board sees "net revenue retention" in one package and a different calculation of it in the next, the first conversation of the meeting is about the metric instead of the business.

How a package gets built and reviewed

The build follows the close. The order does not change much between companies:

Close the books. Nothing downstream is final until the trial balance is.
Run the flux analysis. Explain period-over-period movements and catch errors before they reach a director.
Pull the statements and KPIs. Generate them from the ledger, not from a copy of it.
Draft the variance commentary. FP&A drafts, budget owners confirm.
Write the summary. The CFO writes or rewrites this page.
Review in two passes. A controller checks numbers for tie-out. The CFO checks the story.
Distribute. Send the package with enough lead time for directors to read it.

Two controls matter most. First, every number in the package should tie to the ledger, and the tie-out should leave a record. Second, anyone who changes a number after review must say so, so the CFO never presents a figure the controller has not seen.

Why close speed sets reporting speed

A package cannot be built faster than the close finishes. A company that closes on business day 10 and meets with the board on day 15 has five days to build, review and distribute. A company that closes on day 5 has ten.

The extra days buy more than comfort. They give the controller time to run tie-outs, give FP&A time to write commentary from facts instead of guesses, and give the CFO time to ask the second question. Late closes produce thin commentary because there is no time left to find causes.

For the close itself, see the guide to month-end close, the close calendar, and the practice of a continuous close, which spreads reconciliation across the month so the period end holds less work. The outcome a CFO buys from a faster close is a package that arrives earlier with fewer corrections.

What AI agents change about CFO reporting

Report preparation includes a lot of assembly: pulling balances, matching them to schedules, reconciling a KPI to its source, drafting the first version of a variance explanation. Agents take that assembly work, and a person reviews the result.

In practice that means:

Tie-out. An agent compares each figure in the package to the ledger and lists the ones that disagree.
Variance drafts. An agent drafts a sourced explanation for each movement that clears the threshold, and marks the ones it cannot explain.
Consistency checks. An agent flags a KPI that uses a different formula from the prior package.

Nothing posts or ships without sign-off. The controller still owns the tie-out and the CFO still owns the story. What changes is that the controller starts review with the exceptions already listed and the sources already attached.

Adopt's agents work this way: they prepare, trace each number to the transaction or document behind it, and queue the result for a person to approve. Sign up free to see a close and a report prepared for your review.