S/4HANA Licensing, Costs, and FUE Calculations Explained

Introduction – Why S/4HANA Licensing Feels So Complex

Migrating to SAP S/4HANA isn’t just a technical upgrade – it’s a licensing overhaul. SAP has effectively replaced simplicity with flexibility in its S/4HANA license model – and that flexibility comes with fine print. Full Use Equivalents (FUEs) are now SAP’s standard unit for measuring user licenses, introducing a new layer of complexity beyond the old ECC user model.

Instead of simply counting named users by type, SAP bundles usage into FUE “points” that normalize different user roles and access levels. This means understanding licensing is just as critical as understanding the technology, since it can drive significant long-term cost risks for your S/4HANA project.

In S/4HANA, there are new license categories that map to how users actually use the system. The main types include Professional, Functional, and Productivity users (replacing the old ECC Professional/Limited/ESS model).

Each type has different usage rights and costs, which SAP translates into FUE ratios. On top of user licenses, HANA database licenses, and indirect access fees, can quickly inflate your budget if not planned for. Read our ultimate guide to SAP S/4HANA Licensing Migration Cost Traps: Don’t Let Licensing Surprise You.

In short, S/4HANA licensing feels complex because it introduces new metrics and mixed models that require careful analysis – often more so than the software itself.

Checklist:

• Clarify FUE as SAP’s standard unit of measurement for S/4HANA user licensing (the “points” that all user types convert into).
• Identify main license types (Professional, Functional, Productivity users) and know how they differ in access scope.
• Flag extra cost multipliers like the required HANA database license and indirect/digital access fees for non-SAP integrations.

Understanding S/4HANA’s FUE Model

Full Use Equivalent (FUE) is SAP’s method of normalizing various S/4HANA user licenses into a single metric. Think of FUEs as a “currency” for user licensing. Instead of buying a fixed number of licenses for each user type, you purchase a total pool of FUEs.

Each user you license then “spends” a certain fraction of an FUE based on their type. High-level users consume more FUEs; occasional users consume less.

This gives you the flexibility to mix different user levels under one aggregate entitlement, but it also means you must understand the conversion ratios.

For example, here’s a typical weighting of S/4HANA user licenses to FUEs:

In this illustrative FUE model, a Professional user counts as 1.0 FUE, a Functional user as half, and a low-tier Productivity user as one-tenth. Your total S/4HANA license capacity is measured in FUEs, not raw headcount.

For instance, 10 Productivity users (0.1 each) equate to just 1 FUE of license consumption, whereas 1 Professional user alone is 1 FUE. SAP uses these ratios to give you flexibility – you could swap two Functional users for one Professional in your license mix without buying more FUEs, for example. The key is that your contract’s FUE total is the real entitlement you’re paying for.

Conversational Tip: “FUEs are SAP’s way of bundling flexibility — and hiding the price per user.” In other words, by converting everything to FUE points, it’s less obvious what you’re really paying per high-level user vs. low-level user. Always do the math to know the cost per user category.

Checklist:

• Map user roles to license types: Identify each user role in your organization and decide whether they need Professional, Functional, or Productivity access (or another category) based on job requirements.
• Apply FUE conversion ratios: Calculate how many FUEs each group of users represents using SAP’s ratios (e.g., 2 Functional users = 1 FUE). This ensures your planned user count translates correctly into FUEs.
• Reconfirm the FUE total in proposals: Cross-check that SAP’s quote or proposal uses the same user-to-FUE mapping you expect. Ensure the total FUEs cover all your users without overestimating (or inflating) the count.

Contractual gotchas, Contract “Gotchas” in Migration: The Fine Print That Can Cost You During Your SAP Move.

How SAP Calculates Cost Using FUEs

Once you know your total FUEs, SAP’s pricing formula for S/4HANA looks straightforward on paper:

Total License Cost = (Number of FUEs × Price per FUE) + HANA Database + Add-ons + Support.

In practice, each component needs scrutiny. SAP will assign a list price (and hopefully a discount) per FUE. You pay for the total number of FUEs you need. On top of that, HANA database licenses (required for S/4HANA) and any extra add-on modules are added to the bill.

Finally, maintenance (if on-premise perpetual licensing) or subscription support fees (if cloud) typically add ~22% of the software cost annually.

Example: Imagine you forecast 1,000 total S/4HANA users:

• 200 are Professional (1.0 FUE each)
• 300 are Functional (0.5 FUE each)
• 500 are Productivity (0.1 FUE each)

First, convert these to FUEs:

