Executive summary
Monthly close acceleration is the work of getting reliable monthly financials sooner. The close is not valuable for its own sake. It matters because every report that depends on it waits: the management pack, the board pack, the lender package, and the cash forecast update. A close that finishes on business day 18 means the numbers describe a month that ended almost four weeks ago.
Speed comes from fewer dependencies, not from working faster. Most long closes have the same causes: late cutoffs, accruals estimated from scratch every month, reconciliations started only after the books are "done", intercompany items that are matched at the end, and review loops that begin after everything else finishes. The plan below moves each of those earlier, gives every task an owner and a business day, and measures the result.
Ten days is a working target, not a rule. The right target depends on your size, systems, and reporting deadlines. Set it from your own contractual deadlines and your own trailing best, then use the calendar below to see what has to move.
When to use this
Use this guide when:
- The close regularly runs past the day management needs the numbers.
- Lender or investor reporting deadlines are tight against close completion. See the lender reporting package.
- Finance spends the first two weeks of each month on the close and has no time for analysis.
- Adjustments keep arriving after the books are said to be closed.
- A new CFO, a sponsor, or a pending transaction needs reliable monthly numbers faster.
Do not start with speed if the books are unreliable. If balance sheet accounts are unreconciled or the subledgers do not tie to the ledger, fix accuracy first. A faster wrong close is not an improvement.
Diagnostic questions
- On which business day did each of the last six closes finish, and what did "finish" mean (books locked, or pack delivered)?
- How many adjusting entries were posted after the first draft of the financials, and what caused each?
- Which balance sheet accounts are reconciled monthly, by whom, and by which business day?
- Which accruals are recurring and could be set up as templates, versus truly one-off?
- Which subledgers (AP, AR, inventory, fixed assets, payroll) close on which day, and who controls the cutoff?
- How are intercompany balances matched, and when are differences discovered?
- What data arrives from outside finance (operations, sales, HR), on what day, and what happens when it is late?
- How many review loops does the close have, and does the reviewer wait for the whole package or review as items finish?
- Is there a close checklist with owners and due days, and does anyone check it against what actually happened?
- Which tasks are done by one person with no backup?
- How much of the close is manual spreadsheet work that could come directly from the ERP?
- What do your downstream users (board, lenders, managers) actually need, and by when?
Reading the answers: question 2 shows how much of the delay is rework. Question 5 usually points to the real critical path. Question 10 identifies where a vacation or a resignation will break the close.
The framework: the close as a critical path
Treat the close as a project with a critical path, not a list of chores. The critical path is the longest chain of dependent tasks. Only shortening that chain shortens the close.
| Stage |
Purpose |
Typical delay |
Lever |
| 1. Cutoff and subledger close |
Stop transactions and lock the subledgers |
Waiting for late invoices, receipts, timesheets |
Cutoff calendar, daily processing, hard cutoffs |
| 2. Accruals and adjustments |
Capture what is owed or earned but not yet booked |
Rebuilding estimates each month |
Recurring accrual templates, trigger reports, PO-based accruals |
| 3. Reconciliations |
Prove balances |
Starting after the books close |
Continuous or early-month reconciliation, ownership by account |
| 4. Intercompany and consolidation |
Match and eliminate |
Differences found at the end |
Daily or weekly matching, shared cutoff |
| 5. Review and analysis |
Check reasonableness, explain variances |
Review begins after everything else |
Staged review, preset thresholds |
| 6. Reporting |
Produce statements and packs |
Manual rebuild |
Standard templates fed directly from the ledger |
Work from the end backward: set the day the numbers are needed, subtract the reporting, review, and consolidation time, then see what the earlier stages must deliver and when.
Step-by-step process
- Measure the current close. For the last six months, record the day each task finished. Owner: Controller. Output: a task-by-day timeline and a list of adjustments posted after first draft.
- Identify the critical path. Find the chain of dependent tasks that determines the finish day. Owner: Controller. Output: a critical path diagram or table.
- Set the target by method. Use the downstream deadline (for example, the lender delivery date), your own trailing best close, and what the critical path analysis says is reachable in the next quarter. Owner: CFO. Output: a target day and a plan date to reach it.
- Create the business-day calendar. Assign every task an owner, a due business day (BD), and a predecessor. Owner: Controller. Output: the close calendar (template below).
- Hard-wire the cutoffs. Set cutoff times for AP invoices, expense reports, receipts, timesheets, and shipments, and publish them. Escalate misses to the person who owns the source process. Owner: Controller with operations and HR.
- Replace manual accruals with templates. Create recurring accrual entries with a trigger report, such as received-not-invoiced from purchasing and unbilled revenue from operations. Owner: AP lead and Controller.
- Move reconciliations earlier. Assign every balance sheet account to a named preparer and a reviewer, with a due BD. Reconcile high-risk accounts during the month. Owner: Controller.
- Match intercompany continuously. Agree on a weekly matching routine and a single owner for differences. Owner: Controller.
- Stage the review. Review by area as each area finishes, using a preset variance threshold, instead of reading everything at the end. Owner: Controller and FP&A.
- Standardize the pack. Build the management and lender reports directly from the ledger with a fixed template, so reporting is a refresh, not a rebuild. Owner: FP&A.
- Run the retrospective. Within three business days of each close, list the late items, their causes, and one fix per cause. Owner: Controller. Output: a short list reviewed at the next kickoff.
- Lock the calendar. After two or three closes at the new pace, make the calendar the standard and review it quarterly.
Templates
Close calendar (copy into a spreadsheet)
| Task |
Owner |
Backup |
Predecessor |
Due BD |
Actual BD |
Late? |
Cause |
| AP cutoff and subledger lock |
|
|
|
|
|
|
|
| AR billing and subledger lock |
|
|
|
|
|
|
|
| Payroll and benefits accrual |
|
|
|
|
|
|
|
| Recurring accruals posted |
|
|
|
|
|
|
|
| Inventory and COGS true-up |
|
|
|
|
|
|
|
| Fixed asset and depreciation run |
|
|
|
|
|
|
|
| Balance sheet reconciliations |
|
|
|
|
|
|
|
| Intercompany match and eliminate |
|
|
|
|
|
|
|
| Management review of P&L |
|
|
|
|
|
|
|
| Statements and pack issued |
|
|
|
|
|
|
|
Reconciliation tracker
| Account |
Preparer |
Reviewer |
Due BD |
Completed BD |
Unreconciled difference |
Aged items |
Status |
Post-close adjustment log
| Entry |
Amount |
Posted after BD |
Cause |
Preventable? |
Fix owner |
Cutoff calendar for contributors outside finance
| Source |
Data needed |
Cutoff BD |
Owner |
Escalation |
| Purchasing |
Received-not-invoiced report |
BD 1 |
|
|
| Operations |
Unbilled work or shipments |
BD 1 |
|
|
| HR / payroll |
Hours, bonuses, headcount changes |
BD 2 |
|
|
| Sales |
Credit memos, rebates, commissions |
BD 2 |
|
|
Metrics and KPIs
| Metric |
Formula |
Data source |
| Close duration |
Business day on which the books are locked |
Close calendar |
| Report delivery day |
Business day on which the pack is issued |
Close calendar |
| Post-close adjustments |
Entries posted after first draft ÷ total entries, and in dollars |
Adjustment log |
| On-time task rate |
Tasks completed by due BD ÷ tasks in calendar |
Close calendar |
| Reconciliation timeliness |
Accounts reconciled by due BD ÷ accounts |
Reconciliation tracker |
| Unreconciled differences |
Count and dollar total at lock |
Reconciliation tracker |
| Manual journal share |
Manual entries ÷ total entries |
GL |
| Backup coverage |
Tasks with a named, trained backup ÷ tasks |
Close calendar |
Setting targets without invented benchmarks. Anchor on three things in order: the day your downstream deadlines require (for example, the lender package due date from your agreement), your own best close in the last twelve months, and what the critical path analysis shows can be removed with the changes you control. Use named public peers only if they disclose their close timing. Do not adopt a target from an article and apply it to your systems and entity count.
Common mistakes
- Speeding up tasks off the critical path. Faster payroll accrual does not help if the intercompany match is what finishes last. Find the path first.
- Trading accuracy for days. If post-close adjustments rise or reconciliations are skipped, the close is not faster, only earlier and wrong. Track both.
- Soft cutoffs. If the cutoff moves whenever someone asks, the close inherits every late item. Escalate misses to the source owner.
- Leaving reconciliations to the end. Reconciling after the books close doubles the work and moves errors into the review window.
- Rebuilding accruals each month. Templates with a trigger report are faster and more consistent than rebuilt estimates.
- No backup for key tasks. A single point of failure makes the calendar fragile.
- Skipping the retrospective. Without a short review after each close, the same delays return.
- Tool purchase as the first step. Software helps once the calendar, cutoffs, and ownership are in place. Without them it automates the delay.
- Ignoring accounting judgment. Accrual, reserve, and revenue recognition questions need accounting and audit input. Faster should not mean bypassing your policies or your auditors.
Worked example (illustrative)
The figures below are made up to show the method. They are not benchmarks.
A manufacturing company closes on BD 18. The critical path, in business days per stage, looks like this:
| Stage on the critical path |
Current days |
Target days |
Change that makes the difference |
| Cutoff and subledger lock |
3 |
2 |
Hard cutoffs; daily invoice processing in the last week |
| Accruals and adjustments |
4 |
2 |
Recurring accrual templates; received-not-invoiced report on BD 1 |
| Reconciliations and intercompany |
4 |
3 |
Reconcile high-risk accounts mid-month; weekly intercompany match |
| Inventory and COGS true-up |
3 |
1 |
Cycle-count adjustments posted weekly; standard cost variances pre-loaded |
| Review and analysis |
2 |
1 |
Staged review with preset thresholds |
| Statements and pack issued |
2 |
1 |
Standard template refreshed from the ledger |
| Total |
18 |
10 |
|
Arithmetic: current 3 + 4 + 4 + 3 + 2 + 2 = 18. Target 2 + 2 + 3 + 1 + 1 + 1 = 10. Days removed = 8, of which 4 come from accruals and inventory (2 and 2), and 4 from the remaining stages (1 each in cutoff, reconciliations, review, and reporting).
Reading it: half the days removed come from two stages, accruals and inventory true-up, where the fix is a template and an earlier data feed. That is where to start. The company should not promise BD 10 on day one. A realistic plan moves in steps, for example BD 18 to BD 14 in the first quarter, and then to the target as templates and cutoffs hold. Each step is set only after the previous close shows which items actually moved.
The check on accuracy matters as much as the day count. Before the first accelerated close, the Controller records the baseline: number and dollar value of post-close adjustments, and unreconciled differences at lock. If those worsen while the close speeds up, pause and fix the cause.
Every total above was recomputed by script and ties: 18 and 10 as stated, and 18 − 10 = 8.
AI prompt assistance
AI can help analyze the close and draft procedures. It does not replace accounting judgment, and it must not post entries or decide accounting treatment. Provide your own data and verify results.
1. Find the critical path.
Here is a table of close tasks with start day, finish day, and predecessor for the last three months. Identify the longest dependent chain, list which tasks were on it each month, and show the days between each predecessor finishing and its successor starting.
Check: confirm the chain against how the close really ran, with the Controller.
2. Classify post-close adjustments.
Here are 30 adjusting entries posted after the first draft with their descriptions. Tag each as late cutoff, missed accrual, error, estimate change, or other. Return a count and dollar total by tag, and list any entry you could not classify.
Check: sample ten entries against the support, and confirm causes with the preparers.
3. Draft accrual template procedures.
I will describe a recurring accrual (the data source, the calculation, the account). Draft a one-page procedure with inputs, calculation steps, the reviewer check, and what changes would require a manual override. Do not state any accounting conclusion; flag questions for our accountant.
Check: the Controller reviews the procedure, and technical points go to your accounting adviser or auditor.
4. Summarize the retrospective.
From this close calendar with actual days and causes, write a half-page retrospective: the five latest tasks, their causes, and one proposed fix for each, with a suggested owner.
Check: verify each task day against the calendar, and confirm owners before assigning.
Implementation guide
| Phase |
Timing |
Owner |
Exit criteria |
| Measure |
Days 1-30 |
Controller |
Six-month task timeline built; critical path identified; baseline for post-close adjustments recorded |
| Redesign |
Days 31-60 |
Controller with CFO |
Calendar published; hard cutoffs agreed with operations, HR, sales; accrual templates and reconciliation ownership in place |
| Run and tighten |
Days 61-90 |
CFO |
Two closes run on the calendar; retrospective held each month; target day confirmed or reset from evidence |
Governance: the CFO owns the target and the cutoff escalations, the Controller owns the calendar and the retrospective, and each task owner is responsible for their due day and a named backup. Report close day, post-close adjustments, and on-time rate to the CEO monthly, alongside the numbers themselves. For the policies behind accruals and revenue recognition, follow your accounting adviser and auditor.
Downloadable assets
The close calendar, reconciliation tracker, adjustment log, and cutoff table above are designed to be copied into a spreadsheet.
Related resources
Frequently asked questions
What is a 10-day close?
A 10-day close means the books are locked and the financial statements are available by the tenth business day after month end. Ten days is an example target, not a rule. Set your own from downstream deadlines such as a lender due date, your best recent close, and what your critical path analysis shows you can change.
How do you shorten the monthly close?
Find the critical path, then shorten it at the source: hard cutoffs, recurring accrual templates, early reconciliations, continuous intercompany matching, staged review, and a standard report template. Speeding tasks that are not on the critical path does not shorten the close, so measure first.
Does a faster close hurt accuracy?
Not if you track accuracy as you speed up. Measure post-close adjustments and unreconciled differences before and after each change. If they rise, the close is earlier but less reliable, and the cause should be fixed before going further. Accounting judgments remain subject to your policies and your auditors.
Should we buy software to speed up the close?
Software helps once your calendar, cutoffs, and ownership are defined, because it can automate the steps you have standardized. Buying first usually automates the existing delays. Start with the critical path analysis, then decide which steps, such as reconciliations or accrual templates, justify a tool.
How often should we review the close process?
Hold a short retrospective after every close, within a few business days, and review the whole calendar each quarter. Each retrospective should list the latest tasks, their causes, and one fix each. Over a few cycles this removes more days than a one-time redesign.
How this works in a System of Performance
A close slows down where information is scattered: cutoff reports in operations, accrual support in email, reconciliations in spreadsheets, and review comments in chat. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see where your own close days go, bring it to us as a launch partner.