UCLA and Oracle resolve Ascend dispute with $4.41m in concessions
UCLA and Oracle have settled a dispute over Ascend, a financial systems overhaul that was delayed and paused after the university said Oracle’s cloud software did not meet its requirements. The settlement gives UCLA $3.1 million in credits towards future Oracle charges and removes $1.31 million from its unpaid bill.
UCLA will pay $350,000 of $1.66 million in outstanding invoices, while the credits expire at the end of May 2028. The project was originally budgeted at $120 million, later revised to $98.9 million, and was expected to go live in January 2025. UCLA stopped paying its Oracle subscription in September 2024, citing shortcomings in grants management.
- Oracle waived $1.31 million of UCLA’s unpaid fees.
- UCLA also received $3.1 million in credits.
- The settlement follows delays and functionality concerns.
New here? Start with this
Ascend is a major financial systems upgrade that UCLA undertook to modernise how it manages money and grants. The university had budgeted over $100 million for the project, which was intended to replace outdated systems and improve operational efficiency.
Oracle, the technology company supplying the cloud software, and UCLA disagreed over whether the system met the university's requirements. UCLA paused the project and stopped paying Oracle's bills in late 2024, arguing that the software did not adequately handle grants management.
This dispute reflects broader challenges that universities face when implementing large-scale technology projects. When systems fail to meet expectations, institutions must decide whether to invest further in fixing problems or pursue alternatives, whilst vendors and clients may clash over where responsibility lies.
Both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
Oracle would argue that massive enterprise software implementations inherently encounter complexity reflecting organisational readiness, change management, and requirement definition—all shared client responsibilities. The company likely maintains its cloud platform meets requirements when properly configured, and that UCLA's specific issues, including grants management functionality, involve customisation and institutional adaptation that any organisation faces. The settlement represents a reasonable compromise acknowledging mutual implementation challenges rather than an admission the software fundamentally failed.
The case against
UCLA's decision to suspend payment in September 2024 and pause the project indicates genuine performance failures by Oracle. A significant delay beyond the January 2025 target, a £21.1 million budget reduction, and specific functional gaps in grants management demonstrate Oracle did not deliver what was contracted for. The substantial concessions Oracle granted—£3.1 million in credits and £1.31 million in bill reduction—implicitly acknowledge this shortfall; when a vendor fails to provide contracted capabilities, the vendor bears principal responsibility.
Read the full article at the source →
Originally published by The Register as “UCLA settles Oracle ERP dispute with $3.1M in credits and $1.31M wiped off the bill”.