SAP ELP & Compliance Gap: The Complete Enterprise Guide for 2026

The SAP Effective Licence Position — universally known as the ELP — is the document that defines the financial outcome of every SAP audit. It sits at the heart of the sap-elp-compliance-gap process: a structured reconciliation of what your contract says you own against what SAP's measurement tools claim you are consuming. The compliance gap is the delta — and it is the number SAP will invoice you for if you let it stand unchallenged.

In 2026, with SAP's auditors intensifying pressure ahead of the ECC 2027 end-of-maintenance cliff, understanding the ELP in forensic detail is not optional for enterprise buyers. It is survival arithmetic.

This guide covers every dimension of the ELP: how SAP constructs it, where errors systematically appear, how to build your own counter-position, and the structured methodology for closing — or eliminating — the compliance gap on terms that protect your business.

1. What Is the SAP Effective Licence Position?

The Effective Licence Position is a formal document, typically presented in a spreadsheet by SAP's licence compliance team or a partner auditor such as KPMG or Deloitte acting on SAP's behalf. It has three primary columns:

On its face, the ELP looks objective. In practice, it is shaped by a series of methodological choices — user classification rules, landscape consolidation decisions, engine metric calculations — that systematically overstate consumption and understate entitlement. Every one of those choices is contestable.

📬 SAP Licensing Intelligence

Get Independent SAP Licensing Insights

Expert analysis on SAP audits, contracts, and cost reduction — direct to your inbox. Corporate email required.

Please use a corporate email address (no Gmail, Yahoo, Hotmail, etc.)

Subscribe — Free Intelligence →

2. How SAP Builds Its Effective Licence Position

SAP's measurement methodology is built around three tools that work in sequence. Understanding this sequence is foundational to any ELP defence strategy.

USMM — The User and System Measurement Transaction

USMM (transaction code /nUSMM) is an ABAP transaction executed inside the SAP system — either by SAP's auditors with temporary access, or by your own team using the LAW self-declaration route. USMM classifies every named user in the system based on their assigned role profiles and the transaction codes those profiles permit access to. Critically, USMM uses a capability-based model: it classifies users not by what they actually do, but by what their authorisation profiles theoretically allow them to do.

This is the primary source of ELP inflation. A warehouse operative whose role profile was copied from a power user profile — a common IT shortcut — may appear in USMM as requiring a Professional User licence even if they only ever approve goods receipts. Every such user inflates the measured position and widens the compliance gap.

LAW — The Licence Auditing Workbench

The Licence Auditing Workbench (LAW) consolidates USMM data across multiple SAP systems. In a multi-system landscape — ECC, CRM, BW, SRM, and so on — LAW applies system consolidation rules to avoid double-counting users who are active across several systems. The highest licence type across all systems generally determines classification in the consolidated ELP.

LAW consolidation is another rich source of errors. The system requires accurate landscape mapping: if your quality, development, or training systems are incorrectly included in the production landscape measurement, user counts become inflated. In one engagement we reviewed, a client's development system containing 340 technical test users was inadvertently included in the LAW consolidation, adding €1.4 million to the initial compliance gap claim. The fix was a configuration correction, not a licence purchase.

SLAW — The SAP Licence Audit Workbench

SLAW is the external tool used by SAP's auditors to receive, process, and present measurement data. It adds engine metrics — database sizes, package-based licensing, HANA memory, BTP consumption — on top of the named-user data from USMM/LAW. SLAW is where the ELP spreadsheet you receive is actually generated.

The SLAW-generated ELP often contains engine metric assessments that are disconnected from your actual system configuration. HANA memory calculations, for example, are frequently based on total addressable memory rather than licensed memory tiers as defined in your contract. Our SAP audit defence engagements regularly identify engine metric errors worth seven figures.

3. Key Components of an ELP Document

A well-structured SAP ELP will contain separate sections — or tabs in the spreadsheet — covering each of the following areas. Knowing what should be there helps you identify what SAP has chosen to omit or aggregate.

Named User Licences

This is almost always the largest section of the ELP and the most contestable. Named users are classified into SAP's user type hierarchy — typically Professional User, Limited Professional User, Employee User, Employee Self-Service (ESS), and various specialist types depending on your contract generation. The compliance gap here is driven by user overclassification, stale user accounts, technical/system users wrongly classified as named users, and users who have left the organisation but not been deprovisionned.

Engine and Package Licences

This section covers metric-based licences: HANA database sizes, BW data volumes, SCM order counts, CRM transaction volumes, and so on. These metrics are measured at a point in time and can fluctuate significantly depending on when the measurement is taken. SAP auditors are not required to time measurements to minimise your exposure — and they won't.

Indirect / Digital Access

Since SAP's landmark Diageo settlement in 2017 and the subsequent introduction of the Digital Access Adoption Programme (DAAP), indirect access has been a significant and often opaque component of compliance gap claims. If third-party systems — your own applications, partner portals, IoT sensors, RPA bots — create, modify, or delete documents in SAP, SAP may assert that document-based licensing applies. This area requires specific contractual analysis: DAAP applies only if your contract references it, and many contracts pre-2017 do not.

Cloud and BTP Consumption

For SAP customers with RISE with SAP, BTP, or cloud product subscriptions, the ELP may include consumption-based metrics that are pulled from cloud usage reports. These are typically more straightforward but can include expired or orphaned subscriptions that should have been decommissioned.

4. The Eight Most Common Sources of Compliance Gap Inflation

In our experience across hundreds of SAP audit engagements, compliance gap inflation consistently originates from the same categories of error. Each category represents a forensic challenge target.

1. User Overclassification via Bloated Role Profiles

The single largest source of ELP inflation. SAP's USMM classifies users by their authorisation profiles, not their actual usage. When role profiles are over-permissioned — containing transaction codes that trigger higher licence types — users are systematically upgraded to more expensive categories. The fix is demonstrating that the underlying role profiles exceed operational need, and agreeing a re-classification based on actual business function.

2. Stale and Unused User Accounts

User accounts that have not been accessed in 90+ days — leavers, contractors, employees on extended leave — are still counted in USMM unless they carry a validity date. This is a governance failure with direct financial consequence. An exercise to identify and lock or delete dormant accounts before measurement can materially reduce user counts.

3. Technical and System Users Miscounted as Named Users

Technical users — background job users, RFC communication users, EDI batch users, and similar system accounts — should not consume named user licences under SAP's standard policies. However, if they are not correctly type-flagged in the system (user type = B or S in SU01), USMM will include them in the named user count. A focused technical user review typically yields significant reductions.

4. Non-Production System Inclusion

Development, QA, training, and sandbox systems should generally not contribute to your production licence measurement unless your contract specifically includes them. Inadvertent inclusion of non-production landscape in the LAW consolidation is a common auditor error — or an opportunistic inclusion that is rarely disclosed as such.

5. Indirect Access Over-Assertion

SAP's indirect access assertions are often significantly broader than their contractual basis. Many customers have successfully challenged indirect access claims on the grounds that: the contract predates SAP's DAAP framework; the third-party integrations use standard SAP interfaces (which carry different rules); or the document counts used by SAP's auditors include cancelled, test, or duplicate documents.

6. Engine Metric Over-Measurement

HANA database sizing, BW data volumes, and SCM metrics can vary by 30–50% depending on measurement timing and methodology. SAP auditors have discretion in timing — and the incentive is always to measure at peak. Contractual definitions of metric measurement (e.g., maximum versus average, including or excluding backups) are frequently misapplied.

7. Wrong Contract Schedule Applied

Enterprises with complex contract histories — multiple purchases, conversions, MVLS agreements — sometimes find that SAP's auditors have applied the wrong contract schedule to calculate contracted entitlement. This can both understate your contracted position and apply incorrect price lists for the compliance gap valuation.

8. S/4HANA Transition Classification Errors

Customers who have converted to S/4HANA or are in the process of conversion are subject to updated user classification rules that differ from legacy ECC metrics. Applying ECC user type rules to an S/4HANA system — or vice versa — is a recurring source of ELP distortion that requires version-specific contractual analysis.

Our Services

Independent SAP Audit Defence

Forensic ELP review, compliance gap challenge, and settlement negotiation — exclusively for enterprise buyers.

Explore Audit Defence → Case Studies

ELP Defence Results

See how enterprises reduced their compliance gap claims by 40–65% through forensic ELP challenge.

Read Case Studies →

5. How to Read and Interpret Your ELP

When SAP's audit team delivers the initial ELP, most enterprises make the mistake of treating it as a negotiating starting point — accepting the structure as valid and arguing only about the price. The correct approach is to challenge the ELP's foundational validity before entering any discussion of value.

Step 1: Verify the Contracted Position

