Critical Clauses in SAP Contracts: What Is Negotiable at Renewal

Not every clause in an SAP RISE contract carries equal weight. Some govern details that rarely surface in day-to-day operations. Others determine how much room you have to maneuver over the entire next term: when prices adjust, when your organization changes, when you need to exit.

Renewal is the governance moment when these clauses can be reviewed, adjusted, and, where necessary, renegotiated. Organizations that systematically work through a clause review during renewal preparation enter the conversation with SAP knowing exactly what the next contract should say. Those who skip it extend the status quo, including every constraint it contains.

This article covers six clause areas that should be fully evaluated in every clause review before renewal.

Six Clause Areas That Determine How Controllable Your Next Contract Will Be

1. Price Adjustment Clause (CPI Mechanism)

The price adjustment clause governs how SAP may announce price increases at renewal and within what limits they are permissible. It is one of the most frequently discussed clause areas in SAP renewals because it directly affects how costs evolve over the next term.

What is publicly documented: Schedule 5 of the RISE Enterprise Agreement caps increases at 3.3 percent per renewal period. SAP is required to announce any intended increase at least 45 days before the renewal start date. If the announcement is not made on time, it takes effect in the period after next, not the upcoming one. When a price increase is announced, you have the right to terminate for convenience. This right is part of the SAP standard and applies regardless of whether an increase actually occurs.

What can be negotiated beyond the publicly documented framework is the precise language of the mechanism in your individual contract. Key considerations: is the cap stated in absolute or percentage terms? Which index serves as the reference, and over what measurement period? A clause tied to a specific price index can behave very differently across market environments. Reviewing this language before the renewal conversation gives you the basis to ask targeted questions.

There is an interaction with the credit reduction mechanism worth noting: SAP standard terms allow SAP to adjust the discount if credit balances are reduced. If you plan to lower your volume in the next term, this interaction should be part of your scenario analysis before the renewal conversation begins.

2. Auto-Renewal Clause

The auto-renewal clause governs the conditions under which the contract extends, what notice periods apply, and what options both parties have. In practice, it is the clause most often underestimated, because its effect only becomes visible once a deadline has passed.

The RISE contract renews automatically without active termination. The renewal period typically mirrors the original term unless the Order Form specifies otherwise. The notice period is contract-specific and found in the Order Form or the Schedule references. It is typically three months, but it must be verified, not assumed.

What this clause means for governance: without an actively managed deadline calendar with sufficient lead time, the relevant decision window can pass unnoticed. This is not an unusual situation. It arises wherever renewal preparation is not run as a structured process with clear ownership.

What to evaluate in this clause area at renewal: does the renewal period still align with your planning cycles? Is there a reason to agree on a shorter or longer extension period? These questions can be addressed in a structured way before renewal, not after.

For the full timeline of renewal preparation, see [Cluster 1: The Renewal Timeline in Practice].

3. SLA Structure and Scope

The SLA in the RISE contract (Schedule B) defines system availability. The standard level is 99.7 percent. Enhanced Operations (Schedule 3) for large enterprises sets the bar at 99.95 percent. What the SLA measures is the logon availability of the core system, not response times, batch processing windows, or service request quality.

Key scope limitations to understand before any clause review: Cloud Features run on separate infrastructure and are not covered by the core system SLA. Service requests have no contractually guaranteed response times. Overage periods are explicitly excluded from SLA coverage.

What this means for governance: SLA credits are a limited steering instrument. The maximum credit per quarter is 0.25 percent of the annual fee, capped cumulatively at five percent, issued as credit only, and must be claimed within one month of quarter close in writing (Schedule D). Operational performance governance must therefore be built independently of the SLA credit mechanism.

What to evaluate at renewal: does the agreed SLA level match actual operational requirements? Are there system components where a higher availability threshold would be meaningful? The clause review is the right governance moment to ask these questions and fully assess the infrastructure dimension.

4. Exit Clauses and Data Portability

Exit clauses are not absent from SAP contracts. They are addressed in the standard, but often at a level of detail that does not fully support active exit governance. The difference lies in the specifics: format, timeline, cost.

What the RISE contract standard includes: Schedule C (DPA) covers data protection obligations for the period after contract end. This is a necessary baseline, but it does not contain automatic portability guarantees in customer-chosen formats. The Divestiture clause provides twelve months of transition use after a corporate divestiture, with two weeks' advance notice. Third-party cloud services are explicitly excluded from this provision.

