Contents
Key takeawaysHow S/4HANA is pricedThe FUE metricCosts beyond the licenseWhat we have seenNegotiating the priceTerms that protect the pricePreparation timelineWhat to do nextFAQSAP S/4HANA pricing in 2026 rests on the Full Use Equivalent user count, the modules you run and the documents your other systems create. The headline rate SAP leads with matters less than any of them.
- The user count drives the price. The FUE count, or the named user mix on premises, shifts the bill more than the headline discount does.
- Documents are charged separately. Digital access charges for documents that non SAP systems create in S/4HANA, and first quotes often leave it blank.
- Neither deployment is cheaper by default. Cloud and on premises each win in some cases, and the run rate over the term decides which.
- Preparation closes the gap. Buyers who bring their own count and document baseline sign well below SAP's first quote.
- The default classification favors SAP. An independent count built from usage data shows where SAP has placed users in heavier types than their work requires.
- Year three is the real price. Model the run rate after migration credits expire and the renewal uplift starts to apply.
How is SAP S/4HANA priced in 2026?
SAP S/4HANA is priced in layers. The user count comes first, then the modules and the database, then the digital access charge for documents your other systems create. The headline rate SAP leads with is applied to that stack, so the stack decides most of what you pay.
The metric depends on how you buy. In the cloud editions, including RISE with SAP, users are counted in Full Use Equivalents (FUE) and paid as a subscription. On premises, S/4HANA licenses are still sold as named user types, such as Professional Use, Functional Use and Productivity Use, with annual support on top.
The FUE user count
The Full Use Equivalent count blends user types into one number. Heavier types weigh more, so the mix of users sets the base price. On premises the same logic applies through the named user types, where Professional Use carries broader rights and a higher price than Productivity Use.
Modules and database
Each module and the HANA database add to the base. Right sizing the modules to what you actually run removes spend you never needed.
On premises, SAP's own licensing material prices the HANA runtime database at 15 percent of the HANA SAP Application Value, while a full use HANA license is priced by memory. Runtime is cheaper but limits what else can run on that database.
Cloud or on premises
A RISE subscription bundles the software, the infrastructure and SAP's technical operations into one annual fee. On premises keeps capital control, since you buy perpetual licenses once and then pay support every year.
SAP's published list rate for Enterprise Support on new on premises purchases has been 22 percent of the license value per year. Compare the run rate over the full term, with every credit and uplift in its year.
- Users. The FUE count, or the named user mix on premises, is the largest single line.
- Modules. Only the modules and industry add ons you run should sit in the base.
- Database. HANA sizing should match real data volume, and runtime against full use should be a deliberate choice.
- Documents. Digital access volume belongs in the first quote, with a number against it.
For the full comparison of the two deployment routes, see our guide to RISE against S/4HANA on premises and the detail on HANA runtime and full use licensing.
S/4HANA Negotiations: The Discount Is Dead. The Tier Is the Deal.
What is the FUE metric and how does it change the bill?
The FUE metric decides how much each user costs. SAP fixes the weights in its service use descriptions, so the question that stays open is which type each person is classified into. Classify users upward and the whole bill inflates, every year of the term.
| Use type | Users per FUE | Typical activity |
|---|---|---|
| Advanced use | 1 user per FUE | Broad create, change and configuration rights across functions |
| Core use | 5 users per FUE | Operational transactions within a defined scope |
| Self service use | 30 users per FUE | Own data, requests, approvals and simple reporting |
| Developer access | Each developer counts as 2 FUE | Development and technical access |
User types matter
An advanced user costs five times a core user and thirty times a self service user, and each developer costs twice an advanced user. Match each person to the lightest type their activity allows. A planner who only posts confirmations in one area belongs in core use, however wide the role assigned in the system happens to be.
Build an independent count
Model the count from real usage before SAP proposes one. Your own number becomes the reference point for the whole negotiation, and SAP then has to explain each user it wants to move up. Our FUE calculator and the FUE calculation guide walk through the method.
A worked example of a remapped count
Say a company has 2,000 people who need S/4HANA access, and SAP's first quote classifies them from their current authorization roles. The independent remap classifies the same 2,000 people from twelve months of transaction usage. The figures below are hypothetical and show the arithmetic only.
| Use type | First quote users | First quote FUE | Remap users | Remap FUE |
|---|---|---|---|---|
| Advanced use | 400 | 400.0 | 280 | 280.0 |
| Core use | 900 | 180.0 | 780 | 156.0 |
| Self service use | 700 | 23.3 | 940 | 31.3 |
| Total | 2,000 | 604 | 2,000 | 468 |
The remap removes 136 FUE, about 23 percent of the quoted count, without a single person losing access. At an illustrative rate of $1,500 per FUE per year, used here only to show scale, that is $204,000 a year and $1,020,000 over a five year term, before any discount is applied.
SAP RISE Negotiation Guide
Pricing benchmarks and contract terms for RISE with SAP and S/4HANA deals.
Get the white paper →Where do S/4HANA costs hide beyond the license?
Four costs sit outside the visible license line: digital access, integration rework, data migration and the renewal uplift. Together with the run rate once migration credits expire, they decide the real total over the term.
Digital access
Documents created in SAP by non SAP systems count under digital access. SAP counts nine document types: sales, purchase, invoice, manufacturing, material, quality management, service and maintenance, financial, and time management documents. Only creation counts, so reads, updates and documents SAP generates automatically from a counted one are excluded.
Measure the volume yourself before SAP raises it, integration by integration. An ecommerce platform posting sales orders or a supplier portal creating purchase orders can each create documents in the millions over a term when order volumes are high. Our digital access guide covers the counting rules in detail.
Integration rework and data migration
These are project costs rather than license lines, but they belong in the same model. Interfaces rebuilt for S/4HANA are also the moment document flows change, which changes the digital access number. Data migration scope decides how much history lands in HANA, and that feeds the database sizing.
The year three run rate
Migration credits and first year incentives flatter year one. Model the steady state after they expire under the software use rights and order form terms that govern the deal, then add the renewal uplift for each remaining year. A five year view with credits on their own row shows the cost that stays.
What have we seen in recent S/4HANA pricing reviews?
Across roughly 40 to 50 S/4HANA pricing reviews in 2024 and 2025, the gap between SAP's first quote and the signed deal averaged 25 to 40 percent once the buyer controlled the user count. The best cases reached 40 percent. The same three patterns came up again and again.
- Inflated counts. FUE counts in the first quote ran 18 to 30 percent above a clean independent remap.
- Missing document numbers. Digital access was quoted as a placeholder or left out in 7 of 10 first drafts.
- A higher steady state. The year three run rate came in 20 to 35 percent above year one once credits expired.
The headline rate is the part of the S/4HANA price SAP is happy to discuss. The user count is the part that decides what you actually pay.
The size of the buyer mattered far less than a clean user count and a measured document position. Our data on the typical drop from first quote to signed price sets out the ranges by deal type.
How do you negotiate the S/4HANA price down?
Work the components in order of how much each one shifts the total, starting with the ones you control. The count and the document position are yours to fix with data. The discount is SAP's to give, and it comes more readily once the base is settled.
| Component | Typical swing | Who controls it |
|---|---|---|
| FUE count remap | 18 to 30 percent | Buyer, with usage data |
| Headline discount | 10 to 22 percent | SAP, under pressure |
| Digital access | Removes a future fee | Buyer, before signature |
| Module right sizing | 5 to 12 percent | Buyer, with scope review |
| Renewal uplift cap | Protects all of the above | Buyer, at drafting |
Why the biggest discount percentage is the wrong target
The common advice is to win the largest possible discount percentage and treat it as the measure of a good deal, and we disagree with it. SAP concedes the percentage easily because an inflated base and loose renewal terms protect the lifetime value of the contract. Chasing the percentage alone is the most common pricing error we see.
Compare two offers on the same clean requirement of 100 units at list price. A 35 percent discount on a count inflated by 25 percent costs 125 times 0.65, or 81.25 units. A 20 percent discount on the clean count costs 80 units, so the smaller discount is cheaper before the renewal cap and digital access are even considered.
The better sequence is to fix the count, measure digital access, negotiate the rate, then cap the uplift. Each step is then priced on a base you control, and the discount SAP offers at the end applies to a number you have already verified.
How to check your own position
You need evidence SAP cannot dispute, drawn from your own systems. On an ECC or on premises S/4HANA system, these sources give you most of it:
- ST03N workload statistics. Transactions executed per user over the trailing months, the basis for classifying by activity.
- SUIM user information. Roles and authorizations per user, which shows where assigned access runs ahead of real use.
- USMM and SLAW. SAP's own measurement results, so you know the user classification SAP will start from.
- IDoc monitoring and middleware logs. WE02 and your integration platform's message counts show which interfaces create documents, and how many.
What the account team will say, and how to answer
- "The FUE count comes straight from your current authorizations." Roles were built for convenience over many years. Ask SAP to classify against the service use description definitions and your usage data, user group by user group.
- "This discount only holds if you sign by quarter end." Take the deadline as a sign SAP wants the deal this quarter, and use it to push on price. Agree to the date only once the count in the quote matches your own.
- "Digital access can be sorted out after go live." After go live, you will be negotiating against a measured volume with no alternative. Ask for a priced document allowance in this order form, sized from your own baseline.
- "The renewal terms are standard across our customers." Ask for the uplift cap in writing and offer term length in exchange. Standard renewal clauses do change when you give something back.
- "With RISE you just pick the FUEs you need." The number of FUEs you pick is the user count under another name, so bring your own classification to that conversation.
For timing inside SAP's year, our note on the fiscal quarter effect on SAP pricing shows when concessions tend to come.
Which terms protect the S/4HANA price after signature?
The price is set at signature, but the terms decide whether it holds for the full term. Three terms matter most, and a few supporting clauses keep them from being worked around later.
Renewal uplift cap
Cap the annual increase in writing. Without a cap, the run rate resets toward list price when the discount lapses at renewal. Our uplift cap benchmark shows what other buyers have secured.
User true up method
Define the measurement window and the user definitions that apply. A clear method, stated in the order form, beats an open ended recount that SAP runs on its own terms. Tie it to the classification you agreed at signature.
Digital access cap
Set a document cap or a credit at signature. The exposure should be closed while you still have a signature SAP wants, before the volume is measured on SAP's schedule.
- Price hold on additional FUEs. New FUEs bought during the term at the signed rate, so growth does not reopen the discount.
- Ramp schedule. FUEs that rise with the rollout waves, so you stop paying for users who have not gone live.
- Reduction right. A stated right to reduce FUEs or modules at renewal after divestments or scope changes.
- Credit expiry dates. Every migration credit listed with its value and end date, so the year three rate is visible in the contract.
When should you start preparing an S/4HANA pricing negotiation?
Start twelve months before the planned signature. The independent count and the document baseline take months to build, and the room to change price and terms exists only before you commit.
| Time before signature | What to do |
|---|---|
| 12 months | Pull usage data, list every integration that creates documents, confirm the modules in scope |
| 9 months | Finish the independent FUE count and the digital access baseline |
| 6 months | Request the first quote and compare it line by line with your own numbers |
| 3 months | Negotiate the rate, the uplift cap, the true up method and the document cap |
| 1 month | Check the order form against every agreed term and credit before signing |
If you are still on ECC, the ECC to S/4HANA migration guide covers how the migration plan and the commercial timeline fit together.
What to do next
- Count. Build an independent FUE count from trailing twelve month usage.
- Scope. Right size modules to what the business actually runs.
- Measure. Measure digital access document volume across every integration.
- Model. Model the year three run rate after credits expire.
- Benchmark. Compare the price against comparable S/4HANA deals.
- Test. Run the SAP RISE TCO calculator to set your target number.
- Get help. Engage independent SAP advisory before the commercial close.
Frequently asked questions
How is SAP S/4HANA priced in 2026?
In RISE and the other cloud editions, S/4HANA is priced per Full Use Equivalent as a subscription that bundles infrastructure and operations. On premises, you buy named user licenses, modules and a HANA database license, then pay annual support. In both models, the digital access metric charges separately for documents created by non SAP systems.
What is a Full Use Equivalent user?
A Full Use Equivalent, or FUE, is SAP's blended unit in RISE and the cloud editions that converts different user types into one count. You contract a total number of FUEs, and within that total the mix of user types can change without a new order form, as long as the weighted sum stays inside it.
How much does S/4HANA cost for a mid sized enterprise?
A mid sized S/4HANA deal typically lands in the low to mid seven figures over the term once users, modules and digital access are included. The range is wide because the user mix and the document volume move the number more than the headline rate does.
Is S/4HANA cheaper as a cloud subscription or on premises?
Neither is automatically cheaper. The cloud subscription folds infrastructure and technical operations into one fee and lowers the operating burden, while on premises keeps capital control and ownership of the licenses. Base the decision on the run rate after credits expire.
What hidden costs sit beyond the S/4HANA license?
Beyond the license, budget for digital access, integration rework, data migration and the renewal uplift. The first and last are contract terms you can fix before signing. Integration and migration are project costs, but they change the document volume and the HANA sizing, so model them alongside the license.
How much can you discount S/4HANA?
Well prepared buyers reach a 25 to 40 percent gap between the first quote and the signed deal. Most of that comes from correcting the user count and the scope before the rate is discussed, so ask for the quote broken down by user type and module to see where the room is.
Does the FUE count favor SAP by default?
Yes. The default classification usually follows assigned roles and authorizations, which tend to place users in heavier types than their activity warrants. Building an independent count from real usage is the single most effective way to bring the price down.
When should you start pricing an S/4HANA deal?
Begin twelve months before signature. A clean user count and a document baseline take time to build, and your ability to change price and terms only exists before you commit to the deal. Starting late usually means negotiating from SAP's numbers.