The median organization completes its monthly consolidated financial statements in six calendar days, according to APQC’s Open Standards Benchmarking data drawn from 11,223 companies. Half the market is slower than that.
If you are asking how long a month-end close should take at your company size, the honest answer is that size matters far less than three or four structural things that actually set your timeline. This article shows you which ones, and what the sourced benchmarks really say.
How long should a month-end close take? The short answer
A healthy month-end close takes three to six business days for most companies. Single-entity businesses with clean data can finish in two to four days, multi-entity organizations with inventory and audit requirements typically need six to ten, and anything past ten days signals a process problem rather than a complexity problem.
That range holds up against every credible dataset. What does not hold up is the assumption that your headcount tells you where in the range you belong.
One warning before you compare yourself to anything
Benchmark tables mix calendar days and business days without telling you, and the two are not interchangeable. APQC’s six-day median is measured in calendar days; most vendor surveys report business days.
A “six-day close” can therefore mean six calendar days or roughly eight. Check the unit before you conclude you are behind.
What the sourced benchmarks actually say
Four datasets are worth anchoring to. Everything else circulating in blog posts traces back to one of them.
APQC: six calendar days is the median, across 11,223 organizations
APQC measures cycle time in calendar days from period end to completed consolidated financial statements. The public median is 6.0 days on a sample of 11,223 companies, which makes it the largest and most defensible anchor available.
This is the number to hold yourself against if you want one figure. It spans industries, sizes, and geographies rather than a single vendor’s customer base.
Ledge’s 2025 survey: half of finance teams still need six or more business days
Ledge surveyed 100 finance professionals at companies ranging from 51–200 employees to over 10,000. The distribution: 18% close in one to three business days, 32% in four to five, 23% in six to seven, and 27% take more than seven.
Read that as a bell curve with a long tail. The modal team lands at four to five business days, but a quarter of the market is still spending more than a working week on the close.
Ventana Research: 53% finish the monthly close inside six business days
Ventana Research (now part of ISG) found that only 53% of companies complete their monthly close within six business days, and just 40% manage it for the quarterly close.
Ventana adds a caveat worth repeating: those numbers are probably flattering. Some organizations report a week-long close and then post material adjustments for several days afterward.
The paradox nobody quotes: bigger finance functions close slower
APQC publishes a separate measure for finance shared services centers. The median there is 8.0 calendar days on a sample of 3,303 organizations, two full days slower than the all-company median.
Shared service centers are, almost by definition, larger and more centralized. Consolidating the close into a dedicated function does not automatically speed it up, and that single data point undermines most of the “bigger company, longer close” logic you will read elsewhere.
Month-end close benchmarks by company size
Here is the part most articles get wrong. No major public survey publishes a clean days-to-close table broken out by revenue band or headcount, which is why the tables you find are either unattributed or quietly extrapolated.
So the ranges below are built honestly: sourced anchors where they exist, clearly labelled practitioner targets where they do not.
| Company profile | Typical close length | Realistic target | What sets the timeline |
| Under 50 employees, single entity | 3–7 business days | 2–4 business days | Bookkeeping discipline and bank feed hygiene |
| 50–250 employees, 1–2 entities | 4–8 business days | 3–5 business days | AP volume, accrual completeness, approval delays |
| 250–1,000 employees, multi-entity | 5–10 business days | 4–6 business days | Intercompany, consolidation, inventory |
| 1,000+ employees, private | 6–12 business days | 5–7 business days | Entity count, regional dependencies, controls |
| Public filers (any size) | 4–8 business days | 3–5 business days | Statutory reporting deadlines |
| Finance shared services centers | 8 calendar days (APQC median) | 5–6 calendar days | Handoff latency between regions and the centre |
Two rows in that table are directly sourced. The rest are practitioner ranges consistent with the APQC, Ledge, and Ventana distributions, and you should treat them as orientation rather than gospel.
Under 50 employees: your close should be short, and often isn’t
A company this size has one entity, one ERP, and a handful of bank accounts. There is no structural reason a close here should run past four business days.
When it does, the cause is almost always upstream: invoices arriving late, uncoded transactions, or one person holding the whole process in their head. The fix is scheduling discipline, not software.
50–250 employees: the band where closes quietly get worse
This is where AP volume outgrows manual handling. Invoice counts climb into the hundreds or low thousands per month, approvals scatter across department heads, and the accrual for anything not yet invoiced becomes genuine guesswork.
Teams in this band often report the same close length they had at 60 employees while working significantly harder to hold it. That flat line is the warning sign, because effort is absorbing growth that the process should be absorbing.
250–1,000 employees: consolidation becomes the critical path
Multiple entities mean intercompany reconciliation, elimination entries, and currency translation. Add inventory and the close now depends on operational counts you do not control.
At this size the bottleneck stops being data entry and becomes waiting. Ledge found 56% of teams cite dependency on other departments or regions as their primary blocker, which is the dominant constraint in this band.
1,000+ employees and public filers: deadlines replace guidelines
Large private companies have the most entities and the loosest external pressure, which is exactly why their closes drift. Public filers face the opposite: a legal ceiling that forces discipline.
Regulatory deadlines are the only genuinely hard close benchmark that exists, and they are set by company size. More on that below.
The four drivers that actually set your close length
Company size correlates with close length, but it does not cause it. These four things do.
1. Entity and consolidation count
Each additional legal entity adds a reconciliation, an elimination, and a handoff. Two entities is not twice the work of one, but eight entities is considerably more than four.
Entity count predicts close length better than either revenue or headcount. A 90-person group with six entities will close slower than a 600-person single-entity business, every month.
2. How dirty the data is when it arrives
The close does not create errors; it discovers them. Miscoded invoices, missing PO matches, and duplicate vendor entries all originate weeks earlier in accounts payable.
Every hour spent correcting AP data during the close is an hour that should never have been in the close at all. This is the single most controllable driver on the list, and the least often addressed.
3. Where the dependencies sit
If your close depends on a warehouse count, a regional controller’s submission, or a department head’s approval, your timeline is set by the slowest of them. Sequential dependencies compound; parallel ones do not.
Ledge’s respondents ranked cross-departmental dependency as their top blocker at 56%, ahead of Excel at 50%. The bottleneck is usually organizational, not technical.
4. Whether anyone is actually waiting for the number
Closes expand to fill available time. A company whose board reviews results on day five has a five-day close; a company where nobody asks until the 20th has a 20-day close.
Deadline pressure is the most underrated close accelerator there is. If your close has been ten days for three years, check whether anyone downstream has ever asked for it faster.
The hard deadline: what public company rules imply for everyone else
Public filers face statutory reporting deadlines that scale inversely with company size, and the SEC’s accelerated filer framework sets them explicitly:
- Large accelerated filers (public float of $700 million or more): 60 days for the 10-K, 40 days for the 10-Q
- Accelerated filers (float of $75 million to under $700 million): 75 days for the 10-K, 40 days for the 10-Q
- Non-accelerated filers (float under $75 million): 90 days for the 10-K, 45 days for the 10-Q
Note the direction of travel. The largest, most complex companies get the shortest deadline, which tells you complexity is not a defence for a slow close.
Those windows cover the close, review, audit, and drafting. Working backwards, a large accelerated filer generally needs the books closed inside five business days to leave room for everything else.
If a multi-billion-dollar filer can hit that, a 200-person private company has no structural excuse for twelve.
Red flags that your close is too slow for your size
Length alone is a weak diagnostic. These signals matter more:
- Post-close adjustments are routine. If material entries land after you have “closed”, your real close is longer than your reported close.
- The timeline varies by more than two days month to month. Volatility means the process depends on individuals rather than structure.
- Nobody can tell you the status mid-close. If answering “where are we?” requires phoning three people, you have no process, you have a habit.
- The same reconciliation breaks every month. A recurring break is an upstream data problem wearing a close-process costume.
- One person’s holiday delays the close. Single points of failure are the most common cause of a good close becoming a bad one.
- Your team works weekends every month. A close that only completes on unpaid overtime is not a five-day close.
A target close calendar by company size
Working targets, mapped to business days after period end:
| Day | Under 250 employees | 250–1,000 employees | 1,000+ / multi-entity |
| Day 1 | Cut-off enforced, AP and AR sub-ledgers closed | Sub-ledgers closed, entity data submitted | Local cut-off, regional submissions opened |
| Day 2 | Bank and card reconciliations complete | Cash and AP reconciliations complete | Entity-level reconciliations complete |
| Day 3 | Accruals and prepaids posted, first draft TB | Accruals, inventory, intercompany matched | Intercompany matched, eliminations drafted |
| Day 4 | Variance review, adjustments posted | Consolidation run, variance review | Consolidation run, currency translation |
| Day 5 | Books closed, reporting pack issued | Adjustments posted, review complete | Variance commentary, controller review |
| Day 6 | n/a | Books closed, reporting pack issued | Adjustments posted |
| Day 7 | n/a | n/a | Books closed, reporting pack issued |
If your calendar has activities sitting on day eight or later, work backwards and ask which of the four drivers put them there.
How to compress your close cycle without adding headcount
Most close acceleration projects target the wrong end of the process. They automate the reporting and leave the data problems untouched.
| Dimension | The traditional close | The compressed close |
| When data quality is fixed | During the close, by the accountant | Upstream, at invoice capture |
| Reconciliations | Manual, in Excel, per account | Automated matching with exception queues |
| Variance analysis | Rebuilt in spreadsheets each month | Continuous, with drilldown to transactions |
| Task tracking | Shared checklist and email chasing | Owned activities with dependencies and status |
| Journal entries | Retyped from reconciliation workings | Generated from the reconciliation, approved, posted |
| Workpapers | Assembled at audit time | Generated as the close runs |
| Audit trail | Reconstructed from file versions | Logged continuously per adjustment |
| Visibility | Controller asks; team answers | Real-time dashboard for the whole team |
| Failure mode | One person’s absence stops the close | Ownership and reviewers are explicit |
| Where the time goes | Finding and fixing errors | Reviewing exceptions and explaining results |
The practical sequence matters more than the tooling:
- Enforce a hard AP cut-off and mean it. Invoices arriving after cut-off go to next period, full stop.
- Fix data at capture, not at close. Structured, validated invoice data eliminates the corrections that make accounts payable reconciliation the longest task in most closes.
- Parallelise everything that does not depend on something else. Reconciliations rarely need to be sequential, but checklists make them so.
- Automate the recurring reconciliations first. The ones that break every month are the highest-return targets.
- Make variance analysis continuous. Running variance analysis only at close means you discover problems when it is most expensive to fix them.
- Publish close status where everyone can see it. Visibility does more for timelines than any single automation.
When close automation actually makes sense, and when it doesn’t
Software will not fix an undisciplined close. If your timeline slips because cut-offs are negotiable and nobody owns tasks, automation will simply make a disorganised process faster at being disorganised.
Three signals suggest tooling is the right next move. You are re-performing the same reconciliations every month, your accountants spend more close time correcting AP data than reviewing it, and your entity count has grown past what one consolidation spreadsheet can hold safely.
Three signals suggest it is not. Your close is short but your reporting is late, which is a reporting problem rather than a close problem.
Your team is one person, where process discipline returns more than software every time. Or you are mid-ERP-migration, where adding a layer on unstable data rarely ends well.
This is the reasoning behind how DOKKA’s financial close automation is built. Reconciliations, flux analysis, journal entries, and workpapers run against clean upstream data from AP automation rather than against whatever arrives in the general ledger, because the cheapest close problem to solve is the one that never enters the close.
DOKKA is built for mid-market finance teams of roughly two to ten people, with native integrations for SAP Business One, NetSuite, QuickBooks, and Priority. If you run a 40-person finance function across thirty entities, BlackLine or OneStream is the more honest recommendation.
Frequently asked questions
How long should month-end close take?
Three to six business days for most companies, with APQC benchmarking across 11,223 organizations putting the median at six calendar days to completed consolidated financial statements.
Simple single-entity businesses should target two to four days. Multi-entity groups with inventory typically need six to ten.
What is a good month-end close time by company size?
Under 250 employees with one entity should target three to five business days. Companies of 250 to 1,000 employees with multiple entities should target four to six.
Above 1,000 employees, five to seven business days is realistic. Entity count matters more than headcount at every level.
Is a 10-day month-end close too long?
For most companies, yes. Ten calendar days puts you at the bottom of APQC’s distribution and behind the 53% of companies that Ventana Research found close within six business days.
It is defensible for a highly complex multi-entity group with inventory and statutory audits in several jurisdictions. It is not defensible for a single-entity business.
Why does month-end close take so long?
The dominant causes are organizational rather than technical. Ledge’s 2025 survey found 56% of teams blocked by dependency on other departments or regions, 50% by managing the close in Excel, and 40% by legacy systems without integration.
Underneath all three sits data quality. Most close time is spent finding and correcting errors that originated upstream in accounts payable.
Do larger companies always take longer to close?
No, and the data pushes back on the assumption. APQC’s median for finance shared services centers is 8.0 calendar days across 3,303 organizations, two days slower than its 6.0-day all-company median, despite shared services being a large-company structure.
Public filers close faster than many mid-market private companies because external deadlines force discipline. Complexity slows you down; scale on its own does not.
What is the difference between a soft close and a hard close?
A soft close skips certain procedures to produce faster management numbers, typically by estimating accruals and deferring detailed reconciliation. A hard close performs the full set of procedures to produce auditable statements.
Many teams run soft closes in months one and two of a quarter and a hard close in month three. Doing so honestly requires knowing which estimates you have made.
How much can automation reduce close time?
Be sceptical of any single percentage, because published figures come from vendor samples rather than controlled studies. What is measurable is where the time goes: if reconciliations and data correction consume most of your close, automating those tasks moves the timeline; if you are waiting on regional submissions, it will not.
Model it against your own task times instead. A financial close automation ROI calculator is a more useful input than an industry average.
Should close benchmarks be measured in business days or calendar days?
Pick one and state it, because the difference is material. APQC reports calendar days from period end; most vendor surveys report business days.
A five-business-day close is roughly seven calendar days. Comparing a business-day figure to a calendar-day benchmark makes you look about 30% faster than you are.
Closing faster starts before the close
The benchmark you should hold yourself to is three to six business days, adjusted for entity count rather than headcount. The companies that hit it are not working harder during the close; they are arriving at it with cleaner data and fewer dependencies.
Start by measuring where your close time actually goes, then ask how much of it is correcting problems created weeks earlier. That answer usually points upstream.
Want to see what an automated close built on clean AP data looks like in your ERP? Book a demo.
