The Month-End Close Checklist, done right.

The month-end close (also called the accounting close process) is the set of procedures a company's finance team performs at the end of every accounting period to verify, adjust, and finalize the financial records before they're locked and reported. The output of close is a trial balance that's accurate enough to build financial statements from — an income statement, a balance sheet, and a cash flow statement that the CFO, the board, lenders, or auditors can rely on.

Close isn't one task. It's a sequence of reconciliations, journal entries, reviews, and sign-offs that all have to land before the books can be called "final." A month-end close checklist is simply the documented, ordered list of every one of those tasks — who owns each one, when it's due, and what "done" looks like. Without a checklist, close becomes tribal knowledge: it lives in one controller's head, and it falls apart the day that controller is on vacation.

Most close checklists are built around three categories of work:

• Sub-ledger close — closing accounts payable, accounts receivable, payroll, fixed assets, and inventory before the general ledger can close.
• Adjusting entries — accruals, deferrals, depreciation, amortization, and reclassifications that align the books with accrual-basis accounting.
• Review and reporting — reconciliations, flux analysis, management review, and the financial statements themselves.

It's worth being precise about one more distinction that trips up a lot of people new to close: a hard close versus a soft close. A hard close completes every task on the checklist in full — every reconciliation, every review, every sign-off — and is what most companies run every month. A soft close (sometimes called a "flash close") is a faster, lighter version run mid-period or for internal-only purposes, where the team estimates a few line items instead of fully reconciling them, just to get management a directionally accurate snapshot. Soft closes are useful for forecasting; they are not a substitute for the real close, and the numbers from a soft close should never be the ones that go to a lender or appear in audited financials.

It also helps to be clear on why accrual-basis accounting requires a close process at all when cash-basis accounting mostly doesn't. Under cash-basis accounting, a transaction is recorded when money actually changes hands — there's very little to "adjust" at period-end because the bank balance and the books are nearly the same thing. Accrual-basis accounting, which is required under GAAP for most companies above a certain size, deliberately separates the timing of cash from the timing of economic activity. That separation is exactly what creates the need for accruals, deferrals, and depreciation — and therefore exactly what creates the need for a close checklist to track them.

Industry benchmarking on close cycles consistently shows the same pattern: top-performing finance teams close their books in roughly 3 to 5 business days, median performers take closer to 6 to 10 days, and laggards can take three weeks or more. The gap between those numbers isn't really about effort. It's about whether the process is documented, standardized, and checked off the same way every single month.

A checklist solves three specific failure modes that show up constantly in real accounting departments:

Notice what doesn't happen: nothing on Day 4 starts before Day 1 through 3 finish. That's the entire logic of a close checklist — it isn't a to-do list, it's a dependency chain. A flux analysis run against an unreconciled trial balance isn't just early, it's wrong, because the numbers it's analyzing haven't been proven yet.

Every task in the five phases above can be done two ways: manually, with spreadsheets, email approvals, and someone remembering to run the report — or with some degree of automation, where the system itself enforces sequencing, deadlines, and review. Neither approach changes what needs to happen during close. It changes how much of the team's time goes toward judgment calls versus mechanical steps.

The mistake many growing companies make is jumping straight to automation tooling before the underlying checklist is even documented. Software can't enforce a sequence that doesn't exist on paper first. The right order is almost always: write the checklist, assign real owners, run it manually for a quarter or two to find the gaps, then automate the pieces that are genuinely repetitive and rules-based — not the judgment calls.

Smaller teams collapse several of these roles into one or two people, and larger teams split each one further — but the underlying responsibilities don't change much by company size. What changes is who's wearing each hat.

Notice the pattern: the further up the chain, the more the role shifts from doing the task to reviewing it. That's not bureaucracy for its own sake — it's the segregation-of-duties principle showing up directly in the checklist's task ownership column. The person who books an accrual should generally not be the same person who approves it, and the person who reconciles a bank account shouldn't be the one with check-signing authority over that same account.

Start small if you need to. Even a single shared document listing the twenty or so tasks that matter most to your business — sub-ledger closes, the core accruals, bank reconciliations, a trial balance review, and a sign-off — will outperform no checklist at all. Add structure as the business grows: more entities mean more eliminations, more revenue streams mean more recognition rules, and more headcount means more reviewers in the chain. The five-phase structure in this guide scales in either direction, from a single-person bookkeeping operation to a multi-entity company preparing for audit.