HM Treasury has contributed to funding the shared Matrix ERP programme since 2021 — to the tune of £1.15 billion by available accounts — without having decided whether it will actually participate as a user (The Register, June 2026). The formal decision has been pushed back to December 2026, pending feasibility documents expected by the end of summer.
The Matrix Programme: Nine Departments, One Workday
Matrix sits within the UK government’s broader strategy to consolidate back-office services across departments. The Matrix cluster brings together nine government departments — including DSIT (Department for Science, Innovation and Technology, as lead), the Cabinet Office, and the ministries for Energy, Culture, Trade, Education, Health, the Attorney General’s Office, and HM Treasury — under a single shared ERP contract.
In 2024, the government awarded Workday the software contract (finance and HR as SaaS) and Cognizant the systems integration work, for a combined contract value of £144.3 million (UKAuthority). Projected benefits over 15 years reach £4.37 billion: £1.4 billion in direct cashable gains and £2.98 billion in non-monetary benefits (productivity improvements, reduced operational risk).
Why Treasury Is Holding Back
Treasury’s position is paradoxical: it co-funds the programme, sits on the steering committee, and yet refuses to commit to its own migration. The National Audit Office documents make the reason explicit — Treasury currently runs Oracle Fusion in a heavily customised configuration, tuned to the specific financial processes of a finance ministry. Joining Matrix would mean giving up some of that functionality to adopt the standardised Workday configuration the programme requires.
The language used in official documents is telling: “loss of functionality” and “unnecessary cost.” This isn’t a rejection in principle — it’s a classic trade-off between standardisation and operational specificity, the same debate that stalls ERP projects in the private sector at a fraction of this scale.
The financial stakes are real. According to the NAO’s sensitivity analysis, if both Treasury and the Department for Education stay out of the programme, the net present value of projected benefits drops from £185 million to £109 million (The Register, March 2026). Treasury disputes these figures, which adds another layer of complexity to the decision.
What This Tells Us About Complex ERP Migrations
For a CIO or CFO running or considering an ERP programme, this case illustrates three recurring dynamics:
Customisation as hidden debt. A heavily customised Oracle Fusion deployment represents years of bespoke development, workarounds, and processes that have become “the way we’ve always done it.” That debt is invisible until someone asks the organisation to migrate to a more standardised system. The deeper the customisation, the more painful the trade-off.
Co-funding without operational commitment. Treasury signed the funding agreement but not the order for its own migration. This kind of disconnect is more feasible in a complex public-sector environment; it is less common in private enterprise but not unheard of in group-level shared-services projects or inter-subsidiary consolidations.
Delay as a de facto decision. December 2026 is two years after the Workday-Cognizant contract was awarded. Every month of delay, the rest of the programme advances on a standardised Workday configuration. If Treasury joins late, it will either need to adapt its processes to a configuration already locked in place, or negotiate exceptions — both options carry a cost premium.
What to Watch
Two milestones to track:
End of summer 2026: delivery of the feasibility documents Treasury is waiting for. This body of analysis will form the basis of the December decision. Any further delay in that delivery is an early signal that the December decision will slip again.
December 2026: formal decision from Treasury. An outright “no” would trigger a scope renegotiation and a direct hit to the programme’s business case. A late “yes” opens questions about integration terms into a programme already well underway.
The Department for Education is in a similar position. If both major contributors remain outside the scope, the programme’s financial model is under pressure — even if the Workday-Cognizant contract continues independently.
Further Reading
This case illustrates precisely what a pre-migration audit should surface before any ERP decision. For deeper methodology, see our ERP audit guide — how to evaluate your current system before migration, our analysis of the true cost of an ERP project, and our practical guide to ERP change management.
