SAP Indirect vs Digital Access: How to Choose the Right Licensing Model

The Origins of SAP's Access Licensing Problem

For most of its history, SAP licensed its software on a named-user basis. Every person who logged into an SAP system — whether directly or via a third-party application — needed a corresponding licence. As enterprise architectures became more interconnected, with e-commerce platforms, CRM systems, IoT devices, and robotic process automation tools all generating transactions inside SAP, the traditional user-count model became increasingly contested.

SAP's position was straightforward: any value derived from SAP data or processing, regardless of the access route, required a licence. Customers pushed back. The result was years of costly audit disputes, landmark legal battles (most notably the Diageo and Anheuser-Busch InBev cases in the United Kingdom), and eventually a new licensing framework introduced in 2018: Digital Access.

Understanding the distinction between the legacy Indirect Access model and the current Digital Access framework is essential for any organisation managing an SAP estate — especially those in the midst of, or approaching, an S/4HANA migration, where the licence baseline resets and SAP uses the transition as an opportunity to enforce updated compliance terms.

What Is SAP Indirect Access?

Indirect Access refers to scenarios where data is sent to or retrieved from SAP through a non-SAP application, without an SAP user interface being directly involved. A typical example: a customer places an order through your e-commerce website, which in turn creates a Sales Order in SAP automatically. The customer never touches SAP — but SAP's position under the legacy model is that the processing of that transaction requires an SAP licence.

The traditional Indirect Access model is measured on a user basis. SAP would argue that named users of the third-party system — the people initiating or receiving the transactions — require SAP licences. In complex scenarios involving thousands of e-commerce customers, automated RPA bots, or IoT sensors, this could generate enormous theoretical licence claims. Organisations caught in Indirect Access audits have faced demands running to tens of millions of dollars based on this logic.

The key metric in Indirect Access disputes is DDLC — Document Driven Licence Consumption. While DDLC is more formally associated with the Digital Access model, SAP's audit teams apply a document-count lens even when assessing traditional Indirect Access claims. The auditors examine which business documents were created in SAP as a result of external system interaction and build their financial claim from that volume. Understanding DDLC is therefore critical regardless of which access model nominally applies to your contract.

What Is SAP Digital Access?

Digital Access is SAP's document-based licensing model, formally introduced in 2018. Rather than counting the users of third-party systems, Digital Access counts the documents created in SAP as a result of external access. The unit of measure is the SAP document, not the person.

This is the DDLC metric in its formal home. Under Digital Access, customers purchase licences for a defined number of documents per year, drawn from a specific set of nine SAP document types. When an external system — whether an e-commerce platform, a logistics partner portal, an RPA tool, or an API integration — triggers the creation of one of those document types in SAP, a licence unit is consumed.

The Nine SAP Digital Access Document Types

SAP has defined nine document categories that are subject to Digital Access licensing. Each has specific counting rules that determine how many licence units are consumed per document created:

• Sales Documents — created when external systems generate sales orders, quotations, or returns. Counts as 1.0 unit per document.
• Purchase Documents — purchase orders, scheduling agreements, or purchase requisitions created externally. Counts as 1.0 unit.
• Invoice Documents — customer invoices and supplier invoices generated through integration. Counts as 1.0 unit.
• Manufacturing Documents — production orders, process orders, or planned orders created by external MES or scheduling systems. Counts as 1.0 unit.
• Quality Management Documents — inspection lots or quality notifications created from external quality systems. Counts as 1.0 unit.
• Service and Maintenance Documents — service orders or maintenance notifications generated by external field service platforms. Counts as 1.0 unit.
• Time Management Documents — time confirmations or attendance records submitted through third-party HR or workforce management systems. Counts as 1.0 unit.
• Financial Documents — accounting entries or journal postings created by external financial systems. Counts as 0.2 units per document.
• Material Documents — goods receipts, goods issues, or stock transfers triggered by external logistics or WMS platforms. Counts as 0.2 units per document.

The reduced weighting for Financial and Material Documents (0.2 units) reflects their typically high volume. A single warehouse operation may generate hundreds of material movements daily, and pricing them at full rate would make Digital Access economically unworkable for many industries.

What Does Not Trigger Digital Access?

Pure read-only queries do not trigger Digital Access obligations. If an external system queries SAP data — running reports, pulling inventory levels, checking order status — without creating a new document, no licence is consumed. This is a critical distinction when assessing your integration landscape. Many organisations have overstated their exposure by treating all API calls as billable, when only document-creating transactions actually count.

Indirect Access vs Digital Access: The Core Differences

The two models differ across several dimensions that matter practically when preparing for or defending against an SAP audit:

Metric: Users vs Documents

Indirect Access is user-based. Digital Access is document-based. This has significant financial implications. Under the user model, SAP can claim that every distinct external user of a connected third-party system requires a full SAP named-user licence — potentially a far larger number than the actual volume of documents created. Under the document model, the claim is constrained by the volume of actual transactions flowing into SAP.

For organisations with high user counts but relatively modest transaction volumes, Digital Access will almost always be cheaper. For organisations with high-volume, highly automated transaction flows — large retailers, manufacturers, logistics companies — the calculation is more complex.

Measurability

Digital Access is objectively measurable. SAP provides tooling (a measurement note for ECC systems, and a native report in S/4HANA) that counts documents by type, giving both parties a common data source. The nine document categories are defined, the counting rules are published, and the output is reproducible.

