The affiliate definition decides who may use your license.

01 Key findings

1. The definition, not the price, sets who is licensed. A license grants rights to one named entity; every subsidiary, branch and shared-service center outside the affiliate definition is technically unlicensed, and that gap is exactly what an audit is designed to find.

2. Set the threshold at 50 percent or control. Broad enough to cover every subsidiary that needs access, precise enough to survive an audit — the percentage and the meaning of "control" are the negotiable variables that determine your coverage in every structure you run.

3. M&A is where the clause is tested hardest. Vendors monitor public deals and time audits to follow them. Without automatic inclusion of acquired entities, every acquired user is unlicensed from day one and chargeable at a premium.

4. A divestiture transition license is the single best pre-emptive ask. Twelve to twenty-four months of continued use lets a departing unit stand up its own contracts. Vendors grant it readily at signing because it costs them no current sale.

5. Negotiate the clause per vendor against one entity map. Oracle, Microsoft, SAP and IBM each use their own affiliate language and all default to vendor-favorable terms; a definition won from one does not carry to another.

02 What the affiliate clause controls

A software license grants usage rights to a named legal entity, the contracting party. The affiliate clause extends those rights to related entities, defining who counts as an affiliate and therefore who may legitimately deploy and use the software. Without a clear affiliate definition, only the single signing entity is licensed, and every subsidiary, branch and shared-service center using the software is technically unlicensed — a gap audits are designed to find.

The definition usually turns on ownership or control. A typical formulation grants affiliate status to any entity that the contracting party controls, is controlled by, or is under common control with, where control means ownership of more than 50 percent of voting equity. The precise percentage and the meaning of control are the negotiable variables, and they determine the breadth of your license in every corporate structure you operate.

The clause interacts with the license metric. If a contract is priced per user or per employee, the affiliate definition sets which entities employees can be counted from, and a broad definition that includes a large subsidiary can increase the licensed count as much as it increases coverage. The two have to be read together, because a generous affiliate clause attached to an employee metric can quietly raise the bill rather than just extend rights.

03 Vendor vs buyer positions

Vendors prefer a narrow affiliate definition because it limits the population entitled to use software bought under one agreement, preserving the opportunity to sell additional licenses to each related entity. Buyers want a broad definition that covers the whole corporate family under one contract and one price. The negotiation is a contest over how many of your entities one purchase covers.

The buyer position is not simply the broadest possible definition. An affiliate clause so broad that it sweeps in joint ventures and minority holdings can create its own problems, including disputes over whether usage by a partly owned entity is licensed at all and whether it counts toward a usage-based metric. The aim is a definition matched to your actual corporate structure and growth plans — covering the entities that genuinely share the software without overreaching into structures the vendor will contest.

04 M&A and divestiture risk

The affiliate definition is tested hardest during mergers, acquisitions and divestitures — the moments when corporate structure changes fastest. When you acquire a company, its employees often need access to software licensed under your existing agreements. If the affiliate clause includes newly acquired entities automatically, that access is licensed from day one. If it does not, every acquired user is unlicensed until a new purchase is made, and the vendor is entitled to charge for them, frequently at a premium and frequently discovered in an audit triggered by the deal.

Divestitures cut the other way. When you sell a business unit, the affiliate clause determines whether the divested entity can keep using the software during separation. A clause that strips affiliate status the instant ownership drops below the threshold can leave the divested unit — and the transitional services you owe it — running on unlicensed software. A negotiated transition license, allowing the former affiliate continued use for a defined period such as 12 to 24 months, prevents that and is far easier to secure at signing than mid-divestiture.

Carve-outs and spin-offs are the hardest case, because the entity leaving may itself be large enough to need its own enterprise agreement on day one. Planning the affiliate and transition terms before the transaction is announced lets the parent and the departing entity separate cleanly, each with defined rights, rather than discovering during diligence that the software both sides rely on cannot legally follow the split. The cost of getting this wrong is paid twice — once by the seller in audit exposure and once by the buyer of the divested unit in a rushed, weak-position purchase.

05 Strong vs weak clause language

The gap between a clause that protects the buyer and one that protects the vendor comes down to a handful of specific phrasings. Compare the weak default language against the language worth negotiating in.

06 Corporate structures that complicate it

Several common structures strain a standard affiliate definition. Holding-company arrangements, where the contracting entity owns but does not operate the systems, can leave the operating subsidiaries outside a narrowly drawn definition. Shared-service centers that run software on behalf of the whole group raise the question of whether the center, the group, or each served entity is the licensed party. Joint ventures and minority-owned ventures sit at the edge of most definitions and are a frequent source of dispute.

The practical step is to map these structures against the affiliate clause before signing, not after an audit names them. For each entity that touches the software, confirm it falls inside the definition, and where it does not, decide whether to widen the clause, license the entity separately, or restructure access. A clause written to a current, accurate entity map is the cheapest insurance against the audit findings these structures produce. Our audit scope limitation guide covers how to bound the audit itself.

07 How major vendors treat affiliates

Affiliate language is not uniform across vendors, and the differences matter. Oracle ties affiliate rights closely to the ordering document and is restrictive about extending use beyond the contracting entity, which makes the definition a priority in any Oracle agreement. Microsoft enterprise agreements handle affiliates through enrollment structures that can either include or exclude affiliates from the master agreement, so the choice of structure is itself a negotiation. SAP and IBM both define affiliates by ownership thresholds that buyers can negotiate, and both treat divestitures and acquisitions as events that can change licensed scope.

The common thread is that every major vendor leaves room to negotiate the threshold, the treatment of acquisitions and divestitures, and the transition period — and every one of them defaults to language that favors the vendor. Treating the affiliate clause as a standard negotiated item across the portfolio, rather than vendor boilerplate, is what keeps the corporate family covered under the contracts you already pay for.

08 Negotiation checklist

Four discrete, low-controversy asks turn a standard affiliate clause into one that protects the buyer. Raise them together at signing rather than one at a time under pressure.

09 Where to focus