Average Month-End Close Time: Benchmarks by Company Size

Deepak Anchala
Co-Founder and CEO, Adopt AI4 November 2026

Your CFO asks whether a seven-day close is good. You do not know. Your last survey said the average was somewhere near six days, a peer told you theirs takes three, and the auditors mentioned a company that closes in one. Each number is true for someone, and none of them tells you what to do about yours.
The average month end close time is a range, not a point. This post lays out the ranges finance teams report at each company size, explains why published benchmarks disagree, and shows how to measure your own close so the comparison holds up.
What is the average month-end close time?
Finance teams report close times from 3 business days to 20. In our conversations with controllers and CFOs, 6 to 14 days is the band we hear most often. A fast-growing startup might close in 7 or 8 days and call it slow. An acquirer with several systems might take 9 or 10. A multi-location operator with a small finance team can slip from a 15th-of-the-month target to the 30th.
Goals are tighter than results. The teams we talk to set a target of 3 to 5 business days, and most of them sit well above it today.
That gap is the useful finding. The average month end close time tells you where the field is. The target tells you where the work is.
Average close time by company size
Size matters because it sets how many things must tie out before the books lock. Use the table as a map of drivers, then plug in your own days.
| Company profile | Reported range | What stretches the close |
|---|---|---|
| Under 50 employees, one entity | 3 to 10 business days | One person owns everything; the close waits on their calendar and on outside accountants |
| 50 to 200 employees, one or two entities | 5 to 10 business days | Accruals and prepaid schedules in spreadsheets; manual bank and card reconciliations |
| 200 to 1,000 employees, several entities | 6 to 14 business days | Intercompany eliminations, multiple banks, review layers |
| 1,000+ employees, multi-ERP | 7 to 20 business days | Consolidation, currency translation, many contributors, system handoffs |
These are ranges teams report to us, not survey statistics. We have not tied them to a single published dataset, and you should treat any table that does with the same caution (more on that below).
Two points stand out. First, the ranges overlap heavily. A 40-person company with a messy cutoff can take longer than a 400-person company with a clean calendar. Second, the long tail comes from structure: more entities, more banks, more handoffs. Headcount in accounting does not scale with them, so each added entity adds days.
Why published benchmarks disagree
Search for the average close time and you will find figures that differ by days. Four things cause that.
The start and stop points differ. Some surveys stop the clock when the trial balance is final. Others stop at the board package, or at lock. A close that is 4 days to trial balance and 8 days to board package has two correct answers.
Business days and calendar days get mixed. A 10-calendar-day close and a 10-business-day close differ by four days. Ask which one the source used.
Respondents skew large or small. A survey of public companies reports different results from one of owner-operated businesses. Neither is wrong. Neither is you.
The close is not one thing. A soft close, where management books are ready, finishes before the hard close, where the period locks. Read Soft Close vs Hard Close before you compare your days to anyone's.
When you cite a benchmark to your CFO or board, say which stop point it uses and which population it surveyed. A number without those two facts invites an argument you will lose.
How to measure your own close time
You need one definition and three months of data. Do this before you compare to anyone.
- Pick the stop point. We suggest controller sign-off and period lock, because that is when the numbers become usable and the period closes to new entries.
- Count business days from period end. Day 1 is the first business day after the last day of the month.
- Log the date each major task finishes. Bank reconciliations, subledger close, accruals, intercompany, flux review, and sign-off. The calendar view in Close Calendar shows how to structure it.
- Record the days after lock. Count every adjustment posted after sign-off. A close that locks on day 5 and reopens on day 8 is an 8-day close.
- Track the trend for three months. One month is noise. A seasonal quarter-end can add days that a normal month does not.
The Days to Close entry gives the formula. The output is one number per month, and the number you can defend in a review.
Where the days actually go
Most of a long close sits in a few places, and they are the same places across company sizes.
- Waiting for data. Bank statements, card feeds, payroll files, and subledger exports arrive on different days. The reconciliation cannot start until the statement does.
- Reconciliations. Two to four hours per bank account adds up fast. A team with 80 accounts spends days here before any judgment work starts.
- Accruals and adjusting entries. Each one needs support, and the support lives in someone's inbox.
- Review loops. The reviewer finds a question, the preparer finds the answer, and the item goes around again.
- Variance write-ups. Explaining the flux takes a day when the data is clean and three when it is not. See Flux Analysis: The Complete Guide.
Look at your own task log. If waiting and reconciling account for most of your days, a faster spreadsheet will not shorten the close. A calendar that moves work earlier will.
What moves the number
Teams that shorten the close tend to do four things, in this order.
- Fix cutoff. Agree on the last day each input is accepted, and publish it.
- Move work out of the close window. Reconcile weekly, accrue recurring items on a schedule, and keep the period-end list short. The month-end close checklist shows which tasks can start before day 1.
- Write a close calendar with dependencies. A critical path shows which late task delays the lock. How to Close the Books Faster walks through the seven steps.
- Let agents prepare while people review. Matching, tie-outs, and first-draft variance explanations are preparation work. A reviewer who starts from a finished draft with the support attached spends the day on judgment.
The fourth step changes the shape of the work. Adopt's agents run the matching and tie-outs in the background, so by the first of the month the reconciliations are already waiting for review, and nothing posts without a person's sign-off. The controller's day moves from assembling the numbers to approving them.
Use the benchmark to set a target
A benchmark is a starting point for a conversation, and the useful version of that conversation has three numbers: your current days, your goal, and the days you can remove from the biggest task.
If your close takes 9 days and your goal is 5, find the four days. Look at your task log, circle the longest dependency chain, and ask what would have to be true for it to finish two days earlier. That question has an answer. "Why are we not at the average?" does not.
Measure one close with the five steps above, then sign up free and bring your messiest reconciliation, or book a pilot to see what review-first preparation does to your days.
FAQs
Related Articles
How to Automate Bank Reconciliation, Including Banks With No API

Why we bet Adopt AI on agents running the office of the CFO

See it running on your workflows
Automate your accounting workflows