Indirect Access under the legacy model was often contested precisely because there was no agreed measurement methodology. SAP and customers routinely disagreed on which users, which systems, and which transactions were in scope. This ambiguity was one of the main reasons SAP introduced Digital Access — it gave SAP a more defensible audit basis and gave customers a more predictable cost model.

S/4HANA Migration Impact

This is a point that many organisations underestimate until it is too late. When you migrate to S/4HANA, your existing licence baseline does not automatically carry over without modification. SAP treats an S/4HANA migration as a contract renegotiation event, and the Digital Access framework will apply to your new landscape from day one. Existing Indirect Access clauses in older ECC-era contracts may not survive the migration agreement intact.

Before you sign any S/4HANA or RISE with SAP contract, you must understand what integration volumes you are committing to, what document types are in scope, and what the per-document pricing will be over the full contract term. SAP's sales teams are not incentivised to surface this complexity for you.

The Digital Access Adoption Program (DAAP)

SAP created the Digital Access Adoption Program to help customers transition from the legacy Indirect Access model to the document-based framework. DAAP offers up to 90% discounts on initial Digital Access document licence purchases, and allows customers to trade in existing named-user licences for credit against new Digital Access entitlements.

DAAP remains available as of 2026, but SAP reserves the right to sunset it at any time and has done so with similar transitional programmes in the past. The window to benefit from maximum DAAP discounts is finite. Organisations still operating under legacy Indirect Access terms who have not engaged with DAAP are carrying unnecessary risk — they are contractually exposed to the older, more expensive user-based model if SAP initiates an audit before a DAAP conversion is completed.

What DAAP Does Not Solve

DAAP addresses the pricing transition. It does not address the underlying obligation to measure and license all document-creating integrations. Organisations that convert to Digital Access via DAAP but fail to accurately count their document volumes will simply replace one compliance risk with another. The DAAP discount reduces your initial investment; it does not validate your licence position.

Choosing the Right Model: A Framework

Whether Digital Access or the legacy Indirect Access model is better for your organisation depends on the specific characteristics of your integration landscape. A structured assessment should cover the following questions:

• How many distinct third-party systems create documents in your SAP environment?
• What is the annual volume of documents created by type — Sales, Purchase, Manufacturing, Financial, Material, and the others?
• What is the current user count exposed under your legacy Indirect Access terms?
• What is SAP's current per-document pricing in your geography and industry sector?
• Are you within 18 months of an S/4HANA migration or RISE with SAP contract signature?

In the vast majority of enterprise scenarios we have analysed at Redress Compliance, Digital Access produces a lower total licence cost than the legacy user-based model — but only if the document volumes are properly measured and the initial DAAP discount is secured before the programme window closes.

Common Mistakes Organisations Make

Having advised on more than 80 Indirect Access disputes, we have observed a consistent set of errors that inflate organisations' exposure or weaken their negotiating position:

• Treating all API calls as chargeable — read-only queries do not trigger Digital Access. Over-counting your exposure leads to unnecessary spend.
• Failing to run SAP's measurement tools before the audit — if SAP runs the measurement first, they control the framing. Run your own measurement and have it ready.
• Assuming legacy Indirect Access terms survive S/4HANA migration — they often do not. The migration contract is where SAP resets the rules.
• Delaying DAAP engagement — SAP can and does close programme windows. Waiting until an audit letter arrives is the most expensive time to discover you needed DAAP three years ago.
• Accepting SAP's document count without challenge — SAP's measurement tools have known limitations and can double-count in certain architectural configurations. Always validate independently.

How Redress Compliance Supports SAP Indirect and Digital Access Engagements

Redress Compliance operates exclusively on the buyer side — we have no commercial relationship with SAP and do not receive referral fees or commissions. Our SAP licensing team has defended more than 80 Indirect Access and Digital Access disputes across industries ranging from manufacturing and retail to financial services and utilities.

Our engagement model for Indirect and Digital Access includes an independent measurement of your document volumes using SAP's native tooling, a gap analysis between your current entitlements and your actual consumption, a benchmarking of SAP's proposed per-document pricing against comparable transactions in our dataset, and active negotiation support to secure DAAP pricing or to challenge inflated audit claims.

If you are approaching an S/4HANA migration, we recommend engaging at least 12 months before the planned contract signature date. The leverage available to you in pre-migration negotiations is substantially greater than the leverage you have after you have signed a RISE with SAP agreement and are operationally dependent on SAP's cloud infrastructure.

Key Takeaways

SAP Indirect Access and Digital Access are not interchangeable terms — they represent fundamentally different licensing frameworks with different metrics, different measurement tools, and different financial implications. The DDLC metric underpins both, and understanding how it is applied is the foundation of any effective compliance or negotiation strategy. The nine document types, their counting rules, and their interaction with your specific integration architecture determine your actual exposure far more accurately than any theoretical user-count argument.

Digital Access, implemented properly via DAAP, generally produces a more predictable and often lower licence cost than the legacy model — but only if you measure accurately, engage before an audit rather than after, and treat the S/4HANA migration moment as the critical licence reset event that SAP intends it to be.

For independent advice on your SAP Indirect or Digital Access position, contact Redress Compliance. We work exclusively for buyers.