UCLA settles Oracle ERP dispute with $3.1M credits and $1.31M bill reduction

The University of California, Los Angeles, has settled a pre-litigation dispute with Oracle regarding its cloud enterprise resource planning implementation. The agreement, approved by the Board of Regents in May following a recommendation from the Compliance and Audit Committee, resolves conflicts over the Ascend project.

Under the terms revealed in California Public Records Act documents, Oracle waived $1.31 million in outstanding fees. The vendor also granted $3.1 million in credits against future charges, which expire at the end of May 2028. UCLA agreed to pay $350,000 of the $1.66 million in outstanding invoices.

Context and Background

UCLA halted its Oracle subscription payments in September 2024, according to records obtained by Eric Guyer, founder of consultancy Advizant. The university alleged that the ERP Cloud Services lacked sufficient functionality to meet its specific requirements. Specifically, UCLA cited shortcomings in grants management functionality as a primary reason for the payment stoppage.

The institutions signed their initial agreement for the Ascend project in November 2017. The project had a revised go-live date of January 2025 but was paused in mid-2024. UCLA claimed the services did not perform as warranted in the original Oracle Agreement. The university stated it incurred costs and delays due to the software's inability to meet expectations.

Who is Affected

The settlement applies to UCLA and Oracle, with both parties acknowledging the university is subject to public records laws. The agreement includes a confidentiality clause preventing public statements about the settlement terms. However, the existence of the dispute and its resolution are now matters of public record due to the state's transparency requirements.

The dispute highlights challenges in large-scale ERP implementations, where functional gaps can lead to significant financial disagreements. UCLA alleged that Oracle breached the agreement by failing to deliver warranted performance. The resolution allows the university to continue its relationship with Oracle while adjusting financial obligations.

What should you do?

Organizations evaluating large ERP contracts should scrutinize functional warranty clauses and performance metrics. IT leaders should ensure that critical business processes, such as grants management, are explicitly defined in service level agreements. Regular audits of vendor deliverables against contract specifications can help identify discrepancies early. Stakeholders should maintain detailed records of delays and functional gaps to support potential dispute resolutions.

What to do and how to stay safe: Oracle

• Review ERP contract terms for specific functional warranties and performance metrics related to critical business processes.
• Monitor vendor deliverables against agreed-upon specifications and document any deviations or delays in real time.
• Establish clear escalation procedures for addressing functional gaps before they escalate into payment disputes or litigation.
• Consult legal and compliance teams when considering withholding payments due to alleged vendor non-performance.

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

How much did UCLA pay Oracle in the settlement?

UCLA agreed to pay $350,000 of the $1.66 million in outstanding invoices under the settlement terms.

Why did UCLA stop paying its Oracle subscription?

UCLA stopped payments in September 2024 due to alleged shortcomings in grants management functionality and performance failures.

When do the Oracle credits expire?

The $3.1 million in credits granted to UCLA expire at the end of May 2028.