The Birmingham City Council’s ambitious plan to implement an Oracle Fusion enterprise resource planning (ERP) system has turned into one of the most striking cautionary tales of public sector mismanagement, financial strain, and systemic failures. What began as a visionary initiative aimed at modernizing the council’s financial operations has since devolved into a chronicle of errors, revealing crucial lessons on governance, risk management, and cultural alignment. This article explores the sequence of events leading to this debacle, guided by findings and recommendations from a forensic investigation conducted by Grant Thornton.
The Forensic Report and Initial Findings
In February 2025, Grant Thornton released a detailed 66-page forensic report that provided an exhaustive analysis of the failed Oracle Fusion ERP implementation at Birmingham City Council. The findings were sobering, determining that the council would be without a functional finance system until at least 2026, with the costs skyrocketing to £90 million beyond the original budget. This staggering amount reflects not only the initial investment in the Oracle system but also the ongoing expenses required to address and mitigate its numerous shortcomings.
Central to the report was the observation that the council’s steering committee had grossly underestimated the risks associated with adopting the Oracle solution. This underestimation became a significant factor in the project’s ultimate downfall, rendering the council incapable of effectively managing its finances over several fiscal years, from 2022/2023 through 2024/2025. With each passing fiscal cycle, the lack of a reliable financial system further exacerbated the council’s operational inefficiencies and financial vulnerabilities.
Governance and Management Shortcomings
Fundamental weaknesses in governance and program management were at the heart of the ERP initiative’s troubles. High turnover rates among senior and operational staff further destabilized the project, eroding the continuity and stability required for its success. The council’s historical reliance on an SAP ERP system implemented in 1999, which had been customized over the years to align with the organization’s evolving processes, also played a role. However, SAP’s announcement to cease support for its older ERP systems by 2027 compelled the council to seek alternatives, leading to the selection of Oracle Fusion in 2019.
The decision to transition was riddled with governance and management challenges from the start. High turnover rates at both senior and operational levels created gaps in leadership and consistency, which are critical for steering such a complex project. These staffing issues aggravated an already precarious situation, fostering an environment where the lack of stable leadership further compromised the project’s progression. Moreover, the council’s governance framework and decision-making processes were inadequate in addressing the emerging issues, leading to poorly informed decisions and ultimately, project failure.
Challenges and Supplier Performance
From the outset, the transition to Oracle Fusion faced numerous challenges, many of which were intricately tied to supplier performance. Key program support contracts were awarded to entities like Insight UK Ltd, Socitm Advisory, and Egress, each responsible for systems integration, program and change management, and data migration, respectively. Ameo Professional Services was brought in for program management and assurance starting in January 2021. Despite these efforts, the performance of these suppliers came under scrutiny and is the subject of a separate and legally privileged report, raising questions about their effectiveness in managing this complex implementation.
Initial financial projections for the Oracle system suggested potential savings compared to the existing SAP system. Managed by Capita, the SAP system’s annual cost was about £5.1 million, totaling £46 million over a nine-year period. The Oracle system was projected to achieve cumulative savings of around £10.9 million over the same timeframe. Unfortunately, the reality of transitioning IT services in-house after terminating Capita’s contract in August 2019 proved to be a daunting challenge, particularly in the absence of sufficient Oracle expertise. Building in-house Oracle capability was described as “very challenging,” highlighting the council’s struggle to bridge the expertise gap and effectively manage the transition.
Financial Implications and Manual Interventions
As the project progressed towards its go-live date in 2022, the Oracle system encountered significant problems that required ongoing manual interventions to resolve accounting issues. These persistent challenges necessitated the allocation of additional resources, further inflating the project’s costs. By 2024, the council had set aside £5.3 million specifically to support and remediate Oracle system issues manually. This unanticipated expenditure not only added to the financial burden but also underscored the underlying issues in the ERP implementation.
The report suggests that the failure of the Oracle Fusion project was a contributory, though not fundamental, factor to the council’s broader financial woes. In 2023, Birmingham City Council effectively declared bankruptcy, revealing a deeper financial instability exacerbated by the ERP system’s failure. The combination of escalating costs, manual interventions, and ongoing technical challenges further strained the council’s already tenuous financial position, leading to a cumulative impact that was both severe and far-reaching.
Misalignment and Cultural Issues
One of the most critical findings of the Grant Thornton report was the stark misalignment between the council’s approach and the designed principles of the Oracle system. Rather than adhering to the Oracle-standard functionality, the council attempted to bend the system to fit its existing processes. This misalignment significantly hampered the implementation, as the ERP system was not designed to accommodate such extensive customization.
This decision to force the Oracle ERP system to conform to pre-existing processes highlighted a broader cultural issue within the organization. There was a marked lack of preparation for the necessary business and cultural changes, which are critical for the successful adoption of any new IT system. End users were neither adequately prepared nor sufficiently trained to engage effectively with the Oracle software, further impeding its utilization and fostering resistance to change. This lack of cultural readiness was a significant barrier to the project’s success and revealed deeper issues in how the organization approached change management.
The Role of Organizational Culture
The Birmingham City Council’s lofty ambition to install an Oracle Fusion enterprise resource planning (ERP) system has become a prime example of public sector mismanagement, financial difficulties, and organizational breakdowns. What initially was a forward-thinking move to update the council’s financial operations has descended into a series of blunders, unveiling significant lessons in governance, risk management, and cultural coherence. This narrative traces the sequence of missteps that led to this turmoil, informed by insights and suggestions drawn from a forensic analysis carried out by Grant Thornton. The findings shed light on the myriad challenges and pitfalls encountered during the implementation, emphasizing the critical importance of thorough planning, effective oversight, and proper alignment of organizational culture. The Birmingham City Council’s experience serves as an essential case study for other public institutions embarking on similar modernization initiatives.