Six months after a new ERP goes live, most finance teams are still closing the books in 10 to 15 days. The technology works. The dashboards are configured. The integrations are running. And yet the close hasn’t gotten meaningfully faster, the team is still spending nights on spreadsheet reconciliations, and the CFO is starting to wonder whether the implementation cost was worth it.
We’ve seen this pattern enough times to recognize the failure mode. It’s not the software. It’s not the team. It’s the assumption that the close gets faster automatically once the new system is live.
The story behind every stalled close
A finance transformation usually starts with a clear pain point: the month-end close takes too long, ties up too much analyst time, and produces numbers that are already stale by the time the leadership team reviews them. The CFO sponsors a project. A new ERP — NetSuite, Workday, SAP, Dynamics — gets selected, implemented, configured. Go-live happens. Champagne is opened.
Six months later, the close is still taking 10 days. Sometimes 11. The team is exhausted. And nobody knows quite what went wrong, because the system works. The journal entries flow. The consolidations run. The reports generate. Everything the project plan said would happen, happened.
What’s missing isn’t software. It’s the surrounding architecture that makes the software useful.
The four reasons closes stall
1. The process wasn’t redesigned
Most implementations port the old process into the new system. The close still has 47 sequential steps. There are still three manual reconciliations between sub-ledgers. The intercompany eliminations still require an analyst to download CSVs and manipulate them in Excel before re-uploading. The system is new, but the workflow is identical.
If you ask the finance team what changed, they’ll often answer “the screens look different.” That’s the tell. The process should be redesigned before the system is selected, not after — otherwise you’ve spent six months and $500K automating workflows that should have been eliminated.
2. Adoption was an afterthought
The implementation team trained the finance team on the new system in week 8. By week 12 of operating in the new environment, half the team has reverted to their pre-launch habits. They’re exporting data out of the new ERP into Excel, doing their work the old way, and pasting the result back in. The system thinks they’re using it. They’re not.
This is the most common failure we see. Change management isn’t a phase you do once before go-live — it’s a continuous practice for the first six months after.
3. Data quality wasn’t addressed
The new ERP is configured beautifully. But the data feeding it is still messy: customer master records have duplicates, vendor data is inconsistent across entities, and the chart of accounts wasn’t rationalized during migration. The system surfaces the mess faster than the old one did, which makes the close feel slower, not faster.
4. Reporting wasn’t reimagined
The new system has powerful reporting. But the finance team is still generating the same 14 reports it used to, because that’s what leadership expects. The new ERP could give them a real-time financial dashboard. Instead it’s being used as a transaction processor with a dressing of fresh paint.
The five-step recovery playbook
If you’re 6–18 months post-implementation and the close hasn’t accelerated, here’s how we approach the recovery:
Step 1 — Diagnose, don’t blame
Spend two weeks mapping the actual current-state close process — what really happens, not what the project plan said would happen. Time-stamp every step. Identify the three slowest steps; they’ll account for 60–80% of the total elapsed time.
Step 2 — Redesign the top three bottlenecks
Most close acceleration comes from fixing the top three bottlenecks, not from improving everything 10%. Common candidates: intercompany eliminations, sub-ledger reconciliations, manual journal entries. Each one is usually a candidate for automation that was deferred to “phase 2” and never came back.
Step 3 — Address the data layer
Run a data quality audit on the customer master, vendor master, and chart of accounts. Clean what’s salvageable, archive what’s not. Establish ownership: who is responsible for keeping each master record clean going forward?
Step 4 — Re-engage the team
The finance team has been operating on autopilot for six months. They’ve built workarounds. They’ve stopped suggesting improvements because the original ones got ignored. Hold a structured “what would make this 50% faster?” session — with promises kept, and acted on within 30 days. Adoption is a trust problem more often than it’s a training problem.
Step 5 — Rebuild the reporting layer
Replace the legacy reports one at a time with real-time dashboards that surface the metrics leadership actually uses. This is the visible win — and it’s the win that buys you credibility to keep optimizing the rest.
What “fixed” looks like
A successful close acceleration takes a 10–15 day cycle down to 3–5 days within six months, and frees up 30–40% of analyst time previously spent on transaction processing. The finance team starts contributing strategically: scenario modeling, decision support, real-time variance analysis. The CFO becomes a strategic partner to the CEO rather than a reporter of the past.
None of this happens by reinstalling the ERP or buying additional software. It happens by addressing the four reasons closes stall — in the right order, with the right discipline.
Read more: Finance Transformation for Modern CFOs — our overview of how we approach finance modernization. Or continue with Process Before Platform — the working framework that underpins every transformation we run.