• Professional users: 200 × 1.0 = 200 FUE
• Functional users: 300 × 0.5 = 150 FUE
• Productivity users: 500 × 0.1 = 50 FUE

Total FUEs = 200 + 150 + 50 = 400 FUE. This 400 FUE pool covers all 1,000 named users in various roles.

Now, if SAP’s unit price is, say $1,000 per FUE, your base S/4HANA software license cost would be $400,000. But that’s not the full picture. You must then add the cost for the SAP HANA database to run S/4 (for example, a HANA runtime license might cost roughly 15% of your software spend – here around $60,000, or more if using a full-use HANA license based on data size).

Next, include any add-on module licenses (perhaps you need advanced warehousing or analytics modules – we’ll cover these later). Lastly, include support: typically 22% of the license fees annually for on-premise (in this example, about $88,000 per year if the software cost is $400k).

In a cloud subscription scenario, support is baked into your subscription price, but expect yearly inflation adjustments.

So, a quoted $400k license can easily turn into a first-year spend well over $500k after HANA and support are added.

Over 5 years, that support accumulates significantly. The lesson: always calculate the true total cost of ownership (TCO), not just the initial license fee.

Pro Tip: Always ask SAP for the detailed FUE breakdown in your pricing. Don’t settle for just “400 FUEs = $400k” as a lump sum. Request to see how many users of each type they assumed and the effective price per user. This FUE matrix transparency helps you validate the quote and negotiate better.

Checklist:

• Validate user-to-FUE mapping: Double-check SAP’s classification of each user type and quantity. Ensure, for example, that casual users aren’t mistakenly counted as higher license types (which would overstate FUEs and cost).
• Recalculate cost independently: Do your own cost model with the FUE counts and unit prices. Verify the math of SAP’s quote – including how add-ons and database fees are applied – to avoid any “black box” pricing.
• Include support in TCO: Don’t forget maintenance or subscription support fees (~20–22% yearly). For a true budget, calculate 3-5 years of support on top of license fees. A license is not a one-time purchase; support costs will often equal the license cost within 4–5 years.

FUE Licensing Categories and Add-On Products

Buying S/4HANA isn’t like buying one all-inclusive package – there’s the digital core and then a constellation of optional products.

Your FUE count typically covers the core S/4HANA Enterprise Management modules (finance, procurement, sales, manufacturing, etc. – the basics of ERP). However, many Line-of-Business (LoB) modules and industry solutions are licensed separately as add-ons. It’s critical to know where the FUE-based licensing stops and extra fees begin.

Categories of S/4HANA licenses:

• Core Enterprise Licenses (FUE-based): These cover standard ERP functionality. If you purchase, say, 400 FUEs of S/4HANA Enterprise, it usually includes the common modules every company uses (general ledger, order management, basic warehouse, production planning, etc.). The FUE model gives you flexibility in user mix for these core features.
• LoB Add-Ons: For specialized capabilities, SAP still uses engine metrics or separate licenses. Examples include Extended Warehouse Management (EWM) for advanced warehousing, Transportation Management (TM) for logistics, Global Trade Services (GTS) for trade compliance, Central Finance, or Group Reporting for consolidated financials. These often do not consume your FUEs; instead, they require you to buy a separate license (often measured by transactions, volume, or users specific to that module). For instance, S/4HANA might include basic warehouse management in the core. Still, if you need the full EWM functionality (slotting, automated picking, etc.), that’s a paid engine where cost could be based on the number of warehouse orders or warehouse size.
• Industry Packages: If you’re in a sector like Utilities, Retail, or Manufacturing, SAP offers industry-specific S/4HANA solutions or add-ons (e.g. Utility billing, Retail assortment planning). These can carry premium pricing or unique metrics. Often, they are not covered by the generic FUE count. An industry engine might be priced on industry metrics (utility customers, retail stores, sales revenue, etc.). Always check if any industry functions you need are included in the core or sold separately.

The important point is that “included” doesn’t always mean included. SAP sales might imply that certain functionality is part of S/4, but the devil is in the details.

Always confirm in writing which modules are part of your FUE-based license and which require separate licenses. Every add-on can significantly change your cost structure.

Conversational Tip: “Every add-on SAP calls ‘included’ — verify that in writing.” If advanced warehousing or planning is critical to you, get clarity: is the basic version included with your S/4HANA Enterprise license and at what limit? When do you need a separate license? Don’t rely on verbal assurances that “oh, you have that functionality” – ensure your contract reflects it.

Checklist:

