SAP Master Agreement Key Clauses Explained

1. The Licence Grant Clause

The licence grant clause is the core of any SAP Master Agreement. It defines precisely what rights the customer acquires when they purchase SAP software. Understanding the exact language is the starting point for all subsequent commercial analysis — including audit exposure, indirect access risk, and exit strategy.

SAP's standard licence grant is a non-exclusive, non-transferable, limited right to use the software for the customer's internal business purposes. Each of those qualifiers carries significant commercial implications:

• Non-exclusive — SAP can sell the same software to any competitor. You have no exclusivity rights on pricing, features, or access.
• Non-transferable — You cannot sell, sub-licence, or transfer SAP licences to another entity without SAP's explicit written consent. This affects M&A, outsourcing, and shared service centre models.
• Internal business purposes — Use is restricted to the legal entity named in the agreement for its own operational needs. Use by affiliates, subsidiaries, or third-party service providers requires separate licence provisions.

1.1 The Affiliate Clause — Often Missing, Always Important

Enterprise SAP deployments almost always span multiple legal entities within a corporate group. The standard Master Agreement grants rights to the named contracting entity only. SAP uses this to claim that system access by affiliates, subsidiaries, and overseas offices constitutes licence non-compliance, triggering back-licence claims.

The affiliate clause should explicitly list, or provide a definition for, all entities within the corporate group that are permitted to use the licensed software. It should also address how newly acquired entities are brought within scope (most enterprise buyers need a 90-day grace period post-acquisition for compliance alignment).

For full context on negotiating this and other SAP Master Agreement provisions, read our complete SAP Master Agreement breakdown and our SAP Licensing Basics guide.

2. The Payment and Maintenance Obligation Clauses

SAP Master Agreements contain payment provisions that extend far beyond the initial licence purchase. Understanding the perpetual nature of maintenance obligations — and the specific conditions under which they can be terminated — is essential for long-term cost management.

2.1 Perpetual Licence with Annual Maintenance

The SAP perpetual licence model means the customer pays once for the right to use the software indefinitely, but then pays annually for maintenance (currently 22% of net licence value) to maintain access to updates, patches, legal changes, and SAP support. The Master Agreement's payment clause determines whether this maintenance obligation is truly optional.

In most versions of the SAP Master Agreement, maintenance is structured as a separate annual contract that renews automatically unless cancelled in writing within a specified notice period (typically 90 days before the renewal date). However, certain versions of the agreement contain "maintenance commitment" provisions that require the customer to maintain SAP support for a minimum period — sometimes three to five years from the original licence purchase date.

2.2 Price Escalation Mechanisms

The maintenance fee structure under SAP's standard Master Agreement is calculated as a percentage of net licence fees — the price actually paid for licences. However, some agreement versions use list price (SAP's published retail price, which is typically 3–5x the actual negotiated price) as the maintenance base. This distinction alone can create a maintenance obligation two to three times larger than expected.

Additionally, watch for price escalation mechanisms tied to SAP's list price rather than CPI or a fixed cap. SAP has increased list prices significantly in recent years; agreements with list-price-linked maintenance escalation have seen fees increase by 15–40% above what was anticipated at contract signature.

3. The Acceptable Use Policy Clause

SAP's Acceptable Use Policy (AUP) clause — or its equivalent "Prohibited Use" section — defines the boundaries of permitted software use. Violations of the AUP are typically defined as material breach, which gives SAP grounds for termination of all licences. This makes the AUP clause operationally critical in ways many procurement teams don't appreciate.

3.1 What SAP Prohibits