Pull your complete contract history — the original Enterprise Licence Agreement (ELA), all supplements, any Global Master SAP Agreements (GMSAs), Order Forms, and any MVLS migration agreements. Map every line of the ELP's contracted position against the actual contract language. SAP auditors sometimes understate entitlement, particularly where legacy entitlements were not formally migrated in more recent contracts.

Key questions: Does the ELP reflect all licence types you contracted? Have any licence types been sunset by SAP in a way that should have converted your entitlement to equivalent current types? Are all supplementary licences captured?

Step 2: Audit the Measurement Methodology

Request the raw USMM and LAW data files that underpin the ELP. SAP is often reluctant to provide these, but you are entitled to understand the basis for the measurement claim. The data files will reveal: which systems were included in the landscape consolidation; how technical users were treated; which role profiles drove user uplift; and what measurement date was used for engine metrics.

Step 3: Run Your Own Independent Measurement

The most powerful response to an SAP ELP is a counter-ELP built on your own data. This involves executing USMM and LAW yourself, after conducting the remediation work described above — removing dormant users, correcting technical user flags, verifying landscape scope. The resulting measurement becomes your negotiating baseline. Learn more in our guide to building your own SAP Effective Licence Position.

Step 4: Line-by-Line Challenge

For each compliance gap line, prepare a written challenge that identifies: the specific error or over-assertion; the contractual basis for your challenge; the corrected figure; and the supporting evidence. This challenge document forms the basis of your formal response to SAP's audit team and, if necessary, the foundation for escalation or legal proceedings.

6. The ELP Challenge Process: A Structured Approach

Challenging the SAP ELP is not a confrontation — it is a structured professional process that SAP's own contractual terms accommodate. The audit contract clause in most enterprise licence agreements includes provisions for query and validation periods. Understanding and using these provisions is not adversarial; it is contractual due diligence.

Phase 1: Acknowledgement Without Acceptance

On receipt of the initial ELP, acknowledge it in writing within the timeframe specified in your contract (typically 30–60 days). Do not acknowledge accuracy — acknowledge receipt. A simple written response stating that you have received the document, are reviewing it in detail, and will provide a formal response within the contractual period is sufficient. This preserves your right to challenge without triggering default provisions.

Phase 2: Internal Remediation Sprint

In parallel with formal review, execute an internal remediation sprint. This involves your SAP Basis team, IT governance, and HR/identity management. Key activities include: running USMM internally to understand your pre-remediation position; auditing dormant accounts against HR termination records; reviewing technical user type assignments; and validating your landscape scope against the contract's system scope definition.

Phase 3: Formal Written Challenge

Submit a formal written challenge to SAP's licence compliance team that addresses each material error in the ELP. Structure the challenge by section — named users, engine metrics, indirect access — and support each challenge with documentary evidence. Where your counter-measurement produces different numbers, provide the USMM/LAW export data as an appendix.

For a detailed methodology on this challenge process, see our guide on challenging SAP's ELP with an evidence-based approach.

Phase 4: Negotiated Settlement

The vast majority of SAP ELP disputes are resolved through negotiation rather than litigation. SAP's commercial model depends on customer relationships, and their audit teams have significant latitude to agree revised figures — particularly where you have presented credible, document-supported challenges. Settlement negotiations should address not just the gap amount but also the price applied (current list price vs. discounted price vs. SAP's Price Protection right) and the commercial packaging of any back-licence payment.

For a detailed breakdown of what to expect at each stage of the ELP dispute process, see SAP ELP vs SAP's Measurement: Closing the Gap.

7. The ELP in the Audit Settlement Context

The compliance gap figure in the ELP becomes the basis for SAP's settlement demand. Understanding how SAP converts that gap into a monetary claim — and the levers available to reduce it — is essential for any enterprise navigating SAP audit defence.

How SAP Prices the Compliance Gap

SAP applies list price — the current SAP Global Price List — to the compliance gap units. This produces an eye-watering initial figure that is almost never the final settlement number. The list price figure is a ceiling, not a floor. SAP's auditors know this, and they know you know it. The real negotiation is about the discount applied to the compliance gap valuation.

SAP typically offers a commercial package that bundles back-licence costs with a new cloud product or RISE with SAP commitment. These bundles are designed to convert audit liability into forward-looking revenue for SAP. They are almost always structured in SAP's favour. Any commercial bundle offered in the context of audit resolution should be analysed independently — the back-licence relief being offered is frequently less valuable than it appears once you account for new multi-year commitments.

