Why month-end close takes so long: Challenges, causes, and fixes

A month-end close often takes so long because close work waits in queues: for other teams' inputs, for reconciliations rebuilt by hand, for one reviewer, and for accounts reopened by late entries.

• Waiting timeElapsed time when a task is blocked on an input, an approval, or a person, and no one is working on it
• Rework loopWork done again after sign-off because a late entry, an error, or a missing document reopened it
• Critical pathThe longest chain of dependent tasks in your close, which sets the day you sign off and lock the period

Month end problems compound because close tasks depend on each other. An accrual input that arrives two days late delays the accrual and its review, and if that accrual sits on your critical path, it delays the period lock too. That's how a team can stay busy for the whole close and still finish late.

In Ledge's 2025 survey of 100 finance professionals, 50% needed six or more business days to close. Vena's survey of 624 US finance and accounting professionals, published October 23, 2026, put the average at 6.2 business days. Targets by company size are in how long should month-end close take.

The most common month-end close challenges are late inputs from other departments, spreadsheet-based work, disconnected systems, reliance on a few key people, and too little time left for review and controls.

Surveys from 2024 to 2026 rank these in a similar order, but their samples, countries, and questions differ. Compare the order of the causes, and treat the exact percentages as directional.

Two patterns stand out. The four sources above that ask what blocks or complicates the close (Ledge, Vena, Sixthfin and Odoxa, and LiveFlow) all put information from outside finance at or near the top. In Vena's survey, only 19% said more staff would help, behind better integration (32%), standard processes (28%), and automated consolidation (27%).

The same financial close challenges show up at quarter-end and year-end, with more volume and more audit scrutiny. The challenges in achieving a fast month-end close are mostly timing and coordination problems, so the data points to fixing those before you add headcount.

A slow month-end close comes from seven bottlenecks: late inputs, manual reconciliations, accrual chasing, intercompany mismatches, disconnected systems, late adjustments that reopen work, and audit requests during the close.

In a traditional close, where most work starts after month-end, all seven stack up in the same few days. Review queues and key-person dependence make each of them worse, and they get their own sections below. Use the table to match what you see in your close to a likely cause, a first fix, and an owner.

Four causes don't show up in a status report. They are tiny accruals, unmapped master data that drops entries into suspense, reconciliations in personal spreadsheets, and reviewers who wait for every preparer. Each adds rework or queue time without looking like a late input.

Late inputs from other teams

Late inputs are the most-reported cause in the surveys above. Nearly 8 in 10 of the 43 senior finance leaders in LiveFlow's March 2026 survey blamed close delays on waiting for data from other systems or departments, as CFO Dive reported on May 5, 2026.

None of these surveys measures the share of close hours spent waiting, so your own time log is the way to measure it. Late inputs also cause errors. Of the 488 Vena respondents who had corrected numbers, 27% traced the latest correction to late or missing information from another department. The 37% of teams that still sourced data from email or shared documents averaged 6.8 business days to close, against 5.9 for everyone else in the survey.

To spot this cause, compare each input's due day with the day it arrived complete. To fix it, publish an input calendar before month-end with an owner, a due time, and a format for every input. Track the inputs in one shared status view instead of email threads. The month-end close calendar gives you a day-by-day schedule to start from.

Manual reconciliations and spreadsheets

Manual reconciliations slow the close because every month starts from fresh exports, and each difference is found and explained by hand. In Ledge's 2025 survey, 94% used Excel in the close, and reconciling accounts was the most time-consuming task. Cash reconciliation alone took 20–50 hours a month.

Spreadsheet sprawl adds its own delay. 38% of the UK finance leaders in the Sixthfin and Odoxa survey named spreadsheet proliferation as a main difficulty. In Vena's survey, 52% of teams on 7–8 systems spent half or more of the close timeline manually consolidating data. Only 15% of teams on 3–4 systems did.

You'll spot this cause when a reconciliation shows "in progress" for several days, or when two people hold different versions of the same file. Reconcile bank, card, and other high-volume accounts weekly, match transactions automatically, and fix recurring exceptions at their source. The method is in account reconciliation, and the tools are covered in financial close automation.

Accrual chasing and small accruals

Accruals slow the close when each one waits on a budget owner's estimate, or when the team books small amounts that don't change any decision. Ledge's 2025 respondents ranked accruals and provisions second among the most time-consuming close tasks, after reconciliations.

