A month-end close checklist your team can adapt.
A clear close is less about a perfect calendar and more about ownership, dependencies, review, and evidence. Use this checklist to shape your own process.
Start with ownership. Finish with evidence.
Close calendars differ by company size, systems, reporting obligations, and transaction volume. Treat these steps as prompts; set dates and sign-off rules to fit your own controls.
Before the period ends
- Confirm the close calendar, reporting cutoff, and one accountable owner per task for every entity in scope.
- List recurring and expected manual journals, with the support each one requires and who will approve it.
- Confirm source-system access for each preparer: ERP, bank portals, payroll, cards, and subledgers.
- Record an interface owner and an expected delivery time for every recurring file or feed the close depends on.
- Identify dependencies outside finance: payroll approvals, revenue data, fixed-asset additions, and legal invoices.
- Note known changes for the period, including new entities, bank accounts, contracts, and chart-of-account updates.
- Agree materiality, review thresholds, and escalation contacts before preparation starts.
- Pull the prior-period open-items list so carry-forwards are visible from day one.
At close kickoff
- Publish the task list with one accountable owner per task and a named backup for each.
- Confirm the reporting cutoff date, time zone, and the treatment of transactions in flight at cutoff.
- Record scope changes: entities, accounts, reporting basis, or consolidation changes that affect comparability.
- Confirm the pre-close tie-out expectation for each subledger to its general-ledger control account.
- Open the exception log and populate it with unresolved items carried forward from the prior cycle.
- Agree where reconciliations, journal support, and approvals will be retained, and who can access them.
- Set the materiality threshold for flux review and confirm who signs off on explanations.
- Confirm review meeting times and the decision rights of each attendee.
During preparation
- Reconcile key balance-sheet accounts to independent support, and record the reconciling difference even when it is zero.
- Tie subledger and source-report totals to general-ledger control totals; document timing differences and expected clearing dates.
- Investigate unusual movements, large or round-dollar entries, and anything posted outside the normal pattern.
- Review aged reconciling items and assign an owner and expected resolution date to each one.
- Confirm revenue, expense, and payroll accruals against the approved policy and their supporting evidence.
- Review intercompany balances, confirmations, and the elimination entries that will be required.
- Keep preparer work and reviewer approval distinct; record the reviewer's name and date on the record.
- Log every manual adjustment with the reason, the evidence, and the person who approved it.
Before sign-off
- Confirm high-risk and unusual entries have review evidence attached rather than verbal sign-off.
- Resolve open exceptions, or explicitly carry them forward with an owner and a next review date.
- Review fluxes against the approved comparison basis and document material drivers with the business owner.
- Confirm the trial balance balances, the consolidation is complete, and the reporting basis is unchanged.
- Confirm the final journal batch is posted and the period is actually closed in the ledger.
- Retain the final trial balance, key reconciliations, journal support, and sign-offs in one location.
- Record the close result, open carry-forwards, and lessons for the next cycle in the exception log.
Close evidence index
Decide where each item lives before the period starts. The most common close failures are retention failures, not calculation failures.
| Evidence | Prepared by | Reviewed by | Common failure |
|---|---|---|---|
| Final trial balance | Accountant | Controller | Filed without a balance or control-total check |
| Final journal batch | Accountant | Controller | Posted in pieces with no single approved batch |
| Bank reconciliations | Accountant | Controller | Preparer and reviewer are the same person |
| Subledger-to-GL tie-outs | Accountant | Controller | Timing differences never given a clearing date |
| Accrual support | Accountant | Controller | Accrual is created and never reversed |
| Intercompany confirmations | Accountant | Controller | Confirmation signed without checking the balance |
| Flux commentary | FP&A owner | Controller | Explanation written after the report is circulated |
| Close calendar sign-off | Close owner | Controller | Status marked complete without evidence |
| Exception log | Close owner | Controller | Items listed but nobody owns the next action |
Escalation triggers
Define these before the close is under time pressure. The point is to move a decision to someone who can make it, not to document a failure.
| Trigger | Why it matters | Escalate to | Typical response |
|---|---|---|---|
| Material flux with no explanation | A number can move without anyone accountable for the driver | CFO / FP&A lead | Same business day |
| Reconciling item older than 60 days | Stale items tend to hide a real error or an unreviewed write-off | Controller | Within 2 business days |
| Manual journal without support | Unsupported entries are the most common audit finding pattern | Controller | Before posting |
| Interface failure on a control account | Subledger may be out of balance without anyone noticing | Systems owner + controller | Same business day |
| New entity, bank account, or basis change | Comparability and completeness of the close are both affected | Controller | Before kickoff |
| Close task late by more than one day | Late tasks cascade into review, which is where quality is lost | Close owner | Daily stand-up |
| Preparer and reviewer are the same person | The control does not exist, whatever the checklist says | Controller | Before sign-off |
Common failure modes
These recur across teams that have a checklist on the wall but no evidence discipline behind it.
Marked done, not evidenced
A task is closed because it feels complete. Ask to see the artifact, and record where it lives.
The reviewer became the preparer
A small team fixes a backlog by doing the work and approving it. Split the roles or document why the control cannot operate.
One-off treatment of a recurring item
The same misposting is corrected every month. Track repeats; they are process defects, not close tasks.
Accruals that never reverse
An accrual is booked to make the period balance and never cleared. Reconcile the accrual schedule each period.
Exception log nobody owns
Open items are listed in a file that no one is accountable for. Assign a name and a date per line.
Cutoff drift
The cutoff moves a little each cycle until comparability is quietly lost. Fix the cutoff date and hold it.
Can another person follow the trail?
For each material balance or journal, a reviewer should be able to find the source, the preparation logic, the open questions, and the recorded approval without relying on the preparer's memory. If that test fails for a recurring item, the fix belongs in the process, not in the file.
Compare notes with the Yoraito team.
Tell us which close routines consume the most review time in your environment.