SAP renewals are not events, they are processes. The negotiable terms — support fee uplift, package mix, named user composition, engine consumption, indexation language, and contract-vehicle structure — are decided across an 18-month window that begins long before the renewal notice arrives. Buyers who treat the renewal as a 90-day procurement exercise lose. Buyers who treat it as an 18-month commercial programme typically recover 15–35% of base spend without scope reduction. This article maps the calendar and the moves.
A defensible SAP renewal runs across an 18-month timeline. At T-18, the entitlement baseline is reconstructed: every contract addendum, every named user split, every package licence, every engine entitlement, every prior LAW report, every audit settlement. At T-12, consumption telemetry is gathered: actual usage by user class, package licence utilisation, HANA memory, Digital Access document counts, BTP consumption. At T-9, the gap analysis runs: what is owned versus what is used, where the over-spend sits, where the compliance exposure sits. At T-6, the negotiation strategy is set: bring-down targets, the alternative-vendor narrative, the leverage points. At T-3, the negotiation opens with SAP. Renewal sign at T-0.
Buyers who open the renewal at T-3 with no prior preparation negotiate against an SAP account team that has been preparing for 12 months. The information asymmetry decides the outcome.
This is when the heaviest leverage is built — not when the notice arrives.
SAP support is sold in three tiers. Standard Support (basic) is roughly 19% of net licence value annually. Enterprise Support (the default for most buyers) is 22% of net licence value. MaxAttention (the premium tier with dedicated TQM resourcing) is priced bespoke, frequently north of 25%. Support fees are calculated on the original net licence value at purchase, escalated annually under the contract uplift clause. Across a 10-year ownership period, support fees typically exceed the original licence cost.
The negotiation moves are sequenced. First, scrutinise the net licence value used for the support fee calculation — historic mergers and credit-and-rebook events frequently leave that figure inflated. Second, negotiate the annual uplift cap (the default 3% becomes meaningfully cheaper as a fixed 0–2%). Third, evaluate third-party support providers (Rimini Street, Spinnaker) as a genuine alternative; the leverage exists even when the buyer's strategy is to stay with SAP.
A contract that escalates support fees by "CPI capped at 5%" reads similarly to "fixed 3%" in a normal year. In a high-inflation year the gap is enormous, and SAP has been quick to take the upside. The buyer-protective language is a fixed annual rate with no CPI link. The fallback is CPI-linked with a hard ceiling at 3%.
Includes the renewal calendar template, the support fee benchmarking framework and the indexation clause library.
Default SAP licence agreements do not include a right of removal. Once purchased, the licence sits on the entitlement baseline indefinitely, with support fees calculated against the full original net licence value, even after the licence is decommissioned in use. Across a typical large enterprise, 12–28% of the active SAP support base is paid against licences with zero active use.
The negotiation moves available: at renewal, negotiate a right-of-removal clause permitting the buyer to remove specified licences from the support base at anniversary in exchange for a defined commercial concession; alternatively, negotiate a credit-and-rebook event that swaps unused licences for net-new entitlement at the same value. The credit-and-rebook is the more frequently granted move, but it requires the buyer to have new requirements to land the credit against. The right-of-removal is harder to extract but more valuable long-term.
Credit-and-rebook events can re-purpose unused licences at full historic value.
We have run SAP renewals from $500K to $80M ACV across 340+ engagements.
Weekly compliance intelligence for IT leaders.