• List out planned modules: Identify all the SAP modules and add-ons you intend to use (or might use in the future). Check the price list or with SAP, which of those are part of the base S/4HANA license and which are additional.
• Confirm FUE coverage vs. extra licenses: For each add-on (EWM, TM, Supply Chain, etc.), determine if it consumes your existing FUEs (rare) or if it comes as a separate engine license. Also, verify if users of those systems need higher license types. For example, using EWM might require certain users to be Professional users due to advanced functionality.
• Obtain corresponding SKUs: If new modules require their own license SKU, get SAP to provide those metrics and costs upfront. Never assume a capability is free – always ask, “If we turn on this module, do we need to pay for it separately?” and document the answer.

Key Cost Drivers Beyond FUEs

Even with the right mix of user licenses, some big cost drivers in S/4HANA can catch you off guard.

Beyond user FUEs, budget for these factors:

• HANA Database Licenses: S/4HANA runs exclusively on SAP’s HANA database, which is a separate licensing item. You have two options: HANA Runtime or HANA Full Use. A HANA Runtime license is a discounted, restricted-use license that allows HANA only for SAP applications (like S/4 or BW). It’s often priced as a percentage of your S/4HANA software value (for example, ~15%). This can be cost-effective if you only use HANA under S/4. However, if you plan to use HANA as a general database (connecting third-party apps, doing custom development on HANA), you must buy a Full Use HANA license. Full Use licenses are measured by memory size (GB of HANA RAM) or HANA cores, and can be significantly more expensive as your data grows. Choosing runtime vs. full use has major cost implications and compliance implications – using HANA beyond its licensed scope (even inadvertently) can trigger an audit finding. Plan your HANA usage carefully and include the chosen license cost in the S/4 budget. (In a cloud subscription like RISE with SAP, the HANA database is typically included in the subscription price, but you’re paying for it one way or another.)
• Indirect Access (Digital Access): Indirect access refers to scenarios where external systems or users interact with S/4HANA data without a direct SAP login (for example, an e-commerce website creating sales orders in SAP, or a robotic process automation script reading data). SAP now addresses this via its Digital Access Document License model, which charges for certain document types (sales orders, invoices, etc.) created indirectly. This can be a hidden cost multiplier if you have many non-SAP integrations. For instance, integrating your Salesforce or e-commerce platform with S/4 could generate thousands of SAP documents – each potentially requiring a licensed allocation. SAP offers packs of documents for a fee under the digital access model. Make sure to either negotiate this as part of your deal or at least quantify the potential volume so you’re not blindsided later. In some cases, older contracts allowed some indirect use under named users; but with S/4, SAP pushes the document licensing approach. Align your integration plans with an indirect access strategy (whether that’s adopting SAP’s model or negotiating exceptions).
• Cloud Extensions and Platform Services: Implementing S/4HANA often comes with the need for related cloud services. For example, you might use SAP Business Technology Platform (BTP) for extensions/integrations, SAP Analytics Cloud (SAC) for reporting, or other SaaS offerings like Ariba, SuccessFactors, or Concur alongside S/4. These are separately licensed and can add recurring subscription costs. They aren’t measured in FUEs, but they contribute to your total SAP spend. When building your business case, include any complementary SAP products or cloud services you’ll likely use, because they can be significant (and often have their own user or capacity-based fees).
• Support and Uplifts: If you license S/4HANA on-premises, you’ll pay annual maintenance (support) on the licenses, typically 22% of the net license price each year for SAP Enterprise Support. This means in roughly 5 years, you pay the value of the license again in maintenance fees. Over a decade, support can cost more than the original licenses several times over. For cloud subscriptions (like RISE or S/4HANA Cloud), support is included, but be aware of uplift clauses – many cloud contracts allow SAP to increase fees annually (e.g. by a certain percentage or an inflation index). Always check if your agreement fixes the subscription rate or if SAP can apply CPI-based increases. Support costs are often non-negotiable once set, so negotiate the base carefully and budget for the long haul. Also consider that SAP’s support has tiers (Standard 19%, Enterprise 22%) – new contracts usually default to 22%, but if you’re a large customer, see if there’s any flexibility or additional value-add you can demand for that fee.

Checklist:

