SAP Digital Access Licensing Model Explained (2026)

SAP's Digital Access model replaced indirect access claims for document-based scenarios in 2018. Eight years on, it remains widely misunderstood — and widely over-negotiated in SAP's favour. This guide explains how Digital Access works, what the nine document types mean for your organisation, and how to control your costs.

Background: From Indirect Access to Digital Access

For much of the 2010s, SAP's indirect access licensing policy was one of the most feared commercial mechanisms in enterprise software. The rule was simple in principle but devastating in practice: any third-party system that accessed SAP data — or triggered a process in SAP — required every user of that third-party system to be licensed with an appropriate SAP named user licence.

The consequences were severe. A customer portal with 50,000 end customers accessing an order status page could, under SAP's interpretation, require 50,000 SAP licences. The landmark Diageo case — which resulted in a £71M settlement — made the risk concrete and brought indirect access to the boardroom agenda of virtually every SAP customer.

In 2018, SAP announced Digital Access as a structural replacement for indirect access in document-based scenarios. Rather than counting every user of every connected system, Digital Access measures the number of specific SAP documents created via digital channels. The nine initial document types provided a more predictable, quantifiable commercial framework — though as we will discuss, 'more predictable' does not mean 'cheap'.

"Digital Access solved the scale problem of indirect access — but it created a new cost challenge. Enterprises with high transaction volumes can face Digital Access bills that rival their core SAP licence costs."

The Nine Digital Access Document Types

SAP's Digital Access model is built around nine core document types. Each represents a category of business transaction that SAP deems to require a licence when created via digital interfaces rather than direct user interaction. Understanding which document types are relevant to your system landscape is the foundation of any Digital Access commercial analysis.

Document Type SAP Transaction Code Common Trigger Scenario Risk Level
Sales Order VA01 / VBAK E-commerce platform or EDI creating orders in SAP without user login High
Delivery VL01N / LIKP WMS or logistics system triggering deliveries in SAP High
Billing Document VF01 / VBRK Automated billing runs triggered by external systems Medium
Financial Accounting Document FB01 / BKPF Bank integration, treasury system, or AP automation creating FI postings High
Goods Movement MIGO / MSEG Warehouse systems, IoT sensors, or RFID creating goods receipts/issues Very High
Scheduling Agreement ME31L / EKKO EDI or supplier portal creating/updating scheduling agreement lines Medium
Service Entry Sheet ML81N / ESSR Contractor portals or procurement systems creating service confirmations Medium
Purchase Order ME21N / EKKO Automated purchasing, procurement platforms, or MRP creating POs High
Production Order CO01 / AUFK MES or planning systems creating production orders in SAP PP Medium

Important: SAP has added document types beyond the original nine in subsequent releases and negotiations. Always verify the complete list in your current SAP contract and in SAP's latest Digital Access pricing supplement.

What Counts as a "Digital Document"?

SAP defines a Digital Access document as one created via a non-SAP interface — meaning any system, application, or process that creates the SAP document without a licensed user directly operating the SAP UI. This includes EDI integrations, API calls from custom applications, machine-to-machine interfaces, IoT platform integrations, and automated batch processes running under a technical user.

Crucially, SAP's position is that documents created by a technical user (a service account or batch user rather than a named human user) constitute Digital Access usage — even if a licensed user indirectly triggered the process. This is one of the most common disputed areas in Digital Access audits.

Digital Access Pricing Benchmarks

SAP's Digital Access pricing is published as a per-document list price that varies by document type. In practice, the list prices are aggressive — particularly for high-volume document types like Goods Movements and Sales Orders in manufacturing and retail environments. Enterprises that do not negotiate explicit Digital Access packages can face unexpected costs equivalent to 20–40% of their core SAP licence spend.

Document Type SAP List Price (approx. per doc) Negotiated Rate (enterprise) Annual Volume Threshold
Sales Order$0.40–$0.60$0.08–$0.22500K–5M+
Financial Accounting Document$0.25–$0.40$0.06–$0.181M–20M+
Goods Movement$0.18–$0.30$0.04–$0.125M–100M+
Purchase Order$0.40–$0.60$0.10–$0.25200K–2M+
Billing Document$0.30–$0.50$0.08–$0.20500K–5M+
Production Order$0.30–$0.45$0.08–$0.18200K–2M+

Benchmarks reflect enterprise negotiated outcomes from The Negotiation Experts engagements 2023–2026. Volume discounts and package deals significantly affect per-document pricing.

"A global manufacturer with 50 million goods movements per year at SAP's list price would face a Digital Access bill of $9–15M annually — on top of their core SAP licence. With proper negotiation, we reduced this to under $2M for one client."

