SAP Affiliate Licensing: Covering Group Companies Under Existing SAP Contracts

Who counts as a user within the corporate group?

SAP contracts are typically concluded with a single legal entity: the contracting party. But what happens when subsidiaries, joint-venture partners, or newly acquired companies use the same SAP systems? And who determines whether that use is contractually covered?

The answer lies in the affiliate licensing provisions of each SAP contract. These clauses define which affiliated entities are authorized under an existing agreement, under what conditions that authorization applies, and what happens when the ownership structure changes.

In practice, the topic rarely surfaces until a governance moment has already arrived: an acquisition, a carve-out, a reorganization. At that point, companies scramble to determine what the contract actually says. Those who review earlier retain more room to act.

What affiliate licensing means

In SAP contracts, "affiliate" generally refers to a company that is directly or indirectly controlled by the same parent entity. The exact definition varies by contract version and negotiation history, but the core concept is consistent: companies belonging to the same corporate group should, under certain conditions, be authorized to use software under a shared license agreement.

That sounds like an operational simplification. In reality, it masks a governance moment on the cost side: SAP frequently charges additional license fees for affiliate use when the number of authorized users, license classes, or usage volume exceeds the contractually defined thresholds. Without a systematic review, it is nearly impossible to track whether and when those thresholds are reached.

There is also the question of entitlement: not every group company is automatically covered by an existing contract. Some contract structures require an explicit list of authorized affiliates. Others permit implicit shared use but attach notification obligations or audit rights on SAP's part.

Governance moments in a corporate group context

Complexity arises when the corporate structure changes. Four typical situations:

Newly acquired company: A company is acquired that also runs SAP. This immediately triggers a governance moment around usage: under which contract do the acquired company's SAP systems continue to operate? Under the existing group contract, under the target company's legacy agreement, or does everything need to be renegotiated? That decision is not only technical. It is contractual and commercial.

New subsidiary: A new entity is founded or a joint venture is established. In this governance moment around entitlements, the question is whether that entity falls under the existing contract at all. If so, on the basis of which clause and with what restrictions. If not, what is the correct path to licensing?

Carve-out or spin-off: A company is divested. This governance moment around infrastructure requires answers on system separation, transferable licenses, and ongoing support contracts. SAP licenses are generally not freely transferable, which makes a carve-out contractually complex.

Corporate reorganization: Internal restructurings in which entities are merged or reassigned can render existing affiliate provisions ineffective. The governance moment here is on the cost side: entities using SAP without updated licensing create an undercoverage risk.

What affiliate clauses typically cover

Without claiming completeness and without reference to specific contract details, the most common areas of regulation can be identified from public sources:

Scope of authorized affiliates: Most SAP contracts define "affiliate" based on majority ownership or controlling interest. Companies held only as minority stakes, or joint-venture partners with shared control, are often not automatically included.

Conditions of use: Authorized affiliates are typically permitted to use the systems for internal purposes only, not for external services or as resellers. This boundary matters when SAP systems are intended to become part of a managed-service offering.

Notification obligations: Many contracts require that changes to the affiliate population be reported to SAP. The deadlines and consequences of non-notification are contract-specific but can trigger audit rights or retroactive licensing requirements.

Compliance consequences for non-fulfillment: When affiliates use SAP without contractual coverage, an SAP audit may classify this as undercoverage. The consequences, typically retroactive licensing at current list prices, are a separate matter from how the situation arose in the first place.

What this means for ongoing governance

Affiliate licensing is not a one-time contract topic. It is an ongoing governance subject, because corporate structures change. Companies that practice strategic SAP vendor management therefore embed a regular review of affiliate coverage into their governance rhythm.

The questions to ask are manageable: Which entities in the group use SAP? Are all of them licensed under the current contract? Are there entities where affiliate status is unclear? Has the ownership structure changed since the last contract was signed?

Once these questions are anchored in the governance calendar, affiliate licensing shifts from a reactive topic to a proactively managed area.

Frequently asked questions

What is the difference between a subsidiary and an affiliate in SAP contracts?

The term "affiliate" in the SAP contract context is broader than the accounting definition of a subsidiary. It typically covers all entities that are directly or indirectly controlled by more than 50 percent. The precise definition is contract-specific and should be taken from the relevant contract text.

Does SAP need to be notified when a new subsidiary starts using SAP?

That depends on the specific contract. Many contracts include notification obligations for changes to the affiliate population. Whether a new entity is automatically covered or must be explicitly added is determined by the license coverage clauses and the affiliate schedule.

What happens to SAP contracts in an acquisition?

Contracts are generally not automatically transferable to an acquired company. Assignment clauses typically require SAP's consent. Whether the acquired company can be integrated into the existing group contract as a new affiliate, or whether a standalone contract continues or is renegotiated, is a matter for M&A-related contract governance. For more, see the article SAP Contracts in M&A, Carve-Out, and Corporate Acquisitions.

What risks arise when affiliates use SAP without license coverage?

If SAP conducts an audit and identifies usage without corresponding license coverage, this can lead to retroactive licensing at current list prices. The risk is especially relevant after acquisitions where the compliance posture of the acquired company has not been fully reviewed.

Conclusion

Affiliate licensing in SAP is not a peripheral topic. It is a concrete governance moment that becomes relevant in any corporate group with multiple entities, as soon as the structure changes. The foundations are laid in the contract; the consequences emerge in day-to-day operations. Organizations that integrate this area into their governance rhythm, rather than reviewing it only when something goes wrong, retain the ability to act before costs escalate.

For further aspects of SAP contract governance during structural changes, see the pillar Managing SAP as a Strategic Vendor and the article on M&A, Carve-Out, and Contract Transfer.

About the author

Bernhard Mändle is Managing Consultant at FinOptory. He helps organizations govern their SAP contracts after signature: aligning usage and costs, and making the SAP investment work as intended. Years of experience in SAP contract negotiation and governance across on-premise, BTP, and RISE. DSAG member. Independent of SAP, resellers, and system integrators. Learn more at finoptory.ai.

Sources: