Guides finance teams through a controlled month-end close - sub-ledger cutoffs, journal entries in dependency order, full balance-sheet reconciliation, flux analysis, and sign-off - targeting a locked close by business day 5-10. Use when someone asks "help me close the books", "build a close checklist", "our close takes three weeks, how do we shorten it", "what order do the journal entries go in", or is preparing for an audit. Do NOT use for constructing or interpreting the financial statements themselves - use financial-statement-builder instead - or for writing the budget-variance narrative that follows the close - use budget-vs-actual instead.
Click to play with sound.
---
name: Month-End Close
description: Guides finance teams through a controlled month-end close - sub-ledger cutoffs, journal entries in dependency order, full balance-sheet reconciliation, flux analysis, and sign-off - targeting a locked close by business day 5-10. Use when someone asks "help me close the books", "build a close checklist", "our close takes three weeks, how do we shorten it", "what order do the journal entries go in", or is preparing for an audit. Do NOT use for constructing or interpreting the financial statements themselves - use financial-statement-builder instead - or for writing the budget-variance narrative that follows the close - use budget-vs-actual instead.
---
# Month-End Close
A fast, clean close is the result of consistent preparation, not heroics at deadline. The failure this skill prevents is the restatement: a late invoice posted after reconciliation, an unreconciled variance carried forward "to fix next month," a flux swing nobody explained that turns out to be a misposted entry. The sequence below has hard checkpoints so nothing slips and the books reflect economic reality.
Target: sign-off and lock by business day 5 for a well-run close; day 10 is the outer acceptable bound. A close consistently past day 10 means the pre-close phase is being skipped - fix the calendar, not the deadline.
## Operating procedure
The order is dependency order, and it is not negotiable: journals before sub-ledger lock, lock before reconciliation, reconciliation before flux, flux before sign-off. Reconciling before the lock guarantees rework; running flux before reconciliation means explaining errors instead of catching them.
### Step 1: Gather inputs (once, when adopting this process)
1. Chart of accounts and entity structure (any intercompany?).
2. Sub-ledger systems for AP, AR, payroll, inventory, and who owns each cutoff.
3. Materiality threshold for reconciliation variances and flux explanations - a common working floor is the greater of 10% line variance or a fixed dollar amount scaled to the business (for example 0.5% of monthly revenue). If none exists, set one now and label it a first guess to be calibrated after two closes.
4. Recurring journal list: depreciation, prepaid amortization, deferred revenue release, payroll accruals.
5. The reporting deadline the close feeds (board package, lender covenant, audit).
### Step 2: Pre-close, days -3 to -1