The Month-End Close Checklist: A Controller's Guide to Closing Faster and Cleaner

The median finance team takes 6.4 calendar days to close its books each month. The top 18% do it in three. The difference isn't talent — it's process. This guide gives you the checklist, the dependency logic, and the close management framework to move from the median to the top quartile.

What Is the Month-End Close?

The month-end close is the set of accounting procedures that finalize a company's financial records for a given period. It produces the trial balance, financial statements, and supporting documentation that auditors, management, and the board rely on to make decisions.

Every close answers one question: are the books accurate, complete, and defensible?

Most teams treat the close as a checklist — a flat list of tasks to grind through. That works until it doesn't. When the team grows past three people, when auditors start asking for evidence, when the CFO wants to know why it takes nine days instead of five, a checklist alone stops being sufficient. The distinction matters: a checklist tells you what to do. Close management tells you what you can do right now, who's blocking whom, and whether the period is actually locked.

We'll start with the checklist — because that's what you need today — then show you where it runs out.

The Complete Month-End Close Checklist

This checklist is organized into three phases that mirror how well-run accounting teams actually close. Each task includes the typical owner and what it depends on — because the order matters as much as the list.

Phase 1 — Pre-Close Preparation (Days 1–2)

Pre-close is about cutting off inflows so the execution phase has clean data to work with.

• Enforce AP/AR cut-off dates — Owner: Controller. No dependencies. Set hard deadlines for invoice submission and payment recording. Late entries go to the next period.
• Collect outstanding invoices and receipts — Owner: AP Clerk. Depends on: cut-off communication. Chase down any invoices that arrived after the cut-off but relate to the closing period.
• Verify bank feed completeness — Owner: Staff Accountant. No dependencies. Confirm that all bank transactions through the last day of the period have been downloaded and are available in the GL.
• Confirm intercompany balances — Owner: Senior Accountant. No dependencies. Reconcile intercompany receivables and payables with counterparty entities. Resolve discrepancies before execution begins.
• Review open purchase orders — Owner: AP Clerk. No dependencies. Identify POs that should have been received and accrued. Flag any that need to be carried forward or closed.

Phase 2 — Execution (Days 3–5)

Execution is where the real work happens. These tasks have dependencies — you can't reconcile the bank until the feeds are confirmed, and you can't run the trial balance until reconciliations are complete.

• Reconcile bank accounts — Owner: Staff Accountant. Depends on: bank feed verification (Phase 1). Match every transaction. Investigate and resolve all reconciling items.
• Reconcile credit cards and petty cash — Owner: Staff Accountant. Depends on: bank feed verification. Same rigor as bank reconciliation. Ensure all charges are properly coded and receipts are attached.
• Review and post adjusting journal entries — Owner: Senior Accountant. Depends on: reconciliations. Prepaid amortizations, accrued liabilities, deferred revenue adjustments. Each entry needs a memo explaining the why.
• Reconcile subledgers to the general ledger — Owner: Senior Accountant. Depends on: JE posting. AR, AP, inventory, and fixed asset subledgers must tie to their GL control accounts. Investigate and resolve differences.
• Accrue known expenses — Owner: Senior Accountant. Depends on: AP cut-off. Services received but not yet invoiced. Utilities, professional fees, contract labor — estimate and accrue.
• Verify revenue recognition entries — Owner: Senior Accountant / Controller. Depends on: AR reconciliation. Confirm revenue is recognized in the correct period per ASC 606 or your applicable framework.
• Review fixed asset depreciation — Owner: Staff Accountant. Depends on: asset register updates. Run depreciation, verify new additions and disposals are reflected, confirm accumulated depreciation balances.
• Reconcile payroll clearing accounts — Owner: Staff Accountant. Depends on: payroll processing completion. Confirm all payroll-related liabilities (taxes, benefits, net pay) have cleared properly.

Phase 3 — Review & Close (Days 6–7)

