Understanding the 22% Rate and What You're Actually Paying For
SAP's standard annual maintenance rate is 22% of the net license value (NLV) — the discounted purchase price of your SAP software licenses. For a company with $8M in net license value, that's $1.76M per year, every year, in perpetuity. Over 10 years, that's $17.6M in maintenance fees for software you already own.
For the full SAP pricing context, see the SAP Pricing Benchmarks overview.
What does 22% maintenance actually deliver? Standard SAP support includes access to SAP Notes (patches and corrections), legal and regulatory compliance updates, access to the SAP Support Portal, incident management, and remote technical support. SAP has historically argued that maintenance also funds product innovation — R&D for future SAP releases. Most enterprise customers dispute this characterization, noting that access to new products typically requires additional licensing, not just maintenance.
The Net License Value Problem
The 22% rate is applied to net license value — but NLV is itself a flawed basis for maintenance. NLV is the discounted price you paid for licenses, which may have been set during negotiations years or decades ago, potentially at artificially high starting prices. Organizations that paid $12M for licenses 15 years ago and negotiated hard at the time may now be paying 22% of a figure that was inflated to begin with. The compound effect over time is significant.
Benchmark Your SAP Maintenance Rate
Find out if your maintenance rate is above market — and what comparable organizations are paying after negotiation.
Maintenance Rate Benchmarks: What Enterprises Actually Negotiate
SAP's official position is that 22% is the standard rate and deviations are exceptional. Our benchmark data from 100+ SAP maintenance negotiations tells a different story — the majority of enterprise organizations that actively negotiate achieve rates below 22%.
| Annual Maintenance Spend | Standard Rate | Median Negotiated Rate | Best-in-Class Rate | Annual Saving per $1M |
|---|---|---|---|---|
| $200K–$500K / year | 22% | 20–21% | 18–19% | $10K–$40K |
| $500K–$1M / year | 22% | 19–20% | 17–18% | $20K–$50K |
| $1M–$3M / year | 22% | 18–19.5% | 16–17.5% | $25K–$60K |
| $3M–$8M / year | 22% | 17.5–18.5% | 15.5–16.5% | $35K–$65K |
| Over $8M / year | 22% | 16.5–18% | 14.5–16% | $40K–$75K |
Note: Rate reductions are applied to the underlying NLV, so the annual dollar saving scales with total NLV. A 2% rate reduction on $15M NLV = $300K annual saving.
"We had been paying 22% for nine consecutive years. We assumed SAP wouldn't negotiate on maintenance. Our benchmark report showed that 68% of comparable organizations had negotiated below 20%. We reduced our rate to 18.5% — $280K per year in perpetuity — in a single negotiation."
Third-Party SAP Maintenance: The 50% Alternative
Third-party maintenance (TPM) providers — primarily Rimini Street and Spinnaker Support — offer SAP ECC and S/4HANA maintenance at approximately 50% of SAP's annual rate. This is the most dramatic cost reduction available in SAP maintenance and is the right decision for a meaningful subset of SAP customers — but not for all.
Third-Party Maintenance Benchmark Pricing
| Current SAP Maintenance Spend | SAP Rate | TPM Rate (Approx.) | Annual Saving |
|---|---|---|---|
| $500K / year | 22% | ~10–11% | ~$250K / year |
| $1M / year | 22% | ~10–11% | ~$500K / year |
| $2M / year | 22% | ~10–11% | ~$1M / year |
| $5M / year | 22% | ~10–11% | ~$2.5M / year |
When Third-Party Maintenance Makes Sense
TPM is the right choice for organizations that meet most of the following criteria:
- Running SAP ECC and have made a firm decision to remain on ECC long-term (or migrate to a non-SAP ERP)
- Not planning a RISE migration in the next 3–5 years
- Primarily need bug fixes, security patches, and regulatory compliance — not access to new SAP product functionality
- Comfortable managing the SAP relationship risk that comes with leaving SAP support
- Have a stable, mature SAP environment that doesn't require frequent SAP-specific support intervention
When Third-Party Maintenance Does NOT Make Sense
- Organizations actively planning a RISE migration — SAP typically requires return to SAP support before migration, and returning from TPM after leaving often results in premium pricing
- Organizations with active SAP development or significant customization requiring SAP Core modification support
- Organizations heavily dependent on SAP's regulatory update service in complex multi-jurisdiction environments
- Organizations where the SAP relationship is a strategic factor (e.g., SAP-certified products, co-innovation agreements)
TPM vs. SAP Support: Get the Numbers
We'll model the 5-year cost comparison between SAP support, TPM, and a negotiated SAP maintenance reduction — based on your actual maintenance spend.
Using Maintenance as Negotiation Leverage
The most powerful use of SAP maintenance benchmarking is as leverage — not just for maintenance itself, but in broader SAP commercial negotiations. Here's how maintenance leverage works in practice:
TPM Credibility as RISE Pricing Lever
Organizations that credibly demonstrate they are evaluating TPM — by issuing RFPs to Rimini Street or Spinnaker, sharing competitive offers, or explicitly conditioning the RISE conversation on maintenance resolution — achieve materially better RISE pricing. Our benchmark data shows a 12–18% RISE pricing improvement for organizations that present documented TPM alternatives versus those that don't raise maintenance as a consideration.
Maintenance Freeze Periods
SAP sometimes offers "maintenance holidays" — periods of reduced or frozen maintenance in exchange for a new license commitment or RISE migration commitment. These freeze periods (typically 1–3 years) are not widely advertised but are achievable in ~25% of large enterprise negotiations, particularly when combined with a RISE commitment.
Base Price vs. Rate Reduction
Maintenance negotiation can target either the rate (reducing from 22% to a lower percentage) or the base NLV (negotiating a credit or write-down on the net license value itself). Rate reduction is more common and more straightforward. NLV write-downs are less common but possible when organizations can demonstrate that the original license value was inflated or that significant license retirement is appropriate.
When to Negotiate SAP Maintenance
Maintenance negotiation is most effective at three specific moments in the SAP commercial calendar:
- Annual renewal (60–90 days before maintenance anniversary): The highest-leverage moment is always the period before your maintenance contract renews. SAP has a revenue recognition interest in renewal — use it.
- Combined with a new license purchase or RISE negotiation: Any time you're committing new spend with SAP, maintenance is a legitimate part of the broader commercial conversation. Organizations that address maintenance in isolation lose leverage they'd have by bundling.
- ECC end-of-maintenance deadlines: The 2027 ECC standard maintenance deadline creates a negotiation window that won't exist again. Organizations that haven't used this window to renegotiate maintenance terms are leaving a time-limited opportunity unused.
- Obtain benchmark data on current market maintenance rates for your spend level
- Evaluate TPM alternatives (minimum: obtain a Rimini Street or Spinnaker quote)
- Identify your leverage points: renewal timing, RISE migration timeline, new license purchase
- Calculate the dollar value of a 2%, 3%, and 4% rate reduction on your NLV
- Determine whether NLV write-down is achievable based on unused or retired licenses
- Bundle maintenance into the broader SAP commercial conversation — never negotiate it in isolation
Related Resources
