SAP will not move the 22% Enterprise Support rate if you argue about the rate. It will move the number if you change what the rate is applied to. The four levers that work are rebasing the license value before renewal, capping the annual uplift, freezing the support fee through an S/4HANA conversion, and holding a credible third-party support quote. Combined, they cut annual SAP support spend 20–40% in our engagements — and the saving recurs every year.
Yes — but almost never by negotiating the percentage itself. SAP treats the 22% Enterprise Support rate (19% for Standard) as policy and rarely discounts it directly. What is negotiable is everything the percentage interacts with: the license base it is calculated on, the index-linked annual uplift that compounds on top, the step-up that a conversion to S/4HANA would otherwise trigger, and the competitive pressure a third-party support quote applies. Move those and you move the bill — by 20–40% across the SAP support engagements we run.
The core insight: support fee = rate × license base × (1 + uplift)^years. The rate is fixed; the base, the uplift, and the conversion step-up are not. Attack the three movable terms, not the one fixed one.
This is a sub-guide in our SAP support strategy pillar. It pairs with SAP third-party support and the 2027 maintenance deadline, and sits under our SAP vendor practice and contract negotiation service.
Rebasing means lowering the net license value the support percentage is calculated on, by retiring or terminating licenses you no longer use before the renewal locks the base. Most SAP estates carry 15–30% shelfware — Named User licenses for departed employees, engine metrics over-provisioned at signing, modules that were never deployed. Each of those is paying 22% support every year for nothing. SAP will not volunteer to remove them; you must identify them, document non-use, and negotiate the termination as part of the renewal.
The mechanics matter: SAP generally resists partial terminations that simply reduce support, so rebasing is most achievable at a renewal, a conversion, or a contract restructuring — moments when the whole agreement is open. A usage audit feeding a documented shelfware schedule is the prerequisite, which is why this work starts 12–18 months out. See the broader optimization play in SAP license optimization.
| Shelfware source | Frequency | Typical share of base | Annual support waste (22%) |
|---|---|---|---|
| Named Users for leavers | ~90% | 8–15% | 1.8–3.3% of license base |
| Over-provisioned engine metrics | ~70% | 5–12% | 1.1–2.6% |
| Undeployed modules | ~50% | 3–8% | 0.7–1.8% |
| Mis-tiered user types | ~80% | 5–10% | 1.1–2.2% |
We run the usage audit and build the rebasing schedule SAP will accept — before the base hardens.
Because it compounds. SAP's standard support terms permit annual increases tied to a published price index, and left uncapped those increases stack year on year. A support fee rising 3% annually grows roughly 16% over five years; at the higher end of recent index movements it grows materially faster. A negotiated cap — or, in stronger positions, a multi-year freeze — is therefore often worth more over the contract life than a one-time discount, because it bends the entire curve rather than shifting a single point on it.
The cap is one of the most winnable concessions because it costs SAP nothing today and most buyers never ask for it. The chart of outcomes is stark: on a $5M annual support line, the difference between an uncapped index increase and a 0% freeze over five years runs into the millions.
| Uplift scenario | Year 1 | Year 5 | 5-yr total ($5M start) |
|---|---|---|---|
| Uncapped (~5%/yr) | $5.00M | $6.08M | $27.6M |
| Capped at 3%/yr | $5.00M | $5.63M | $26.5M |
| Capped at 0% (freeze) | $5.00M | $5.00M | $25.0M |
"The annual uplift is the quietest line in the SAP contract and the one that costs the most over time. Capping it is the concession SAP gives because nobody asks."
The rebasing checklist, the uplift-cap model, the conversion-freeze clause, and the full negotiation timeline — in one research paper.
When you convert from ECC to S/4HANA, SAP recalculates support on the new license construct — and that recalculation is frequently a step-up, because conversion credits rarely fully offset the new license value and Digital Access exposure is often crystallised at the same moment. The negotiable position is to freeze the support fee at its pre-conversion level for a defined period, so the migration does not double as a repricing event. SAP would prefer the conversion to reset support upward; a freeze clause neutralises that.
This lever only exists at the conversion negotiation, which is why support strategy and migration strategy must be run together rather than sequentially. The conversion-credit and Digital Access mechanics that drive the step-up are covered in S/4HANA migration before 2027 and SAP Digital Access.
A credible third-party support quote is what makes the other three levers move faster. SAP's deal desk discounts when a costed, executable alternative is on the table — Rimini Street or Spinnaker Support at roughly half the fee — and not before. The quote does not have to be accepted to work; it has to be real. Running a genuine evaluation converts an uncontested renewal into a competitive one, at which point rebasing, the uplift cap, and the conversion freeze all become negotiable rather than aspirational. The full mechanics are in SAP third-party support.
| Lever | What it changes | Typical impact | When to deploy |
|---|---|---|---|
| Rebasing | License base | 10–25% of support | Before renewal |
| Uplift cap / freeze | Annual increase | 3–8%/yr compounding | At renewal |
| Conversion freeze | Migration step-up | Avoids 10–20% jump | At conversion |
| Third-party quote | Competitive pressure | Unlocks the other three | Before / during renewal |
We sequence all four levers against your timeline and run the SAP conversation with you. Buyer-side only.
Twelve to eighteen months before the renewal. Rebasing needs a usage audit and a shelfware schedule SAP will accept; the third-party evaluation needs a real RFP cycle; and the strongest concessions are won when SAP knows you have time to walk. Starting three months out means renewing on an un-rebased base with no alternative in hand — the position SAP counts on. For estates above roughly $5M in annual support, the combined reduction typically pays for the engagement several times over, every year it holds.
$1.8B+ in documented client savings across 340+ engagements. Buyer-side only since 2016. Gartner recognised.
Weekly compliance intelligence for IT leaders.