SAP's annual maintenance fee — typically 22% of net licence value — is one of the largest fixed costs in an enterprise IT budget. For most large SAP customers this runs to millions annually. These strategies can cut that cost by 30–60% without abandoning SAP support entirely.
SAP maintenance fees — formally "SAP Software Maintenance" — are calculated as a percentage of the net licence value (NLV) in your agreement. The standard rate is 22% per annum, though many older agreements sit at 18–20% and some large enterprise contracts have negotiated bespoke rates below the standard.
What does SAP maintenance provide? In principle, it covers access to SAP Notes and patches (bug fixes and security updates), legal and regulatory compliance updates (tax rule changes, payroll legislation, financial reporting requirements), new feature releases within the product version, access to SAP's support portal and expert teams, and system monitoring tools through SAP Solution Manager. In practice, the majority of maintenance spend goes towards security patches, regulatory updates, and product version upgrades — all of which diminish in value for organisations running stable, non-evolving ECC landscapes.
This guide is part of our comprehensive SAP license negotiation guide. For the broader context on how maintenance spend fits into your SAP commercial strategy, including RISE and cloud migration economics, see our RISE with SAP review and S/4HANA migration negotiation guide.
SAP offers two primary support tiers for on-premise software: SAP Standard Support and SAP Enterprise Support. Most large enterprise customers are on Enterprise Support — but the additional cost is rarely justified by the incremental value delivered.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Standard Support provides access to SAP's global support infrastructure, including SAP Notes, patches and legal/regulatory updates, system monitoring through SAP Solution Manager's basic functions, and access to SAP's knowledge base and community resources. Support response SLAs under Standard Support are generally 4 hours for priority 1 (production down) issues.
Enterprise Support (historically priced at 22% vs Standard Support at 18%) adds a dedicated Technical Quality Manager (TQM), enhanced SLAs (1 hour for priority 1 vs 4 hours), access to SAP's Mission Control Center for run-time analysis, CQC (Customer Quality Check) sessions, and value experience sessions demonstrating SAP's innovation roadmap. For organisations with stable, well-understood SAP landscapes, the practical value difference between the two tiers is often minimal.
Requesting a downgrade from Enterprise Support to Standard Support can save 3–4 percentage points on your maintenance rate — a 14–18% reduction in maintenance spend. SAP's response to this request is often to offer concessions (additional support credits, innovation sessions, extended payment terms) rather than lose the premium. Even if SAP refuses the downgrade, initiating the conversation creates commercial leverage.
The most dramatic maintenance cost reduction available to SAP customers is switching from SAP-provided support to a third-party support provider. The two principal providers in this market are Rimini Street and Spinnaker Support, both of which provide SAP support services at approximately 50% of the SAP maintenance rate — a substantial saving that is especially attractive for organisations on stable ECC landscapes with no imminent S/4HANA migration timeline.
Third-party support providers offer their own technical support infrastructure, including access to licensed SAP software for internal research purposes, teams of former SAP employees and implementation consultants, and extended support timelines beyond SAP's own end-of-maintenance dates. For ECC, SAP's standard maintenance runs to end of 2027 (with extended maintenance available to 2030 for an additional fee) — third-party providers commit to supporting ECC well beyond this horizon.
Rimini Street and Spinnaker provide security patches for SAP vulnerabilities (developed and tested independently, without direct access to SAP's source code), tax, legal, and regulatory compliance updates for the jurisdictions your organisation operates in, interoperability updates for supported databases and operating system versions, general technical support and break-fix assistance, and custom code support for ABAP modifications.
Third-party providers cannot deliver new feature functionality — innovation is not part of the offering. They cannot access SAP's Future Pack releases, new product versions, or roadmap features. Customers on third-party support effectively freeze their SAP software at the version they're on at the point of transition. For organisations on stable ECC with no plans to adopt new SAP capabilities, this is an acceptable trade-off; for those planning S/4HANA migrations or RISE transitions, it may delay the project.
| Factor | SAP Enterprise Support | Third-Party Support |
|---|---|---|
| Annual cost (% of NLV) | 22% | ~11% (50% saving) |
| Security patches | SAP-sourced | Independently developed |
| Regulatory updates | Global + local | Jurisdictions covered by contract |
| New feature access | Yes | No — version frozen |
| Interoperability updates | SAP-certified | Provider-certified |
| RISE/cloud transition path | Direct | Requires return to SAP |
| Audit risk while on TPS | Low | Elevated — requires management |
Third-party support is not without risk, and these risks must be assessed carefully before transition. The key risk areas are legal, technical, and commercial.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
SAP has litigated aggressively against third-party support providers, most notably in the Rimini Street case that ultimately reached the US Supreme Court. The core legal dispute involves how TPS providers access SAP's software to research and develop their own patches — specifically, whether their research processes infringe SAP's copyright. Both Rimini Street and Spinnaker have been forced to modify their support delivery methodologies as a result of court rulings. Customers considering TPS should obtain independent legal advice on the current litigation status and the specific support delivery practices of their chosen provider.
TPS patches are developed independently — they are not the same as SAP's official patches, though they address the same vulnerabilities. In practice, TPS patches have a strong record of effectiveness, but organisations with complex, heavily customised SAP landscapes should conduct a detailed technical assessment of patch compatibility before transitioning.
Organisations that leave SAP support for a TPS provider and later decide to return to SAP support — for example, to facilitate an S/4HANA migration — must negotiate re-engagement terms with SAP. These terms are not standardised, and SAP has sometimes required customers to pay backdated maintenance for the period of TPS coverage as a condition of re-engagement. This is a critical risk to model before transitioning — your ability to return to SAP on reasonable terms is a significant consideration.
SAP's willingness to waive backdated maintenance for customers returning from TPS varies significantly based on your commercial relationship, the duration of TPS usage, and SAP's strategic interest in your account. Negotiate re-engagement rights explicitly before leaving SAP support — or ensure you have a credible plan to sustain TPS indefinitely if necessary.
Many organisations assume that the 22% maintenance rate is fixed and non-negotiable. This is incorrect. SAP's standard maintenance rate is a published list price — and like all SAP list prices, it is subject to negotiation. The credible threat of switching to third-party support is the single most powerful lever for reducing your SAP maintenance rate through direct negotiation.
The most effective approach is to formally engage a third-party support provider, receive a commercial proposal, and present this to SAP as a concrete alternative you are evaluating. SAP's commercial teams have significant discretion to offer maintenance discounts when faced with a credible TPS threat — particularly for large accounts where the maintenance revenue is material.
Discounts achieved through this approach typically range from 10–25% off the standard rate, with the largest savings available to the largest accounts with the most credible TPS alternatives. The offer may be structured as a reduced percentage rate, a credit against future purchases, extended payment terms, or a bundle of professional services credits.
Some SAP agreements include maintenance caps — provisions that limit annual maintenance fee increases to a fixed percentage (e.g., 2% per year) regardless of changes to list prices or licence additions. Negotiating a maintenance cap in your next renewal, particularly in a multi-year agreement, can protect against future maintenance cost inflation.
Ready to reduce your SAP maintenance bill? Get independent specialist support to structure the negotiation.
Since maintenance is calculated as a percentage of net licence value, reducing the NLV of your agreement also reduces your maintenance spend proportionally. Licence base reduction is therefore a maintenance cost strategy as well as a direct licensing optimisation.
The most common opportunities for NLV reduction include returning unused named user licences that are included in your agreement but not actively consumed, eliminating module licences for SAP products that are no longer deployed or in use, and restructuring bundle agreements where individual component licences at current list prices would be cheaper than the bundle rate (less common, but occasionally relevant for older agreements).
Returning licences to SAP is typically only possible at renewal and requires careful negotiation — SAP is not obliged to reduce your NLV and often resists. The most effective approach combines licence returns with a broader renewal negotiation that gives SAP a commercial "win" (such as a longer term commitment or a new product addition) in exchange for the base reduction. See our detailed guidance on this in the SAP license negotiation guide.
The approaching end of SAP's standard maintenance for ECC (end 2027, extended 2030 with premium) creates both a risk and an opportunity for ECC customers. SAP is highly motivated to convert ECC customers to S/4HANA — and this motivation can be used to negotiate favourable commercial terms, including maintenance reductions, during migration discussions.
Specifically, organisations in active S/4HANA migration discussions can negotiate: reduced ECC maintenance rates for the transition period (as an incentive to commit to migration), migration credits that offset RISE or S/4HANA subscription costs against current maintenance payments, and deferred maintenance payments during implementation project periods. These concessions require skilled negotiation and are rarely offered proactively by SAP — they must be extracted through structured commercial conversations.
Our S/4HANA migration negotiation guide covers the full range of commercial levers available during migration discussions, including maintenance bridge provisions and transition credit structures.
Request Enterprise → Standard Support downgrade. SAP often offers concessions rather than grant it. Either way, you reduce cost or create leverage.
Obtain a formal TPS proposal from Rimini Street or Spinnaker. Present to SAP as a live commercial alternative. Typically yields 10–25% direct discount.
Return unused licences at renewal to reduce the maintenance calculation base. Bundle with a renewal commitment to give SAP a commercial quid pro quo.
Use ECC end-of-life as leverage to negotiate maintenance bridge discounts and transition credits as part of your S/4HANA commercial agreement.
Negotiate an annual increase cap (e.g., CPI or fixed 2%) in your renewal to protect against future cost inflation on a growing licence base.
Move peripheral or frozen SAP components to TPS while maintaining SAP support for strategic, actively evolving systems. Optimises cost and risk.
A sophisticated approach that more large organisations are adopting is the hybrid support model — maintaining SAP support for actively developed, strategically important SAP systems while transitioning stable, peripheral, or sunset SAP components to third-party support.
For example, an organisation might maintain SAP Enterprise Support for its core S/4HANA production environment (which requires active patch and update coverage) while transitioning its legacy SAP CRM or SCM components (which are being phased out over the next 3 years) to Rimini Street at 50% of the current cost.
This model requires careful mapping of your SAP landscape to identify which components are genuinely active and evolving versus stable and sunset. It also requires careful structuring of the two support agreements to avoid gaps or overlaps in coverage. Independent SAP licensing specialists can help design and implement a hybrid model that maximises savings while managing risk.
The timing of maintenance reduction initiatives matters. The most favourable window for negotiating with SAP is 6–12 months before your maintenance renewal date. At this point, SAP's account team is focused on retention and has maximum incentive to negotiate. Approaching SAP 30 days before renewal provides minimal leverage.
For third-party support transitions, the optimal timing depends on your S/4HANA migration timeline. If migration is planned within 3 years, the risks of TPS re-engagement costs may outweigh the savings. If migration is 5+ years away — or genuinely uncertain — TPS delivers compelling economics even accounting for potential re-engagement costs.
With SAP's extended ECC maintenance running to 2030 (at premium pricing) and third-party providers offering ECC support beyond this horizon, organisations have a genuine choice about their support strategy. The key is to evaluate that choice with independent commercial analysis rather than accepting SAP's maintenance cost as a fixed budget line.
The 22% rate is SAP's opening position, not an immovable fact. Independent negotiation specialists consistently achieve 15–30% reductions for enterprise clients.