It’s the same conversation every month.
The financial controller has been in the office since 8 am. The accounting team is working through lunch. Someone is chasing the regional office for a number that should have arrived two days ago. Management wants the P&L by Thursday. It’s Tuesday, and the data isn’t clear yet.
If this sounds familiar, you’re not behind; you’re in the majority.
Read more:What is Stopping Your Organisation from Adopting Continuous Close?
According to Ledge‘s 2025 Month-End Close Benchmarks report, only 18% of finance teams close their books within three days. APQC’s General Accounting Open Standards Benchmarking survey, covering 2,300 organisations, puts the median at 6.4 calendar days, and the bottom 25% take ten or more. The typical organisation spends more than a working week on close every single month.[¹][²]
The uncomfortable question isn’t whether your close is slow. It’s what that slowness is actually costing you, and whether you’ve ever sat down to calculate it properly.
Why does the month-end close take so long?
Most finance teams don’t have a slow close because they’re inefficient. They have a slow close because the systems underneath the close weren’t designed for speed.
The problem usually comes down to three things that feed each other.
The first is data that lives in too many places. Transactions happen in one system. Expenses are tracked in another. Revenue comes from a third. Fixed assets sit in a spreadsheet maintained by one person. When it’s time to close, someone must gather all the data, check it for consistency, reconcile any differences, and consolidate it into a single place. That process alone can take days, and it has to happen every single month.
The second is Excel. Not because Excel is inherently bad, but because Excel was never designed to be the backbone of a consolidation process. Ledge’s 2025 benchmarks found that 94% of finance teams still rely on Excel for close activities, and half of those teams cite it as a key reason their close runs slow.[¹] When the month-end workflow runs through a shared spreadsheet, you get version control problems. You get formulas that break when someone adds a row. You get one person who understands the model and everyone else who is afraid to touch it. When that person is on leave, the close stops.
The third is approval chains that weren’t built for speed. Journals waiting for sign-off. Intercompany transactions require coordination across time zones. Payments that can’t be processed until someone approves them in a system they haven’t logged into since last month. Each of these takes a few hours. Added together across a full cycle, and you’re looking at days.
None of these are new problems. Finance leaders have been dealing with them for years. But familiarity with a problem doesn’t mean it isn’t costing you.
What does a slow month-end close cost your business?
The most visible cost is time. A finance team spending ten days closing the books isn‘t doing anything else for those ten days. No analysis. No forecast. No looking ahead. Just getting the numbers to a point where they can be trusted.
The industry benchmark for what’s achievable is a three to five-day close. Top-quartile finance teams close in around 4.8 days.[²] The difference between a ten-day close and a five-day close, for a team of four people working twelve months a year, is roughly 240 person-hours annually. The equivalent of six full working weeks of finance capacity sitting inside the close process. That’s time that could be spent on budgeting, forecasting, business partnering, or any of the strategic work finance is supposed to do but rarely has time for.
The second cost is decision quality. Management reports are produced at the end of a ten-day close. They are already ten days old when they’re delivered. For a business making pricing, staffing, or investment decisions based on that data, ten-day-old information is not the same as current information. The gap between when something happens in the business and when leadership can see it is the window during which problems can grow undetected, and opportunities can be missed.
Many CFOs describe a version of the same frustration: by the time the board sees the numbers, they’ve already had to make decisions based on instinct that should have been made on data.
The third cost is the people cost. Finance teams that spend the first half of every month in a close cycle are operating under chronic pressure. Ledge’s research found that cash reconciliation alone takes between 20 and 50 hours per month for many teams, and if even one source is delayed, it pushes back the entire close.[¹] The manual, repetitive nature of that work is not why skilled finance professionals chose the profession. Turnover in finance roles is expensive. The predictable grind of a long close is one of the most underestimated factors.
Is a 3-day month-end close actually achievable?
A finance team that closes in three to five days isn’t working harder. It’s working on a different underlying structure.
The distinguishing characteristics are: data that flows automatically from source systems into one place rather than being manually collected; a chart of accounts flexible enough to report on what management actually needs to see without requiring manual reclassification; approval workflows that run inside the system rather than through email chains; and reconciliation that happens continuously rather than as a month-end exercise.
APQC research shows that organisations with widespread adoption of a standard chart of accounts can shave approximately two days off their close time alone.[²]
90% Less Manual Work: How Did Radisson Blu Hotel Increrase Their Financial Efficiency? →
None of this is theoretical. Finance teams operating this way exist across every industry. From single-entity businesses to organisations spanning multiple countries and currencies. The common thread is not the size of the organisation or the sophistication of the team. It’s whether the systems supporting the close were built to help the close happen faster, or whether they were built for something else and adapted over time.
The gap between a ten-day close and a five-day close is, in most cases, not a skills gap. It’s an infrastructure gap.
How do you speed up your month-end close process?
If your close is running longer than you want, the most useful first step is a clear picture of where the time is going.
Map the close process from the final transaction of the month to the moment the P&L is delivered to management. Note every step that requires a person to manually move, transform, or reconcile data. Note every step that depends on input from another system, another team, or another location. Note every approval that runs outside the system.
That map will tell you more about what needs to change than any benchmark survey. The bottleneck is usually obvious once it’s written down, and it’s almost always in one of the three places described above.
The question after that is what to do about it. That’s a longer conversation, and the right answer looks different for every organisation. But the starting point is the same: knowing exactly what your close is costing you, in time and in the decisions being made without current data.
How to choose the right solution for your current situation? Share your concerns with us and let’s explore all the possibilities!
Sources
- Ledge, The State of Month-End Close in 2025: Finance Team Benchmarks & Insights (April 2025), https://www.ledge.co/content/month-end-close-benchmarks-for-2025
- APQC, Metric of the Month: Cycle Time for Monthly Close, as reported by CFO.com, https://www.cfo.com/news/metric-of-the-month-cycle-time-for-monthly-close/659297/
- Numeric, How Long Does Month-End Close Take? Examining Benchmarks, https://www.numeric.io/blog/how-long-does-month-end-close-take
