Why SAP Renewal Is the Most Important Negotiation Event
SAP's annual maintenance fees — typically 22% of net licence value — represent the single largest recurring software cost for most SAP customers. Over a 5-year period, maintenance costs exceed the original licence investment. Over 10 years, maintenance alone can reach 2–3× the initial licence fee. The renewal event is the only moment when you have concentrated leverage to restructure this cost base: SAP wants the renewal signed, and you have the ability to walk away, reduce scope, or switch providers. Every concession not secured at renewal becomes a compounding cost for years to come.
| Licence Value | Annual Support (22%) | 5-Year Support Cost | 10-Year Support Cost | Savings at 3% Annual Reduction |
|---|---|---|---|---|
| $5M | $1,100,000 | $5,500,000 | $11,000,000 | $330K/year = $3.3M over 10 years |
| $10M | $2,200,000 | $11,000,000 | $22,000,000 | $660K/year = $6.6M over 10 years |
| $20M | $4,400,000 | $22,000,000 | $44,000,000 | $1.32M/year = $13.2M over 10 years |
SAP applies annual support price increases of up to 3.3% (indexed to CPI in many geographies, with some contracts allowing up to 5%). On a $10M licence base, uncapped 3.3% annual increases escalate the $2.2M/year support cost to $2.94M by year 10 — a cumulative overspend of $3.6M compared to a flat rate. Negotiating a cap on annual increases (ideally 0–2%) at renewal is one of the highest-ROI negotiation moves available. Every percentage point of cap reduction saves $100K+ per year on a $10M estate.
Step 1: Audit SAP Usage and Eliminate Shelfware
Before engaging SAP on any renewal discussion, conduct a thorough internal audit of your current SAP usage. The most immediate and impactful cost reduction comes from identifying and eliminating shelfware — licences you are paying annual maintenance on but are not actually using. In our advisory practice, we find shelfware representing 15–35% of total SAP licence value in most enterprise estates.
| Shelfware Category | How to Identify | Typical Savings | Action at Renewal |
|---|---|---|---|
| Inactive user licences | Run USMM/LAW reports; identify users with no login in 90+ days or users who have left the organisation | $200K–$2M+ in licence value freed | Deactivate accounts; reduce licensed user count; renegotiate support base |
| Unused modules | Cross-reference purchased modules against actual transaction volumes and configuration activity | $500K–$5M+ in licence value | Negotiate removal from support scope or trade-in for credit toward modules you need |
| Over-classified users | Users with Professional licences who only use Employee Self-Service or basic reporting — needing only Limited Professional or ESS licence | $100K–$1M+ (price differential × user count) | Reclassify users to appropriate licence types; reduce Professional user count |
| Duplicate environments | Development, sandbox, or test systems that are no longer actively used but still licensed | $100K–$500K | Decommission unused environments; consolidate test landscapes |
A global manufacturer with a $12M SAP licence estate paying $2.64M/year in maintenance. Internal audit reveals: 400 inactive user accounts ($1.2M licence value), 3 modules never fully implemented ($2.4M licence value), and 200 Professional users who should be Limited Professional ($800K licence value differential). Total shelfware: $4.4M in licence value = $968,000/year in unnecessary support fees. Over 5 years: $4.84M in wasted maintenance payments. Negotiating removal at renewal eliminates this cost permanently and reduces the ongoing support base for all future years.
Step 2: The 12-Month Renewal Playbook
Phase-by-Phase Renewal Strategy
Months 12–9: Internal Assessment
Form cross-functional renewal team (IT, procurement, finance, legal, SAP CoE). Conduct comprehensive usage audit using USMM/LAW reports and SAP License Administration Workbench. Inventory all licences, modules, and user classifications. Identify shelfware. Map current licence position against actual business needs. Benchmark your SAP spend against industry peers.
Months 9–6: Strategy Development
Define your SAP roadmap for the next 3–5 years (stay on ECC, migrate to S/4HANA, evaluate RISE, explore non-SAP alternatives). Set renewal objectives: target discount percentage, maintenance rate cap, shelfware removal, contract flexibility requirements. Obtain competitive quotes from third-party support providers (Rimini Street, Spinnaker) as negotiation leverage. Prepare initial SAP engagement — signal that you are evaluating options.
Months 6–3: Active Negotiation
Present SAP with your optimised licence position (shelfware removed, users reclassified). Negotiate licence discounts (target 30–50% off list for any new purchases). Negotiate maintenance rate reduction or cap on annual increases. Address indirect access/digital access compliance proactively. Negotiate ECC-to-S/4HANA conversion terms if applicable. Secure contractual flexibility (licence swaps, volume adjustments, favourable audit terms).
Months 3–0: Finalise and Document
Finalise commercial terms with all negotiated concessions documented in the contract (not verbal promises). Verify all shelfware removals are reflected in the new support base. Confirm maintenance rate, annual increase cap, and any price protections are written into the ordering document. Secure executive sign-off. Archive all renewal documentation for future reference.
Step 3: Negotiation Tactics That Save Millions
| Negotiation Lever | How to Deploy It | Typical Impact | When to Use |
|---|---|---|---|
| Shelfware removal | Present documented evidence of unused licences/modules; demand removal from support base or trade-in credit | $500K–$5M+ in annual support savings | First negotiation session — establishes your right-sized baseline |
| Third-party support proposal | Obtain a formal quote from Rimini Street or Spinnaker showing 50–60% maintenance savings. Share with SAP as credible alternative. | 5–15% maintenance rate reduction | Mid-negotiation — when SAP resists maintenance concessions |
| Competitive alternative | Demonstrate active evaluation of alternative platforms (Workday for HCM, Oracle Cloud ERP, Microsoft Dynamics) for part of your landscape | 10–20% additional discount on new purchases | When SAP is pushing new product adoption or RISE conversion |
| Fiscal calendar alignment | Time your renewal decision to coincide with SAP's quarter-end (March, June, September, December) or year-end | 5–15% additional discount | Always — but especially effective at year-end |
| Multi-year commitment | Offer a longer commitment period (3–5 years) in exchange for deeper discounts, maintenance rate locks, or additional licence credits | $1M–$10M+ in total cost savings over commitment period | When you have confidence in your SAP roadmap and want maximum price protection |
| Licence swap rights | Negotiate the right to swap existing licence types (e.g., Professional → Limited Professional, or ECC → S/4HANA) without penalty | $200K–$2M in avoided re-purchase costs | During renewal — especially if S/4HANA migration is planned within 2–3 years |
Need Expert SAP Licensing Guidance?
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →Step 4: ECC vs S/4HANA — Renewal Implications
| Scenario | Renewal Strategy | Financial Impact | Key Risk |
|---|---|---|---|
| Staying on ECC (2027+ support) | Negotiate extended maintenance terms. Cap annual increases. Evaluate third-party support for post-2027 period. | Extended maintenance premium of 2–4% above standard rate | ECC mainstream support ends 2027; extended support to 2030 at premium pricing. Plan required. |
| Migrating to S/4HANA on-premises | Negotiate ECC-to-S/4HANA licence conversion at renewal. Demand conversion at no additional licence cost with maintenance parity. | Potential $0 additional licence cost; maintenance may adjust | Maintenance recalculation can increase annual support by 10–30% if not negotiated |
| Moving to RISE with SAP | Negotiate RISE subscription with existing licence credit. Compare total cost against on-premises continuation over 5 years. | RISE typically costs 2–3× on-premises annual maintenance; negotiate credits to close the gap | Post-initial-term RISE renewal pricing may spike 20–50% without contractual caps |
| Hybrid (partial cloud + on-premises) | Negotiate flexibility to move workloads between on-premises and cloud during the contract term. Avoid paying for both simultaneously. | $500K–$5M+ risk of dual spending if not managed | SAP may not credit on-premises licences against RISE subscription without explicit negotiation |
The RISE Renewal Trap
RISE with SAP initial-term pricing is often heavily discounted to incentivise adoption. However, SAP's standard contract language allows significant price increases at RISE renewal — typically 20–50% above the initial subscription rate. If you adopt RISE during your current renewal cycle, negotiate contractual caps on RISE renewal pricing (ideally 0–5% annual increase) and ensure you have exit provisions that allow you to return to on-premises licensing without penalty if RISE economics become unfavourable. Without these protections, your "cost-saving" cloud migration may become a cost escalation within 3–5 years. See our RISE with SAP Advisory.
Step 5: Indirect Access & Digital Access Compliance
Indirect access — where third-party systems (Salesforce, web portals, middleware, IoT devices) interact with SAP data — has historically been a major source of unbudgeted SAP licence costs. SAP's 2018 introduction of the Digital Access licensing model provides an alternative to licensing every external touchpoint as a named user, but digital access licences must be proactively negotiated at renewal to avoid retroactive claims.
| Access Type | Old Model (Named User) | New Model (Digital Access) | Renewal Action |
|---|---|---|---|
| Salesforce → SAP integration | Every Salesforce user accessing SAP data potentially requires an SAP named user licence | Licensed by document type (sales orders, invoices) created in SAP, not by user count | Negotiate digital access licence package at renewal to cover integration volumes |
| E-commerce / web portal | Every customer creating orders in SAP via web portal requires a named user licence | Licensed by document count — number of orders, invoices, etc. processed through SAP | Assess document volumes; negotiate digital access pricing with volume discounts |
| IoT / machine integration | Each device interacting with SAP could require a named user licence (impractical at scale) | Licensed by document count or specific IoT licence package | Negotiate IoT-specific terms at renewal to avoid per-device named user obligations |
| RPA / bot access | Each RPA bot interacting with SAP transactions may require a named user licence | Digital access may cover bot-generated documents; verify with SAP | Proactively address RPA access at renewal before SAP raises it in audit |
Step 6: Maintenance & Support Cost Optimisation
| Strategy | How It Works | Typical Savings | Considerations |
|---|---|---|---|
| Shelfware removal from support base | Negotiate removal of unused licences/modules from the support calculation, reducing the annual maintenance fee | 15–35% of annual support cost | SAP's default position is all-or-nothing; large customers have negotiated partial removals |
| Maintenance rate reduction | Negotiate the support percentage below the standard 22% — achievable for large estates, especially with third-party support leverage | 1–3% of licence value per year ($50K–$600K+/year) | SAP rarely goes below 19%; use third-party support proposals as credible alternative |
| Annual increase cap | Cap year-over-year maintenance increases at 0–2% instead of SAP's standard CPI-linked 3.3–5% | $100K–$500K+/year by year 5 (compounding effect) | Negotiate at renewal when you have maximum leverage; once missed, the next opportunity is years away |
| Third-party support | Switch to Rimini Street, Spinnaker, or similar providers for 50–60% maintenance savings. No SAP updates or patches. | 50–60% of annual maintenance cost | No new SAP patches/updates; reinstatement fees to return to SAP support; evaluate carefully for stable environments |
| Support tier optimisation | Verify you are not overpaying for Enterprise Support if Standard Support meets your needs | 2–5% of licence value per year | Enterprise Support includes additional services (MaxAttention, premium engineering); evaluate whether you use them |
SAP Renewal Compliance Checklist
Pre-Renewal Governance Disciplines
Run USMM and LAW reports
Execute SAP's User Master Maintenance (USMM) and Licence Administration Workbench (LAW) to generate the current licence measurement. This is the same data SAP uses in audits — review it before SAP does.
Classify all users correctly
Verify every user has the correct licence type (Professional, Limited Professional, Employee Self-Service, Developer, etc.). Reclassify over-provisioned users before renewal to establish a clean, optimised baseline.
Map indirect access exposure
Identify all third-party systems, web portals, APIs, RPA bots, and IoT devices that interact with SAP data. Quantify the document volumes they generate. Address these proactively at renewal rather than reactively during an audit.
Benchmark your SAP spend
Compare your licence costs, maintenance rate, discount level, and contract terms against industry benchmarks and peers. If you are paying above-market rates, use benchmark data as evidence in negotiations.
Document all negotiated terms in writing
Every concession — discounts, credits, swap rights, maintenance caps, audit protections — must be explicitly documented in the signed ordering document. Verbal assurances from SAP account executives have no contractual standing.
Engage independent advisory
SAP licensing is complex and SAP's account teams are skilled negotiators. Independent advisory firms (like Redress Compliance) provide benchmarking data, negotiation strategy, and contract review that typically deliver 3–8× ROI on advisory fees through improved renewal terms.
Expert Recommendations — 10 Rules for SAP Renewal Success
| # | Rule | What It Means in Practice | Consequence of Ignoring |
|---|---|---|---|
| 1 | Perform internal licence audit first | Use USMM/LAW to map actual usage vs entitlements before SAP engagement. Know your compliance position before SAP does. | SAP discovers compliance gaps first and uses them as renewal leverage |
| 2 | Clean up and reallocate before negotiation | Deactivate inactive accounts, reclassify over-provisioned users, identify unused modules. Enter negotiation with an optimised baseline. | You negotiate on an inflated baseline, paying support on licences you do not need |
| 3 | Start 12 months before renewal | Form cross-functional team, set objectives, gather competitive intelligence, engage SAP with lead time for iterative negotiation. | Rushed renewals favour SAP — last-minute deals consistently cost 20–40% more |
| 4 | Align renewal with SAP roadmap | Integrate ECC-to-S/4HANA migration plans, RISE evaluation, and digital access requirements into the renewal negotiation. | Dual spending on old and new platforms; missed conversion credits; unprotected RISE renewal terms |
| 5 | Benchmark against industry peers | Know what discounts, maintenance rates, and terms comparable organisations achieve. Use benchmark data as evidence in negotiations. | You accept SAP's "standard" terms that are significantly above market rate |
| 6 | Negotiate beyond price | Contract flexibility (licence swaps, volume adjustments), audit protections, maintenance caps, and exit provisions are as valuable as upfront discounts. | Low headline price but restrictive terms that create $1M+ in costs during the contract period |
| 7 | Use leverage strategically | Third-party support proposals, competitive platform evaluations, and fiscal calendar timing create genuine negotiation pressure. | SAP has no incentive to offer concessions if you demonstrate no credible alternatives |
| 8 | Document everything in writing | Every discount, credit, swap right, cap, and protection must appear in the signed ordering document — not in emails or verbal commitments. | Verbal promises from SAP reps have no contractual standing; you lose all negotiated concessions |
| 9 | Engage independent advisory | SAP licensing specialists provide benchmarking data, negotiation playbooks, and contract review that internal teams cannot replicate alone. | 3–8× ROI missed; internal teams lack SAP's pricing intelligence and negotiation benchmarks |
| 10 | Stay firm but relationship-focused | Be assertive on cost objectives while maintaining a collaborative tone. You want a fair deal, not a confrontation. | Adversarial approach damages relationship; overly accommodating approach costs millions |
Related Guides
Explore More Licensing Hubs
Ready to Take Control of Your Software Licensing?
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →