SAP's licensing model is among the most complex — and most abused — in enterprise software. From named user types and indirect access traps to RISE contracts and S/4HANA migration leverage, this guide covers everything you need to negotiate with SAP from a position of strength.
SAP's commercial model has been built over decades and reflects the company's history as an on-premises ERP vendor that is mid-way through a cloud transition. The result is a licensing landscape of considerable complexity — one that SAP's own sales teams do not always fully understand, and that creates significant risk for enterprise buyers who approach negotiations without specialist support.
At its core, SAP licensing operates on two primary dimensions: named users (people who interact with SAP systems) and packages/modules (the functional areas licensed). On top of these, SAP has layered engine-based metrics for certain products — charging based on the volume of data, transactions, or managed objects rather than headcount. The introduction of RISE with SAP and the SAP Business Technology Platform (BTP) has added subscription-based cloud dimensions to what was previously a perpetual licence plus annual maintenance model.
Understanding the full commercial landscape — across your existing ECC or S/4HANA estate, any BTP or cloud products, and any third-party integration points — is the essential first step before any SAP negotiation. For a comparison of how SAP licensing complexity compares to other major vendors, see our guide on Oracle vs SAP negotiation strategies.
Enterprise SAP buyers carry commercial exposure across three distinct areas that must be addressed in any negotiation strategy. First, licence compliance — whether your actual deployment matches your contracted licence entitlement across user types, modules, and indirect access. Second, maintenance cost optimisation — reducing the 22% annual maintenance burden that represents the largest ongoing SAP cost for most organisations. Third, strategic positioning — how your current licence position, migration plans, and competitive alternatives interact to create negotiating leverage with SAP.
SAP's negotiating approach is driven heavily by its S/4HANA transition targets. Any enterprise on ECC with 2027 maintenance end approaching has significant leverage — SAP needs your migration commitment and will offer substantial commercial incentives to secure it. Use this window strategically, not reactively.
SAP's named user model assigns each user a licence category based on their permitted transactions. The category determines both the acquisition price and the ongoing maintenance charge. Misclassification — assigning users to lower-cost categories than their actual activity warrants — is the most common source of SAP audit liability.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
| User Type | Permitted Activity | Relative Price | Common Misuse Risk |
|---|---|---|---|
| Professional User | Full read/write access across all licensed modules | Highest | Low — typically assigned correctly |
| Limited Professional | Read/write in defined functional areas only | High | Medium — scope limitations often violated |
| Employee User | Self-service HR, travel, expenses, basic transactions | Medium | High — used for broader access in practice |
| Starter User | Very limited transactions, typically SME deployments | Low | Very High — deployed to reduce costs, scope violated |
| Developer User | Development, testing, and system administration | High | Low — well-defined scope |
| ESS/MSS User | Employee/Manager Self-Service only | Low | High — often used beyond self-service scope |
Beyond named users, SAP licenses specific capabilities through engine metrics that have nothing to do with headcount. SAP BusinessObjects (BI platform) is licensed on a named user basis but also has processor and core licensing options. SAP HANA database is licensed on memory consumed. SAP BTP services are increasingly licensed on consumption metrics — API calls, compute hours, storage volumes. Understanding which engine metrics apply to your landscape — and how usage maps against your contracted entitlement — is as important as the named user analysis.
For a comprehensive breakdown of licence categories and their implications, see our dedicated guide on SAP licence types explained.
Indirect access is the single most contentious area of SAP licensing — and the area where enterprise organisations carry the greatest unquantified exposure. The concept is straightforward: if a non-SAP system (a portal, mobile app, RPA bot, API integration, or third-party application) reads or writes SAP data, SAP's position has historically been that the users of that system require SAP named user licences, even if they never log into SAP directly.
The commercial implications of this position are enormous. A manufacturing company with 5,000 named SAP users might have 50,000 production operators querying SAP data through custom MES screens. Under historical SAP licensing, every one of those operators is a potential SAP user requiring a licence. SAP has used this exposure as a commercial lever in audit and renewal negotiations, with claims in the tens of millions not uncommon for large enterprises with complex integration landscapes.
In 2018, SAP introduced the Digital Access model for S/4HANA as a response to the indirect access controversy. Instead of charging per indirect user, Digital Access charges per digital document — a fixed fee per order, delivery, invoice, or other SAP document created or updated via a third-party system. This model is more predictable and auditable than per-user indirect licensing.
However, Digital Access applies only to S/4HANA deployments. Organisations still running SAP ECC remain subject to historical indirect access interpretations under their EULA. The migration to S/4HANA — and with it, the opportunity to adopt Digital Access and resolve historic indirect exposure — is a significant commercial driver for ECC customers. For full analysis of this critical topic, see our SAP indirect access guide.
Before any SAP negotiation, audit, or renewal conversation, conduct an independent assessment of your indirect access exposure. Entering a negotiation with undisclosed compliance gaps significantly weakens your position and can result in audit claims that dwarf any licence savings you achieve. Know your exposure before SAP does.
SAP's end-of-mainstream-maintenance for SAP ECC was originally set for 2025, then extended to 2027, with extended maintenance available (at a premium) until 2030 or beyond under certain support packages. This timeline creates the most significant commercial leverage point for ECC customers in the history of SAP licensing.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
SAP needs its ECC customer base to migrate to S/4HANA — both for its own revenue model (cloud subscription versus one-time perpetual licence plus maintenance) and to reduce the legacy support burden that comes with maintaining ECC. This strategic need translates into a willingness to offer substantial commercial incentives to secure migration commitments: new S/4HANA licence discounts, maintenance credits, migration funding, implementation subsidies, and BTP credits.
The leverage window is not indefinite. Organisations that delay migration decision until 2026 or 2027 — under the pressure of approaching maintenance end — will negotiate from a weaker position than those who engage SAP proactively in 2024–2025 with genuine competitive analysis and a credible alternative evaluation in progress. SAP's incentives reduce as the end-of-maintenance deadline approaches, because the commercial urgency has largely been resolved for SAP once the customer has no choice but to migrate or pay premium extended support.
The strongest migration negotiations involve a genuine evaluation of migration paths — S/4HANA on-premises, S/4HANA Cloud Private Edition (via RISE), S/4HANA Cloud Public Edition, or competitive alternatives including Oracle ERP Cloud or Infor. Having a credible alternative path — even if S/4HANA is your preferred destination — fundamentally changes the commercial dynamic. For detailed migration negotiation tactics, see our S/4HANA migration negotiation guide.
The most consistently successful SAP migration negotiations begin 18–24 months before any planned go-live, with a formal competitive evaluation in progress. SAP account teams respond to structured procurement processes with executive sponsorship very differently from bilateral renewal conversations — the former signals that the customer is genuinely considering alternatives, which unlocks commercial flexibility that bilateral conversations rarely surface.
RISE with SAP is SAP's bundled cloud transformation offering, introduced in 2021 as SAP's answer to the question of how to move large ECC estates to cloud without requiring customers to navigate the full complexity of a traditional cloud migration project. RISE packages S/4HANA Cloud Private Edition (the hosted, single-tenant version of S/4HANA), SAP BTP, application lifecycle management, infrastructure (running on hyperscaler of choice), and support into a single subscription agreement with SAP as the prime contractor.
For organisations that value commercial simplicity, RISE reduces the number of contracts — eliminating separate hyperscaler agreements, infrastructure management, and some application management overhead. For organisations that value flexibility and control, RISE represents a significant long-term commitment at pricing that is not always competitive with equivalent buy-your-own-parts approaches.
RISE pricing is not standardised — it is negotiated based on organisation size, current SAP landscape, migration timeline, and competitive context. SAP's list prices for RISE are a starting point, not a ceiling. Large enterprises consistently achieve 20–40% discounts from RISE list pricing when engaging with appropriate negotiation support. The key commercial variables are: subscription term length, bundled BTP consumption levels, SLA commitments, data sovereignty provisions, and exit rights at contract end.
Exit rights deserve particular attention. RISE contracts can create significant data portability challenges if you later wish to migrate to a different SAP environment or exit SAP entirely. Negotiate exit assistance obligations, data export provisions, and transition support requirements into the original contract rather than attempting to address them at renewal. See our full RISE commercial analysis at SAP RISE review.
| Approach | Commercial Control | Infrastructure Flexibility | Negotiation Complexity | Typical Cost vs RISE |
|---|---|---|---|---|
| RISE with SAP | Low — bundled | Moderate | Lower | Baseline |
| S/4HANA on hyperscaler (self-managed) | High | High | Higher | 10–25% lower |
| S/4HANA on-premises | Full | Full | Moderate | Potentially lower (capex) |
| S/4HANA Cloud Public Edition | Lowest | Lowest (SaaS) | Lowest | Variable |
SAP maintenance — charged annually at 22% of the net licence value — is frequently the largest line item in an enterprise SAP budget. For organisations with large perpetual licence estates accumulated over many years, annual maintenance can run to millions of dollars for licences that were purchased at full price and may no longer reflect actual usage or business value.
The most immediate lever for maintenance reduction is licence rationalisation — identifying and retiring licences that are no longer required before the annual maintenance calculation date. This requires a thorough user access review against actual SAP system activity logs. In our experience, organisations typically find 10–25% of their named user population either entirely inactive or classifiable at a lower (and therefore cheaper) user type. Converting or retiring these licences before renewal reduces the maintenance base for all future years.
SAP's standard 22% maintenance rate is a starting point, not a fixed obligation. In the context of S/4HANA migration discussions, SAP regularly agrees to maintenance rate caps (freezing the rate below 22%), maintenance credits that can be applied against migration costs, or reduction in the maintenance base through agreed licence returns. These commitments are rarely offered proactively — they require explicit negotiation as part of a migration conversation. For a step-by-step approach to maintenance cost reduction without moving to third-party support, see our guide on reducing SAP maintenance costs.
Third-party support providers — most notably Rimini Street — offer SAP support at approximately 50% of SAP's maintenance rate, covering break-fix support, regulatory updates, and performance tuning for the existing licence estate. For organisations that have stabilised their SAP implementation and have no near-term plans to adopt new SAP functionality, third-party support represents a significant cost reduction opportunity.
The risks are equally significant: moving to third-party support typically means losing access to new SAP innovation, restricts your ability to run certain SAP cloud services that require active maintenance, and may affect your ability to migrate to S/4HANA under your existing licence terms. Organisations considering third-party support as a permanent strategy (rather than a tactical bridge) should obtain independent legal advice on the contract implications before making the switch.
Concerned about your SAP maintenance costs or upcoming renewal?
SAP conducts licence audits through its Global License Audit and Compliance (GLAC) team, which operates separately from the account management relationship. Understanding the audit process — and how to manage it strategically — is essential for any enterprise SAP customer.
SAP initiates audits for a range of reasons: scheduled compliance reviews under standard EULA terms, commercial intelligence suggesting under-licensing (often surfaced through account team conversations or partner reports), ahead of renewal discussions to establish a compliance baseline, following a business acquisition, or as a direct commercial tactic when a customer is exploring competitive alternatives. Understanding the context of an audit notice helps you calibrate your response strategy.
The audit rights in SAP's standard EULA give SAP the right to audit compliance, but they do not give SAP unlimited access. You have the right to negotiate the audit scope (what systems and periods are in scope), the audit methodology (how usage is measured), and who conducts the audit (SAP directly or an agreed independent third party). You also have the right to conduct your own internal compliance review before the audit commences — and this is strongly recommended, as it enables you to identify and remediate exposure before the formal audit finds it.
On receiving an SAP audit notice, your first call should be to external legal counsel experienced in software licensing — not to your SAP account team. The audit and commercial teams at SAP operate with different objectives, and information shared with one will reach the other. Engage a specialist before making any response to SAP.
Audit findings are almost always subject to commercial negotiation. SAP's initial audit claim is a calculated position, not a final number. Experienced SAP licensing advisors consistently reduce initial audit findings by challenging the measurement methodology, disputing user classification decisions, negotiating conversion of audit liability into migration commitments, and using the audit settlement as leverage for broader commercial improvements in the subsequent agreement. For a comprehensive audit response playbook, see our SAP audit defence guide.
SAP is a sophisticated commercial counterparty with highly trained account teams, deep knowledge of their own licensing model, and significant information advantages. Effective SAP negotiation requires preparation, competitive alternatives, and the ability to execute credibly on alternative scenarios. The following tactics represent the most consistently effective approaches across enterprise SAP negotiations.
The SAP Business Technology Platform (BTP) is SAP's strategic cloud platform for integration, extension, data management, and AI applications. Its licensing model operates on cloud credits — you purchase a pool of credits and consume them across BTP services as used. This model offers flexibility but creates cost management challenges that traditional software budgeting is not designed to handle.
BTP credits are consumed at different rates depending on the service — Integration Suite, Extension Suite, Data and Analytics, ABAP Cloud, and AI and ML services all have different credit consumption rates. The most common BTP cost management failure is deploying BTP broadly across an enterprise without metering consumption, resulting in credit pools exhausted months before contract renewal. SAP then offers top-up credits at standard (non-committed) pricing, which can be 30–50% more expensive than committed rates.
For a detailed analysis of BTP pricing and optimisation strategies, see our dedicated guide on SAP BTP licensing.
RISE agreements include a BTP credit entitlement, but the level is frequently insufficient for organisations that intend to use BTP substantively for integration and extension scenarios. Negotiate the BTP credit level in your RISE agreement carefully — the default bundle is typically designed for minimal BTP usage, not for organisations planning to run Integration Suite as their primary middleware platform or to develop significant custom extensions via ABAP Cloud.
This pillar guide covers the strategic landscape of SAP licensing. For detailed analysis of specific topics, explore the articles in our SAP Licensing & Negotiation series:
The firms on our ranked list have collectively saved enterprise clients hundreds of millions in SAP licensing costs. Let us connect you with the right specialist for your situation.