Key Takeaways

  • Never accept SAP's ELP as accurate. The opening claim is systematically inflated through maximum classification, inactive user inclusion, and list price application.
  • The three-track challenge methodology — technical, contractual, and commercial — produces significantly better outcomes than single-track approaches.
  • Inactive user cleanup alone typically reduces the measured user count by 10–25% before any contractual arguments are needed.
  • Custom licence type definitions in your contract may be more favourable than SAP's standard USMM classifications — and they govern, not SAP's tools.
  • Building your own counter-ELP with full supporting evidence is the single most impactful document you can produce in an SAP audit defence.

Why SAP's Opening Claim Is Always Wrong

To understand why you must challenge SAP's initial audit claim, you first need to understand how that claim is constructed. SAP's Effective Licence Position is produced by applying USMM and LAW measurement outputs to your purchased entitlement data, then pricing the resulting shortfall at list rates. At every step of this process, SAP's tools and methodology systematically bias the result upward.

USMM applies maximum licence type classification when a user's authorisation profile is ambiguous — it assigns the highest applicable licence category, not the most commercially reasonable one. LAW's consolidation logic for multi-system landscapes is prone to double-counting users who exist across migration environments. STAR's classification rules may not align precisely with the custom licence type definitions in your specific contract. And the entire output is priced at SAP list rates, which in practice no enterprise pays.

The result is an opening ELP that typically represents 150–300% of the legitimate commercial liability. This is not accidental — it is structural. SAP's GLAC team knows that most buyers will negotiate down from the opening position without scrutinising the individual lines, allowing SAP to settle at a figure that still captures substantial overcharge. This is the complete context for the SAP audit process overview: the challenge is where the real value is created.

⚠ The Most Expensive Mistake

The most expensive mistake enterprises make in SAP audits is treating the challenge as a negotiation over the discount rather than a challenge to the underlying claim. Negotiating a 30% discount from an inflated ELP produces a worse outcome than challenging the ELP itself down to a legitimate figure and then negotiating the discount. Always challenge the claim before negotiating the terms.

The Three-Track Challenge Methodology

Track 01

Technical Challenge — Challenging the Measurement Data

The technical track attacks the accuracy of SAP's measurement outputs. USMM counts what it is configured to count — if your system has accumulated years of inactive users, over-privileged authorisation profiles, and system interface accounts, the USMM output will reflect that system debt rather than your actual operational reality.

Track 02

Contractual Challenge — Challenging the Legal Basis

The contractual track attacks SAP's legal entitlement to charge what it is claiming. Your licence agreement governs your obligations — not SAP's internal classification tools. If your contract defines user types differently from USMM's standard definitions, your contract governs.

Track 03

Commercial Challenge — Creating Negotiating Leverage

The commercial track operates above the technical and contractual level. SAP's settlement decision is ultimately commercial — how much risk of dispute, relationship damage, or account loss is acceptable to achieve a given settlement level.

Related Guide

For the complete technical breakdown of USMM and LAW — including classification logic, deduplication failure modes, and the exact preparation steps before measurement — see: SAP USMM & LAW Tools: The Complete Enterprise Guide for 2026. The step-by-step preparation guide is at: How to Prepare Your Systems Before SAP Runs USMM.

Track 1 — Technical Challenge Deep Dive

The technical challenge begins with your own independent USMM run — ideally conducted after a period of user master record cleanup that removes the systematic errors that inflate SAP's measurement. The goal is to establish a defensible technical baseline that you can present as your counter-position to SAP's measurement.

User Master Record Cleanup

Before running your own USMM, address the following user categories systematically:

  • Inactive users: Users with zero system login in the previous 12 months. In most enterprise SAP landscapes, 8–20% of active named user accounts fall into this category due to staff turnover, role changes, or incomplete deprovisioning processes. These users should be deactivated — not deleted — in the user master record before measurement. Deactivation removes them from the USMM active user count.
  • System interface accounts: Background processing users, RFC connection accounts, and batch job execution users are technical accounts that execute automated processes without human login. They should be classified as "System" or equivalent non-named user types, not as Professional or Limited Professional users. SAP's USMM may classify these as Professional Users if their authorisation profiles include high-tier transaction codes.
  • Test and training users: Test accounts and training environment users should be excluded from production user counts. If they appear in USMM output, they should be specifically identified and removed from the shortfall calculation.
  • Locked and expired accounts: User accounts with a validity end date in the past, accounts locked by the system administrator, and accounts associated with former employees are all includable in USMM by default but should not be counted against your licence position.

Authorisation Profile Review and Reclassification

USMM assigns licence types based on the highest-tier transaction codes in a user's authorisation profile. A user whose profile includes a Finance transaction code — even if they only ever actually use a single reporting function — may be classified as Professional User on that basis alone.

