SAP licensing has never been a casual line item. It shapes how you deploy SAP, scale it, budget for it over the next decade, and how exposed you are during an audit. And yet, for many organisations, the conversation only starts when a contract renewal or migration project forces it.
That timing is rarely ideal. With mainstream maintenance for SAP ECC 6.0 ending on 31 December 2027, and extended maintenance running only through 2030 at a premium, every business still on a legacy SAP estate is now actively choosing or being pushed into a new licensing model. The decisions made over the next 18 to 24 months will define IT budgets, deployment models, and operational flexibility for years to come.
This guide breaks down the SAP licensing models in use today, the core SAP license types within each, and a practical framework for choosing the right one for your business.
Why SAP Licensing Looks Different in 2026
SAP’s licensing portfolio has shifted dramatically in recent years. Three forces are driving the change:
- The cloud transition. SAP is steering customers toward S/4HANA Cloud through two flagship subscription packages, RISE with SAP and GROW with SAP, and away from perpetual on-premise licences.
- The 2027 migration deadline. Customers using ECC software need to consider their choices, including the possibility of migration, extended maintenance services, or even opting for a cloud-migration strategy. Each choice would entail different licensing considerations.
- Direct Access change. SAP launched its Digital Access initiative in 2018, which replaced the convoluted process of licensing named users for any indirect integrations. It has become standard in all new license agreements.
This has developed a diverse mix of perpetual licenses, subscription models, and consumption-based agreements in many organizations.
Main SAP Licensing Models
- Perpetual (On-Premise) Licensing
This is the classic model that powered ECC and still applies to S/4HANA on-premise. Customers pay a one-time licence fee, then 19–22% of that licence value annually for maintenance.
Within it, two SAP license types coexist:
Licences for Named Users. Each person accessing SAP must have their own licence. SAP provides various categories such as Professional (entire function access), Functional or Limited Professional (roles or module access), Productivity or Employee Self-Service (minimal function access), and Developer. The cost is dependent on the category of licence; a Professional licence will cost US$3,000, whereas a self-service one will be much cheaper.
– Package and Engine licences:
Advanced Warehouse Management, APO, certain modules of HCM, etc., can be examples of applications where transaction volume, head count, revenue, or some other metric of the engine is used as a criterion for licensing, instead of using the number of users to license them.
If the organisation values ownership, utilises extensively customised landscapes, and prefers CapEx accounting, then perpetual licensing can make sense. The downside is the overhead cost. You own the infrastructure, the upgrade costs, and the audit risk.
- RISE with SAP
Launched in 2021, RISE with SAP is positioned as “business transformation as a service.” It bundles S/4HANA Cloud public or private edition with infrastructure hosting, technical managed services, business process intelligence (Signavio), SAP Business Technology Platform credits, and Business Network access into a single subscription contract.
The pricing is pegged on Full User Equivalents (FUE), a common measure used to consolidate all kinds of licenses for SAP into one.
The calculation of FUE is as follows:
one Professional user = 1.0 FUE;
one Functional user = 0.5 FUE;
and one self-service user = approximately 0.033 (meaning that 30 ESS users will be equivalent to 1 FUE).
RISE agreements are highly negotiable, lasting between 3 and 5 years.
RISE fits enterprises with complex requirements, sizable existing SAP investments, regulated environments that need private-cloud control, or transformation programmes that demand customisation. The premium price reflects the breadth of what is bundled into a single fee.
- GROW with SAP
GROW with SAP launched in 2023 for an alternative target market: mid-market and greenfield companies looking for SAP S/4HANA Cloud – public edition alone and without the intricacies of RISE. This product line has two pre-configured editions, namely Base and Premium, with clear-tiered pricing per FUEL
GROW is faster to deploy, runs on SAP best-practice processes, and removes much of the negotiation overhead. The trade-off is flexibility. You adopt SAP’s standard processes rather than redesigning them, and you sit on SAP’s quarterly upgrade cycle. For most SMBs and organisations with fewer than roughly 500 users, GROW is the more cost-effective path to cloud ERP.
- Digital Access (Indirect Use)
Digital Access is not an architecture but a measure, where integration and interaction between non-SAP systems and SAP becomes the focal point of concern. The previous approach to licensing, called the named-user approach, would require every user or system connected with SAP to have the Named User license.
Digital Access shifts the basis of licensing from who accesses SAP to what gets created in it. SAP defines nine document types: sales orders, invoices, purchase orders, and so on, and customers license a volume of these documents per year.
This is now the default for new S/4HANA contracts and is built into RISE and GROW subscriptions, though customers on legacy ECC contracts may still operate under the older named-user model.
How to Choose the Right SAP License for Your Business
There is no universally preferred SAP licensing model. This largely depends on the following five considerations:
- Complexity and size. For small to mid-sized organizations, those with well-established processes, and those without any customizations, GROW seems preferable. Whereas, for big enterprises, regulated sectors, and highly customized organizations, the option between RISE and S/4HANA on-premise becomes more favorable.
- Existing SAP environment. If the company possesses perpetual licensing, then RISE offers support for the conversion of these contracts, accounting for any investments made previously. Nonetheless, this is not a point of relevance in greenfield scenarios, since there is no prior history to account for in this context.
- Requirements for customization. In public-cloud versions (GROW and RISE public), customization can only be made in extension layers and SAP BTP. In the private-cloud version of RISE and the on-premise S/4HANA version, customization can be more intensive.
- Integration landscape. The more you depend upon third-party solutions, eCommerce, or the Internet of Things (IoT), the greater the likelihood that you will face Digital Access hazards. Plan for integrations from the beginning; volumes of documentation could have an impact in the commercial world.
This entails the use of a continuous cycle model that produces an initial expenditure known as CapEx. On the other hand, in the subscription model, such costs become OpEx costs that recur every year.
A practical stepwise approach would be applicable to most alliances, where they first determine the delivery model (whether cloud or on-premise, whether public or private), followed by mapping the user populations based on either FUE or Named User units, followed by quantification of digital access risk, followed by negotiation. Moving directly to commercial negotiations will certainly lead to missed opportunities.
A Few Pitfalls Worth Avoiding
– Assuming a less diverse user population. The analytics capabilities of SAP may be inclined toward overstating the user count. Ensure that those with lighter utilization are categorized properly so that you do not end up paying for the Professional plan based on self-service consumption.
-Ignoring the fact that escalation clauses are a reality. Subscription services typically have provisions where pricing can escalate annually. Escalation clauses should be capped at the time of contract signing.
– Neglecting Digital Access considerations. Workloads vary significantly depending on the company’s performance. Plan for volume fluctuations and agree on a true-up mechanism prior to signing.
– Deferring until 2027 to make a choice. Migration efforts made out of desperation are almost certain to result in higher costs than when undertaken through careful planning. Begin your assessment process right away.
Conclusion
SAP Licensing has progressed beyond a simple purchasing function to becoming a strategic choice influencing the implementation, expenditure, and risks associated with it over several years.
Choosing the correct SAP License Model will take into account the way your organization currently operates and the manner it is projected to operate, as well as its scalability, which may differ greatly between a 200-user company in manufacturing versus a multinational running 50 factories and complex integrations.
Being familiar with the SAP license types like the Named User License, Package/Engine Licenses, RISE License, GROW License, and the Digital Access License will set you on the right path.
The trick lies in selecting the model that suits your needs with respect to the size and complexity of your organization and how you will budget for the same. Otherwise, your licensing model might slowly rob you of its value.




