S/4HANA licensing, three meters, one bill
S/4HANA licensing looks complex because it stacks three independent models: the Full User Equivalent metric for people, the digital access document model for machines, and the RISE versus on premise delivery choice that reprices both. Get each meter right and the bill is predictable. Get one wrong and the error compounds across the term.
Prepared by Redress Compliance · August 6, 2026 · SAP licensing advisory. Based on 30 to 40 S/4HANA licensing reviews run 2024 to 2026.
Executive summary
The user meter is the FUE. S/4HANA prices people through Full User Equivalents, a weighted single metric replacing the legacy named user tiers: advanced users at full weight, functional users at a fifth, self service at a thirtieth. The weighting makes classification the lever: across our reviews, 20 to 35 percent of professional users were misclassified and qualified for a lighter, cheaper type, the single largest recovery on the user side.
The machine meter is digital access. Indirect use, other systems creating documents in S/4HANA through interfaces, prices by counted document type, not by the connected system. The counts are measurable, which cuts both ways: the first SAP estimate ran 30 to 50 percent above the defensible counted figure in our reviews, and buyers who counted first negotiated against their own number.
The delivery choice reprices everything. RISE bundles license, infrastructure, and support into one indexed subscription; on premise keeps the perpetual license plus the standard 22 percent maintenance base. Neither is universally cheaper, and the conversion moment is where every classification error inherited from ECC becomes permanent. Buyers who modeled both paths before talking to SAP held materially more negotiating room, whichever they chose.
The reviews say the stack is winnable: in the large majority of the 30 to 40 estates we reviewed, the buyer was over licensed against actual usage, across all three meters at once. The sequence that recovers it is always the same: classify the users from evidence, count the documents yourself, and model both delivery paths before the order form is drafted.
Meter one, users in Full User Equivalents
The FUE construct weights each user by the depth of access their role needs and sums the weights into the contracted count. The ratios are fixed, one advanced user per FUE, five functional, thirty self service, and the mechanics, the pooling, the floors, and the drift clauses, are worked in the FUE licensing guide. What matters at the S/4HANA level is the classification, because SAP's default lands legacy Professional users in the heaviest bucket wholesale.
The recovery is behavioral evidence: per user transaction history classified against the contract's tier definitions, covered in the user types guide. In our reviews it moved 20 to 35 percent of professionals to lighter types and cut weighted totals 10 to 25 percent, with no one losing access they used.
Meter two, digital access and the document count
Digital access prices what connected systems do, not what they are: nine document types, sales orders, invoices, purchase orders and the rest, counted when an external system creates them in S/4HANA through an interface. The model replaced the indirect use lawsuits era with a meter, and the meter rewards whoever counts first:
- The estimate is an offer, not a measurement. First SAP estimates ran 30 to 50 percent above the defensible counted figure in our reviews, built on interface inventories rather than actual document creation.
- SAP's own measurement tooling produces the real number, and running it yourself, with the double counting and technical document exclusions applied, is the negotiation position.
- The conversion programs are negotiable events. Digital access adoption deals trade document licensing against the wider S/4HANA commitment, and they price best when your count is on the table.
The SAP RISE negotiation guide
The RISE pricing benchmarks, the CVR framework, the digital access posture, and the buyer side moves across the full SAP estate. The reference for every number in this guide.
Get the white paper →The full pricing mechanics sit in the digital access pricing analysis, including the document type rates and the estimation traps.
Meter three, RISE versus on premise
The delivery choice is a repricing of the whole estate, and both paths carry structures the other lacks:
| RISE with SAP | On premise S/4HANA | |
|---|---|---|
| What you buy | One subscription bundling license, infrastructure, and support, priced in FUEs | Perpetual license plus infrastructure you run, priced in FUEs at signature |
| The recurring cost | The indexed subscription, with its escalator and renewal baseline | The 22 percent annual maintenance base on the license value |
| Where it wins | Estates shedding infrastructure operations, and conversions negotiated with full entitlement credit | Estates with sunk infrastructure discipline and long horizons, keeping the perpetual asset |
| The trap | The conversion inherits every classification error at subscription rates, forever | Maintenance on shelfware, and the drumbeat of RISE repricing pressure at every renewal |
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across S/4HANA reviews, 2024 to 2026
Across roughly 30 to 40 S/4HANA licensing reviews between 2024 and 2026, the buyer was over licensed against actual usage in the large majority of estates, and the three meters failed in the same ways:
Professionals whose transaction history qualified them for lighter types, carried at full weight since the ECC conversion.
The gap between SAP's first document estimate and the defensible counted figure, in SAP's favor every time.
The compounding is what makes the stack expensive: a misclassified user base converted to RISE at the wrong FUE count, with an uncounted digital access estimate folded in, locks all three errors into one indexed subscription. The estates that avoided it treated the conversion as the audit: everything measured before anything signed, with the ECC migration playbook as the sequence and the audit defense framework as the evidence standard.
Your first five moves
- Classify the users from transaction evidence against the contract tier definitions, and take the 10 to 25 percent FUE reduction into the negotiation.
- Count digital access documents yourself with the measurement tooling, exclusions applied, before responding to any estimate.
- Model RISE and on premise both, with entitlement credit, escalators, and the maintenance base priced, whichever way you lean.
- Negotiate the three meters as one package: the FUE count, the document position, and the delivery terms trade against each other at the conversion moment and nowhere else.
- Write the drift protections into the order form: reclassification rights, renewal baselines, and escalator caps. The SAP practice and the RISE benchmarks run the numbers with you, on your side of the table.
Frequently asked questions
How does SAP S/4HANA licensing work?
Three stacked models priced separately: users in Full User Equivalents, a weighted metric where advanced users count full, functional a fifth, and self service a thirtieth; digital access, pricing indirect use by counted document types; and the delivery choice between the RISE subscription and perpetual on premise licensing with 22 percent annual maintenance.
What is the biggest lever on S/4HANA licensing cost?
User reclassification. Twenty to 35 percent of professional users in our reviews qualified for lighter, cheaper types on their actual transaction history, cutting weighted FUE totals 10 to 25 percent with no access loss. The digital access count and the delivery model negotiation follow close behind.
What is SAP digital access and how is it priced?
The model for indirect use: when external systems create documents in S/4HANA through interfaces, the documents, nine defined types, are counted and licensed, regardless of which system created them. First SAP estimates ran 30 to 50 percent above defensible counted figures in our reviews, so measuring before negotiating is the entire game.
Is RISE cheaper than on premise S/4HANA?
Neither is universally cheaper. RISE bundles license, infrastructure, and support into one indexed subscription; on premise keeps the perpetual asset plus 22 percent maintenance and your own infrastructure. The answer depends on the estate, and modeling both paths before engaging SAP held material negotiating room in our reviews, whichever path the buyer chose.
What happens to licensing errors during an S/4HANA conversion?
They become permanent. A misclassified user base converts at the wrong FUE count, an uncounted digital access estimate folds into the subscription, and the indexed escalator compounds both for the term. The conversion moment is the one chance to fix the meters, which is why everything should be measured before anything is signed.
Do we still pay maintenance on S/4HANA on premise?
Yes, the standard 22 percent annual maintenance base on the license value, which is the recurring cost RISE re-wraps into its subscription. On premise estates should also reconcile maintenance against deployed licenses, because maintenance on shelfware is one of the quietest recurring losses in the SAP estate.