The reclassification process involves reviewing the actual transaction usage logs (SM20, ST05, or equivalent) for users who are classified at a higher tier than their business role warrants. If a user's actual logged transaction usage is entirely consistent with a lower licence tier, you can build a user-by-user evidence file supporting reclassification. This is labour-intensive but typically yields the largest single reduction in the claimed shortfall.

Practical Result — User Reclassification

In a typical mid-size enterprise audit with 8,000 active named users, user master record cleanup and authorisation-based reclassification together reduce the measured shortfall by an average of 1,500–2,500 users. At average list prices of €2,000–€4,000 per Professional User licence, this represents €3M–€10M in claim reduction before any contractual arguments are advanced.

Track 2 — Contractual Challenge Deep Dive

The contractual challenge requires a line-by-line review of your SAP licence agreement, all amendments, ELA schedules, and any side letters. The key contractual arguments available in most enterprise licence agreements include:

Custom User Type Definitions

Many large enterprises negotiated custom user type definitions in their original ELA. These definitions may be more favourable than SAP's standard USMM classification categories. If your contract defines a "Limited Professional User" as someone who performs specific functions without reference to SAP's standard transaction code list, and SAP's USMM classifies users based on its standard transaction list rather than your contractual definition, SAP's classification is wrong. Your contract governs.

Identifying these discrepancies requires simultaneously holding the contractual user type definition and the USMM classification logic in view — which is why independent SAP licensing advisors with contract law expertise are essential for the contractual track.

Consolidation and M&A Provisions

If your contract includes landscape consolidation rights — common in large enterprise ELAs — you may be entitled to consolidate licences across acquired entities, merged systems, or parallel migration landscapes without additional charge. SAP's USMM does not automatically apply these provisions; you must identify and assert them explicitly in your challenge.

Indirect Access and DAAP Scope

If SAP's ELP includes indirect access or Digital Access charges, the contractual basis for those charges must be examined carefully. Pre-DAAP legacy contracts that use "Named User" indirect access language may not support document-based Digital Access charges. Post-DAAP contracts that include specific document type commitments govern on those terms. Either way, SAP's indirect access claims frequently exceed what the contract actually supports. Our audit defence team specialises in indirect access contract analysis.

Track 3 — Commercial Challenge Deep Dive

The commercial track operates at the business relationship level. Its goal is not to defeat SAP's claim — that is the technical and contractual track's job — but to create the commercial conditions under which SAP will settle at your challenged position rather than its revised position.

Demonstrating Commercial Alternatives

SAP's settlement flexibility expands significantly when the account is at risk. Credible, documented alternatives — third-party maintenance providers, non-SAP ERP evaluations, cloud migration programmes that reduce on-premise SAP footprint — signal that SAP's future revenue from the account is not guaranteed. This context changes the settlement calculation from "how much can we extract?" to "how do we preserve the relationship while closing this case?"

The commercial signal must be credible. A passing mention that you "might consider alternatives" is easily dismissed. A formal RFP process, a published migration roadmap, or an active third-party maintenance evaluation — documented and referenced in your challenge response — creates genuine commercial pressure.

Executive Escalation

SAP's GLAC team operates with defined settlement authority. When the gap between the challenged position and SAP's revised position remains substantial, escalating the negotiation to SAP's senior account management or regional leadership often unlocks additional flexibility that GLAC cannot grant unilaterally. Escalation signals that the account is strategically important and that the audit is creating relationship risk — both of which expand SAP's settlement latitude.

Building Your Counter-ELP

The counter-ELP is your formal written response to SAP's Effective Licence Position document. It should contain three sections: a technical rebuttal (your corrected user count and licence type classification, with supporting evidence), a contractual rebuttal (the specific contractual provisions that modify or eliminate specific line items in SAP's claim), and a commercial position (your proposed settlement and the basis for it).

The counter-ELP should be a professional document that a senior SAP executive, legal counsel, and a neutral arbitrator could all read and find credible. Emotional or polemical language weakens your position. Specific, evidenced, contractually-grounded arguments strengthen it. The SAP audit defence guide provides a structural template for building a robust counter-ELP.

✓ Counter-ELP Results Benchmark

Enterprises that submit a well-constructed counter-ELP — supported by corrected USMM outputs, user-level reclassification evidence, and specific contractual arguments — typically reduce SAP's revised claim to 30–50% of the opening figure within two rounds of formal exchange. Enterprises that submit informal "we disagree" responses without detailed evidence typically see SAP revise its claim by only 10–20%.

Our Services

Independent SAP Audit Defence

We build your counter-ELP, run the technical challenge, and manage the negotiation. 100% buyer-side, no SAP affiliation.

Explore Audit Defence → Case Studies

Real Challenge Results

See how our three-track methodology reduced audit claims from €12M to €3.1M and €8M to €2.4M for enterprise buyers.

Read Case Studies →

Related Articles in This Series