Month-end reporting pack: A sample pack, the close package behind it, and a calendar to send by day 6

A month-end reporting pack, also called a management reporting pack or monthly management report, is the document finance sends leadership after each close: results against budget and prior year, the balance sheet, cash, KPIs, and written commentary.

• Management reporting packThe detailed monthly pack for the executive team, also called a management pack, management information pack, CFO reporting pack, monthly management accounts, month-end report, end-of-month report, or monthly reporting package
• Board packA shorter, summarized version for directors and investors, built from the same numbers and often sent quarterly
• Close packageThe workpapers behind the numbers, also called a close binder: trial balance, reconciliations, entry support, flux explanations, and sign-offs

In simple words, the pack is the story of the month, and the close package is the proof. A month-end close report usually means the same pack, sometimes with a close status page added. It matters because leaders make hiring, pricing, and spending calls from it, so a late or wrong pack leads to late or wrong decisions. The pack is the output of the month-end close, and it can only be as good as that close.

How is a management pack different from statutory accounts?

A management pack is internal, monthly, and built for decisions, so it can use budgets, KPIs, and non-GAAP measures in any format. Statutory accounts are annual financial statements that follow GAAP or IFRS, are usually audited, and are filed with regulators where the law requires it (in the US, mainly public companies filing with the SEC).

Both should come from the same ledger. If the management pack and the annual accounts disagree, the difference should be a known list of year-end adjustments, not a surprise found during the audit.

The reporting pack shows leadership what happened, and the close package proves the numbers are right. Finance builds the close package first, during the close, and the pack second, from the locked results.

Month-end closing and reporting are two halves of one process. Closing produces reconciled balances and a locked period, and reporting turns those balances into the pack. Treat them as one chain, with the close status page as the link that tells readers what is signed off.

A month-end reporting pack should open with a one-page summary and the decisions needed, then the P&L against budget and prior year, the balance sheet, cash, KPIs, commentary, the forecast, close status, and an action log. Detailed schedules go in an appendix.

Readers should get the whole story from the first two pages. Keep the order fixed so changes stand out from month to month.

The P&L columns follow the budget vs actual layout. Show favorable variances as positive for both income and costs, and say so in a footnote, so a reader never has to guess the sign.

For the KPI page, a common starting set is five financial KPIs: revenue growth against budget, gross margin, EBITDA margin, free cash flow or cash runway, and DSO. Add two or three operating KPIs that drive your business, such as ARR and net revenue retention for a SaaS company. Formulas and targets for close-side metrics are in financial close KPIs.

This sample pack shows every page for a fictional company, Sample Co, for October 2026, in $000s. All numbers are illustrative, on an accrual (US GAAP) basis, and every total ties across pages.

Page 1: Summary and decisions

Page 2: P&L vs budget, prior year, and year to date

Variances are favorable when positive. For costs, variance is budget minus actual, and variance % is variance divided by budget.

Two checks prove the page. The gross profit variance (−44) equals the revenue variance (+200) plus the COGS variance (−244). The EBITDA variance (−94) equals the gross profit variance plus the opex variance (−50).

Page 3: Gross-profit bridge

The bridge splits the gross profit miss into a volume effect and a margin effect, so the reader sees that the revenue beat was real but the margin drop was bigger.

Page 4: Balance sheet

Cash, fixed assets, debt, and equity roll from the cash flow and the P&L, so the balance sheet only balances if the pack ties.

In the sample, DSO is accounts receivable divided by the month's revenue, times a 30-day convention: 6,720 ÷ 4,200 × 30 = 48.0 days, against a 45-day target and 47.6 days in September. Equity also ties, with no dividends or share issues this year: 8,076 at year-end plus 3,224 of YTD net income equals 11,300.

Page 5: Cash

The cash page uses the indirect method, so every line comes from the P&L or a balance sheet change.

Page 6: KPIs

Each KPI shows its definition, actual, budget or target, prior month, trend, and a status set by a stated rule.

The status rule is On track when a KPI is at or better than budget, Watch when it's worse but within tolerance, and Off track when it's worse by more. In the sample, tolerance is 1 point for margins and opex %, 60 for free cash flow, and 2 days for DSO.

Page 7: Commentary

Commentary covers every variance over the sample threshold of $25,000 or 10%, with a cause the budget owner has confirmed. The threshold is a review trigger you set, not an accounting or materiality rule, so a smaller item can still need a note.