Review is where the controller takes ownership. Everything upstream must be complete before this phase begins.

• Run the trial balance — Owner: Senior Accountant. Depends on: all Phase 2 reconciliations and JEs. Verify debits equal credits. Scan for unusual balances or unexpected movements.
• Perform flux analysis — Owner: Controller. Depends on: trial balance. Compare P&L line items month-over-month and against budget. Document explanations for variances exceeding your materiality threshold (typically 5–10%).
• Manager/controller review and sign-off — Owner: Controller. Depends on: flux analysis. Review the complete close package. Sign off that the period is accurate and complete.
• Lock the period — Owner: Controller. Depends on: sign-off. Prevent any further postings to the closed period. This is non-negotiable — an unlocked period is an unfinished close.
• Generate financial statements — Owner: Controller. Depends on: period lock. Balance sheet, income statement, cash flow statement. These are your deliverables.
• Archive supporting documentation — Owner: Senior Accountant. Depends on: financial statements. Bank reconciliations, journal entry support, variance explanations, sign-off records. This is your audit trail.

Task Dependencies: What Blocks What

The tasks above aren't a flat list — they're a directed graph. Understanding the dependencies is what separates a five-day close from a nine-day close.

Here's what actually blocks what:

• Bank feed verification gates every reconciliation in Phase 2. If your bank feeds aren't confirmed by end of Day 2, your entire execution phase slides.
• AP cut-off gates expense accruals. If AP is still accepting invoices on Day 4, your accruals will be incomplete and your trial balance will be wrong.
• Reconciliations gate journal entries. You can't post meaningful adjustments until you know what the actual balances are.
• All of Phase 2 gates the trial balance. Running a trial balance before reconciliations are complete is a waste of time — you'll just have to run it again.
• Trial balance gates flux analysis. You can't explain variances against a trial balance that isn't final.
• Flux analysis gates controller sign-off. The controller needs to see the variances and their explanations before they'll sign off.

A flat checklist hides these dependencies. Your staff accountant marks "bank reconciliation — done" but the bank feeds weren't actually confirmed, so the reconciliation is built on incomplete data. Nobody notices until the trial balance doesn't tie on Day 6, and now you're starting over.

This is why close management — tracking not just what is done, but what is now unblocked — matters once your team is bigger than one person.

Where Month-End Closes Actually Break

If you've run a few dozen closes, you'll recognize these scenarios. They're not exotic — they're the mundane failures that add two or three days to every close.

The missing vendor invoice. A vendor sends their invoice on the 5th of the following month. AP already cut off. Do you accrue it? Reopen the period? Post it to the next month and explain the variance? The answer depends on materiality, but the problem is that nobody owned the follow-up. An accrual reminder tied to the AP cut-off task would have caught it.

The intercompany balance that doesn't tie. Your subsidiary recorded $47,200 in intercompany payables. Your parent shows $45,800 in the corresponding receivable. The $1,400 difference could be a timing difference, a missed entry, or an error. Without a formal intercompany reconciliation step with a named owner, this discrepancy gets discovered during the trial balance review — three days later than it should have been.

The journal entry posted after period lock. Someone posts an adjustment after the controller signed off. If your system doesn't enforce period locks, the financial statements you delivered to the board are now stale. This is an audit finding waiting to happen.

The "done" task with no evidence. A staff accountant marks the bank reconciliation complete. The auditor asks to see it. There's nothing attached — no reconciliation report, no screenshots, no sign-off. The work might have been done correctly, but without evidence, it might as well not have been done at all.

These aren't checklist problems. They're coordination problems — task ownership, dependency tracking, evidence collection, and period control. A spreadsheet checklist can't solve them because a spreadsheet doesn't enforce anything.

From Checklist to Close Management

A month-end close checklist is a fine starting point. If you're a solo bookkeeper handling fewer than 20 tasks, a well-maintained spreadsheet will serve you for a long time.

