Month-End Close Checklist for Controllers

Every controller has a close checklist somewhere. The problem is usually that it lives in three places at once: a stale Confluence page, a senior accountant's personal spreadsheet, and whatever the last audit's PBC list said the process was supposed to be. None of the three agree, and the gap between them is where late items and control breaks hide.

This is the checklist I'd hand a new controller on day one, organized the way the close actually runs: what has to happen before period-end, what happens each day of close week, what has to be true before you call it done, and what to keep so the auditors don't make you rebuild the trail from memory. Pair it with Close Cadence: Getting to a 5-Day Month-End for the reasoning behind the calendar and Accruals, Revenue Recognition, and Reserves for how to size the judgment calls this checklist assumes you've already made.

Phase 1: Pre-Close (D-5 to D-1)

Pre-close is the highest-leverage phase and the one most checklists skip entirely. If these items aren't locked before period-end, everything downstream slips.

Anti-pattern: publishing cutoffs without a named owner acknowledging them. A cutoff nobody confirmed receiving is a cutoff that will get missed, and the miss will be someone else's fault in their telling of it.

Phase 2: Close Days (D+1 through D+5)

This is the day-by-day sequence from Close Cadence, broken into checkable tasks instead of a narrative calendar.

D+1: Cash and Revenue

• Bank reconciliations auto-posted and reviewed
• Payment processor (Stripe or equivalent) tied out to the GL
• Deferred revenue rollforward completed
• Cash position confirmed for treasury and covenant reporting
• Any bounced payments or chargebacks investigated

D+2: Subledgers

• AR aging finalized and reconciled to GL
• AP aging finalized and reconciled to GL
• Fixed asset additions, disposals, and depreciation posted
• Prepaid amortization schedule run and posted
• Inventory count (if applicable) reconciled to the perpetual system

D+3: General Ledger Close

• All recurring journal entries posted
• All manual journal entries reviewed and posted, with support attached
• Accruals booked per the accrual sizing methodology
• Intercompany balances eliminated and confirmed to zero
• FX revaluation posted
• Trial balance reviewed for accounts with no activity that normally have activity (a common miss)

D+4: Review and Flux

• Balance sheet reviewed account by account against prior period
• Income statement variance analysis vs. budget and prior period completed
• Flux commentary drafted for any variance over your team's materiality threshold
• Subledger-to-GL tie-outs confirmed for AR, AP, fixed assets, and deferred revenue
• Unusual or non-recurring items flagged and documented

D+5: Close and Report

• Books locked (system close, not just "we're mostly done")
• Financial package delivered to CFO and/or board
• Close package archived with supporting workpapers
• Post-mortem scheduled within the following week
• Any open items logged with an owner and a resolution date, not left implicit

Phase 3: Reconciliation Sign-Off Gates

A close isn't done because the calendar says D+5. It's done when these gates are actually true, not assumed true.

• Every balance sheet account has a reconciliation on file, current as of period-end
• Every reconciliation has a preparer and a separate reviewer (segregation of duties, not the same person closing and reviewing)
• Every reconciling item over your materiality threshold has a documented explanation
• No reconciliation is more than one period stale
• Tick-marks and supporting documentation are attached, not "available if asked"

If you can't check every box on this list honestly, your close isn't a 5-day close. It's a 5-day close plus an undocumented amount of catch-up work that happens quietly in the following weeks. See Controller Metrics: Close Speed, Accuracy, Controls for how to track whether these gates are actually holding month over month.

Phase 4: Audit-Ready Documentation

What you keep from every close determines how painful the next audit is. Build this into the close, not into a scramble the week before fieldwork starts.

• All manual journal entries have a written business reason, not just a dollar amount
• Reconciliations are saved with a consistent naming convention and version, not five files ending in "FINAL_v3"
• Judgment calls on accruals and reserves have a documented methodology, reviewed and approved
• Approval trail exists for every entry above your review threshold
• Close package is archived in a location the audit team can access without asking you to dig through email

This is exactly the discipline Audit Prep That Doesn't Blow Up Q4 walks through in more depth. The controllers who dread audit season are almost always the ones treating documentation as a year-end project instead of a monthly habit.

Where Closes Actually Break

Run this checklist for a few cycles and you'll notice the same handful of failure points repeat. Named here so you can watch for them specifically instead of discovering them the hard way.

These same patterns show up across the seven traps in Common Controller Pitfalls, which is worth a read if two or more of these are showing up in your own close.

Using This With Your Tech Stack

Whether you're running this checklist in a shared spreadsheet, Asana, or a dedicated close management tool like FloQast or BlackLine, the structure doesn't change: named owner, due date, evidence attached, reviewer sign-off. The tool automates the tracking and the tick-mark documentation. It doesn't replace the discipline of publishing cutoffs and enforcing them. See Controller Tools and Tech Stack for a fuller comparison of what each platform actually does well.

According to close-benchmark data compiled from APQC's General Accounting Open Standards Benchmarking survey, top-quartile finance teams close in about 4.8 business days while median performers take around six, and bottom-quartile teams run ten or more. The gap between those tiers is almost never headcount. It's whether a checklist like this one is actually enforced or just filed away and referenced from memory.

Building This Into Your First 90 Days

If you're new in the Controller or Assistant Controller seat, don't rewrite this checklist against your predecessor's process in week one. Watch one full close using it as an observation tool, note where the real process diverges from what's documented, and fix the biggest gap before touching the rest. The full ramp plan is in Your First 30/60/90 Days as a New Controller.

The One-Sentence Version

A checklist only works if the cutoffs are enforced, the reconciliations are reviewed by someone other than the preparer, and the documentation happens during the close, not after the auditor asks for it.

Learn More

• Controller Job Description Template
• Close Cadence: Getting to a 5-Day Month-End
• Accruals, Revenue Recognition, and Reserves
• Audit Prep That Doesn't Blow Up Q4
• Controller Metrics: Close Speed, Accuracy, Controls