SAP Renewal Negotiation Framework: Renewal Preparation Over 12 to 18 Months

SAP contract renewals are not shaped in the final weeks before the term ends. They are shaped in the 12-to-18-month window that precedes that date. Organizations that consolidate usage data, review critical clauses, and align stakeholders during this window enter the renewal with a structured negotiating position. Those that wait negotiate under time pressure, with incomplete data, and with an active auto-renewal risk.

Table of Contents

1. Why Renewal Preparation Begins 12 to 18 Months Out
2. Four Phases: The Renewal Timeline
3. Building the Data Foundation: What Counts and What Doesn't
4. BTP Usage Data as Negotiation Input
5. Critical Clauses: What the Next Contract Must Include
6. CPI Clauses and Price Adjustment Mechanisms
7. Self-Reporting Obligations and Overage Governance Before Renewal
8. Stakeholder Model: Who Needs to Be Involved and When
9. Auto-Renewal: Deadlines, Risks, and Options
10. Exit Rights: What Should Be Negotiated
11. How-To: Renewal Readiness in 10 Steps
12. FAQ
13. Next Steps

---

Why Renewal Preparation Begins 12 to 18 Months Out {#why-renewal-preparation-begins-12-to-18-months-out}

Renewal is not an event that materializes at the end of a term. It is a structured governance moment that begins 12 to 18 months before that date and must be managed across all four governance areas: usage, entitlements, infrastructure, and cost. Organizations that use this governance moment systematically enter the negotiation with a complete data foundation. Those that miss it cede the governance moment entirely.

The mechanics of the RISE Enterprise Agreement impose structural deadlines that allow no exceptions. Missing those deadlines means you can no longer shape terms actively. You can only react to the conditions your counterparty sets.

Auto-Renewal as the Structural Default

The RISE Enterprise Agreement renews automatically without an active termination notice. The renewal term typically matches the original contract term, unless the Order Form specifies otherwise. This mechanism is not an edge case. It is the contractually intended default.

What this means for planning: without an active decision, the contract continues under terms that SAP may adjust according to contractual rules. The 45-day price increase notification window (Schedule 5, publicly available) is the relevant reference point, not the contract end date itself. Organizations that wait until the notification arrives have already missed the governance moment.

For governance practice, this means the renewal calendar does not start from the expiration date. It starts from the back-calculated decision deadline. If a RISE contract ends on March 31, 2028, and SAP requires three months' notice, the latest governance moment for an active decision is December 31, 2027. Structured preparation therefore begins no later than September 30, 2026, meaning 18 months before contract end.

Credit Expiry at Contract End

A governance moment that has its full effect in the final contract year: the degressive roll-over mechanism in the RISE Enterprise Agreement reduces the transferable credit balance by contract year. In the final year, any remaining credit expires entirely with no option to carry it forward.

In practice, this means the governance pressure does not arise at contract end. It arises in the penultimate year. Organizations that recognize their credit balance will exceed their planned consumption profile still have options in the year before: expand usage, shift credits into CAS packages, or open a discussion about volume adjustment. In the final year, those governance options are constrained because subscription lock-out periods apply. The last six months before contract end allow no new Managed Service or Software subscriptions. The last twelve months allow no new CAS units.

Understanding this deadline structure means treating credit planning and renewal preparation as a connected task.

SAP Starts Earlier Than the Customer

A structural dynamic that renewal preparation regularly underestimates: SAP typically initiates the renewal dialog with customers 12 to 18 months before the term ends. The SAP renewal team works with structured sales processes, complete usage histories from SAP's own systems, and a clear target for the next contract.

This head start creates an information asymmetry. SAP knows the usage data from its own systems. Customers who have not systematically prepared their own consumption picture face a structured counterparty without an equivalent data foundation. This situation is not inevitable. It arises where usage data is not continuously consolidated.

The renewal governance moment is therefore also a governance moment for information parity. Organizations that have solid data across the same four governance areas, usage, entitlements, infrastructure, and cost, enter the conversation on equal informational footing.

The Renewal Governance Moment

Renewal is not an administrative process. It is the central commercial governance moment in the SAP contract lifecycle. The quality of the next contract, its volume, pricing, clauses, and flexibility options, depends on the preparation work done in the preceding 12 to 18 months.

All four governance areas are relevant at renewal simultaneously. Usage data shows which components are fully utilized and where volume adjustment potential exists. Entitlement data confirms correct FUE allocation and identifies optimization potential across license classes. Infrastructure data provides the basis for appropriate sizing of the next term. Cost data enables a well-grounded assessment of price changes and renewal scenarios. Organizations that consider only one of these areas negotiate from an incomplete foundation.

Once the new contract is signed, terms are fixed for the next term. The next governance moment of this scale will not come again for three to seven years.

---

Four Phases: The Renewal Timeline {#four-phases-the-renewal-timeline}

A structured renewal process breaks down into four phases. Each phase has clear tasks, owners, and a defined output. The phase model begins 18 months before contract end (M-18) and concludes with signing and the transition governance for the new term (M-0).

Phase 1 (M-18 to M-12): Inventory and Data Foundation

Phase 1 lays the groundwork for everything that follows. The objective is a complete, current picture of your own contract position: what is contractually agreed, what is actually being used, and where do gaps exist?

Consolidate usage data. Prepare FUE utilization by user type (Advanced Use, Core Use, Self-Service Use, Developer Access) for the past 12 to 18 months. Document BTP credit consumption by subaccount and project area. Compare Cloud Managed Services usage against purchased volume. CAS package usage: paid volume versus services actually delivered.

Update contract documentation. Review the Order Form, all Schedules, Amendments, and special agreements for completeness and currency. Validate Schedule 5 as the pricing reference: unit prices, tiered thresholds, minimums. Trace credit development by contract year from Balance Statements. Document subscription minimum terms and current lock-out periods.

Identify underutilization. Components for which credit is being spent without the agreed usage scope being reached need to be identified in this phase. This finding is not a critique of past operations. It is the foundation for sound volume planning in the next term.

Prepare quality data. Analyze SLA compliance for the past 12 to 18 months. Document ticket volumes and service request turnaround times. Record unresolved escalations as a factual summary.

The output of Phase 1 is a complete picture of your contract position: what is agreed, what was actually used, and what the delta is.

Phase 2 (M-12 to M-9): Internal Alignment and Scenario Analysis

Phase 2 prepares the decision-making framework. The objective is an internally aligned picture of your requirements for the next term.

Constitute the stakeholder team. The four roles relevant to renewal are actively engaged in Phase 2: Contract Manager, Procurement, Controlling, and Executive. Each role brings a specific perspective whose absence creates decision gaps in later phases. Assembling the stakeholder team only in Phase 3 or 4 loses lead time.

Define three scenarios. Not every renewal requires full renegotiation. A clear view of three core scenarios sharpens internal discussion: status-quo renewal without changes, volume or component adjustment based on usage data, or full renegotiation with revised contract parameters. Each scenario has different implications for timeline, budget, and resource commitment.

Determine projection requirements. What usage volumes are planned for the next term follows from comparing actual consumption against planned changes: new modules, changed user populations, planned BTP expansions, AI Unit requirements. This projection is the basis for all subsequent budget scenarios.

Obtain external assessment. Where internal data or market knowledge is incomplete, Phase 2 is the right time for an independent review of your contract position.

The output of Phase 2 is an internally aligned decision framework: which scenario is being pursued, which parameters are negotiable, and what budget range has been approved.

Phase 3 (M-9 to M-6): Clause Review and Negotiation Preparation

Phase 3 translates the data foundation and scenarios into a concrete negotiating position. The objective is a complete assessment of critical clauses in the current contract and a documented starting point for the conversation with SAP.

Identify critical clauses. The price adjustment clause, auto-renewal clause, SLA structure, exit rights, divestiture clause, and subscription flexibility are all assessed in the current contract. These six clause areas determine whether the next contract will be governable. Section 5 of this framework covers them in detail.

Structure BTP usage data. The BTP data prepared in Phase 1 is formatted as structured input for the renewal negotiation: a time series covering 12 to 18 months, project attribution, cost center structure, credit volume calibration for the new term.

Open discussions with SAP. Proactive contact with the SAP renewal team, before SAP takes the initiative, sends a different signal than reactive waiting. The party that sets the timing of the conversation shapes the frame of the renewal dialog.

The output of Phase 3 is a complete negotiating position: clause delta between current and target contract, structured data foundation, and an initial conversation record with SAP.

Phase 4 (M-6 to M-0): Negotiation, Closing, Transition

Phase 4 is the execution phase. The groundwork was laid in the previous phases. Now you negotiate, decide, and close.

Negotiate from a prepared data foundation. Negotiation is led from the data assembled in Phases 1 through 3: usage analysis, clause delta, budget scenarios. The Executive releases the negotiation mandate in this phase.

Auto-renewal termination as a tactical option. Formal termination in response to a price increase notification is a contractually provided right (SAP standard, Schedule 5). It can be used as a signal in the negotiation process without any actual intent to end the contract relationship.

Respect lock-out periods. No new Managed Service or Software subscriptions can be added in the last six months before contract end. No new CAS units are possible in the last twelve months. Any required component adjustments must be completed before these deadlines.

Establish transition governance. What runs under the old contract through the end of its term, and what starts under the new contract? This question needs to be answered before signing, not after.

The output of Phase 4 is the signed new contract with documented transition governance for the opening phase of the new term.

---

Building the Data Foundation: What Counts and What Doesn't {#building-the-data-foundation-what-counts-and-what-doesnt}

Negotiating position is not a negotiating technique. It is a function of your data. Four data categories determine how solid your position is in a renewal conversation. With all four complete, you can answer any question about volume, pricing, or clauses with facts. Without them, you lose governance moments because you are reacting to SAP statements instead of contributing your own.

Usage Data: Actual Consumption

FUE utilization by user type is the most important usage metric. Advanced Use users (1 FUE per user), Core Use users (1 FUE for 5 users), and Self-Service Use users (1 FUE for 30 users) have different value contributions per unit of credit deployed. Knowing actual utilization by user type lets you plan FUE allocation for the next term on solid ground.

BTP credit consumption by subaccount and project gives you the granular picture of cloud platform usage. Which BTP services are in productive use, which are test and development environments, and how has consumption volume developed over the past 12 to 18 months?

Cloud Managed Services usage versus purchased volume shows whether the infrastructure components of the RISE package match actual operating needs. Infrastructure overcapacity is not an uncommon finding, particularly when sizing was based on an initial state before the full user population was active.

CAS package usage: the comparison of paid CAS volume against services actually drawn down is a frequently neglected governance metric. CAS packages have a minimum term of twelve months and cannot be newly booked in the last twelve months before contract end.

Contract Data: What Is Agreed

Schedule 5 as the pricing reference: the unit prices, tiered thresholds, and minimums for all components fixed at contract signing. This price lock applies for the full term, but for Cloud Managed Services only for the initial subscription. A re-subscription after decommissioning is priced at current rates.

Credit development by contract year from monthly Balance Statements. With complete Balance Statements for the past 12 to 18 months, you can trace credit development and project the remaining balance at contract end.

Subscription minimum terms and lock-out periods. Which components still have active minimum terms? Which lock-out periods apply in the final months before contract end? This information is essential for planning component adjustments.

Special agreements in the Order Form. Amendments, Transformation Incentive agreements, and specific special terms. These documents take precedence over the standard Schedules and are often where meaningful concessions from the original negotiation were captured.

Market Data: What Is Publicly Available

Publicly available market data from DSAG reports, Gartner and Forrester analyst notes, and specialized sources such as saprisenegotiations.com and redresscompliance.com supplements your own usage data. It is not a secret weapon, but it provides context: how does your situation compare to industry benchmarks?

Across product types: for organizations with an SAP product portfolio beyond RISE, including SuccessFactors, Ariba, or IBP, publicly available information on those products provides additional orientation.

The Transition Option and its timeline as a reference point: the Transition Option for on-premises customers after 2030 has been publicly communicated at a 20 percent premium over comparable SAP ERP Private Edition, with a service start window between 2028 and 2030 (source: SAP Help Portal). This is a factual reference point for conversations about contract continuity.

Quality Data: What SAP Has Delivered

SLA compliance for the past 12 to 18 months: how often was the agreed availability met? Were there deviations, and were SLA credits claimed? Schedule B defines P1 response and correction times; Schedule D defines the SLA credit mechanics (maximum 0.25 percent per quarter, maximum five percent cumulative, as credits only).

Ticket volume and service request turnaround times: SAP does not contractually guarantee SLA coverage for service requests. That is a known element of the RISE operating model. Documenting your own observations gives you a factual basis for conversations about service quality.

Unresolved escalations: as a factual record, not a list of complaints. The structured presentation of open items from the current contract term is a legitimate input to the renewal negotiation.

---

BTP Usage Data as Negotiation Input {#btp-usage-data-as-negotiation-input}

BTP credits are part of every RISE contract. They are rarely prepared systematically as negotiation input, however. Yet they provide the most direct evidence of actual cloud usage below the FUE level: granular, time-stamped, and attributable to projects.

What BTP Credit Data Shows and What It Doesn't

BTP credit consumption differs by service family. Depreciation Group 1 (BTP core services) and Depreciation Group 2 (more expensive specialized services) carry different credit weightings. This distinction matters when projecting a consumption profile for the next term.

AI Unit consumption is a separate data stream. PUPM-based usage (Per User Per Month) and AI Unit allocations from the RISE bundle are separate consumption pools that cannot be offset against each other. Organizations using AI Units within their RISE contract need to pull consumption data from their own BTP reporting.

Unused credits are not a problem. They are evidence of an overallocation that can be corrected in the next term planning. This is a factual observation, not a value judgment.

What BTP credit data does not show: it provides no direct EUR equivalent of usage, because the individual price per credit is set in the Order Form. For budgeting purposes, the comparison with the contractually fixed credit price is required.

How BTP Data Feeds into the Renewal Data Foundation

A time series covering 12 to 18 months is the minimum requirement for a reliable BTP-level renewal data foundation. Shorter series do not capture seasonal variation and lead to unreliable projections.

Project attribution: which BTP usage represents productive operations, and which represents test and development environments? This distinction matters because development activity cannot be used as evidence of productive scaling requirements.

Cost center attribution as the basis for internal reporting: organizations that can attribute BTP usage to cost centers can close out internal reporting for the prior term and build a grounded projection for the new one.

What BTP Data Means for the Next Contract

Credit volume calibration: a realistic annual volume for the next term can be derived from the 12-to-18-month time series. Planned expansion projects, new integrations, and any AI Unit scaling should be added as an increment.

AI Unit demand planning: if an expansion of Business AI usage is planned, for example the move from embedded Copilot features to agentic deployments, this demand needs to be quantified early. Agentic deployments can consume three to twenty times the AI Units of a pure Copilot projection. Underestimating this factor leads to unexpected overages.

Quantify overage risk: how much BTP credit volume will likely be needed in the next term? Organizations that can estimate this reliably can negotiate volume with specific numbers rather than accepting SAP's generic sizing proposals.

BTP Data Governance Before Renewal

Monthly Balance Statement review as a mandatory process: the Balance Statement is the only reliable source for the current credit position and the only basis for a consistent time series.

Subaccount structure as a reporting foundation: organizations that operate BTP usage within a structured subaccount hierarchy can analyze consumption by project, business unit, or environment. This granularity is not achievable with a flat subaccount structure.

Who in your organization can reliably provide BTP data: answering this question before renewal preparation begins saves time. In many organizations, BTP operational data sits with the architecture or platform team, not the Contract Manager. The renewal process requires coordinated data delivery across multiple functions.

For further detail: SP-2 (BTP Usage Data as Negotiation Input) covers this topic in depth.

---

Critical Clauses: What the Next Contract Must Include {#critical-clauses-what-the-next-contract-must-include}

Not all clauses in a RISE contract carry equal weight for ongoing governance. Six clause areas determine whether the next contract will be governable, or whether actionable options will only become visible after the fact. These six areas should be fully assessed in every clause review before renewal.

Price Adjustment Clause (CPI Mechanism)

How SAP may announce price increases at renewal is governed by Schedule 5 of the RISE Enterprise Agreement. The publicly communicated framework allows a maximum increase of 3.3 percent per renewal period, with a 45-day advance notice requirement before the renewal start date (source: Schedule 5, SAP contract framework). If the notification is late, the increase applies only to the period after next.

The customer has the right to terminate for convenience in response to a notified price increase. This right is part of the SAP standard and exists regardless of whether an increase actually occurs.

What can be negotiated in this clause area relates to the formulation and cap on the adjustment mechanism: absolute or percentage limits, reference index, and adjustment period. An interaction exists with the credit reduction mechanism: SAP standard terms allow for a discount adjustment when credit volume is reduced.

Auto-Renewal Clause

The auto-renewal clause governs the conditions under which the contract renews and the applicable deadlines. The relevant elements: renewal period, notice period, pricing at renewal. The exact terms are contract-specific and can be found in the Order Form or the referenced Schedules.

What this clause means for governance: without an active decision, renewal takes effect. This requires an actively managed deadline calendar with at least three months' lead time before the critical decision point.

SLA Structure and Scope

The SLA in the RISE contract (Schedule B) defines system availability, typically 99.7 percent in the standard tier. Enhanced Operations (Schedule 3) for larger enterprises provides 99.95 percent. What the SLA measures is the system's ability to accept logons, not response times, batch windows, or service request quality.

Key scope limitations: Cloud Features run on separate infrastructure and are not covered by the main system SLA. Service requests carry no contractually guaranteed response times. Overage periods are explicitly excluded from SLA coverage.

SLA credits are in practice symbolic: a maximum of 0.25 percent of the annual amount per quarter, cumulatively capped at five percent, issued as credits only, claimable within one month after quarter end, in writing (Schedule D). Performance governance therefore needs to happen operationally, not through SLA credits.

Exit Clauses and Data Portability

What happens to data at contract end is governed by Schedule C (DPA). The DPA sets out data protection provisions for the post-contract period but does not include automatic portability guarantees in customer-selected formats.

What should be actively negotiated: data portability in standardized formats, access periods after contract end, and cost allocation for SAP-side export services. These questions should not arise for the first time when contract end is imminent.

Divestiture Clause

The standard divestiture provision in the RISE contract allows for a maximum twelve-month transition use, with two weeks' advance notice. Third-party cloud services are explicitly excluded from this provision.

For organizations with active M&A activity or corporate restructuring, the exact terms of this clause are material. What applies in the event of a carve-out, spin-off, or sale of a business unit that uses RISE is contract-specific in its detail.

Subscription Flexibility

Minimum terms by component determine when decommissioning is possible: Cloud Managed Services six months, Cloud Software six months, CAS packages twelve months. Third-party software is generally not decommissionable, a mechanism that is frequently underestimated during initial contract structuring.

Lock-out periods for new subscriptions in the final months before contract end restrict your options: no new Managed Service or Software subscriptions in the last six months, no new CAS units in the last twelve months.

---

CPI Clauses and Price Adjustment Mechanisms {#cpi-clauses-and-price-adjustment-mechanisms}

CPI clauses (Consumer Price Index) in SAP contracts govern how and to what extent price adjustments are permissible at renewal. How the mechanism is drafted influences your room to maneuver in the renewal conversation and in the subsequent contract cycle.

What CPI Clauses Govern in SAP Contracts

In the RISE Enterprise Agreement, a distinction needs to be drawn between the contractual CPI binding in the strict sense and SAP's ability to announce price increases at renewal. Both address the same question but follow different logic.

The notification obligation under Schedule 5 is a well-defined procedure: SAP must announce any intended increase at least 45 days before the renewal start date. If the notification is not timely, it applies only to the period after next. This deadline logic is relevant for your deadline calendar.

What Is Publicly Known (Schedule 5)

Schedule 5 of the RISE Enterprise Agreement is the publicly accessible contract framework documenting price adjustment rules. The maximum increase per renewal period is 3.3 percent. The 45-day notification obligation is also specified there. The customer's right to terminate upon a notified increase is SAP standard.

What Needs to Be Clarified in Contract Design

The formulation of the adjustment mechanism in the individual contract determines the available room to maneuver. Relevant considerations: is the cap absolute or percentage-based? Which CPI index serves as the reference, over what period is it measured, and what is the calculation base? A clause tied to a particular index can behave differently in a high-inflation environment than in a stable one.

An interaction exists with the credit reduction mechanism: SAP standard terms allow for a discount adjustment when credit volume is reduced. Organizations that want to reduce volume in the next term should keep this interaction in view.

Interaction with Other Mechanisms

The combined effect of a CPI increase and a price increase from credit reduction is a structural risk that should be addressed in the scenario analysis in Phase 2. Both mechanisms can occur simultaneously. Their additive impact should be quantified before the renewal conversation begins.

Tier pricing (Schedule 5) is relevant when volumes are adjusted across tier thresholds: a volume reduction into a lower tier can increase the unit price even without a CPI adjustment. Organizations that want to reduce volume should analyze the tier price structure in advance.

At renewal of an existing contract, different price stability conditions apply than for a new contract. This distinction is relevant if the renewal process is moving toward a full renegotiation scenario.

---

Self-Reporting Obligations and Overage Governance Before Renewal {#self-reporting-obligations-and-overage-governance-before-renewal}

In the RISE Enterprise Agreement, the obligation to report overuse lies with the customer. This obligation exists regardless of whether SAP is aware of the overuse. Organizations that do not manage this systematically risk unresolved open items in a window that should be used for renewal preparation.

What the Self-Reporting Obligation Means

The customer is required to report overuse to SAP before it occurs, not after it is identified. SAP has no automatic obligation to notify the customer when usage exceeds the agreed credit balance.

The consequences of overuse are contractually defined: consumption above the credit balance is invoiced at a 15 percent premium on the standard usage fee. For the overuse period, no SLA guarantee applies. Invoicing occurs monthly in arrears, meaning overages only become visible on the next invoice.

What Overage Governance Should Look Like Before Renewal

Monthly Balance Statement review as a mandatory process: the Balance Statement is the primary governance tool for the credit position. Reviewing it monthly allows you to identify deviations from the consumption plan early.

Threshold definition: at what credit balance is an internal escalation triggered? A clear threshold, for example 20 percent remaining credit against the annual plan, creates a structured escalation path.

Internal escalation path: who decides between adding a subscription and accepting overage? This decision belongs in a defined process with clear ownership, not in ad-hoc conversations.

Why Overage Governance Matters Particularly Before Renewal

Unresolved overage items in the 12 months before contract end weaken your position in the renewal conversation. Bringing open claims or unresolved billing questions into a renewal negotiation means resolving them in parallel, which consumes resources and attention.

Clean accounting across the full contract term, with complete Balance Statements, documented overage decisions, and a traceable consumption path, is a strength, not a given.

Self-Reporting and FUE Metering in Context

Since 2025, SAP has introduced increasingly automated FUE usage measurement through PCE Metering (Private Cloud Edition Metering). This measurement runs in parallel with the customer's own metering.

Your own metering as a control instrument: organizations that regularly determine their own FUE utilization are able to validate SAP-side measurement results. Where SAP measurement and self-assessment diverge, a structured reconciliation process built on documented data is required.

---

Stakeholder Model: Who Needs to Be Involved and When {#stakeholder-model-who-needs-to-be-involved-and-when}

Renewal preparation is a cross-functional task. The four roles that an SAP contract governance model requires are all needed simultaneously at renewal, and each has a different time horizon. When a role is engaged too late, decision gaps emerge that become visible in the renewal conversation.

Contract Manager

The Contract Manager owns the deadline overview, clause review, and contract documentation. This role enters the renewal process earliest.

From M-18: refresh contract documentation. Review the Order Form, all Schedules, and Amendments for completeness and currency. Establish and document the renewal calendar deadlines. Validate Schedule 5 as the pricing reference.

Core task at M-9: define the clause delta between the current and target contract. Which clauses meet the requirements of the next term, and which should be revised? This task is the central output of the clause review in Phase 3.

The Contract Manager also ensures that all deadlines in the renewal calendar are actively managed: the auto-renewal decision, notice periods, and subscription lock-out periods.

Procurement

Procurement owns the negotiation leadership and the budget mandate for the new term. This role does not engage at the outset but needs sufficient lead time to build a solid negotiating position.

From M-12: scenario analysis and budget planning. Based on the usage data from Phase 1 and the scenarios from Phase 2, Procurement builds the budget ranges for the three renewal scenarios.

Core task at M-6: lead the negotiation with SAP. Procurement conducts the renewal conversation with a complete data foundation, a defined negotiation mandate, and Executive approval.

Controlling

Controlling owns cost allocation, budget planning, and forecasting for the new term. The connection to the data foundation is especially close for Controlling: without the usage analysis from Phase 1, Controlling cannot develop reliable budget scenarios.

From M-12: usage analysis and internal allocation for the prior period. Which business units consumed which SAP services to what extent? This question is relevant both for closing out the current period and for projecting the next one.

Core task at M-9: build budget scenarios for the new term. The three renewal scenarios must be translated into budget figures before the Executive can make an informed decision.

Executive

The Executive makes the strategic decision: extension, volume adjustment, or realignment? And releases the negotiation mandate.

From M-12: review scenarios and set the decision framework. The Executive does not need detailed depth at this point, but does need a clear overview of the three scenarios and their budget implications.

Core task at M-6: release the negotiation mandate and sign the final contract. The decision on the room to maneuver that Procurement has in the negotiation must be approved before the first formal renewal meeting with SAP.

What Happens When Roles Are Missing

Without the Contract Manager: clause risks and missed deadlines surface late, often when the window for action has already closed.

Without Procurement: the negotiation proceeds without an adequate budget mandate, which limits your options.

Without Controlling: usage data is not prepared, and budget scenarios are based on estimates rather than validated figures.

Without the Executive: decisions about the negotiation mandate are delayed, which introduces time pressure into the negotiation phase.

---

Auto-Renewal: Deadlines, Risks, and Options {#auto-renewal-deadlines-risks-and-options}

Auto-renewal in the RISE Enterprise Agreement is a structural deadline, not a formality. What happens if it is missed is contractually clear. What tactical options are available depends on how early the governance moment is used.

How Auto-Renewal Works in the RISE Contract

The RISE contract renews automatically without active termination. The renewal period typically matches the original contract term, unless the Order Form specifies otherwise.

Pricing at renewal: SAP may increase the price for the new period but must announce the increase at least 45 days before the renewal start date. If the announcement is late, the increase applies only to the period after next.

The Critical Deadlines

The 45-day notification window for price increases is documented in Schedule 5. It is the earliest point at which customers learn whether SAP intends an increase.

The notice period is contract-specific and typically three months. It can be found in the Order Form or the referenced Schedules, not determined generically. Reviewing your own Order Form is essential.

The combination of the notice period and the 45-day window defines the earliest and latest governance moment: organizations that want to keep the termination option open must have decided by the notice period deadline at the latest. Those that want to respond to a price increase notification have 45 days from the notification.

What Happens If the Deadline Is Missed

The contract renews under the announced or current terms. Renegotiation without a new opening of the negotiation framework is not possible. The binding period extends at minimum over the renewal term. This situation is reversible, but only at significant effort.

Auto-Renewal as a Tactical Option

Active non-termination as a deliberate signal: waiving termination even when you theoretically have the right signals continuity. That waiver should be a deliberate decision, not an omission.

Formal termination upon a notified price increase as an option: the customer's right to terminate in response to a price increase notification is part of the SAP standard. This right can be exercised without any intent to end the contract relationship, if it is used as a tactical signal within a simultaneously running renegotiation process.

Parallel track: termination filed and renegotiation opened at the same time. This approach requires full clarity on your own risk if the renegotiation fails.

How Deadline Management Should Be Organized

A deadline calendar with at least three months' lead time before each critical decision point is the minimum system. Ownership of maintenance and escalation should be clearly assigned, typically to the Contract Manager.

The reminder system needs at least two escalation levels: an operational reminder three months before the deadline and a strategic escalation to the Executive four to five months before the deadline.

Documentation of termination, if filed: written form, proof of dispatch, receipt confirmation. This documentation is relevant if deadlines or delivery times are later called into question.

For further detail: Pillar 1 SP-1 (Auto-Renewal Deadline Overview) covers this topic in depth.

---

Exit Rights: What Should Be Negotiated {#exit-rights-what-should-be-negotiated}

Exit clauses are not absent from SAP contracts because they are fundamentally unavailable. They are absent because they were not systematically addressed during the negotiation phase. Renewal is the best time to close that gap. After the fact, meaning outside a renewal or amendment, additions are structurally more difficult.

What Exit Rights Cover in a SAP RISE Contract

Termination for convenience: notice periods, conditions, and consequences. What happens to credits, active subscriptions, and outstanding CAS packages?

Termination for cause: which circumstances entitle a party to terminate for cause? Material breach by the counterparty is addressed in most SAP contracts, but the exact definition and procedure are contract-specific.

Data portability at contract end: in what format can data be exported, what access window applies after contract end, and who bears the cost of SAP-side export services?

What the Standard RISE Contract Contains

Schedule C (DPA) governs data protection aspects for the post-contract period, but not portability details in the desired format or cost-free export windows. The DPA is a necessary foundation but not sufficient for complete exit governance.

The divestiture clause provides for twelve months of transition use in the event of a business divestiture, with two weeks' advance notice. Third-party cloud services are explicitly excluded.

No automatic right to extended data retention after contract end: what happens to data after contract end is governed by the standard, but not necessarily in the format needed for a migration or vendor transition process.

What Should Be Actively Negotiated

Data portability in standardized formats: SAP offers export functions. The formats, level of granularity, and costs should be contractually defined before a need arises.

Transition periods after contract end: how long does read access to production data remain available after the contract relationship ends? For migration projects, an adequate transition window is essential.

Definition of customer ownership for migration purposes: which data and configurations are unambiguously customer property, and what constitutes SAP-owned service content?

Cost allocation: who pays for SAP-side export services? Without a contractual provision, SAP's standard price list applies, which treats export services as a billable item.

Vendor Lock-In and Exit Strategy in Context

What runs on the HANA runtime is tied to the SAP infrastructure. What runs on BTP as custom development may, depending on the technology stack, also be operable outside the SAP infrastructure. This distinction is relevant for an exit strategy.

The S/4HANA Compatibility Pack is time-limited: usage rights through December 31, 2030 (and earlier if the subscription ends sooner). For organizations still running ERP code in Compatibility Pack mode, this deadline is a hard planning constraint.

Exit Rights and Renewal Negotiation

Negotiating exit options at renewal strengthens your position for all subsequent renewals. A clear picture of your own exit options increases your negotiating position regardless of whether those options are ever exercised.

Demonstrated exit readiness as a factual signal in the negotiation: organizations that have documented which exit options exist and what a migration would look like technically and commercially demonstrate that their decision for continuity is an informed choice, not a forced one.

For further detail: SP-3 (Negotiating Exit Rights in SAP Contracts) covers this topic in depth. Also relevant: Pillar 8 (Managing SAP as a Strategic Vendor).

---

How-To: Renewal Readiness in 10 Steps {#how-to-renewal-readiness-in-10-steps}

The following ten steps are in chronological order, each assigned to a point in time before contract end. They reflect the four phases of the renewal timeline in operational form.

Step 1 (M-18): Anchor the renewal date and auto-renewal deadline in the company calendar. The starting point is not the contract signing. It is a structured calendar entry. Renewal date, notice period, the 45-day window, and lock-out periods are documented as separate entries with clearly named owners for each deadline.

Step 2 (M-18): Update all contract documents. Order Form, all Schedules, all Amendments. The complete contract record is reviewed for completeness and currency. Missing documents are requested from SAP. The Balance Statement record is assembled for the past 18 months.

Step 3 (M-15): Prepare usage data for the past 12 months. FUE utilization by user type, BTP credit consumption by subaccount, CAS usage against booked volume, Balance Statement time series. This preparation is the foundation for all subsequent steps. It cannot be caught up in four weeks if it has not been maintained for 18 months.

Step 4 (M-12): Identify usage gaps and underutilization. Based on the usage data: where does actual consumption fall below purchased volume? Which components are not being used to the extent planned at contract signing? This finding is the basis for the scenario analysis.

Step 5 (M-12): Constitute the stakeholder team. Contract Manager, Procurement, Controlling, and Executive are formally brought into the renewal process. Responsibilities by role are documented in writing. A communication cadence for renewal preparation is established.

Step 6 (M-9): Assess critical clauses in the current contract. Price adjustment clause, auto-renewal clause, SLA structure and scope, exit clauses and data portability, divestiture clause, subscription flexibility. For each of the six areas, document what the current contract says and what should be different for the next term.

Step 7 (M-9): Define three scenarios. Scenario 1: status-quo renewal, extension on substantially unchanged terms. Scenario 2: volume or component adjustment based on usage analysis. Scenario 3: full renegotiation with revised contract parameters. Each scenario is assessed for budget implications and time commitment.

Step 8 (M-6): Proactively open the negotiation conversation with SAP. No reactive waiting for SAP to reach out. The party that initiates the conversation sets the initial framing. The opening of the conversation is based on the data from Steps 3 and 4 and the clause assessment from Step 6.

Step 9 (M-3): Make the auto-renewal decision. File termination or consciously let it run. This decision is now made with all relevant information: negotiation status with SAP, budget approval from the Executive, deadline calendar. It should not be made under time pressure because preparation steps were not completed on time.

Step 10 (M-2): Sign the contract and establish transition governance. The new contract is signed. Transition governance for the new term is documented: what runs under the old contract through when, and what starts under the new one? Credit transition planning, new subscription start dates, updated deadline calendar for the new term.

---

FAQ {#faq}

1. When should I start renewal preparation, and why 12 to 18 months?

Structured preparation begins no later than 18 months before contract end. The reason: the data foundation required for a well-grounded negotiating position cannot be built quickly. Usage time series covering 12 to 18 months, complete contract documentation, stakeholder alignment, and clause review all require lead time. In addition, SAP typically begins the renewal dialog on its side 12 to 18 months before the term ends. Starting later means meeting a counterparty that is already fully prepared.

2. What happens if I miss the auto-renewal termination deadline for RISE?

The contract renews automatically at term end, typically for the original contract duration. SAP may increase the price for the new period, provided the increase was announced at least 45 days before the renewal start date. Renegotiation without a new opening is not possible. The customer's right to terminate remains available even after renewal, provided SAP announces a price increase.

3. What data do I need for a well-grounded negotiating position?

Four data categories: usage data (FUE utilization by user type, BTP credit history, CAS consumption), contract data (Schedule 5, Balance Statements, special agreements), market data (public DSAG reports, specialized sources), and quality data (SLA compliance, ticket volumes, unresolved escalations). With all four categories complete, you can answer any question about volume, pricing, or clauses with facts.

4. What is the 45-day price increase notification period and what follows from it?

SAP must announce any intended price increase for the renewal period at least 45 days before the renewal start date (Schedule 5). If the notification is late, the increase applies only to the period after next. The customer has the right to terminate for convenience upon receipt of the notification. This window is a structured governance moment: those who know it can position proactively.

5. Can I reduce scope or cancel components at renewal?

Yes, subject to the contractually defined restrictions. Cloud Managed Services and Cloud Software have a minimum term of six months; CAS packages, twelve months. No new Managed Service or Software subscriptions can be added in the last six months before contract end, and no new CAS units in the last twelve months. Third-party software is generally not decommissionable. Volume adjustments must be completed before the applicable lock-out periods.

6. What are CPI clauses in SAP contracts and how do they affect renewal costs?

CPI clauses govern the extent to which price adjustments are permissible at renewal. The publicly communicated framework in Schedule 5 allows a maximum increase of 3.3 percent per renewal period. The specific clause language in the individual contract, including the reference index, calculation period, and cap formulation, determines the actual adjustment room. An interaction exists with the credit reduction mechanism: SAP standard terms allow for a discount adjustment when volume is reduced.

7. What happens to unused credit at the end of the contract term?

Remaining credit at the end of the contract term expires entirely. The degressive roll-over mechanism allows a portion of credit to be carried forward in prior years (30 percent in year one, 20 percent in year two, 10 percent from year three onward), but roll-over is excluded in the final year. This mechanic is a structural reason why credit planning must begin in the penultimate contract year, not the final one.

8. Which stakeholders need to be involved in renewal preparation?

The four roles of the SAP contract governance model: Contract Manager (from M-18, deadline owner and clause review), Procurement (from M-12, negotiation leadership and budget mandate), Controlling (from M-12, usage analysis and budget scenarios), and Executive (from M-12, strategic decision and release of the negotiation mandate). The stakeholder team should be formally constituted no later than Phase 2.

9. What are exit rights in an SAP contract, and how are they negotiated?

Exit rights govern the conditions for ending the contract, including notice periods, data portability, and cost allocation. The best time to negotiate them is at renewal: addressing exit options during renewal means they do not need to be introduced later through an amendment. Key items to negotiate actively include data portability in standardized formats, transition periods after contract end, and cost allocation for export services.

10. How do I use BTP usage data as a basis for the renewal negotiation?

BTP credit data provides the granular picture of cloud platform usage below the FUE level. A time series covering 12 to 18 months with project attribution and cost center structure is the minimum requirement. From this series, you can calibrate the credit volume for the next term, quantify overage risk, and project AI Unit demand if an expansion of Business AI usage is planned. BTP data is therefore directly actionable negotiation input, not just internal reporting.

---

Next Steps {#next-steps}

Start renewal preparation with structure. FinOptory's contract check delivers a complete picture of your SAP contract position in four weeks: usage data, clause assessment, data foundation for the renewal conversation. Fixed price: EUR 7,900. The contract check is the defined entry point. After four weeks, you know where you stand and which of the three renewal scenarios applies to your situation.

Use FinOptory AI. You can get a quick assessment of your renewal situation through the FinOptory AI chat at finoptory.ai. An initial overview of your contract structure and the relevant governance moments is available without any lead time.

Further reading. Pillar 1 (SAP Contract Governance Across the Full Portfolio) sets out the foundational framework for all SAP contract types. Pillar 8 (Managing SAP as a Strategic Vendor) deepens the perspective beyond the individual renewal. Both pillars are available through the FinOptory resources page.

---

Created 2026-05-21. Version v1, status: draft, released for Bernhard review. Source basis: SAP_RISE/02_vertragsstruktur_enterprise_agreement.md, SAP_RISE/04_rise_betrieb_und_governance.md, SAP_RISE/07_service_description_guide.md (all partner-visible). SAP_RISE/08_rise_negotiation_playbook.md was not used.