Underlying EBITDA ties: 486 + 35 + 15 = 536, and 536 − 580 = −44, which is exactly the gross profit miss. Cost of goods sold (−244, 16.1%) is over the threshold and is explained in the gross profit line. Research and development (+10, 1.6%), G&A (−20, 4.0%), and depreciation (−6, 10.0%) don't exceed the threshold, so they need no commentary.

Page 8: Forecast

The forecast page adds the November–December forecast to year-to-date actuals and compares the full year with budget.

The forecast assumes the November–December gross margin stays at 59.0% against a 62.0% budget until the pricing review lands. That assumption explains why full-year revenue is 1,200 over budget while gross profit is only 86 over. With operating expenses 300 over budget, EBITDA lands 214 under.

Page 9: Close status

The close status page tells readers what is signed off behind the numbers, so they know how far to trust each page. Send the pack only when every reconciliation is signed off. The one exception is a difference you have quantified and the controller and CFO have formally approved as immaterial under your written materiality policy, listed here with its amount. An unexplained difference is corrected in the month it belongs to before the lock, or recorded as an unadjusted difference under that policy. It doesn't roll into next month by default.

Page 10: Risk and action log

The action log carries every open item forward until it's done, so last month's commitments show up again.

Good variance commentary gives the number, the direction, and the cause, then says whether it will recur and what happens next. Write the cause only after the budget owner confirms it, and never guess.

Use the same five parts for every line over your threshold.

1. 1NumberThe variance in dollars and percent, against budget, prior year, or both
2. 2DirectionFavorable or unfavorable, in words, so the sign can't be misread
3. 3CauseThe driver, confirmed by the person who owns the budget line
4. 4Recurring or one-offWhether it will repeat next month
5. 5ActionWhat happens next, with an owner and a date, or “none”

Show one-off and prior-period items on their own line or in a reported vs underlying bridge, never buried in the month. Label accrual-driven swings, give the underlying result next to the reported one, and say what is non-recurring, so the board doesn't mistake a timing effect for a trend. In the sample, the 35 trade show and the 15 prior-period audit fee true-up would otherwise read as a 50 overspend.

The same thresholds and explanation rules drive the close-side review in flux analysis. Reuse the flux explanations the controller already signed off, so the pack and the close package never tell two stories.

A management pack is the detailed monthly pack for the executive team, and a board pack is the shorter version for directors and investors, focused on strategy, risk, the forecast, and decisions. Build both from the same locked numbers so they never disagree.

There's no rule for length, but shorter packs get read. Set a page budget for each audience, move detail to an appendix, and cut any page that doesn't lead to a question or a decision. To turn the sample pack into a board pack, keep the Summary, KPIs, Cash, Forecast, and Actions pages up front and move the rest to the appendix.

A board pack is more useful when it leads with the decisions you need and shows a few trend charts instead of tables. Explain each variance with cause and action, and keep the same format every time. Send it early enough for directors to read before the meeting.

For a SaaS company, the board pack adds ARR, new and churned ARR, net and gross revenue retention, CAC payback, burn multiple, and runway to the standard financials. The close steps behind those numbers are in SaaS month-end close.

For a group with three or more entities, give the executive team entity and department detail, and give the board a consolidated pack with entity detail in an appendix. Both should come from the same consolidated, locked numbers, built as described in month-end consolidation.

To do a month-end report, lock the period, tie the trial balance to the reconciled balance sheet, refresh the pack from the ledger, explain variances over threshold with owner-confirmed causes, review it, and send it.

1. 1Close and lock the period so no one can post to it while the pack is built
2. 2Tie the trial balance to the reconciled balance sheet and the close package
3. 3Refresh the pack from the ledger, never by retyping numbers
4. 4Flag variances over your threshold, such as $25,000 or 10%
5. 5Get causes from budget owners on a fixed day, with a deadline
6. 6Write the commentary in the five-part format above
7. 7Review: the controller checks the numbers and the CFO checks the story
8. 8Send the pack, and save a dated, approved copy that doesn't change after sign-off

The calendar below targets working day 6. Treat that as a target you set for your team, not an industry standard. For the October 2026 close, working day 1 is Monday, November 2.

For an outside reference point, use APQC's Open Standards Benchmarking measure 100625 (no publication date, read November 11, 2026). Its median is 10.0 calendar days, including weekends, from the first entity trial balance to the period-end management report, across 3,287 organizations. A pack sent on November 9 from a November 2 trial balance takes 7 calendar days on that measure. Targets by company size are in how long should month-end close take, and the task-level schedule is in the month-end close calendar.

