Skip to content

Reporting

A month-end reporting checklist

A working checklist for closing the month on time: cut-offs, reconciliations, variance checks, commentary, and sign-off.

Talha Ansari··5 min read

Key takeaways

  • Fix the calendar and cut-offs before the month starts; late data is a process problem, not a reporting one.
  • Reconcile at the level you report, with a materiality threshold and a named owner for every break.
  • Every material variance needs a cause, evidence, action, owner, and date.
  • Archive the lock file and review the close so the next cycle takes less effort.
On this page

Set the close calendar first

A month-end checklist only works if the dates are fixed before the period ends. Publish a close calendar that shows the data cut-off, each reconciliation, the draft pack, the review, and the issue date. Use working days rather than calendar days, and exclude public holidays, so a long weekend does not quietly consume the buffer.

The timetable below is a workable default for a small finance team. Adjust the offsets to the business, then keep them stable for a quarter so people can plan around them.

A workable month-end timetable
Working dayActivityOwnerOutput
WD-2Send cut-off reminders and confirm known late itemsFinancial controllerCut-off notice
WD+1Post accruals, prepayments, payroll, and currency adjustmentsFinance teamDraft trial balance
WD+2Reconcile bank, debtors, creditors, and intercompanyAccountantSigned reconciliations
WD+3Review the P&L against budget and forecastFinance leadVariance file
WD+4Draft commentary and the summary pageFinance leadDraft pack
WD+5Issue the final pack and archive the lock fileFinancial controllerIssued pack

Lock the data cut-off

Every source needs a named cut-off: sales invoices, purchase invoices, bank statements, payroll, stock counts, and timesheets. Write the time as well as the date. A supplier invoice received after the deadline is either accrued using a known estimate or held for the next period and disclosed in the pack.

Freeze the ledger once the cut-off passes. Backdated postings should require a logged adjustment with a reason and an approver. Without that rule, the pack will not agree to the ledger a week later, and the review meeting will be spent explaining versions rather than results.

Reconcile the accounts that can break the story

Reconcile in priority order: bank and cash, debtors and creditors control accounts, intercompany, stock and work in progress, deferred and accrued revenue, payroll and tax control accounts, and fixed assets. Reconcile at the level at which the number is reported, not at transaction level.

Agree a materiality threshold in advance. A workable default is the greater of £5,000 or 1% of the balance, with any unexplained break above it escalated before the pack is issued.

  • Bank: statement balance to ledger, with every unreconciled item dated and owned.
  • Debtors: control account to aged ledger, then to the ten largest balances.
  • Intercompany: both sides agree before elimination, with one named resolver.
  • Accruals: each manual entry has a basis, an owner, and a reversal date.

Run the variance and sense checks

Before writing commentary, test the numbers against each other. Most pack errors are not subtle: revenue does not agree to invoicing, gross margin has moved outside its normal range, or the cash movement does not tie to the balance sheet.

Apply a two-way test to every large P&L variance: it should be explained by a volume or price change, or by a matching balance sheet movement. If neither explains it, the number is probably wrong.

  • Revenue agrees to invoiced sales plus the movement in deferred revenue.
  • Gross margin sits within its normal range, or the reason is known.
  • Payroll agrees to headcount and the prior month, allowing for starters and leavers.
  • Every balance sheet movement has a one-line explanation.
  • Closing cash agrees to the bank statements and the cash flow statement.

Write commentary in a fixed order

Use four parts: result, cause, evidence, action. For example, a line might read: Revenue is £28,000 below budget. Two orders worth £35,000 moved into the following month, partly offset by stronger renewals. The sales director will confirm revised delivery dates by Friday.

Do not repeat the number; the table already shows it. State whether the cause is timing, volume, price, cost, or a one-off, and name the person responsible for the response. A comment that ends without an action is a description, not reporting. Three sentences is usually enough for a material line.

Sign off, archive, and review the close

The pack owner signs off the final version and records the date. Archive the pack, the trial balance extract, the adjustment journal, and any source file that cannot be regenerated. The archive lets you answer a question three months later without rebuilding the month from memory.

Review the process after the pack is issued, not during the close. Ask what arrived late, what was reworked, and which check would have caught the problem. Change one thing before the next close; changing five usually changes none.

  • Freeze the reporting file and record its version.
  • Store the final pack, ledger extract, and journals together.
  • Log every late source and every manual fix.
  • Assign one improvement to the next close, not five.

Frequently asked questions

How long should a month-end close take?+

For a small business, aim for five to ten working days, depending on stock, payroll, and the number of entities. A predictable date matters more than the shortest close.

What if the numbers are not final by the cut-off?+

Issue the pack with clearly labelled estimates and reconcile them in the next period. A dated estimate is more useful than a late pack, provided the uncertainty is visible.

Should the pack be issued before the review meeting?+

Yes, two or three working days before, so the meeting discusses decisions and actions rather than reading the pack for the first time.

Need help applying this?

Get help with Automation & Workflows.

Review the service scope or tell us what you are trying to improve. We will reply with a clear next step.

Free KPI definition template

Related reading