The month-end reporting package: what it contains, when it lands, and how to stop rebuilding it

Financial statements

Income statement for the month and year to date against budget and prior year; balance sheet; cash flow summary.

Variance analysis

Actual against budget and prior period, line by line, with a threshold for what gets a sentence.

KPIs and metrics

Gross and EBITDA margin, DSO, DPO, DIO, current and quick ratio, and the operating metrics the business runs on.

A/R and A/P aging

Receivables and payables by bucket, so collections and cash are visible at a glance.

Commentary

What changed, why, and what leadership should act on. The paragraph that makes it a package rather than a set of statements.

Supporting schedules

Whatever the reader keeps asking for: headcount, revenue by segment, cash forecast.

1. Day 1–2Bank reconciliations, sub-ledger close, cut-off. A/R and A/P aging run.
2. Day 2–3Accruals, prepaids, depreciation, intercompany. Trial balance reviewed.
3. Day 3–4Financial statements and schedules built from the trial balance. Variances identified.
4. Day 4–5Commentary written, KPIs updated, package reviewed by the controller, sent to leadership.

Days one to three are accounting and cannot be skipped. Days three to five are mostly the package: moving the trial balance into the package spreadsheet, repairing what the new month broke, writing the commentary, and reviewing because a figure did not tie. The month-end close checklist covers the first half; the rest of this page covers the second.

In the UK, Ireland, Australia and New Zealand the same document is the month-end pack, or the management pack: profit and loss against budget and last year, a balance sheet, cash flow, KPIs, aged debtors and creditors, and commentary. The vocabulary shifts — turnover rather than revenue, debtors rather than A/R — but a controller in Chicago and a finance director in Leeds are producing the same six parts for the same reason. In India it is the monthly MIS report.

“Month-end close package” is used two ways. Some teams mean the reporting package on this page. Others mean the close binder: the bank and balance sheet reconciliations, the journal entries with their support, and the signed-off close checklist — the evidence that the trial balance is right, kept for the reviewer and the auditor rather than sent to leadership.

Both start from the same closed trial balance, and they answer different readers. The close package shows the books are right; the reporting package says what they mean. Magic MIS produces the second from the trial balance the first has already proved, and checks that every figure in it ties back to that trial balance.

The package is a function of the trial balance. Every statement line is a sum of accounts; every variance is a subtraction; every KPI is a ratio of lines; the aging is a sort of open items. What is done by hand each month is the mapping of accounts to lines, which does not change between months, and the arithmetic, which a spreadsheet does badly only because it was built by hand.

Magic MIS takes the raw trial balance, maps each account to a statement line — by rules first, with AI for the accounts rules cannot place — and computes the statements, KPIs and aging with every figure checked against the trial balance. The commentary is drafted around those figures; it never writes a number of its own. The mapping is remembered, so the next month is a refresh that takes minutes and makes no AI calls when the chart of accounts has not changed.