You'll see accrual emails still open on BD3 and dozens of entries below any amount leadership would notice. Write an accrual threshold that management approves and your auditor reviews, and treat it as a review trigger, not a bright line: check the total of what you skip each month, because many small accruals can add up to a material amount. Use standing estimates for recurring vendors, and true them up in the month the actual invoice arrives. Build the received-not-invoiced list from purchase order data instead of asking each budget owner. The entries and examples are in accrued expenses.

Intercompany and multi-entity mismatches

Intercompany balances slow the close when entities book the same transaction in different amounts, periods, or currencies, so eliminations don't net to zero. In Vena's 2026 survey, single-entity teams averaged 4.7 business days to close, and teams with more than 10 entities averaged 8.3.

The symptom is a consolidation day spent chasing differences between two entities, or one late entity holding up the group. Confirm intercompany balances during the month and again by BD2. Use one agreed set of intercompany accounts, and set an entity cutoff before consolidation starts. The entries are in intercompany accounting.

Disconnected systems and ERP setup

Disconnected systems slow the close because data moves between them by export, re-keying, or upload, and every handoff can drop or duplicate a transaction. In Ledge's 2025 survey, 40% named legacy systems that don't integrate as a blocker. Half of LiveFlow's respondents cited reconciliation across systems as a persistent drag.

Vena's 2026 survey shows the cost in accuracy. 92% of teams using 7–8 systems corrected or restated numbers, against 57% of teams using 1–2. Watch for suspense balances on BD1, subledgers that don't tie to the ledger, and new vendors or customers without account mapping. Clear suspense daily, map master data when records are created, and integrate the highest-volume feed first.

Late adjustments and reopened work

Late adjustments slow the close because each entry posted after review reopens reconciliations and reports that were already signed off. Vena's 2026 survey found that 78% of respondents had restated or corrected numbers in the past year, even after the close was marked complete. Of the 488 who had corrected numbers, 28% traced the latest correction to manual or data entry errors.

Gartner's survey of 497 controllership staff, published February 21, 2024, named insufficient review and reopening the books among the sources of errors. Look for entries posted after your cutoff and reconciliations signed off twice. Set a hard cutoff for top-side entries. An item that arrives after the cutoff and falls below your review threshold can usually be booked in the next open period as an out-of-period adjustment. Track the running total of those items, and review any that are unusual in nature whatever their size, because materiality is a judgment, not a fixed number. Lock the period once the controller signs off. Lock accounting period explains who can still post after the lock.

Audit requests during the close

Audit requests slow the close when auditors' prepared by client (PBC) requests land in the middle of it, and preparers stop close work to rebuild support. The surveys above don't measure this cause, so check your own log for days when close tasks stalled during audit fieldwork.

Keep the support for each reconciliation and entry with the work as you prepare it, so a request takes minutes to answer. Agree a request calendar with your auditors that puts fieldwork requests after the lock, and name one person to receive and route them.

Review becomes the bottleneck when every reconciliation and entry reaches one controller near the end of the close, so finished work waits in a queue, and any late entry reopens items already signed off.

This is batch review: preparers finish in the first days, and the controller starts only when the last item is ready. Two or three days of review then sit at the end of the close. In the Sixthfin and Odoxa survey, 33% of UK finance leaders said they had too little time for controls.

In your log, it shows up as a long gap between ready for review and approved. Most of the controller's hours fall in the last few days. Review each item as it's ready instead of in one batch. Tier items by risk, so the controller reviews high-risk accounts and judgment entries, and a second accountant reviews low-risk reconciliations where your policy allows it. Use standard workpapers and review account movements against set thresholds with flux analysis, so each review takes less time.

The close depends on a few people when the knowledge of hard accounts, accruals, and review sits with one or two senior accountants, so every difficult task waits in their queue and the close moves at their pace.

In the Sixthfin and Odoxa survey of 303 UK finance leaders, 35% named reliance on key individuals as a main close difficulty. Replacing those people is hard. The Controllers Council's 2026 talent study, published July 17, 2026, found that 44% named controllers and assistant controllers as the hardest finance roles to fill.

Concentrated work also drives errors and stress. In the same Gartner survey, 59% made several errors a month, and 18% made errors at least daily. Gartner tied those errors closely to low capacity. A close that depends on two people working late every month is a staffing risk and an accuracy risk at once.

