Editorial photograph of a CFO comparing SAP standard support and third party support proposals in a boardroom
Article · SAP · Third Party Support

SAP Third Party Support. Compared.

SAP standard support runs at twenty two percent of the net license value annually. Three independent third party support providers price at half the rate. The decision turns on the roadmap, the audit posture, and the support coverage scope.

Read the Framework SAP Hub
3Independent providers
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP charges twenty two percent of net license value annually for SAP Enterprise Support. Three established third party support providers price at eleven to twelve percent annually. The provider cost saving runs forty five to fifty percent.

The three providers are Rimini Street, Spinnaker Support, and Support Revolution. The choice turns on the SAP roadmap, the deployment footprint, and the audit posture. The choice does not turn on the price alone.

Read this article alongside the SAP knowledge hub, the SAP advisory practice, the SAP RISE Negotiation Guide, the Rimini Street SAP reference, and the Vendor Shield subscription.

Key Takeaways

What a CIO and CFO need to know in 90 seconds

  • SAP Enterprise Support prices at 22% of net license value. Third party support prices at half the rate.
  • Three established providers cover SAP. Rimini Street, Spinnaker Support, and Support Revolution.
  • The roadmap drives the decision. S/4HANA migration plans collide with third party support coverage gaps.
  • SAP audit posture tightens after third party support exit. The contract retention discipline matters more than the price.
  • Tax and security patches are the coverage gap. Each provider runs a different model for legal and security updates.
  • Re entry to SAP support carries a back maintenance fee. The fee typically runs eighteen to twenty four months of back support.
  • The contract retention discipline is non negotiable. License grants, support entitlement, and deployment records.

Standard support economics

SAP Enterprise Support is the default support program for ECC, S/4HANA on premise, BW, CRM, and SCM. The annual support fee runs twenty two percent of the net license value. The fee compounds at a five to seven percent annual uplift across most enterprise agreements.

SAP support tier comparison

TierRateCoverageTypical fit
Enterprise Support22% of net licenseAll products, SLAs, roadmap accessS/4HANA migration in plan
Standard Support19% of net licenseCore products, longer SLAsLegacy ECC on extended maintenance
Product Support for Large EnterprisesBy quoteCustom SLAs, dedicated teamTop fifty SAP accounts
Third Party Support11% to 12%Break fix, tax and legal, custom codeStable ECC or S/4 footprint

The buyer side fix on standard support

Read the SAP support order document. Confirm the support entitlement scope, the SLA tier, and the renewal uplift clause. Document the net license value baseline. The third party support price quote uses the same baseline as the SAP quote.

The three providers

Three independent providers cover SAP at scale. Each provider runs a different commercial model, a different geographic coverage, and a different roadmap on tax and legal updates.

Three SAP third party support providers

  • Rimini Street. Public company, US headquartered, the largest provider by SAP revenue. Coverage runs ECC, S/4HANA on premise, BW, BusinessObjects, and SuccessFactors.
  • Spinnaker Support. Private, US headquartered, the engineering led provider. Coverage runs ECC, S/4HANA, JD Edwards, and Oracle. Smaller SAP footprint, higher technical depth.
  • Support Revolution. Private, UK headquartered, the European specialist. Coverage runs ECC and S/4HANA on premise. Strong European tax and legal coverage.

The buyer side fix on provider selection

Request three proposals in parallel. Compare on price, coverage scope, tax and legal coverage, response SLA, custom code support, and geographic presence. The proposal comparison is a six column grid. The grid is the buyer side selection artifact.

Coverage and roadmap

The coverage gap between SAP standard support and third party support sits in three areas. New product releases, regulatory and legal updates outside the contracted countries, and security patch sourcing.

Coverage comparison across providers

CoverageSAP EnterpriseRimini StreetSpinnakerSupport Revolution
Break fix and L1 to L3YesYesYesYes
Tax, legal, regulatory updatesAll countriesHundred plus countriesForty plus countriesThirty plus countries
Custom code supportLimited to standard interfacesFull custom code coverageFull custom code coverageFull custom code coverage
New product releasesYes, includedNo, out of scopeNo, out of scopeNo, out of scope
Security patch sourcingSAP Note channelIndependent patch creationIndependent patch creationIndependent patch creation
S/4HANA roadmap accessYesNoNoNo

The buyer side fix on the coverage gap

The coverage gap is real but rarely material for stable footprints. The fix is to plan the third party support window. Move to third party support after the last major upgrade. Plan re entry to SAP support twelve to eighteen months before the next major upgrade.

Third party support is not a permanent decision

The third party support window typically runs three to seven years. The re entry to SAP support carries a back maintenance fee that runs eighteen to twenty four months. The fee is negotiable when the customer carries a roadmap commitment to S/4HANA.

Plan the third party support window inside the broader SAP roadmap. The window unlocks fifty percent of the support spend for the duration. The window also unlocks the negotiation leverage on the next SAP commercial event.

Audit posture under third party support

SAP tightens the audit posture after a customer moves to third party support. The drivers include the loss of the standard support quarterly check ins, the loss of access to SAP system telemetry, and the contractual incentive on the SAP account team.

Six audit hygiene rules for third party support customers

  • Retain the license grant document. The original order, the metric definitions, and the named user list.
  • Retain the support entitlement record. The last paid SAP support invoice, the support termination notice, and the certified deployment count.
  • Document the system landscape. Production, QA, development, sandbox, and DR. Each system tied to a license entitlement.
  • Run a quarterly internal compliance review. Named user counts, engine usage counts, indirect access counts.
  • Track every system change. New module activation, new integration, new user population added.
  • Preserve the audit trail for the indirect access usage type. The Digital Access Adoption Program math runs against the historical document count.