• Include all layers in TCO: Build your total cost of ownership model to include user license FUE costs, HANA database licenses, key add-ons/engines, indirect access (if applicable), and support or cloud subscriptions over time. This comprehensive view prevents nasty surprises.
• Plan for indirect use: Review how your systems interact with SAP. If you foresee heavy integration or use of bots/third parties accessing S/4 data, consult SAP’s digital access licensing early. You might negotiate a document license bundle or clarify in the contract what is permitted to avoid future compliance issues.
• Review support terms: Check your contract for any support fee increases or unusual terms. In on-prem deals, know that 22% annually is a significant cost – ensure it’s in your budget. In cloud deals, see if you can cap any annual uplifts. It’s easier to address these before signing than to fight them later.

Estimating Your S/4HANA License Budget

To make S/4HANA licensing less abstract, build a sample cost model for your scenario. Let’s walk through an example of estimating a first-year S/4HANA license budget:

In this rough scenario, the initial license purchase is about $670,000 for the software (users + HANA DB + extra modules). On top of that, first-year support would be approximately $147,000 (if this is an on-prem license deal). That brings the Year 1 total to roughly $817,000. Over 5 years, assuming a static environment, support would add up to ~$735,000 on top of the original license cost. And if your usage grows (more users, more data), those costs will increase further.

For a cloud subscription equivalent, you might be quoted an annual subscription fee that already includes HANA and some add-ons. For instance, SAP might quote ~$800,000 per year as a subscription that bundles all this. In that case, you wouldn’t break out HANA or support separately, but you should still perform the multi-year total calculation (e.g., $800k × 5 years = $4M) and check if any escalation applies after year 1.

The takeaway is to forecast your SAP costs 3–5 years out. Look at your existing ECC spend as a baseline (maintenance on ECC plus any engine licenses you pay for today). Then compare it to the S/4HANA scenario with all the new costs.

Often, S/4HANA’s first few years will cost more than you’re paying for ECC currently, especially when you factor in project implementation costs on top. However, with careful planning and negotiation, you can mitigate some of the increases.

Conversational Tip: “If you can’t explain your FUE math to Finance, SAP can — and that’s dangerous.” Always be able to justify the numbers in simple terms. For example, be ready to explain: “We need 400 FUEs to cover 1,000 users, which costs $400k. Then we need $150k for the database and $120k for two extra modules, plus support. That’s why year one is ~$817k.” When you can articulate this clearly, you control the conversation – not SAP.

Checklist:

• Build a multi-year budget projection: Don’t stop at the year 1 costs. Model the next 3-5 years, including growth in user count, data (for HANA sizing), or added modules. Incorporate the annual support or subscription fees. This will give management a clear view of the total investment.
• Compare to ECC spend: Use your current SAP ECC licensing cost as a benchmark. How does the new S/4HANA annual cost (license + support) compare to what you pay now? This helps in building a business case and understanding the incremental cost of moving to S/4.
• Factor in discounts/credits: If SAP is offering any migration discounts, such as credits for existing licenses (e.g., through a cloud extension policy or conversion program), reflect those in the budget. Also include any one-time costs like SAP Professional Services or partner licenses if they’re part of the deal. The goal is to leave no cost unaccounted for.

Negotiation Levers to Optimize FUE Costs

The good news is that S/4HANA pricing is negotiable. As a customer, you have several levers to pull to optimize the cost before you sign on the dotted line.

Here are key strategies:

• Volume and Tiered Discounts: SAP, like most vendors, offers better pricing per unit (per FUE) as the volume increases. If you anticipate needing more users in the future, consider negotiating a higher volume upfront to secure a lower price per FUE. For example, if you currently need 300 FUEs but will likely grow to 500 in a year or two, negotiate pricing at the 500-FUE level now. This can dramatically drop the unit price. Even if you don’t purchase all at once, you can often get SAP to agree on a discounted rate for incremental FUEs. Also, bundling multiple SAP products in one negotiation (S/4HANA + analytics + HR, etc.) can give you leverage to ask for a cumulative discount across the larger deal.
• Multi-Year Price Protections: Lock in your costs to avoid future surprises. This can be done via price caps or freezes. For instance, negotiate a clause that your FUE unit price will not increase for 3 years, or that you can purchase additional FUEs at the same discounted rate if needed. If you’re signing a subscription, try to cap any annual price increase. Without a cap, SAP might raise cloud subscription fees by a few percent each year. Get those limits in writing. Another lever is to negotiate fixed discount percentages that apply to future purchases of licenses or add-ons during the contract term. You want to insulate yourself from SAP list price hikes or metric changes down the road.
• Leverage Existing Investment (Conversion Credits): If you’re coming from ECC, use your current maintenance payments as a bargaining chip. SAP’s Cloud Extension Policy and similar programs allow you to reallocate some of your on-prem license value or maintenance into new S/4HANA subscriptions. Essentially, you shouldn’t pay twice for overlapping usage. In a conversion negotiation, push for credits for the licenses you already own. For example, if you have a lot of ECC users and you’re still paying 22% maintenance on those, ask SAP to credit a portion of that value against the S/4 license cost or subscription fees. The more you can capitalize on what you’ve already paid, the lower your net new spend. Also consider timing your S/4 purchase around your maintenance renewal cycle – you might be able to cancel a year of maintenance and funnel those funds into the new S/4 contract if negotiated correctly.
• Bundle HANA and Others in the Deal: Don’t treat the HANA database or key add-ons as separate afterthoughts. When negotiating S/4, also negotiate the price for the required HANA licenses and any likely add-ons. Bundling them in the same deal can get you a package discount. If you negotiate S/4 user licenses but leave HANA DB for later, you might lose leverage. SAP knows you have no choice on HANA, so get a firm quote for it upfront and try to tie it to the overall discount structure. The same goes for high-cost modules you know you’ll need – it’s better to get them discounted as part of the initial purchase than to add them a year later at full price.

