SAP Support & Maintenance Negotiation Guide: Cutting the 22% Fee
SAP annual maintenance at 22% of net licence value is one of enterprise software's most persistent overcharges. This independent guide covers all SAP support tiers, maintenance fee mechanics, third-party maintenance at 50% saving, and the negotiation tactics that reduce total SAP support cost by 17–50% without compromising operational stability.
Executive Summary
SAP support and maintenance fees represent one of the largest and most predictable line items in enterprise software budgets. For most SAP customers, annual maintenance is priced at 22% of the net licence value — generating consistent revenue for SAP regardless of actual support usage or value delivered to the customer. The commercial opportunity in SAP support is substantial: enterprise buyers who engage proactively with their support strategy consistently reduce total maintenance costs by 20–50% through a combination of direct renegotiation with SAP, support tier right-sizing, and strategic use of third-party maintenance (TPM) alternatives.
This paper provides a comprehensive commercial framework for SAP support and maintenance strategy, covering all SAP support tiers (Standard, Enterprise Support, MaxAttention), the mechanics of annual maintenance fee calculation and escalation, third-party maintenance providers and their commercial implications, and the negotiation tactics that produce the most durable cost reductions.
Third-party maintenance providers including Rimini Street and Spinnaker Support consistently deliver SAP support at 50% below SAP's annual maintenance rate, with service levels that meet or exceed SAP Standard Support. In February 2026, Cubic Corporation publicly disclosed a 50% reduction in SAP annual maintenance fees following migration to Rimini Street. Silicon Labs achieved comparable savings in the same period. The credible alternative to SAP support has never been stronger.
This guide is structured for procurement, IT, and finance leaders who are approaching SAP maintenance renewal or conducting a strategic review of their SAP support model.
SAP Support Tiers Explained
SAP offers three primary support tiers for on-premises and private cloud deployments, with significantly different cost and service profiles. Understanding the actual value difference between tiers is fundamental to right-sizing support spend.
| Tier | Annual Cost | Key Features | Who Needs It |
|---|---|---|---|
| SAP Standard Support | 22% of net licence value | SAP Notes, patches, legal change support | Organisations with strong internal SAP capability |
| SAP Enterprise Support | 22% of net licence value (same) | + Mission-critical support, extended SLAs, advisory | Orgs requiring faster critical issue response |
| SAP MaxAttention | 22% + significant premium | Dedicated SAP team, proactive engagement | Large complex estates requiring deep SAP partnership |
Standard vs Enterprise Support: the value gap
SAP moved all customers from Standard to Enterprise Support in 2015 without a price increase, positioning Enterprise Support as a free upgrade. In practice, the difference for most enterprise customers is marginal: the additional Enterprise Support features (primarily Mission Critical Support and the SAP Engagement & Service Delivery model) are not actively used by the majority of the SAP customer base. Organisations paying for Enterprise Support but using only Standard Support features are not extracting the tier's stated value.
SAP MaxAttention is the highest-cost support tier and includes dedicated SAP resource assignment and proactive engagements. It is appropriate for large, complex SAP landscapes with active innovation programmes. Organisations that have signed MaxAttention contracts without rigorous ROI assessment frequently find the premium — which can add £500K–£2M annually versus Enterprise Support — unjustified by actual utilisation of MaxAttention-specific services.
Maintenance Fee Mechanics: How the Uplift Compounds
SAP's on-premises support fee model calculates annual maintenance as a percentage of the net software licence value. The standard rate is 22%, applied to the aggregate net licence value (NLV) of all SAP software licences owned. As organisations add licences over time — for new modules, additional users, or acquired entities — the NLV increases and maintenance fees scale accordingly.
Annual uplift and compounding
SAP often ties annual maintenance adjustments to the Consumer Price Index (CPI) or a fixed rate. A 3% annual uplift — which SAP routinely applies without explicit negotiation — compounds to over 15% additional cost over five years. For an organisation paying £2M annually in SAP maintenance, a 3% uncapped uplift adds approximately £330K in cumulative additional maintenance over five years, for no additional service value. Negotiating an explicit cap is straightforward and consistently successful when raised before renewal.
| Annual Uplift | Year 1 | Year 3 Cost | Year 5 Cost | 5-yr Compound Premium |
|---|---|---|---|---|
| Uncapped (3%) | £2.00M | £2.12M | £2.31M | +£330K |
| Capped at 2% | £2.00M | £2.08M | £2.17M | +£166K |
| Capped at CPI (avg 2%) | £2.00M | £2.08M | £2.17M | +£166K |
| Fixed (no uplift) | £2.00M | £2.00M | £2.00M | £0 |
Third-Party Maintenance: The 50% Alternative
Third-party SAP maintenance providers — primarily Rimini Street and Spinnaker Support — offer support for SAP on-premises systems at approximately 50% of SAP's annual maintenance rate. This represents the most significant single cost-reduction option available to organisations with stable SAP landscapes who are not in active migration to S/4HANA.
What third-party maintenance includes
Third-party SAP maintenance covers: break-fix support for all SAP products in the estate; custom code support; interoperability patches for OS and database upgrades; regulatory, tax, and legal updates for supported countries; and security patches for supported releases. The primary differences from SAP support are: no access to new functionality releases, no access to SAP's support portal (SAP Notes) for new issues, and no official pathway to S/4HANA upgrade support.
Rimini Street's 2026 SAP offering
Rimini Street extended support for SAP ECC 6.0 and S/4HANA through 2040 in 2025, removing the time-horizon concern that previously limited TPM adoption. The company currently supports hundreds of SAP ECC 6.0 and S/4HANA clients. Its patented AI tools provide issue resolution support, and a named Primary Support Engineer model provides dedicated, expert-level engagement. Cubic Corporation's February 2026 announcement confirmed 50% annual maintenance savings, a figure consistent with Rimini Street's standard commercial model.
Using TPM as Leverage Without Committing to It
The most commercially valuable application of third-party maintenance knowledge is as negotiating leverage — not necessarily as an operational decision. Organisations that present a credible TPM alternative to SAP's account team before renewal consistently achieve 10–20% better SAP maintenance pricing, even when they ultimately remain with SAP support.
The leverage mechanism
Obtaining a formal TPM proposal from Rimini Street or Spinnaker Support 6–9 months before SAP maintenance renewal serves several purposes: it establishes a concrete cost alternative (typically 50% of SAP fees); it signals to SAP that the organisation is engaged in the commercial process; and it provides a price anchor that SAP's account team must respond to. SAP's response to a customer with a TPM proposal on the table is materially different from their response to a customer who approaches renewal as a standard administrative exercise.
The decision: SAP vs TPM
For organisations actively planning S/4HANA migration within 2–3 years, remaining with SAP support is typically the right commercial choice — the migration pathway, credit entitlements, and technical support continuity justify the premium. For organisations on stable ECC or S/4HANA landscapes with no near-term migration trigger, TPM delivers the same operational continuity at 50% of the cost. The decision should be made on commercial and roadmap grounds, not on the basis of SAP's sales narrative about the risks of third-party support.
ECC Deadline and Maintenance: Commercial Strategy Framework
SAP's ECC 6.0 mainstream maintenance schedule creates a direct commercial intersection between support strategy and migration planning. The maintenance commercial decision and the migration commercial decision should be evaluated together, not independently.
Scenarios and their commercial implications
| Organisation Scenario | Recommended Support Strategy | Commercial Rationale |
|---|---|---|
| S/4HANA migration within 2 years | Remain with SAP Standard/Enterprise | Preserve migration credits, roadmap access |
| S/4HANA migration in 3–5 years | Negotiate SAP cap + TPM as leverage | Reduce near-term cost while preserving optionality |
| No S/4HANA plans (stable ECC) | Evaluate TPM seriously | 50% saving, TPM support through 2040 available |
| S/4HANA RISE evaluation underway | Negotiate ECC maintenance cap now | ECC maintenance will overlap RISE; minimise overlap cost |
Capping Annual Maintenance Uplifts
The simplest and most consistently successful commercial intervention in SAP maintenance is negotiating an explicit annual increase cap at the next contract event. SAP's standard maintenance contract language does not include such a cap by default — it is negotiated in, not standard. The negotiation is straightforward: propose a maximum increase of 2–2.5% annually or CPI (whichever is lower), supported by the observation that the maintenance fee is already paying a significant premium for a support tier whose underlying costs are not increasing at the same rate.
What SAP will offer vs what you can achieve
SAP's typical opening position on uplift caps is 3% or CPI+1%. Well-prepared buyers consistently achieve 2% fixed or CPI with a 2% ceiling. The gap between 3% and 2% annual compounding on a £2M maintenance contract is £166K over five years — material enough to justify the negotiating effort. Some well-positioned buyers with TPM alternatives on the table achieve fixed-rate or even fee reductions at renewal.
SAP Support Negotiation Tactics
A Rimini Street or Spinnaker Support proposal at 50% of your SAP maintenance cost is the single most effective commercial tool in any SAP maintenance negotiation.
Document the SAP support cases raised, SLA attainment, and MaxAttention/Enterprise Support features actually utilised. This evidence supports right-sizing discussions and removes SAP's ability to claim support value without substantiation.
SAP's Net Licence Value calculation should be audited before renewal. Decommissioned licences, consolidated user counts post-optimisation, and retired modules that still appear in the NLV create overstated maintenance base values. Correcting the NLV reduces the maintenance calculation base.
For MaxAttention customers who are not actively consuming the premium services, negotiate a tier reduction to Enterprise Support with a formal service utilisation review. This commonly produces £300K–£1M annual saving on large estates.
SAP maintenance renewals signed in the final three weeks of SAP's fiscal year (end of December) or regional quarter-end consistently achieve 5–10% better commercial terms than off-cycle renewals.
Pre-Signature Checklist
Formal third-party maintenance proposal at ~50% of current SAP maintenance cost.
Explicit cap in the maintenance contract, not subject to CPI variability above the cap.
Decommissioned licences and consolidated user counts removed from NLV before maintenance calculation.
MaxAttention reviewed against service utilisation; Enterprise Support confirmed vs Standard Support requirement.
If S/4HANA migration is in scope, ECC maintenance suspension or credit mechanism agreed for the overlap period.
Maintenance contract expiry aligned with anticipated S/4HANA go-live to avoid locked-in SAP maintenance during RISE subscription.
Case Study: Global Manufacturer Saves £3.6M on SAP Support Over 5 Years
A FTSE 100 global manufacturer with a complex SAP estate (ECC 6.0, BW, CRM, and multiple ancillary products) was paying £2.4M annually in SAP Enterprise Support. No S/4HANA migration was planned within three years. Redress was engaged to conduct a comprehensive support strategy review.
Actions taken
Redress: audited the NLV and identified £180K of decommissioned licences in the maintenance base; assessed actual Enterprise Support utilisation (finding only Standard Support features were used); obtained a Rimini Street proposal at £1.2M annually (50% saving); conducted a migration timeline review; and presented findings to SAP's account team six months before renewal.
Outcomes
| Variable | Before | After | Annual Saving |
|---|---|---|---|
| NLV correction | £10.9M NLV | £10.08M NLV | £180K/yr |
| SAP maintenance rate | 22% | 22% (same tier) | — |
| Annual uplift | 3% uncapped | 2% capped (5yr) | £48K/yr compound |
| Support tier | Enterprise Support | Enterprise Support (retained, justified) | — |
| TPM leverage benefit | No alternative | SAP reduced base by 8% | £178K/yr |
| Total annual saving | £2.4M | £1.99M | £410K (17%) |
Total 5-year saving including compounding uplift cap benefit: approximately £3.6M. The organisation remained with SAP support, preserving full S/4HANA migration optionality — with a materially better commercial position.
About Redress Compliance
Redress Compliance is a Gartner-recognised, 100% buyer-side enterprise software licensing advisory firm. We have no commercial relationships with any software vendor.
Our SAP advisory practice covers SAP support strategy, maintenance optimisation, TPM assessment, and S/4HANA migration commercial preparation across 300+ engagements.
SAP Licensing Knowledge Hub · All White Papers · Enterprise Spend Navigator Newsletter