SAP license negotiation: what actually saves money

SAP licence negotiation saves real money in four places, and the headline discount is not one of them. The first is user classification: paying for the access people actually use. The second is digital access from non-SAP systems. The third is contract terms such as price caps, notice periods, expiring credits and exit rights. The fourth is new: since 10 July 2026, SAP's maintenance commitments to the European Commission let on-premise customers stop paying maintenance on unused licences in defined cases. This guide is for CIOs, CFOs and procurement leads facing a renewal, an audit or a move to RISE or GROW. Start the usage review six months before the renewal date, not six weeks.

I have watched companies sign SAP agreements, smile and move on. A few months later the smiles fade when the first audit lands.

One firm purchased thousands of licences, but usage data showed barely half were active. Another assumed indirect access was just a clause in fine print. Then came a bill that nearly matched its original deal. These are not unusual stories. I have seen companies quietly lose 25 percent of their ERP budget through these gaps.

On-premise perpetual licences

You pay for the licence upfront, then an annual support fee. SAP's list price for Enterprise Support is 22% of the licence value. After the initial price lock, SAP may raise support fees by inflation each year, subject to contract terms.

Know what you are measured on:

1. Named user types. ECC used Professional, Limited Professional, Employee and Developer users. S/4HANA on-premise contracts use Professional Use, Functional Use, Productivity Use and Developer Access. Misalignment between assigned type and actual use is the most common audit finding.
2. Package metrics. Some engines are priced on revenue, purchase order volume or employee count. Ask why that metric was chosen. Some penalise growth in ways nobody anticipated at signing.
3. Digital access. Documents created in SAP by non-SAP systems are licensed separately (covered below).
4. Non-production systems. Check how development, test and sandbox systems are treated in your contract before you build them.

Cloud subscriptions, RISE and GROW

S/4HANA cloud subscriptions are counted in Full Use Equivalents (FUE). Each user type converts at a fixed ratio: one FUE covers one advanced user, five core users or thirty self-service users, and a developer counts as two FUE. Classify users carefully. Every advanced user who only approves things costs you five times what a core user would.

As advanced usersAs core users

Full Use Equivalents needed4FUE−16 FUE · −80%

As advanced users20 FUE

As core users4 FUE

• Classified on what they actually do
• One FUE for every five users

RISE with SAP (private cloud, now also sold as SAP Cloud ERP Private) bundles the S/4HANA subscription, infrastructure, technical managed services and some BTP consumption credits. It simplifies vendor management and reduces your ability to negotiate each component separately. GROW with SAP is the public cloud route for companies new to SAP, with a more standard scope and price.

For either one, four questions matter. Which credits and services are included? When do they expire? How do users convert from your current contract? What happens to your data when you leave? My RISE with SAP page covers the offering itself.

After an EU competition investigation (case AT.40823), SAP agreed a set of maintenance and support commitments that took effect on 10 July 2026. They apply globally to all on-premise customers for ten years. The ones that change a negotiation:

1. Landscape splits. You can divide your landscape into separate commercial installations and choose a different support model, a different support provider or no support for each. A split does not trigger repricing of your licences.
2. Terminating unused licences. You can terminate licences and their maintenance without re-discounting in four cases. The product is only in customer-specific maintenance. The implementation failed. The company is insolvent. Or the workforce shrank by more than 10% over two years (retroactive to 1 January 2025). Notice is three months before the end of the term.
3. Initial term. Buying additional licences no longer restarts the initial maintenance term.
4. Reinstatement. The reinstatement fee is waived, and back-maintenance is capped at the lower of 50% of the missed fees or six months of payments.
5. Single metric contracts. Available where fees exceed EUR 500,000. If an audit shows underuse, SAP reduces the maintenance base by up to 20% a year.
6. Divestitures. You can transfer the divested business's user licences to the buyer, or terminate the ones it does not take, without re-discounting.

If you are on ECC and paying full maintenance on modules you stopped using, this is the first thing I would put on the renewal agenda.

These clauses look routine and become expensive.

Price uplift. Cloud subscriptions can rise at renewal unless the contract says otherwise. Cap the annual increase, or lock pricing for the full term, at signature. Uncapped increases compound across a five-year term.

Auto-renewal. Check the notice period in every order form. Miss the window and you are committed to another term at whatever price applies.

Data access after termination. Agree the export format, timing and any charges for post-termination access before you sign. Some exports need conversion work to be usable.

Non-production coverage. Confirm what development, test and sandbox systems are covered. Adding them after signature costs money.

Digital access scope. Define how documents created by external systems are measured and what volume is included.

Expiring services and credits. Implementation hours, training budgets and BTP credits included in a deal have use-by dates buried in the terms. I have seen organisations lose thousands of dollars in included services because nobody tracked the expiry.

For the wider commercial picture, see my ERP contract negotiation guide for CFOs.

Before any renewal conversation starts, run your own utilisation review. Do not rely on the vendor's usage summary.

1. Pull a login report for the last 90 days. Zero-login accounts almost always belong to leavers or people who changed roles.
2. Run a classification report. Compare each user's licence type with the transactions they actually run.
3. Review composite roles. Custom role bundles sometimes carry a permission that lifts a user into a higher licence type for no reason.
4. Map integrations. Find every technical user and interface that creates documents.