SAP audit teams treat third party support customers as priority targets. The audit fee schedule is the same. The audit findings tend to be larger. The buyer side fix is contract retention discipline, not third party support avoidance.

Decision framework

The decision turns on five factors. The roadmap, the deployment stability, the custom code estate, the geographic coverage, and the audit posture readiness. The framework runs as a five question decision tree.

Five decision questions before moving to third party support

  1. Is the SAP roadmap stable for the next three to seven years? Third party support fits stable footprints. Migration in flight blocks the move.
  2. Does the custom code estate carry full documentation? Custom code support depends on the customer providing the source and the spec.
  3. Does the geographic footprint align with provider coverage? Tax and legal coverage varies by country.
  4. Is the SAP audit posture ready? Contract retention, license grants, deployment records.
  5. Is the re entry math acceptable? The back maintenance fee on re entry typically runs eighteen to twenty four months.

What to do next

The seven step checklist below is the buyer side starting position to evaluate SAP third party support.

  1. Confirm the SAP roadmap is stable. Three to seven year third party support window.
  2. Request three provider proposals. Rimini Street, Spinnaker Support, Support Revolution.
  3. Build the coverage comparison grid. Six column proposal comparison.
  4. Run the contract retention exercise. License grants, support entitlement, deployment records.
  5. Model the cumulative saving. Five year cumulative against the SAP renewal trajectory.
  6. Plan the re entry path. Twelve to eighteen month notice, back maintenance fee math.
  7. Engage independent advisory. Buyer side decision framework, provider negotiation, audit readiness.

Frequently asked questions

How much does SAP third party support actually save?

SAP Enterprise Support prices at twenty two percent of net license value annually. Third party support prices at eleven to twelve percent annually. The headline saving runs forty five to fifty percent on the support line.

Including the SAP renewal uplift trajectory at five to seven percent per year, the cumulative five year saving runs fifty five to sixty percent on the support cost line.

Does third party support cover S/4HANA?

Rimini Street, Spinnaker Support, and Support Revolution all cover S/4HANA on premise. Third party support coverage for RISE with SAP and S/4HANA Cloud is limited because the cloud deployment ties to the SAP cloud contract. The buyer side fit for third party support is the on premise S/4HANA estate, the legacy ECC estate, and the BusinessObjects estate.

What happens to the SAP roadmap when moving to third party support?

Access to new product releases, SAP Notes via the standard channel, and the SAP Learning Hub stops. The third party provider creates its own patches, sources its own security updates, and provides its own knowledge base. The customer loses access to the SAP S/4HANA roadmap documents during the third party support window.

Can a customer re enter SAP support after third party support?

Re entry is possible. SAP charges a back maintenance fee that typically runs eighteen to twenty four months of the standard support rate. The fee is negotiable when the customer brings a roadmap commitment to S/4HANA. Independent advisory runs the re entry math and the re entry negotiation.

Does third party support trigger an SAP audit?

The decision to move to third party support does not trigger an immediate SAP audit. SAP audit teams treat third party support customers as priority targets across the audit cycle. The buyer side fix is contract retention discipline, license grant documentation, and a quarterly internal compliance review.

How does Redress engage on SAP third party support?

Redress runs SAP third party support evaluations inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers the decision framework, the three provider proposal comparison, the contract retention exercise, the cumulative saving model, and the re entry path. Always buyer side, never SAP paid.

How Redress engages on SAP support

Redress runs SAP support evaluations inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The SAP commercial leadership sits with the founders.

Read the related benchmarking, about us, locations, and contact pages.

Score your SAP support decision against the buyer side framework in under five minutes.
Open the SAP Calculator →
White Paper · SAP

Download the SAP RISE Negotiation Guide.

A buyer side reference on SAP commercial leverage, including third party support evaluation, the provider comparison grid, the re entry math, and the audit posture. Built from hundreds of SAP engagements.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying SAP estates. No SAP influence. No sales kickback.

SAP RISE Negotiation Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
22%
SAP Enterprise rate
11 to 12%
Third party rate
3 to 7 yr
Typical window
500+
Enterprise clients
100%
Buyer side

SAP audit teams treat third party support customers as priority targets. The audit fee schedule is the same. The audit findings tend to be larger. The buyer side fix is contract retention discipline, not third party support avoidance.

Head of SAP Procurement
Global manufacturer, two thousand named users
More Reading

More from this practice.

SAP Hub →
Rimini Street SAP
SAP · Article
Rimini Street SAP
The largest provider profile.
14 min read
SAP RISE Negotiation
SAP · White Paper
SAP RISE Negotiation
Buyer side RISE framework.
18 min read
SAP Knowledge Hub
SAP · Hub
SAP Knowledge Hub
Master SAP reference.
16 min read
SAP Advisory Services
SAP · Service
SAP Advisory Services
The SAP practice.
10 min read
SAP BTP Licensing
SAP · Article
SAP BTP Licensing
Cloud credit pool optimization.
16 min read
Editorial photograph of enterprise contract negotiation strategy

SAP support decisions close cleaner with buyer side framework.

We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.

SAP intelligence, monthly.

Third party support evaluation, provider proposal comparison, re entry math, contract retention discipline, and the audit posture across every SAP engagement we run.