But if any of these are true, you've outgrown the spreadsheet:

• Your team has three or more people working on the close
• Auditors are asking for evidence you can't easily produce
• You have more than 30 tasks per close period
• You're spending time chasing status updates instead of reviewing work
• Tasks get marked "done" without supporting documentation

Close management means tracking the full lifecycle: task assignments with named owners, dependency chains that show what's blocked and what's ready, period locking that prevents post-close tampering, sign-off workflows that create an audit trail, and evidence collection attached to every task.

This is what ComplyBar was built for — not to replace your checklist, but to make it load-bearing. Task dependencies show your team what they can work on right now. Period locking prevents the "journal entry after sign-off" problem. Every task carries its evidence, so when the auditor asks, you have an answer in seconds, not hours.

At $10/user/month for your accounting team and $1/month for view-only users like auditors and CFOs, it's built for the teams that FloQast and BlackLine price out.

Month-End Close Best Practices

Standardize the Sequence

Run the same tasks in the same order every month. Standardization reduces errors, cuts training time for new hires, and makes it obvious when something is off. If your close looks different every month, you don't have a process — you have a series of emergencies.

Assign Owners, Not Teams

Every task gets one name, not "accounting department." When a task is owned by a team, nobody owns it. Assign the specific person responsible for completion, and make that assignment visible to the whole team.

Set Hard Cut-Off Dates

AP and AR cut-offs aren't suggestions — they're deadlines. Communicate them a week before month-end. Enforce them. Late entries go to the next period unless they meet your materiality threshold for adjustment. Every day of slack in your cut-off adds a day to your close.

Run a 15-Minute Post-Close Retro

After every close, spend 15 minutes answering three questions: What caused delays? What required rework? What went smoothly? Document the answers. Over six months, you'll have a clear map of your process's structural weaknesses — not guesses, evidence.

Benchmark Your Close

Track your days-to-close every month. The median is 6.4 days. High-performing teams close in 3–5. If you're consistently above 7, your process has a bottleneck worth finding. Plot it over time — the trend matters more than any single data point.

Free Month-End Close Checklist Template

We've built the three-phase checklist from this guide into a ready-to-use template. It includes every task from Phases 1–3, with columns for owner assignment, due dates, dependencies, status tracking, and evidence links.

Sign up for ComplyBar's free trial to get the interactive version with built-in dependency tracking, or use our 90-day free trial to run your next close with full task management.

Frequently Asked Questions

How long should a month-end close take?

High-performing teams close in 3–5 business days. The median across all finance teams is 6.4 calendar days. If you're consistently taking more than 7 business days, you likely have a process bottleneck — usually in reconciliations or waiting for information from other departments.

What are the steps in a month-end close?

The close follows three phases: (1) pre-close preparation — enforcing cut-offs, collecting outstanding items, confirming data feeds; (2) execution — reconciliations, journal entries, accruals, revenue verification; (3) review and close — trial balance, flux analysis, controller sign-off, period lock, financial statement generation.

How do you automate the month-end close?

Start with the highest-leverage automation points: bank feed imports, recurring journal entries, and task assignment/reminders. Reconciliation matching can be partially automated for high-volume accounts. Be cautious about automating judgment-heavy tasks like flux analysis — automation should handle the data gathering so your team can focus on the analysis.

What's the difference between a close checklist and close management software?

A checklist is a list of tasks. Close management software adds dependency tracking (which tasks block which), period locking (preventing post-close entries), evidence collection (attaching reconciliation reports to tasks), sign-off workflows (audit-ready approval chains), and team coordination (who's blocked, who's done, what's next). A checklist tells you what to do; close management tells you what you can do right now.

What should a month-end close policy include?

At minimum: cut-off dates and their enforcement rules, the complete task list with named owners, an escalation path for blockers, evidence requirements per task type (what documentation must be attached), the review and sign-off workflow, and the close calendar for the full fiscal year.