SAP Digital Access Licensing: The Complete Guide to Document-Based Charges

SAP Digital Access is how SAP charges for third-party systems that create documents inside SAP. Not for named users sitting at SAP screens — those are governed by traditional user licences. Digital Access applies when an e-commerce platform, a warehouse management system, an IoT device, or a CRM submits a transaction to SAP that generates a specific document type. Each document carries a per-unit licence fee. At scale, these fees can dwarf an enterprise's entire named user licence spend.

SAP introduced the Digital Access model in 2018 as a replacement for its older, more aggressive "indirect access" model. The shift was partly a response to the high-profile Oracle vs Rimini Street legal battles and SAP's own confrontational audit behaviour — most notably the £54.4M damages claim against Diageo in 2017. Digital Access was presented as a simpler, more transparent alternative. It is more transparent. But it is not more favourable to customers.

This guide covers everything you need to know about SAP indirect access and Digital Access advisory: the document types, the measurement process, where overcounting occurs, and how to push back on inflated claims.

What Is SAP Digital Access and Why Did It Replace Indirect Access?

The original "indirect access" doctrine held that any user who indirectly accessed SAP functionality through a third-party system — even without touching the SAP UI — required an SAP named user licence. This interpretation allowed SAP to argue, in principle, that every employee using a connected system like Salesforce, ServiceNow, or a bespoke warehouse application owed SAP a licence fee. The commercial claim was theoretically limitless.

Digital Access replaced this user-count model with a document-count model. Instead of asking "how many people indirectly touched SAP?", the question became "how many documents were created in SAP by non-SAP systems?" The four qualifying document types are: Sales Orders, Purchase Orders, Service Entries, and Goods Receipt/Invoice Receipts.

The document model is intellectually cleaner. It is also potentially more expensive for high-volume transactional environments. A retail enterprise processing one million customer orders per year through an e-commerce platform that writes to SAP directly faces a Digital Access liability measured in millions of documents annually, not hundreds of named users.

The Four Document Types and What They Cost

SAP's Digital Access licence covers exactly four document types. Each has a distinct commercial rate, which is always negotiated (SAP does not publish a fixed list price). The rates below reflect the mid-range of what we see in enterprise deals of 100,000–500,000 annual documents per type.

The pricing rates above are not fixed. SAP's starting position in negotiations is typically 3–5x higher than what a well-prepared enterprise can achieve. The key levers are volume commitment (agreeing to a minimum annual document count in exchange for a lower per-unit rate), multi-year commitment, and cross-portfolio deal bundling. For industries with extremely high document volumes — retail, manufacturing, logistics — negotiating a blended all-in rate across all four document types is often more advantageous than negotiating each type separately.

How SAP Measures Digital Access: SLAW and the Measurement Process

SAP measures Digital Access usage through SLAW — the SAP Licence Audit Workbench. This tool, executed within Solution Manager or directly on the SAP landscape, generates a count of qualifying documents created by non-SAP user sessions during a defined measurement period. The output feeds directly into SAP's compliance gap calculation.

The critical concept here is "non-SAP user session". SAP's measurement methodology attempts to identify documents that were not created by a named licensed user working through SAP's standard UI. Interface transactions, RFC connections, BAPI calls, and OData API invocations from third-party systems are the primary sources of Digital Access document generation.

SAP typically requests system measurement data as part of an enhanced audit. Before any measurement is run, enterprises should understand exactly which RFC connections, API integrations, and interface programmes exist in their landscape and which SAP document types they create. This landscape map should be prepared independently before SAP's measurement team arrives — it forms the basis of any challenge to the measurement output. Our SAP audit guide covers how to prepare for this process in detail.

Common Overcounting Scenarios and How to Identify Them

SAP's SLAW measurement has well-documented limitations that systematically inflate document counts above actual billable usage. Understanding these overcounting patterns is fundamental to challenging a Digital Access assessment.

1. Duplicate Document Creation

