Month End Close Checklist: Tasks, Owners and Sign-Off

A month end close checklist should tell your finance team what needs to be completed, who owns the work, what evidence proves completion and who can approve the result. A list of account names isn't enough. It's a reminder, not proof, and it won't tell you what's still waiting on review. If a reconciliation is marked done without its workpaper, the controller still can't rely on it.

Use the checklist below to close a period from transaction cutoff through management reporting. It's written for a US accounting team using an ERP or general ledger with separate payroll, billing and banking inputs. The sequence is adaptable, but don't remove review steps merely to meet a reporting deadline. You'll save little time if the numbers can't be explained later.

Copy this month end close checklist

Our month end close checklist is a practical starting point, not a substitute for your company's accounting policies. Assign every line to a person and keep its workpaper next to the task. The controller should decide which steps apply to the entity, reporting basis and materiality policy. That isn't a decision a generic template can make for you.

A checkbox becomes useful only when its completion rule is explicit. For example, “bank reconciliation complete” means the statement balance has been tied to the ledger, reconciling items have explanations and the reviewer can find the supporting file. It doesn't mean somebody opened the banking portal. If the source report isn't dated, you can't tell whether the comparison covers the right period. If you're choosing a tool for that tie-out, see our guide to account reconciliation software.

The checklist deliberately separates prepared, reviewed and approved. A preparer can finish a workpaper while its reviewer is still waiting on an explanation. Calling both states “done” hides risk from the person signing the management accounts. It's better to show an honest delay than a false completion.

The minimum task record

Use these columns in a spreadsheet, task board or close management system. Copy the header row directly into your tracker.

Task	Preparer	Reviewer	Due point	Evidence	Status	Exception owner
Bank reconciliation	Staff accountant	Accounting manager	Early close	Statement and reconciliation	Awaiting review	Treasury lead
AP cutoff	AP accountant	Controller	Early close	Aging and unbilled receipts	Blocked	Procurement lead
Prepaid release	Senior accountant	Controller	Middle close	Rollforward and journal	Prepared	Senior accountant
Flux review	Controller	CFO	Final review	Variance memo	Not started	Controller

Treat those statuses as an example of how the tracker works, not as real results from a company. The critical detail is that the reviewer and evidence fields remain visible even when a task is late. If the close is blocked, the exception owner needs to be someone who can remove the dependency, rather than the person who merely noticed it. Otherwise, you'll get another status update but won't get the missing document.

Set the cutoff and gather inputs before closing

The first close gate is completeness: your team needs a credible view of what belongs in the period before it can certify balances. That starts with an agreed cutoff and an inventory of upstream systems. Don't wait for the first reconciliation to discover that payroll, a payment processor or a billing feed is missing. It's much easier to request an export before the close than to explain an incomplete account afterward.

1. Publish the close calendar

   Name the reporting period, the internal reporting deadline, each workstream owner and the reviewer. State how late documents will be escalated.

2. Confirm the source systems

   List the ledger, bank, billing, payroll and fixed asset inputs. Name a responsible person for each source.

3. Review open items

   Check the unresolved items from the previous close.

4. Collect records

   Gather dated statements and ledger schedules.

5. Record blockers

   Document missing inputs and their owners.

A reliable cutoff is a communication process as much as an accounting process. Tell sales operations when contract changes must reach finance. Tell procurement how to report goods received without invoices. Tell payroll which adjustments are still pending. A shared cutoff memo prevents the accounting team from assuming that silence means there was no activity. If procurement hasn't confirmed receipts, the AP cutoff isn't fully supported.

Choose the right accounting basis

The checklist can't decide whether your business should use cash or accrual accounting. That decision comes from the applicable reporting and tax rules and your adopted policies.

The IRS describes Publication 538 as guidance on accounting periods and methods. That's tax-method guidance, not a substitute for deciding financial statement treatment under your applicable accounting framework. You can't infer financial statement treatment from a tax overview alone.

For an accrual-basis close, review earned but unbilled revenue, received but unbilled services, deferred revenue and prepaid expenses against the applicable policies. For a cash-basis internal report, document the different scope rather than silently skipping those areas in a checklist labeled “GAAP close.”

Reconcile the balance sheet and prove the numbers

A reconciliation is a documented explanation of how a ledger balance agrees with a source or supporting schedule. It should show the balance, the comparison source, reconciling items, the preparer's conclusion and evidence of review. A zero difference without a workpaper isn't a useful control. You'd still have to reconstruct the tie-out when someone asks for it.

Start with cash and card accounts because missing deposits, fees or settlements can affect multiple schedules. Then work through AR, AP, payroll liabilities, prepaids, fixed assets, debt, inventory and intercompany balances where applicable. The correct order depends on your source systems, but the reviewer shouldn't approve a dependent schedule while its upstream input is still open. That's how a small missing input can contaminate several apparently finished tasks.

