An accounting month end close checklist is the most inherited document in finance. It arrives with the job, it is edited under pressure, and it describes the close as somebody ran it three years ago. The tasks that were added because something went wrong are still on it; the ones that quietly became necessary are not. That is why the same three items slip every month and why nobody can say honestly how long the close takes. This page is about building one that stays true: what belongs on it, the categories everybody omits, and the small discipline that keeps it matching reality rather than drifting from it.
Put the chasing on it, because the chasing is the work
Most checklists hold the accounting tasks and omit everything that involves waiting for another person: chasing an approval, querying a supplier, asking a manager what an accrual should be. Those are the tasks that make a close overrun, and leaving them off is why the plan is always optimistic.
Give every task an owner and a duration
An owner because unowned tasks are done last, and a duration because a checklist without durations cannot be planned. On the worked example on this site, 40 tasks at 45 minutes plus 6 reviews at 30 is 33 hours, which is 2.75 working days across two people at six hours a day. The point of the numbers is not precision, it is that the close becomes a quantity you can argue about.
Review it in the first week after the close, not the last
The month you have just run is the only time you remember what actually happened. Ten minutes then, adding what was missing and deleting what nobody did, keeps the checklist true. A quarterly review of an inherited document keeps it plausible.
Questions people ask about accounting month end close checklist
Should we use a template?
As a prompt for what you might have forgotten, yes. As the checklist itself, no: a template describes a business with different systems, different volumes and different people, and its durations are meaningless for yours.
How detailed should each task be?
Detailed enough that a second person could do it. That is the test that matters, because the reason to have a checklist at all is that the close should not depend on one person's memory.
What if the checklist is never followed?
Then it is wrong rather than ignored. A checklist people route around is describing a process that is not the one running, and the fix is to write down the real one.