Month-End Close Checklist: Owners, Evidence, Reconciliations and Sign-Off

A month end close checklist turns a recurring deadline into a controlled workflow. It shows what must be prepared, what evidence proves completion, who reviews each result and which unresolved items need escalation before reporting is finalized.

The checklist is a coordination record, not an accounting policy or a financial verdict. Your approved chart of accounts, close policy, control framework and professional guidance remain authoritative. Adapt the sequence to the entities, systems and reporting obligations in scope.

Define the close scope and calendar

Start by identifying the legal entities, ledgers, business units, currencies and reporting period covered by the close. Name the close lead and the person authorized to approve final release. Document the cutoff date, working-day timetable and dependencies between teams.

Build backward from the required reporting date. Allow explicit time for preparation, first review, correction and final review. A task due at the moment the report must be issued has no realistic review window. Where several tasks depend on one source, such as bank data or payroll output, identify that dependency once and notify every affected owner.

Use a stable status set such as not started, in progress, ready for review, returned, complete and blocked. Define each status. “Complete” should mean the required work and evidence have both passed the assigned review, not merely that a preparer opened the task.

Copy this month end close checklist

MONTH-END CLOSE CONTROL SHEET

Entity / ledger / period:
Close lead / final approver:
Cutoff date / reporting deadline:
Status definitions:

TASK REGISTER
Task / account or process:
Dependency / source system:
Preparer / due date:
Reviewer / review date:
Required evidence / storage link:
Status / completion timestamp:
Exception / action / owner / due date:

CORE CLOSE STEPS
[ ] Confirm period, entity scope and calendar
[ ] Communicate transaction and submission cutoffs
[ ] Post approved recurring entries
[ ] Review interfaces and failed postings
[ ] Reconcile cash and bank accounts
[ ] Reconcile receivables, payables and control accounts
[ ] Review accruals, prepayments and fixed assets
[ ] Review payroll, tax and intercompany balances
[ ] Investigate material or unusual movements
[ ] Record and approve supported adjustments
[ ] Complete analytical review
[ ] Resolve or formally escalate exceptions
[ ] Lock or restrict the period as authorized
[ ] Obtain final sign-off and archive the close pack

FINAL SIGN-OFF
Open items and assessed effect:
Evidence index complete:
Preparer confirmation:
Reviewer confirmation:
Authorized release decision / date:
Post-close actions / owners / dates:

Treat this as a starting structure. Remove tasks that are genuinely out of scope and add controls required by your accounting policies rather than allowing a generic list to become an unofficial policy.

Assign preparers, reviewers and evidence owners

Every task needs one accountable preparer and one reviewer. A team name alone does not tell colleagues whom to contact when evidence is late. If segregation of duties is required, configure assignments so the same person does not prepare and approve the item without an authorized exception.

The close lead manages timing, dependencies and escalation; the preparer performs the work and links evidence; the reviewer challenges completeness, accuracy and policy alignment; the account owner explains underlying activity; and the final approver decides whether the close pack is ready for authorized release. System administrators support access and period controls but should not be treated as accounting approvers by default.

Record a backup owner for critical work. Absence should trigger reassignment with a visible audit trail, not silent credential sharing or retroactive approval.

Control cutoff and source completeness

Communicate cutoff rules before the period ends. State which transactions must be submitted, which system timestamp controls inclusion and how late items are handled. Confirm that expected source feeds arrived and that rejected or duplicate interfaces were investigated.

Use control totals, sequence checks or source-to-ledger comparisons where the approved process requires them. Missing data can make a ledger appear unusually quiet, so “no movement” is not evidence of completeness by itself. Record source report names, parameters, extraction times and responsible owners so a reviewer can reproduce the basis.

When a cutoff question requires judgment, route it to the qualified accounting owner. The checklist should record the decision and supporting policy reference; it should not invent the treatment.

Prepare and approve journal entries

Separate recurring, standard and manual entries according to your control framework. Each entry should have a clear business purpose, period, accounts, amount basis, preparer, supporting evidence and required approval. Avoid descriptions that merely repeat an account name.

Review unusual, late or top-side entries with appropriate scrutiny. Confirm that uploads balanced, landed in the intended entity and period, and did not create duplicate postings. Where estimates are used, preserve the method, inputs, assumptions and authorized review.

An approved entry is not automatically a correct entry if the source was incomplete. Link entry review to the broader reconciliation and analytical review. Use a decision log when a material treatment choice needs a durable rationale, owner and review date.

Reconcile accounts to controlled evidence