Account area	What to reconcile	Evidence the reviewer needs	Escalate when
Cash	Ledger to bank statement	Statement and outstanding items	An unexplained difference remains
Card and processors	Ledger to provider settlement	Settlement detail, fees and payout timing	Settlement bridge doesn't tie
Receivables	AR aging to control account	Aging, credit notes and unapplied cash	Customer balances don't match GL
Payables	AP aging to control account	Vendor aging and unbilled receipts	Cutoff items remain unassessed
Payroll	Liability accounts to payroll reports	Payroll register and accrual support	Withholding or wages differ
Prepaids and assets	Ledger to supporting rollforward	Additions, releases and disposal support	Schedule and GL diverge
Debt and leases	Ledger to agreement and schedule	Lender statement or amortization schedule	Principal or interest doesn't tie
Intercompany	Counterparty balances	Bilateral confirmation and elimination log	Entities disagree

Make the exception log more useful than a red flag

A red status doesn't tell the controller whether the problem is a missing document, a posting error or an unresolved estimate. Give exceptions their own structured record: account, evidence gap, estimated impact if known, decision owner, due point and proposed treatment. Distinguish an open reconciling item that has an explanation from a true unexplained difference.

Suppose the payment processor shows a settlement after the reporting cutoff. The preparer should document the timing bridge and compare it with the ledger. If the item is simply cash in transit, the workpaper should say so and show how it clears. If the processor report is missing, the item stays blocked until the evidence arrives or the controller makes and records an appropriate decision. The checklist can't make that judgment for you. It's there to expose the decision and its supporting facts.

Post adjusting entries with a separate review trail

Adjusting entries make the books reflect the reporting period under the applicable accounting policies. Prepare them from schedules, not memory, and retain a trail from the journal back to its support. Reviewers should know which assumptions were used and which reversals are expected next period. They shouldn't need to guess which schedule produced a journal.

Accruals and unbilled costs

Ask department owners for services received but not yet invoiced, then evaluate the appropriate accounting treatment. Keep the underlying purchase order, receipt or service confirmation with the estimate. An accrual without a reversal plan can quietly become a recurring overstatement, while a blanket reversal without checking the actual bill can create a new error. You'll want a clear link between the estimate and the later invoice.

Deferred revenue and revenue recognition

Reconcile deferred balances to the billing and contract schedules before releasing revenue. If contracts have unusual milestones, modifications or credits, escalate them for technical accounting review. A spreadsheet formula may be correct while the underlying contract interpretation isn't. That's why the reviewer needs the contract evidence, not only the calculation.

Prepaids, depreciation and other schedules

Roll forward each schedule from the prior signed balance, add current-period changes and reconcile the ending balance to the ledger. Confirm that the entry uses the current policy and asset information. Review debt interest, payroll accruals, inventory adjustments and intercompany eliminations when relevant.

Journal entry approval

Record the preparer, journal ID, source file, reviewer, posting date and any later reversal. A journal that's drafted but not posted shouldn't count as a completed close task. Likewise, a posted entry that's awaiting review should remain visible as pending approval. It isn't cleared merely because the ledger accepted it.

For US public-company reporting, the SEC's staff guidance emphasizes reasonable assurance rather than absolute assurance in internal control over financial reporting. That doesn't impose a universal checklist on every private business, but it reinforces why the controller should choose risk-appropriate evidence and review controls instead of chasing a perfect-looking task count.

Review financial results before the controller signs off

A finished set of reconciliations doesn't automatically mean the financial statements make sense. The controller should review balance sheet movements, income statement trends and material variances, then connect unusual results back to transactions and accounting judgments. This is the step that catches a perfectly reconciled account posted to the wrong place. Without it, you might miss a classification error that's invisible in the account's own tie-out.

Build a useful flux review

Compare the current period with a relevant prior period and the approved budget, if available. Choose materiality thresholds based on your business and reporting purpose. Avoid copying a percentage threshold from a blog and calling it policy. It won't reflect your risk appetite or reporting needs.

Area	Review question	Evidence or explanation
Revenue	Does change agree with activity and contract timing?	Billing bridge and revenue schedule
Payroll	Does expense align with headcount and pay dates?	Payroll register and accrual memo
Gross margin	Are mix and classification changes plausible?	Margin bridge and ledger drilldown
Operating expenses	Are unusual charges real or misclassified?	Vendor detail and journal support
Cash	Does movement match receipts and financing?	Cash bridge and bank reconciliations

A good variance note names the driver, the supporting record and the person who checked it. It shouldn't read like a guess dressed up as analysis. “Timing difference” isn't enough if the team can't say what is timed differently and when it should reverse. If a number is still under investigation, report the uncertainty rather than presenting a tidy but unsupported story.

Use a sign-off gate, not a celebratory checkbox

Before releasing statements, the controller should confirm that material account reconciliations are reviewed, required adjustments are posted, the trial balance is sensible and unresolved items have explicit decisions. The approver needs a concise exception summary with links to evidence, not an email that says “all done.” If the sign-off can't be reproduced, it isn't much of a control, period.

