The Anatomy of a Mid-Market Close: Where the Days Really Go
Ask a controller how long the close takes, and you’ll get a number of days. Ask them what happens during those days, and most can’t tell you. Not because they don’t know the work. It’s that no one has ever actually mapped it. The close gets a start date and an end date, and everything in between is just “the close.”
That gap matters, because it hides which part of the calendar is actually expensive.
What a mid-market close is made of
Strip a typical month-end down to its real stages, and it looks something like this:
- Data pull and assembly. Exporting from the ERP, gathering subledger detail, chasing down entities or departments that haven’t submitted yet.
- Reconciliation and tie-outs. Bank, intercompany, subledger-to-GL: matching everything that has to match before anything else can happen.
- Report build. Reformatting exported data into the layouts leadership, lenders, or the board actually expect to see.
- Review and adjustments. Catching what’s off, booking accruals and reclasses, chasing down the one number that doesn’t tie.
- Board pack and distribution. Assembling the final package and getting it to the people waiting on it.
- Sign-off. The last check before the numbers are called final.
Most finance teams have never put a percentage against each of these. They know the close “takes a week.” Few know that reconciliation alone is probably eating more of that week than anything else.
Where the time actually concentrates
Industry benchmarking gives a rough picture. Ledge’s 2025 State of Month-End Close survey found that half of finance teams still take six or more business days to close, and only 18% close in three days or less. A PwC Finance Benchmarking analysis puts the median close at 6.4 days across companies of varying size.
Reconciliation is consistently the single biggest line item inside that timeline. Multiple close-benchmarking studies estimate that manual reconciliation work (bank, cash, intercompany, subledger tie-outs) consumes somewhere between 30% and 40% of total close-cycle time, with individual team members logging 10 to 20 hours a month on reconciliations alone.
Putting those pieces together into a rough stage breakdown for a mid-market close (this is a synthesized estimate from aggregated benchmarks, not a single primary study, so treat it as directional):
| Stage | Approx. share of close time |
| Data pull & assembly | ~25% |
| Reconciliation & tie-outs | ~35% |
| Report build / reformatting | ~15% |
| Review & adjustments | ~15% |
| Board pack & distribution | ~5% |
| Sign-off | ~5% |
Roughly three-quarters of a typical close, on this breakdown, is data assembly and mechanical tie-out work. Review and analysis, the part that actually requires judgment, is a fifth of the calendar at best.
Assembly, not analysis
That split is the uncomfortable part. Most of what eats a close isn’t controllers or analysts thinking about the numbers. It’s controllers and analysts moving numbers around: pulling them out of one system, reshaping them for another, checking that two versions of the same figure actually agree.
None of that work is a skill problem. The team isn’t slow. The calendar is just structured so that the majority of the hours go to assembly before anyone gets to look at what the numbers mean. As one recent look at the relationship between close design and audit outcomes put it, “audit readiness is not a phase. It is an outcome of how your close actually works.” The same is true of speed. A close built around manual assembly keeps costing the same hours no matter how the team around it improves.
This is also why “hire better people” or “tighten the checklist” only moves the needle so far, which is a theme worth sitting with on its own. The bottleneck isn’t who’s doing the work. It’s how much of the close is built around moving data rather than interpreting it.
The question worth asking
If you mapped your own close the way it’s mapped above, where would the biggest block of time land? And if you could get one stage back, not eliminate it, just get the hours back, which one would you choose?
See Where Your Team is Leaking Hours + Download Free Guide
![]() |
![]() |
Reading about the problem is one thing. Seeing it mapped to your own team is more useful. We built a free Lean Finance Self-Assessment for exactly that, a quick diagnostic that pinpoints where your close, your reporting, and your team’s time are quietly bleeding capacity.