Finally, don’t be afraid to propose creative clauses that give you flexibility. For example, a clause allows you to adjust the FUE count down after a year if you overestimated, or swap certain license types for others if your needs change.

SAP may or may not agree, but if you don’t ask, you don’t get. Aim to craft a deal that not only lowers cost now but also protects you as your business evolves.

Sample Clause: “SAP agrees to maintain the FUE list price and discount for 36 months, irrespective of any future price list changes or metric updates.” – Including something like this ensures that even if SAP’s pricing model changes or list prices go up, your negotiated rate per FUE stays the same for the term of the agreement.

Checklist:

• Double-check all discounts: Ensure the final agreement reflects all negotiated discounts on FUEs, HANA, and add-ons. Verify the math – what percentage discount are you actually getting from list price? Is it applied correctly across all components?
• Secure unit price caps in writing: If you negotiated fixed pricing for additional FUEs or a cap on subscription increases, make sure the contract language clearly states the duration and scope (e.g., “price per FUE won’t exceed $X for up to Y additional FUEs purchased by date Z”). This protects you from future cost shocks.
• Leverage legacy spend: Use your existing ECC licenses and maintenance as a bargaining tool. For on-premise S/4, consider trade-in credits or selective shelfware retirement in exchange for better terms. For the cloud, use the cloud extension or conversion programs to avoid duplication. Let SAP know you’re considering all options – including non-SAP alternatives – and that you need a compelling financial case to move to S/4HANA.

5 Ways to Keep S/4HANA Licensing Costs Under Control

1. Validate SAP’s FUE ratios independently before signing. (Don’t just accept SAP’s categorization – verify each user’s classification to ensure you’re not over-counting FUEs.)
2. License in phases aligned to the go-live scope. (Stagger purchases to match rollouts. Avoid buying all licenses up front if parts of the project won’t go live for a year or more.)
3. Negotiate conversion credits for old licenses. (Leverage any value in your ECC licenses or maintenance payments – push for credits or discounts when transitioning to S/4HANA.)
4. Fix FUE unit pricing for at least three years. (Lock in your per-FUE cost or subscription rate so you’re shielded from price hikes or metric changes in the near term.)
5. Track and reconcile FUE usage quarterly. (Once live, continuously monitor your user counts and license types. Reclaim or reclassify users to lower tiers if possible and ensure you’re not exceeding your FUE allotment.)

By following these practices, you can demystify SAP’s licensing model and maintain control over your S/4HANA costs. The key is to be proactive: understand the rules, run the numbers yourself, and negotiate safeguards into your contract.

With that diligence, you’ll keep surprises at bay and make your S/4HANA investment as cost-effective as possible.

Read about our SAP Services.

fredrik.filipsson

Fredrik Filipsson is the co-founder of Redress Compliance, a leading independent advisory firm specializing in Oracle, Microsoft, SAP, IBM, and Salesforce licensing. With over 20 years of experience in software licensing and contract negotiations, Fredrik has helped hundreds of organizations—including numerous Fortune 500 companies—optimize costs, avoid compliance risks, and secure favorable terms with major software vendors. Fredrik built his expertise over two decades working directly for IBM, SAP, and Oracle, where he gained in-depth knowledge of their licensing programs and sales practices. For the past 11 years, he has worked as a consultant, advising global enterprises on complex licensing challenges and large-scale contract negotiations.

See Full Bio