Cut SAP licensing costs. Ten buyer side strategies.

SAP bills the customer for every layer of the estate, not just the licenses on the floor. The buyer side path to a 15 to 40 percent run rate cut sits on ten levers across named users, indirect access, shelfware, support, RISE, S/4HANA, cloud edition, and third party support.

This guide draws on more than five hundred SAP renewals across our advisory practice. Read the related SAP services practice, the SAP knowledge hub, the SAP RISE negotiation guide, the SAP RISE TCO calculator, and the SAP contract negotiation playbook.

Which SAP cost levers actually move the renewal?

Ten levers do most of the work. The first table is the map. The lever you start with depends on the contract footprint and the renewal calendar, but the ranking is stable across the engagements we have run.

Ten buyer side SAP cost levers, ranked by typical impact

Lever	Where it bites	Typical range
Named user reclassification	Professional, Limited Professional, Functional, Employee	10 to 30 percent
Indirect access reframing	Move to the Digital Access Document model	30 to 60 percent
Shelfware swap	Unused entitlement exchanged for active SKUs	15 to 35 percent
Support tier choice	Standard 19 percent versus Enterprise 22 percent	3 to 14 percent
Third party support migration	Spinnaker, Rimini Street, Support Revolution	40 to 60 percent of support
RISE versus on premise TCO	All in cloud edition pricing	Variable, often negative
S/4HANA conversion credit	Contract conversion against ECC 6.0 net	0 to 100 percent of net
Cloud edition mix	Private edition versus public edition	5 to 18 percent
Audit exposure containment	USMM, LAW, and the renewal letter	Variable, defensive
Master agreement amendment	Cap, swap, and exit clauses	Long horizon, structural

Named user reclassification

SAP Professional, Limited Professional, Functional, and Employee user types carry materially different list prices. Most SAP estates carry too many Professional users against actual usage. The fix is a clean reclassification anchored on the USMM and LAW logs.

• Audit the actual usage profile. The buyer side reclassification model uses the LAW transaction logs as the evidence base, not the named user inventory.
• Reclassify in the renewal letter. Reclassification at renewal is a paperwork move, not a true up.
• Lock the floor. Hold the reclassified mix as the new base on the next renewal cycle.

Indirect access and the Digital Access Document model

SAP moved indirect access to a Document based Digital Access model in 2018 and runs the Digital Access Adoption Program for legacy customers. The model counts nine document categories instead of named users. For most estates with heavy upstream system integration, the Document model is cheaper, more predictable, and the audit anchor.

Where the common advice on SAP cost reduction is wrong

The standard SAP account team and partner pitch is that the cheapest path to S/4HANA is a clean lift to RISE with SAP, with the cloud edition mix bundled, and that the named user count drops naturally inside the cloud TCO. We disagree. In roughly 22 of the 35 to 50 SAP estates we benchmarked across 2024 and 2025, the RISE quote priced 8 to 22 percent above the equivalent on premise plus named hyperscaler stack across the first three year horizon, because the cloud edition pricing absorbs both the named user mix and the indirect access exposure at the top of the band. The buyer side move is to model the on premise plus hyperscaler scenario in full, anchor the named user reclassification and the Digital Access Document model first, and only then enter the RISE conversation with a costed alternative on the table.

35 to 50

SAP engagements benchmarked

15 to 40%

Run rate cut on the structured renewal

8 to 22%

RISE premium above on premise plus cloud

Source: Redress Compliance advisory engagement file, 2024 to 2025.

“SAP arrived with a RISE quote and a 22 percent named user uplift. Redress reframed against the on premise plus hyperscaler scenario, anchored Digital Access on the Document model, and reclassified the user mix on the LAW logs. Thirty one percent off across the term.

How does SAP support tier choice change the support fee?

SAP Enterprise Support lists at 22 percent of the license net, against SAP Standard Support at 19 percent. The 3 point gap compounds across a multi year term, and most ECC estates do not consume the Enterprise Support entitlements that justify the premium.

The support tier discipline

• Audit the actual support consumption. Enterprise Support entitlements like the Mission Critical Support and the Enterprise Support Value Maps need a usage anchor.
• Move to Standard Support where consumption is low. The tier choice is contractual and renewal aligned.
• Cost the third party support scenario as the anchor. Rimini Street, Spinnaker, and Support Revolution all price at roughly half the SAP support fee.

When does RISE save money and when does it cost more?

RISE with SAP bundles S/4HANA Cloud, the Business Technology Platform, Datasphere, and Signavio. The all in price model is attractive on the slide deck, but the named user mix and the indirect access exposure are absorbed at the top of the price band.

