When SAP introduced Digital Access in 2018, it represented a genuine commercial reform — replacing a named user indirect access model that had become commercially unworkable for many organisations with a transaction-based model that is, in principle, more proportionate to actual system usage. In practice, however, Digital Access introduces its own complexity: the definition of what constitutes a "document," the measurement of document consumption, the interaction between Digital Access and legacy indirect access rules, and the commercial negotiation of Digital Access volume packages all require careful independent analysis. This guide provides the framework that enterprise buyers need to navigate Digital Access correctly.
The Five Digital Access Document Types
SAP Digital Access covers five specific transaction types that can be written to SAP through indirect channels. Each document type has a precise technical definition that determines what generates consumption and what does not.
1. Sales Orders
A Sales Order document is generated each time a third-party system — such as a CRM, e-commerce platform, EDI interface, or customer portal — creates a new sales order in SAP. The key definitional question is whether the creation event occurs in SAP (consuming a document) or in the third-party system (not consuming a document). An e-commerce order that is created in the e-commerce platform and then transmitted to SAP via an integration generates a Digital Access Sales Order consumption event when the SAP order is created. The same e-commerce order that is manually re-entered into SAP by an SAP-licensed user does not generate Digital Access consumption — the user's named user licence covers the transaction.
2. Purchase Orders
Purchase Order consumption is generated when a purchase order is written to SAP from an external procurement system, supplier portal, EDI connection, or procure-to-pay platform. Organisations running SAP Ariba, Coupa, Jaggaer, or similar third-party procurement platforms as their primary procurement interface — with SAP as the financial system of record — are typically the highest-volume Digital Access purchase order consumers. EDI-connected supplier relationships, where purchase orders flow from a planning system to SAP automatically, also generate significant Digital Access consumption.
3. Service Orders
Service Order consumption occurs when field service management systems, customer service platforms, or maintenance management tools create service orders in SAP through an integration. Organisations running Salesforce Field Service, ServiceMax, ServiceNow, or similar platforms that integrate with SAP's Plant Maintenance or Customer Service modules will typically generate Service Order digital access consumption.
4. Production Orders
Production Order consumption is generated when manufacturing execution systems (MES), production planning tools, or IoT platforms write production orders or production confirmations to SAP. Organisations with advanced manufacturing operations where shop floor systems interact with SAP PP or PM modules through real-time integrations are the primary consumers of Digital Access Production Order capacity.
5. Materials Management Documents (Goods Movements)
Goods Movement consumption covers materials management transactions — goods receipts, goods issues, stock transfers, and inventory adjustments — written to SAP from external systems such as warehouse management systems, goods receipt portals, or logistics platforms. This is often the highest-volume document type for manufacturing and distribution organisations.
| Document Type | Common Trigger Systems | Typical Volume Range | Price Benchmark (negotiated) |
|---|---|---|---|
| Sales Orders | CRM, e-commerce, EDI, portals | 50K–5M per year | $0.12–$0.22/doc |
| Purchase Orders | Ariba, Coupa, Jaggaer, EDI | 100K–10M per year | $0.10–$0.18/doc |
| Service Orders | Salesforce FS, ServiceMax, ServiceNow | 20K–2M per year | $0.14–$0.25/doc |
| Production Orders | MES, production planning, IoT | 50K–3M per year | $0.12–$0.20/doc |
| Goods Movements | WMS, logistics platforms, portals | 200K–20M per year | $0.08–$0.15/doc |
What Digital Access Does Not Cover
Digital Access is specifically scoped to the five document types above. A significant body of indirect access scenarios fall entirely outside Digital Access coverage and remain subject to the legacy named user framework. The most commercially significant non-covered scenarios are:
- Read-only access: Systems that read SAP data — such as customer portals displaying order status, BI platforms querying SAP tables, or analytical applications extracting transactional data — do not consume Digital Access documents because they do not write documents. However, they may still trigger named user licence obligations under the legacy indirect access rules for the users who access the data through those interfaces.
- Master data management: External MDM platforms that write to SAP master data tables (customer master, material master, vendor master) do not write the five document types and are not covered by Digital Access. Master data write-access from external systems remains a legacy indirect access scenario requiring separate commercial treatment.
- Configuration and administrative access: Third-party tools that access SAP configuration tables, administrative functions, or Basis-level system management interfaces are not covered by Digital Access.
- Analytical and reporting extractions: Direct database queries via JDBC, OData service calls that extract report data, and API-based analytics tool connections that read rather than write SAP data are outside Digital Access scope.
Compliance Gap Warning: Many organisations that have converted to Digital Access believe they have fully resolved their indirect access compliance obligations. In the majority of cases audited by firms including Redress Compliance, organisations that converted to Digital Access have resolved their document-based indirect access exposure but left read-only and non-document write scenarios unaddressed. A comprehensive indirect access compliance framework must address both Digital Access (for the five document types) and legacy named user obligations (for all other indirect access patterns). See our SAP Indirect Access guide for the full framework.
Digital Access Volume Modelling
Accurate Digital Access volume modelling is the single most important commercial lever available to enterprise buyers in Digital Access negotiations. SAP's initial Digital Access proposals are based on conservative volume estimates that are typically 2–4× the actual document consumption of the organisation. Accepting SAP's volume estimate without independent modelling means paying for unused Digital Access capacity on a committed basis — a cost that accrues every year of the contract.
Independent Digital Access volume modelling involves three steps. First, extract actual historical document volumes from the SAP system for each of the five document types, filtered to include only documents created through non-SAP interfaces (excluding documents created by named SAP users, which are already covered by their user licences). This requires careful filtering of the SAP document creation log to exclude named user-generated documents. Second, identify planned integration changes over the contract period — new EDI connections, additional integration scenarios, system migrations — that would increase or decrease future document volumes. Third, apply appropriate seasonal and growth assumptions to produce a five-year volume forecast that is both realistic and independently documented.
The volume modelling exercise consistently produces estimates that are 40–65% lower than SAP's initial proposals. For a large enterprise with an initial SAP proposal of 10 million Digital Access documents at $0.25 per document ($2.5M per year), independent modelling typically produces a defensible actual volume of 4–6 million documents per year at a negotiated rate of $0.14–$0.18 per document — an annual cost of $560K–$1.08M, saving $1.4M–$1.9M per year against SAP's initial proposal.
Negotiating a Digital Access Agreement
Digital Access agreements are negotiated on three commercial dimensions: the volume commitment (number of documents per year per type), the price per document, and the overuse handling mechanism. All three are negotiable and all three significantly affect total contract cost.
Volume Commitment Negotiation
Digital Access volume commitments should be sized at actual forecast volumes plus a modest buffer (typically 10–20%) to accommodate volume variation without triggering overuse charges. SAP's initial proposals include buffers of 50–100% above realistic volumes, padding the committed spend significantly. The independent volume model provides the basis for challenging SAP's proposed volumes and anchoring the negotiation at a defensible level.
Price Per Document Negotiation
Digital Access per-document pricing is directly negotiable. SAP's list rate is approximately $0.35–$0.55 per document, but this rate is never paid by well-advised enterprises. Achievable negotiated rates — based on committed volume, contract duration, existing SAP relationship value, and competitive evaluation — range from $0.08 to $0.22 per document depending on volume tier. Larger committed volumes generate lower per-document rates. Multi-year commitments (three to five years) generate better pricing than annual agreements, but must be balanced against the risk of over-commitment if volumes are uncertain.
Overuse Handling
Standard SAP Digital Access templates specify that document consumption in excess of the committed volume is charged at the contracted per-document rate — meaning any volume above the committed threshold generates additional invoicing. The critical protective clause to negotiate is a capped overuse rate: limiting additional invoicing for volume overages to a specified percentage of the annual committed amount (typically 10–15%) before requiring a formal contract amendment. This provides genuine volume protection without the risk of unlimited additional charges for unexpected volume spikes.
The audit exclusion for historical Digital Access use — covering document consumption before the Digital Access agreement was signed — is equally important and should be explicitly included in the agreement. Without this exclusion, SAP retains the right to pursue indirect access claims for historical document consumption under the legacy named user framework even after a Digital Access agreement is signed.
For the broader context of SAP indirect access, including the legacy framework that Digital Access partially replaces, see our SAP Indirect Access guide. For the complete SAP licensing landscape, see the Complete SAP Licensing Guide. If you are in an active SAP audit where Digital Access is being discussed as part of the resolution, our SAP Audit Defence guide provides the full response framework.