Common prohibitions in SAP's AUP clause include: benchmarking SAP software against competing products without SAP's consent; reverse-engineering SAP code; accessing SAP software to build competing products; and disclosing SAP confidential information (including SAP's internal cost structures revealed during audit discussions). The benchmarking prohibition is particularly relevant — enterprises comparing SAP pricing against Oracle or Microsoft product sets should ensure their Master Agreement doesn't require SAP consent to do so.

3.2 Training and Sandbox Use

SAP AUP clauses also address training environments, development systems, and test instances. SAP's position in many agreements is that non-production systems require separate licences at reduced rates — "development licences" or "test licences." The number of named users on training systems, the frequency of use, and whether production data is used in test environments can all create audit exposure if not addressed in the AUP or a supplemental development use schedule.

4. The Confidentiality Clause — Two-Way Obligations

SAP's confidentiality clause imposes mutual obligations on both parties. SAP is obligated to protect the customer's data and commercially sensitive information; the customer is obligated to protect SAP's proprietary information, including pricing. The asymmetry in practice: SAP's obligations are general; the customer's obligations are specific and policed through audit processes.

4.1 Pricing Confidentiality

SAP's standard confidentiality clause typically prohibits the customer from disclosing the commercial terms of their agreement — including the discounts received. This is commercially significant because SAP uses pricing opacity to prevent customers from benchmarking their deal against peers. Enterprises should seek to narrow the scope of the pricing confidentiality obligation to allow disclosure to professional advisors (lawyers, financial advisors, M&A counterparties) under appropriate confidentiality controls.

4.2 Survival of Confidentiality Obligations

The confidentiality clause typically survives termination of the Master Agreement by five to seven years. This means even after an enterprise has exited the SAP relationship, it remains bound by pricing confidentiality obligations. Consider the implications for RFP processes, competitive benchmarking, and the use of historical SAP pricing data in future procurement decisions.

5. The Force Majeure Clause — SAP's Performance Escape

SAP's force majeure clause — defining circumstances where SAP is excused from performance obligations — is broad by design. Standard force majeure language excuses SAP from liability for: acts of God, labour disputes, government actions, and — in many modern versions — "cyber events" or "widespread infrastructure failures."

The practical implication: if SAP's cloud infrastructure suffers a significant outage during your financial year-end processing, SAP's force majeure clause may prevent you from claiming compensation. Given that RISE with SAP contracts involve SAP-managed cloud infrastructure, the force majeure clause deserves careful scrutiny. Enterprises should negotiate specific SLA carve-outs from force majeure — the fact that SAP's data centre suffers a hardware failure does not change the commercial impact of your SAP system being unavailable during critical business periods.

6. The Data Processing Agreement (DPA) — Compliance Risk

Any SAP Master Agreement covering systems that process EU personal data requires a compliant Data Processing Agreement. SAP provides a standard DPA addendum, but its terms — particularly around data sub-processing, data residency, and breach notification timelines — have not always kept pace with GDPR and subsequent regulatory developments.

Key DPA clauses to scrutinise: (a) the list of SAP sub-processors and the process for approving new sub-processors; (b) data residency commitments for RISE with SAP and SAP BTP deployments; (c) the breach notification timeline (GDPR requires 72 hours; some SAP DPAs allow longer); and (d) the audit rights within the DPA, which should permit the customer to commission independent data protection audits of SAP's processing activities.

For a comprehensive view of all provisions in the Master Agreement and how they interrelate, read our SAP Master Agreement breakdown guide. To understand what you should actively negotiate, see what to negotiate before signing.

7. The "Most Favoured Customer" Clause — Rarely Present, Always Worth Seeking

A Most Favoured Customer (MFC) clause obliges SAP to offer the customer pricing and terms at least as favourable as those offered to similarly-situated customers. SAP rarely offers MFC clauses voluntarily. When they do appear in enterprise agreements — typically in the context of very large deals or in markets where SAP faces strong competition — they provide meaningful ongoing price protection.

Even absent a formal MFC clause, enterprise buyers should request regular benchmarking rights: the right to demand SAP provide evidence that their pricing remains competitive with comparable deals. This is a weaker mechanism than an MFC clause but nonetheless creates accountability. Our SAP contract negotiation advisory service includes benchmarking analysis against a proprietary database of enterprise SAP deals.