SAP Maintenance Renewal:
Escaping the 22% Trap

SAP maintenance renewal is the most predictable large spend in most enterprise IT budgets — and among the least scrutinised. The invoice arrives annually, procurement approves it based on historical precedent, and SAP collects 22% of your perpetual licence value without substantive commercial challenge. Multiply that rate across a £20M licence estate and you are paying £4.4M per year for support services whose actual consumption is rarely audited.

Our SAP support cost reduction service focuses exclusively on this recurring spend. Across engagements with enterprises running SAP estates from £5M to £200M in licence value, we consistently identify 15–30% in achievable annual support cost reductions — through tier renegotiation, licence right-sizing, third-party support evaluation, and direct commercial challenge. This article sets out the complete methodology.

The SAP Support Tiers: What You Actually Get

SAP offers three primary support tiers for on-premise licences, each with a different annual cost and a different set of commitments. Understanding the precise differences — and mapping them against what your organisation actually uses — is the starting point for any maintenance negotiation.

Support Tier	Annual Cost	Key Features	SAP's Target Buyer
Standard Support	18% of licence value	SAP Notes access, software updates, SAP ONE Support Launchpad	Smaller or less complex landscapes
Enterprise Support	22% of licence value	All Standard features plus: SLA commitments, Solution Manager integration, SAP Learning Hub access, Innovation Cycles	Complex enterprise landscapes — SAP's default push
Premium Engagement	Negotiated, typically 25%+	All Enterprise features plus dedicated Technical Quality Manager, proactive advisory	Very large or strategically critical accounts

The commercial reality is that SAP's default position is to place all enterprise customers on Enterprise Support, regardless of whether the additional capabilities over Standard Support are actually used. A rigorous consumption audit — assessing actual use of Solution Manager integration, SAP Learning Hub, Innovation Cycles, and the enhanced SLA framework — frequently reveals that Standard Support is operationally adequate for a significant portion of the enterprise landscape.

The Compounding Cost Problem

What makes SAP maintenance costs particularly insidious is the compounding dynamic. Your licence value was established in a prior contract, possibly years ago, at prices that were inflated by SAP's historical pricing architecture. Enterprise Support at 22% is calculated against that inflated base. If your organisation has over-licensed — carrying Professional Named Users that should be lower-tier, or packages that are no longer actively deployed — you are paying 22% on a base that is itself inflated. The double-compounding of over-licensing and high support rates is the most common source of structural SAP overspend we see in the enterprise sector.

Seven Tactics for Reducing SAP Maintenance Costs

The following seven tactics represent the complete toolkit for SAP maintenance cost reduction. They are not mutually exclusive — the most effective engagements use several in combination, each reinforcing the overall commercial argument for reduced maintenance spend.

1. Audit Your Actual Support Consumption

Before any commercial negotiation, build an evidence base for what you actually use in your current support tier. This means extracting data from SAP's support portal (SAP for Me) on incident volumes by priority level, Solution Manager usage frequency, Learning Hub access records, and Innovation Cycle participation. The objective is to demonstrate either that Enterprise Support's differential features over Standard Support are genuinely under-utilised (making a tier downgrade commercially reasonable) or that your current usage pattern is consistent with a lower-cost support structure.

Most organisations that conduct this audit for the first time discover they are using less than 40% of the incremental Enterprise Support features they are paying for. That finding becomes the opening argument in the maintenance renegotiation.

2. Right-Size the Licence Base

Since maintenance is calculated as a percentage of licence value, every pound removed from the licence base reduces the maintenance charge proportionally. A user reclassification exercise — moving Professional Named Users to Limited Professional, Employee, or lower-tier classifications where the transaction evidence supports it — reduces both the direct licence cost and the compounding maintenance burden. Our SAP licence optimisation service typically identifies 20–40% licence base reduction opportunities in complex enterprise landscapes.

3. Negotiate Enterprise Support Down Toward 19–20%

