Why RISE Negotiations Require a Different Approach
RISE with SAP is not a software licence transaction. It is a multi-year subscription for software, cloud infrastructure, and managed services bundled into a single commercial relationship. The negotiation dynamics differ materially from a traditional ELA renewal or an on-premise licence agreement.
In a traditional SAP negotiation, the buyer controls the timing and scope. In a RISE negotiation, SAP's account team is managing multiple interdependent elements simultaneously: the software subscription value, the hyperscaler infrastructure commitment, the managed services scope, the migration timeline, and the indirect access settlement. Each element creates leverage opportunities — but only for buyers who understand the structure and have prepared accordingly.
SAP's fiscal year ends December 31. This creates a highly predictable leverage window in the October through December period, when account teams face intense pressure to close deals before year-end and are authorised to offer deeper discounts and additional concessions. Buyers who can credibly threaten to walk away from a Q4 deadline — because they have done their preparatory work and established a viable alternative — consistently extract better terms than those who arrive at the table underprepared in November.
Tactic 1: Establish Your Independent Pricing Benchmark
The single most impactful commercial decision in a RISE negotiation is establishing an independent benchmark before SAP presents its first offer. Benchmark data consistently shows that large enterprises achieve 30 to 50 percent discounts on RISE list pricing. The list price for an SAP S/4HANA Cloud Advanced user (1.0 FUE) is approximately $150 to $180 per user per month. Well-prepared buyers pay materially less.
Your benchmark should cover three dimensions. First, the per-FUE subscription rate at your expected contract volume and term. Second, the BTP credit rate for the additional BTP consumption you require beyond the standard bundle. Third, the infrastructure component, which SAP often prices opaquely within the RISE bundle and which has limited external comparators. Redress Compliance maintains current benchmark data across 80+ RISE negotiations and can validate whether SAP's commercial proposal falls within market range.
Presenting your own benchmark — factually, as a reference point — changes the commercial dynamic immediately. It signals preparation, it establishes a credible lower anchor, and it puts the burden on SAP to justify any premium over the market rate.
Tactic 2: Control the FUE Composition Analysis
RISE with SAP is priced using the Full Use Equivalent (FUE) metric. An Advanced user (full system access) counts as 1.0 FUE. A Core user (limited functional access) counts as 0.2 FUE. A Self-Service user counts as 0.05 FUE. The total subscription cost is driven by total FUE count multiplied by the per-FUE rate.
SAP's account team will propose an FUE composition based on your current named user count and their standard role-to-tier mapping. This mapping consistently favours Advanced user classification and overestimates total FUE requirements. An independent role analysis — mapping each user's actual transaction usage pattern against the S/4HANA user tier definitions — reliably identifies material over-classification. The difference between an SAP-proposed FUE mix and a buyer-validated FUE mix is often 20 to 35 percent of total annual subscription value.
Conduct this analysis before SAP presents its proposal. Present your validated FUE composition as the basis for commercial discussions. Require SAP to justify any deviation from your analysis with specific evidence. This tactic alone can reduce the subscription baseline by millions of dollars annually on large enterprise deals.
Tactic 3: Address Indirect Access Before It Becomes a Liability
Indirect access — the use of SAP data by third-party systems — is measured under SAP's Document-Driven Licensing Concept (DDLC). When a non-SAP system creates, reads, updates, or deletes a document in SAP (an order, an invoice, a goods movement, a production order), SAP can claim that the interaction requires a Digital Access licence. The DDLC metric is document-type specific and volume-dependent, and SAP's auditors are experienced at quantifying maximum exposure.
In a RISE contract, indirect access does not disappear. It transitions from the on-premise indirect access exposure to a Digital Access subscription line within the RISE agreement. The question is whether you define the scope and price that subscription proactively — before contract signature — or reactively, when SAP conducts a consumption review twelve to eighteen months into the contract.
The proactive approach requires completing a full integration mapping exercise before negotiation: identify every third-party system that interacts with SAP, document the document types involved, and estimate annual volumes. This mapping becomes your evidence base for sizing a Digital Access subscription that covers known integrations at a fixed contractual price. Agree in the contract that the defined scope of Digital Access is exhaustive — any additional claims require a contractual amendment, not a supplemental purchase order.
The reactive approach — where buyers accept undefined Digital Access scope in the RISE contract — typically results in SAP raising a supplemental charge claim within two years of go-live, often for millions of dollars, citing document volumes that were not explicitly excluded at contract signature.
Need support mapping DDLC exposure before your RISE negotiation?
We have defended 80+ indirect access disputes and RISE engagements.Tactic 4: Negotiate Annual Uplift Caps
SAP's standard RISE contracts include annual price escalation clauses. The default uplift mechanism is typically tied to a consumer price index or a fixed percentage, often in the range of three to five percent per year. Over a five-year contract, a three percent annual uplift compounding on a $5 million per year subscription adds approximately $800,000 in incremental cost. A five percent annual uplift adds approximately $1.4 million.
Negotiating a lower annual uplift cap — or a flat price freeze for the initial term — is one of the highest-ROI contract terms available in a RISE negotiation. Target a maximum annual increase of zero to two percent for the initial contract term. SAP will resist this, citing inflation and infrastructure cost growth, but precedent exists for zero-uplift initial terms on large strategic deals, particularly when the buyer is migrating a significant ECC estate to RISE and represents a material revenue commitment for SAP.
If SAP will not accept a zero-uplift clause, negotiate a fixed dollar cap on annual increase rather than a percentage-based cap. A fixed dollar cap on a large subscription protects proportionately more value as the subscription grows through add-ons and expansions.
Tactic 5: Use SAP's Fiscal Year Deadline as Leverage
SAP's fiscal year ends December 31. The Q4 window — particularly October and November — is when SAP account teams are most flexible on pricing and terms. This is not speculation; it is structural. SAP's internal approval processes allow larger discounts to be authorised more quickly in Q4 than in Q1 or Q2. Account teams are personally incentivised on full-year quota attainment.
To exploit this leverage window effectively, you must be ready to close in Q4 — not just negotiating. Readiness means your FUE analysis is complete, your DDLC mapping is done, your TCO model is built, your internal stakeholders are aligned, and your legal team has reviewed the contract. Buyers who are genuinely ready to sign by November 30 extract the best Q4 terms. Buyers who arrive unprepared in October and scramble through December give up much of the year-end benefit to their own internal delays.
It is also valid to signal credibly that you would be willing to delay to Q1 if terms are not acceptable. SAP's motivation to avoid losing a Q4 close to a Q1 drag into the next fiscal year makes this threat credible even if you prefer to close in Q4. The key is that the threat must be believable — which requires genuine readiness and a visible alternative.
Tactic 6: Negotiate BTP Credits at Contract Origination
Standard RISE subscriptions include a BTP starter entitlement that covers basic integration and extension scenarios. Organisations planning material BTP-based development, advanced analytics, or high-volume integration workloads will exhaust the included allocation and need to purchase additional BTP credits.
BTP credits purchased at contract origination — as part of the initial RISE deal — are typically negotiated at the same discount level as the core subscription. BTP credits purchased post-contract, when your leverage has dissipated and SAP knows you depend on the platform, are purchased closer to list price. The commercial implication is clear: identify your realistic BTP consumption requirements during the readiness phase and negotiate the full credit bundle upfront.
Additionally, push for flexibility in BTP credit consumption timing. Standard credits may have use-it-or-lose-it expiry terms. Negotiate roll-forward provisions that allow unused credits from one year to carry into the next, preventing the artificial pressure to consume BTP services in a given period to avoid credit forfeiture.
Tactic 7: Protect Exit Rights
RISE with SAP is a five to seven year commitment. Circumstances change — acquisitions, divestitures, technology strategy pivots, financial constraints. The default contract terms do not favour graceful exits. Data portability provisions are often vague, termination fees are structured to deter early exit, and the notice periods for non-renewal can be longer than buyers expect.
Before signing, negotiate three specific exit protections. First, documented data portability rights — the right to receive your SAP data in a standard, portable format (CSV, standard SAP export) within a defined timeframe at no additional cost. Second, capped early termination fees — if termination for cause is defined broadly, ensure the fee is proportional and capped as an absolute dollar amount. Third, defined non-renewal notice periods — ensure you know how far in advance of contract expiry you must notify SAP of non-renewal, and that this period is commercially reasonable (90 to 180 days, not 12 months).
Tactic 8: Require a Dual-Use Period During Migration
RISE migrations take 12 to 24 months for most enterprise deployments. During that period, you are running your existing ECC or S/4HANA environment in parallel with the RISE environment being built. SAP's default contract structure has historically required customers to pay both on-premise annual support (approximately 22 percent of net licence value) and the RISE subscription during the migration window.
Negotiate a dual-use provision that grants you access to both environments during the migration period without requiring double payment. Target a minimum six-month dual-use window. Large deals with long migration timelines should target 12 months. SAP has agreed to dual-use provisions on many strategic migrations; this is a negotiable term, not a fixed commercial reality.
Putting It Together: The Negotiation Sequence
Effective RISE negotiations follow a defined sequence. Begin with internal preparation: complete the readiness checklist, build the FUE model, map DDLC exposure, establish your TCO baseline, and align stakeholders on walk-away terms. Only then engage SAP's commercial team.
When SAP presents its first commercial proposal, do not respond with acceptance or a single counter. Respond with your FUE analysis, your benchmark data, and a specific request for SAP to explain any deviation. This immediately signals competence and shifts the burden of justification to SAP. From that foundation, negotiate each commercial element in sequence — subscription rate, FUE composition, uplift cap, Digital Access scope, BTP credits, dual-use period, and exit terms — rather than accepting a package offer.
If your organisation does not have the internal SAP licensing expertise to execute this sequence, our SAP commercial advisory specialists support buyer-side RISE negotiations with independent benchmarking, FUE modelling, DDLC mapping, and contract review. We work exclusively for buyers, never for SAP, and have supported over 80 RISE engagements across industries and geographies.