Key takeaways
- The month-end close best practices that matter most are a dated calendar with named owners, early cutoffs, reconciliations during the month, a flux review threshold, independent sign-off, a locked period, and a short review after every close.
- Adopt them in order. Ownership and the calendar come first, because a practice without an owner and a due day rarely survives a second close.
- Measure more than speed. APQC's median is 6.0 calendar days from the first trial balance to the consolidated statements, but late reconciliations and post-close adjustments tell you whether the practices hold.
Adopting month-end closing best practices in order helps you close on a predictable day and correct fewer numbers after the fact. This guide ranks 10 practices, gives each one an owner, a "done when" test, and a measure, and includes a worked flux review threshold and a retrospective log you can copy.
What are month-end close best practices?
Month-end close best practices are the rules a finance team follows so each month's books are complete, correct, reviewed, and locked on schedule. They say who does each task, when it's due, what evidence it needs, and who signs it off.
- Best practiceA rule that's written down, has one owner, and can be checked, such as "every balance sheet account reconciled to independent supporting detail by business day 4"
- Financial close best practicesThe same rules applied to every period close, including quarter-end and year-end, which often add work such as physical inventory counts and the full tax provision
- Flux review thresholdA trigger, in percent and dollars, that management sets for explaining account movements before sign-off; it isn't financial statement materiality, which needs qualitative as well as quantitative judgment
Month-end accounting best practices don't replace the close steps; they make each step repeatable. The close itself is explained in what is month-end close, and the steps it runs through are in the month-end close process.
What are the best practices for month-end close?
The 10 best practices for month-end close are a calendar with owners, published cutoffs, work moved into the month, reconciliations to independent supporting detail, supported journal entries, a flux review threshold, subledgers closed in order, independent review, a fixed reporting package, and a review after every close.
The table gives each practice an owner, a test for when it's done, and a measure you can track every month. Business day 1 (BD1) is the first business day after month-end.
| Practice | Owner | Done when | Measure |
|---|---|---|---|
| 1Publish a close calendar with one preparer and one reviewer per task | Controller | Every task has a preparer, a reviewer, and a business day, and the team has the calendar before month-end | Tasks with no owner: 0 |
| 2Set cutoffs and send them before month-end | Controller, with the AP, payroll, and billing leads | Invoice, expense report, payroll, and billing cutoffs go out three business days before month-end | Inputs received after cutoff |
| 3Move work into the month | Accounting manager | Bank, card, and clearing accounts are reconciled weekly, and recurring entries are drafted before month-end | Share of reconciliations finished before BD1 |
| 4Reconcile every balance sheet account to independent supporting detail | Staff and senior accountants | Each account ties to a bank statement, subledger, schedule, or confirmation, and every reconciling item has an age and an owner | Reconciliations signed off by their due day |
| 5Support and approve every manual journal entry | Preparer, with an approver above your threshold | Each entry has support, a description, and an approver who isn't the preparer | Manual entries posted without approval: 0 |
| 6Set a flux review threshold | Controller | Every account movement above the threshold has a written explanation before sign-off | Movements above threshold left unexplained |
| 7Close subledgers in order, then lock the period | Accounting manager and ERP administrator | AP, AR, inventory, and fixed assets close before the general ledger, and the period locks on sign-off day | Entries posted after the lock |
| 8Review the trial balance and statements independently | Controller, then the CFO | Someone who didn't prepare the numbers signs off the adjusted trial balance | Post-close adjustments |
| 9Report from a fixed package | Financial reporting lead or FP&A | The same statements, commentary, KPIs, and cash view go out on a set business day | Business days to deliver the package |
| 10Run a 30-minute review after every close | Controller | Each issue has a root cause, one fix, an owner, and the close it's due by | Issues repeated from last month |
To manage the month-end close, run it from this table and put the task-level schedule in a month-end close calendar. Your month-end close checklist holds the full list of month-end accounting procedures; a good checklist gives each task an owner, a due business day, and the evidence that shows it's done. The free close checklist template gives you a starting file with owners and due days.
Four of the practices need more detail:
- Cutoffs (practice 2)Sending dates three business days early gives budget owners time to submit invoices and expense reports. Costs incurred in the month that arrive late get accrued from your best estimate and trued up next month, so they don't hold the close.
- Work in the month (practice 3)A close that starts on BD1 runs as one large batch. The continuous close guide shows which tasks can run weekly instead.
- Subledgers in order (practice 7)Lock AP and AR first, so no new invoice or receipt changes a balance you've already reconciled. Lock settings by ERP are in lock accounting period.
- Review (practice 8)The reviewer checks the reconciliations, the entries above threshold, and the explanations for large movements, then signs. Flux analysis keeps that review focused on the movements that matter.
Which month-end close best practices should you put in place first?
Put ownership and the close calendar in place first, then cutoffs and reconciliations, then review rules, the lock, and the retrospective. Each practice depends on the one before it: a review rule can't work until every reconciliation has an owner and a due day.
A workable order for a new controller:
- First closePractices 1 and 2. Write the calendar, name a preparer and reviewer for every task, and send cutoffs.
- Second closePractices 4 and 5. Reconcile every balance sheet account, and require support and approval for manual entries.
- Third closePractices 6, 7, and 8. Set the flux review threshold, close subledgers in order, lock the period, and add independent sign-off.
- Fourth close onwardPractices 3, 9, and 10. Move work into the month, fix the reporting package, and start the review after each close.
Separating preparer from reviewer is the hardest practice for a small team, because one person often does both. The table shows one way to split the work by team size.
| Team size | Prepares | Reviews | Signs off | How preparer and reviewer stay separate |
|---|---|---|---|---|
| 3 people: a controller and two accountants | The two accountants, split by account | Each accountant reviews the other's low-risk reconciliations, and the controller reviews high-risk accounts | Controller | The CFO or an outside CPA reviews the controller's own entries each month |
| 6 people | Staff and senior accountants | Accounting manager | Controller | The manager reviews what staff prepare, and the controller reviews the manager's entries |
| 12 or more people | Staff accountants by area, such as cash, AP, revenue, and payroll | Senior accountants and the accounting manager | Controller, then the CFO for the statements | Reviews follow the reporting lines, and the ERP blocks anyone from approving their own entry |
Company type changes which accounts carry the most risk. Revenue and deferred revenue schedules lead in a SaaS month-end close, and intercompany eliminations lead in a multi-entity month-end close.
Why is it important to optimize the month-end close?
Optimizing the month-end close matters because leadership decides on last month's numbers, so late or wrong numbers delay decisions, add audit work, and wear out your team. A close that ends on a fixed day with few corrections also gives FP&A more time to explain the results.
APQC's benchmark gives you a reference point. Across more than 10,000 organizations, the median is 6.0 days to complete the monthly consolidated financial statements, counted in calendar days, including weekends, from the first monthly trial balance (APQC Open Standards Benchmarking, measure 100162, read November 11, 2026). Six calendar days usually hold 4 or 5 business days, so convert before you compare.
Example
Your first trial balance for October 2026 runs on Monday, November 2, and the consolidated statements are done on Tuesday, November 10. That's 8 calendar days by APQC's count, 2 more than the median, and 6 business days of work.
Targets by company size are in how long should month-end close take, and the free close benchmark checker compares your own numbers.
What is financial close optimization?
Financial close optimization, also called month-end close optimization, means taking work out of the close, moving work earlier in the month, and catching errors sooner, while keeping review and controls in place. You measure it by fewer corrections and less rework, not only by fewer days.
To improve your month-end close process, run this loop:
- Time every task for one close, in business days and hours.
- Mark the three tasks that most often finish late, and note what each one waited on.
- Fix one cause per close, such as an earlier cutoff, a weekly reconciliation, or a template entry.
- Keep a fix only if it holds for two closes in a row.
An efficient month-end close finishes on its planned day, needs few changes after sign-off, and doesn't depend on overtime. The plan for cutting a 10-day close to 5 is in speed up month-end close, and the zero-day target is explained in zero-day close.
How do top companies reduce errors during month-end close?
Top companies reduce close errors by spreading work through the month, reconciling to independent supporting detail, explaining movements above a flux review threshold, and requiring a reviewer who didn't prepare the work. Most errors trace back to a few common pitfalls in the month-end process.
| Common pitfall | How it shows up | Fix |
|---|---|---|
| Work left to the last days | Reconciliations and accruals pile up on BD2–4 | Reconcile high-volume accounts weekly, and draft recurring entries before month-end |
| Waiting on other teams | Accruals wait on AP, payroll, or sales data | Give every input an owner and a cutoff day, and accrue from an estimate when it's late |
| Spreadsheets with no review trail | Broken links, old versions, and support nobody can trace | Keep one version of each schedule, with the preparer and reviewer recorded |
| Reconciling the ledger to itself | A balance "ties" to a report built from the same ledger | Reconcile to bank statements, subledgers, invoices, or confirmations |
| Reviewing only accounts that moved | Errors sit in balances that didn't change, so nobody opened them | Sign off every reconciliation under a documented, risk-based reconciliation policy, and use the flux threshold only to pick movements that need commentary |
| Changes after the close | Entries land in a period you've already reported | Lock the period on sign-off day, and post a correction in the open period only when documented analysis shows neither period is materially misstated |
In Ledge's 2025 benchmark survey of 100 finance professionals, reported by CFO.com, 56% named dependence on other teams as a blocker, 50% named Excel-driven processes, and 40% named legacy systems. The strategies for better data integrity follow from the table: one version of each schedule, reconciliations to independent supporting detail, and no edits after the lock.
The close feels hard because many tasks depend on each other inside a few days, but most of that difficulty comes from the pitfalls above, and you can fix them one at a time. Common accounting mistakes at month-end include missed accruals, entries in the wrong period, duplicate invoices, and clearing accounts left unreconciled. How to correct them is covered in adjusting entries.
Best practices for using ERP systems at month end
Use your ERP as the single record for the close: run the checklist against it, post recurring and reversing entries from templates, close subledgers before the general ledger, and lock the period once the trial balance is signed off. A later correction goes into the open period only when documented analysis, including cumulative and qualitative effects, shows it doesn't materially misstate either period; otherwise you correct the affected period.
- One recordReconcile each subledger to the general ledger every month, so the AP, AR, and fixed asset reports match the balance sheet.
- Templates for recurring entriesSet up depreciation, prepaid amortization, and standard accruals as templates, with accruals set to reverse on the first day of the next month.
- Exception reportsSave searches for unposted transactions, manual entries without approval, and balances in suspense or clearing accounts, and run them before BD1.
- Period controlsLimit who can post to a closed period.
- AccessReview who can create, approve, and post entries at least once a quarter.
In NetSuite, for example, the Period Close Checklist takes you through the Lock A/P, Lock A/R, and Lock All tasks, which stop A/P, A/R, and payroll transactions from posting, before you close the period (NetSuite Help, "Using the Period Close Checklist," read November 11, 2026). The full walkthrough is in NetSuite month-end close.
Best practices for efficient month-end financial reporting
Efficient month-end financial reporting starts from a locked, reviewed trial balance and a package with the same contents every month, sent on a set business day. The controller reviews it, and the CFO approves it before it goes to leadership.
| Part of the package | What it shows | Prepared by | Reviewed by |
|---|---|---|---|
| Income statement, balance sheet, and cash flow statement | Results for the month and year to date | Financial reporting lead | Controller |
| Variance commentary | Explanations for movements above your flux review threshold, against budget and last month | FP&A, with the accountant who owns each account | Controller |
| KPIs | A short set agreed with leadership, such as revenue growth, gross margin, and cash runway | FP&A | CFO |
| Cash view | Cash balance, a short-term cash forecast, and debt covenant headroom | Treasury or FP&A | CFO |
| Close notes | Late items, estimates used, and anything to true up next month | Controller | CFO |
Keep the package to what leadership reads each month. Line-by-line comparisons to budget are covered in budget vs actual.
How can software improve the financial close?
Software improves the financial close by matching transactions, reconciling accounts, preparing recurring entries and workpapers, and recording who did what, so your team spends its time on review and judgment. Estimates, unusual items, and final sign-off should stay with a person.
Let software do it
- Bank, card, and intercompany matching
- Reconciliation workpapers with every difference listed
- Recurring and reversing entries
- First drafts of explanations for large movements
- Tracking tasks, owners, and due days
Keep it with a person
- Accrual estimates that need judgment, such as bonuses or legal costs
- Deciding how to treat an unusual transaction
- Approving entries above your threshold
- Final commentary that goes to leadership
- Signing off the adjusted trial balance
Financial management apps improve accuracy during the close when they check every transaction instead of a sample, record each step, and leave sign-off to a named reviewer. Cloud-based close tools fall into two groups: tools that track the close, with checklists, owners, and sign-offs, and tools that do the work, such as matching, reconciliations, and entries. To see which group a tool is in, ask the vendor to run one task in front of you, from source data to an approved entry. Options are compared in best month-end close software, and the method is in month-end close automation.
Worked example: A flux review threshold for the close
A flux review threshold tells your reviewer which account movements need a written explanation before sign-off. Management sets it, often as a movement above both a percentage and a dollar amount, documents it in the close policy, and revisits it each year. Auditors may comment on it, but the decision is management's.
Example
A company with about $40 million in annual revenue sets this rule for income statement lines: explain any change against last month that's more than 10% and more than $25,000. All amounts are illustrative.
| Line | September | October | Change | Change % | Explain? |
|---|---|---|---|---|---|
| Revenue | $3,300,000 | $3,420,000 | +$120,000 | +3.6% | No, under 10% |
| Payroll | $1,410,000 | $1,452,000 | +$42,000 | +3.0% | No, under 10% |
| Contractors | $150,000 | $196,000 | +$46,000 | +30.7% | Yes |
| Marketing | $260,000 | $205,000 | −$55,000 | −21.2% | Yes |
| Travel | $42,000 | $71,000 | +$29,000 | +69.0% | Yes |
| Software | $84,000 | $97,000 | +$13,000 | +15.5% | No, under $25,000 |
Three of the six lines need an explanation before the controller signs off. The threshold only decides which movements need commentary. It isn't a materiality judgment, which weighs qualitative factors as well as size, and it doesn't replace signing off every reconciliation. Many teams also comment on revenue every month whatever the change, and set larger dollar thresholds for balance sheet accounts.
What is close continuous improvement?
Close continuous improvement is a short review after every close that logs what ran late or went wrong, finds the root cause, and assigns one fix with an owner before the next close. Close performance improvement is the same loop, tracked with a few numbers each month.
Hold the review within two business days of sign-off, for 30 minutes, with every task owner who missed a due day. Bring the numbers, then fill in an issue log.
Example
The issue log from an October close.
| Issue | Impact | Root cause |
|---|---|---|
| The payroll accrual file arrived on BD3 | Accruals and the flux review slipped two business days | The payroll provider's report runs after BD2 |
| $4,800 of card charges were uncoded at the card reconciliation | A reclass entry after review | Cardholders code charges at month-end |
| Two entries posted to October after sign-off | The period was reopened and the package resent | The lock was set on BD7, two business days after sign-off |
| Issue | Fix | Owner | Due |
|---|---|---|---|
| The payroll accrual file arrived on BD3 | Request the report on BD1, and accrue from last month's run rate if it's late | Payroll lead | November close |
| $4,800 of card charges were uncoded at the card reconciliation | A weekly coding reminder and a mid-month card reconciliation | Senior accountant | November close |
| Two entries posted to October after sign-off | Lock on sign-off day, and let only the controller post to a closed period | Controller | November close |
To see whether the close is improving beyond days to close, track five measures: business days to close, reconciliations signed off by their due day, post-close adjustments, manual journal entry share, and overtime hours in close week. Formulas and targets are in month-end close KPIs.
How we approach it
Our Close Agent works the close checklist through the month: it reconciles accounts to bank statements, subledgers, and invoices, and prepares each entry with its workpaper for a named reviewer who's separate from the preparer. Nothing posts to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, or QuickBooks until an approver signs off the exact lines, and the month can't lock until every task is signed off. Explore our Close Agent to see these practices run inside your own close.
Share this article