Most monthly reporting packs start short and grow until nobody reads them. The first version carries a profit and loss against budget, a cash figure and a paragraph of commentary. Two years later it runs to twenty-two pages, three of them are rebuilt by hand each month, and the board spends its hour on page fourteen. Fixing that is design work. Decide what each audience needs, fix the page order, and generate every page from one data sheet.

The figures rarely differ between the management pack and the board pack. What changes is the level of detail, the order of the pages and the framing around them. A finance manager needs the ledger movement behind a cost line, because that is the number they can act on. A director needs to know whether the business traded as planned, whether it can pay its debts as they fall due, and what is being asked of the board this month.

This guide covers the contents and page order of a monthly pack, the design rules that keep it readable, the consolidation approach that lets one data sheet feed every page, and the version discipline that makes the document defensible after it has been circulated.

Two Audiences, One Set of Numbers

A management pack is an operating document. It goes to the people who can act on the numbers, and it carries enough detail for them to act without opening the ledger. Department revenue and cost by category, headcount and overtime against establishment, the debtor ageing behind the receivables figure, job or project margin, and the close working papers. Most businesses run it monthly with a shorter weekly version covering the current month.

A board pack is a governance document. Directors carry duties under the Corporations Act, including the duty to prevent insolvent trading, and they are accountable for the decisions recorded in the minutes. Every page should serve one of three purposes: how the business performed against the approved plan, whether it remains solvent and inside its covenants, and what the board is being asked to decide. A page that serves none of those three purposes belongs in the appendix, or in the management pack where its audience already sits.

The same revenue figure can appear three times in one cycle and be correct each time. In the management pack it is split by department and by customer group. In the board pack it is a single line with a variance and two sentences of explanation. In the appendix it is a list of accounts that reconciles to the trial balance. Rebuilding those three views separately is where the errors come from, and one data sheet with entity, account, department, period and scenario columns can feed all three.

The Standard Pack Contents and Page Order

The structure below is a working default that suits most small and mid-sized groups. What matters is that the order becomes fixed, so a director learns the document once and can find the cash page without asking.

The executive summary decides whether the board reads the rest. Three to five points, each one a sentence carrying a number, followed by a short block naming the decisions sought. A month with nothing to approve should say so on that page, which frees the board hour for the two pages that carry real risk.

Design Rules That Keep a Pack Readable

Six rules do most of the work.

One page per section. A section that needs two pages gets two numbered pages with the section name repeated in the header. It does not get squeezed onto one page at eight point font.

Fixed column structure month to month. Actual, budget, variance, variance percent, forecast, full year. The column order never moves, so a reader who learned the structure in July can still find the variance in December.

One variance sign convention, applied everywhere. Sign every variance to profit, so a negative number always reduces profit. Under that convention a cost overspend shows as a negative and a cost underspend as a positive, and the variance column adds up to the profit variance with no adjustment step. Label each line favourable or unfavourable as well, because a director reading a single row should not have to work out the direction.

The four variances sum to (43), which is the profit variance for the month. A reader can check that on the page in a few seconds, and that is the point of the convention.

Commentary beside the number it explains. The commentary sits in the row it describes, in a wide final column or a merged cell, instead of on a separate page of notes. A reader should never have to match a line reading "as noted on page 9" against a figure on page 4.

Every chart earns its page. A chart earns its place when the page commentary refers to it and the numbers behind it sit on the same page. A chart pasted in from another workbook with a different colour scheme and an axis label from an earlier year subtracts credibility from everything around it.

Consistent rounding and units. State thousands or millions on the cover page and use that unit on every page. Mixed units across pages produce the arithmetic error a director finds in the meeting and remembers afterwards.

Building the Pack From One Data Sheet

The single data sheet separates a pack that takes two hours from one that takes two days. Load the accounting export with four identifier columns and one value column, then let every pack page read from it.

The data sheet needs entity, period (a month end date works well), account code, department or cost centre, scenario and amount. Scenario holds Actual, Budget or Forecast. A separate mapping tab groups account codes into pack lines, so moving an account into an existing pack line changes one row in the mapping and every page follows.

A single month, single account line reads like this:

=SUMIFS(Data[Amount],
        Data[Entity],   $B$3,
        Data[Account],  $A12,
        Data[Period],   $B$2,
        Data[Scenario], "Actual")

Year to date uses the same function with two period criteria, which removes the need for a helper column:

