
Write a month-end close checklist that names the evidence
How to approach: Write a month-end close checklist that names the evidence
A close checklist should tell the team what to prepare, who reviews it, and what evidence proves the step is done. Start with the task, the owner, and the evidence file. A checklist that only lists task names will be marked complete without the work. Keep the boundary visible in the place where the work is assigned.
Keep the checklist in the order the work happens. A reviewer should be able to open it on the first working day and see the critical path. The list should be short enough to finish and specific enough to defend. Write the deadline as a date and a local time.
Name the task and the owner
Write each task as a verb and an object, such as reconcile the bank account or post the accrual. Record one owner and one backup for every task. A task with two owners usually has none. Keep the original note beside the corrected version.
Record the due date as a working day, not a vague week. If a task depends on another team, record the dependency and the date it is expected. A dependency without a date is a surprise waiting to happen. Ask whether a new reviewer could act on the record without a conversation.
Attach the evidence
For each task, name the file or system that proves it is complete. A reconciliation should point to the signed schedule; a journal entry should point to the support. Evidence that lives only in an inbox is not evidence. Update the template when the same question appears twice.
Record the reviewer and the review date. A preparer who reviews their own work is a single point of failure. The review should be visible in the checklist, not assumed. Name the owner in the same line as the action.
Set the exception path
Write what happens when a task cannot be completed on time. Record the reason, the owner, and the new date. An exception that is not recorded becomes a late close with no explanation. Ask whether a new reviewer could act on the record without a conversation.
Decide who can approve a late task and what the threshold is. A close lead should not be able to waive every step without a record. The exception path protects the team as much as the deadline. Test the rule on one real transaction before applying it to the run.
Review the checklist after the close
Ask the team which step caused the most waiting. Move the dependency earlier or change the owner. A checklist that is reviewed after each close gets shorter and more accurate. Keep the boundary visible in the place where the work is assigned.
Record the changes and the date. A checklist that changes without a version is hard to compare across months. Keep the previous version for the next review. Name the owner in the same line as the action.
This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.