SAP's published Enterprise Support rate is 22%, but it is not immovable. SAP has historically offered rate concessions to large accounts that demonstrate: (a) credible intent to evaluate third-party support alternatives, (b) clear documentation of support under-utilisation, or (c) a concurrent negotiation on broader commercial terms (e.g. a new deployment or a RISE migration). The typical achievable floor on Enterprise Support in a direct negotiation is 19–20%, representing 2–3 percentage points of annual savings on the full licence base. On a £30M licence estate, that is £600,000–£900,000 per year.

4. Evaluate Third-Party Support as a Genuine Alternative

Third-party SAP support providers — including Rimini Street, Spinnaker Support, and LiquidHub — offer maintenance services for SAP ECC and older SAP ERP releases at rates significantly below SAP's. Typical third-party rates are 40–50% below SAP's Enterprise Support rate, with comparable or better incident response SLAs for many support categories. The threat of third-party support migration is SAP's most significant commercial pressure point in a maintenance negotiation. It must be presented credibly — with an actual third-party proposal in hand — to be effective. Our team includes former SAP support professionals who understand precisely how to frame this option.

Important caveat: third-party support excludes SAP product updates and patches. This has significant implications if your current SAP release requires ongoing security patches or if your organisation has compliance obligations that depend on current SAP software versions. Evaluate the operational implications carefully alongside the financial case.

5. Challenge the Licence Value Base Directly

If your maintenance is calculated against a licence value that was established in a prior contract at artificially high prices — a common situation for SAP estates built up through legacy deal structures — the licence value base itself is challengeable. This requires a retrospective analysis of your historical Order Forms and the applicable price lists at the time of purchase, followed by a commercial argument that the maintenance base should be recalibrated against current market pricing for equivalent entitlements. This is a technically demanding position, but one that our team has successfully argued in multiple large-enterprise contexts.

6. Use Upcoming Deployment Decisions as Leverage

If your organisation is evaluating S/4HANA migration, RISE adoption, or a broader SAP deployment decision, the maintenance renewal is best negotiated as part of that broader commercial conversation rather than in isolation. SAP's commercial team is structurally incentivised to support migration decisions — linking a maintenance cost concession to a deployment commitment is a transaction that SAP's account hierarchy can typically approve where a standalone maintenance reduction would face more resistance.

7. Consolidate Maintenance Schedules for a Single Negotiation

Enterprises with multiple SAP contracts — often accumulated through acquisitions, regional deployments, or legacy product purchases — frequently maintain multiple separate maintenance schedules with different renewal dates. Consolidating these into a single annual renewal provides the combined volume leverage of the full estate, rather than negotiating each component independently at a fraction of the total value. Schedule consolidation alone typically improves negotiating position by 5–10% on maintenance rate.

The Third-Party Support Decision in Depth

Third-party support warrants a dedicated section because it represents the most structurally impactful option available to enterprises managing mature SAP landscapes — and the one that SAP's commercial team most consistently works to discourage.

Third-party support providers maintain dedicated SAP engineering teams with deep expertise in SAP ECC, SAP BW, SAP CRM, and other mature SAP products. For organisations that have no current plans to upgrade to S/4HANA, have stable landscapes with low incident volumes, and prioritise cost efficiency over access to SAP's latest innovation cycles, third-party support is often the rational commercial choice.

The financial case is direct. Rimini Street, the market leader in third-party enterprise software support, typically prices SAP support at 50% of SAP's maintenance rate. On a £20M SAP licence estate paying 22% Enterprise Support, that represents moving from £4.4M per year to approximately £2.2M — a saving of £2.2M annually. Over a five-year period, with no uplift, that is £11M in cumulative savings.

The Risk Calculus

The risks of third-party support are real and must be evaluated honestly. Third-party providers cannot deliver new SAP functionality or feature updates — your landscape will remain on the current version without access to SAP's development roadmap. For organisations planning S/4HANA migration in the next three to five years, third-party support may extend the time on a legacy platform and complicate the eventual migration. And SAP's commercial relationship will be materially affected — SAP account teams view third-party support as a hostile act and typically withdraw advisory access and early-programme involvement from accounts that take this route.

Our recommendation is to evaluate third-party support as a genuine option in every maintenance renewal, regardless of whether you ultimately take it. The evaluation itself — and its presentation to SAP as a credible alternative — consistently produces better outcomes in the SAP maintenance negotiation than any negotiation conducted without it.

