Management reporting: what goes in the monthly reporting package, in what order, and the bridge that explains it

Management reporting is the internal monthly package that shows managers how the business performed against budget, forecast and last year, and why. It opens with a one-page summary of the variances that matter, explains each one with a bridge, and then gives the P&L, cash, balance sheet, KPIs and department detail. In the March example below, EBITDA came in $81,000 under budget, and the summary says why in one sentence: $56,000 from lower sales, $40,000 from a lower margin rate, partly offset by $15,000 of lower spending.

What management reporting is, and how it differs from financial reporting

Financial reporting is for outsiders. A US public company files audited annual statements on Form 10-K and quarterly statements on Form 10-Q, prepared under US GAAP; the SEC's guide to reading a 10-K lists the income statement, balance sheet, cash flow statement and statement of stockholders' equity that Item 8 requires. The format is standardized and the subject is the past.

Management reporting is for the people running the business. It is monthly, often weekly for sales, it compares results with the company's own plan, and it looks forward to the full year. No standard sets its format: as the OpenStax managerial accounting text puts it, managerial accounting is not governed by GAAP, so the company chooses what goes in, and it can mix financial and non-financial measures.

That freedom is the risk. With no required format, packages grow a page every time someone asks a question, and after two years nobody can find the five numbers that matter.

The monthly reporting package, section by section

In the order the reader needs them:

1. Summary and exceptions. One page: the headline figures against budget and prior year, and the three to five variances that crossed a threshold, each with one sentence of cause. The movements page is this page for a sales team.
2. P&L, month and year to date. Actual, budget, prior year and variances, line by line. A P&L laid out line by line is the base; the package adds the comparison columns.
3. The bridge. Budget profit to actual profit in three to five steps.
4. Cash and working capital. Opening cash, operating cash flow, capital spending, financing, closing cash; receivables, inventory and payables days.
5. Balance sheet. Month end against prior month end and against budget.
6. KPIs. Eight or so, each with a target and an owner.
7. Department and product detail. Cost center spending against budget; revenue and margin by product line or region. The commercial side has its own monthly commercial pack of seven tables that reconcile.
8. Forecast update. Year to date plus the latest estimate of the remaining months, against the full-year budget.

Worked example: the summary page

March, one company, in thousands of dollars.

Variances are shown so that a positive figure is favorable to profit: lower operating expenses than budget is +15. EBITDA is gross profit less operating expenses in every column: 1,544 - 1,105 = 439; 1,640 - 1,120 = 520; 1,470 - 1,060 = 410.

Against last year the month is good: revenue up 6.5% (240 / 3,720) and EBITDA up 29, or 7.1%. Against budget it is not: revenue 3.4% short and EBITDA 81, or 15.6%, short. The summary page shows both, because a manager who sees only the prior-year column will think March went well.

The bridge that explains the month

The bridge splits the 81 shortfall into causes that add up to it exactly.

Volume effect = (Actual revenue - Budget revenue) × Budget gross margin %

Margin rate effect = Actual gross profit - Actual revenue × Budget gross margin %

Opex effect = Budget opex - Actual opex

Check: Budget EBITDA + Volume + Rate + Opex = Actual EBITDA

Volume and rate together, -56 and -40, make the gross profit variance of -96. The summary sentence writes itself from the table: EBITDA was 81 below budget, 56 from lower sales, 40 from a lower margin rate, partly offset by 15 of lower spending. Each step then gets its own detail page: which customers or products were short, and where the margin rate fell. Variance analysis splits each step further, into price, quantity and mix.

Management dashboards and the reporting package

A management dashboard and a reporting package do different jobs. The dashboard gives the headline, refreshed daily or weekly: revenue to date, margin, cash, a handful of KPIs. The package gives the explanation once a month, with the bridge and the commentary. A list, of overdue customers or cost centers over budget, gives the action. The split is set out in dashboard vs report vs list.

The rule that keeps them together is one definition per measure. If the dashboard's gross margin includes freight and the package's does not, two numbers for the same measure circulate, and the meeting is spent reconciling them.

A management report template outline

Set a threshold before the month closes, for example 5% and $50,000 on any P&L line, and comment only on lines that cross it. The rest stays in the tables.

The checks before it goes out

• The P&L ties to the trial balance. Revenue, cost of goods sold and every expense line in the package equal the ledger totals for the month.
• The bridge sums to the variance. Budget EBITDA plus the steps equals actual EBITDA: 520 - 56 - 40 + 15 = 439. A bridge with an "Other" step that absorbs the difference is not a bridge.
• The balance sheet balances. Total assets equal total liabilities plus equity, at both month ends.
• The cash movement ties. Opening cash plus the month's movements equals closing cash on the balance sheet.
• Year to date equals the sum of the months. After a late journal, the year-to-date column must be recomputed, not carried forward.

Where it goes wrong

• Every line, every month. A package with no thresholds lists every variance, and the five that matter are lost among forty.
• Commentary by email chase. Asking every budget holder to explain their lines takes a week, and the answers arrive after the decisions were made.
• Two definitions. The package and the dashboard compute the same measure differently, so two numbers circulate.
• Year to date that does not add up. A late journal changes February, but the year-to-date column still shows the old figure.
• No forecast. The package reports March in detail and says nothing about where the full year will land.

The monthly package, rebuilt from your files

The reporting package is the same tables every month, rebuilt by hand. Covirage's tools produce them from your ledger and budget exports, build the bridge and check that everything reconciles; the external AI model drafts the explanation and never does the arithmetic. See FP&A reporting for how the package and the board narrative are produced, with every figure cited to the rows behind it. To start from a workbook, see the management accounts template and the board report template; for the early read before the close, flash report.