SAP S/4HANA licensing in 2026. Users, documents and delivery on one bill.

S/4HANA licensing stacks three models: users priced by type, digital access priced by counted documents, and the RISE or on premises choice that reprices both. Measure each one yourself before the conversion, because errors signed there last the whole term.

How does SAP S/4HANA licensing work?

SAP S/4HANA licensing charges you through three separate models that land on one bill. People are licensed by user type, external systems that create documents in S/4HANA are licensed through digital access, and the delivery choice between RISE with SAP and on premises reprices both.

Each model has its own definitions and its own measurement, so SAP prices them separately. Negotiate them together anyway: at the conversion from ECC they trade against each other and against your overall commitment.

How are users licensed in SAP S/4HANA?

In RISE with SAP and S/4HANA Cloud, users are counted in Full User Equivalents (FUEs), one weighted metric that replaced the legacy named user types. Each use type carries a fixed weight.

• Advanced use. One user counts as one FUE.
• Core use. Five users count as one FUE, so each weighs a fifth. You will still see this tier called functional use, after the nearest on premises category.
• Self service use. Thirty users count as one FUE, so each weighs a thirtieth.

On premises, S/4HANA is still sold as named users in Professional, Functional and Productivity use categories, plus Developer access. The categories differ between the two models, yet the pricing logic matches: the more a user type allows, the more each person in it costs.

The ratios themselves never move in a negotiation. The mechanics around them, including pooling, floors and the clauses that let the count drift upward, are worked through in our FUE licensing guide.

Why does classification drive the user bill?

Because the weights are fixed, the one variable you control is which type each person sits in. SAP's default conversion lands legacy ECC Professional users in advanced use wholesale, even though SAP's own 2021 RISE licensing overview maps Professional users to advanced or core use depending on the role.

The correction is behavioral evidence: each user's transaction history, classified against the use type definitions in your contract. Our user types guide covers those definitions. In our reviews this moved 20 to 35 percent of professional users to lighter types and cut weighted totals by 10 to 25 percent, and no one lost access they used.

What does reclassification look like in numbers?

Say you run 2,000 ECC users: 600 Professional, 200 Limited Professional and 1,200 Employee users. Employee users map to self service in SAP's 2021 overview, and we assume the Limited Professional users land in core use. That leaves the 600 Professional users to argue over. Suppose 150 of them, a quarter, only work inside one operational area.

The evidence based count is 120 FUE lower, about 18 percent below the default mapping, which sits in the middle of what we usually find. Every renewal priced from 680 instead of 560 carries that difference forward. Run your own population through the FUE calculator before the first quote meeting.

How is SAP digital access priced?

Digital access prices what connected systems do in S/4HANA. When an external system creates one of nine document types through an interface, that document is counted and licensed, whichever system created it. Only the initial creation is licensed. Reads, updates and deletions are not.

• Weighted at 1. Sales, invoice, purchase, service and maintenance, manufacturing, quality management and time management documents.
• Weighted at 0.2. Financial documents and material documents.
• Counted per line item. Sales, invoice, purchase, financial and material documents, so one order with ten lines counts as ten.

The model replaced the era of indirect use lawsuits with a meter, and whichever side produces the count first sets the starting point for the negotiation. The per document rates and the estimation traps are covered in our digital access pricing analysis, and the document definitions in our guide to the digital access document model.

Why is SAP's first digital access estimate usually too high?

Treat SAP's first estimate as an opening offer. In our reviews it ran 30 to 50 percent above the figure a careful count supported, because it was built from interface inventories rather than from documents actually created. An interface list shows a connection exists, not how many documents it creates.

How do you count digital access documents yourself?

Use SAP's own measurement tooling and run it before SAP does. The estimation tool for S/4HANA comes with SAP Note 2644172, and the ECC version with SAP Note 2644139. Then apply the exclusions and weighting before any figure leaves your team. Our overview of digital access measurement tools covers setup.

• Double counting. Remove documents that appear more than once in the output.
• Technical documents. Exclude documents the tool picks up that your contract definitions do not count.
• Weighting. Apply the 0.2 factor to financial and material document line items.
• Creation only. Strip out changes to existing documents, which the licensing terms do not count.

The weighting alone changes the picture. Say your interfaces create 400,000 sales document line items, 1,500,000 financial document line items and 500,000 material document line items over 12 months. Weighted correctly that is 400,000 plus 300,000 plus 100,000, or 800,000 documents, while a count at full weight shows 2,400,000.

Should you take a digital access adoption offer?

Treat any adoption offer as a negotiable event. These deals trade document licensing against the wider S/4HANA commitment, and they price best when your own count is on the table. SAP's published 2020 terms for its Digital Access Adoption Program offered two routes.

• Growth option. License at least 115 percent of your estimated document use and pay fees only on the growth portion.
• Discount option. License at least 100 percent of estimated document use and receive a 90 percent discount on digital access.

Both routes start from estimated document use, so an inflated estimate raises the floor of either deal.

Is RISE with SAP cheaper than S/4HANA on premises?

Neither path is cheaper for every company. RISE bundles license, infrastructure and support into one indexed subscription priced in FUEs. On premises keeps the perpetual license, bought as named users, with annual maintenance on top and infrastructure you run yourself.

Why we push back on signing early to beat the 2027 deadline

