Digital Access turned indirect use into a per document charge. The bill follows the document count, and the document count is defensible. This is the buyer side response that holds it down.
SAP Digital Access charges for indirect use by counting documents created in SAP by other systems. The bill tracks the document count, and the document count is defensible. A buyer side estimation note, built before SAP fixes the number, is the difference between an opening demand and a defended figure.
Digital Access is not arbitrary. The charge follows a countable, evidenced quantity. That is exactly why a buyer side estimate, built from the integration architecture, can hold the number down.
Read this alongside the SAP Digital Access complete guide, the SAP audit trends for 2026, the SAP knowledge hub, and the Vendor Shield subscription.
SAP Digital Access is the per document model for indirect use, introduced through the SAP Digital Access announcement in 2018. It charges when non SAP systems create documents in SAP.
Indirect use touches almost every integrated estate. Because Digital Access converts that use into a countable charge, it has become the largest single exposure in most SAP audits we defend.
The old view licensed indirect access by named user, which was ambiguous and disputed. The SAP software use rights now frame it as a per document charge across nine document types, which is more countable but also easier for SAP to assert at scale.
SAP counts the initial creation of a document in SAP that originates outside SAP. The weighting differs by document type.
Digital Access document types, weight, and where exposure hides
| Document type | Relative weight | Share of typical exposure | Where exposure hides |
|---|---|---|---|
| Sales document | Full | High | Order confirmations created twice |
| Service document | Full | High | Field tickets from external apps |
| Invoice document | Full | Medium | Billing runs counted per line |
| Material document | Lower | Medium | Inventory feeds from logistics |
| Financial document | Lower | Low | Cross system postings |
| Manufacturing document | Lower | Low | Production confirmations |
Yes. Only the initial creation is chargeable. Reads, updates, and documents derived downstream from an initial document are not separately charged. That single rule is the basis of most of the defense.
Respond with your own estimate before SAP fixes the count. The RISE with SAP estimate is an opening position.
The SAP Digital Access Adoption Program offers a discounted entry to the per document model. It can be attractive, but the discount frames against an estimate. Defend the estimate before you accept the discount.
Exposure falls when the document count falls. Three levers reduce the count with evidence.
The common advice is to run the SAP Digital Access estimation tool, accept the figure it returns, and take the Adoption Program discount to settle the indirect access question. We disagree. In the engagements we have run, the tool counts gross document creation and ignores duplicate paths, downstream documents, and integration artifacts, so the figure overstates the real chargeable volume by a wide margin. Accepting it locks a discount against an inflated base. The buyer side move is to build an independent estimate from the integration architecture, defend it, and only then weigh the Adoption Program against a number you trust.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Digital Access follows a countable quantity, and a countable quantity is defensible. The first SAP estimate is the opening bid, not the bill.
The estimation note is the artifact that holds the defense together. It documents the count and the reasoning behind every reduction.
SAP Digital Access is the licensing model that charges for indirect use of SAP based on documents created by non SAP systems. It replaced the older per user view of indirect access with a per document charge across nine document types, introduced in 2018.
SAP counts the initial creation of documents in the SAP system that originate from third party or non SAP applications. Only the first creation of a document is chargeable. Reads, updates, and downstream documents derived from an initial document are not separately charged.
Sales and service documents carry the full weight in the Digital Access model. Material, financial, time, manufacturing, quality, and other document types carry a lower weight. Sales and service volume usually drives the largest part of an exposure estimate.
Respond by running your own document estimation before SAP fixes the count. Reconcile the count against the integration map, remove duplicate creation paths, and submit a defended figure. The initial SAP estimate is an opening position, not a settled bill.
The Digital Access Adoption Program is the SAP transition path that offers a discounted entry from a per user indirect position to the per document model. It can be attractive, but the discount frames against an estimate, so the estimate has to be defended first.
Yes. Exposure falls when duplicate document creation paths are removed, when integrations are consolidated, and when documents are created in batch rather than per transaction. Each reduction has to be evidenced against the integration architecture.
No. Digital Access applies inside RISE as well. A RISE conversion often uses the Digital Access estimate as part of the credit math, so the estimate still has to be defended before the conversion is priced.
Redress runs Digital Access defense inside Vendor Shield, the Renewal Program, and the Software Spend Assessment. We build the estimation note, map integrations, remove duplicate paths, and defend the count against the audit. Always buyer side, never SAP paid.
SAP RISE pricing benchmarks, the CVR framework, indirect access 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.
