Key Takeaways

  • An evidence-based ELP challenge is a structured, written process — not an informal conversation. Every challenge claim requires documentation.
  • Six evidence types consistently move the needle in SAP ELP disputes: system data exports, contract extracts, HR records, IT governance documentation, independent measurement data, and SAP's own published methodology.
  • The challenge letter structure matters. A well-formatted challenge document that mirrors SAP's ELP layout is significantly more effective than a narrative response.
  • SAP's published classification rules — including the SAP Licence Type Determination Rules (LTDR) — are publicly accessible and provide the authoritative basis for challenging user type misclassification.
  • Indirect access challenges require specific contractual and technical evidence that most in-house teams are not equipped to assemble without specialist support.

Challenging SAP's ELP effectively requires two things: a clear understanding of what evidence is needed to support each type of challenge, and a formal written response structure that SAP's compliance teams must engage with professionally. When you dispute an SAP ELP claim, you are not having a conversation — you are building a documented record that will define the negotiation and, if necessary, support legal proceedings.

This guide is the final article in our series on the SAP ELP and compliance gap process. It assumes you have already reviewed your ELP, built a counter-position (see How to Build Your SAP Effective Licence Position), and understood the financial implications (see SAP Compliance Gap: How to Calculate Your Exposure). This article focuses on the specific evidence types required for each challenge category, and how to structure your formal challenge response.

The Evidence Principles of ELP Challenge

Before reviewing specific evidence types, three overarching principles apply to all ELP challenges.

Specificity over generality. A challenge that says "we believe the user count is overstated" is not a challenge — it is an opinion. A challenge that says "we believe 143 users classified as Professional in your ELP should be classified as Limited Professional, based on the attached USMM output dated 15 March 2026 and the role profile analysis attached as Exhibit C" is a challenge. Be precise about numbers, dates, and evidence references.

Written, dated, and addressed. Every formal challenge communication should be in writing, clearly dated, addressed to the named SAP contact on the audit correspondence, and sent through a channel that creates a record of delivery. Email with read receipt is acceptable; letter with tracked delivery is preferable for high-stakes disputes.

Reserve your position. When submitting a formal challenge, include standard reservation-of-rights language: "Nothing in this response constitutes an acceptance of any element of the ELP not specifically agreed in writing. We reserve all rights in relation to any unresolved items." This language prevents partial acknowledgements from being construed as full acceptance.

Six Evidence Types That Move the Needle

Evidence Type 1

System Data Exports

Raw USMM and LAW output files from your own independently-run measurement. These provide the technical foundation for every user count challenge.

Evidence Type 2

Contract Extracts

Specific clauses, schedules, and order forms from your contract chain that support your contracted position or challenge SAP's metric application.

Evidence Type 3

HR and Identity Records

Termination records, role change notifications, and identity management audit logs proving users are no longer active in the roles SAP claims.

Evidence Type 4

IT Governance Documentation

Landscape architecture documentation proving which systems are production vs. non-production, and access governance records for technical user classification.

Evidence Type 5

SAP's Own Published Rules

SAP's Licence Type Determination Rules (LTDR), SAP Note 1702947, and published indirect access guidance provide authoritative challenge basis for methodology disputes.

Evidence Type 6

Third-Party Technical Reports

Independent technical analysis by qualified SAP licensing advisers documenting measurement methodology, landscape scope, and role profile assessment findings.

Challenges by ELP Category

Challenging Named User Overclassification

The user classification challenge is the most common and typically most valuable ELP challenge. The evidence chain required is: the USMM output showing SAP's classification; your independently run USMM output showing the corrected classification; the role profile analysis documenting which profiles were amended and why; and a reference to the specific SAP LTDR rules that map the corrected roles to lower licence types.

The LTDR (Licence Type Determination Rules) is SAP's authoritative specification of which transactions map to which user types. It is available as an SAP Note and is the contractual basis for user classification in most enterprise agreements. When SAP classifies a user as Professional on the basis of transaction code access, cross-reference that transaction against the current LTDR to verify the classification is correct. Errors in LTDR application — particularly in older system landscapes where LTDR versions may have changed since the original classification was set — are a fruitful source of challenges.

The LTDR is Your Friend

Many SAP audit teams apply simplified or outdated LTDR interpretations. The published SAP Note for the current LTDR version — and its predecessor versions — provides a precise mapping of transaction codes to user types that you can use to challenge individual user classifications line by line. If a user's profile contains Transaction X, and Transaction X maps to Limited Professional under the LTDR, classifying them as Professional is an error — regardless of what USMM's automated classification engine outputs.

Challenging Technical User Inclusion

