Named user licences are the backbone of SAP cost. Misclassification leads to overspending and audit risk. This playbook provides a comprehensive, step-by-step approach — including licence type analysis, right-sizing tactics, shelfware elimination, governance frameworks, and negotiation leverage — to cut SAP spend while maintaining full compliance.
Named user licences are the backbone of SAP cost. In most SAP environments, user licences account for the largest share of ongoing SAP spend. Every employee or external user accessing SAP needs a licence, and SAP offers different licence tiers at vastly different price points.
If you default everyone to expensive licence types, your ERP budget will balloon. Assigning a Professional User licence to someone who only needs basic self-service access can cost 10–20 times more than necessary. Multiply that across hundreds or thousands of users, and the overspend becomes enormous.
Over-licensing isn't just a budget issue — it's also a compliance risk. SAP licence audits scrutinise whether each user's activities match their licence type. If a user performs transactions that exceed what their licence allows, auditors can flag it and demand back-payments or additional licence purchases.
Conversely, unused or inactive accounts still assigned licences count as "shelfware" that incurs maintenance fees year after year. In extreme cases, companies may have dozens of ex-employees or duplicate accounts consuming expensive licences without being noticed.
SAP offers multiple user licence types, and choosing the right one for each user is crucial. The cost difference between tiers is significant — assigning everyone a Professional licence "just to be safe" will blow up your IT budget.
| Licence Type | Access Scope | Typical Users | Relative Cost | Key Guidance |
|---|---|---|---|---|
| Professional User | Full access to all SAP modules and transactions | Power users, administrators, finance directors | 100% (highest tier) | Use sparingly — only for users who truly require unrestricted access |
| Limited Professional (Functional) | Restricted to specific modules or business areas | Finance clerks, procurement staff, defined-role users | ~50% of Professional | Right-sizing from Professional to Limited immediately halves cost |
| Employee (ESS) | Basic self-service tasks only — timesheets, pay stubs, HR info | General workforce, occasional SAP users | 5–10% of Professional | Perfect for the majority of employees with minimal SAP interaction |
| Developer User | Development and administration tools (ABAP, configuration) | Developers, Basis administrators, system configurators | ~100% (similar to Professional) | Only for users doing actual development — not day-to-day business transactions |
| Specialist (Warehouse/Shop Floor) | Specific operational tasks for frontline workers | Warehouse staff, production floor operators | Much lower than Professional | Purpose-built for operational roles at significantly reduced cost |
Align each user with the cheapest licence that still covers their actual usage. This minimises costs while staying compliant. The guiding principle is least-privilege licensing — give each user the lowest-tier licence that covers all the transactions they perform.
Even savvy organisations fall into classic traps when managing SAP user licences. CIOs should watch for and address these missteps.
The most rampant mistake. This "one-size-fits-all" approach leads to massive overspending, since many users never utilise the full capabilities of a Professional licence. It usually happens out of convenience or fear of under-licensing. Instead, assign the licence type based on role — don't use an expensive umbrella when a smaller one will do.
Companies accumulate SAP accounts for people who no longer work there or no longer need access. If these user IDs aren't deactivated and their licences reclaimed, they continue counting toward your licence total and maintenance fees. Inactive users can quietly "hog" licences for years.
It's common to find SAP developers, Basis administrators, or technical support users assigned expensive Professional licences. In many cases, a Developer licence would cover their needs at a lower effective cost. If technical staff are not performing operational tasks in SAP, classify them under the developer/technical category.
SAP's named user model doesn't allow sharing logins, yet some companies create generic accounts (like "ShopFloor1" or "TestUser"). Each account — even if shared — requires a licence. Similarly, one person might have multiple accounts across systems. Every unique login counts. Leverage SAP's LAW tool to link duplicate accounts so they're counted as one named user.
Identify and eliminate licence waste before SAP's auditors find it first.
SAP Licence Optimisation Service →Before you can optimise, you need a clear picture of your current SAP user landscape. Data is your ally — gathering the right information will highlight where the problems are.
Export a list of all SAP user accounts (using transaction SU01 or relevant user administration reports). Include username, assigned licence type, last login date, and user group or role. This shows who has what licence currently and who hasn't logged in recently.
Run USMM (User Measurement) in each system to get SAP's perspective on how many users fall into each licence category. Use LAW (Licence Administration Workbench) to consolidate data across multiple systems and identify duplicates. These tools simulate what SAP's auditors will look at, giving you a baseline.
Inactive accounts — users with no login activity for 3, 6, or 12 months — are candidates for deactivation. Duplicate accounts should be consolidated. Flag users with Professional licences who barely use the system — they're prime candidates for downgrading. Also catch under-licensed users performing critical transactions beyond their allowance.
With a clear view of the discrepancies in your SAP user licensing, you can methodically right-size licence assignments. Follow these steps to clean up and reallocate licences.
Start by removing or deactivating any user IDs that are no longer needed. Shut down accounts for departed employees and ended contractors. Delete old test users and generic accounts. This immediately frees up licences and improves security. Maintain a policy to automatically lock and review any account inactive for 90+ days.
Downgrade users who have more licence than they need. If someone has a Professional licence but only runs basic reports, switch to Limited Professional. If 500 employees are on Professional but only use self-services, reclassify as ESS users. The guiding principle is least-privilege licensing — the lowest tier that covers all transactions performed. Also correct any under-licensed users to prevent audit findings.
Review all accounts used by developers, system integrators, or for background jobs and interfaces. Ensure technical users are classified appropriately (often as Developer users) instead of consuming full business user licences. Batch job users performing data loads may not need a Professional licence. Eliminate training accounts or test logins in production.
In operations where multiple individuals share the same role in shifts (call centres, plant operators), evaluate whether you truly need separate licences for each individual. If three people cover one position across three shifts, consider a licence pooling approach. At minimum, avoid automatically buying three full licences without analysis. Discuss any such arrangements with SAP to stay compliant.
Following these steps, you'll progressively eliminate waste: first by clearing out accounts that shouldn't count at all, then by ensuring each remaining user is classified to the optimal licence type. The result is a leaner, more accurate licence portfolio.
Manually sifting through user data can be tedious, especially in large SAP landscapes. Fortunately, there are tools to automate and streamline SAP licence optimisation.
USMM (System Measurement) and LAW (Licence Administration Workbench) are provided by SAP for audit purposes, but you can run them any time to self-audit. LAW is particularly useful for multi-system landscapes — it detects the same person's accounts across environments so you don't double-count. Make it routine to run these tools internally and examine the results. They flag unclassified users (which default to Professional) and give a snapshot of licence counts versus entitlements.
Software Asset Management (SAM) tools from vendors like Voquz, Snow, ServiceNow, and others can automatically analyse user roles and transaction history to suggest the appropriate licence type for each user. They provide dashboards identifying over-licensed and under-licensed users. Some simulate different licensing scenarios or enforce policies (auto-assigning default licence types based on role). While these tools have their own cost, they quickly pay for themselves by uncovering optimisation opportunities.
Need expert help analysing your SAP user licence landscape?
SAP Licence Optimisation →Optimising licences isn't a one-time project — it should become an ongoing part of your IT governance. Here's how to embed continuous licence management in your operations.
Treat SAP licence reviews like financial audits or security reviews. Set a schedule (quarterly is a good cadence) to revisit all user accounts and licence assignments. Update changes — people changing roles, leaving, or new hires coming in. Regular check-ups ensure you won't backslide into misclassification. It's far easier to make small adjustments every quarter than to do a massive true-up right before an SAP audit.
Integrate licence management with HR processes. When someone leaves or no longer needs SAP access, immediately reclaim that licence. When onboarding a new user, check for surplus licences from recent departures and assign appropriately, rather than purchasing new. Establish a policy that defines who decides the licence type for a new user (based on role mapping, not whim) and handles transfers between roles.
Ensure it's clear who in your organisation is responsible for SAP licence compliance and optimisation. Define processes for how licence decisions are made and documented. Train security administrators and helpdesk staff on the importance of correct licence assignment from the start. When everyone knows that "a sales clerk gets a Functional User licence, not Professional," you prevent the lazy default of giving out Professional licences.
By embedding governance practices, you establish a sustainable model that enables continuous licence optimisation. The payoff is not just in savings, but in being audit-ready at any time and having confidence that your SAP user count and classifications are always current.
Optimising named user licences not only saves money internally but also strengthens your hand when dealing with SAP on contracts. Here are tactics to leverage your optimisation in negotiations.
When you reduce the number of expensive licences, it's not just licence fees you save. SAP's annual maintenance fees (typically around 22% of licence price) will decrease. Ensure changes are reflected in your next maintenance renewal. Align your internal cleanup with the timing of your SAP support contract renewal so you can adjust official licence counts downward and immediately cut recurring costs.
SAP is often resistant to reducing licence counts, but during renewal or new purchase negotiations you have leverage. Bring data from your optimisation efforts. If you've identified 200 surplus Professional licences, negotiate a conversion into cheaper licence types or other products of equivalent value. Push to eliminate contractual clauses enforcing fixed ratios of licence types. Seek freedom to reallocate licences as business needs change.
If you identify unused licences (shelfware), formally surrender them to remove them from your maintenance base. SAP representatives may claim you can't, but if you properly relinquish the right to use them, they can be removed from your support bill. Give SAP notice three months before your renewal date. This requires planning but is entirely achievable.
When SAP knows you're on top of your licence usage — and not afraid to challenge the status quo — you're in a far better position to negotiate contract terms. Any cost you cut from licences isn't just a one-time saving; it's a reduction in your cost base for years to come.
Preparing for an SAP contract renewal? Leverage your optimisation data.
SAP Contract Negotiation →What kind of impact can a CIO expect from diligent SAP user licence optimisation? Significant savings and risk reduction.
Organisations that undergo this process typically reduce their count of full Professional users by 10–20% (or more) without compromising operations. Those users are reclassified to more cost-effective licences that better meet their actual needs.
If your SAP Professional licence costs $3,000 and you downgrade 200 to $1,500 Limited licences, that's $300,000 in cost avoidance — plus about $60,000 less in annual support fees going forward. The exact numbers vary, but the pattern is clear: licence optimisation pays for itself many times over.
Every licence you eliminate or downgrade means lower maintenance costs every budget cycle. Over a 5- or 10-year period, the cumulative effect is substantial — money that can be reinvested into innovation instead of licensing overhead.
By cleaning up user licences, you dramatically lower the risk of an audit surprise. Many CIOs find that after optimisation, the company can breeze through SAP audits with minimal findings — avoiding the panic and unplanned expenses that audits often bring.
Right-sizing your SAP named users leads to a leaner, more cost-effective licence footprint. You'll spend less on SAP year after year, and sleep better knowing your compliance is under control. It's a strategic win for IT cost management and a tactical win for licensing teams.
To ensure your SAP user licences remain optimised, CIOs should incorporate the following action steps into their IT management routine.
Regularly review all SAP accounts and their activity to catch changes, inactive users, or misclassifications. Use USMM and LAW across all systems.
Continuously identify users who can be moved to a cheaper licence tier without impacting their work. Apply the least-privilege licensing principle.
Promptly clean up user accounts when employees leave or no longer need access, so licences aren't wasted on shelfware.
Use internal audit data to adjust your SAP contract — eliminate or swap out surplus licences during true-ups or renewals to reduce costs.
Leverage SAP's tools or third-party solutions to monitor user activity and help assign the right licence types as an ongoing practice.
Automate licence reclamation when employees leave. Assign correct licence types during onboarding based on role mapping. Establish a licence recycling policy.
Assign clear responsibility for SAP licence compliance. Define processes for licence decisions and train security administrators on correct assignment practices.
Have an independent SAP licensing advisor validate your licence position, identify hidden risks, and support negotiation strategy with SAP.
Facing an SAP licence audit? Our former SAP experts defend your position.
SAP Audit Defence Service →Whether you need a licence audit, shelfware elimination, contract renegotiation, or audit defence — Redress Compliance provides expert, independent SAP advisory from former SAP licensing specialists.
Explore our complete SAP licensing knowledge hub — playbooks, guides, and case studies.
SAP Knowledge Hub →