UCLA and Oracle have settled their dispute over a delayed financial-systems overhaul, with Oracle waiving $1.31 million in fees and granting $3.1 million in future credits. The deal closes a costly chapter in a cloud ERP project that UCLA said failed to meet its needs, without either side admitting liability.
Oracle Watch analysis
What happened
UCLA agreed to pay $350,000 of $1.66 million in outstanding invoices, according to settlement documents reported by The Register. The $3.1 million in credits expire at the end of May 2028. The agreement also bars both parties from making further claims for damages related to the dispute.
The Ascend project began in 2018 and aimed to modernise UCLA’s financial, budgetary and research administration systems using Oracle Cloud. Its main financials rollout was paused in August 2024, after the planned go-live date had shifted to January 2025. UCLA alleged the software lacked functionality it needed; Oracle has not admitted liability. The Register says it asked Oracle for comment.
Why it matters
This was not a small software swap. UCLA’s project had an original budget of $120 million, later revised to $98.9 million in a 2025 university report. The Register, citing a campus newspaper, says at least $213 million had been spent and a 2024 presentation projected total costs of roughly $286 million. Those figures describe different budget and spending estimates, not the settlement amount.
The settlement offers a concrete lesson for organisations buying cloud ERP: credits and waived invoices can close a dispute, but they do not recover years spent on a project that has stalled. UCLA’s procurement module went live in January 2024, while the core financials system remained paused.
Our read
The settlement draws a line under the invoices, not the implementation. UCLA still has to decide how to modernise its financial systems, and the public terms do not explain what happens next with Ascend. For buyers, the uncomfortable question is not just whether a supplier’s software works as specified, but how quickly a troubled rollout can be recognised before delay becomes its own expensive system.
What to watch
- Whether UCLA sets out a new plan, supplier or timeline for financial-systems modernisation.
- Whether the $3.1 million in Oracle credits are used before they expire in May 2028.
- What further public records reveal about project spending, requirements and delivery.
- Whether either party makes a statement beyond the settlement terms.
Discussion spark: When a major software rollout stalls, should the buyer prioritise recovering costs from the supplier, or cutting its losses and switching systems?
Sources and evidence
- UCLA settles Oracle ERP dispute with $3.1M in credits and $1.31M wiped off the bill – The Register (12 October 2026, 12:58 UTC)
not affiliated with or endorsed by Oracle