When Indirect Access Still Applies

Digital Access does not eliminate indirect access exposure — it replaces it for specific document-based scenarios. Indirect access still applies in two primary situations that organisations frequently overlook.

Non-Document Indirect Access

Any scenario involving a third-party application accessing SAP data or triggering SAP processes in a way that does not result in the creation of one of the nine Digital Access document types remains subject to the traditional indirect access licensing rules. Examples include: reporting tools that read SAP data via RFC without creating documents; BI platforms that extract data from SAP via direct database connections; and custom portals that read-only query SAP master data to display product or customer information.

Contractual Hybrid Situations

Some older SAP contracts — particularly those signed before 2018 — may have specific indirect access provisions that have not been updated to reflect Digital Access. In these situations, organisations may technically have both indirect access exposure and Digital Access obligations simultaneously. Resolving this ambiguity during renewal negotiations is important and frequently overlooked.

Audit Exposure Under Digital Access

SAP's audit methodology for Digital Access has evolved significantly since 2018. SAP's License Audit and Compliance (LAC) team uses a combination of USMM measurement data, custom reports, and direct database queries to count Digital Access documents. The audit process typically follows this sequence:

  1. SAP requests USMM data. The standard SAP licence measurement tool captures some Digital Access document data, though its accuracy for Digital Access purposes is limited.
  2. Custom measurement reports are deployed. SAP's audit team typically runs bespoke reports to count specific document types by creation method — identifying documents created by technical users versus licensed named users.
  3. Technical user analysis. SAP maps service accounts and batch users to the integration scenarios that created documents, building a picture of which systems and interfaces are responsible for document creation.
  4. Commercial claim is presented. Based on document counts and list prices (minus any contracted Digital Access allowances), SAP presents a retroactive commercial claim — often covering 2–3 years of historical usage.

The most effective audit defence is a pre-emptive one. Organisations that understand their Digital Access document volumes before SAP requests an audit are far better positioned to negotiate the scope, methodology, and commercial outcome.

Negotiating Digital Access Terms

Digital Access is fully negotiable — and the gap between SAP's standard commercial position and an optimised contract outcome is very large. The following strategies have consistently delivered the best results in our engagements.

Negotiate a Document Package Upfront

Rather than paying per-document at list price, negotiate a fixed annual Digital Access package that covers your projected document volumes with a buffer. Package deals typically come with 60–80% discounts from per-document list prices when structured as part of a broader SAP commercial negotiation — particularly during renewal or during RISE migration discussions.

Challenge the Document Count Methodology

SAP's initial document counts often include duplicates (reversal documents, partially-processed documents, and test environment transactions) that should not be billable. Our advisers routinely identify 15–30% of SAP's claimed document counts as legitimately excludable through careful review of the measurement methodology.

Conversion Credits from Indirect Access

If your organisation has historical indirect access exposure that has not been formally resolved, SAP will often offer to convert those claims to Digital Access obligations. Ensure that any conversion is treated as a settlement — not an acknowledgement of the original indirect access claim — and secure a written release of all prior indirect access claims as part of the deal.

Price Caps and Renewal Protection

Negotiate contractual caps on per-document price increases at renewal — ideally tied to CPI or capped at 3–5% annually. SAP has increased Digital Access list prices significantly since 2018; without caps, renewal increases of 20–40% are possible.

"The best time to negotiate Digital Access is before SAP raises it as an audit issue. Once SAP's LAC team is involved, the commercial dynamic shifts in SAP's favour."

Digital Access in RISE with SAP

RISE with SAP includes Digital Access as part of its bundled commercial framework — but the inclusions are not unlimited and are not automatically comprehensive. Organisations migrating to RISE should scrutinise the Digital Access terms carefully.

RISE contracts typically include a Digital Access allowance specified in the contract, covering defined document types up to a contracted volume. Usage above that volume is billed at the applicable per-document rate. The allowance is negotiable during RISE commercial discussions — and organisations that do not proactively negotiate higher allowances frequently find themselves paying significant Digital Access overages in their first year of RISE operation.

For organisations considering RISE, we recommend conducting a Digital Access volume analysis before entering RISE negotiations. This allows you to anchor the Digital Access allowance discussion on actual data, rather than accepting SAP's standard inclusion package.

Related Articles

Negotiate Better IT Contracts

Our advisors are former senior executives from Oracle, Microsoft, SAP, AWS, and Google Cloud. We know what vendors negotiate privately — and we bring that intelligence to every engagement. Average client saving: 38%.

We respond within one business day. No spam, ever.