The month-end close is a set of dependent tasks that turns a month of transactions into reliable reports. It usually takes longer than it needs to, because of waiting, rework, and manual reconciliations, and its speed decides how quickly leaders can act on the numbers.
This guide covers the measures that matter, how to find the critical path of a close, and a worked example in which a team cuts a 9-day close to 7 days by shifting work earlier in the month and automating variance analysis, while tracking post-close adjustments so accuracy is not sacrificed.
Before You Start
Why the Close Deserves Process Improvement
It Sets the Pace for Decisions
Leaders cannot act on numbers they do not have. A shorter, more predictable close means faster, better-informed decisions.
Rework and Waiting Dominate
Most of the days in a close are spent waiting for information, redoing entries, and chasing reconciliations, not on value-adding analysis.
Quality and Speed Support Each Other
Errors found after the close cause adjustments and restatements. A cleaner process is also a faster one.
Finance Talent Is Scarce
Time saved in the close can go to analysis and business partnering.
Measures for the Close
| Measure | Definition | Why it matters |
|---|---|---|
| Days to close | Business days from period end to the point when books are closed and reported | The headline speed measure. |
| Post-close adjustments | Entries or corrections made after the close is declared complete | A quality measure: late corrections mean the close was not clean. |
| Reconciliations completed on time | Share of account reconciliations prepared and reviewed by their due date | Timeliness of a key control. |
| Manual journal entries | Count of manual entries in the period | Manual entries carry more risk and take more time. |
| First-pass acceptance | Share of reports accepted by reviewers without rework | How often work is right the first time. |
Find the Critical Path
A close is a set of tasks with dependencies: reconciliations wait for cutoff, eliminations wait for reconciliations, review waits for eliminations. The critical path is the longest chain of dependent tasks, and it sets the number of days. Effort to shorten the close should go to tasks on that path. Tasks with float can slip a little without delaying the close. The Outage Planning Guide explains the same idea for maintenance outages.
Worked Example: A 9-Day Close
A company maps eight close tasks. Durations and dependencies are illustrative.
| Task | Days | Starts after |
|---|---|---|
| A Subledger cutoff | 1 | Period end |
| B AP and AR reconciliations | 3 | A |
| C Payroll and accruals | 2 | A |
| D Inventory and fixed assets | 3 | A |
| E Intercompany eliminations | 1 | B and D |
| F Review and adjustments | 2 | C and E |
| G Consolidation and reporting | 1 | F |
| H Management review | 1 | G |
Improvement ideas, aimed at the critical path. The team reconciles AP and AR continuously during the month, so at close only the last few days remain: B falls from 3 days to 1. It moves inventory and fixed-asset entries earlier, so D falls from 3 to 2. It also automates variance analysis in review, so F falls from 2 days to 1.
| Task | Before | After |
|---|---|---|
| B AP and AR reconciliations | 3 | 1 |
| D Inventory and fixed assets | 3 | 2 |
| F Review and adjustments | 2 | 1 |
| Days to close | 9 | 7 |
The new critical path is A, D, E, F, G, H: 1 + 2 + 1 + 1 + 1 + 1 = 7 days. Payroll and accruals, at 2 days, now has only 1 day of float, so any further gain has to come from inventory and fixed assets (D) first, and then from payroll and accruals (C) as well. Speeding up B alone would not have helped much, since D was equally critical: with both at 3 days, cutting only B leaves the path through D at 9 days. That is why the team analyzes the path before choosing what to improve.
Quality check. A faster close is only better if it stays accurate. The team tracks post-close adjustments and reconciliations completed on time alongside days to close, and it does not remove reviews to save time, since that would trade speed for risk. Any change to controls should be reviewed by finance leadership and, where relevant, the auditors.
Model your own close with the Close Calendar Critical Path Calculator, and track it in the Month-End Close Checklist Template.
Four Levers for a Faster, Cleaner Close
Once the critical path is known, improvement comes from a small number of levers. Each one shortens the close by removing work, moving it, or making it faster or more reliable.
Eliminate. Ask of each step: who uses this output, and what decision does it support? Steps that exist for historical reasons can often be dropped or simplified. Do not remove steps that provide required assurance; change how they are done.
Move work earlier. Many reconciliations can be done weekly or continuously, and recurring accruals can be prepared in advance. A soft close, in which most of the work is completed a few days before period end and only the last transactions remain, shortens the critical path.
Standardize and automate. Write checklists and templates, and automate matching, recurring entries, and data loads where volumes justify it. Automating a confused process creates a fast, confused process.
Improve upstream. Late invoices, miscoded transactions, and missing accrual information from departments force rework at close. Agree cutoff dates with the business, and give feedback on recurring errors to their source.
Speed Without Weakening Controls
A faster close must not be a weaker one. Controls such as reconciliations, journal entry review, and management sign-off protect the accuracy of the financial statements, and they should be preserved or redesigned to work as well in less time.
- Risk-based reconciliation. Focus effort on accounts with higher risk or larger balances, and reconcile low-risk accounts less often, following your policy on materiality.
- Review with evidence. Reviewers should see the support, explanations for differences, and the preparer's sign-off. A review that only checks that a box was ticked is not a control.
- Journal entry discipline. Require support and approval, limit who can post manual entries, and review unusual entries. Reducing manual entries reduces risk and time.
- Flux analysis with thresholds. Explain variances above agreed thresholds and keep the explanations.
- Keep an audit trail. Retain the checklist, evidence, and approvals so that the close can be reviewed later.
| Measure | Watch for |
|---|---|
| Days to close | Shortening it while post-close adjustments rise |
| Post-close adjustments | A rising count means quality is slipping |
| Reconciliations on time and with differences explained | Timeliness and completeness |
| Manual journal entries as a share of total | Risk and workload |
| Review findings and rework | Quality of first-pass work |
Test a change in a low-risk month and compare results. Involve internal audit or your auditors early when you change a control, so that the redesign is acceptable. See the Close Calendar Critical Path Calculator, the Month-End Close Checklist Template, and the Internal Controls and Sampling Guide. This guide is educational and is not accounting, audit, tax, or legal advice. Follow your accounting policies, the standards that apply to you, and the advice of qualified professionals. Figures in the examples are illustrative.
Self-Assessment Questions
- Do we know our critical path, and which tasks have float?
- Do we measure post-close adjustments as well as days to close?
- Which tasks could move earlier into the month?
- Are reconciliations prepared and reviewed by their due date?
- Do improvements keep or strengthen controls?
Common Mistakes
Speeding Up Tasks Off the Critical Path
Effort on tasks with float does not shorten the close. Find the path first.
Cutting Reviews to Save Days
Removing a control saves time until an error reaches the reports. Automate checks instead of dropping them.
Measuring Only Days to Close
A fast close with many post-close adjustments is not a good close. Pair speed with quality.
Leaving Manual Workarounds in Place
Spreadsheets and rekeying add time and risk. Standardize and reduce manual entries.
Month-End Close Process Improvement: Frequently Asked Questions
How can we shorten the month-end close?
Map the close as a set of tasks and dependencies to find the critical path, then shorten the tasks on that path: reconcile continuously during the month, move accruals and entries earlier, automate variance analysis and checks, and reduce manual entries. Keep controls in place, and track post-close adjustments so speed does not cost accuracy.
What is a good number of days to close?
It varies by company size, complexity, and reporting requirements, so compare mainly with your own trend and with what your leaders need. A shorter close is only better if it stays accurate, so track post-close adjustments and the timeliness of reconciliations alongside days to close.
What is float in a close schedule?
Float is the amount of time a task can slip without delaying the end of the close. Tasks on the critical path have zero float, and tasks off it have positive float, which means effort to shorten the close should focus on the critical tasks.
Sources and Further Reading
- Project Management Institute, Practice Standard for Scheduling, on the critical path method.
- Institute of Management Accountants and similar bodies, guidance on the financial close.
- Eliyahu Goldratt, The Goal, on focusing improvement on the constraint.
- Mike Rother and John Shook, Learning to See.