Key Takeaways

  • The gap between your counter-ELP and SAP's measurement is not a problem to solve — it is a negotiating position to defend.
  • SAP's audit process has four escalation levels: licence compliance team, licence compliance management, SAP account executive, and SAP legal. Understanding where you are in this structure informs your strategy.
  • Three-quarters of SAP ELP disputes are resolved before reaching the account executive level when buyers present credible, documented counter-positions.
  • The measurement date is negotiable in more cases than SAP's auditors typically acknowledge — particularly where business events (acquisitions, disposals, restructuring) have materially changed the user population.
  • Walking away from commercial settlement packages tied to cloud commitments is a legitimate option — and SAP's teams know it.

You have built your own SAP Effective Licence Position. You have reviewed SAP's ELP. There is a gap between the two figures — as there almost always is. The question is how to close that gap on terms that protect your business. This guide covers the negotiation strategy, the escalation levers, and the settlement structures that work for enterprise buyers in SAP ELP disputes.

This article is part of our series on the SAP ELP and compliance gap process. For the evidence-based challenge approach to specific ELP line items, see Challenging SAP's ELP: Evidence-Based Approach. For the financial dimensions of the gap calculation, see SAP Compliance Gap: How to Calculate Your Exposure.

Understanding the Nature of the Gap

Before engaging on strategy, it is worth being precise about what the gap between your counter-ELP and SAP's measurement actually represents. It is rarely a simple factual disagreement about system data. It is typically a composite of several types of difference, each requiring a different closing approach.

Type 1

Remediation Differences

Users or configurations you corrected before measurement that SAP's auditors measured in their original, un-remediated state.

Type 2

Methodological Differences

Differences in measurement approach — timing, landscape scope, technical user treatment — that produce different numbers from the same underlying system.

Type 3

Contractual Interpretation

Disagreements about what your contract entitles you to use — product scope, user type definitions, engine metric measurement methodology.

Type 4

Factual Errors

Mistakes in SAP's measurement data — wrong system included, wrong product mapped, incorrect contracted position.

Types 3 and 4 are the strongest challenge basis — they are either wrong or they are interpretive, and interpretation is what lawyers and commercial negotiators engage with. Types 1 and 2 involve more nuance: SAP will argue that your remediation should not reduce the historical measured position; you will argue that it demonstrates the measurement overstated the operational reality.

The Remediation Argument

SAP's standard position is that pre-measurement remediation reduces your forward-going exposure but does not affect the compliance gap for the audit period. This is commercially aggressive but not always contractually supported. The audit clause in most enterprise agreements focuses on the state of the system at the time of measurement — not a historical average. If your contract's audit provisions do not specifically require a historical look-back, the remediated measurement is the measurement.

The SAP ELP Negotiation Structure

Understanding who you are negotiating with — and who they report to — is fundamental to ELP dispute strategy. SAP's audit process involves four distinct organisational levels, each with different authority and different objectives.

Level 1: Licence Compliance Team (LAC)

This is where ELP disputes begin. SAP's Licence and Compliance (LAC) team are measurement specialists — they execute USMM, prepare the ELP, and manage the initial challenge process. LAC teams have limited authority to deviate from SAP's standard methodology, but they do have discretion on factual error corrections. If your challenge is primarily about Type 4 errors (factual mistakes in the ELP data), the LAC team can correct them without escalation.

Level 2: Licence Compliance Management

Methodological and contractual disagreements escalate to LAC management. This level has more authority to accept alternative measurements and agree on contested contractual interpretations. The key is presenting a challenge that is well-documented and clearly framed — this level responds to professional, evidenced argument rather than commercial pressure.

Level 3: SAP Account Executive

When the LAC process stalls, the dispute moves into the commercial domain handled by your SAP Account Executive and their management chain. This is where the gap between measurement and settlement becomes explicitly commercial — and where cloud deal packaging typically enters the conversation. AEs have authority to offer commercial concessions (reduced maintenance look-back, settlement discounts) but will typically seek a forward-looking commercial commitment in return.

Level 4: SAP Legal

Escalation to SAP legal is rare but does occur, typically when the compliance gap claim is very large and the commercial track fails to produce resolution. Legal involvement changes the tone significantly but does not change your fundamental position — and courts have historically been cautious about SAP's more aggressive audit interpretations. Having legal counsel familiar with SAP contract law before this stage is strongly recommended.

Strategies for Closing the Gap

The following strategies, applied in sequence, represent the most effective approach to closing the gap between your counter-ELP and SAP's measurement position.

Strategy 1: Segregate the Gap by Type

