News

UCLA and Oracle Reach Settlement in ERP Dispute

UCLA and Oracle reached a settlement in their ERP dispute, including $3.1 million in credits and a reduction of $1.31 million from the original bill, following allegations of insufficient functionality in Oracle's cloud services.

AI-generated editorial illustration of the article topic; not a photograph, product screenshot or measured result.

Background of the Oracle ERP Dispute

In November 2017, UCLA and Oracle entered into an agreement for the Ascend project, aimed at modernizing the university's financial systems. However, the transition proved problematic, with reports indicating that UCLA was still relying on legacy financial systems software from the 1980s, even as its budget had grown significantly. In May, the University of California's Compliance and Audit Committee recommended a settlement [PDF] for UCLA's pre-litigation dispute with Oracle, which was later approved by the Board of Regents. The settlement includes $3.1 million in credits and a reduction of $1.31 million from the original bill. The dispute highlights the challenges institutions face when implementing large-scale ERP systems, particularly when legacy infrastructure and evolving needs create complications.

UCLA's Allegations and Termination of Payments

According to documents released in response to a California Public Records Act request, UCLA stopped paying its Oracle subscription in September 2024 over what it described as shortcomings in grants management functionality. The settlement records UCLA's allegation that "the ERP Cloud Services did not perform as warranted in the Oracle Agreement." "The ERP Cloud Services lacked sufficient functionality to meet the University's requirements and could not be used by the University as expected," said the document, which was seen by The Register. It continued that "the University incurred costs and delays due to the ERP Cloud Services inability to meet the University's requirements." It added: "As a result, Oracle breached the Oracle Agreement." Under the settlement, UCLA agreed to pay Oracle $350,000 of the $1.66 million in outstanding invoices.

Terms of the Settlement Agreement

Under the terms of the Settlement Agreement, UCLA and Oracle have agreed to make no further claims for damages related to the contract dispute, and neither party has admitted liability. According to the settlement document, the University informed Oracle via email on June 20, 2025, that it wished to terminate the Ascend project and the ERP Cloud Services. Oracle then waived the remaining balance – $1.31 million – and credited $3.1 million against future Oracle fees. The University has continued to evaluate its path forward for financial systems modernization, as noted in a May statement from a spokesperson. The Daily Bruin reported that at least $213 million had been spent, citing a May 2024 town hall presentation projecting total costs of roughly $286 million.

Project Status and Financial Implications

In its 2025 report [PDF], the University of California Board of Regents' Finance and Capital Strategies Committee highlighted ongoing challenges in UCLA's Oracle ERP implementation. The project, initially budgeted at $120 million, was revised to $98.9 million, with $13.5 million remaining as of December 31, 2024. The report noted Oracle's lack of responsiveness, particularly regarding licensing costs and support, as a significant risk. The procurement module, BruinBuy Plus, went live in January 2024, but the main Oracle Financials go-live has been paused since August 2, 2024, and is undergoing program assessment. Mitigation plans include reassessing the tool and provider to determine whether to continue with Oracle or explore alternatives.

Industry Perspectives and Broader Context

In the broader context of enterprise software disputes, the UCLA-Oracle settlement highlights the complex dynamics between universities and major vendors. According to Guyer, Oracle likely offered discounted software to secure the "coveted" UCLA logo, suggesting a strategic move to bolster its reputation in higher education. A social media post indicated that the credits may imply UCLA’s intention to continue the project with Oracle as the primary vendor, despite the challenges faced. This case is described as rare, with Oracle agreeing to absorb some costs in exchange for UCLA’s silence in a highly competitive market. Such settlements often reflect the balance of power between institutions and vendors, where financial concessions can serve as both a resolution and a public relations strategy. The outcome underscores the importance of careful planning in large-scale ERP implementations and the potential for vendor relationships to influence institutional decisions.