When SAP presents a back-licence claim, one of the most consequential strategic decisions you face is whether to fight the historical exposure directly or pivot to a going-forward commercial negotiation that resolves the audit as part of a broader deal. The SAP back-licence strategy decision is not simply about which path costs less — it is about which approach best serves your commercial interests over the next 3–7 years of your SAP relationship.
Both strategies have legitimate use cases. Both can produce excellent outcomes — and both can produce poor outcomes if pursued without a clear framework. This article provides the decision framework you need to choose the right approach for your specific situation, and to execute whichever path you choose with maximum effectiveness.
Key Takeaways
- The choice between fighting back-licence claims and pivoting to going-forward commercial resolution is the single most important strategic decision in an SAP audit.
- A going-forward strategy works best when you have genuine future SAP spend to commit, and when the back-licence claim is the primary blocker to a deal you would make anyway.
- A fight strategy works best when the claim is clearly inflated, you have strong evidence, and you are not under time pressure to close a commercial deal with SAP.
- The most effective approach combines both: challenge the claim to establish credible evidence, then use the going-forward commitment as the lever to achieve a waiver.
- Going-forward deals must be carefully structured — a poorly negotiated ELA can create the next back-licence claim.
- SAP's account team has strong incentives to close new bookings; this incentive structure is your most powerful lever in any going-forward negotiation.
Understanding the Two Strategic Paths
⚔ Fight the Back-Licence Claim
- Independent counter-analysis challenging measurement data and calculation methodology
- Formal dispute mechanism invocation
- Legal challenge options (arbitration, litigation)
- Negotiated settlement at evidence-based exposure level
- No new commercial commitments to SAP required
📈 Going-Forward Commercial Resolution
- New ELA or expanded licence agreement that resolves compliance shortfall going forward
- Back-licence claim waived or substantially reduced as part of new deal
- Multi-year volume commitment in exchange for commercial concessions
- Clean slate on compliance, new audit clock starts from zero
- Potential for better pricing and terms than standalone purchase
When to Fight: The Fight Strategy Decision Criteria
A pure fight strategy — challenging the back-licence claim through independent analysis and formal dispute, without making a significant new commercial commitment to SAP — is appropriate when specific conditions are met.
Strong Evidence Base
If your independent analysis reveals that SAP's claimed shortfall is clearly overstated — that the actual measurement data, correctly interpreted, shows a fraction of the alleged exposure — then you have the foundation for a credible fight. Evidence-based challenges consistently achieve 60–80% reductions even without a going-forward deal on the table.
No Near-Term Going-Forward Spend
If you are not planning significant new SAP investment in the next 2–3 years — no cloud migration, no new modules, no significant user expansion — then you have nothing to offer SAP in a going-forward negotiation. In this situation, the fight strategy is your only real option.
SAP Relationship Is Already Adversarial
If the audit has already damaged the commercial relationship to the point where a constructive going-forward conversation is unrealistic, a clean legal challenge and settlement may be preferable to a commercial deal made under duress. Deals made under audit pressure often contain hidden traps — volume commitments, maintenance terms, or audit rights provisions — that create new exposure.
Small Claim Relative to Advisory Costs
For back-licence claims under $500K, a going-forward commercial resolution is often not worth pursuing because the deal structure required to achieve a waiver would commit you to more SAP spend than the claim itself. A straightforward evidence-based settlement at evidence-based exposure levels is typically the right outcome.
When to Go Commercial: The Going-Forward Decision Criteria
A going-forward commercial strategy — pivoting the audit resolution into a broader licence negotiation — delivers the best outcomes when specific commercial conditions are in place.
You Have Genuine Future SAP Spend
The going-forward strategy only works if you have real future SAP spend to commit — a RISE with SAP transition, a significant module expansion, a multi-year ELA renewal, or a substantial user growth trajectory. SAP will not waive a back-licence claim in exchange for a commitment you would not have made anyway. If you have to manufacture spend to make the deal work, you are creating future cost exposure to solve a present problem.
"The most powerful negotiating position in an SAP audit is: 'We have done our analysis, we believe the defensible back-licence exposure is $X, and we are prepared to commit to a new 3-year ELA worth $Y. We want to close both discussions in the same room, in the same week.' That combination routinely produces outcomes that neither approach achieves alone."
— SAP Commercial Negotiation Advisor, SAP Licensing ExpertsThe Back-Licence Claim Is the Primary Blocker
If the back-licence claim is the primary reason a going-forward deal is not getting done — if both sides want to transact but the audit is creating a commercial stalemate — then linking resolution to a new commitment is the natural path. SAP's account team wants new bookings; your team wants the audit closed. The going-forward deal serves both interests.
You Are Under Time Pressure
A major system migration, a regulatory deadline, an internal digital transformation programme — these time-bound events create leverage for SAP (who knows you need to close the deal) but also create an opportunity to link audit resolution to a commitment you were going to make regardless. Use the time pressure deliberately rather than letting SAP use it against you.
The Combined Strategy: How to Do Both
The most effective approach in most medium-to-large back-licence disputes combines elements of both strategies, executed in sequence. This is the framework that consistently produces the best commercial outcomes.
- Complete the evidence-based challenge first. Before engaging commercially, prepare your counter-analysis and establish a credible defensible exposure figure. This is not optional — without it, you have no commercial leverage. SAP will not waive a $10M claim in exchange for a going-forward deal unless you can credibly demonstrate that the $10M is not recoverable anyway.
- Formally invoke the dispute mechanism. Send formal written notice disputing the claim and invoking the contractual dispute process. This creates a structured timeline and forces SAP to engage at a senior level.
- Signal going-forward interest in parallel. Through your account team (not the audit team), signal that you have genuine future SAP spend but that you cannot commit while the audit is unresolved. This activates SAP's commercial interest in closing the audit.
- Connect the deals explicitly. When SAP's commercial and audit teams are both engaged, make the explicit link: you will commit to the going-forward deal, and you want the back-licence claim resolved as part of that conversation. This is not a concession — it is the structure that allows SAP to achieve its commercial goal (new bookings) while you achieve yours (audit closure).
- Negotiate the going-forward terms rigorously. The back-licence waiver should not come at the expense of poor going-forward terms. Negotiate the ELA or cloud commitment as if it were a standalone deal, with full market benchmarking and independent analysis of the pricing.
The Going-Forward Deal Traps to Avoid
A poorly structured going-forward deal can be worse than paying the back-licence claim. The following traps are common and must be specifically avoided when negotiating a commercial resolution of an SAP audit.
Trap 1: Volume Commitments You Cannot Use
SAP frequently offers to waive back-licence claims in exchange for ELA commitments that include volume far in excess of your realistic consumption. If you commit to licences or cloud units you will never use, the "waiver" is illusory — you are just paying the back-licence in a different form. Ensure going-forward commitments are sized to your realistic usage trajectory.
Trap 2: Sweeping Audit Waiver Language
Some SAP agreements include language that waives the current audit findings but preserves SAP's right to audit the same period again under a different pretext. Ensure any settlement agreement explicitly releases all back-licence claims for the specified period, including indirect access claims, and that SAP's future audit rights for historical periods are extinguished.
Trap 3: Undiscounted Going-Forward Pricing
SAP account teams sometimes frame going-forward deals as "already discounted because of the back-licence waiver." This is a negotiating tactic — not a genuine market reality. Going-forward pricing should be benchmarked independently against comparable deals, with the back-licence waiver treated as a separate commercial matter, not as a substitute for proper price negotiation.
Trap 4: Loose Licence Metric Definitions
If the back-licence claim arose from ambiguous licence metric definitions, a going-forward deal that perpetuates the same ambiguity will create the next audit. Ensure the new agreement includes clear, documented definitions of the licence metrics relevant to your actual usage — particularly user classifications and indirect access rules.
Comparing Total Cost: Fight vs Going-Forward
| Scenario | Example Claim ($10M) | Strategy | Typical Total Cost |
|---|---|---|---|
| Accept claim at face value | $10M | No defence | $10M + going-forward at list |
| Fight only (evidence-based) | $10M | Challenge + settle | $800K–$1.5M settlement + advisory fees |
| Going-forward only (no fight) | $10M | New ELA at list, waiver implied | Expensive ELA + hidden back-licence value baked in |
| Combined strategy (optimal) | $10M | Challenge + link to going-forward deal | $0 back-licence + market-rate ELA on your terms |
The combined strategy — challenge first, then link to going-forward — consistently produces the best total commercial outcome. The back-licence waiver is genuine (not offset by inflated going-forward pricing), and the new ELA is negotiated on your terms, not SAP's.
For the detailed technical challenge methodology, see our article on how SAP calculates back-licence fees. For the legal options when going-forward negotiation fails, see disputing SAP back-licence claims through legal channels. For the complete back-licence defence framework, see our SAP back-licence claims complete guide.
SAP Back-Licence Strategy Advisory
Independent strategic advisory on fight vs going-forward approach — tailored to your specific commercial situation.
Explore Audit Defence → Contract NegotiationSAP Going-Forward ELA Negotiation
Independent negotiation of SAP ELA and cloud commitments — ensuring going-forward terms are commercial, not audit-driven.
Explore Contract Services →Free Consultation
Get Strategic Advice on Your SAP Back-Licence Situation
We'll help you choose the right strategy — fight, going-forward, or both — based on your specific commercial situation. No SAP affiliation.
Book a Free Consultation →