SAP Licence Cost Reduction: 8 Quick Wins You Can Implement Without Renegotiating

Named User Professional licences cost 3–5x more than Limited Professional. Most enterprises have 20–40% of their user estate over-classified — not through deliberate decision-making, but through IT provisioning defaults that assign broad role profiles to new users without reviewing licence type implications.

USMM measures user classification based on system role assignments and authorisation profiles, not actual transactional usage. A user assigned a role that includes even one Professional-level transaction will be classified as Professional — regardless of whether they ever run that transaction. The steps to take now:

• Export your current USMM classification output and compare against actual transaction usage data from SM20 or system logs
• Identify users whose actual usage patterns fall within Limited Professional definitions (primarily read-only or single-module users)
• Submit a formal reclassification request to SAP with documented transaction evidence
• Update role provisioning governance to prevent over-classification recurrence

SAP's response

SAP's account team will resist reclassification without documentation. Come prepared with USMM extracts, transaction usage logs, and job function descriptions. Our licence optimisation team has documented reclassification frameworks that SAP accepts.

SAP counts all licensed users in your system regardless of activity. Users who left the organisation months ago, contractors whose projects ended, or employees on extended leave continue to consume named user entitlements and generate maintenance charges. Inactive account hygiene is the lowest-effort, fastest-return optimisation available.

SAP's definition of "named user" is contractually specific — a real person who has been authorised to use the system. Inactive accounts where the individual no longer needs access can legitimately be removed from the licence count with no contractual risk. The key actions:

• Run a named user audit via SM04 and SU01 — identify any account with zero login activity in the past 90 days
• Cross-reference against HR system to identify accounts for employees no longer active
• Lock, deactivate, or delete accounts that cannot be justified
• Implement an automated offboarding process to prevent future accumulation

USMM — SAP's primary measurement tool — applies automated classification logic that frequently overcounts. Before submitting annual measurement data, enterprises should review and challenge specific classification outputs rather than accepting them at face value. Key areas where USMM commonly overcounts:

• Interface/technical users: System-to-system integration accounts often get classified as full named users rather than the cheaper Technical User type
• Test accounts: Development and QA system users should not appear in production licence counts — verify system landscape classification in Solution Manager
• Emergency access accounts: Firefighter IDs and emergency access accounts may trigger Professional classification without representing real usage
• Basis/admin accounts: SAP Basis administrators running only technical functions are often over-classified

Challenge each of these categories with documented evidence before submission. What you submit to SAP becomes your declared Effective License Position (ELP) — and any gap becomes a compliance claim.

SAP BTP credits are bundled into most RISE with SAP contracts, and enterprises frequently over-commit on BTP credit quantities at contract signature based on projected consumption that never materialises. 70% of enterprises consume less BTP credit than contracted — but because the credits are typically use-or-lose within the contract year, the surplus represents pure waste.

The immediate win is not recovering wasted credits — it's right-sizing your commitment for the next contract period. Use SAP BTP Cockpit to pull actual consumption data by service and compare against contracted quantities. Then:

• Identify services where provisioned credits vastly exceed consumption
• Build a 12-month consumption forecast based on actual usage patterns, not SAP's projections
• Use the consumption gap data as evidence in the next contract negotiation to reduce credit commitment (and the associated charges)
• Identify credits expiring within the next 90 days and accelerate legitimate consumption to avoid waste

For a deeper analysis of how BTP credits work, see our guide to SAP BTP credit consumption.

Indirect access — where third-party systems read from or write to SAP without licensed users — is the single largest source of unquantified SAP audit exposure. Enterprises with CRM, WMS, HR, IoT, or bespoke integration systems connecting to SAP often have significant undisclosed exposure that SAP's audit team will identify and monetise.

The quick win here is not eliminating the exposure — it's knowing your own exposure before SAP measures it. Running your own internal indirect access assessment gives you three advantages:

• You understand the scope and can calculate exposure before SAP inflates it
• You can pursue Digital Access document-based pricing (typically far cheaper than traditional indirect access rates) proactively
• You can remediate the highest-risk integrations before audit notification arrives

Our indirect access advisory service conducts rapid landscape assessments and helps enterprises negotiate appropriate Digital Access coverage before audit pressure forces unfavourable terms.

SAP shelfware — licences purchased but never deployed — generates 22% annual maintenance charges indefinitely. The quick win is not recovering the initial licence cost (which is essentially sunk), but stopping the maintenance bleed and building a case to use unused entitlements as negotiating currency in the next commercial discussion.

Map your purchased entitlements against your actual USMM-measured deployment. Any product category where entitlement significantly exceeds measurement is candidate shelfware. Document it, cost the annual maintenance drain, and prepare to use it in your next negotiation to offset new licence requirements rather than paying twice.

SAP's production licence entitlements cover production system usage. Development, QA, and test systems should be governed by SAP's landscape rules — which permit development/test use without additional named user licences under certain conditions. However, if your non-production systems are not correctly categorised in SAP Solution Manager's Landscape Management Database (LMDB), USMM may include their user counts in your production measurement.

Check that each system in your landscape is correctly classified as Development, Test, or Production in Solution Manager. Incorrect classification is common, especially in organisations that have grown through acquisition or rapid system deployment. Correcting landscape classification can reduce measured user counts without any commercial negotiation whatsoever.

The structural quick win is process, not negotiation. Enterprises that implement a quarterly SAP licence governance review consistently maintain lower cost positions than those that only examine licences at renewal or audit. A 90-day review cycle should cover three areas:

• User audit: Review new user provisioning, departures, role changes, and classification accuracy quarterly
• Landscape changes: Any system additions, integrations, or module deployments reviewed for licence impact before go-live
• Consumption tracking: BTP credits, Digital Access documents, and package licence usage monitored against contracted entitlements

This governance cycle is the foundation of the SAP Licence Management Office model. It does not require large investment — it requires designated ownership and structured process. See our guide to SAP licence compliance for a framework to implement today.