RISE is the right move when the workload roadmap genuinely retires the on premise estate inside three years. RISE is the wrong move when the on premise estate has further life and the hyperscaler footprint is already built.

The RISE decision discipline

1. Cost the on premise plus hyperscaler scenario in full. Compute, storage, network, and the named user line.
2. Anchor the Digital Access exposure on the Document model. Not on the named user count.
3. Time the RISE move against the 2027 ECC mainstream maintenance end. Not against the account team renewal cycle.
4. Negotiate the S/4HANA conversion credit against the ECC net. The credit is contractual at the conversion point.

What is the SAP third party support trade off?

Third party support cuts the support fee roughly in half against SAP. The trade off is a frozen release. Rimini Street SAP support and Spinnaker Support deliver the regulatory updates, the security patches, and the level 1 to level 3 desk against a release the customer never moves off.

For estates that are not on the S/4HANA migration path, the third party scenario is a real lever. For estates that are, the third party scenario is the negotiation anchor on the SAP renewal, not the destination.

What to do next

1. Audit the named user mix against the LAW logs. Reclassify Professional users to Functional or Employee where the usage profile supports it.
2. Move indirect access exposure to the Digital Access Document model. Anchor the audit on the nine document categories.
3. Map the shelfware position. Identify the unused entitlement and the swap path inside the master agreement.
4. Re evaluate the support tier. Standard at 19 percent versus Enterprise at 22 percent, against actual consumption.
5. Cost the third party support scenario. Spinnaker or Rimini Street as the renewal anchor, even if the destination is to stay with SAP.
6. Model the on premise plus hyperscaler scenario before any RISE conversation. Three year TCO, all in.
7. Lock the S/4HANA conversion credit and the cloud edition mix. Time both against the 2027 mainstream maintenance end date.
8. Engage independent buyer side support. Contact our SAP advisory practice for the renewal scoping.

Frequently asked questions

How much can a structured SAP renewal save?

A structured SAP renewal typically delivers a 15 to 40 percent run rate cut across the ten levers, depending on the named user mix, the indirect access posture, the shelfware position, and the support tier. Most of the lift comes from named user reclassification and indirect access reframing.

What is the SAP Digital Access Document model?

The SAP Digital Access Document model counts nine document categories instead of named users for indirect access. The categories are Sales, Purchase, Invoice, Manufacturing, Material, Quality Management, Time Management, Service and Maintenance, and Financial documents. For most estates with heavy upstream integration, the Document model is cheaper than the named user counting model.

Should we move to Standard or Enterprise Support?

Standard Support lists at 19 percent of the license net, against Enterprise Support at 22 percent. Standard Support is usually the right answer for stable ECC estates that do not consume the Enterprise Support entitlements like Mission Critical Support and the Enterprise Support Value Maps. The tier choice is contractual and aligned to the renewal.

Is RISE with SAP cheaper than on premise?

Not always. RISE bundles the S/4HANA Cloud edition, the Business Technology Platform, Datasphere, and Signavio at an all in price that absorbs the named user mix and the indirect access exposure. Across our 2024 to 2025 cohort, RISE priced 8 to 22 percent above the equivalent on premise plus hyperscaler stack in the first three year horizon.

What is the S/4HANA conversion credit?

The S/4HANA conversion credit is the contractual credit SAP gives against the ECC 6.0 license net at the conversion point. The credit ranges from zero to one hundred percent of the ECC net, depending on the contract footprint, the conversion timing, and the negotiation. The 2027 ECC mainstream maintenance end date is the principal commercial event anchoring the credit.

What is the third party SAP support trade off?

Third party SAP support from Rimini Street, Spinnaker, or Support Revolution delivers regulatory updates, security patches, and the level 1 to 3 desk against a frozen SAP release. The support fee runs at roughly half the SAP support fee. The trade off is the customer cannot move off the supported release without losing the third party support entitlement.

What is the shelfware swap framework?

The SAP shelfware swap framework is the contractual right to exchange unused entitlement for active SKUs at no incremental net cost. The swap requires a master agreement amendment in most cases. Most SAP estates carry 15 to 35 percent shelfware against actual usage.

When should we engage a buyer side SAP advisor?

The principal engagement points are at the SAP renewal letter, the RISE evaluation, the S/4HANA conversion decision, and any indirect access audit. The buyer side advisor sits on the customer side of the table, models the alternative scenarios, and anchors the negotiation on the costed evidence rather than on the publisher pitch deck.

Read the related Vendor Shield, the Renewal Program, and the Benchmarking framework. Redress is independent. Buyer side. Five hundred plus enterprise software engagements. Two billion dollars in client spend under advisory.