SAP raised a large indirect access claim against a UK engineering firm. A document driven defense and an accurate measurement of real digital use brought the final settlement 81 percent below the opening demand.
SAP raised a large indirect access claim against a UK engineering firm over third party systems touching SAP data. A document driven defense and an accurate use measurement settled the claim 81 percent below the opening demand.
This is an anonymised account of a real SAP audit defense. Figures are presented as ranges to protect the client. The mechanics are exactly as they unfolded.
SAP indirect access, now framed as digital access, is the charge for non SAP systems that read or write SAP data. SAP set out the license use rights that govern it. The claim turned on how use was measured.
SAP raised a large claim over third party systems integrating with the SAP core. The firm ran several integrations that moved data in and out of SAP without named user licences for the connected systems.
The claim covered a logistics system, an engineering application, and an e commerce front end, all touching SAP data. SAP described the digital access model as the basis for the charge.
The opening demand was large enough to threaten the year budget. It was built on theoretical access across every connected system, not on measured document creation.
The defense did not argue that no exposure existed. It argued about measurement, scope, and the right licensing model. Each was evidenced with documents.
The team measured actual digital documents created through each integration. The SAP digital access guide ties the charge to documents, and the measured count came in far below the claim.
Contractual history showed some integrations were covered by existing named user and engine licences. That history removed a block of the claim before pricing began.
Opening claim versus settlement (indexed, claim = 100)
| Line | Opening claim | Settlement | Lever |
|---|---|---|---|
| Logistics integration | 40 | 8 | Measured documents |
| Engineering app | 35 | 6 | Prior use rights |
| E commerce front end | 25 | 5 | Digital access document pricing |
| Total | 100 | 19 | Roughly 81 percent reduction |
The common advice is to remediate indirect access by buying named user licences for everyone touched by an integration. We disagree. In roughly four out of five engagements, the digital access document model priced machine driven integrations far below named user remediation, and the measured document count came in well under the claim. The buyer side move is to measure real document creation, establish prior use rights, and only then choose the licensing model that fits. Buying named users to settle a machine integration claim usually overpays for access no human ever uses, and the SAP account team rarely volunteers the cheaper document based path.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
SAP can license a document that was created. It cannot license a connection that might be used. The defense lives in that distinction.
Four levers carried the defense. None denied exposure. Each replaced an assertion with a measured fact.
Measuring real digital documents created per integration replaced SAP theoretical access with an evidenced count. This was the largest single lever.
Digital access document pricing fit machine integrations better than named user remediation. Choosing the model deliberately, not by default, cut the unit cost sharply.
The settlement came in roughly 81 percent below the opening demand and converted an audit threat into a planned digital access purchase.
A digital access document package sized to measured use, prior rights honored, and a clean baseline for future integrations, consistent with SAP guidance on its corporate news channel. The firm also documented its measurement method for the next review.
The firm cut the SAP indirect access claim by 81 percent by measuring real digital document creation rather than theoretical access, establishing prior use rights, and choosing digital access document pricing over named user remediation. The measured count came in far below the claim.
SAP indirect access, now framed as digital access, is the licensing charge for non SAP systems that read or write SAP data, such as logistics, engineering, or e commerce integrations. The charge applies even when no human user logs in to SAP directly.
Digital access document pricing is usually cheaper than named user remediation for machine driven integrations, because it prices the documents created rather than buying named users for access no person uses. In our engagements it beat named user pricing in roughly four out of five cases.
An SAP digital access claim should be measured by the count of digital documents created through each integration, not by the number of systems that can reach SAP. SAP can license documents that were created, so the defensible number is the measured document volume.
Yes. Prior contracts and existing named user or engine licences often cover part of an integration, which narrows the claim before pricing begins. Contractual history reduced scope in roughly four out of five of the engagements we ran.
No. Opening SAP indirect access claims overstated real document creation by 50 to 80 percent in our engagements. The opening figure is built on theoretical access, so it should be tested against a measured document count before any settlement discussion.
An 81 percent reduction is not guaranteed and is specific to this engagement. The result depended on the gap between theoretical access and measured documents, the strength of prior use rights, and the fit of digital access pricing to the integrations involved.
Respond to an SAP audit notice by inventorying every system that touches SAP data, measuring real document creation, and establishing prior use rights before discussing money. Engaging independent advisory early keeps the response evidence driven rather than reactive.
SAP RISE pricing benchmarks, the indirect access framework, document license posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
