Client Overview
A Germany-based automotive parts manufacturer headquartered in Munich, with approximately 10,000 employees and annual revenue of €5 billion. The company produces automotive components with factories and offices across Europe, North America, and Asia.
Oracle E-Business Suite for ERP (finance, procurement, manufacturing), Oracle Database instances supporting production planning and logistics, and Oracle Fusion Middleware for enterprise application integration. All covered under a 5-year Oracle ULA scoped for global operations.
During the ULA term, the company acquired a competitor with operations in Japan and divested one business division. Both events introduced entity-scope complications that risked leaving deployments unlicensed if not properly managed before certification.
Certify and exit the Oracle ULA without falling foul of Oracle's compliance rules. Ensure full coverage for all global entities (including the acquired Japanese subsidiary), proper handling of the divested division, and avoidance of Oracle's €15 million renewal proposal.
The Challenges
This engagement combined the standard complexity of an Oracle ULA certification with the added dimension of corporate M&A activity. A scenario that dramatically increases compliance risk.
| Challenge | Detail | Risk |
|---|
| Acquisition scope gap | The Japanese subsidiary acquired mid-term had deployed Oracle Database instances not explicitly listed in the original ULA's entity scope | Critical |
| Divestiture complications | A spun-off division was still using Oracle under a transitional services agreement; its deployments needed to be excluded from the ULA certification or handled separately | High |
| Geographical expansion | New deployments in Asia potentially fell outside the ULA's geographic or entity bounds, depending on contract language | High |
| Oracle renewal pressure | Oracle's German account team was actively pushing a ULA renewal at €15 million, framing certification as risky given the cross-border M&A changes | High |
| Board-level budget governance | German headquarters required board approval for large expenditures; the CIO was under pressure to reduce IT costs, not increase them | Medium |
M&A and Oracle ULAs: a high-risk combination. Oracle ULAs are often scoped to specific legal entities at the contract start date. Acquisitions, mergers, and divestitures that occur during the ULA term can silently create compliance gaps. Deployments fall outside the agreed scope but continue running in production. Oracle's LMS team is specifically trained to identify these gaps and use them as leverage for renewal or additional purchases. For detailed guidance, see our article on managing Oracle licences during mergers, acquisitions, and divestitures.
How Redress Compliance Helped
Redress Compliance was engaged to navigate both the technical and contractual complexities of this case. The approach combined deep contract analysis, comprehensive deployment auditing, strategic remediation, and targeted negotiation with Oracle.
1
Phase 1: Contract scope review. Redress's licensing experts conducted a thorough review of the original ULA contract. They identified exactly which corporate entities and regions were covered. The review revealed that the ULA covered "all worldwide affiliates as of the contract start date" but did not automatically include acquired companies. The Japanese subsidiary acquired mid-term was therefore outside the original scope. Redress flagged this as a priority issue to resolve before certification.
2
Phase 2: Global deployment audit and gap analysis. Redress conducted a comprehensive audit of all Oracle deployments across the company, including the new Japanese subsidiary's IT systems. Every Oracle Database instance and E-Business Suite module in use was catalogued. The audit revealed the extent of usage in Japan that was technically out of scope, and quantified the usage in the spun-off division (which was still running Oracle under a transitional services agreement). Redress performed a gap analysis: what licensing would be required to cover the Japanese deployments, and what to do about the divested division's usage.
3
Phase 3: Scope remediation plan. To address the out-of-scope usage, Redress devised a two-part remediation plan. For the Japanese subsidiary: rather than concealing the deployments, Redress recommended negotiating with Oracle to extend the ULA scope to cover that entity for certification, achieved through a modest one-time licence purchase specifically for the Japanese subsidiary's Oracle usage. For the divested division: ensure that Oracle usage in that division was frozen and documented up to the date of divestiture, then excluded from the certification. Redress coordinated with the company's legal team to ensure compliance with divestiture agreements and Oracle's policies on licence transfers.
4
Phase 4: Negotiation and leverage. Redress turned Oracle's renewal pressure into a leverage point. They approached Oracle with a clear position: the client was prepared to certify out, but acknowledged the Japan scope issue. Redress proposed a solution beneficial to both sides: a one-time licence purchase of approximately €2 million for the Japanese subsidiary's Oracle usage, in exchange for Oracle agreeing to include those deployments in the ULA certification. Oracle, recognising that a €15 million renewal was unlikely and preferring a sale over an audit standoff, agreed. Redress also secured a competitive discount on the purchase through established negotiation tactics.
5
Phase 5: Optimised certification process. With scope issues resolved, Redress guided the certification execution. They prepared the certification document listing final counts of Oracle Database processors and E-Business Suite modules deployed globally, including those in Japan, now legally added. The spun-off division's usage was excluded with Oracle's written acknowledgement. Redress scheduled the certification submission strategically at quarter-end, when Oracle is focused on closing sales, making Oracle more amenable to quick closure of the concurrent licence purchase.
Entity scope clause: a frequently overlooked risk. Oracle's standard ULA contracts often contain an entity scope clause that freezes the list of authorised entities at the contract start date. Any company acquired after that date, even a wholly-owned subsidiary, may not be covered. This is one of the most frequently overlooked compliance risks in enterprise licensing. The fix is rarely complex, but it must be identified and addressed before certification. If Oracle discovers it first, they will use it to force a renewal or demand back-dated licensing at list price.
Outcomes
€10M total savings over 3 years. Avoided renewal, audit penalties, and inflated support costs. The €2M one-time licence purchase represented an 87% reduction compared to Oracle's €15M renewal proposal.
Zero compliance issues at certification. All entities and regions fully covered. The Japanese subsidiary's Oracle deployments were properly included via the negotiated licence purchase. The divested division's usage was excluded with Oracle's written acknowledgement.
Clean ULA exit with perpetual licences secured. No ongoing Oracle lock-in. Oracle must now win future business on merit and price, not through ULA dependency. The client leveraged the exit to diversify, adopting open-source databases for new projects.
Zero operational disruption. Production lines, ERP systems, and planning systems were completely unaffected throughout the engagement. No emergency purchases, no audit-driven system changes.
| Metric | Before Engagement | After Engagement |
|---|
| Oracle's renewal proposal | €15 million ULA renewal | €2M one-time purchase: 87% less than renewal |
| Japan subsidiary compliance | Out of ULA scope; deployments technically unlicensed | Covered via negotiated licence purchase; included in certification |
| Divested division | Uncertain handling; risk of incorrect inclusion/exclusion | Properly excluded with Oracle's written acknowledgement |
| Audit risk | High: M&A scope gaps gave Oracle clear audit leverage | Eliminated: all potential non-compliance resolved proactively |
| Ongoing vendor lock-in | Facing 3+ more years tied to Oracle ULA | Fully independent; Oracle must win future business on merit |
| Operational disruption | Potential for audit-driven system changes or emergency purchases | Zero disruption: production lines, ERP, and planning systems unaffected |
"Our company's evolution meant our Oracle agreement fell out of step with reality. A dangerous situation we would not have resolved on our own. Redress Compliance came in with a clear plan and deep expertise. They untangled the contract, turning a potential compliance nightmare into a straightforward solution. We especially appreciate how they negotiated on our behalf. It saved us millions and a lot of headaches. Redress proved to be the independent advisor we needed, always in our corner. We now have the licences we need, no more and no less, and can move forward confidently."
Head of IT Procurement, German Automotive Manufacturer
Key Takeaways for CIOs and IT Leaders
This engagement highlights several critical lessons for organisations managing Oracle ULAs during periods of corporate change.
M&A events silently break ULA scope. Oracle ULAs are typically scoped to entities that exist at the contract start date. Acquisitions during the ULA term do not automatically inherit unlimited rights. Every corporate transaction (acquisition, merger, spin-off, or joint venture) should trigger an immediate review of Oracle licensing exposure. See our guide to
Oracle licensing in M&A scenarios.
Read the entity scope clause before assuming coverage. The difference between "all worldwide affiliates as of the effective date" and "all worldwide affiliates" (open-ended) can represent millions in compliance exposure. Review this clause with licensing counsel before any corporate change.
Convert compliance gaps into negotiation leverage, not crisis. Identifying a scope issue proactively gives you control. Redress turned this client's Japan gap into a small, negotiated purchase (€2M) rather than letting Oracle discover it during certification and demand a €15M renewal. The approach matters as much as the finding.
Time your certification strategically. Submitting the certification at quarter-end, when Oracle's sales team is under pressure to close deals, made the concurrent licence purchase more attractive to Oracle and facilitated a faster resolution. Timing is a material negotiation lever. Learn more about
Oracle ULA renewal timing tactics.
Handle divestitures explicitly in the certification. Spun-off entities using Oracle under transitional services agreements must be carefully documented and excluded from the ULA certification. Obtain Oracle's written acknowledgement of the exclusion to prevent future disputes.
Post-exit vendor independence is the strategic prize. After certification, the client holds perpetual Oracle licences with no ongoing contractual obligation. Oracle must now win future business on merit and price, not through ULA lock-in. This client leveraged the exit to diversify, adopting open-source databases for new projects. For exit planning, see our
Oracle ULA Exit Strategy guide.
Oracle Advisory Services and Resources
FF
Fredrik Filipsson
Co-Founder, Redress Compliance
20+ years of enterprise software licensing expertise, including nine years working directly at Oracle and over a decade in independent Oracle licence consulting. He has advised hundreds of Fortune 500 organisations on complex Oracle licensing challenges, with particular depth in ULA certification, audit defence, M&A-related licence risks, and contract negotiation.
← Back to Oracle Knowledge Hub