Faster is only better if the period is locked and reconciled first. A pack built on an open ledger will change after it goes out, and leaders stop trusting it.

Flash report vs full pack

A flash report is a one-page early read, sent before the full pack (working day 2 in the sample calendar), with revenue, gross margin, EBITDA, cash, and any big surprise, marked as subject to change. The full pack follows once the period is locked and reviewed.

Keep the flash to a handful of numbers and one line on anything unexpected. If a flash number moves by more than your threshold in the full pack, say so in the pack's summary.

Before the pack goes out, confirm the period is locked, the pack ties to the trial balance, every variance over threshold has an owner-confirmed cause, one-offs are labeled, KPI definitions haven't changed, and the CFO has approved it.

The KPI check borrows from public company rules. The SEC's interpretive release 33-10751 (January 30, 2020) says a key metric in MD&A should generally come with a clear definition and how it is calculated. It also says a company should consider disclosing any change in the calculation method, the reason, and its effect, and may need to recast prior periods. A management pack isn't an SEC filing, but the same habit stops a quiet definition change from looking like a trend.

A month-end close package, or close binder, is the evidence behind the month's numbers: the trial balance, reconciliations, journal entry support, schedules, flux explanations over threshold, the close checklist, and preparer and reviewer sign-offs.

Organize it by section and balance sheet account, not by date, and put the checklist and sign-off log at the front. Each row below needs a preparer and a different reviewer.

For each account, the binder should hold the GL balance and the reconciliation tied to the trial balance. Add support for every reconciling item, related journal entries with approval, and a flux note if the movement crosses your threshold. The method for each reconciliation is in account reconciliation, and the entries behind section 12 are in month-end journal entries. Multi-entity groups add an intercompany section with matched balances and eliminations.

Sign-off evidence is what makes the package usable. Every reconciliation and entry should show who prepared it, who reviewed it, when, and against what support, and manual entries should be approved before posting. The tasks that produce this evidence are in the month-end close checklist. At year-end, add the post-closing trial balance to prove temporary accounts closed to retained earnings.

Close package vs PBC list

Your team builds the close package every month to prove the books are right before they're locked. A PBC (“provided by client”) list is the auditor's request list at quarter-end or year-end. A complete monthly close package answers many PBC requests before the auditor asks.

In many mid-size companies, the controller owns the actuals, FP&A owns the analysis, budget comparison, and commentary, and the CFO reviews and signs off before the pack goes out. In small teams, one person often does both jobs.

When one person prepares the whole pack, a second reviewer matters more, not less. Ask the CFO or an outside accountant to review the numbers against the close package before the pack goes out. How the FP&A role fits next to the controller is covered in what is FP&A.

Build the statements once in your ERP's report tool, map every account to a pack line, lock the period, then refresh the same template each month. Never paste numbers into the pack by hand.

For the close package in NetSuite, keep journal entry approvals in the system and store each reconciliation with its support by period and account. The controller and auditors can then trace any balance from the statements back to source.

To automate the pack in Excel or Power BI, connect to the ledger through a standard export or connector and map accounts to pack lines once. Refresh after the period locks, then check that the pack still ties to the trial balance. Automate the numbers and variance flags first, and keep commentary and review with people.

A small business pack on QuickBooks or Xero can be four to eight pages: summary, P&L against budget and last year, balance sheet, cash with a short cash forecast, a few KPIs, and commentary. The close behind it is in month-end close for small business.

AI can pull the numbers, rank variances, build the bridge, and draft the commentary. A person must still confirm the period is locked, the numbers tie to the reconciled ledger, each stated cause is true, and judgment items are right.

Month-end reporting software falls into three groups. Close tools track and evidence the close, FP&A and reporting tools build the pack from the ledger, and AI agents prepare the work in both for review. Choose by the work that takes your team's hours, using the best month-end close software guide, which compares options by the work each one does.

Our Close Agent reconciles the ledger and prepares each entry with its workpaper for a named approver, and nothing posts to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, or QuickBooks until that approver signs off. Our FP&A Agent then investigates the variances, separates recurring from one-off effects, and updates your own management pack or board deck with numbers, analysis, charts, and commentary for your review. Explore our Close Agent and our FP&A Agent to see the close package and the pack prepared before your team starts reviewing.