SAP licence pools are typically signed by a single contracting entity and consumed by users across the whole group. Shared-service centres process for many entities, joint ventures consume against the parent contract, divested entities continue to consume during transition periods, and acquired entities consume under their original contracts pending integration. Each pattern intersects the named-user, affiliate-use, and territorial clauses of the master licence in ways that determine whether the consumption is permitted, conditionally permitted, or a breach. This article sets out the patterns and the contractual treatment of each. The full advisory frame sits within our licence compliance assessment service.
The affiliate-use clause
The master licence typically permits use by the named contracting entity and its affiliates as defined in the contract. The definition of affiliate is the principal lever. Common definitions include majority-owned subsidiaries, entities under common control, and entities meeting a minimum ownership threshold (often 50%). Each definition produces a different scope of permitted use. Joint ventures below the threshold are usually outside the affiliate scope and require separate licensing or contractual extension.
The shared-service centre pattern
A shared-service centre processes transactions on behalf of multiple group entities. Each transaction is initiated by a user in one entity and processed by a user in the centre. The licence question is whether the processing user is consuming on behalf of the initiating entity, the centre’s entity, or both. The answer depends on the contract’s territorial and affiliate-use language and on the documented operating model. Estates with shared-service centres that have not formally documented the operating model carry a latent compliance exposure at audit. The indirect access pillar covers the related document-trigger considerations.
Operational arrangements that pre-date the current SAP contract are often the source of the most consequential compliance exposures. The contract was signed against a structure that has since evolved without contract amendment.
The joint-venture pattern
Joint ventures occupy a contractual grey zone. A 50/50 joint venture is typically not an affiliate of either parent under the standard definitions, and yet it consumes SAP through one or both parent contracts. The joint venture should be on a separate contract, on an explicit extension of the parent contract, or on a documented partner agreement. Estates that consume joint-venture transactions against the parent contract without explicit cover face compliance discussions at audit that consume time disproportionate to the actual usage. The remediation is a contract amendment, typically inexpensive at renewal and disproportionately expensive at audit.
The divestment period
Divested entities frequently continue to consume SAP under transition-services arrangements pending their own implementation. The licence treatment depends on the divestment agreement, on the SAP contract’s assignment clauses, and on the timing of the transition. SAP’s standard position is that the divested entity exits the affiliate scope at the close date and must license independently from that point. Negotiated divestment-period extensions are available but require explicit drafting. The contract negotiation pillar covers the transition-period clauses.
The acquisition period
Acquired entities typically arrive with their own SAP contract, their own licence portfolio, and their own user base. The integration question is whether the acquirer’s contract absorbs the target’s users, the target’s contract continues independently, or the contracts merge into a new combined contract. Each path has distinct economic and compliance consequences. Estates that allow acquired entities to consume against the acquirer’s contract without formal absorption produce both compliance exposure and renewal-cycle complexity. See the licence harvesting article for the related portfolio rationalisation methodology.
The territorial overlay
SAP contracts increasingly include territorial provisions: permitted use is limited to a defined geography, expansion into new territories requires notification or contract extension, and certain entities (joint ventures with regional partners, for example) are explicitly excluded. The territorial overlay interacts with the affiliate-use clause to determine the actual scope of permitted consumption. Estates with operations in newly added geographies should verify the territorial scope against the contract before assuming the consumption is covered. The licence-types topic page covers the contractual mechanics.
The contractual instruments
Three contractual instruments support clean pool sharing across entities. The affiliate-use clause defines the scope. The named-user assignment determines the consumption metric. The transfer-and-reassign clauses govern whether named-user licences can move between entities within the pool. Estates that operate all three intentionally maintain compliance with substantially less effort than estates that operate only the affiliate-use clause. See the named-user licenses pillar for the per-licence-type assignment rules.
The audit exposure
Pool-sharing arrangements are a routine target of SAP audit teams because the patterns produce documentable evidence of cross-entity consumption that the auditor can compare against the contractual scope. The audit conversation is typically procedural rather than substantive: did the consumption exceed the affiliate-use scope, the territorial scope, or the named-user assignment scope? The audit-readiness work is the contractual mapping of the consumption to the scope, with documented operating-model evidence supporting the mapping. The audit defence pillar covers the response methodology and the conglomerate pool-rationalisation case file illustrates the work in practice.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Estates with shared-service centres, joint ventures, divested entities in transition, or recently acquired entities should run a contractual mapping of the consumption against the affiliate-use, territorial, and named-user scopes. The mapping typically takes between four and eight weeks for a multi-entity group and produces a remediation plan that closes the latent exposure before the next audit cycle. The remediation is consistently less expensive than the audit-driven retrofit and contributes to the average 68% audit-claim reduction the practice achieves.