Month-end close checklist: the steps in order, and the ones that set the timeline

A month-end close checklist lists every task a finance team completes after the month ends to produce that month's financial statements, and a useful one lists the tasks in the order they depend on each other. The order matters more than the list. APQC's benchmark, published in 2018 and drawing on roughly 2,300 organizations, puts the median monthly close at 6.4 calendar days, with top-quartile finance teams done in 4.8 days or fewer and the bottom quartile taking ten or more. The fast teams rarely have fewer tasks. They finish sooner because the tasks everything else waits for are done first, done early, or done before the month ends at all.

The month-end close checklist, in dependency order

The close runs in seven stages. Tasks inside a stage can run in parallel; a stage can't finish until the stages it depends on have.

1. Before the month ends: publish the close calendar, send accrual requests to department heads, clear unapplied cash and suspense items, and confirm the cutoff procedures.
2. Cutoff: record every sale shipped and invoiced through the last day, log goods received but not yet invoiced, and stop the payment run at the cutoff.
3. Subledger closes: complete payables with every invoice for the period, receivables with billing done and cash applied, payroll with wages and benefits accrued, inventory with counts and costing, and fixed assets with additions, disposals and depreciation.
4. Reconciliations: reconcile the bank accounts and cards, tie each subledger to the general ledger, and reconcile the balance sheet accounts, clearing accounts and intercompany balances.
5. Adjustments: book accruals, prepaid amortization, deferred revenue, reserves for bad debt and obsolete inventory, and intercompany eliminations.
6. Review: review the trial balance, compare every line against budget and prior periods, and explain the material variances.
7. Reporting: issue the financial statements and the management pack, sign off, and lock the period.

Each task on a real checklist carries three more things: an owner, a due day relative to the month end, and the evidence the reviewer will look for, whether that is a reconciliation file, an accrual calculation or a variance note. A checklist without the evidence column gets completed on trust, and the reviewer ends up redoing the work to check it.

The critical path sets the length of the close

The dependency order is what turns a list into a schedule. Receivables can't be reconciled until billing is complete and the month's cash is applied. Accruals for goods received but not invoiced can't be booked until payables has entered every invoice that arrived. The variance review can't start until the adjustments are in, because the variances before adjustment are noise. Each of these chains has a length, and the close takes as long as the longest one.

Two consequences follow. A task off the critical path can run late without moving the close date, so effort spent speeding it up saves hours but not days. And a task on the critical path moves the whole close with it, which is why one slow reconciliation or one late input from a department can hold a finance team for two extra days while most of its work sits finished. APQC's close cycle time counts both the time spent performing the work and the time spent waiting to move forward, and the waiting is measurable. Ventana Research found in 2023 that 47 percent of teams with little or no close automation wait a noticeable amount of time for others to finish before they can start their own tasks, against 27 percent of teams that run the close on workflows. A checklist that shows dependencies makes the waiting visible. A flat list hides it, and teams with flat lists tend to speed up whatever is easiest to speed up.

Where the days go in a slow close

The days in a slow close tend to go to the same four places. Inputs arrive late: supplier invoices keep coming for a week after the month ends, payroll and commission data come from outside finance, and inventory counts depend on the warehouse. Reconciliations carry unexplained differences, and each one becomes an investigation into a timing difference, a misposting or a missing entry. Manual journal entries pile up at the adjustment stage, each needing support and approval. And review becomes a queue when one controller signs off every reconciliation and every entry.

The benchmarks show how little has changed. In the same Ventana research, 58 percent of organizations completed their monthly close within six business days, statistically unchanged from 60 percent in 2019, and only 44 percent closed the quarter that fast. APQC's figures for period-end management reporting widen the gap further, running from six days at the top quartile to ten at the median and fifteen at the bottom. A team in the bottom quartile is doing roughly the same checklist as one in the top. The difference is mostly in the four places above.

Which steps bring the close date forward when automated

Automation shows up clearly in the close benchmarks. Ventana's earlier Office of Finance benchmark, from 2018 and 2019, found that 88 percent of organizations that use extensive automation in their close finish within six business days, against 40 percent of those that use little or none. The steps worth automating first are the ones on the critical path that consist of matching and gathering. Reconciliations are the clearest case: most of the lines match by rule, and the days go into the unmatched remainder, which is where an agent can do the investigation and hand the accountant a proposed explanation with the evidence attached. We cover what a machine can and can't match in reconciliation automation. Cash application is the second case, because receivables can't close until the month's payments are applied, and we walked through that step in rebuilding cash application. Accrual support is the third: an agent can read open purchase orders, receipts and contracts and propose the accrual with its calculation, leaving the judgment on the estimate to the accountant.

Variance review is a fourth, with a limit. An agent can pull the transactions behind each variance and draft the explanation, and a controller still decides whether the explanation holds. We walked through one close rebuilt this way, from trial balance to statements, in rebuilding the month-end close.

Moving work out of the close

The other way to shorten the critical path is to move tasks off it entirely. A bank account reconciled weekly arrives at month end with a week of activity to clear rather than a month. Cash applied the day it arrives leaves nothing for the close. Recurring accruals booked on a schedule, and payroll checked before the run goes out rather than after, remove items from the adjustment stage; we describe the payroll case in rebuilding payroll. The close then becomes a review of work already done, and the checklist gets shorter in the only way that matters, by having fewer tasks that must wait for the month to end. ISG Research expects two-thirds of organizations to apply continuous accounting principles and close within one business week by 2027, up from half in early 2024, a forecast rather than a measurement, and one that depends on exactly this kind of work moving out of the close.

A reasonable counter, answered

A reasonable counter is that close speed is a vanity metric: the statements have to be right, a controller who closes in four days with errors has done worse than one who closes in eight without them, and pushing for speed invites mistakes. The premise has evidence behind it. When the SEC shortened 10-K filing deadlines in 2003, companies forced to file faster than they had before became more likely to restate those filings later, according to a 2013 study in the Journal of Accounting and Public Policy. And Gartner's 2024 survey of controllership staff found that 18 percent of accountants make financial errors at least daily and a third make several every week, errors Gartner linked to capacity constraints. A checklist built for speed alone is a bad checklist. But speed and accuracy fail for the same reasons in most finance teams. The slow close is slow because reconciliations are done by hand at month end, adjustments are rushed at the end of a long week, and one reviewer is looking at everything at once, and those are the same conditions in which errors get through. Doing the matching continuously, attaching the evidence to each task, and giving the reviewer a queue of explained exceptions rather than a stack of raw work tends to make the close both shorter and more accurate, because the time saved comes out of the manual steps rather than out of the review.