Why ERP Implementations Fail, and What CFOs Can Do About It

Gartner expects more than 70% of recently implemented ERP initiatives to fall short of their original business case goals by 2027, with as many as a quarter failing outright.¹

For a CFO, that number lands differently than it does for IT. The business case usually carries finance's signature. When the system goes live and the month end close slips by a week, the board turns to the finance function for answers.

ERP failure is rarely a mystery, though. The same causes appear on project after project, and most of them are visible well before go-live. Below, VantagePoint's consultants set out seven of them, drawing on what we see on live engagements, with practical steps to avoid each one.

The cost of failure

Birmingham City Council is the UK's most expensive recent example. Its move from SAP to Oracle was budgeted at around £20 million. The council's latest forecast for the programme is £144.4 million to 2027/28,² and an independent analysis by the University of Sheffield's Audit Reform Lab put the total financial impact at £216.5 million.³ The failed implementation left Europe's largest local authority unable to produce auditable accounts and contributed to its effective bankruptcy in 2023.⁴

The private sector isn't immune. Medical device maker Zimmer Biomet is suing Deloitte for at least $172 million over its SAP S/4HANA rollout,⁵ claiming the business was barely operational for a quarter after go-live and unable to ship products or issue invoices.⁶ Deloitte disputes the claims and has called the lawsuit meritless.⁷

Neither project failed because of the software. Both show patterns that finance leaders can spot early.

1. The business case is too vague to say no to anything

When objectives are loose, every feature request looks reasonable and scope has nothing to push against. A 2023 Gartner survey found 73% of technology leaders said their ERP strategy wasn't strongly aligned with business strategy.⁸ In the Zimmer Biomet case, the company alleges 51 change orders added $23 million to a $69 million contract.⁹

How to avoid it: Write objectives in finance terms. Days to close, cost per invoice processed and forecast accuracy are measurable; "better visibility" isn't. Price every change request against the business case before it's approved, and make sure finance has a permanent seat on the steering committee rather than an occasional invitation. An independent advisory support in development of said business case before board sign-off is cheaper than a mid-project reset.

2. Selection starts before requirements are clear

Most fit gaps are avoidable. They appear when a business goes into selection without a clear picture of how its own processes run, so the questions that matter most never get asked. According to Panorama Consulting's 2026 ERP Report, the most common cause of budget overrun was an unexpected need for additional technology: a fit gap that should have surfaced during selection.¹⁰

How to avoid it: Map your processes before you speak to a vendor. Use that map to shape the demos you see, so each one walks through your real scenarios, such as an intercompany elimination or a foreign currency revaluation. A demo built around your own processes and data tells you far more than a general product tour, and it gives the vendor a fair chance to show how their system handles your business. Before you sign, meet the people who will deliver your project and ask what they've implemented for businesses like yours.

3. The project automates a broken process

A new ERP will run your existing process faster. If that process relies on spreadsheets, manual journals and a reconciliation that only one person understands, you'll get the same problems at greater speed. Birmingham planned an "out-of-the-box" implementation, then built customisations including a bank reconciliation system that failed to work properly.¹¹ That system later became the focus of years of remediation.

How to avoid it: Redesign your record-to-report and close processes before configuration starts. Agree a standard chart of accounts early, because it's much harder to change after go-live. Limit customisation to areas that give you a competitive advantage and adopt standard functionality everywhere else. Close management tools such as FloQast can then sit on top of a process that already works.

4. Data migration is treated as an IT task

Data migration is where many ERP projects go wrong, and it's fundamentally a finance problem. If opening balances don't reconcile, or historical transactions land in the wrong period, your first set of accounts on the new system are compromised. Birmingham's system was reported to have allocated £2 billion of transactions to the wrong year.¹²

How to avoid it: Start data cleansing at kick-off, months before you think you need to. Make finance the owner of data quality sign-off. Run several trial migrations and reconcile each one to the general ledger. Be deliberate about how much history you bring across, since migrating everything isn't always the safest option.

5. The ERP is planned in isolation from the rest of the finance stack

Your ERP feeds consolidation, planning, treasury and statutory reporting. If its entity structure and chart of accounts don't map cleanly to those systems, the problems show up in SIT or UAT, long after the project team has celebrated go-live.

How to avoid it: Build an integration map that lists every system the ERP connects to and which one holds the master record for each shared field. Test the full chain before go-live, including a mock month-end that runs through consolidation and into your reporting pack.

6. Timelines are set by the board calendar

Go-live dates often get fixed to a financial year-end or a board commitment, then defended at all costs. Testing gets squeezed, training is cut short and known issues are labelled as fixes for after launch. Birmingham's auditors described a culture where bad news was either unwelcome or uncomfortable to share.¹⁵