If one person handles the books, don't pretend a second reviewer exists. Arrange an independent periodic review with an external accountant, owner or qualified supervisor where feasible. When that isn't possible, document the limitation and use compensating checks suited to the risk. The sign-off record should describe the review that actually occurred. It can't document oversight that never happened.

Finalize the period and preserve an audit-friendly close package

Period finalization is the last control after review, not the first step taken to make the dashboard green.

Follow your accounting system's closing procedure and restrict backdated postings according to company policy. If a correction becomes necessary, use an authorized reopening and reapproval process that preserves what changed.

Archive the approved statements, trial balance, reconciliation index, journal support, reviewer decisions and exception log under a consistent period label. Keep references to source systems where the actual records live. A folder full of screenshots with no account, period or owner information won't help the next reviewer. They'll need the context that makes each file meaningful.

Carry exceptions forward deliberately

A carried item needs an owner, a due point and a reason it was accepted. A documented bank timing item can remain on a watchlist, but an unexplained balance shouldn't be marked as routine. The controller decides whether an open item can be accepted and records the supporting rationale.

A sample close calendar

The calendar is an illustrative sequence, not an industry benchmark. Set real deadlines after mapping reporting requirements and staff capacity.

Phase	Work to finish	Dependency	Decision owner
Before cutoff	Confirm inputs and owners	Source availability	Controller
Early close	Record activity and reconcile cash	Final source reports	Accounting manager
Middle close	Supporting schedules and journals	Reconciled subledgers	Senior accountant
Review window	Investigate variances and workpapers	Posted entries	Controller
Release window	Approve statements and file records	Reviewed exceptions	Controller or CFO

Don't force every task into a strict waterfall. Cash reconciliations and payroll reviews can progress in parallel when they don't share dependencies. A revenue recognition entry, however, shouldn't be signed off before the contract and billing inputs that support it are complete. Track dependencies explicitly so a blocked task is visible to the person waiting downstream.

Common month end close checklist mistakes

Most close problems are failures of ownership, evidence or timing rather than missing task labels. Review these failure modes when designing your process.

Marking preparation as approval

A preparer may have posted an entry and attached a reconciliation without receiving independent review. Track prepared and reviewed separately. If an approver requests changes, reopen the task and retain the earlier workpaper version. A task can be operationally complete but not yet approved for financial reporting.

Reusing last month's evidence

A rollforward schedule can start from a prior-period balance, but last month's screenshot isn't evidence for the current month's bank balance. Carry forward accounting policies and recurring task definitions, then refresh source reports, workpapers and sign-offs for the period being closed. The reviewer should be able to tell which period each attachment supports.

Closing the books before resolving exceptions

A deadline doesn't make an unexplained difference disappear. Put each material unresolved item in the exception log with an owner, estimated exposure when supportable, decision and planned resolution. Escalate to the controller before releasing reports. A reviewer may accept a documented timing difference, but the team shouldn't silently convert an unresolved difference into a completed task.

Using one status for every task

A simple done/not-done column hides whether the work is waiting for source data, preparation, review or approval. Use a small set of meaningful statuses and an exception field. Keep the status vocabulary stable from month to month so that recurring bottlenecks are visible. The goal isn't to maximize green checkmarks. It's to give the controller a truthful view of what can be relied on.

How to adapt the checklist to your team

Start with your reporting entity, close frequency and accounting basis. Delete tasks that genuinely don't apply, but record the reason rather than making them vanish. Add specialized schedules for revenue contracts, inventory, foreign currency, leases or consolidation only where those processes exist. Assign a named preparer and reviewer to each material workstream. If staffing is limited, document an independent oversight step or an appropriate compensating review rather than claiming segregation of duties you don't have.

When the checklist outgrows a spreadsheet, our comparison of financial close software shows which tools add reconciliations, transaction matching and consolidation on top of it, and which ones only run the checklist.

Use the same column definitions across teams: task, period, source, preparer, reviewer, due point, evidence, status, exception owner and approval date. That record allows an accounting manager to ask a better question than “Are we done?” They can ask which approved statements are still exposed to an unresolved item, and who can decide it.

For recurring work, review the prior close's exceptions during planning. If the same bank feed is late every month, move the source request earlier. If journal approvals repeatedly wait for one person, delegate the permitted review work or adjust the calendar. If workpapers are complete but management reporting is late, investigate the handoff between accounting and FP&A rather than adding more checklist rows.

The strongest close process is one that a different qualified team member can follow next month without reconstructing decisions from chat messages. Preserve the trail from source document to journal, reconciliation, review note and signed financial package. That is what turns a checklist into an operating control.

Month end close checklist FAQs

Sources and methodology

Our month end close checklist is an editorial controller workflow, not a prescribed legal or audit standard. The accounting-method discussion draws on IRS Publication 538, checked October 19, 2026. The distinction between risk-appropriate evidence and absolute assurance draws on the SEC staff statement on internal control over financial reporting, also checked October 19, 2026. That SEC guidance addresses public-company reporting and shouldn't be read as a universal requirement for every private business. All task tables and calendars above are illustrative operating templates, not survey benchmarks.