When SAP presents a back-licence claim, the initial figure is almost always dramatically higher than what any reasonable negotiation would settle at. Understanding the SAP back-licence claim anatomy — how each component of a large demand is constructed, where SAP's methodology overstates exposure, and what specific evidence dismantles each element — is the foundation of effective claim defence.
This article provides a forensic walkthrough of a representative $10M SAP back-licence demand, breaking down every line item, identifying the inflators built into each component, and showing what a well-prepared response achieves in practice. The pattern described here is drawn from extensive real-world audit defence experience, not theoretical analysis.
Key Takeaways
- A $10M SAP back-licence demand typically contains 60–80% inflation relative to defensible exposure.
- SAP uses list prices, maximum user counts, maximum back periods, and maximum maintenance rates — every component is calibrated to maximise the opening figure.
- The three highest-impact challenge areas: user count accuracy, back period length, and price basis (list vs contract rates).
- Indirect access components are frequently the most contestable — often resolving through DAAP at a fraction of the claimed amount.
- An independently prepared counter-analysis submitted early anchors the negotiation at a realistic number.
- Most $10M demands settle in the $1.5M–$3M range after thorough independent challenge.
The Case: A Global Retailer with 3,500 SAP Users
Our hypothetical — constructed to reflect the most common pattern we encounter — involves a global retail enterprise with approximately 3,500 named SAP users across ECC 6.0 and SAP Analytics Cloud, operating under an Enterprise Licence Agreement signed in 2019 with a major scheduled renewal in 2026. SAP's GLAC team initiates an audit in Q3 2025, requesting USMM data and a full system measurement submission.
The company runs USMM under SAP's supervision and provides the output. Four weeks later, SAP presents the following opening claim. This represents a typical example of SAP back-licence claim anatomy at the large end of the market.
SAP Opening Back-Licence Claim — Global Retail Enterprise
Back-licence shortfall — user reclassification (550 users, 4-year back period @ list price): $4.84M
Annual maintenance arrears — 22% pa on back-licence value, compounded 4 years: $3.44M
Indirect access — 3 third-party integrations, document-based pricing 4 years: $1.62M
SAP Analytics Cloud — unlicensed additional users, 2-year back period: $340K
Total Opening Claim: $10.24M
"The first time a procurement director sees a $10M audit demand, the instinct is to panic and settle quickly. That instinct is exactly what SAP's opening claims are designed to produce. Every component of that number is calibrated to be as large as defensible — not to reflect what a reasonable calculation would produce."
— SAP Audit Defence Lead, SAP Licensing ExpertsDissecting Component 1: User Reclassification ($4.84M)
The largest single element of most back-licence claims is user reclassification — SAP's assertion that users currently classified at a lower-cost licence tier should have been higher-tier users throughout the back period. In our example, SAP claims 550 users should have been Professional rather than Limited Professional or Employee, over a 4-year period at list prices.
Where SAP's Figure Is Inflated
- User count (550 stated): USMM captures everyone with active accounts, including users who have not logged in for 12+ months, IT system accounts, interface users, and HR records that haven't been deprovisioned. Independent log analysis typically reduces the "reclassification-eligible" user count by 25–40%.
- Back period (4 years stated): SAP claims the full 4 years since the last ELA signing. But system logs typically show that Professional-level transactions only became prevalent 18–24 months ago, when a new module was deployed. The defensible back period is 18–24 months, not 48.
- Price basis (list price): The ELA was signed with a 62% volume discount on Professional users. SAP's calculation uses list prices. Applying the contract discount reduces this component's value by 62%.
Challenge Result for Component 1
- Revised user count after log analysis: 340 (vs 550 claimed) — a 38% reduction
- Revised back period: 20 months (vs 48 months claimed) — a 58% reduction in time factor
- Contract rate applied (62% discount): 38% of list price
- Combined effect: $4.84M × 0.62 × 0.42 × 0.38 = $479K defensible exposure
Dissecting Component 2: Maintenance Arrears ($3.44M)
Maintenance arrears are calculated as 22% per annum of the back-licence value — compounded over 4 years. Since SAP's back-licence figure was itself inflated, the maintenance arrears compound that inflation. At 22% annually for 4 years, the maintenance component represents 105% of the back-licence value — making it roughly equal in size to the licence fees themselves.
Challenge Points for Maintenance
- Maintenance is typically calculated on the corrected back-licence value, not SAP's inflated figure
- Maintenance accrues from the date the shortfall actually existed — in our example, the 20-month actual back period, not 48 months
- SAP frequently agrees to waive maintenance arrears entirely in exchange for a multi-year going-forward maintenance commitment — this is a standard negotiation lever
- Pro-rata calculation applies for partial years — SAP's compound methodology overstates arrears on shorter back periods
Challenge Result for Component 2
After correcting the back-licence value to $479K and reducing the back period to 20 months: maintenance arrears = $479K × 22% × 1.67 years = $176K defensible, before exploring the maintenance waiver option (which, in practice, typically results in full waiver in exchange for a 3-year going-forward commitment at market rates).
Dissecting Component 3: Indirect Access ($1.62M)
SAP's indirect access claim covers three third-party systems that interact with SAP data via APIs and RFCs. SAP has applied document-based pricing — the number of SAP documents created or modified by these systems over 4 years — which produces a substantial number at list-price rates per document.
Challenge Points for Indirect Access
- The technical architecture of two of the three integrations qualifies for the Digital Access Adoption Programme (DAAP), which provides a fixed annual fee structure significantly below document-based pricing
- One integration creates SAP documents but reads from a dedicated data replication layer, not from direct SAP access — this may not constitute indirect access at all under a forensic reading of the licence agreement
- SAP's document count methodology counts every API call, including test calls, error retries, and system-generated entries — actual business document volumes are typically 30–50% lower
Challenge Result for Component 3
DAAP resolution for two systems: approximately $180K annual going-forward cost (no back-licence component under DAAP retroactive enrolment). Third integration: technical architecture challenge eliminates the claim. Total indirect access exposure: $180K going-forward, $0 back-licence.
Dissecting Component 4: SAP Analytics Cloud ($340K)
The SAP Analytics Cloud component alleges that additional users accessed SAC functionality beyond the contracted named-user count over a 2-year period. This is typically the most straightforward component to challenge because SAC maintains detailed user activity logs.
Challenge Result for Component 4
SAC log analysis confirms that peak concurrent users never exceeded the contracted entitlement. The additional "users" identified by SAP's measurement include the same individuals under multiple email aliases following an internal IT consolidation project. After reconciliation: $0 exposure.
The Counter-Analysis: From $10.24M to $655K
Independent Counter-Analysis — Defensible Exposure
User reclassification (340 users, 20-month back period, contract rates): $479K
Maintenance arrears (on corrected base, 20 months): $176K
Indirect access — DAAP going-forward only (back-licence waived): $0 back
SAP Analytics Cloud — no shortfall confirmed: $0
Total Defensible Exposure: $655K
In practice, a well-executed negotiation using this counter-analysis as the starting position — combined with a credible going-forward commitment (new ELA or RISE transition) — typically achieves a final settlement in the $400K–$700K range, with maintenance arrears waived and DAAP formalised going forward. That represents a 93–96% reduction from SAP's opening claim of $10.24M.
The Negotiation Timeline
| Phase | Timing | Key Actions | Outcome |
|---|---|---|---|
| Audit notification | Week 1 | Acknowledge receipt, request extension, engage independent advisors | 30-day extension obtained; no data submitted yet |
| Independent analysis | Weeks 2–5 | System log review, user classification analysis, indirect access mapping | Counter-analysis complete: $655K defensible exposure |
| Counter-claim submission | Week 6 | Formal written counter-analysis submitted to SAP audit team | SAP's team acknowledges; escalates internally |
| SAP revised claim | Weeks 8–10 | SAP revises claim to $4.2M (still inflated, but 59% reduction) | Confirms our analysis has leverage |
| Escalation & commercial linkage | Weeks 11–14 | Connect audit resolution to new ELA negotiation; escalate to SAP senior commercial | SAP commercial team engaged; DAAP enrolment agreed |
| Settlement | Week 16 | Final settlement: $580K back-licence, maintenance waived, DAAP formalised | 94% reduction from $10.24M opening claim |
Key Lessons from Back-Licence Claim Anatomy
Every large SAP back-licence claim follows a predictable architecture: inflated user counts, maximum back periods, list prices instead of contract rates, and compound maintenance. Understanding this architecture means you can predict where the challenge opportunities are before you even start the negotiation.
The most important lesson from this anatomy analysis: the opening claim is designed to create fear, not to represent SAP's expectation of what they will recover. SAP knows the opening figure will be challenged — the audit team builds in inflation specifically to create negotiating room while still achieving a commercial outcome. Your job is to take that room systematically and with evidence.
For the complete framework for handling back-licence claims from notification to settlement, see our SAP back-licence claims complete enterprise guide. For the technical detail on how SAP calculates each component, see our analysis of how SAP calculates back-licence fees. For strategies to reduce claims by 60–80%, see our back-licence reduction guide.
Independent SAP Back-Licence Defence
Forensic analysis and negotiation of SAP back-licence claims — buyer-side only, no SAP affiliation.
Explore Audit Defence → Case StudiesReal Back-Licence Settlement Results
See how we've reduced SAP back-licence demands by 60–95% for enterprise buyers across industries.
Read Case Studies →Free Consultation
Get Independent SAP Back-Licence Claim Analysis
Send us your claim figure and we'll give you an initial view of the defensible exposure — no commitment, no SAP affiliation.
Book a Free Consultation →