Many integration architectures create a document, encounter an error, roll back the transaction, and then re-create the document after the error is resolved. SLAW counts each creation attempt, including the failed attempts. The document that ultimately persists in SAP is one; the SLAW count may record two, three, or more. For high-volume EDI environments with non-trivial error rates, this overcount can represent 15–30% of the reported total.

2. System-to-System Documents

Documents created by SAP background jobs, SAP workflow processes, or SAP Solution Manager itself are not subject to Digital Access charges — only documents created by non-SAP systems are in scope. However, SLAW does not always correctly attribute the creating session. Automated SAP processes that use technical user IDs (BASIS users, batch job users) are sometimes mis-attributed as non-SAP interface calls, inflating the Digital Access count.

3. Test and Development Documents

Documents created in SAP development, quality assurance, or sandbox systems are explicitly excluded from Digital Access measurement. However, many enterprises share logical SAP clients between production and non-production activity, or fail to clearly tag non-production RFC connections. SLAW measurements that capture QA or integration testing traffic against production documents inflate the count materially.

4. Migration and Conversion Documents

Historical data migration activities — particularly during S/4HANA transitions — create very large volumes of SAP documents in a short window. These migration loads should be explicitly excluded from Digital Access measurement scope under most enterprise licence agreements. If your RISE or S/4HANA contract does not explicitly carve out migration activity, negotiate this exclusion before your first LMDB measurement.

High-Risk Integration Scenarios by Industry

Digital Access exposure is not evenly distributed. Certain architectural patterns and industries carry substantially higher risk than others. The following represent the highest-exposure scenarios we encounter in enterprise engagements.

How to Challenge a Digital Access Claim

When SAP presents a Digital Access compliance gap, the initial claim is almost always challengeable. Our experience across hundreds of digital access assessments is that the first number SAP presents is reduced by 30–60% through systematic challenge — before any commercial negotiation begins.

The challenge process works in three stages. The first is technical validation: independently re-running the SLAW measurement with your BASIS team and comparing results to SAP's count. Discrepancies above 5% require SAP to provide query-level evidence of their measurement methodology. Most SAP account teams cannot readily produce this level of detail, which immediately weakens their negotiating position.

The second stage is exclusion analysis: categorising every document in the SAP count and applying the exclusion criteria defined in your contract. Test system documents, migration documents, SAP-to-SAP documents, and background job documents are the primary exclusion categories. Each must be substantiated with evidence, but a competent BASIS team with good system documentation can typically exclude 20–35% of the initial count on technical grounds alone.

The third stage is contractual challenge: examining whether your existing licence agreement already covers some or all of the Digital Access use cases. Many older enterprise agreements contain "connector" licences, engine licences, or interface user provisions that provide some coverage for system-to-system document creation. These provisions are frequently overlooked by both customers and SAP's measurement teams.

Contractual Protections to Negotiate Before You Have a Problem

The best time to address Digital Access risk is during contract negotiation — not after SAP has delivered a compliance gap letter. Several contractual provisions materially reduce your Digital Access exposure at zero additional licence cost if negotiated before signing.

The most important is a defined measurement protocol. Your contract should specify: the measurement tool (SLAW version and configuration), the measurement period (typically 12 months, not a single-day snapshot), the exclusion categories that apply, and the notice period before any unilateral measurement is triggered. Without these provisions, SAP can time measurements to capture atypical volume periods — pre-Christmas retail spikes, year-end financial close, post-go-live stabilisation periods — and hold you to those counts.

Second, negotiate volume caps or annual document allowances. Rather than paying per-document rates with no ceiling, many enterprise agreements can be structured with an included annual allowance of documents across all four types, with overage pricing only applying above that threshold. This converts an open-ended consumption risk into a manageable, predictable cost.

Third, carve out specific integration patterns that are genuinely low-risk. SAP-to-SAP document creation (for example, within a group SAP landscape or between an acquired company's SAP system and the parent SAP system) should be explicitly excluded. Documents created by SAP-delivered integration content (SAP Integration Suite flows that SAP themselves sold you) are a grey area that should be clarified in writing before deployment.

For more background on how SAP audits relate to Digital Access measurement, see our complete guide to SAP Indirect Access and our SAP audit defence playbook.