Blog /Accounting

The Complete Month-End Close Checklist (Free Template)

Deepak Anchala

Co-Founder and CEO, Adopt AI

8 October 2026

TODO: select before publish, see editorial notes and the Unsplash candidate in chat

Most close checklists are a list of tasks with no owner, no timing, and no dependency, which makes them a record of what should have happened rather than a tool for making it happen. A checklist earns its keep only when a missed item shows up as a visible chain reaction, not as a surprise on sign-off day.

This is the full checklist, phase by phase, with an owner, a typical timing window, and a dependency for every task. Copy it into a spreadsheet, replace the generic roles with your actual team's names, and run it next month. For the reasoning behind each phase, the benchmarks, and where the hours actually concentrate, see The Month-End Close: The Complete Guide.

Timing notation: BD1 is the first business day after month end. BD-2 is two business days before month end. "Ongoing" means the task runs continuously through the month rather than on a fixed day.

How to use this checklist

Three things make a checklist like this one actually work, rather than sit in a shared drive unread.

Name a person, not a team, for every row. "Accounting" is not an owner. A name is. If nobody owns a task today, that is the first gap to fix, before worrying about timing.

Treat the dependency column as the real schedule. The phases below run in the order they do because the numbers feed each other, not by convention. A task that depends on a subledger close cannot start early just because someone has free time; running it early produces a number that has to be redone.

Risk-rate the reconciliation rows before you run this for real. Not every balance sheet account needs full monthly rigor. High-risk, high-volume accounts (cash, revenue-adjacent, clearing) hold the tight timing shown here. Lower-risk, low-movement accounts can run on a lighter, documented cadence. See Account Reconciliation: The Complete Guide for how to set that tier once and stop relitigating it every month.

Phase 0: Pre-close (all month)

The single strongest predictor of a fast close is how much of it happened before month end. None of this is technically "the close." All of it decides how long the close takes.

Task	Owner	Timing	Depends on
Cash activity matched daily or weekly	Staff accountant	Ongoing	Bank feed or portal access
AP inbox worked down, not saved for cutoff	AP lead	Ongoing	Vendor invoices arriving
Customer payments chased while still current	AR lead	Ongoing	Open invoice list
Suspense and clearing items cleared as they appear	Staff accountant	Ongoing	None
Recurring entries templated (rent, subscriptions, standing accruals)	Senior accountant	Set once, then maintained	None
Invoice submission deadline communicated to budget owners	AP lead	BD-5	Budget owner list
Commission or usage data requested from sales ops and engineering	FP&A	BD-5	None

Phase 1: Cutoff and subledger close (BD-2 to BD2)

Cutoff is where more restatements and audit findings originate than anywhere else in the close. Nothing in later phases should post against a subledger that is still open.

Task	Owner	Timing	Depends on
AP queue swept for received-but-unentered invoices	AP lead	BD-2 to BD1	Pre-close AP hygiene
Accrual candidates listed for goods or services received without an invoice	AP lead	BD1	AP sweep
Late customer billings confirmed in the right period	AR lead	BD1	None
Three-way match stragglers resolved (PO, receipt, invoice)	AP lead	BD1	PO system access
AP subledger closed	AP lead	BD1	AP sweep complete
AR subledger closed	AR lead	BD1	Billings confirmed
Payroll subledger closed	Payroll / HR	BD1-2	Payroll provider report
Inventory subledger closed (count or perpetual rollforward)	Inventory accountant	BD1-2	Count complete, if applicable
Fixed asset subledger closed	Senior accountant	BD2	Additions and disposals logged

Phase 2: Cash and balance sheet reconciliations (BD1 to BD3)

Every balance sheet account needs substantiation, not just cash. A reconciliation that says "agrees" with no support behind it has not reconciled anything.

Task	Owner	Timing	Depends on
All bank accounts reconciled to statement	Staff accountant	BD1-2	Subledger close, bank statements
All card and processor accounts reconciled	Staff accountant	BD1-2	Statements available
AR tied to the aging	AR lead	BD2	Subledger close
AP tied to the vendor subledger	AP lead	BD2	Subledger close
Prepaid, accrual, and deferred schedules tied to the GL	Senior accountant	BD2-3	Subledger close
Fixed assets tied to the depreciation schedule	Senior accountant	BD2-3	Fixed asset subledger close
Clearing and suspense accounts at zero, or a dated exception list with owners	Staff accountant	BD2-3	None
Risk tier confirmed per account (full rigor on high-risk, lighter cadence elsewhere)	Controller	Set once, reviewed quarterly	None

Phase 3: Accruals and adjusting entries (BD2 to BD4)

This is accrual accounting earning its name. Every entry needs support attached at posting time: the calculation, the source, the approver, not reconstructed later.