Price Protection Clauses

Many enterprise licence agreements contain Price Protection clauses that allow customers to purchase additional licences at their original contract price — not current list — for a defined period. If your contract contains such a clause and the audit measurement period falls within the protection window, the per-unit cost of the compliance gap should be significantly lower. These clauses are frequently not applied by SAP unless the customer explicitly invokes them.

The Role of SAP Maintenance

Back-licence payments typically include both the licence fee and retroactive maintenance (typically 22% of licence fee per annum). In negotiations, the maintenance backdating period is often a key battleground. Limiting the maintenance look-back period to 12 months rather than the full audit period can substantially reduce the settlement total.

8. Expert Strategies for Minimising Your Compliance Gap

The following strategic principles consistently produce the best outcomes in SAP ELP disputes. They represent the consolidated learning from hundreds of buyer-side audit engagements.

Engage an Independent Adviser Before Responding

The single highest-return action most enterprises can take is to engage an independent SAP licensing adviser — one with no SAP affiliation, no reseller relationship, and no conflict of interest — before submitting any formal response to the ELP. An expert reviewer will identify challenges you would miss and will understand SAP's commercial leverage points in ways that in-house legal teams typically do not.

Never Rely on SAP's Auditors to Find Your Credits

SAP's audit teams — and their partner auditors — are measured on audit revenue recovered. They have a structural incentive to find overages and no incentive to identify areas where you may be over-licensed. Counter-intuitively, many enterprises carry significant surplus licences in some categories (ESS, professional limited) while being under-licensed in others. A full licence inventory review often reveals offsetting credits that reduce the net compliance gap materially.

Manage the Measurement Timing

If you have any ability to influence the timing of the USMM measurement — and in self-declaration processes you do — time it to minimise your measured position. For engine metrics, ensure measurements are taken outside peak processing periods (end-of-month, fiscal year-end, peak operational periods). For user counts, complete your dormant account clean-up before measurement, not after.

Document Everything

Every communication with SAP's audit team should be in writing, with clear records of dates, claims made, and commitments given. Verbal agreements made in audit discussions are not binding, and SAP's internal audit teams have been known to repudiate oral assurances once the commercial team takes over settlement discussions. Written records are your protection.

Use the Audit as a Compliance Programme Driver

The ELP process, uncomfortable as it is, provides a unique incentive to get your SAP licence governance in order. The enterprises that emerge from SAP audits in the strongest position are those that use the audit as a catalyst to implement ongoing licence monitoring, user governance, and contract management practices that prevent future gaps from accumulating. Our licence compliance programme is specifically designed for this objective.

9. Deep Dives: This Guide's Supporting Articles

10. The ELP in the Broader SAP Audit Process

The ELP does not exist in isolation. It is produced at a specific stage of the broader SAP audit process, and understanding where it sits in that process helps you deploy the right resources at the right time.

SAP audits typically follow a six-stage process: formal notification; landscape scoping; measurement execution; ELP delivery; challenge and negotiation; settlement execution. The ELP arrives at stage four. If you have used stages one through three effectively — validating the audit's contractual basis, scoping the landscape correctly, and conducting your own internal measurement — you will arrive at stage four with a strong counter-position already prepared.

For a full overview of the SAP audit process from notification to settlement, see our SAP Audit Process Overview: The Complete Enterprise Guide for 2026. For detailed guidance on the audit notification stage — the critical first 48 hours — see our guide to defending SAP audits.

Conclusion: The ELP Is a Negotiating Position, Not an Invoice

The most important thing to understand about the SAP Effective Licence Position is its contractual status: it is an assertion, not a determination. SAP's ELP represents SAP's view of your compliance position based on their measurement methodology, applied to your systems. That view is almost always contestable — and in our experience, it almost always overstates your exposure by a material amount.

The sap-elp-compliance-gap process rewards preparation, rigour, and independence. Enterprises that treat the ELP as an opening negotiating document — and who invest in understanding the methodology deeply enough to challenge it line by line — consistently achieve dramatically better outcomes than those who simply negotiate discounts off an unvalidated SAP figure.

The compliance gap SAP presents is not your compliance gap. It is SAP's measurement of your compliance gap, made using SAP's tools, according to SAP's methodological choices, at a time of SAP's choosing. Every one of those variables is open to challenge. Use that opportunity.