SAP's License Administration Workbench (LAW) consolidates user and usage data across systems and is the basis of any audit. If the data feeding it is messy, you will overpay. SAP Solution Manager adds usage monitoring that shows low-adoption modules, though its mainstream maintenance ends in 2027.

A warehouse team I reviewed had Professional licences assigned on their original job titles at implementation. When we mapped what they actually did (logistics execution transactions only), the licence type dropped to Employee. The cost in that group fell by around 40%.

Inactive accounts are the simplest place to start. I once cut a licence bill by ten percent by deleting test IDs.

Digital access (the older term is indirect access) is when a non-SAP system creates documents in SAP. Since 2018, SAP has licensed it on nine document types: sales, invoice, purchase, service and maintenance, manufacturing, quality management, time management, financial and material documents. SAP counts only the initial creation. Reads, updates and deletes are not counted. Documents that SAP creates automatically from the first one (an invoice following a sales order, for example) are not counted either.

The table shows where exposure usually comes from.

Scenario	Why it counts	Mitigation
E-commerce orders	Each order pushed from an external platform creates a sales document, counted per line item	Agree a document volume in the contract; review whether every line needs to post
Middleware invoice import	Supplier invoices created by an interface are invoice documents	Map every invoice source and include it in the estimate
Mobile field service entries	Each saved confirmation or notification can create a document	Design the interface to post consolidated documents where the process allows
BI and analytics extraction	Reading data does not create documents, so it does not count under the document model	Confirm your contract uses the document model; older named-user terms may treat it differently
Batch jobs	Only jobs that create new documents count; updates to existing ones do not	List which jobs create documents and which only change them

Before renewal, map every non-SAP system that touches SAP. SAP provides estimation notes for ECC (2644139) and S/4HANA (2644172) that count documents created through technical users. Treat the result as a baseline, then agree a volume in the contract rather than leaving it undefined.

One client I worked with had a mobile field service app. It pushed a status update into SAP after every technician visit, and each update created a document, thousands of times a month. Once we mapped it, we restructured the integration to batch the updates instead. That one change significantly reduced their digital access exposure.

Work through these in order. The first three need the most lead time.

1. Pull a 90-day login report and remove or reassign zero-activity accounts
2. Map every interface that touches SAP, including CRM, e-commerce, analytics and middleware, and estimate its document volume
3. Check whether any licences qualify for termination or a landscape split under SAP's July 2026 commitments
4. Confirm user type definitions in writing, with the activities each type permits
5. Cap annual price increases for the full term
6. Clarify development, test and sandbox coverage
7. List every bundled hour, credit and service with its expiry date
8. Agree the digital access measurement method and included volume
9. Negotiate the right to reclassify users downward without new charges
10. Agree exit terms: data format, timing, charges and audit notice periods

If you want an independent view before you sit down with SAP, my piece on SAP negotiation advisors covers when outside help pays for itself.

What is indirect access in SAP licensing and how does it create costs?

Indirect access, now called digital access, is when a non-SAP system creates documents in SAP without a person logging in. SAP has licensed it since 2018 on nine document types, counting only the initial creation of each document. Reads, updates, deletes and documents SAP creates automatically afterwards are not counted. Exposure comes from interfaces such as e-commerce orders, imported invoices and mobile apps. Map them before renewal and agree a document volume in the contract.

What SAP user licence types exist and how should they be assigned?

ECC contracts use named users such as Professional, Limited Professional, Employee and Developer. S/4HANA on-premise contracts use Professional Use, Functional Use, Productivity Use and Developer Access. Cloud subscriptions convert users into Full Use Equivalents. Assign by what people actually do in the system, not by job title. Professional licences given to warehouse staff, field technicians or approvers are the most common audit finding.

How is RISE with SAP licensed and what is included?

RISE with SAP is a subscription that bundles S/4HANA private cloud software, infrastructure, technical managed services and some SAP BTP credits, priced in Full Use Equivalents. Industry add-ons, other SAP cloud products, extra BTP consumption and implementation services are usually extra. Negotiate how your current licences convert, when included credits expire, and how your data is returned if you leave.

What changed in SAP maintenance contracts in 2026?

From 10 July 2026, SAP applies commitments agreed with the European Commission to all on-premise customers worldwide for ten years. Customers can split landscapes and choose support per installation. They can terminate unused licences in defined cases without re-discounting. Buying more no longer restarts the initial term, and support can be reinstated without a reinstatement fee. The full detail is on SAP's support site under case AT.40823.

What should be reviewed before an SAP licence renewal?

Five areas. User utilisation over the last 90 days. Digital access volumes from every interface. The status and expiry of bundled credits and services. Whether you use everything you pay for. The price escalation terms. On-premise customers should add a sixth: whether any licences now qualify for termination or a landscape split under the 2026 commitments.

How does an SAP licence audit work and how can companies prepare?

SAP audits examine user classification, digital access and the systems in use, usually from LAW data and measurement programs SAP asks you to run. Your contract should set the notice period and the accepted data sources. Preparation is continuous: quarterly utilisation checks, documented user type assignments, a record of any exceptions agreed with SAP, and a written agreement on what data SAP can access before the audit starts.