Month-end close checklist: 12 steps to close the books faster

Finance teams are under real pressure to speed up the month-end close, but median performers take at least six business days, while bottom performers need 10 or more, according to data from APQC.

A structured checklist with named owners and deadlines is one of the fastest ways to close that gap. It moves work upstream, catches late inputs before they land in the period-end window, and gives controllers a clear view of where the cycle stands at any point in the month.

What month-end close is — and why it matters

The month-end close is the structured process of finalizing all financial transactions for a period and producing accurate financial statements. It covers posting outstanding transactions, reconciling accounts, recording accruals and adjusting entries, reviewing results against budget, and locking the period. Done well, it gives leadership trustworthy numbers for decisions, supports compliance requirements such as Sarbanes-Oxley Section 404 documentation for public companies, and helps keep financial controls intact.

Manual processes usually stretch the timeline. When accountants pull balances out of spreadsheets and card portals by hand, the assembly work bunches up inside the period-end window. When expense reports, invoices, and card statements arrive late or uncoded, controllers spend the first days of the cycle assembling data before they can review it.

The controller or accounting manager typically owns the process and final sign-off. Accounting staff executes the tasks, the CFO provides oversight, and FP&A typically partners on variance analysis. Ownership only helps when it’s assigned task by task.

The 12-step month-end close checklist

The checklist below organizes the close into three phases. Each step needs a named owner and a due date. If your team runs the same cycle every month without knowing who owns a particular task, that’s usually where the delay compounds.

Pre-close (before the last business day)

1. Set cutoff dates for invoices and expense reports. Communicate them at least a week ahead, so your submitters have time to comply. Without a firm cutoff, late submissions become the default rather than the exception, and each one pushes assembly work into days you meant to spend reviewing, not chasing paperwork.

2. Chase open items and confirm submission deadlines. Send reminders to your expense submitters, AP approvers, and any team owing supporting documentation. One unconfirmed deadline or missing approval can stall the entire execution phase, since reconciliation cannot begin until the inputs it depends on are actually in hand.

3. Assign an owner and due date to every close task. A task without an owner is a task nobody does. Publish the assignments where your team can see them. Diffused ownership is a most common reason that a close drags on: When a step belongs to “the team” instead of a person, nobody notices it’s late until it blocks something further down the checklist.

Execution (the core close)

4. Validate subledger balances to the general ledger. Investigate timing differences between when a transaction hit the subledger and when it was posted to the GL. Small timing gaps here are easy to miss, but if they carry into later steps, you end up building the rest of the close on a balance that was never right to begin with.

5. Post pending transactions. Approved expense reports, journal entries, and any other outstanding items should be posted before reconciliation begins. Reconciling against an incomplete ledger creates mismatches that look like errors but are really just postings that have not happened yet, and chasing them wastes hours you could spend on real discrepancies.

6. Reconcile bank and credit card accounts. Match recorded balances to statements and investigate discrepancies. This is the step that confirms your cash and card position is actually accurate, and it’s usually where duplicate charges, missed refunds, or timing gaps first surface.

7. Prepare accruals and adjusting entries. Include depreciation expenses and deferrals. Accruals for goods or services received but not yet invoiced are estimated from historical patterns and reversed when the invoice arrives. Skip or rush this step and the close can look finished while it is not: Costs incurred during this period simply will not show up until the invoice arrives, understating what the period actually cost.

8. Verify GL coding and cost-center assignments. Do this before the period locks, so your team can correct miscoded expenses and cost-center transfers in-period. Catch a coding error before lock and it’s a quick fix; catch it after and you’re reopening a closed period, which is slower and can throw off the variance analysis you’re about to run.

9. Review the balance sheet and income statement. Run variance analysis against budget and prior periods; flag VAT and other indirect tax items for review. This is the review that catches what earlier steps missed. Skip it and a coding error or missed accrual can ride straight through into the numbers leadership sees.

10. Lock the period once adjustments are posted. Locking the period is what keeps a number you have already reported from quietly changing later, since it blocks any new entry from landing in a period that is supposed to be finished.

Post-close (after the period closes)

11. Obtain controller sign-off and distribute final statements. Send the reporting package to leadership and archive the version distributed. Sign-off is the formal record that someone reviewed and stands behind these numbers, and that record is exactly what an auditor or a leader will ask for later.

12. Archive workpapers and hold a brief post-mortem. Note what slowed the cycle down and assign someone to fix it before your next close. Skip this step and the same bottleneck usually resurfaces next month, because nobody owns fixing it, and workpapers scattered across inboxes are hard to reconstruct months later when an auditor asks.

Working the same checklist every month, with the same owners and cutoffs, gives the cycle a rhythm. That’s often the difference between a close that wraps up on schedule and one that drags for days.

How automation can speed up the month-end close

Automation can shorten the cycle by moving work upstream, so transactions arrive coded and matched, with documentation attached, before period-end even starts. In The State of Corporate Travel and Expense 2026, a report from Skift and Navan, 80% of T&E managers surveyed said they’re confident in the data their organization can access, yet only 40% have real-time visibility into that data. Automation can close that gap by capturing data as it happens rather than assembling it after the fact.

In the same Skift and Navan report, 29% of T&E managers surveyed still process expense reports manually. Each manual workflow adds a dependency that accounting has to clear during period-end itself. The same pattern drives accounts payable automation: Moving structured data upstream can remove cleanup work later in the cycle.

When spend data only reaches finance after the period closes, auditing that data consumes real time every cycle. A Total Economic Impact™ study conducted by Forrester Consulting, commissioned by Navan and based on a composite organization, found that the composite organization cut the time previously spent auditing expenses by 40%. Accountants keep the judgment calls on material variances and real exceptions. They also own final sign-off.

T&E shows how this works in practice. Expense data typically feeds the cycle through several manual steps: receipts submitted after trips end, coding applied by an approver days later, and card statements reconciled against submitted reports at period-end. When coded transaction data syncs straight to your ERP, it reaches accountants already labeled with GL codes and cost centers through AI-driven spend monitoring.

Navan Expense captures 130-plus data points per transaction at the point of swipe. These include merchant details and accounting assignments such as the GL code and cost center, so automated card reconciliation can happen throughout the period.

Common bottlenecks and how to address them

Close delays typically trace back to the same handful of causes. Naming them explicitly is the first step to fixing them.

• Late or uncoded expense reports and card charges. Set clear submission cutoffs and use tools that capture coding at the point of swipe, so card data and expense reports arrive labeled and ready for review.
• Manual bank and card matching. This is often the first-day workload that pushes everything else back for your team. Direct card feeds and automated matching can reclaim days.
• Cross-team dependencies. Waiting on other departments to confirm balances or approve items is a common close blocker. Named owners and published deadlines make dependencies visible before they hold anything up.
• Manual accruals for T&E. Late receipts force a guess every month, corrected only after the fact. Real-time capture can remove the guesswork.

None of these are new problems, but they’re easier to address once your team can see which one is doing the most damage this month.

Making the close a routine, not a scramble

A month-end close that keeps running late rarely comes down to one big problem. It’s almost always a handful of small ones, repeating every month because nobody assigned an owner or moved the input upstream before it became urgent.

Start with the checklist above and whichever bottleneck is costing you the most right now. If your team keeps losing the first few days to bank and card matching, a direct feed can close that gap faster than any reminder email. If expense reports are your holdup, capturing that data at the point of swipe can mean it’s already coded and matched by the time you need it, instead of something you have to chase.

Once you can see where your hours actually go each month, closing the books stops being something your team survives and starts being something you run on schedule.