Task	Owner	Timing	Depends on
Expense accruals posted for received-not-invoiced items, as reversing entries	Senior accountant	BD2-3	AP accrual list
Prepaid amortization released	Senior accountant	BD2-3	Prepaid schedule
Depreciation and amortization posted	Senior accountant	BD2-3	Fixed asset and intangible schedules
Payroll accrual posted for days worked past the last pay date, plus bonus or commission	Payroll accountant	BD2-3	Payroll calendar
Allocations posted (overhead, shared costs, department recharges)	Senior accountant	BD3	Allocation policy
Every posted entry has its basis, source, and approver attached	Preparer and reviewer	Same day as posting	None

Phase 4: Revenue and cost recognition (BD2 to BD4)

The work here depends on the business model, but the recurring failure is the same regardless: revenue recognition depends on data owned by teams outside finance, and the close inherits every delay in that handoff.

Task	Owner	Timing	Depends on
Deferred revenue schedule rolled forward (bookings in, recognized revenue out)	Revenue accountant	BD2-3	Billing and contract data
Billed usage reconciled to metered usage (usage-based models)	Revenue accountant	BD2-3	Usage export
COGS trued up, standard cost variances capitalized or expensed per policy	Inventory accountant	BD3	Count or perpetual records
Revenue recognized per policy for the period	Revenue accountant	BD3	Deferred revenue rollforward

Phase 5: Intercompany and consolidation (BD3 to BD5, multi-entity only)

Single-entity companies skip this phase. For everyone else, intercompany is a notorious close-killer because it requires two entities' books, two teams, and often two ERPs to agree.

Task	Owner	Timing	Depends on
Intercompany balances confirmed between entities	Assistant controller	BD3	Entity trial balances
Intercompany eliminations posted	Assistant controller	BD3-4	Confirmed balances
Foreign entities translated at period and average rates	Assistant controller	BD3-4	FX rates
Entities rolled up into a consolidated trial balance	Controller	BD4	All entity trial balances closed

Phase 6: Trial balance review and flux (BD4 to BD5)

With the entries in, the question changes from "is it recorded" to "is it plausible." This is the close's quality gate, and it is where real errors get caught before the statements ship.

Task	Owner	Timing	Depends on
Preliminary trial balance pulled	Controller	BD4	All entries posted
Flux analysis run against the prior period, threshold applied	Senior accountant	BD4	Preliminary trial balance
Every line above threshold explained causally, with a source attached	Preparer	BD4	Flux run
Flux explanations reviewed and accepted	Controller	BD4-5	Explanations drafted

Phase 7: Statements and reporting (BD5 onward)

Every manual hop between the trial balance and the thing a reader sees is a place an error can enter after the controls have already run.

Task	Owner	Timing	Depends on
Balance sheet, income statement, and cash flow derived from the TB, not re-keyed	Controller	BD5	Flux cleared
Management and department reporting package assembled	FP&A	BD5	Statements
Board package built, if applicable	CFO	BD5-6	Statements, flux
Covenant or lender reporting prepared, if applicable	Controller	BD5-6	Statements

Phase 8: Sign-off and lock

The close ends when someone with authority reviews the package and the period is locked so nothing can post to it again. An unlocked prior period is not closed; it is resting.

Task	Owner	Timing	Depends on
Final review completed by someone other than the preparer	Controller or CFO	BD5-6	Statements, flux
Approvals recorded	Controller	BD5-6	Final review
Period locked in the system	Controller	BD5-6	Approvals recorded
Thirty-minute post-mortem: what was late, what moves to pre-close next month	Controller and team	Within a week	Period locked

What this checklist doesn't replace

A checklist says what has to happen. It doesn't show the dependency graph that makes a one-day slip visible three phases later, which is what a proper close calendar does. It doesn't carry the reasoning for why each phase exists, where benchmarked close times actually land, or how teams risk-rate reconciliations without losing control, which is the full treatment in The Month-End Close: The Complete Guide. And it doesn't settle the soft close versus hard close question, or what a continuous close realistically changes versus what it's pitched to change. Use this checklist to see every task at once; use those for the judgment calls around it.

Where AI agents fit into this checklist

Most of the rows above are preparation, not judgment: retrieving a statement, matching transactions, building a reconciliation, drafting an accrual with its basis attached. That is the layer agents can take on directly, operating the bank portals, the ERP, and the close systems a team already uses, including the ones with no API. The genuine exceptions, an unexplained flux line, an estimate with no precedent, still route to a person, and nothing in the checklist above changes: the owner still reviews, and the sign-off row still belongs to a human. See What AI Agents Change About the Close for the mechanism, or Month-End Close for how it runs against a real calendar.

Book a Pilot to run this checklist against your own close, or start free to see it on one phase first.

Related guides

Glossary

Close Calendar · Record to Report (R2R) · Soft Close vs Hard Close · Continuous Close · Accrual Accounting · Journal Entry · Bank Reconciliation · Deferred Revenue · Three-Way Match · Variance Analysis

Related workflows

Timing windows and owners above are typical for a single mid-sized company and will shift with entity count, revenue model, and system fragmentation. Use your own measured days-to-close, not this template's windows, once you have a few cycles of data.

FAQs

Automate your accounting workflows

See it running on your workflows