SAP's 2026 Standard Support maintenance fee rises 3.3 percent on average. Enterprise Support rises 4.0 to 5.0 percent. RISE and GROW cloud subscription rises 5 to 7 percent at renewal unless contractually capped. The increases apply to net license fee for on premise customers and per FUE subscription for cloud customers. For a $18M on premise SAP estate the 2026 increase adds $600K to $900K to annual maintenance cost. The increase compounds: a customer with no contractual price hold faces a 17 to 26 percent total fee increase across a five year window. This page documents the 2026 increase structure, the negotiation levers that cap or defer it, and the multi year price protection clauses that shield against compound increases.
The 2026 increase structure
SAP's annual maintenance fee increase is tied to a published consumer price index calculation, applied differently to Standard Support and Enterprise Support tiers, and applied separately to cloud subscription products.
| Fee category | 2025 to 2026 increase | Calculation basis |
|---|---|---|
| SAP Standard Support (19% of net license) | 3.3% on average | Tied to consumer price index in primary contract jurisdiction |
| SAP Enterprise Support (22% of net license) | 4.0 to 5.0% on average | CPI calculation plus enhanced scope premium |
| SAP Extended Maintenance (additional 2% surcharge) | Same as underlying tier plus surcharge applied to 2025 base | Compound effect: base rises with tier, surcharge applies on top |
| RISE Premium subscription | 5 to 7% at renewal | Per FUE rate increase, applied at term renewal |
| RISE Premium Plus subscription | 5 to 7% at renewal | Per FUE rate increase, applied at term renewal |
| GROW subscription | 4 to 6% at annual auto renew | Per FUE rate increase, applied at auto renew anniversary |
| BTP CPEA consumption rate | Varies by service, 0 to 8% | Service by service rate adjustment |
The published increase for on premise Standard Support of 3.3 percent is the headline number. The realised increase for individual customers ranges from 2.8 percent (favourable jurisdiction CPI) to 4.2 percent (less favourable jurisdiction CPI). Enterprise Support increases land higher because the enhanced scope premium applies on top of the base CPI calculation.
The compound effect over five years
Annual increases compound. A customer with no contractual price hold faces a multi year compounded increase that materially exceeds the headline annual figure. The five year compound effect at typical annual rates:
| Annual increase | 2 year compound | 3 year compound | 5 year compound |
|---|---|---|---|
| 3.3% Standard Support | 6.7% | 10.2% | 17.6% |
| 4.5% Enterprise Support | 9.2% | 14.1% | 24.6% |
| 6.0% RISE renewal | 12.4% | 19.1% | 33.8% |
| 7.0% RISE renewal aggressive | 14.5% | 22.5% | 40.3% |
A $18M Standard Support base compounds to $21.2M by year five at 3.3 percent annual. Enterprise Support compounds to $22.4M at 4.5 percent. The cumulative incremental cost over a five year window is $9.7M for Standard Support and $14.1M for Enterprise Support, against an unprotected starting position.
Compound effect rule: the most expensive sentence in a SAP contract is the one that says nothing about annual price increase. Customers who accept SAP's default contract face the full compounded increase. Customers who negotiate a multi year price hold cap the compound at 0 to 3 percent across the protected window.
Multi year price protection clauses
Five clause patterns cap or eliminate the annual increase. Each carries different commercial implications and is negotiated differently in cloud versus on premise contracts.
| Clause | Effect | Where applicable |
|---|---|---|
| Flat fee multi year hold | Maintenance or subscription fee held flat for 2 to 5 years | RISE, GROW, on premise Maintenance with multi year prepayment |
| Capped annual increase | Annual increase capped at a fixed percentage (typically 0 to 3%) | RISE renewal terms, on premise Enterprise Support |
| CPI capped at floor | CPI based increase capped at a stated floor (typically 2 to 3%) | On premise Standard Support and Enterprise Support |
| Maintenance prepayment | Multi year prepayment at current rate, locking the rate for the prepaid window | On premise Standard Support and Enterprise Support, typically 3 year prepayment |
| Renewal anchored to original rate | Term renewal anchored to original per FUE rate plus a defined CPI factor | RISE multi year extensions |
The most negotiated clause in 2026 RISE contracts is the capped annual increase, typically negotiated at 0 to 3 percent across the initial term. SAP's default RISE contract includes no annual cap, meaning the per FUE rate is subject to SAP's discretionary increase at each term renewal. The cap is the difference between a five year cost of $25.5M (uncapped, 6 percent compound) and $20.0M (capped at 2 percent compound) on a $4.5M per year starting subscription.
When to negotiate the cap
Multi year price protection is negotiable at contract signature and at renewal. The negotiation window matters: signing a new RISE contract gives the strongest commercial position for a capped annual increase because SAP is competing for the initial commitment. Renewal negotiation has lower flexibility because the customer is already on the platform.
For on premise customers, the negotiation window for Maintenance price protection opens at any time the customer is signing a new license purchase or evaluating Third Party Maintenance as an alternative. SAP's commercial team will accept a CPI capped at floor clause to retain Maintenance revenue against a credible Third Party Maintenance alternative. The framework for Third Party Maintenance evaluation is in Reduce SAP Maintenance.
ECC Extended Maintenance fee pattern
Customers staying on ECC under Extended Maintenance face a specific 2026 pricing pattern. The Extended Maintenance surcharge of 2 percent applies on top of the underlying Enterprise Support fee, which itself rises with the annual CPI calculation. The combined effect is meaningful:
| Year | Enterprise Support rate | Extended Maintenance surcharge | Total Maintenance rate |
|---|---|---|---|
| 2027 (Mainstream) | 22.0% | 0% | 22.0% |
| 2028 (Extended begins) | 22.9% (4% CPI) | 2% | 24.9% |
| 2029 (Extended) | 23.8% (4% CPI) | 2% | 25.8% |
| 2030 (Extended ends) | 24.8% (4% CPI) | 2% | 26.8% |
| 2031 (Customer Specific Maintenance) | 22 to 26% negotiated | Variable | Variable, no patch commitment |
Customers signing Extended Maintenance contracts in 2026 should negotiate the Extended Maintenance fee structure for the full window, locking the 2 percent surcharge and capping the underlying CPI increase. Recent SAP Extended Maintenance contracts have included language allowing SAP discretionary increases above the 2 percent surcharge, which materially shifts the multi year cost.
Conversion Credit as a price increase shield
Customers planning a S/4HANA conversion within the next 24 months can use the Conversion Credit timing as a shield against the 2026 increase. The mechanics:
- Defer the 2026 Maintenance increase by signing the conversion contract in 2026. The conversion to RISE or to on premise S/4HANA license terminates the historical ECC Maintenance, replacing it with a new subscription or new Maintenance term. The 2026 increase does not apply to the new contract.
- Apply Conversion Credit at maximum ratio. The conversion negotiation is the moment to push the Conversion Credit ratio from the published 50 to 70 percent toward the negotiated 80 to 95 percent. The detailed framework is in S/4HANA Conversion Credits.
- Negotiate the multi year price hold in the new contract. The new RISE or new on premise contract is the right vehicle to cap the annual increase at 0 to 3 percent for the initial term.
- Apply Maintenance prepayments as conversion offset. Multi year Maintenance prepayments on the historical ECC contract carry value at conversion, typically converting at 100 percent against future subscription or future Maintenance, but only when explicitly preserved.
The combined effect is to skip the 2026 increase entirely while improving the conversion economics. The strategy applies only to customers who are actually planning a conversion. Customers without a near term conversion plan cannot use this shield.
Benchmarking the increase
The first defence against an annual increase is benchmarking. SAP commercial teams quote the increase as a percentage of current fee without context. The defensible benchmarks:
- The published CPI for the contract jurisdiction. SAP's CPI calculation should match the published index in the customer's primary contract jurisdiction. Customers should verify the calculation explicitly.
- Comparable customer renewal data. Realised increases observed across comparable customer renewals provide a defensible reference range. Advisor led benchmarking surfaces 50 to 200 comparable renewals across industries and contract sizes.
- Third Party Maintenance alternative pricing. Rimini Street, Spinnaker, and other Third Party Maintenance providers publish indicative pricing 40 to 60 percent below SAP Standard Support. The alternative pricing is the floor for negotiation pressure.
- Multi year RISE renewal data. RISE renewals in 2025 and 2026 typically landed at 4 to 7 percent uncapped, 0 to 3 percent capped. The realised range is the benchmark for new RISE contracts.
2026 negotiation rule: the published annual increase is the starting position. The negotiated outcome depends on contract structure, multi year commitment, and credible alternative. Customers with no negotiation activity accept the full headline increase. Customers with active negotiation, multi year commitment, and Third Party Maintenance benchmark routinely cap at 0 to 3 percent.
2026 cost increase by SAP product family
The 2026 increase is not uniform across SAP product families. Some families face higher than headline increases, others lower. The product family breakdown observed across 2025 to 2026 SAP renewal data:
| SAP product family | 2026 increase observed | Notes |
|---|---|---|
| ECC Enterprise Support | 4.0 to 4.5% | Mainstream Maintenance final year, headline CPI applied |
| S/4HANA on premise Enterprise Support | 4.5 to 5.0% | SAP applying higher rate to drive RISE adoption |
| RISE Premium subscription | 5 to 7% at renewal | Uncapped contracts face full rate, capped contracts 0 to 3% |
| RISE Premium Plus subscription | 5 to 7% at renewal | Same pattern as Premium |
| GROW subscription | 4 to 6% at auto renew | Lower headline rate, smaller volume base |
| SuccessFactors HCM Suite | 5 to 8% | Above SAP average, reflecting SaaS premium |
| Ariba spend management | 3 to 6% | Per module variation, supplier side fees separate |
| Concur Travel and Expense | 4 to 7% | Per user and per transaction components both rising |
| BTP CPEA consumption rates | 0 to 8% | Service by service variation, some flat, some accelerated |
| SAP Analytics Cloud | 3 to 5% | Per user pricing, modest increase |
The highest increases land on cloud subscription products (RISE, SuccessFactors, Concur), where SAP has the most pricing power and the longest commercial commitment. On premise Maintenance increases are more modest in absolute terms but compound over a longer base contract.
Where to start
The 2026 increase is here. The defence is contract structure, not negotiation tactics in isolation. The first step is reviewing the current contract for existing cap language, multi year prepayment options, and CPI tie language. The second step is benchmarking the proposed increase against comparable renewals and Third Party Maintenance alternatives. The third step is negotiating capped annual increase, multi year hold, or Conversion Credit timing depending on the customer's strategic position.
For the broader SAP commercial framework see SAP Licensing Complete Guide and the SAP vendor intelligence hub. For Maintenance reduction options including Third Party Maintenance see Reduce SAP Maintenance. For Conversion Credit timing as a price shield see S/4HANA Conversion Credits. For active SAP commercial work see Software Licensing Advisory and Cloud Contract Negotiation. For the ECC deadline driving the 2026 to 2030 fee pattern see SAP ECC 2027 End of Life Strategy.