A reconciliation should connect the ledger balance to a reliable independent source or a documented supporting schedule. Identify the account, ledger balance, source balance, reconciling items, age, explanation, owner and expected clearance date. Mathematical agreement without source integrity is not enough.

Use the audit evidence log template to index controlled records when the close pack contains many files. Do not paste sensitive bank, payroll or personal information into a broadly accessible task board. Link to restricted evidence with access appropriate to the reviewer.

Reviewers should test whether reconciling items are genuine timing differences, errors or unsupported placeholders. Repeated carry-forwards require explanation and escalation under the organization’s threshold rules.

Review estimates, accruals and movements

Accruals, provisions, prepayments and other estimates require an explicit basis. Compare current assumptions with prior periods, available operational evidence and subsequent information permitted by the reporting process. Record who supplied each input and who challenged it.

Perform analytical review by account, business unit or another meaningful dimension. Compare actual movement with expectations, prior periods and authorized plans, but do not treat a small variance as proof that a balance is correct. Investigate unusual relationships, reversals, dormant accounts with activity and significant round-number entries.

If budget context is relevant, keep the explanation traceable to approved records rather than creating a narrative to fit the result. A client status report template offers useful patterns for separating evidence, change and required attention, even when the audience is internal.

Record exceptions without hiding them

An open item is not automatically a failed close. It becomes dangerous when its nature, possible effect, owner or decision route is unclear. Record the issue, affected accounts and reports, available evidence, current assessment, containment, owner, deadline and escalation status.

Use defined thresholds, but allow qualitative escalation for fraud indicators, regulatory concerns, access-control failures or recurring process breakdowns. Do not automatically waive an item because it falls below a numeric threshold. Authorized finance, compliance or legal specialists determine the required response.

The delivery exception report template provides a practical structure for describing deviation, impact, response and ownership. Keep provisional conclusions labeled as provisional until responsible reviewers decide.

Escalate blockers and missed deadlines

Set escalation triggers before the close begins. Examples include missing source feeds, unreconciled differences above an approved threshold, overdue review, unavailable approvers, suspected duplicate postings or an inability to lock the period. Pair each trigger with an escalation owner and response time.

Escalation is a request for a decision or resource, not a blame statement. Describe what is blocked, evidence already checked, reporting effect, available options and the latest useful decision time. If management accepts a residual risk or defers correction, preserve the authorized decision and follow-up requirement.

Do not let messaging channels become the only record. Transfer the outcome into the controlled close log and notify affected task owners.

Use automation and meeting capture responsibly

Automation can route tasks, detect missing fields and compare structured values, but it cannot establish that a balance is appropriate without the required evidence and judgment. Require human review of exceptions, mappings, adjustments and final reports. Preserve logs for automated jobs and investigate failed runs.

Close meetings may contain payroll, banking, customer or commercially sensitive information. Capture them only with authorization, clear notice, appropriate access and a defined retention purpose.

For an authorized close review with visible, consented capture, Kuno can help turn discussion into draft notes and follow-up actions for human verification. It does not approve entries, determine accounting treatment or sign off the close. Explore Kuno

Verify every generated owner, date, amount and conclusion against the controlled record. Remove unnecessary confidential content before distribution.

Complete final QA and sign-off

Before release, confirm that every task has the required evidence and reviewer, all late changes were incorporated, and reports agree to the finalized ledger version. Check entity, period, currency, report parameters and comparative columns. Re-run reports after final approved entries rather than relying on an earlier draft.

The close lead should compile open items and their assessed reporting effect for the final approver. Sign-off must identify the version approved, approver, date and any conditions. Lock or restrict the period only through the authorized process, and document any later reopening.

Use meeting follow-up practices to distribute one reviewed action record. Archive the close calendar, reconciliations, approvals, exception log and report set under the retention and access rules that apply.

Improve the next close from evidence

Hold a short retrospective after urgent corrections are complete. Review late tasks, repeated reconciling items, manual workarounds, duplicate requests and review bottlenecks. Distinguish a one-off event from a control design or capacity problem.

Assign improvements with owners and dates. Track whether they actually reduce delay or error in the next cycle. Do not shorten the timetable simply because leadership wants a faster close; remove root causes while preserving enough time for meaningful review.

Final QA should ask whether another qualified reviewer could understand what was done, reproduce key checks and locate each approval. That test is more useful than a dashboard showing every box in green.

Make close discussions easier to review without outsourcing judgment. Kuno supports authorized in-room capture and draft action notes; responsible finance professionals verify the evidence, treatments, exceptions and final sign-off. See Kuno