Oracle Licence Compliance in M&A: Due Diligence Checklist

Why Oracle Licensing Compliance Matters in M&A

Mergers and acquisitions trigger intensive scrutiny of software licensing. Unlike many vendors, Oracle treats acquisition events as major audit triggers. Oracle's Global License Application Services team actively monitors M&A activity and news, using it as a signal to initiate comprehensive license compliance reviews. For mid-sized companies, the cost of post-acquisition audits ranges from $1-5M when under-licensing is discovered.

The core issue is straightforward: Oracle licenses are non-transferable. When you acquire a company, their Oracle licensing rights do not automatically transfer to the acquiring entity. Many executives believe they own the licenses outright, but Oracle's licensing agreements vest rights in specific legal entities, not in the technology itself. This distinction creates substantial risk during transitions.

Oracle licensing M&A due diligence is not optional. It is a contractual, financial, and operational necessity that must be addressed before closing. Understanding the hidden costs, compliance exposure, and remediation options available during negotiations gives you leverage and protects against seven-figure surprises post-deal.

The Customer Definition Problem: Legal Entity Misalignment

Oracle's licensing agreements contain a critical clause: the "customer definition." This clause specifies which legal entity owns the right to use the software. It is not the software itself that matters for compliance; it is which organization is contractually defined as the customer.

When a merger closes, the acquired company's legal entity may cease to exist or be folded into a parent holding company. If the original Oracle customer definition tied licenses to the acquired entity alone, the acquiring company has no contractual right to use those licenses post-merger. This is a compliance violation from day one.

Consider a practical example: Company A acquires Company B for $500M. Company B has 400 Oracle Database Enterprise Edition processors licensed under contracts naming only "Company B, Inc." as the customer. Post-merger, Company B, Inc. becomes a subsidiary with those contracts still bearing only its original name. If Company A tries to use those licenses, they are in violation. Oracle's audit team will identify the mismatch and demand either: (1) re-licensing under Company A's name, or (2) retroactive license fees covering the period of non-compliance.

Due diligence must map every Oracle contract to the specific customer definition and determine how merger or integration will trigger contract amendments, formal novation agreements, or license re-purchasing. This work must begin in the discovery phase, not after close.

Full Oracle Product Inventory and Contract Review

The second pillar of effective Oracle licensing M&A due diligence is a complete product inventory and contract review. Many companies underestimate the breadth of Oracle's estate. Beyond the obvious Database and Middleware products, Oracle licenses include Java, Exadata, engineered systems, application software, and cloud services.

A full inventory addresses five critical questions:

• What products are deployed? Database, Middleware, Java, WebLogic, SOA Suite, application servers, and fusion applications each carry distinct licensing terms and audit risk.
• How many processors or named users? Processor-based and named user licensing have vastly different cost profiles. Miscounting creates immediate exposure.
• What support agreements are in place? Support is not optional. Missing support creates hidden cost exposure. Oracle backdates support fees at 22 percent of the license cost per year, meaning three years of missing support can add 66 percent to the license bill.
• Are there geographic restrictions? Some Oracle contracts limit use to specific countries or regions. Post-acquisition operations spanning new geographies may require new licenses.
• Are there embedded third-party licenses? Oracle Database includes third-party software with separate licensing obligations. Some embedded components (like certain Java versions) require separate tracking.

The contract review must also examine Oracle licensing during mergers and acquisitions clauses specific to M&A scenarios. Some Oracle agreements contain explicit change-of-control clauses requiring renegotiation or termination. Others allow continued use if certain conditions are met.

Oracle Audit Triggers and Notification Requirements

Oracle's global audit program is sophisticated and aggressive. The company uses news monitoring, acquisition database subscriptions, and internal tracking to identify targets. When an acquisition closes, Oracle already knows. Larger deals trigger automated audit requests within 30 to 180 days.

Check your specific contracts. Many Oracle agreements require the customer to notify Oracle of material changes, including acquisition or merger. Failure to notify is itself a compliance violation, independent of whether your licensing position is correct. Some customers compound the problem by not notifying Oracle because they hope to avoid triggering an audit, but non-disclosure strengthens Oracle's negotiating position if and when they discover the deal later.

Best practice: Notify Oracle formally during deal negotiations or immediately after close, depending on your contractual obligations. Provide accurate disclosure of the transaction scope, entity structure changes, and your current compliance status. This approach demonstrates good faith and can improve settlement terms if any gaps are discovered.

Use our Oracle audit assessment tool to identify your specific disclosure obligations before making notification decisions.

Duplicate Entitlements, Consolidation, and Divestiture Complexity

Some acquisitions present opportunity alongside risk. If the acquiring company and the target both license Oracle products, consolidation can identify duplicate entitlements that can be eliminated post-close.

For example, if Company A has 600 Oracle Database Enterprise Edition processors and acquires Company B with 200 more, you do not necessarily need 800 licenses post-merger. Consolidation analysis identifies where workloads can be rationalized, databases can be merged, and redundant licenses can be removed. This creates genuine cost savings and strengthens your compliance posture immediately after close.

Divestiture scenarios add complexity in the opposite direction. If you are selling a division that uses Oracle software, carving out those licenses from your parent company's umbrella agreements requires careful contract restructuring. Oracle agreements often do not permit simple license splitting. Divestiture may require licensing one set of products to the divested entity and modifying your parent company's agreements to remove reference to the sold business unit.

Work with Oracle licensing experts to model consolidation and divestiture scenarios during the due diligence phase. Over 70 percent of Oracle customers face some level of non-compliance risk, and many of those gaps can be resolved through strategic consolidation rather than expensive re-licensing.

For additional context on best practices, review our CIO checklist for Oracle M&A due diligence and the broader Oracle Knowledge Hub.