What the month-end close is for
Every month, someone outside the finance team relies on the numbers: a CEO deciding on hiring, a board reviewing burn, a lender testing a covenant, a sponsor comparing portfolio companies. The close is the process that makes those numbers complete, accurate and defensible before anyone uses them.
A close does three jobs:
- Completeness. Everything that belongs in the month is recorded: every bill, every invoice, every payroll run, every accrual for work done but not yet billed.
- Accuracy. Every balance on the balance sheet is proven against something independent: a bank statement, a subledger, a schedule, a contract.
- Explanation. Every material movement has a reason a reviewer can check, not a restatement of the number.
When all three are done, the period is locked and nobody posts to it again without an approved reopen.
The seven stages of a month-end close
Most closes follow the same order, whatever the company size or ERP. The order matters because each stage depends on the one before it: you can't explain a variance on an account that hasn't been reconciled.
1. Cut-off and accruals (BD1 to BD2)
Make sure every transaction lands in the right month. That means:
- Recording bills received in the first days of the new month that relate to the old one.
- Accruing for services received but not yet billed (legal, hosting, contractors, utilities).
- Checking shipments and deliveries around month-end for revenue cut-off.
- Reversing last month's auto-reversing accruals.
What a reviewer checks: recurring vendors with no bill this month, and the basis for each accrual estimate. Our free Accrual Finder skill for Claude finds the first automatically → /claude-skills/accrual-finder.
2. Subledger close (BD1 to BD3)
Close the detailed ledgers that feed the general ledger: accounts payable, accounts receivable, payroll, fixed assets, inventory and revenue schedules.
- AP: all approved bills entered, payment runs recorded.
- AR: all invoices issued, cash receipts applied.
- Payroll: the payroll register agrees to the GL by department.
- Fixed assets: additions capitalized, depreciation run.
- Revenue: deferred revenue schedule updated for new contracts and recognition.
What a reviewer checks: each subledger total ties to its control account in the GL, to the cent.
3. Account reconciliations (BD2 to BD4)
Prove every balance sheet account against an independent source. Cash first, because cash is the account everyone else depends on.
| Account | Independent source | Typical owner |
|---|---|---|
| Cash (each bank account) | Bank statement | Staff accountant |
| Accounts receivable | AR aging | AR lead |
| Prepaid expenses | Prepaid schedule | Staff accountant |
| Fixed assets | Asset register | Senior accountant |
| Accounts payable | AP aging | AP lead |
| Accrued liabilities | Accrual schedule | Senior accountant |
| Deferred revenue | Revenue schedule | Revenue accountant |
| Debt | Lender statement | Controller |
| Intercompany | Counterparty entity's balance | Controller |
| Equity | Cap table, board minutes | Controller |
What a reviewer checks: support dated the same day as the GL balance, every reconciling item explained with an owner and a due date, and no items older than 60 to 90 days without a reason. See how a bank reconciliation is structured → /resources/bank-reconciliation-excel-template. For multi-entity groups → /resources/intercompany-reconciliation.
4. Flux analysis (BD4 to BD5)
Compare every account to last month (and to budget) and explain every change above your threshold. A common threshold is "over $25,000 and over 10%", adjusted down for higher-risk accounts.
A useful explanation names the transaction behind the change:
Marketing up $48,200 (31%): annual conference sponsorship, invoice INV-2291 for $45,000, posted 14 Oct.
A useless one restates the number:
Marketing up due to higher marketing spend.
What a reviewer checks: each explanation is specific, backed by a document, and covers most of the change.
5. Adjusting entries (BD5)
Post the entries the earlier stages found: reclasses, true-ups, corrections, missed accruals. Each entry needs a preparer, a reviewer and support attached.
What a reviewer checks: no entry approved by the person who prepared it, and nothing posted after the period was locked.
6. Review and sign-off (BD5 to BD6)
The controller reviews the reconciliations, flux and adjustments; the CFO signs off the period. Then the period is locked in the ERP.
What a reviewer checks: every checklist item has a preparer sign-off and a separate reviewer sign-off, dated on or before the lock date.
7. Reporting (BD6 to BD10)
Produce the management pack, the board pack, the sponsor or lender report and any covenant certificates, all from the locked numbers.
What a reviewer checks: every figure in the pack ties to the closed trial balance. For PE-backed companies, see what a sponsor monthly pack contains → /blog/pe-portfolio-reporting-monthly-pack.
A sample close calendar
Here is a realistic calendar for a mid-market company with one or two entities, closing October 2026. October 31 is a Saturday, so business day 1 (BD1) is Monday 2 November.
| Business day | Date | Stage | Done when |
|---|---|---|---|
| BD1 | Mon 2 Nov | Cut-off, accrual review, reversals | All October bills entered; accrual list drafted |
| BD2 | Tue 3 Nov | Subledgers: AP, AR, payroll | Subledgers tie to control accounts |
| BD3 | Wed 4 Nov | Cash and AR reconciliations | All bank accounts reconciled to $0.00 difference |
| BD4 | Thu 5 Nov | Remaining balance sheet recs; flux draft | All recs prepared; flux explanations drafted |
| BD5 | Fri 6 Nov | Adjusting entries; flux review | Entries posted with support; flux reviewed |
| BD6 | Mon 9 Nov | Controller review; CFO sign-off; period lock | Period locked in the ERP |
| BD7 to BD10 | Tue 10 to Fri 13 Nov | Management, board and sponsor reporting | Packs sent; figures tie to locked TB |
Build your own calendar backwards from your hardest external deadline, usually the board pack, lender report or sponsor pack.
Who owns what
| Role | Owns | Reviews |
|---|---|---|
| Staff accountant | Cash recs, prepaids, accrual entries | — |
| Senior accountant | Balance sheet recs, fixed assets, flux drafts | Staff accountant's recs |
| AP / AR leads | Subledger close, agings | — |
| Controller | Close calendar, adjustments, intercompany, equity | All recs, flux, entries |
| CFO | Sign-off, reporting narrative | Controller's review, packs |
In smaller teams one person holds several roles. The rule that never bends: the preparer and the reviewer of the same item are different people. If your team is too small for that, use a detailed review by an outside accountant as the compensating control.
How long should a month-end close take?
There is no universal right answer, and benchmarks vary widely by source, industry and entity count. Two practical rules work better than any benchmark:
- Track your own days to close for six months before setting a target. Days to close is the number of business days from month-end until the period is locked.
- Look at where the days go. In most teams, two or three tasks (usually cash reconciliations, accruals and flux explanations) cause most of the delay, and they slip in the same place every month.
A faster close only counts if it comes from fewer late adjustments and less rework, not from skipped reviews. If audit adjustments go up as days to close go down, the close got faster by getting worse.
Six ways to speed up the close without weakening it
- Reconcile cash weekly, not monthly. By month-end only the last week's lines are left to match.
- Move accruals to BD1. Use twelve months of AP history to find recurring vendors who haven't billed. Don't wait for someone to remember.
- Set a written flux threshold and stop explaining immaterial movements.
- Standardize reconciliation templates so every reviewer looks in the same place for the same thing.
- Automate the matching, not the judgment. Matching bank lines to ledger lines is rule-based; deciding what an unidentified debit was is not.
- Keep evidence with the work. If a reviewer has to email someone to find support, the close is slower and the audit will be too.
Where automation and AI fit in the close
Automation is most useful where the work is high-volume and rule-based, and least useful where it requires judgment about the business.
| Stage | Good fit for automation | Stays human |
|---|---|---|
| Cut-off and accruals | Finding missing recurring bills, estimating from history | Accruals for new contracts or disputes |
| Subledgers | Ties to control accounts | Policy decisions |
| Reconciliations | Matching, tie-outs, rollforwards | Deciding what a difference means |
| Flux | Finding the GL lines behind a change, drafting commentary | Accepting the explanation |
| Adjustments | Drafting entries from reconciling items | Approving and posting |
| Review | Checking sign-offs, flagging gaps | The review itself |
| Reporting | Building packs from the locked TB | The narrative |
The test for any automated step is the same one an auditor applies: can someone check how the number was produced and get the same answer? That's why Yoraito computes every match, tie-out and variance with SQL that a reviewer or auditor can rerun. The AI drafts the explanation; the query produces the number.
For a full look at agents in the close → /blog/ai-agents-month-end-close.
Common month-end close mistakes
- Reconciling to the wrong date. A bank statement dated the 30th against a GL balance on the 31st.
- "Plugging" differences into a suspense or miscellaneous account to make a reconciliation tie.
- Reviewing a signature, not the work. A reviewer sign-off without notes, tick marks or questions is weak evidence.
- Posting to a closed period because the lock wasn't enforced in the ERP.
- Explaining flux with the number itself.
- Letting reconciling items age. A $500 item from four months ago is usually a $500 error.
The month-end close checklist
Use our free checklist as a starting point. It lists the tasks above by stage, with columns for owner, due business day, preparer, reviewer and status.
[Get the free month-end close checklist →] /resources/month-end-close-checklist