=SUMIFS(Data[Amount],
        Data[Entity],   $B$3,
        Data[Account],  $A12,
        Data[Period],   ">="&$B$4,
        Data[Period],   "<="&$B$2,
        Data[Scenario], "Actual")

$B$2 holds the current month end and $B$4 holds the start of the financial year. Budget and forecast columns use the same formulas with the scenario criterion changed. The variance columns subtract, the variance percent divides by the budget figure inside an IFERROR wrapper for zero rows, and the commentary stays as typed text from the person who owns that line.

Where one pack line groups several accounts, the mapping rows drive the total:

=SUMPRODUCT(SUMIFS(Data[Amount],
                   Data[Account],  Map[Account],
                   Data[Period],   $B$2,
                   Data[Scenario], "Actual"))

Keep the live workbook as the record. Pasting values over the formulas makes the file quicker to open and the pack untraceable, and the first question about a surprising number is always where it came from.

Version Control and How a Board Paper Is Locked

The document that receives board approval is a numbered version, and it stops changing when it is issued.

The working file carries the version in its name, for example 2026-10 board pack v1.2.xlsx. The distributed document is a PDF stamped with the version number, the issue date and the basis of preparation. Any change after circulation becomes the next version with a short note on the cover saying what moved.

Five controls make that work in practice. Freeze the data cut, so the pack reads from a locked copy of the data sheet and later adjustments land in the following month unless they are material enough to justify a reissue. Number the pages and keep the page count stable, so a reference to page 6 stays valid. Keep the workbook internal and send the PDF, because a workbook that circulates comes back edited and the edits rarely find their way back to you. Record the version in the minutes, so the resolution points at the document the board actually saw. Archive the pack, the data cut and the supporting reconciliation together in one folder per month, which is the same set a lender or an auditor will ask for.

Where a correction is genuinely material after circulation, issue a new version, state the change on the cover, and mark the superseded copy so nobody works from it.

The Month-End Close Is the Upstream Dependency

A pack cannot be more current than the close behind it. Pack dates work backwards from the board meeting. The close is complete by day four, the draft pack is ready by day six, the papers are circulated three working days before the meeting, and changes after circulation are limited to corrections.

The close items that delay a pack most often are cut-off (invoices received but not entered, work completed but not yet billed), accruals for known costs, bank and credit card reconciliations, intercompany balances between entities, and stock counts. Where the group holds foreign currency balances or operates offshore, translation uses the closing rate for assets and liabilities and the average rate for the income statement under AASB 121, with the difference taken to a translation reserve in equity. A pack that presents those figures before translation is complete will be restated.

If the board meeting falls ahead of the close, present the flash estimate on the cover and mark the basis clearly. A pack that states a provisional basis survives scrutiny, and the board can act on it with the caveat in front of them.

Common Failures

The pack grows every month. Each board member asks for one more page and nothing is ever removed, so within two years the document is long enough that the important page gets skipped. A page budget and a quarterly cull solve it.

Commentary restates the number. A line reading "Revenue is below budget by 6.4 percent" tells the board nothing it cannot read from the row. Good commentary explains cause and action, as in "Revenue is 6.4 percent below budget because two north region contracts slipped to October, and the sales manager has confirmed both start dates."

KPI definitions drift between periods. If average days to collect is calculated on total debtors one month and on aged debtors the next, the trend line carries no information. Publish the definition under the metric, hold it fixed, and restate prior periods when the definition genuinely changes.

The pack is rebuilt by hand and lost when one person leaves. This is the most expensive failure, because the rebuild takes months and the next preparer inherits no record of how the numbers were assembled. One data sheet, one mapping tab and a written close checklist reduce the handover to reading three files.

Two more failures show up in almost every pack that stops being useful. A pack with nothing to decide trains the board to treat the meeting as a reading exercise. A pack that presents the appendix turns the board hour into a management meeting.

What to Fix First

Fix the order before the content. List the sections the pack carries today, delete any page that has not produced a question or a decision in three cycles, and renumber what remains. Put the executive summary on one page with a decisions block, and move the detailed pages into the appendix.

Then rebuild the numbers from one data sheet with SUMIFS, add the mapping tab, and state the variance sign convention on the cover so every preparer follows the same rule. Set the close dates and the circulation date, and hold them for a quarter before changing anything else.

The result is a pack the finance team can produce in a morning, that a second person can prepare when the first is on leave, and that a director can read in fifteen minutes. That is the test worth applying.

Related reading

• Financial Reporting Automation
• Sales Variance Analysis and Forecasting
• From Numbers to Insights