SAP contracts are designed to grow. Adding users and modules is easy, but reducing them is not. This guide explains how to negotiate partial termination and downsize rights, avoid shelfware traps, and align SAP costs with actual business needs at every renewal.
This guide is part of the SAP Licensing for S/4HANA Complete Guide pillar. See also: Negotiating S/4HANA Conversions and Credits | Retiring Old Components During Migration | On-Premise vs Cloud TCO.
SAP's annual maintenance fee (typically 20-22% of total licence value) is calculated on the maintenance base: the cumulative value of all licences under support. This base only moves upward. Every new purchase increases it, but SAP's standard terms contain no mechanism to reduce it. If your organisation purchased $5 million in SAP licences, you pay approximately $1.1 million per year in support regardless of whether every licence is in active use.
| Lock-In Mechanism | Detail |
|---|---|
| One-way ratchet | SAP's standard maintenance base only increases. New purchases raise it; reductions are not permitted without explicit contractual provisions |
| Shelfware cost | Industry studies show 30-40% of enterprise software spend goes to unused licences. For a $5M SAP estate, that is $330K-$440K/year wasted on maintenance for unused software |
| All-or-nothing support | SAP's default position: you cannot partially cancel support. Maintenance covers the entire estate or nothing. No selective removal of individual products |
| Auto-renewal trap | Most SAP contracts auto-renew annually. Miss the notice window (typically 3-6 months before renewal) and you are locked in for another full year |
It is not negotiating a better discount on new purchases. It is eliminating the recurring maintenance burden on licences your organisation no longer needs. A 20% reduction in your maintenance base delivers savings every year, compounding with each escalator cycle. The problem intensifies during platform transitions: running parallel ECC and S/4HANA environments without downsize provisions means full maintenance on both for two to four years.
| Case Study: Global Manufacturer | Detail |
|---|---|
| Situation | Manufacturing enterprise paying support on 5,000 SAP user licences (approximately 2 million euros/year). After restructuring, only 4,000 users actively used SAP. 1,000 licences idle |
| Without downsize rights | Continue paying for all 5,000 indefinitely, wasting approximately 400,000 euros annually on shelfware |
| With downsize rights | Surrendered 1,000 unused licences at renewal. Maintenance base shrank by 20%, delivering 400,000 euros annual savings. Over 2 million euros across five years |
| Lesson | The downsize clause cost nothing to negotiate but saved millions. Every SAP contract should include this protection as standard |
| SAP Position | Detail |
|---|---|
| No partial termination (default) | Standard terms do not permit removing individual products or reducing user counts. Support is all-or-nothing for the entire estate |
| Trade-in and migration credits (negotiable) | SAP shows flexibility when reductions are tied to new purchases or cloud migrations. Cloud Extension Policy allows terminating on-premise licences when migrating to equivalent SaaS |
| Explicit downsize clauses (customer-won) | Sophisticated enterprises have secured rights to reduce 10-20% of licence base annually without penalty. Must be negotiated proactively. SAP will never volunteer them |
Watch for three mechanisms SAP uses to limit downsizing: notice periods (3-6 months, miss it and auto-renew at 100%), bundling clauses (dropping Module A forces dropping Module B), and repricing triggers (reducing quantities recalculates your discount from 50% to 35%, eroding savings). Negotiate out all three.
| Step | Action | Detail |
|---|---|---|
| 1 | Insert an explicit downsize clause | Draft language granting the right to reduce quantities or remove products at each annual renewal without penalty. Example: "Customer may decrease Named User licences by up to 15% or remove modules not in productive use, with corresponding fee reduction. Remaining licences retain same discount percentage" |
| 2 | Structure contracts modularly | Separate products, user groups, and regions into distinct line items or order forms. The more granular, the easier to terminate one component without disturbing others. Avoid omnibus agreements bundling everything into a single package |
| 3 | Time the conversation for maximum leverage | Raise downsizing rights early in renewal negotiations. Leverage is strongest when SAP is seeking commitment to renew, expand, or migrate. If evaluating competitive platforms or third-party support, make this visible |
| 4 | Offer a trade-off if needed | Propose value exchange: invest in S/4HANA cloud subscriptions or BTP credits if you can retire equivalent on-premise maintenance. SAP sees net-positive revenue and is more likely to agree |
| 5 | Document everything in writing | Verbal assurances have no contractual weight. Downsize percentages, repricing protections, and notice periods must appear in a signed amendment. Personnel change and corporate memories are short |
| Year | Without Downsize Rights | With Downsize Rights | Annual Saving |
|---|---|---|---|
| Year 1 | $1,100,000 | $1,100,000 | $0 |
| Year 2 | $1,100,000 | $1,100,000 | $0 |
| Year 3 | $1,100,000 | $880,000 | $220,000 |
| Year 4 | $1,133,000 | $906,400 | $226,600 |
| Year 5 | $1,167,000 | $933,600 | $233,400 |
| 5-Year Total | $5,600,000 | $4,920,000 | $680,000 |
This model assumes 3% annual escalator and downsize executed at Year 3 renewal. The $680,000 is conservative. Reducing the maintenance base also reduces the annual escalator impact going forward: 3% on $1.1M costs $33,000 more each year; 3% on $880K costs only $26,400. Over five years, the compounding difference adds $40,000-$60,000 beyond the headline reduction. When presenting downsize business cases to CFOs, always model the escalator compound effect.
| Scenario | Detail |
|---|---|
| SAP Cloud Extension Policy | Enterprises moving to RISE, S/4HANA Cloud, or SuccessFactors can terminate equivalent on-premise licences and reallocate maintenance value toward cloud subscriptions. Negotiate: immediate proportional reduction (not deferred), conversion ratio between maintenance credits and cloud value, what happens if cloud subscription is terminated, remaining on-premise licences retain original discount |
| Mergers, acquisitions, and divestitures | Corporate transactions create immediate licensing mismatches. Negotiate explicit rights to transfer licences to the buyer or terminate proportional to divested headcount. Include a material change clause: licence adjustments within 90 days of qualifying corporate event regardless of standard notice period |
| Third-party support as leverage | Rimini Street and Spinnaker Support offer SAP maintenance at approximately 50% of standard rates. Even without switching, obtaining a quotation demonstrates credible Plan B. SAP frequently offers improved downsize terms when perceiving real risk. Be aware of SAP's re-entry penalties: back-maintenance for the entire period away plus reinstatement fee |
| Licence reclassification | Convert high-cost licence types to lower-cost alternatives without reducing headcount. Professional to Limited Professional or Employee Self-Service can reduce per-user cost by 60-80%. Requires detailed usage audit of transaction logs and role assignments over 6-12 months. SAP will scrutinise. Users must be reassigned to matching roles |
| Timeline | Action |
|---|---|
| 120 days before renewal | Begin internal licence usage audit. Identify all unused accounts, under-utilised modules, and licence types mismatched to actual usage |
| 90 days before renewal | Prepare downsize request with specific licence line items, quantities, and cost justification. Send formal notice to SAP if contract requires 90-day advance notification |
| Review repricing clauses | Confirm whether contract contains discount recalculation triggers. Model net impact and negotiate removal or cap |
| Check bundling dependencies | Identify cross-product ties forcing retention of unwanted modules. Request SAP restructure to remove dependencies |
| Benchmark third-party support | Obtain at least one competitive quotation as leverage, even if you prefer to stay with SAP |
| Never accept renewal invoice as-is | Every renewal is a negotiation opportunity. If usage declined, demand cost reduction via termination, reclassification, or credit toward new investments |
| Document outcomes in writing | Any flexibility SAP agrees to must appear in a signed amendment. Verbal commitments are unenforceable |
| Recommendation | Detail |
|---|---|
| Negotiate partial termination rights upfront | In every new agreement or renewal amendment. Aim for 10-20% annual reduction without penalty |
| Structure contracts modularly | Separate products, regions, user groups into distinct line items for selective termination |
| Eliminate repricing triggers | Lock in discount percentages for the entire term regardless of quantity changes |
| Calendar notice periods | Set reminders at 120+ days before renewal to begin usage review and prepare termination notices |
| Align reductions with business events | Include clauses linking licence flexibility to headcount changes, divestitures, or cloud migration milestones |
| Leverage Cloud Extension Policy | When migrating to RISE or S/4HANA Cloud, negotiate proportional on-premise maintenance reductions |
| Conduct annual licence audits | Identify shelfware, misclassified users, and redundant modules before each renewal cycle |
| Use third-party support as leverage | Credible alternatives strengthen your position even if you do not switch |
| Reclassify over-licensed users | Convert Professional users to Limited or Self-Service where usage justifies it. 60-80% per-user cost reduction |
| Engage independent advisers | Specialist firms identify savings and draft enforceable contract language internal teams may miss |
By default, no. SAP's standard policy is all-or-nothing support for the entire licensed estate. However, partial termination rights can be negotiated as explicit contract clauses. SAP also shows flexibility when reductions are tied to new purchases or cloud migrations under the Cloud Extension Policy. The key is proactive negotiation. SAP will not volunteer these options.
Most SAP contracts require written notice 3-6 months before the support renewal date. Missing this window means maintenance auto-renews at 100% for another full year. Always verify specific dates in your contract and set reminders at least 120 days out.
Potentially. Some contracts contain repricing clauses allowing SAP to recalculate discounts when volumes decrease. A 50% discount on 1,000 users might become 40% on 800, partially offsetting savings. Negotiate these clauses out during the original deal or at renewal, insisting discount percentages remain locked regardless of quantity changes.
No. Surrendered licences are permanently terminated. To regain capacity, you purchase new licences at current pricing, likely at a worse discount than the original deal. Only terminate licences you are confident you will not need. Many enterprises maintain a small buffer to absorb modest regrowth without repurchasing.
Cloud subscriptions typically lock quantities for the committed term (e.g. three years). Mid-term reductions are generally not permitted. At renewal, you can adjust volumes but only if you negotiated renewal flexibility upfront. Insist on a clause allowing reduction of up to 20% at renewal without penalty or repricing.
Primary levers: competition and alternatives. Obtain third-party support quotations. Signal evaluation of competing platforms. Offer to bundle downsizing with new investment (cloud, S/4HANA, BTP credits) so SAP sees net-positive revenue. If local account teams are unresponsive, escalate within SAP or engage your SAP User Group.
Identify all shelfware: unused licences, underused modules, over-classified user types. Calculate annual maintenance cost of each (20-22% of licence value). Project savings over 3-5 years including compound effect of annual escalators (3-5%) on the reduced base. Factor in any repricing impact on remaining licences. Enterprise clients typically find $200K-$500K in annual recoverable shelfware spend.
Redress Compliance has helped hundreds of enterprises secure flexible SAP contracts, reduce shelfware costs, and protect their position at renewal. We work completely independently of SAP. 100% vendor-independent. Fixed-fee engagement.
SAP Contract Negotiation ServiceIndependent SAP advisory. Downsize rights negotiation. Shelfware elimination. Renewal protection. 100% vendor-independent, fixed-fee engagement.