Month End Close Checklist: A Step-by-Step Template
July 2026 · Reconciler
A month end close checklist is an ordered list of the accounting tasks required to finalize one period's books, assigned to an owner and a target day, so nothing gets missed and the close finishes on schedule. The core sequence is the same in almost every US company: cut off the period, finish the subledger work (AP, AR, payroll, expenses), reconcile every cash and clearing account, post accruals and adjusting entries, review the variances, then issue the financials and sign off. Most small and mid-sized teams should be closing in 5 to 10 business days, and the teams that close fastest are the ones that reconcile continuously instead of saving it all for the last two days.
Last updated July 2026.
What is the month end close process?
The month end close process is the recurring set of procedures accountants perform after a period ends to make sure the general ledger is complete, accurate and supportable under GAAP. It covers cutoff, subledger reconciliation to the GL, bank and processor reconciliations, accruals and adjusting entries, review, and the issuance of financial statements.
Think of it as three jobs stacked on top of each other. First, you're making the ledger complete: every invoice, bill, payroll run and card charge that belongs to June is actually in June. Second, you're making it accurate: cash agrees to the bank, Stripe payouts agree to the clearing account, the AR subledger agrees to the control account. Third, you're making it explainable: someone can ask why gross margin dropped 180 basis points and you have an answer that isn't a shrug.
The reason closes drag is almost never the entries themselves. It's the tie-outs. Reconciliations are the step everyone defers, and deferred reconciliations are what turn a clean Day 4 into a chaotic Day 9.
What are the steps in the month end close checklist?
The steps are: (1) pre-close and cutoff, (2) subledger and transaction work across AP, AR, payroll and expenses, (3) reconciliations of bank, credit card, payment processor and balance sheet accounts, (4) accruals, prepaids, depreciation and adjusting entries, (5) review, variance analysis and flux, and (6) reporting and sign-off. Below is the full checklist, phase by phase, with an owner and a target day.
The month end close checklist (copy this)
| Phase | Task | Owner | Day |
|---|---|---|---|
| 1. Pre-close / cutoff | Publish the close calendar and communicate the cutoff date to every department | Controller | Pre-close |
| 1. Pre-close / cutoff | Freeze the prior period in the ledger; restrict posting permissions | Controller | Day 1 |
| 1. Pre-close / cutoff | Chase outstanding employee expense reports and corporate card receipts | Staff Accountant | Pre-close |
| 1. Pre-close / cutoff | Confirm all bank feeds, processor connections and integrations synced through the last calendar day | Staff Accountant | Day 1 |
| 1. Pre-close / cutoff | Roll forward last month's open items list and unresolved exceptions | Accounting Manager | Day 1 |
| 2. Subledger: AP | Enter all vendor invoices received for goods and services delivered in the period | AP Clerk | Day 1 |
| 2. Subledger: AP | Review the unbilled receipts / GRNI report and accrue for goods received not invoiced | AP Clerk | Day 2 |
| 2. Subledger: AP | Reconcile the AP aging to the AP control account in the GL | Staff Accountant | Day 3 |
| 2. Subledger: AR | Issue all customer invoices for the period; confirm revenue cutoff on shipments and deliveries | Billing | Day 1 |
| 2. Subledger: AR | Apply cash receipts, clear unapplied payments, review AR aging | AR Clerk | Day 2 |
| 2. Subledger: AR | Reconcile AR aging to the AR control account; update the allowance for credit losses | Staff Accountant | Day 3 |
| 2. Subledger: Payroll | Record final payroll register, employer taxes and benefit deductions | Payroll | Day 2 |
| 2. Subledger: Payroll | Accrue unpaid wages for days worked but not yet paid; accrue PTO and bonus | Staff Accountant | Day 3 |
| 2. Subledger: Expenses | Post approved expense reports; code and post corporate card transactions | Staff Accountant | Day 2 |
| 3. Reconciliations | Reconcile every operating and payroll bank account to the statement; document outstanding checks and deposits in transit | Staff Accountant | Day 2 |
| 3. Reconciliations | Reconcile corporate credit card statements to the GL liability balance | Staff Accountant | Day 3 |
| 3. Reconciliations | Reconcile payment processors (Stripe, PayPal, Square): gross sales, fees, refunds, chargebacks and payouts to the clearing account | Staff Accountant | Day 3 |
| 3. Reconciliations | Clear the undeposited funds / payments clearing account to zero or explain the residual | Staff Accountant | Day 3 |
| 3. Reconciliations | Reconcile intercompany balances and eliminate | Accounting Manager | Day 4 |
| 3. Reconciliations | Reconcile every remaining balance sheet account with support attached (schedules, statements, amortization tables) | Staff Accountant | Day 4 |
| 4. Adjusting entries | Post recurring accruals: rent, utilities, professional fees, commissions, unbilled vendor spend | Staff Accountant | Day 4 |
| 4. Adjusting entries | Amortize prepaid expenses (insurance, software, deposits) per the prepaid schedule | Staff Accountant | Day 4 |
| 4. Adjusting entries | Record depreciation and amortization; roll the fixed asset register and post additions and disposals | Staff Accountant | Day 4 |
| 4. Adjusting entries | Record deferred revenue movements and revenue recognition entries (ASC 606) | Accounting Manager | Day 4 |
| 4. Adjusting entries | Post inventory adjustments, COGS entries and any reserve true-ups | Accounting Manager | Day 5 |
| 4. Adjusting entries | Record income tax provision estimate and state / sales tax accruals | Controller | Day 5 |
| 5. Review and flux | Run the preliminary trial balance; scan for negative balances, wrong-sign accounts and suspense entries | Accounting Manager | Day 5 |
| 5. Review and flux | Perform flux analysis: month over month and versus budget, on every P&L line above the materiality threshold | Accounting Manager | Day 6 |
| 5. Review and flux | Write a one-line explanation for each variance over threshold; chase the department owner for the rest | Controller | Day 6 |
| 5. Review and flux | Review balance sheet reconciliations, confirm every reconciling item has support and an aging | Controller | Day 6 |
| 6. Reporting and sign-off | Lock the period; no further posting without controller approval | Controller | Day 7 |
| 6. Reporting and sign-off | Produce the financial statements: P&L, balance sheet, cash flow statement | Controller | Day 7 |
| 6. Reporting and sign-off | Deliver the management reporting package with commentary and KPIs | Controller / CFO | Day 8 |
| 6. Reporting and sign-off | Archive support, reconciliations and journal entry approvals for audit | Accounting Manager | Day 8 |
| 6. Reporting and sign-off | Hold the close retro: what slipped, why, what changes next month | Controller | Day 8 |
Two notes on using this as a month end close template. First, the day numbers are targets, not physics. If you're a 15 person company with one bank account, you'll compress phases 2 and 3 into a single day. If you have four entities and inventory, phase 4 alone can take two days. Second, every row needs a named human, not a department. "Accounting" is not an owner.
Pre-close: the work that happens before the month ends
The cheapest day to save is the one before the period closes. Send the cutoff reminder in the last week, not on the first. Ask department heads to submit expense reports and confirm any large committed spend that hasn't been invoiced. Get the AP inbox to zero. A close that starts with a clean inbox and no missing receipts starts two days ahead of one that doesn't.
AP is where this bites hardest, because the bills you haven't seen yet are the ones that force restatements of the accrual. If AP is the step that always runs late in your close, automating vendor invoice intake and coding removes most of the day-two crunch, because the bills are already in the system and coded before the period ends rather than being keyed in after it.
How long should the month end close take?
Most US private companies close in 5 to 10 business days. A well-run mid-market finance team with clean integrations and continuous reconciliation should target 5 business days for a full hard close, and 1 to 3 days for a soft close. Public companies work to much tighter deadlines because of filing requirements, and some run a 3 day close.
The honest answer is that the number matters less than the trend and the quality. A 4 day close with three unexplained suspense balances is worse than a 7 day close that ties out completely. What you want is a close where the day count is stable, the exceptions list is short, and nothing is being fixed in the following month.
If your close runs past 10 business days, the cause is usually one of four things: reconciliations start too late, one person is a bottleneck for everything, the ledger is being reconciled against spreadsheets that someone maintains by hand, or the review step keeps finding errors that push you back into phase 2. All four are fixable.
What is the difference between a soft close and a hard close?
A soft close is a fast, estimate-driven close used for internal management reporting: you post the material accruals, skip immaterial adjustments, and don't fully reconcile every account. A hard close is the complete version: every account reconciled with support, every adjusting entry posted, and financials produced to a standard an auditor would accept.
Many teams run soft closes in months 1 and 2 of a quarter and a hard close at quarter end. That works if you're disciplined about what gets deferred. It fails when "soft" quietly becomes "we stopped reconciling cash," and then quarter end turns into a three week archaeology project. If you soft close, write down exactly which procedures you're skipping and which you never skip. Bank and processor reconciliation belongs in the never-skip column, because those are the accounts where an unnoticed error compounds silently.
Where closes actually slip
In practice the delay concentrates in a few predictable places.
- Reconciliations left to the end. Teams treat reconciliation as a verification step at the end of the close, when it's really a data quality step that should run continuously. If you find a missing deposit on Day 6, you're re-opening subledger work you thought was done.
- Payment processor clearing accounts. Stripe, PayPal and Square settle net of fees, on a lag, with refunds and chargebacks landing in different periods than the original sale. The gross-to-net unwind is where a lot of "we're off by $312 and nobody knows why" comes from.
- Manual spreadsheet tie-outs. The VLOOKUP that reconciles the processor export to the bank export is the single most fragile artifact in most closes, and it usually lives on one person's laptop.
- Unexplained variances. Flux analysis stalls when the accountant has the number but not the story, and has to email three department heads and wait.
- Review finding errors. If the controller's review routinely sends work back, the problem is upstream: the preparer doesn't have the checklist, the support standard, or the time.
How can I close the books faster?
Close faster by moving work earlier and by automating the matching. Reconcile continuously through the month instead of in a Day 5 sprint, standardize a checklist with named owners and hard dates, cut the number of manual journal entries by using recurring templates, and let software do the transaction-level matching so your people only touch the exceptions.
Concrete moves, in the order they usually pay off:
- Reconcile daily or weekly, not monthly. The volume is the same, but you find problems while the context is fresh and while the counterparty still remembers the transaction. This alone removes the most common source of Day 8 surprises.
- Automate the matching layer. Human beings should not be eyeballing thousands of lines. Automated transaction matching handles the identical, one-to-one, obvious matches (which are the vast majority), so the team spends its time on the handful that don't tie.
- Make exceptions a queue, not a hunt. A running list of open items with an owner and an age beats a fresh investigation every month. Discrepancy detection that flags missing entries and amount mismatches as they happen turns the close into triage instead of search.
- Standardize journal entries. Recurring accruals, prepaid amortization and depreciation should be templates with an approved schedule, not fresh calculations.
- Set a materiality threshold for flux, and publish it. If you explain every $400 swing, you'll never finish. Pick a dollar and percent threshold, get it approved, and stop below it.
- Pre-write the variance explanations. The commentary for known items (a new hire, an annual insurance payment, a marketing campaign) can be drafted before the numbers land.
- Kill the reconciliation spreadsheet. Anything that depends on one person's file is a single point of failure and an audit finding waiting to happen.
Where Reconciler fits
Reconciler sits on top of the ledger you already use. It connects your bank feeds, payment processors (Stripe, PayPal, Square) and accounting system (QuickBooks, Xero, NetSuite) with read-only access, matches transactions automatically across both sides, flags discrepancies and missing entries, and explains every match in plain English so a reviewer can accept or reject it in seconds. It never moves money and never auto-posts. A person reviews every exception, and every decision leaves an audit trail your auditor can follow.
That's deliberately a narrow job. It doesn't replace your ERP and it isn't a close management suite. It attacks phase 3, which is the phase that most often blows the schedule. If you want the mechanics, how it works walks through the connection and review flow, and there's more on the month end close workflow and what it looks like for controllers specifically. Plans start at $49/mo (Starter), with Growth at $149/mo and Scale at $399/mo; see pricing for the details.
Month end close best practices worth stealing
- One checklist, one source of truth. Not a Word doc on a share drive that three people have forked.
- Owner and due day on every line. Unowned tasks slip by definition.
- Support attached at the time of reconciliation, not gathered later for the auditor. Retrieving support six months on costs multiples of what it costs to attach it in the moment.
- A standing exceptions list with aging. Anything open more than 60 days is a decision, not a mystery. Write it off or escalate it.
- A close retro every month. Fifteen minutes. What slipped, why, what one change do we make. Closes get faster by attrition of small problems, not by heroics.
- Protect the review step. If review gets compressed because prep ran long, you've traded accuracy for a date, and you'll pay it back next month.
A month end close checklist is a coordination tool, not a compliance ritual. The version that works is the one your team actually opens on Day 1, marks off in real time, and argues about in the retro. Start with the table above, delete what doesn't apply to you, add the three things that always bite your company specifically, and put a name next to every row. For teams running this across multiple entities or a growing transaction volume, the reconciliation phase is the first place to look, and it's what finance teams most often automate first.
This article is general information, not financial, accounting or tax advice. Consult your CPA or advisor about your specific circumstances.
See your accounts tie out to $0.00
Connect your bank, processors and ledger read-only. Reconciler matches transactions, flags what does not add up, and explains every match, so your books close faster. Read-only, never moves money.