Sunday 4 October 2026
Afternoon EditionRSS
ZOTPAPER

News without the noise

ZOTPAPER
Business

Birmingham City Council Faces Three More Years Without Clean Audit as Oracle Hangover Persists

Despite successful reimplementation of Fusion system, historic data problems prevent auditor from vouching for accounts until at least 2028

By LineZotpaper
Published
Read Time2 min
Europe's largest local authority, Birmingham City Council, will go at least another three financial years without auditors being able to certify its accounts, despite finally reimplementing its Oracle Fusion system, according to a report from auditor Grant Thornton. The council will receive 'disclaimer opinions' for the 2025/26, 2026/27, and 2027/28 financial years due to ongoing problems with historic data, and is not expected to regain a clean audit until 2028/29 — roughly a decade after the Oracle programme began.

Birmingham City Council's troubled Oracle Fusion implementation, which has already cost more than seven times its original estimate and contributed to the council's effective bankruptcy, is not yet out of the woods. A report from auditor Grant Thornton has warned that the council will receive 'disclaimer opinions' for the next three financial years, meaning the auditor cannot obtain enough evidence to express an opinion on the financial statements.

The report noted that the council's transition to a rebuilt Oracle Fusion-based HR and finance system in August has been 'largely successful', with the reimplementation appearing to have been 'better managed than the original 2022 implementation'. Unlike the original system — known as 1B, which went live in April 2022 and left the council unable to reconcile bank accounts or understand its cash position — the new system has no outstanding business-critical or priority level 1 or 2 tickets. For context, in September 2025 there were 311 open tickets and two major incidents related to the old system.

However, the damage from the original implementation continues to haunt the council. The first go-live introduced several customisations, including a bank-reconciliation design that failed to function properly. The council has spent more than £5 million on manual workarounds. The overall project, including the reimplementation, is now expected to cost around £144.4 million against an initial estimate of £20 million. Including forgone efficiency savings, researchers estimate the cost could reach £216 million.

The council initially planned to go live in December 2020 for finance and procurement and February 2021 for HR and payroll, before shifting both to April 2022. It had intended to implement Oracle 'out of the box' but introduced customisations that ultimately failed. Taxpayers may take some comfort that the reimplementation appears better managed, but a clean audit opinion remains years away.

§

Analysis

Why This Matters

  • Residents and businesses relying on Birmingham City Council for services face prolonged uncertainty over the authority's financial health, as unverified accounts erode trust and complicate borrowing and investment decisions.
  • The £144 million-plus Oracle fiasco — originally budgeted at £20 million — serves as a cautionary tale for public-sector IT megaprojects, especially those attempting to replace legacy systems without adequate governance.
  • A clean audit is essential for the council to demonstrate it has moved beyond its effective bankruptcy in 2023; the decade-long timeline to regain assurance underscores the scale of the institutional and technical failure.

Background

Birmingham City Council, the largest local authority in Europe, effectively declared bankruptcy in 2023, partly due to the costs and chaos caused by its failed Oracle Fusion implementation. The council had sought to replace its legacy SAP R/3 system with a modern cloud-based HR and finance platform. The original go-live in April 2022 was disastrous, leaving the council unable to reconcile its bank accounts or reliably understand its cash position. A subsequent reimplementation began, and the new system went live in August 2026, but the historic data problems persist. The case has become a symbol of the risks of complex public-sector IT projects in the UK.

Key Perspectives

Birmingham City Council: Has acknowledged the original implementation's failures and worked to rectify them. The successful reimplementation suggests a more disciplined approach, but the council remains burdened by the legacy of inaccurate data from the original system, preventing a quick audit resolution. Grant Thornton (Auditor): Must issue disclaimer opinions because it cannot obtain sufficient evidence on historic transactions. This is a standard professional response but leaves stakeholders without independent assurance. The auditor's report acknowledges the reimplementation's improvement but stresses that data quality from the original system remains an obstacle. Council Taxpayers: Have borne the cost of both the failed implementation and the reimplementation — totalling up to £216 million when lost efficiency savings are included — and will continue to lack independent verification of how their money has been managed until at least 2028.

What to Watch

  • Whether the council can accelerate the timeline for regaining a clean audit opinion by investing in data remediation and hiring additional accounting staff.
  • Any further cost overruns or delays in the Oracle programme, particularly related to ongoing manual workarounds that have already cost £5 million.
  • The impact on the council's credit rating and ability to raise capital for essential services like social care and waste collection.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.

How we workReport an errorSubscribe