SAP Named User Licensing: How to Right-Size Your Licence Mix and Cut Annual Fees

SAP Named User Types Explained

SAP's Named User licensing grants specific individuals access to SAP software. Unlike concurrent user models (where you buy capacity), Named Users are tied to specific people — which means the licence count must equal or exceed your active user population. The key user types in the SAP ECC and S/4HANA world are:

In the S/4HANA world, SAP has also introduced the RISE with SAP user entitlement model, where users map to "Full Use Equivalent" (FUE) metrics rather than discrete Named User types. Under RISE, the conversion from legacy Named User counts to FUE introduces additional commercial complexity — and commercial risk if not managed carefully.

Why Enterprises Systematically Overpay for Named Users

SAP Named User audits — conducted via the USMM (Usage and System Measurement) tool — assess how your users interact with the system and classify them according to their maximum access level. The problem is that USMM measures maximum access, not actual usage. A user who has been provisioned with full Professional User access but only logs in to approve purchase orders will still be measured as a Professional User.

This gap between provisioned access and actual usage is the primary driver of SAP licence overspend. Enterprises that provision broadly and never conduct access right-sizing routinely pay 20–40% more than necessary for their Named User base.

Four patterns create overspend consistently:

• Provisioned but inactive users: Former employees, contractors, or project users whose SAP accounts were never deactivated. USMM counts these users at the licence category of their highest-access role.
• Incorrect user type classification: Users doing limited workflow tasks assigned Professional User licences because provisioning followed a blanket template rather than a role-based approach.
• Accumulated role creep: Users accumulate transaction access over time as their roles change, without corresponding licence type reviews. A user who started as an Employee User and gained finance access over years may now be classified as a Professional User without anyone noticing.
• SI over-provisioning: System integrators implementing SAP projects routinely provision Professional Users to all project team members during implementation. Post-go-live, these users are rarely downgraded to their appropriate licence category.

How to Conduct a SAP Named User Audit

A proper SAP Named User audit follows a structured methodology. Here is the process we use in client engagements:

Step 1: Extract the Current User Register

Using transaction SU01 and SU10, extract a complete list of all Named Users in every SAP production system. This includes active users, locked users, and service users. Include user type, last login date, and assigned roles for each account.

Step 2: Identify Inactive Accounts

Filter for users who have not logged in within the past 90 days. Cross-reference against HR records to identify terminated employees. In most large enterprises, 5–15% of Named User accounts belong to users who are no longer active — these should be immediately deactivated and removed from the licence count.

Step 3: Map Roles to Licence Requirements

For each active user, conduct a role-to-licence mapping. SAP's Product Availability Matrix (PAM) and the specific transaction mappings in your licence contract define which transactions require which licence type. Map each user's assigned roles against these requirements to determine the minimum licence type required for their actual system access.

Step 4: Identify Downgrade Candidates

Based on the role mapping, identify users currently licensed at Professional User level who could be reclassified to Limited Professional or Employee User. Prepare a business case for each downgrade candidate, documenting current licence type, recommended type, and the specific transaction access that supports the reclassification.

Step 5: Implement Access Adjustments

Remove excess role assignments from downgrade candidates. Deactivate inactive accounts. Ensure the access adjustments are implemented in production before the next USMM measurement cycle — typically annual, often aligned to your contract anniversary.

Step 6: Negotiate Licence Reduction at Renewal

Armed with a validated, optimised user count, approach the annual licence true-up or renewal negotiation with the right-sized numbers. SAP's position is that licence counts can go up easily but down is harder — expect pushback. However, a properly documented audit with clear evidence of the right-sizing basis gives you a strong negotiating position.

How SAP Measures You — and How to Challenge It

SAP's primary measurement tool is USMM (Usage and System Measurement), supplemented by the LAW (Licence Audit Workbench) for consolidation across systems. SAP's Global Licence Auditing (GLA) team runs these tools during formal licence reviews or in advance of renewal negotiations.

Key facts about USMM measurement that most enterprises don't know:

• USMM measures maximum access, not actual usage. A user assigned a Professional User role but who only uses ESS functions will still be counted as Professional User in USMM output.
• Measurement timing matters. USMM snapshots are typically taken at a specific point in time. If you have cleaned up users and removed excess roles before the measurement date, the measurement will reflect your optimised position.
• Indirect access can appear in measurements. USMM may identify document creation triggered by third-party systems as requiring Named User licences. This is the SAP Digital Access and indirect access challenge — a separate but related issue that can significantly inflate apparent licence obligations.
• The LAW consolidation process has errors. In multi-system environments, the LAW tool consolidates user counts across systems. Deduplication of users who appear in multiple systems is not always accurate — it must be manually reviewed and challenged.

Named User Right-Sizing at S/4HANA Migration

The single best moment to right-size your SAP Named User base is at S/4HANA migration. Migration projects require a user access review as part of the transition — role redesign, Fiori app mapping, and the change from classic transactions to Fiori tiles all create natural checkpoints for licence reclassification.

In the S/4HANA world, SAP has simplified user types compared to ECC, but introduced new complexities. Under S/4HANA on-premise, the key types are Advanced User and Core User. Under RISE with SAP, users map to FUE (Full Use Equivalent) credits. The FUE conversion from your existing Named User base is where SAP sees maximum commercial opportunity — and where independent advisory has the most impact.

Enterprises that conduct a thorough Named User audit before committing to their S/4HANA FUE count consistently pay less over the life of their RISE subscription than those who accept SAP's initial conversion proposal. The difference is typically 10–20% of total contract value — on multi-million-dollar deals, that is a significant number.

Named User Negotiation Tactics at SAP Renewal

Beyond right-sizing, there are specific negotiation levers for Named User costs at SAP renewal:

• Push for a combined FUE pool: Under S/4HANA and RISE, negotiate for a single FUE pool rather than separate named licence counts per product. A pooled model gives you flexibility to allocate licences to actual users without penalty.
• Negotiate downgrade rights explicitly: SAP's standard agreement often restricts downgrading user types without penalty or renegotiation. Ensure your contract includes an explicit right to reclassify users between types annually without commercial penalty.
• Challenge the indirect access catch-all: SAP will attempt to reclassify some Limited Professional or Employee Users as Professional Users based on indirect system interaction. This is often overstated — push back with documented evidence of actual usage patterns.
• Benchmark your user costs: SAP's standard list prices for Named Users are rarely what enterprises pay. Independent benchmarks of comparable deals typically show 20–40% below list price is achievable — use this as your negotiation baseline.
• Time your negotiation around SAP's fiscal calendar: SAP's fiscal year ends December 31. Q3 and Q4 (especially October–December) represent maximum commercial pressure on SAP's sales team to close deals — which gives buyers meaningful leverage that evaporates in Q1.

Key Takeaways

• Most enterprises carry 20–35% excess Named Users — typically inactive accounts or incorrectly classified users
• USMM measures maximum provisioned access, not actual usage — always validate independently before accepting results
• Conduct a Named User audit at least 90 days before your SAP renewal to give time to implement right-sizing
• Migration to S/4HANA is the best moment to right-size — negotiate FUE counts from an audited baseline, not SAP's conversion proposal
• Negotiate explicit downgrade rights, pooled FUE structures, and price escalation caps into every SAP contract
• Our SAP negotiation service works on gainshare — 25% of verified savings, or you pay nothing