What Happens at the Maintenance Renewal: Timeline and Process

SAP's maintenance renewal process is designed to produce a quiet automatic renewal at the current rate. The invoice arrives approximately 90 days before the renewal date, and SAP's default expectation — reinforced by contract terms that may include automatic renewal provisions — is payment without commercial discussion. Most organisations comply.

The buyers who achieve the best maintenance outcomes begin their commercial engagement at least six months before the renewal date. This allows time for the support consumption audit (four to six weeks), the licence right-sizing analysis (four to eight weeks), the third-party support evaluation and quote (two to four weeks), and the actual negotiation process (four to six weeks). Entering the renewal negotiation 30 days before the invoice due date gives SAP all the time pressure and gives you none.

The renewal conversation should be framed as a commercial review, not a renewal approval. The framing signals to SAP's commercial team that the renewal is not guaranteed on existing terms and that the enterprise has conducted a formal evaluation of its support requirements and alternatives. This framing, consistently applied, produces structurally better outcomes than treating the renewal as an administrative approval process.

RISE with SAP and the Maintenance Transition

For organisations on the path to RISE with SAP or S/4HANA Cloud, the maintenance renewal takes on additional complexity. RISE subscriptions do not use the traditional perpetual licence and annual maintenance model — instead, the subscription fee encompasses both software access and support in a single bundled charge. This means that the current year's maintenance renewal may be the last under the traditional model, or one of a small number of remaining renewals before the transition completes.

SAP's commercial team will use the RISE transition as a reason to avoid substantive maintenance concessions — arguing that the savings in RISE more than offset any near-term maintenance reduction, or that maintenance cost optimisation is superseded by the migration business case. Both arguments may be partially true and should not be dismissed, but neither eliminates the relevance of the current-year maintenance negotiation. The period between announcing RISE intent and completing the migration can span two to four years — during which time annual maintenance payments continue at the unreduced rate.

Our RISE with SAP advisory team specialises in bridging this gap — negotiating maintenance cost reductions on the legacy estate while simultaneously ensuring that RISE commercial terms reflect accurate, benchmarked pricing for the new contract. Both negotiations need to happen, and both matter.

FAQ: SAP Maintenance Renewal

Can we actually negotiate SAP Enterprise Support below 22%?

Yes. SAP's published rate is 22%, but this is not contractually fixed across all scenarios. Enterprises with large licence estates, credible third-party support alternatives, or active deployment negotiations have negotiated rates as low as 19–20% in direct commercial discussions. The key is arriving at the negotiation with documented evidence of support under-utilisation and a credible alternative that SAP's commercial team takes seriously.

Does switching to third-party support void our SAP licences?

No. Your perpetual SAP licences remain valid regardless of your support provider. SAP cannot terminate your licence entitlements because you use a third-party support provider. However, SAP may restrict your access to future software updates, security patches, and certain SAP services that are bundled with SAP support. Review your Master Agreement and applicable T&Cs with independent legal counsel before making the transition.

If we right-size our licences and reduce the base, does that permanently lower our maintenance?

Yes — licence right-sizing has a permanent compounding benefit on maintenance costs. If you remove £2M in over-licensed perpetual licence value from your maintenance base, you reduce your annual Enterprise Support charge by £440,000 (at 22%) in perpetuity. This is why the licence right-sizing exercise is almost always the highest-return activity in a maintenance cost reduction engagement.

How far in advance should we engage SAP about the renewal?

Ideally six months before the renewal date. This gives time for the consumption audit, licence analysis, third-party evaluation, and the actual negotiation. Many organisations engage too late — at 30–60 days before renewal — which compresses the process and gives SAP the time advantage.

Is Standard Support genuinely viable for a complex enterprise landscape?

It depends on your specific landscape, incident profile, and support requirements. Standard Support provides SAP Notes access and software updates, which is adequate for many stable landscapes. However, if you rely heavily on SAP Solution Manager's integrated support capabilities, or have SLA commitments to your internal business users that require SAP's enhanced response commitments, Enterprise Support may be genuinely justified. The decision should be based on a consumption analysis, not on SAP's default recommendation.