The usual advice is to sign a RISE conversion quickly because ECC mainstream maintenance ends in 2027. We disagree with signing on that timetable alone. SAP provides mainstream maintenance for Business Suite 7 core applications until the end of 2027, and optional extended maintenance until the end of 2030 at a premium of 2 percentage points on the maintenance base.

Compare that premium with the cost of a subscription that carries an oversized FUE count and an inflated document estimate for its full term. Start the conversion when your counts are ready, and keep extended maintenance as your fallback if a quarter end offer is poor. Our 2027 maintenance strategy guide sets out the options.

What does on premises maintenance cost over time?

SAP's standard maintenance runs at 22 percent of license value every year, whether or not a license is still deployed. Reconcile the maintenance base against the licenses you use before each renewal, and ask SAP in writing how unused licenses can be retired from it. Our SAP support and maintenance guide covers the options.

Why do S/4HANA conversion errors last the whole contract term?

Because the conversion order form becomes the baseline for everything after it. A misclassified user base converts at the wrong FUE count, an uncounted digital access estimate is absorbed into the subscription, and the indexed escalator compounds both for the term.

• Users. In the 2,000 user example above, the default mapping carries 120 extra FUEs. Over a five year term that is 600 FUE years paid for access no one uses.
• Escalation. Every annual increase applies to those extra FUEs as well, so the cost of the error grows each year.
• Renewal. The signed count becomes the starting point for the next renewal, and SAP has little reason to reopen it in your favor.

Treat the conversion as your own audit, with everything measured before anything is signed. Our ECC to S/4HANA migration guide gives the sequence, and our SAP audit defense guide sets the standard of evidence your classification and document counts should meet.

Which mistakes cost the most at conversion?

• Accepting the role based mapping. A role export shows what people could do. Transaction history shows what they do, and only that supports a lighter type.
• Answering the digital access estimate with a discount request. A discount on an inflated count still pays for documents that were never created. Answer with a count.
• Measuring over a short window. A sample that misses quarter end and year end close understates who needs advanced access, and the next metering run or audit will find the gap.

What have we seen in S/4HANA licensing reviews from 2024 to 2026?

Across roughly 30 to 40 S/4HANA licensing reviews between 2024 and 2026, the customer was over licensed against actual usage in the large majority of cases. The excess showed up in all three models at the same time, and it followed the same pattern each time.

• Users in the wrong tier. Professionals whose transaction history qualified them for lighter types had been carried at full weight since the ECC conversion.
• Document estimates above the count. The gap between SAP's first digital access estimate and the counted figure fell in SAP's favor every time.
• One path modeled. Customers who had modeled RISE and on premises before talking to SAP held materially more negotiating room, whichever path they chose.

A misclassified user base, converted to RISE at the wrong FUE count with an uncounted document estimate folded in, locks all three errors into one indexed subscription.

The customers who avoided that outcome followed one order of work. They classified users from evidence, counted the documents themselves and modeled both delivery paths before SAP drafted the order form.

What will the SAP account team say, and how should you answer?

Expect some version of these four lines. Each reply returns the discussion to your own numbers.

• "Professional users map to advanced use. That is the standard conversion." SAP's own RISE licensing overview maps Professional users to advanced or core use depending on the role. We will classify each user from transaction history against the contract definitions and send you the result.
• "Our digital access estimate reflects your interfaces." An interface list does not count documents. We are running the estimation tool from SAP Note 2644172 and will share the counted figure with exclusions and weighting applied.
• "RISE includes infrastructure and support, so the cost comparison always favors it." Then it will hold up in a like for like model. Price both paths on the same user count, document position and term, and show us the escalator.
• "The conversion incentive expires at quarter end." Our timetable follows our counts and SAP's maintenance dates, and extended maintenance runs to the end of 2030. We will sign when all three meters are agreed.

Which S/4HANA contract terms should you ask for?

Ask for the terms that stop the count drifting upward after signature, and put each one in the order form, where it binds. Our RISE pricing benchmarks show where rates and escalators tend to land.

• Reclassification rights. The right to move users to a lighter type during the term when their usage changes, so the count can fall as well as rise.
• Renewal baseline. Renewal pricing based on the FUE count in use at renewal. Without it, the highest count reached during the term tends to become the new starting point.
• Escalator cap. A ceiling on the annual subscription increase, written as a number, covering the initial term and the first renewal.
• Entitlement credit. Credit for your existing ECC licenses and maintenance, stated line by line in the conversion order form.
• Digital access counting rules. The exclusions and weighting you measured against, attached to the contract, so a later audit counts the same way you did.

What to do next

1. Classify users from transaction evidence. Measure against the contract use type definitions over a full business cycle, and take the resulting FUE reduction into the negotiation.
2. Count digital access documents yourself. Run SAP's estimation tool, apply the exclusions and the 0.2 weighting, and do it before you respond to any SAP estimate.
3. Model RISE and on premises side by side. Price entitlement credit, escalators and the maintenance base on both paths over the same term.
4. Negotiate the three meters as one package. The FUE count, the document position and the delivery terms trade against each other at the conversion and at no other point.
5. Write the drift protections into the order form. Reclassification rights, a renewal baseline and an escalator cap.
6. Bring in support where you need it. Our SAP practice runs the classification, the document count and the TCO comparison with you, working only for the customer.

Frequently asked questions