How to avoid it: Set go-live criteria and stick to them. A reconciled trial balance, a successful parallel run and a completed mock close are reasonable gates. Avoid going live in your busiest period. Above all, build governance where project leads can report problems early without career risk. A delay announced in month six costs far less than a failure discovered in month thirteen.

7. Support ends at go-live

Go-live is when the real test starts. The first few month-end closes will expose issues no test script caught, and the business case benefits only appear once the system is stable. Zimmer Biomet says it incurred $72 million of its own costs after go-live.¹⁶

How to avoid it: Plan for hypercare that covers at least the first two closes. Review results against the business case at 90 days and again at 12 months. Set aside budget for optimisation, because most organisations only find their best improvements once people are using the system every day. Our case studies show what this looks like in practice.

Five questions to ask before you approve the budget

• Can we state the business case in three finance metrics we'll measure after go-live?
• Have we mapped our processes, or are we relying on the vendor's view of them?
• Who on the delivery team has done this before, with a business like ours?
• Who in finance owns data quality, and is their day job covered?
• What has to be true before we go live, and who can stop it if it isn't?

Final thoughts

ERP projects fail in predictable ways, which means CFOs can do a lot to prevent it. The organisations that get value from their ERP treat it as a finance transformation with a technology component, and they keep finance in charge of the outcomes from selection through to the 12-month review.

VantagePoint selects, implements and optimises ERPs for finance teams across EMEA and APAC, including Oracle NetSuite and Sage Intacct. If you're planning a project or rescuing one, book a 30-minute call with our team.

Sources

1. Gartner, "Enterprise Resource Planning (ERP)." https://www.gartner.com/en/information-technology/glossary/enterprise-resource-planning-erp
2. The Register, "Birmingham City Council's Oracle ERP fiasco now £144M and still not working," 29 January 2026. https://www.theregister.com/2026/01/29/birmingham_oracle_latest/
3. The Register, "City council faces £216.5M loss over Oracle system debacle," 20 August 2024. https://www.theregister.com/2024/08/20/birmingham_oracle_cost/
4. The Register, "Birmingham City Council's Oracle ERP fiasco now £144M and still not working," 29 January 2026. https://www.theregister.com/2026/01/29/birmingham_oracle_latest/
5. Loeb & Loeb, "Loeb & Loeb Represents Zimmer Biomet in $172 Million Lawsuit Against Deloitte," September 2025. https://www.loeb.com/en/newsevents/news/2025/09/loeb-represents-zimmer-biomet-in-172-million-lawsuit-against-deloitte
6. MassDevice, Deloitte's response to the Zimmer Biomet ERP lawsuit. https://www.massdevice.com/zimmer-biomet-deloitte-response-erp-lawsuit-looking-glass/
7. Becker's Spine Review, "Zimmer Biomet sues Deloitte for $172M." https://www.beckersspine.com/?p=66707
8. The Register, "ERP carnage continues as orgs jump in unprepared," 13 November 2025. https://www.theregister.com/2025/11/13/erp_disaster_gartner/
9. MassDevice, "Zimmer Biomet sues Deloitte for $172 million." https://www.massdevice.com/zimmer-biomet-sues-deloitte-for-172-million/
10. Panorama Consulting Group, The 2026 ERP Report, as summarised by Rework. https://resources.rework.com/guides/choosing-software/erp-implementation-guide
11. The Register, "Birmingham City Council's Oracle ERP fiasco now £144M and still not working," 29 January 2026. https://www.theregister.com/2026/01/29/birmingham_oracle_latest/
12. The Register, "Mega city council's Oracle finance fix faces further delays," 3 February 2025. https://www.theregister.com/2025/02/03/birmingham_city_council_oracle/
13. Panorama Consulting Group, The 2026 ERP Report, as summarised by Rework. https://resources.rework.com/guides/choosing-software/erp-implementation-guide
14. The Register, "Mega city council's Oracle finance fix faces further delays," 3 February 2025. https://www.theregister.com/2025/02/03/birmingham_city_council_oracle/
15. Local Government Lawyer, "Auditors highlight poor oversight and reporting at city council over troubled IT programme." https://www.localgovernmentlawyer.co.uk/projects-and-regeneration/403-projects-news/60078-auditors-highlight-poor-oversight-and-reporting-at-city-council-over-troubled-it-programme
16. MassDevice, "Zimmer Biomet sues Deloitte for $172 million." https://www.massdevice.com/zimmer-biomet-sues-deloitte-for-172-million/