SAP FUE licensing. Weighted by role.

SAP Full User Equivalents convert your named users into weighted units by role, so the cost tracks the mix of advanced and light users rather than the raw headcount you happen to carry.

Model it first with our SAP FUE calculator.

This guide is for SAP procurement leaders and license managers sizing a cloud subscription in 2026. Read it with the SAP licensing guide and the S/4HANA user types guide.

How does the SAP FUE metric actually work?

FUE replaces counting named users one for one. SAP weights each user by the role they hold, then totals the weighted figures to set your contracted FUE count. SAP describes its cloud ERP on the S/4HANA product pages.

What are the FUE conversion ratios?

SAP publishes role categories with set conversion ratios. The exact numbers vary by agreement, but the structure holds across cloud deals. Advanced roles carry the heaviest weight.

• Advanced user: heaviest weighting, often a full unit each.
• Core user: mid weighting for transactional work.
• Self service user: lightest weighting for occasional access.

How do you work a FUE calculation?

Take each population, multiply by its ratio, then add the results. A site with 50 advanced, 200 core, and 1,000 self service users lands far below 1,250 once the light weighting applies.

What does a worked FUE example look like?

The table below shows how a large raw headcount collapses into a much smaller weighted total. The light tier carries most of the headcount but little of the cost.

Where do buyers overpay on FUE?

The common error is classifying staff too high. An approver who only signs off requests does not need an advanced license, yet many contracts carry exactly that mismatch. SAP RISE pricing context sits on the RISE with SAP pages.

How do you optimize the FUE count?

Map real usage against role definitions, then move each user to the lowest role that fits. The exercise is unglamorous, but it routinely takes double digit percentages off the weighted total.

• Pull usage data: see what each user actually does.
• Match to role: assign the lightest role that covers the work.
• Document the basis: keep evidence for the next true up.

How does FUE play into a RISE renewal?

RISE bundles are quoted in FUE, so the classification feeds straight into the renewal price. Walking in with a defensible, optimized count changes the starting position before discount talks begin.

Where the common advice on SAP FUE is wrong

The standard guidance is to map every existing named user straight into the nearest FUE role and accept the resulting total. We disagree. Across the FUE populations Fredrik Filipsson benchmarked in 2024 to 2025, that straight mapping inflated the weighted total by 20 to 35 percent because legacy roles were set too high years earlier. The buyer side move is to classify from actual usage, not from the old role assignment. Pull what each user really does, place them in the lightest fitting role, then build the contracted FUE from that evidence. The metric rewards honesty about usage, and most estates have never tested it.

FUE is not a headcount. It is a weighting exercise, and the weighting is where the money is.

What to do next

1. Export the full named user list with current role assignments.
2. Pull actual usage data for each user over a representative period.
3. Reclassify every user to the lowest role that fits the work.
4. Recalculate the weighted FUE total on the corrected mix.
5. Compare the optimized total against your contracted figure.
6. Build the gap into your renewal or true up position.
7. Re run the review before each renewal as roles change.

White Paper · SAP

SAP named user licenses. The user classification audit

Read it free.

Read the white paper

Frequently asked questions

What is a Full User Equivalent in SAP licensing?

A Full User Equivalent, or FUE, is a weighted unit SAP uses to count cloud users. Each named user maps to a role type, and each type carries a conversion ratio that sets its share of the total.

How do you calculate the FUE count?

Classify every user by the role they hold, apply the conversion ratio for that type, then add the weighted figures. A few advanced users plus many light users lands well below a raw headcount.

Which user types weigh the most in the FUE model?

Advanced or developer level users carry the heaviest weighting, often a full unit each. Core users sit in the middle, and self service users carry the lightest fraction of a unit.

Why does FUE matter for SAP cloud contracts?

FUE is the metric SAP uses to price S/4HANA Cloud and many RISE bundles. Misclassifying users inflates the FUE total and the cost, so accurate classification is the largest single lever.

Can you reduce your FUE total without removing users?

Yes. Reclassifying users to the lowest role that fits their actual work lowers the weighted total. Many buyers carry advanced licenses for staff who only run reports or approve requests.

How much can reclassification save?

Across our benchmarks, reclassification commonly cuts the weighted FUE total by 10 to 25 percent. The saving comes from light users wrongly licensed as core or advanced over the years.

Is FUE used outside of RISE?

FUE prices S/4HANA Cloud and many RISE bundles. The same weighted logic frames how SAP expects cloud user populations to be counted across its current commercial models.

How often should you review the FUE classification?

Review it before every renewal and after any major rollout. Roles drift as projects end and teams change, so a classification set two years ago rarely matches current usage.