FluxWorkflowsArticlesContact us
AI in the close

How Long Should the Month-End Close Take at a US$5M to 50M Company?

Flux Team · Updated 2026-11-03 · Workflow: All workflows

Five business days or fewer if you run one entity, and longer as you add entities. Vena's August 2026 survey of 624 US finance and accounting professionals found single-entity teams close in 4.7 business days on average. Teams with more than 10 entities took 8.3. In our view, structure predicts your number better than revenue.

What Do the Benchmarks Say?

Three recent surveys, three different samples, one picture.

Source Who was asked When What it found
Vena (FP&A vendor) 624 US finance and accounting professionals Fielded August 2026 Average close of 6.2 business days. Single entity 4.7; more than 10 entities 8.3
Ledge (close software vendor) 100 finance professionals, companies of 51 to over 10,000 employees Published April 2025 18% close in 1 to 3 business days, 32% in 4 to 5, 23% in 6 to 7, 27% in more than 7
Ventana Research (analyst firm) Sample not stated in the release Released July 2022 59% complete the monthly close within six business days, against 60% in 2019

The typical team closes in five to six business days. Ledge's respondents most often named 3 to 5 business days as a good close. In our view, under five is good, and past seven means days are going to waiting, not work.

Ventana's number barely moved between 2019 and 2022. Whatever teams bought in those years, the share closing inside six days stayed flat.

Why Is There No Benchmark by Revenue?

Because the public surveys don't cut it that way. None of the three reports close days by revenue band. Ledge spans companies of 51 to over 10,000 employees with no size split.

Ventana goes further. Similar companies, it found, "vary considerably in the number of days it takes them to complete their accounting cycle" (Ventana Research). Similar meant alike in revenue, headcount, location and industry.

So be wary of any "close days by company size" table that doesn't name its survey. What predicts your number is structure: how many entities, how many systems, and how much is reconciled by hand.

Which Number Should You Compare Yourself To?

Your setup Compare against Source
One entity 4.7 business days, average Vena
More than 10 entities 8.3 business days, average Vena
Some close data arrives by email or shared documents 6.8 business days, against 5.9 for everyone else Vena
Any 3 to 5 business days, the most common target Ledge

With one entity, compare yourself to 4.7. A seven-day close runs more than two days behind the average single-entity team. Vena doesn't report the bands in between, so a two or three entity company should expect to land between 4.7 and 8.3.

All three surveys report business days. We count from the last day of the period to reviewed statements, so reopened work counts too.

What Drives the Gap?

Four things, in the order we'd check them.

  1. Entities. Single-entity teams average 4.7 business days and teams past 10 entities 8.3 (Vena). Each entity adds its own recs, intercompany balances to agree and eliminations to book.
  2. Reconciliations by hand. Ventana found 72% of organizations that automate most or all of their reconciliations finish within six days. Where some or none of that work is automated, it's 25% (Ventana Research).
  3. Inputs that arrive late or by email. In Vena's survey, 37% of teams still source data from email or shared documents, and they close almost a day slower. In Ledge's, 56% named dependency on other departments as a blocker, the most cited one.
  4. Rework after "final." Vena found 78% of teams had to restate or correct numbers within the past year. Among the 488 teams that did, manual errors caused 28% and late or missing information from another department 27%.

The fourth one hides in the benchmark. A five-day close that gets reopened on day eight is an eight-day close.

Two Companies, Same Size, Different Close

Figures are illustrative.

Both companies have US$30M in revenue and a finance team of four. One closes in four business days, the other in nine.

Company A Company B
Entities 1 3, with intercompany
Systems feeding the close Ledger, AP tool, card platform Ledger, AP tool, card platform, payroll, two spreadsheets
Reconciliations Matching automated; team reviews exceptions Built by hand in Excel
Accrual inputs Pulled from PO and receipt data Emailed by four department heads
Review rounds One Two, after a late correction
Business days to close 4 9

Here is where Company B's five extra days go.

Cause Extra days
Intercompany agreed and eliminated at month-end 1.5
Recs built by hand 1.5
Waiting on department emails for accruals 1
Second review after a late correction 1
Total 5

Company B doesn't need a faster team. It needs fewer things that wait. We broke down where a slow single-entity close loses its days in Why a 100-Invoice Month Still Takes 8 Days to Close.

How to Close the Gap

  1. Agree intercompany early. We suggest agreeing balances with each other entity by business day 1, not after the trial balances are final.
  2. Move recs to matching plus exception review. The team reviews breaks, not every line.
  3. Replace emailed inputs with a list and a deadline. Accrue from PO and receipt data where you have it, and ask people only about what the data can't show.
  4. Set a cutoff per system. Card sync, AP and payroll each lock on a named day.
  5. Tie everything before the reviewer opens it. One review round, on judgment, not arithmetic.

Then measure the close the same way each month. Days to reviewed statements, and whether anything was reopened.

What to Automate vs Keep With a Person

Automate (calculate or draft):

Keep with a person:

How Flux Runs This

We embed with your team and map where your close days go, hour by hour. That includes the steps nobody wrote down: the spreadsheet one person rebuilds monthly, or the department head who always answers on day four. A close calendar built from the written procedure misses those, and they're where the days hide.

Then we run the work that's eating the days. Numbers are calculated in code and tied to your ledger before any words are written. AI is used only where judgment or drafting is needed, such as reading memos or drafting variance notes. It never does the math.

Anything the data can't explain becomes a flagged question with an owner, not a guess. Questions get asked on day one instead of found on day eight.

You review and sign off. Every correction is kept, so the next month runs faster.

We work from files you choose to export, with no system access. A mutual NDA is signed before any files are shared. For the free run, output comes back within two business days of complete files. The work gets cheaper for us to run each month, and you see that as a shorter close.

FAQ

What is a good month-end close time? Ledge's respondents most often named 3 to 5 business days. In Vena's 2026 survey, single-entity teams averaged 4.7 business days.

Does a bigger company take longer to close? Not by revenue alone. Entity count, systems and manual recs predict close days better. Ventana found companies with similar revenue and headcount vary considerably.

Should we count business days or calendar days? Business days, from period end to reviewed statements. The surveys cited here all report business days.

Is a 10-day close a problem? For a single entity, it's about twice the 4.7-day average in Vena's survey. Find out which of those days are waiting rather than work.

If your close runs past a week, send us a period you've already closed. We'll map where the days go and run one workstream free, so you can compare the output line by line with your own. See how the free run works.

Contact us