What should be actively negotiated: data portability in standardized formats after contract end, access windows for the period immediately following expiry, and cost allocation for SAP-side export services. These questions typically arise when contract end is imminent. Renewal is the structurally better moment to address them.

Vendor lock-in does not primarily stem from missing exit clauses. It stems from a lack of clarity about what is actually portable: which custom developments run on BTP, which data sits on HANA Runtime, and what constraints the S/4HANA Compatibility Pack carries through December 31, 2030. These questions should be part of the exit clause assessment.

A detailed analysis is available in [SP-3: Negotiating Exit Rights in SAP Contracts].

5. Divestiture Clause

The Divestiture clause governs what happens to a running SAP contract when the organization changes. For many companies, this clause is irrelevant for years, and then becomes highly relevant the moment an M&A transaction or corporate restructuring occurs.

What the standard provides: twelve months of transition use following a corporate divestiture, with a two-week advance notice requirement. Third-party cloud services are explicitly excluded from this provision, meaning third-party software components in the contract must be handled separately.

What applies in the case of a carve-out, spin-off, or sale of a business unit that uses RISE is contract-specific in its detail. The clause creates a framework, but not an automatic operational separation solution. Evaluating this clause in the clause review reveals whether the current standard aligns with your corporate circumstances, and gives you the opportunity to improve it at renewal.

6. Subscription Flexibility

Subscription flexibility determines which components can be adjusted, reduced, or decommissioned, and when. It is a governance moment in the cost dimension and directly relevant to budget management over the next term.

Minimum terms by component type: Cloud Managed Services and Cloud Software carry six-month minimum terms. CAS packages carry twelve-month minimums. Third-party software is generally not decommissionable, a mechanism frequently underestimated during initial contract design that only becomes visible during a contract review.

Lockout periods for new subscriptions in the final months before contract end significantly constrain your options: no new Managed Service or Software subscriptions can be added in the last six months. No new CAS units can be added in the last twelve months. Any necessary component adjustments must be completed before these windows close, which requires early planning.

What to evaluate at renewal: are the minimum terms for individual components compatible with your planning horizon? Are there components where greater flexibility would be valuable in the next term? This clause area connects directly to the data foundation from Phase 1 of renewal preparation, because shelf-ware analysis and subscription flexibility rely on the same usage data.

How the Clause Review Fits into Renewal Preparation

The clause review belongs in Phase 3 of renewal preparation, that is, between nine and six months before contract end. At this point, the data foundation from Phase 1 is in place, the scenarios from Phase 2 have been internally aligned, and the first formal conversation with SAP has not yet begun.

The output of the clause review is a documented clause delta: which clauses meet the needs of the next term, which should be adjusted, and which are acceptable as-is if other points in the renewal are resolved. This delta is the foundation for negotiation preparation.

Not every clause will be actively negotiated in every renewal. But without having completed the review, you enter the conversation without the ability to know that.

FAQ: Critical Clauses in SAP Renewal

What is the single most important clause to review in an SAP renewal? There is no one clause that is equally relevant for every organization. The price adjustment clause is central because it directly affects how costs develop over the next term. The auto-renewal clause is operationally critical because missing its deadline leaves no room for correction. Which clause matters most depends on your current contract situation, your planned changes, and your organization's circumstances.

Can I change clauses that SAP has written as standard at renewal? SAP standard contracts are a starting point, not a ceiling. What ends up in an individual contract depends on the negotiation and your position going in. A solid data foundation, a clearly formulated clause delta analysis, and sufficient lead time are the prerequisites for running that conversation with structure.

What happens if I don't raise exit clauses at renewal? You extend the status quo. That is not necessarily a problem if the current terms meet your needs. Where gaps exist, for example around data portability or transition windows after contract end, they are structurally harder to address after renewal than before it.

How do I find out how the clauses in my contract are actually worded? The first step is complete contract documentation: the Order Form, all Schedules, all Amendments. The clause areas described in this article are typically found in Schedule 5 (price adjustment, auto-renewal), Schedules B and D (SLA and credits), Schedule C (DPA and exit), and the Order Form itself (special agreements, minimum terms, lockout periods).

Next Steps

The six clause areas covered here are the substance of the clause review in Phase 3 of renewal preparation. The data foundation needed to conduct it is described in [Cluster 2: Building the Data Foundation for SAP Renewal]. The complete timeline from M-18 to M-0 is available in the [Pillar 5 Hub: SAP Renewal Negotiation Framework].

If you want to assess your current contract position before your next renewal: the [FinOptory Contract Check] analyzes your contract situation in four weeks. Fixed price, EUR 7,900. A clear starting point for renewal preparation.