The customer affiliate clause defines which entities related to the contracting party are allowed to use the Oracle software, and by extension which entities Oracle may bring into the scope of an audit. It is one of the least examined clauses in an Oracle agreement and one of the most consequential, because it controls how a licence flows across a corporate group and what happens to that licence when the group changes shape through acquisition, divestiture, or restructuring. A buyer that signs the default definition without thought may find that subsidiaries it expected to cover are excluded, that entities it has sold are still inside the audit perimeter, or that an acquired business cannot use the licence without a fresh purchase. This note sets out what the clause does and how a buyer should negotiate it.
What the affiliate definition does.
The agreement is signed by one legal entity, but enterprises rarely operate through a single entity. The software is used across subsidiaries, branches, and shared service centres. The affiliate clause is what extends the right to use the software from the signing entity to those related entities. The standard Oracle definition ties affiliate status to ownership or control, usually expressed as a majority shareholding, so that an entity is an affiliate only while the contracting party owns more than half of it.
That ownership test has consequences the buyer must trace. An entity in which the group holds a large minority stake but not a majority may fall outside the definition and therefore have no right to use the software. A joint venture, a partly owned regional operation, or a newly formed entity not yet majority held can all be excluded by the default wording. The buyer should map its actual corporate structure against the definition rather than assuming every part of the group is covered. This is the same mapping discipline that underpins sound compliance, discussed in the compliance posture note.
The audit perimeter.
The affiliate definition cuts both ways. It defines who may use the software, and it also defines who Oracle may audit. If the definition is broad, Oracle's audit rights reach across the whole group, including entities the buyer did not intend to bring into the relationship. If a subsidiary deployed Oracle software informally, that deployment becomes Oracle's to examine wherever the entity falls inside the affiliate perimeter. The buyer that has not controlled the definition has not controlled the audit exposure.
The point is sharpest in groups that have grown by acquisition, because acquired businesses arrive with their own Oracle estates and their own compliance histories. When those businesses become affiliates, their legacy deployments enter the buyer's audit perimeter under the buyer's agreement. The buyer should understand which entities the affiliate clause pulls in before an audit makes the question concrete. For the wider audit posture this sits within see our audit defense service.
Mergers and the inherited estate.
The most expensive affiliate question arises in mergers and acquisitions. When a group acquires a business, the affiliate clause determines whether the acquired entity may use the buyer's Oracle licences and whether the buyer's licences may flow to it. The default definition usually allows it, but Oracle agreements frequently limit the benefit, restricting use to the historical scope of the business as it existed before acquisition or excluding entities acquired after the contract date.
The buyer that acquires a business and assumes its existing Oracle licences will simply carry forward often finds the position is more complex. Oracle may treat the change of control as a trigger for a true up, and the acquired entity's deployments may need to be re licensed under the new structure. The buyer planning an acquisition should examine the affiliate and assignment clauses in both the acquiring and the acquired agreements before completion, so the licensing cost of the deal is known in advance rather than discovered afterward. The cost modelling discipline this requires is similar to that in the ULA cost model note.
Divestiture and the orphaned licence.
The reverse problem arises on divestiture. When a group sells a business, the divested entity ceases to be an affiliate, and its right to use the buyer's Oracle software ends with the change of control. The divested business that continues to run Oracle software after the sale is using it without a licence unless the buyer has negotiated transition rights or the buyer of the business has acquired its own licences. The seller that has not addressed this in the sale agreement may carry continuing compliance exposure for software it no longer controls.
The buyer planning a divestiture should negotiate the licensing transition before the sale closes, either securing a transition services right that allows the divested business to keep using the software for a defined period or ensuring the acquirer takes on the licensing. Leaving the question to be resolved after the sale, when neither party holds leverage with Oracle, is the expensive path. This timing logic mirrors the broader principle that licensing questions are cheapest to resolve before the commercial event, not after.
Negotiating the definition.
The affiliate clause is negotiable, and the buyer should treat it as a term to shape rather than accept. The asks that improve the buyer's position are widening the definition to include the entities the buyer actually operates through, including partly owned and joint venture entities where relevant, securing the right for licences to flow to entities acquired after the contract date, and obtaining transition rights for divested businesses. The buyer should also seek to limit the audit perimeter so that it matches the use rights rather than extending further.
These asks succeed best at the moments the buyer holds leverage, which is at a new purchase or a large renewal when Oracle wants the signature. The buyer that raises the affiliate question as part of the commercial negotiation, framed as aligning the contract with the group's real structure, often secures improvements that would be impossible to obtain in isolation. For the framing and timing of such asks see the negotiation frameworks note, and for the contract reading that supports them see the licence agreement note.
Keeping the structure current.
An affiliate position negotiated once is not negotiated forever, because the corporate structure changes. Acquisitions, disposals, and reorganisations all alter which entities fall inside the definition, and the buyer should review the affiliate position whenever the structure changes materially. The buyer that treats the clause as a living term, revisited as the group evolves, avoids the slow accumulation of entities that have drifted outside the use rights or remained inside the audit perimeter.
This review is part of the broader governance that a mature buyer maintains over its Oracle relationship, alongside the deployment mapping and the contract record. For the deal structures that interact with corporate change see the ULA deal page, and for the wider product context see the Oracle Database product page.
Engaging an independent advisor.
An independent advisor maps the buyer's corporate structure against the affiliate definition, identifies the entities that are excluded from use or included in the audit perimeter, models the licensing cost of planned acquisitions and divestitures, and negotiates a definition that aligns the contract with the group's real shape. The advisor sits on the buyer side and treats the affiliate clause as a commercial term that controls both value and risk. For the contract reading service this sits within see our contract review service, and for the complete framework read the Oracle Negotiation Playbook.
A multinational manufacturing group engaged an advisor during an acquisition in 2024. The advisor found that the target's Oracle agreement excluded entities acquired after the contract date, which meant the buyer's existing licences would not cover the new business and a fresh purchase would be required. The advisor negotiated the licensing into the broader renewal at favourable terms rather than letting it surface as a standalone true up after completion, saving the group a substantial unplanned cost.