RISE Contract Clauses That Determine Your Commercial Outcome
- SAP's standard price escalation clause (3–5% annually) adds 16–28% to your total contract cost over a 5-year term compared to a fixed price — with no corresponding improvement in service.
- RISE SLA credits are typically capped at 10–15% of monthly fees. For a €5M/year contract, this means maximum compensation of €50,000 for a month of service disruption — immaterial to the business impact.
- SAP's unilateral right to modify service components with 90 days' notice applies to BTP services, managed services scope, and technology stack choices — changes you cannot veto without express contractual protection.
- Most RISE contracts include auto-renewal provisions with 12-month notice requirements — designed to make exit commercially difficult.
- Licence conversion terms (trading on-premise licences for RISE subscriptions) are consistently undervalued in SAP's initial proposals by 20–40%.
This article is part of our complete guide to RISE with SAP contract structure. If you haven't read that first, it provides essential context for understanding why these clauses matter and how they fit into the broader contract architecture.
The RISE contract negotiation mistakes enterprises make are not random. They are the predictable outcome of a process where SAP controls the timeline, the documentation, and the narrative. SAP's commercial teams are experienced, well-briefed, and incentivised to close deals on terms that maximise SAP's long-term revenue. The only counter to that is a structured, independent review of every clause that carries material commercial risk.
The 12 RISE Contract Clauses You Must Negotiate
Annual Price Escalation Mechanism
What SAP's standard terms say: Annual subscription fees increase by 3–5% per year, or by a reference index (CPI, HICP), whichever is higher. No cap.
The commercial impact: On a €5M annual RISE subscription, a 4% compounding escalator adds €1.08M to your total cost over 5 years compared to a fixed fee — with no corresponding improvement in service quality.
What to negotiate: Hard annual escalation cap of CPI + 1% or a fixed maximum of 2%, whichever is lower. Eliminate the "whichever is higher" construct. Include a mechanism to reduce fees if your user count decreases within defined bounds.
SLA Definition and Credit Structure
What SAP's standard terms say: 99.5% monthly uptime SLA. Credits for breaches capped at 10–15% of monthly fees. Downtime measured only after a 15-minute continuous outage threshold.
The commercial impact: 99.5% availability allows for 3.65 hours of downtime per month. For a global manufacturing business, 3 hours of ERP downtime can cost millions in lost production. The credit cap — say €50,000 on a €5M/year contract — is commercially irrelevant to the actual business impact.
What to negotiate: 99.9% availability for production systems; credit structure scaled to actual business impact rather than percentage of monthly fees; downtime measurement commencing at 5-minute threshold; explicit carve-outs for scheduled maintenance with minimum 72-hour advance notice.
SAP's SLA measurement methodology excludes downtime caused by "customer actions, third-party software, or force majeure." In practice, SAP regularly attributes service disruptions to customer-side factors. Negotiating clear definitions of what constitutes a SAP-caused outage versus a customer-caused outage is essential.
SAP's Unilateral Right to Modify Services
What SAP's standard terms say: SAP reserves the right to modify, replace, or discontinue specific services, technology components, or BTP services with 90 days' written notice. No consent required.
The commercial impact: SAP has exercised this right to consolidate BTP services, retire integration tools, and modify managed service tiers. If your implementation is built on a specific BTP service that SAP discontinues, remediation costs fall to you.
What to negotiate: Minimum 12-month notice for any service changes that affect your live production environment. SAP-funded remediation assistance if a service modification requires customer-side changes. Right to exit without penalty if SAP makes a modification that materially reduces service value.
BTP Credit Sizing and Minimum Commitments
What SAP's standard terms say: Minimum annual BTP consumption commitment included in RISE bundle. Credits expire at the end of each annual period. Overages charged at list price minus standard discount.
The commercial impact: SAP sizes BTP credit bundles based on "standard" consumption models that overestimate actual usage, particularly in years 1–3. Unused credits cannot be rolled over. This represents pure SAP revenue with no value delivered.
What to negotiate: BTP credit bundle sized to your actual consumption model (require SAP to provide a usage-based justification); 20% credit rollover between annual periods; overage pricing capped at a pre-agreed rate; right to reduce BTP commitment at annual review with 90 days' notice.
Licence Conversion Economics
What SAP's standard terms say: On-premise licences converted to RISE subscription credits at SAP's standard conversion rate (typically 1:1 on a face-value basis, subject to current pricing).
The commercial impact: SAP's standard conversion terms systematically undervalue on-premise licence estates. The residual commercial value of your on-premise licences — particularly if they include perpetual rights with ongoing maintenance — exceeds SAP's proposed conversion credit in most cases.
What to negotiate: Independent valuation of your on-premise licence estate before conversion; negotiated conversion credit that reflects actual residual value; retention of the right to use on-premise licences during a defined parallel-run period; explicit documentation of what rights are surrendered at conversion.
Migration Milestones and Liability
What SAP's standard terms say: SAP provides "professional services support" for migration. Timelines are "estimates." SAP's liability for migration delays is limited to the fees paid for professional services in the relevant period.
The commercial impact: RISE migrations routinely run 3–12 months over initial estimates. The business cost of delay — extended parallel running of legacy systems, consultant extension costs, delayed benefit realisation — typically exceeds SAP's professional services fees by a factor of 5–10x.
What to negotiate: Fixed migration milestones with defined SAP obligations at each phase; liquidated damages provision of 10–20% of annual subscription fee for each quarter of delay beyond a defined go-live date; clear definition of SAP's versus customer's responsibilities in the RACI matrix.
Need Help Negotiating These Clauses?
Our RISE advisory team has negotiated 80+ RISE contracts. We know exactly which clauses SAP will concede on — and which require a different strategy.
Auto-Renewal and Notice Period
What SAP's standard terms say: Contract auto-renews for a defined period (typically 1–3 years) unless written notice of non-renewal is provided at least 12 months before the contract end date.
The commercial impact: The 12-month notice window is buried in the T&Cs, rarely flagged by SAP, and routinely missed by customers. Missing the notice window locks you into an additional subscription term, often at an escalated price, without any opportunity to renegotiate.
What to negotiate: Reduce the notice window to 6 months; require SAP to proactively notify you of the notice deadline at least 18 months before it falls; eliminate auto-renewal and replace with a structured renewal negotiation process; negotiate the right to reduce scope at renewal without triggering a full reprice.
Data Portability and Exit Rights
What SAP's standard terms say: SAP will provide a data export in SAP's standard format within 30 days of contract termination. No assisted migration to alternative platforms. No guarantee of format compatibility.
The commercial impact: Without explicit data portability commitments, exit from RISE is commercially and technically very expensive. SAP's "standard format" for data export may not be directly usable by alternative platforms, requiring significant conversion investment.
What to negotiate: Data export in an industry-standard format (SQL, JSON, or agreed schema) within 30 days; SAP-assisted data migration support for a minimum of 90 days post-exit; right to request a test data export during the contract term to validate format; explicit confirmation that all customer IP, configurations, and customisations are included in the export.
Confidentiality and Benchmarking Rights
What SAP's standard terms say: Contract pricing is confidential. Customer may not share pricing with third parties without SAP's consent. No right to benchmark pricing against market comparators.
The commercial impact: SAP's confidentiality clause prevents you from sharing pricing with independent advisors or benchmarking services, limiting your ability to validate whether you are paying market rate. This clause is specifically designed to inhibit the kind of independent review that consistently reveals overpricing.
What to negotiate: Explicit right to share pricing with independent advisors under NDA; inclusion of a benchmarking clause allowing you to commission a market price comparison every 2 years; right to renegotiate pricing if benchmarking reveals a material variance from market rate.
Liability Cap and Indemnification
What SAP's standard terms say: SAP's total liability capped at fees paid in the 12 months preceding the claim. SAP indemnified against indirect, consequential, or loss-of-profit claims.
The commercial impact: For a €5M/year contract, SAP's liability is capped at €5M — immaterial relative to the business impact of a significant service failure, data breach, or migration disaster. SAP's exclusion of consequential loss eliminates the category of damage most relevant to enterprise buyers.
What to negotiate: Liability cap of 2x annual fees for material service failures; removal or limitation of consequential loss exclusion for data breaches, prolonged service outages, and migration failures; enhanced liability for security incidents involving customer data.
User Count Flexibility
What SAP's standard terms say: Minimum Named User commitment locked for the full contract term. Users can be added at the contracted per-user rate plus annual escalation. User count cannot be reduced below the contracted minimum.
The commercial impact: Enterprise workforces change. Restructuring, divestments, automation, and outsourcing regularly reduce SAP user requirements. A rigid user floor means you continue paying for licences that are no longer required — often for years after headcount changes.
What to negotiate: Annual review of user count with the right to reduce by up to 15% without penalty; "true-up" measurement at defined intervals rather than rigid floor commitments; user transfer rights in the event of corporate restructuring, M&A, or outsourcing.
Governance and Change Control
What SAP's standard terms say: Changes to service scope require a formal Change Request process. SAP has sole discretion on pricing for scope changes. No mechanism for customer-initiated scope reduction.
The commercial impact: SAP's change control process is designed to enable scope additions (at full price) while making scope reductions commercially unattractive. Any change to your RISE footprint — whether expanding or contracting — is processed through a mechanism that defaults to SAP's pricing advantage.
What to negotiate: Pre-agreed pricing for defined scope additions (additional modules, user types, BTP services); explicit right to reduce scope at defined checkpoints; independent dispute resolution mechanism for pricing disagreements; customer-controlled change request initiation with defined SAP response timelines.
How to Structure the RISE Negotiation Process
Understanding which clauses to negotiate is only half the challenge. The other half is structuring the negotiation to maximise your leverage. SAP's commercial teams are skilled at using urgency (end-of-quarter deadlines, 2027 ECC maintenance timelines) and complexity (multi-month negotiation processes) to wear down enterprise buyers and achieve signature before independent review is complete.
The most effective RISE contract negotiation follows a structured process: independent commercial analysis before any negotiation begins; a written counter-proposal addressing all material clauses before engaging SAP's commercial team; separation of the commercial discussion from the technical/implementation discussion; and a firm internal deadline that is communicated to SAP as the driver for signature, not SAP's fiscal calendar.
Our SAP contract negotiation service provides end-to-end support for this process — from initial contract review through to signature. We know which clauses SAP will concede on quickly, which require sustained pressure, and which require escalation to SAP's executive level to resolve.
For the commercial context behind SAP's pricing, see our RISE with SAP pricing model breakdown — which explains how SAP constructs proposals and where the negotiation room exists. And for a broader understanding of your RISE options, the RISE with SAP Guide provides the strategic framework.
Frequently Asked Questions
Related Reading
RISE with SAP Pricing Breakdown Series
Understanding the contract clauses is only half the picture. For a complete RISE pricing breakdown and negotiation framework:
- RISE with SAP Pricing Breakdown: Complete Enterprise Guide — component-level pricing decoded
- RISE Pricing Negotiation Strategies — four-phase framework including contract protection terms
- RISE Pricing Cost Optimisation Tactics — six levers that reduce total contract value
Related Reading
RISE with SAP SLA & RACI Series
Once you have negotiated the key clauses, you need enforceable SLA commitments and a clear RACI framework to hold SAP accountable post-signature:
- RISE with SAP SLA & RACI: Complete Enterprise Guide — full framework for SLA negotiation and RACI accountability
- Key Questions to Ask SAP on SLA & RACI — 20 due-diligence questions before you sign
- SLA & RACI Negotiation Strategies — six-step framework for enforceable commitments
- SLA & RACI Cost Optimisation Tactics — using accountability gaps as commercial levers
Related Reading
RISE with SAP Exit Strategy Series
Negotiating the right clauses upfront is how you protect your exit rights. For the complete exit strategy framework and cost reduction tactics:
- RISE with SAP Exit Strategy: Complete Enterprise Guide for 2026 — contractual traps, exit scenarios, and the full negotiation framework
- RISE Exit Negotiation Strategies — seven proven levers that shift exit terms in your favour
- RISE Exit Cost Optimisation Tactics — CFO-ready framework for capping the five cost categories
- Key Questions to Ask SAP About Exit — ten questions SAP hopes you never raise
SAP Licensing Experts is an independent advisory firm — not affiliated with, endorsed by, or partnered with SAP SE. SAP, RISE with SAP, S/4HANA, BTP are trademarks of SAP SE. Our advice is 100% buyer-side.