Five million pounds. That's what manual workarounds have cost where an Oracle ERP system was supposed to do the job instead, The Register reports.

It's the kind of number that stops a CIO mid-coffee. Not because the sum is enormous by enterprise-ERP standards — it isn't — but because of what it buys: nothing. No new capability, no modernisation dividend, no licensing relief. Just people doing, by hand, what the software was procured to automate.

What does £5M of workarounds actually look like?

Think spreadsheets stitched between modules. Clerks re-keying data the system should have moved on its own. Reconciliations run outside the platform because the platform, as deployed, couldn't close the loop.

Every organisation that has run a troubled ERP programme recognises the pattern. The workaround starts as temporary. Then temporary becomes quarterly. Then quarterly becomes the operating model, with a price tag quietly compounding in the background — until someone totals it up and arrives at a figure like £5 million.

Why this matters beyond the headline

The core promise of an ERP migration is consolidation: retire fragmented legacy processes, standardise on one platform, cut running costs. When an organisation instead funds a parallel manual layer on top of the Oracle deployment, it's paying twice — once for the licence and implementation, once for the labour that patches the gaps.

For IT leadership, the £5M figure is a benchmark worth filing away. It puts a hard currency value on the gap between "system live" and "system working." Go-live dates make the press releases; the workaround spend tells you whether the programme actually landed.

What does this change for ERP buyers?

Three practical takeaways for anyone mid-programme or weighing one:

• Price the workaround layer. If manual processes are propping up your Oracle deployment, quantify them per year. Unmeasured, they're invisible; measured, they're a business case for remediation — or a warning sign before contract renewal.
• Treat "temporary" fixes as budget line items. A workaround older than two quarters isn't temporary. It's recurring cost.
• Interrogate the gap between design and deployment. ERP failures rarely live in the software itself. They live in configuration, data migration and process fit — the layers vendors and integrators negotiate over, and the ones that generate £5M in spreadsheet labour when they go wrong.

The uncomfortable arithmetic for the organisation in question is simple. Every month the manual layer persists, the bill grows. Five million pounds bought a lot of keystrokes that the Oracle system was meant to eliminate.

That's the quiet scandal of enterprise ERP: not the spectacular outage, but the slow, budgeted, approved accumulation of human effort doing a machine's job.