Close · Guide

Month-end close checklist

A close runs in a sequence. Sub-ledgers have to agree before reconciliations mean anything, and reconciliations have to be signed off before the numbers are worth reporting. Reorder it and you redo the work.

This is sized for a team of one to five. The timings assume a ten-working-day close; compress them, don't reorder them. Every task has one owner and one date — if a task has two owners, it has none.

Before the period ends (day −2 to 0)

Days 1–2 · Cut off and accrue

Days 3–4 · Reconcile the sub-ledgers

Days 5–7 · Balance sheet and adjustments

Days 8–10 · Review and report

The sign-off is the control. A reconciler prepares, a second person reviews, and both names and dates are recorded. "Prepared by" alone is not a control — it's a signature on your own work.

What a close checklist should contain

For every line: the task, the owner, the due date relative to period end, the evidence produced (the reconciliation file, the sign-off), and the dependency. Dependencies are what make a checklist a schedule — the bank reconciliation can't start until the feeds are imported, and the flux analysis can't start until the P&L is final.

Keep the tasks relative to period end (day 3, day 5) rather than calendar dates. Then the same checklist works in February and in December, and you can generate next month's dates from a single period-end value.

Where closes actually slip

What the Close Calendar will do All guides

Related

Finding duplicate invoices · AR aging explained