SAP third party support, half the rate, and the choice is not about price
SAP Enterprise Support charges 22 percent of net license value annually, compounding at a 5 to 7 percent uplift; three established third party providers, Rimini Street, Spinnaker Support, and Support Revolution, price at 11 to 12 percent, a 45 to 50 percent saving. The provider choice turns on the S/4HANA roadmap, the coverage model, and the audit posture that tightens after exit.
Prepared by Redress Compliance · August 7, 2026 · SAP advisory. Based on 25 to 35 SAP support evaluations run 2024 to 2025.
Executive summary
The economics are half rate against a compounding bill. Enterprise Support runs 22 percent of net license value annually, Standard Support 19, and both compound at a 5 to 7 percent uplift across most enterprise agreements, while third party support prices at 11 to 12 percent on the same baseline, a 45 to 50 percent saving that held across our evaluations. The quote uses the same net license value SAP's does, which is why the first move is reading your own support order document: entitlement scope, SLA tier, uplift clause, and the documented baseline.
The three providers differ on coverage, not on the headline. Rimini Street, the largest by SAP revenue, covers tax and legal updates across a hundred plus countries; Spinnaker Support, the engineering led provider, forty plus; Support Revolution, the European specialist, thirty plus with the strongest European tax coverage. All three cover break fix through L3, full custom code, and independent security patch creation, and custom code coverage, not price, decided the provider in roughly half our evaluations. None cover new product releases or S/4HANA roadmap access.
The window is planned, not permanent. The third party term typically runs three to seven years, positioned after the last major upgrade with re entry planned twelve to eighteen months before the next one, because re entry carries a back maintenance fee of 18 to 24 months of support, negotiable in six of ten cases and most negotiable when the customer carries an S/4HANA roadmap commitment. The window unlocks half the support spend for its duration and the leverage on the next SAP commercial event.
The audit posture tightens, and the paper discipline is the defense. SAP's posture hardened in most exits we ran, driven by the lost quarterly check ins, the lost telemetry, and the account team's incentives, so the retention discipline is non negotiable: the license grant with metric definitions, the last paid support invoice and termination notice, the certified deployment count, the landscape documented system by system, quarterly internal compliance reviews, and every change tracked. The support line was the most overlooked saving in the SAP estate, and the paperwork is what keeps it.
The coverage comparison, provider by provider
| Coverage | SAP Enterprise | Rimini Street | Spinnaker | Support Revolution |
|---|---|---|---|---|
| Break fix, L1 to L3 | Yes | Yes | Yes | Yes |
| Tax, legal, regulatory updates | All countries | 100+ countries | 40+ countries | 30+ countries |
| Custom code support | Standard interfaces only | Full | Full | Full |
| Security patches | SAP Note channel | Independent creation | Independent creation | Independent creation |
| New releases and S/4 roadmap | Included | Out of scope | Out of scope | Out of scope |
The window, timed to the roadmap
- Enter after the last major upgrade: the coverage gap, new releases and roadmap access, is real but rarely material for a stable footprint that has already landed its release.
- Run three to seven years: the typical window, unlocking the 45 to 50 percent for the duration and the leverage on the next SAP commercial event.
- Plan re entry twelve to eighteen months before the next major upgrade, because the migration needs vendor support in place before it starts.
- Negotiate the back maintenance on the way in and the way out: the 18 to 24 month fee moved in six of ten cases, furthest when an S/4HANA commitment rode with it.
- Price the baseline first: the third party quote uses the same net license value, so the support order document's entitlement scope and uplift clause are the homework.
The SAP RISE negotiation brief
The commercial event the support window builds leverage for: the RISE economics, the credit mechanics, and the exit terms that matter.
Get the white paper →The audit posture after exit, six rules
SAP tightens after a support exit, losing its quarterly check ins and system telemetry while the account team keeps its incentives, so the defense is documentary: retain the license grant with the original order, metric definitions, and named user list; retain the support entitlement record, the last paid invoice, the termination notice, and the certified deployment count; document the landscape, production through QA, development, sandbox, and DR, each system tied to an entitlement; run quarterly internal compliance reviews across named users, engines, and indirect access; and track every change, each new module, integration, and use case, as it happens rather than at audit time. The indirect access exposure that dominates SAP audits is its own discipline, worked in the digital access pillar, and the audit machinery in the SAP audit defense framework; the wider cross vendor economics of the model, the reinstatement math and the credible option leverage, in the third party support report.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across evaluations, 2024 to 2025
Across roughly 25 to 35 SAP support evaluations run between 2024 and 2025, the support line was the most overlooked saving in the SAP estate:
Against the 22 percent Enterprise Support rate on the same net license value baseline.
The 18 to 24 month re entry fee proved negotiable, furthest with an S/4HANA commitment attached.
The tier landscape frames the decision: Enterprise Support at 22 percent fits an estate with an S/4HANA migration genuinely in plan, Standard Support at 19 fits legacy ECC on extended maintenance, the by quote large enterprise program covers the top fifty accounts, and third party support at 11 to 12 fits the stable footprint between upgrades. The decision is a roadmap decision wearing a price tag: the estate that knows its next major upgrade date can place the window precisely, and the estate that does not should establish the roadmap first, because the audit posture and the re entry fee both price against the plan you can evidence.
Your first five moves
- Read the support order document: entitlement scope, SLA tier, uplift clause, and the net license value baseline both quotes will use.
- Request three proposals in parallel and compare on the six column grid, with custom code depth weighted the way half our evaluations decided.
- Place the window on the roadmap: after the last major upgrade, re entry planned twelve to eighteen months before the next.
- Build the retention file before notice: license grants, entitlement records, certified counts, and the documented landscape.
- Negotiate the back maintenance terms up front, because six of ten moved. The SAP practice runs the evaluation with you.
Frequently asked questions
How much does SAP third party support save?
45 to 50 percent: SAP Enterprise Support runs 22 percent of net license value annually, compounding at a 5 to 7 percent uplift, while the three established providers price at 11 to 12 percent on the same baseline. The saving held across our 25 to 35 evaluations, and the support line was the most overlooked saving in the SAP estate.
Who provides third party support for SAP?
Three established providers: Rimini Street, the largest by SAP revenue, with tax and legal coverage across a hundred plus countries; Spinnaker Support, the engineering led provider covering forty plus; and Support Revolution, the UK headquartered European specialist covering thirty plus. All three cover break fix through L3, full custom code, and independent security patches.
What does SAP third party support not cover?
New product releases and S/4HANA roadmap access, on every provider: the current release line locks for the window, and security patches come from independent creation rather than the SAP Note channel. The gap is real but rarely material for a stable footprint between upgrades, which is why the window places after the last major upgrade.
Can you return to SAP support after leaving?
Yes, with a back maintenance fee typically running 18 to 24 months of support, negotiable in six of ten cases we ran and most negotiable when an S/4HANA roadmap commitment rides with the return. Plan re entry twelve to eighteen months before the next major upgrade so vendor support is in place before the migration starts.
Does SAP audit customers who leave support?
The audit posture tightened in most exits we ran, driven by the lost quarterly check ins, the lost telemetry, and the account team's incentives. The defense is documentary: retained license grants and metric definitions, the last paid invoice and termination notice, the certified deployment count, a documented landscape, quarterly internal reviews, and every system change tracked.
How do you choose between the SAP third party providers?
On coverage against your footprint, not price: custom code depth decided roughly half our evaluations, and the tax and legal country coverage, a hundred plus for Rimini Street, forty plus for Spinnaker, thirty plus for Support Revolution, decides for multinational estates. Run three proposals in parallel across the six column grid: price, scope, tax coverage, SLA, custom code, and geography.