You'll spot this cause when the same names own every task on your critical path, or when a close slips during one person's vacation. Write a short runbook for every recurring task, and train a second preparer for each critical one. Rotate tasks so the backup has done the work before they need to. A month-end close checklist with a named preparer, reviewer, and backup for every task makes the gaps visible.

Log five timestamps for every close task over your last three closes: input due, input received, ready for review, approved, and reopened, then record the hours of real work on each task separately.

The log shows two numbers that a checklist hides: how long each task waited, and which waits sat on your critical path. Run it before you hire a consultant, so any outside review starts from your own data.

Then work out two numbers for each task:

• Waiting timeElapsed business days from the input due day to approval, minus work hours ÷ 8
• Wait shareWaiting time ÷ elapsed time × 100

Finally, trace the critical path. Start at the period lock and walk backward through the task that finished last at each step. The bottleneck is the longest wait on that chain, even if another task takes more hours. For a phase-by-phase split of where a 10-day close spends its time, and the plan to cut it to five, see faster month-end close.

The team has a staff accountant, a senior accountant, and a controller. BD1 is the first business day after month-end, and a business day is 8 working hours. All numbers are illustrative.

The controller starts review on BD6 because task 4, the AP accrual, is ready only at the end of BD5. The senior accountant drafts it in 4 hours on BD3, then waits until the end of BD5 for budget owners to confirm which received-not-invoiced lines are real. So the bank and card reconciliations sit in the queue for three full business days, BD3–5, after they're finished.

The critical path runs through the late AP input, the budget owners' confirmations, the batch review, the late invoice, and the lock. Every other task is ready by BD4, so it has slack.

The critical path holds 4.0 days of work (32 hours) and 5.0 days of waiting, so 56% of its elapsed time is waiting. The other 48 of the 80 hours happen off the path, in parallel.

Three findings come out of the log:

• Adding a person wouldn't move the lock day.A fourth accountant could finish the 48 off-path hours sooner, but the path waits on an input, budget owners, and an invoice, so the period would still lock on BD9.
• Not every late input matters.The intercompany confirmations arrived two days late, but fixing them first wouldn't change the finish date, because they sat off the critical path.
• The three waits have clear fixes.An input calendar targets the 2.0-day AP wait, a received-not-invoiced list built from purchase order data, with standing estimates, targets the 2.5-day wait for budget owners, and a hard cutoff with a review threshold targets the 0.5-day re-approval. The BD8 invoice reopens the accrual only because the period is still open. Rolling review would also move most of the controller's 16 review hours off the path.

Once those waits shrink, a different chain becomes the longest, such as the 20 hours of other balance sheet reconciliations. Log the next close the same way to find the new path.

Make the fix that removes the longest wait on your critical path first, even if another task takes more hours, and buy software only after your time log shows which cause is yours.

Use the table to turn what your log shows into a first fix and a measure to track it.

Formulas and targets for these measures are in financial close KPIs. Track them for three closes after each fix, so you can see whether the finish date moved.

Software helps in two different ways. Close management tools track the checklist, owners, and sign-offs, which fixes status-chasing and gives leadership visibility. Tools that do the work, such as matching, reconciliations, and draft entries with support, shorten the preparation time on your critical path. Pick the type that matches the wait your log found, and compare options in best month-end close software.

A new ERP fixes a slow close only when the ERP itself is the cause, such as missing subledgers or no period lock. Queues for inputs and review move with you to a new system. Once the waits are gone, the next step is moving recurring work into the month, covered in continuous close and zero-day close.

The causes shift with size: small teams on QuickBooks lose days to receipts and one person doing everything, SaaS companies on NetSuite to billing and revenue data, and multi-entity groups to intercompany matching.

A 40-person QuickBooks Online company closing in two weeks needs a different first fix than a 200-person SaaS company on NetSuite. Run the same time log for either one, then start with the longest wait it shows.

On SAP S/4HANA or Business Central, the same causes and the same log apply, but check that the month is actually closed to posting after sign-off. In SAP S/4HANA you close the period in the posting period variant. In Business Central you move the Allow Posting From and Allow Posting To dates on the General Ledger Setup page, and posting dates set for individual users on the User Setup page override them, so review that list too.

Our Close Agent works your close checklist through the month on the schedules you set, and "Run all" starts every task whose inputs are ready. It stops and asks when data is missing, sends every task to a named reviewer separate from the preparer, and posts nothing to your ERP until an approver signs off the exact lines. Explore our Close Agent to see your close tasks prepared before your team starts reviewing.