SAP Named User Optimisation:
Reduce User Count, Cut Licence Costs

Why SAP Named User Licences Are Your Biggest Cost Lever

SAP Named User licences are frequently the single largest line item in an SAP software contract — often accounting for 50–65% of total annual licence fees. Unlike database or application server licences that scale with infrastructure, Named User licences scale directly with headcount, and SAP's audit teams know this. In over 500 engagements across enterprise SAP customers globally, Redress Compliance consistently finds that 30–40% of provisioned Professional users do not require that licence type based on their actual system activity.

The root cause is rarely deliberate over-provisioning. IT teams default to Professional licences because they are the most permissive — they avoid audit risk and support requests. HR and procurement teams rarely scrutinise the SAP Named User line at renewal time, treating it as a fixed cost. The result is a growing licence liability that SAP's account team is happy to ignore until audit season. For a 2,000-user SAP estate, this mismatch can translate to £300,000–£600,000 in unnecessary annual spend.

SAP Named User Licence Types: What Each Category Actually Permits

SAP's six primary Named User licence types carry very different price points and usage rights. Professional Users (the most expensive, typically priced at €1,800–€2,400 per user per year) can perform all transactions in all modules. Limited Professional Users — priced at roughly 30–35% of Professional — can complete specific, restricted transaction types. Self-Service users can create limited documents (purchase requisitions, leave requests) but cannot post general ledger entries or run reports. Developer licences are required for anyone writing ABAP code or configuring workflows, while Employee and Test User types cover self-service HR access and non-production environments respectively.

The classification challenge is that SAP uses transaction codes, not job titles, to determine correct licence type. A Finance Business Partner who regularly posts journal entries needs Professional. A budget holder who only approves purchase requisitions in SRM qualifies for Limited Professional. Many organisations have not mapped these distinctions in years, and every new ERP project cycle adds unlicensed users who default to Professional rather than being formally assessed. Download our SAP Named User Licence Negotiation playbook for the full transaction-to-licence-type mapping used in live optimisation engagements.

How to Conduct a SAP Named User Optimisation Audit

A credible user optimisation programme begins with data, not assumptions. The SAP Licence Administration Workbench (LAW) and transaction USMM provide usage statistics — showing which users have logged in, which transaction codes they have executed, and when. For S/4HANA environments, the System Measurement tool provides equivalent data in a format SAP expects at audit time. Pull at least 12 months of usage data to account for seasonal variation — a Finance user who appears inactive in July may be critical during month-end close in December.

Step 1: Identify Zero-Activity Users

Typically 8–15% of provisioned Named Users in a mature SAP estate show zero system activity in the prior 12 months. These are leavers whose accounts were not deprovisioned, contractors whose projects ended, and users who moved to different roles. Removing these from the licence count immediately reduces your liability and eliminates audit exposure with no operational risk whatsoever.

Step 2: Map Active Users to Transaction Profiles

For the remaining active users, extract their transaction code usage from SM20 or equivalent audit logs and compare against SAP's published transaction classification lists. Users who exclusively run reports (via SE16N, ALV, or specific Fiori apps) without posting may qualify for Limited Professional licences. Users who only interact with self-service Fiori tiles — approving timesheets, raising purchase orders — almost certainly qualify for Self-Service or Employee licences.

Step 3: Build the Reclassification Proposal

Prepare a formal reclassification proposal that maps each affected user account to a proposed licence type, supported by their 12-month transaction profile. SAP account teams will push back on reclassifications without evidence — they will argue that users "could" access transactions even if they never do. Counter this with time-stamped USMM exports. For organisations preparing for a migration to SAP RISE or S/4HANA Cloud, this audit also feeds directly into the Digital Access scoping exercise, ensuring you understand your baseline before SAP conducts their own measurement.

SAP's Reclassification Rules: What They Will and Won't Accept

SAP operates a strict view on downward reclassification — they will resist any proposal that reduces revenue without clear evidence. Their key objection is the "capability" argument: a Professional user who occasionally runs simple reports still has the technical capability to post journal entries, therefore they must be licensed at Professional level. This argument is commercially convenient for SAP but contractually weak. The SAP General Terms and Conditions define licence types by actual use, not theoretical capability, and this is the basis on which Redress negotiates reclassification proposals.

SAP will accept reclassification for users who have demonstrably not executed Professional-class transactions over a sustained measurement period. They will typically agree to a 6–12 month trial period during which reclassified users are monitored, with automatic reinstatement of Professional if their transaction profile changes. In practice, fewer than 5% of reclassified users revert to Professional during a trial period — most managers correctly identify which roles genuinely need full access before the exercise begins. This approach also links closely to your SAP Digital Access strategy, since many users driving documents through integrated systems are better handled under Document licences than Named User agreements.

Presenting the Business Case to SAP

The commercial negotiation requires preparation that goes beyond the technical audit. SAP's account team will understand the financial implication of your proposal immediately — they are measured on contract value, and a reclassification programme that reduces annual licence fees by £400,000 directly affects their targets. Expect initial resistance, requests for more data, and escalation to their regional licence team.

Your strongest commercial leverage in this negotiation is the upcoming renewal cycle. SAP will want to retain total contract value — they may accept reclassification of 200 users from Professional to Limited in exchange for a multi-year commit, or offer additional SAP Analytics Cloud or SuccessFactors entitlements to offset the headline reduction. If you are also evaluating SAP SuccessFactors renewal or expansion, bundle both negotiations into a single commercial discussion. SAP account teams have more flexibility when they can protect total relationship value than when they are defending a single contract line. For independent guidance on SAP's typical concession patterns, book a confidential advisory call with our SAP team.

Risks to Manage During Reclassification

Three risks require active management throughout the programme. First, ensure IT and Basis teams understand that reclassified users may need their SAP role profiles adjusted — a user moved to Self-Service licence must have their system authorisations updated to prevent accidental Professional-class transactions that would trigger a licence breach at audit time. Second, communicate clearly to business users that their system access is being optimised, not restricted. Frame the exercise as licence hygiene rather than cost-cutting — users who feel their access is being arbitrarily reduced will raise escalations that slow the programme. Third, conduct the reclassification before your next SAP System Measurement date, not after. SAP's measurement snapshot will capture the old, higher-cost user counts if you act too late, and correcting the record retrospectively is significantly harder than presenting a clean measurement at the appropriate time. Our SAP Audit Defence Framework covers the measurement process and how to structure your position before SAP's team reviews your system data.