SAP Digital Access and Indirect Access: Terms and History Explained
Anyone working through SAP licensing questions today will encounter two terms that are frequently used interchangeably in practice: Indirect Access and Digital Access. That creates confusion, especially when you need to assess your own contract status or make informed DAAP decisions.
Both terms describe the same underlying issue, but from different eras of SAP licensing policy. Understanding the distinction means understanding not just the history, but also why many existing customers still have open questions in their contracts in 2026.
Indirect Access: The Historical Term (Before 2018)
Until 2018, Indirect Access was the SAP licensing world's catch-all term for any access to SAP data or SAP functions that did not occur through a direct SAP logon session by a licensed user. The underlying idea was logical: if a third-party system uses SAP data, a license should apply.
The problem was the absence of precision. Neither SAP nor its customers had a consistent answer to the question of exactly when a third-party system became subject to licensing. Every integration was potentially exposed. Every new system connection could be classified retroactively as indirect access, without any way for the customer to have recognized that in advance.
This ambiguity was not a theoretical problem. It led to publicly documented legal disputes between SAP and large customers, including Diageo and AB InBev (source: Gartner Research). Those cases made clear that the Indirect Access model, in its undefined form, was not a workable foundation for either side. SAP was forced to develop a clearer model.
In practice, Indirect Access meant years of uncertainty for many organizations: Was the CRM integration licensed? Was the WMS connection a problem? Did RPA usage comply with the contract terms? These questions often went unresolved until an Enhanced Audit put them on the table.
Digital Access: The Successor Model (Since 2018/2019)
SAP responded in 2018 with a structurally different approach. Instead of targeting the access itself, the licensing obligation now attaches to the result of that access. The new model is called Digital Access and has been the standard framework in new SAP contracts and renewals since 2019.
The core logic: it is no longer the fact that a third-party system communicates with SAP that triggers a licensing obligation. What matters is whether that third-party system creates one of the nine defined document types in SAP. The licensing obligation is tied to a clearly measurable quantity: document volume.
This shift has significant practical consequences. First, the gray zone of mere access disappears. A third-party system that only reads SAP data without writing anything back does not trigger a licensing obligation (Static Read). Second, there is a definitive list of relevant document types. Anything not on that list is not subject to licensing, regardless of the nature or volume of the integration. Third, the metric is clear: document items rather than vaguely defined access events.
The nine document types that trigger a Digital Access obligation are: Sales Order Items, Purchase Order Items, Service Order Items, Manufacturing Order Items, Invoice Items (Billing/AR), Payment Items (Incoming Payments), Goods Movement Items, Journal Entries, and Inbound Delivery Items. A detailed description of each type and its trigger logic is covered in the companion article on the nine document types.
What Changed in Practice
The shift from Indirect Access to Digital Access improved the situation for customers, but did not resolve every question.
Named User licensing for third-party access remains available. You can still license users of a third-party system as SAP Named Users. For scenarios with a small number of identifiable individuals, that is often the simpler path. Document-Based Licensing, meaning Digital Access, is the new path for high-volume, automated, or anonymous access.
The choice between Named User and Digital Access is not a one-time decision. It requires an integration inventory and an assessment of each individual scenario. For which integrations does Named User make economic sense? Where is Document-Based Licensing the better option? That question is a recurring governance moment, not a one-time project.
What did not get resolved automatically by the transition to Digital Access: the historical contract status of many existing customers. Organizations with on-premise contracts predating 2019 were not automatically migrated to Digital Access. The DAAP program is the formal path for that migration, and it is voluntary.
The Digital Access Adoption Program (DAAP)
The DAAP is the contractual bridge between the old Indirect Access logic and the new document-based model. SAP has offered it since 2018. It is not a mandatory program, but for many existing customers it is the only reliable path to closing historical compliance gaps.
What the DAAP Program Delivers
At its core, the DAAP enables two things. First: a formal transition to Document-Based Licensing, including the definition of document quotas, overage terms, and measurement standards. The outcome is a DAAP Amendment to the existing SAP contract, typically accompanied by a Digital Access Supplement.
Second: a retrospective settlement. The DAAP program provides an option to settle any historical underlicensing in a single step, without the customer having to make full retroactive purchases. SAP offers an amnesty option for customers who transition to Document-Based Licensing. For customers with long-standing integrations and historical gray areas, this is a significant advantage.
How the Program Works in Practice
The DAAP process follows a structured sequence. First, an SAP Measurement Tool captures current document volume over a representative measurement period. On that basis, a document quota is negotiated that reflects the projected demand for the contract term. The result is a formal amendment with quotas, an overage rate, and a price per document item. Specific pricing is agreed contractually and is not publicly listed.
What to Review Before Entering the DAAP
Entering the DAAP without a complete picture of your integration landscape puts you at risk of a poor negotiation outcome. A quota set too low creates near-term overage. A quota set too high ties up budget that could be deployed more precisely.
The sensible approach before entering the DAAP is therefore: a complete inventory of all integrations with SAP interfaces, broken down by document type and volume. Add a historical measurement period of at least twelve months to capture seasonal fluctuations. And a comparative calculation between Named User and Document-Based Licensing for each integration group.
When DAAP Is Not the Right Choice
The DAAP is not the right fit for every scenario. For integrations with a small number of predictable external users and limited transaction volume, Named User can be the more cost-effective path. The decision logic depends on the ratio between the number of identifiable individuals and document volume. The more external, anonymous users or automated processes are involved, the more the economics favor Digital Access.
Why This Is Still an Open Question in 2026
The transition to Digital Access was completed on paper in 2018/2019. In practice, many customers have not yet fully made that shift.
First: existing customers with pre-2019 contracts may never have completed the DAAP. RISE migrations set new priorities in many cases without systematically resolving digital access status. The result is a contract position that neither cleanly fulfills the old Indirect Access logic nor formally reflects the new Digital Access model.
Second: integration landscapes grow faster than the governance structures designed to manage them. CRM systems, RPA bots, e-commerce platforms, WMS solutions, all of these are potential Digital Access triggers. Many of those integrations were built without a formal license review beforehand.
Third: PCE Metering and SAP's automated cloud monitoring are raising the depth of scrutiny. SAP has the technical infrastructure to reconstruct integration topologies, even when customer-side documentation has gaps. Transaction logs contain sufficient information.
For customers with complex SAP portfolios, the question of Digital Access status across their integrations is not a theoretical compliance topic. It is a concrete governance moment: who manages SAP contracts after signature? For Digital Access, that means tracking document volumes, systematically documenting license status, and making DAAP decisions with full information before an Enhanced Audit sets the agenda.
Frequently Asked Questions
What is the difference between Indirect Access and Digital Access in SAP?
Indirect Access was the historical term for all access to SAP via third-party systems, without a clear definition of when a licensing obligation arose. Digital Access is the successor model in effect since 2018. It replaces the vague access logic with a document-based model: a licensing obligation arises from the creation of one of the nine defined document types in SAP, not from access itself.
What is the DAAP and why does it matter for existing customers?
The Digital Access Adoption Program is a voluntary SAP program that enables a formal transition from historical Indirect Access obligations to Document-Based Licensing. It attaches to the existing contract as a DAAP Amendment and Digital Access Supplement and enables a retrospective settlement of historical compliance gaps. Existing customers whose contracts predate 2019 may not yet have completed the program.
Are existing customers required to complete the DAAP?
The program is voluntary. It does, however, provide planning certainty and audit protection for the covered document types. Existing customers without a DAAP Supplement are operating under the historical Indirect Access gray zone, which can lead to retroactive demands in an Enhanced Audit. Whether the DAAP makes economic sense depends on your integration inventory and the ratio between your user base and document volume.
Can Named User Licensing still be used after Digital Access was introduced?
Yes. Named User remains a fully valid licensing path for third-party access. For scenarios with a small number of identifiable users, it is often the simpler option. Document-Based Licensing is economically stronger for anonymous users, high transaction volumes, or fully automated processes.
Next Steps
The first step toward clarifying your Digital Access status is a complete inventory of your integration landscape. Which systems have an interface to SAP? Which document types do they generate? What licensing basis is in place?
The FinOptory Contract Review addresses these questions systematically in four weeks: integration inventory, Digital Access status, and action items as the starting point for your next renewal negotiation. Fixed price, 7,900 EUR.
For an initial assessment without uploading documents, the FinOptory AI Chat is available.
Further reading: The Nine Document Types and the Mechanics of Digital Access Licensing explains which integrations concretely create a license trigger and how document volume functions as a governance moment and control metric.
Next Steps
If you would like your current contract reviewed for risks and available commercial levers: the FinOptory Contract Check is a fixed-price engagement that delivers a structured basis within four weeks.
This article is part of our topic hub on digital access and indirect access in SAP. To have one specific contract assessed, the FinOptory Contract Check delivers a structured basis within four weeks.
Last updated: July 2026