The 22% Number and Why It's Misleading
SAP Enterprise Support is structured as a percentage of your net software licence value — 22% annually. This percentage has increased over time (it was 17% before SAP's 2008 support model change, rising through 20%, 21%, and reaching 22% by the mid-2010s) and applies regardless of your usage intensity, landscape stability, or how many of the bundled services you actually consume.
The percentage model has an insidious compounding effect that most finance teams underestimate when evaluating SAP total cost of ownership. If your organisation has accumulated £15M of SAP net licence value over 15 years of module additions and user expansions, your annual maintenance fee is £3.3M — regardless of whether your landscape has been in steady state for the last five years and your primary support requirement is break-fix on a known, stable codebase.
The percentage also applies to licences you may no longer actively use. Organisations that have decommissioned modules, reduced user counts, or migrated workloads to other platforms frequently find that their net licence value basis — which SAP controls — does not reflect the current operational reality of their landscape. The licence value basis is sticky upward and resists reduction without formal SAP engagement.
The benchmark: Third-party SAP support is typically priced at 8–12% of net licence value — a flat rate that covers all the break-fix, security, and compliance support you actually need, without the roadmap taxes, cloud credits, and S/4HANA migration subsidies bundled into SAP Enterprise Support.
What SAP Enterprise Support Actually Funds
SAP Enterprise Support bundles multiple services into the 22% fee. Understanding each component — and the actual value it delivers to a stable, run-rate ECC landscape — is the foundation of the cost reduction analysis:
The analysis is stark: of the six major components bundled into SAP Enterprise Support, only two — break-fix support and legal change packages — deliver consistent operational value to a stable ECC landscape. The remaining four components (S/4HANA transition credits, learning, innovation services, and Solution Manager tooling) represent approximately 45% of the total fee, delivering zero value to organisations that have decided not to migrate to S/4HANA in the near term.
Complete SAP Support Cost Model: Three Landscape Scenarios
The following cost model illustrates the total annual SAP support expenditure across three representative enterprise landscape sizes, comparing SAP Enterprise Support against GoVendorFree TPS with equivalent scope:
| Cost Component | Small ECC Landscape (£5M NLV) | Mid-Size ECC Landscape (£15M NLV) | Large ECC Landscape (£40M NLV) |
|---|---|---|---|
| SAP Enterprise Support (22%) | £1,100,000 | £3,300,000 | £8,800,000 |
| Break-fix value (~35%) | £385,000 | £1,155,000 | £3,080,000 |
| Legal change value (~20%) | £220,000 | £660,000 | £1,760,000 |
| Zero-value components (~45%) | £495,000 | £1,485,000 | £3,960,000 |
| GoVendorFree TPS (10%) | £500,000 | £1,500,000 | £4,000,000 |
| Annual saving | £600,000 (55%) | £1,800,000 (55%) | £4,800,000 (55%) |
| 5-year saving | £3,000,000 | £9,000,000 | £24,000,000 |
The 55% saving figure is conservative. Organisations that also address their SAP BASIS staffing model, landscape rationalisation, and AMS (Application Management Services) agreements in parallel with the TPS transition routinely achieve 65–72% total SAP operating cost reduction. The SAP BASIS support cost reduction guide covers the additional levers in detail.
Calculate your exact SAP support saving
Share your current SAP Enterprise Support contract value and landscape overview. We'll produce a detailed cost comparison within 15 minutes.
Get your free SAP cost analysis →Legal Change Packages: The Real Story
The legal change package component of SAP Enterprise Support is frequently cited by SAP as the most defensible reason to maintain vendor support — particularly for payroll, tax, and statutory reporting. This deserves careful examination rather than blanket acceptance.
What Legal Change Packages Actually Cover
SAP legal change packages update ECC for jurisdiction-specific statutory changes: PAYE/NI changes (UK), DATEV changes (Germany), IRS/SSA updates (US), and similar jurisdiction-by-jurisdiction statutory maintenance. For organisations with complex multi-jurisdiction payroll running entirely on SAP, this is a genuine dependency.
The Dependency Is Narrower Than SAP Claims
Third-party support providers including GoVendorFree deliver legal change equivalent through two mechanisms. First, for customers in stable regulatory environments (UK, US, EU core), TPS providers maintain statutory update capability that matches SAP's legal change packages for the covered jurisdictions — typically covering 85–90% of the customer base. Second, for organisations with complex multi-jurisdiction payroll, the legal change dependency may not apply at all if payroll is processed through a specialist payroll platform (ADP, Ceridian, Workday Payroll) rather than natively in SAP HR/ECC.
The practical question is: what percentage of your SAP 22% maintenance fee is actually justifiable as legal change dependency, and how does that compare to the TPS rate? For most mid-to-large ECC landscapes, the honest answer is that legal change justifies 3–5% of licence value — not the full 22%.
SAP Support Reduction and Audit Risk
A consistent objection to reducing SAP support — whether through TPS or negotiated reduced maintenance — is the risk of increased audit scrutiny. This reflects a genuine but often overstated dynamic in the SAP customer relationship.
SAP has used software audits as a commercial tool for decades, and the correlation between customers who contest pricing and subsequent audit activity is real. However, the audit risk calculus is more nuanced than a simple "don't challenge SAP" conclusion:
- Audit scope: SAP software audits focus on licence compliance — named users, indirect access, and module usage. Moving to third-party support does not create new licence compliance exposures; you continue to use the same licences under the same terms.
- Audit timing: SAP audits are typically triggered by specific commercial events (renewal negotiations, disputed invoices, account handover). A clean TPS transition that is managed through a formal renewal cycle, with clear documentation of licence scope, presents lower audit risk than a contested mid-contract reduction.
- Audit preparation: GoVendorFree's audit defense service includes pre-TPS licence position documentation, which reduces audit risk by establishing a defensible baseline before the transition. Organisations that move to TPS with a documented, clean licence position face materially lower audit exposure.
Our position: The audit risk argument is valid as a planning consideration — not as a reason to permanently overpay. Proper TPS transition management, including audit-ready licence documentation and clean contractual separation, reduces the audit risk to an acceptable level for the overwhelming majority of ECC customers.
The 60% SAP Cost Reduction Roadmap
A 60% SAP support cost reduction is achievable in three phases, typically over 18–24 months. The phased approach manages organisational change risk and ensures each reduction initiative is properly validated before the next begins:
Phase 1 — TPS Transition (Months 1–4): ~40% saving
Move SAP Enterprise Support to third-party support at the next renewal date. This single action generates the largest cost reduction. The transition is managed to align with your SAP renewal cycle, ensuring no gap in coverage. All break-fix, security advisory, and compliance support is maintained. Legal change packages are confirmed for your jurisdiction coverage before transition.
Phase 2 — AMS Rationalisation (Months 4–12): additional 10–12% saving
SAP Application Management Services (AMS) — whether delivered by a GSI, a boutique SAP partner, or an internal team — typically assumes SAP's vendor support as a backstop. After TPS transition, AMS scope can be rationalised to remove redundant escalation paths, streamline incident management, and right-size retainer volumes against actual demand patterns. This phase requires careful transition planning but consistently delivers 10–15% additional SAP operating cost reduction.
Phase 3 — Landscape Rationalisation (Months 12–24): additional 8–10% saving
TPS transition provides the commercial stability to address landscape rationalisation — consolidating test and development instances, retiring decommissioned modules, and right-sizing BASIS infrastructure. These actions reduce the operating cost of the SAP landscape directly, and also reduce the TPS scope (and therefore cost) in subsequent renewal cycles.
| Phase | Initiative | Timeline | Saving (of original SAP cost) | Cumulative Saving |
|---|---|---|---|---|
| 1 | TPS transition (Enterprise Support → TPS) | Months 1–4 | 40–45% | 40–45% |
| 2 | AMS rationalisation | Months 4–12 | 10–12% | 50–57% |
| 3 | Landscape rationalisation | Months 12–24 | 8–10% | 58–67% |
| Total 24-month saving (£15M NLV example) | 60–67% | £1.98M–£2.21M annually | ||
SAP S/4HANA Migration Guide
If S/4HANA migration is on your roadmap, our 52-page guide deconstructs the real migration cost (£18M–£45M) and the negotiation playbook that has saved clients £6.8M on average. Free download.
Download free →Is TPS Right for Your Organisation?
Third-party SAP support is the right solution for the majority of ECC customers — but not all. The honest assessment of fit:
TPS is highly suitable when: your ECC landscape is in run-rate mode with no planned module additions; your S/4HANA migration is deferred by 3+ years; your annual SAP support spend exceeds £500K; your regulatory requirements are covered by TPS legal change capabilities for your jurisdictions; and your organisation values stable, expert break-fix support over roadmap access.
TPS requires additional analysis when: you have confirmed S/4HANA migration within 18 months (the SAP transition credits may represent genuine near-term value); you have complex multi-jurisdiction payroll in 10+ countries including high-change regulatory environments; you are mid-cycle in a SAP-funded innovation programme with contractual deliverables.
In our experience working with 500+ enterprise clients, approximately 80–85% of large ECC customers are well-suited for TPS with no material service reduction. The 15–20% who require additional analysis almost always find a hybrid approach — TPS for the majority of the landscape, with a narrow SAP support scope retained for specific functional areas — that still delivers 40–50% total cost reduction.
Find out if TPS is right for your SAP landscape
Our free assessment covers landscape scope, legal change requirements, audit position, and the transition plan. 15-minute response. No commitment.
Book your free SAP assessment →