Before any negotiation meeting with SAP, prepare a written analysis that categorises every element of the measurement gap (using the four types above). This segregation accomplishes two things: it forces SAP to engage with your analysis on its specific merits rather than treating the whole challenge as a single negotiating move, and it identifies which elements are most defensible. Focus your energy on Type 3 and Type 4 challenges first — the factual and contractual disputes that SAP cannot simply dismiss.

Strategy 2: Anchor on Your Counter-ELP, Not SAP's Figure

The most common mistake buyers make in ELP negotiations is opening with SAP's figure and arguing down from it. This cedes the anchor to SAP. Open with your own counter-ELP figure as your stated position, and require SAP to explain every element of the delta before you will engage on commercial resolution. You are not negotiating a discount from their number — you are presenting an alternative analysis and requiring SAP to demonstrate the error in it.

Strategy 3: Use the Measurement Date as a Lever

The timing of SAP's measurement is not always as fixed as they present it. Where there is evidence that the measurement date was chosen to inflate the user count — measured during an end-of-year surge, or shortly after an acquisition before integration rationalisation — there is a legitimate basis to request a re-measurement at a more representative date. This is particularly effective where your own subsequent measurement at a normalised date produces materially lower counts.

Strategy 4: Invoke Your Price Protection Rights Early

As discussed in our compliance gap calculation guide, invoking Price Protection rights reduces the financial exposure immediately without conceding any unit count position. Do this early in the commercial track — it signals to SAP's team that you understand the contract in detail and are not going to accept the list price calculation as a given.

Strategy 5: Keep Commercial and Technical Tracks Separate

SAP's auditors sometimes blur the boundary between the technical measurement challenge (LAC track) and the commercial resolution discussion (AE track). This can result in buyers making commercial concessions before the technical challenge has been fully resolved — effectively paying for gaps that should have been closed through measurement correction. Keep the two tracks formally separate and insist that the LAC process completes before you engage on commercial terms.

The Cloud Bundle Timing Trap

SAP account teams sometimes propose commercial settlement packages — bundling audit relief with cloud product commitments — at a point when the technical ELP challenge is still unresolved. Accepting a commercial bundle before the technical challenge is complete effectively caps your recovery of measurement errors in exchange for what may be an unattractive forward-looking deal. Always resolve the technical track first, then evaluate commercial packaging independently.

Settlement Structures and What to Accept

When the technical challenge has been exhausted — or where a residual gap after challenge is accepted — settlement structures offer different risk profiles. Understanding what is and is not commercially reasonable helps you evaluate SAP's proposals critically.

Cash Settlement with No Commercial Commitments

The simplest and cleanest settlement: a one-time payment for back-licences and maintenance at an agreed level, with no forward-looking product commitments. This structure is achievable but requires willingness to accept the cash outflow. Its advantage is simplicity and finality — it closes the matter entirely without creating future commercial leverage for SAP.

Licence Purchase with Maintenance Going Forward

SAP may agree to treat the back-licence settlement as a current licence purchase — waiving maintenance backdating in exchange for a full maintenance commitment going forward. This is often commercially attractive: it replaces a multi-year maintenance backdating liability with a forward-going commitment at the same annual rate, while potentially preserving entitlement to future price protection on the newly purchased licences.

Commercial Bundle with Cloud Products

SAP's preferred settlement structure bundles audit relief with a commitment to RISE with SAP, BTP, or other cloud products. The relief element reduces the back-licence cash payment; the cloud commitment creates new multi-year revenue for SAP. These bundles require careful independent analysis because the apparent "saving" on the back-licence side is often offset — or exceeded — by the economic cost of the cloud commitments. Engage independent contract negotiation support before accepting any commercial bundle proposal.

Closing Principle: Time Is Your Ally

SAP's audit teams operate under revenue targets and quarterly close pressures. The longer a dispute remains unresolved, the more pressure builds on SAP's commercial team to find a resolution — and the more latitude opens up on commercial terms. Taking the time you need to properly validate the ELP and prepare a robust challenge is not just legally sound; it is commercially strategic. Patience, backed by preparation, consistently produces better outcomes than urgency.

Post-Settlement Positioning

Settlement is not the end of the matter — it is the foundation for the next cycle. Every SAP audit settlement contains provisions that affect your future position: updated contracted entitlements, maintenance terms, Price Protection periods, and often commercial commitments with future compliance implications.

Before signing any settlement agreement, have it reviewed by an independent SAP licensing expert to ensure: the contracted position accurately reflects all entitlements agreed; no provisions create inadvertent future compliance traps; Price Protection and maintenance terms are clearly defined; and any forward-looking commercial commitments are unambiguous in scope and duration.

The settlement agreement you sign today becomes the contracted position you will defend in your next audit. Draft it with that in mind. Our SAP audit defence team reviews settlement agreements as a standard part of every engagement — and has identified provisions in SAP-drafted agreements that would have created substantial new compliance exposures within two years of signing.