For technical users incorrectly counted as named users, the evidence chain is: a list of the disputed user IDs; for each, the User Type field from SU01 (or a table export from USR02); documentation of the user's technical purpose (system documentation, service desk records, or IT governance register); and reference to SAP's published guidance on technical user type assignments (SAP Note 323817 and successors).

SAP's auditors occasionally dispute technical user arguments on the basis that the user type field was not set correctly at the time of measurement — arguing that the incorrect type at measurement time controls, not the corrected type after remediation. Counter this by demonstrating that the user's function was technical throughout the audit period, even if the type flag was incorrectly set. Technical user function can be demonstrated through SM20 security audit log data showing non-dialog access patterns, and system documentation predating the audit.

Challenging Indirect Access Assertions

Indirect access challenges are among the most technically complex ELP disputes. They require: a precise contractual analysis of whether your contract references SAP's indirect access or DAAP framework (many pre-2017 contracts do not); technical documentation of the third-party integration architecture; interface log analysis showing the nature and volume of transactions triggered by third-party systems; and, where DAAP applies, document count data from SAP's own DAAP reporting mechanism.

A significant number of indirect access ELP claims include document counts that encompass cancelled, test, or duplicate documents that should not contribute to the document-based licence metric. Always request the raw document count data from SAP's auditors and validate it against your own system data before accepting any indirect access claim.

Challenging Engine Metric Calculations

For engine metric challenges — HANA sizing, BW volumes, package metrics — the evidence required is: your own independently measured metric figures using SAP's standard measurement transactions; documentation of the measurement methodology applied (with reference to your contract's metric definition); and, where relevant, evidence of metric fluctuation over time demonstrating that SAP's measurement date captured an unrepresentative peak.

Do Not Concede Without Evidence

One of the most damaging mistakes buyers make is conceding elements of SAP's ELP challenge informally — agreeing in conversation that "that user count looks about right" or "we accept the HANA sizing" — without formal written documentation of exactly what is being agreed and on what basis. Every concession becomes a data point SAP will reference in later discussions. Make no verbal concessions. Every agreement must be in writing, precisely stated.

Structuring the Formal Challenge Letter

The formal challenge letter is the centrepiece of your ELP dispute process. It should be a professionally formatted document — not an email — that follows a consistent structure. Recommended sections:

  1. Reference and reservation of rights. Date, SAP audit reference number, and reservation-of-rights language.
  2. Overview of challenge. A two-paragraph executive summary stating the total compliance gap claimed, your counter-position, and the nature of the challenges raised.
  3. Contracted position challenges. Line-by-line table comparing SAP's contracted position column against your analysis, with contract clause references for each discrepancy.
  4. Measured position challenges. For each challenged measurement line: SAP's figure; your counter-figure; basis for the challenge; and evidence references.
  5. Compliance gap financial analysis. SAP's financial claim; your counter-claim; and the specific financial methodology challenges (price list, maintenance period) as described in our compliance gap calculation guide.
  6. Surplus credits and offsets. Any categories where you carry surplus entitlement that should offset gap claims.
  7. Next steps. A clear request for SAP's formal written response within a specified timeframe (typically 15 business days).
  8. Appendices. All evidence exhibits, numbered and referenced in the body of the letter.

The Professional Tone Advantage

A formal challenge letter that is well-structured, professionally toned, and comprehensively evidenced sends a powerful signal before any meeting takes place. It demonstrates that you are a sophisticated counter-party who has invested in understanding the process in detail. SAP audit teams deal daily with buyers who challenge reactively and emotionally — a calm, methodical, evidence-led challenge document stands out and gets taken seriously at a senior level faster.

When and How to Escalate

If SAP's response to your formal challenge is inadequate — rejecting challenges without substantive explanation, or simply restating their original position without engaging with your evidence — you have several escalation options. These are not threats; they are legitimate contractual and business processes.

First, request a meeting at management level within SAP's LAC organisation, explicitly stating that the technical track has been exhausted without satisfactory resolution. Second, engage your SAP account management team in a formal account review meeting — audit disputes that have commercial implications are account-level issues, not just compliance team issues. Third, if the dispute involves material sums and SAP remains unresponsive to evidence-based challenges, consult legal counsel on the options available under your specific contract's dispute resolution clause.

For independent support across the full challenge process — from initial ELP review to formal challenge letter preparation to settlement negotiation — our SAP audit defence team provides buyer-side expertise with no SAP affiliation and no conflict of interest. We have challenged hundreds of SAP ELP documents and achieved an average compliance gap reduction of over 50% from SAP's initial position.

Our Services

ELP Challenge Support

We prepare your formal ELP challenge document, assemble the evidence package, and represent your position through the full dispute process.

Explore Audit Defence → Free Guide

SAP Audit Defence Playbook

Our comprehensive guide covering the complete SAP audit defence process — from notification to settlement.

Download Free Guide →