The Digital Access model charges SAP customers per document, at defined tier prices, for documents created by non-SAP applications that flow into SAP. The model is simpler in principle than the indirect-use clause it replaced, but the practice of counting documents accurately is where most settlements are won or lost. SAP’s opening count, when an audit lands, is almost always higher than the defensible count. The gap is the work of measurement, classification, and contractual reading. This article walks through how to do that work on the buyer side.
The nine document types
The Digital Access model defines nine document types: Sales Document, Purchase Document, Invoice Document, Manufacturing Document, Material Document, Quality Management Document, Time Management Document, Service & Maintenance Document, and Financial Document. Each type has a defined trigger event in SAP — usually a header-level posting in a specific module — and each is charged at a tier price defined in the order form.
The classification is consequential. A document that posts into the Material Document type is priced differently from one that posts into the Manufacturing Document type, and the integration pattern often allows a degree of legitimate choice about which posting path is used. The classification work is the first step in any Digital Access counting exercise.
What counts as a document
SAP’s reading is that a document is created at the moment of the header-level posting in the relevant transaction. A sales order is one Sales Document, regardless of the number of line items. A purchase requisition that becomes a purchase order is one Purchase Document. A goods receipt is one Material Document, even if it covers multiple line items.
The buyer-side reading aligns broadly but requires care on three patterns. Reversals and cancellations — a posted document that is reversed and re-posted is typically counted once for licensing purposes, not three times. Internal-to-internal flows — documents that originate inside SAP, move through a middleware layer, and post back to SAP are not net new documents and should not be double-counted. And inter-company postings — documents that exist in two SAP company codes within the same instance are usually counted once.
The static-data exemption
The Digital Access model carries a static-data exemption: replication of master data that does not change the operational state of SAP is not a document for licensing purposes. The exemption is sometimes contested at the margin — particularly for high-frequency master-data syncs — and the buyer-side position should be written down and held consistently across the audit response. The contractual basis is in the Digital Access order form and is discussed in our Digital Access topic page.
How to measure document volume
Document volumes are measurable in SAP, but not through any single tool. The measurement requires four data sources. The transaction-history tables for the relevant document types (VBAK for sales, EKKO for purchasing, MKPF for material, etc.). The change-document logs (CDHDR/CDPOS) for the postings. The interface logs from the middleware layer that originated the document. And the user table to identify the originating system of each posting.
The measurement should be conducted on a rolling twelve-month window, with the originating-system attribution applied to each document. A posting that originated from a named SAP user is not chargeable under Digital Access; a posting that originated from a non-SAP application is. The attribution is the work that converts a raw document count into a chargeable count.
The originating-system attribution
Most over-counted Digital Access positions come from missing or mis-applied originating-system attribution. SAP’s opening claim, if it lacks the attribution, typically counts every document of the chargeable type as chargeable. The buyer-side measurement separates the documents that originated from named SAP users (not chargeable) from those that originated from non-SAP applications (chargeable). The split, across the estates we have measured, is typically thirty to sixty per cent of the total document volume.
The attribution work uses the technical user ID associated with the integration, the source-system field where populated, and the integration log from the middleware layer. The attribution is rarely complete on the first pass, and a residual unattributed bucket is normal. The unattributed bucket should be addressed as an aggregated allowance in the settlement, not priced at full tier.
The tier structure
Digital Access tier pricing is volume-banded: the per-document price decreases as the contracted volume increases. The bands are defined in the order form and typically include break-points at increments such as one million, ten million, and fifty million documents per year. The negotiation on tier placement is consequential. An estate with three million documents per year priced at the one-million tier pays a significantly higher per-document rate than the same estate priced at the ten-million tier.
The tier should be negotiated at a level that includes a defined headroom above the current measured volume, with a re-measurement protection that fixes the per-tier price for the contract term. The economics are detailed in the Digital Access Pricing Decoded white paper.
The conversion from indirect use
For estates with substantial pre-2018 indirect-use exposure, the conversion to Digital Access is usually the favourable settlement structure. The conversion exchanges the open-ended indirect-use claim for a measured document-count entitlement. The conversion negotiation should include three protections. A document-count baseline that reflects the buyer-side measurement, not SAP’s opening count. A re-measurement protection that fixes the per-tier price. And an exemption schedule for the document types the buyer does not generate.
The conversion is one tool among several. The middleware risk explainer covers the patterns that drive the underlying exposure, and the Digital Access negotiation service page describes how we run the engagement.
What an audit looks like with the counting done
An audit conducted against a current, validated, well-documented buyer-side document count follows a different trajectory from the typical pattern. The opening claim, when it lands, is read against the count, the attribution gaps are identified inside ten business days, the position paper goes back to SAP inside six weeks rather than ten, and the settlement closes at a fraction of the opening claim. Across our engagements where the buyer-side count existed before the notification, the average reduction is higher than the headline sixty-eight per cent. The counting does not change SAP’s opening position. It changes the speed of the buyer’s response.
The global-retailer conversion case file documents one such settlement in full, including the document-count rebuild and the conversion economics. The license compliance pillar covers the broader programme.
Digital Access counting is straightforward in principle and exacting in practice. The gap between SAP’s opening count and the defensible count is, across our engagements, the largest single component of every conversion settlement.
Where to start
If the document count does not exist today, the most useful single project of the next quarter is to build it. The work is structured, finite, and lasts. The methodology is in our Digital Access negotiation service page and in the audit defence pillar. The first conversation is at no cost and under privilege.
The exemption schedule
Every Digital Access order form should carry an exemption schedule that identifies the document types the buyer does not generate and confirms they are out of scope of the agreement. The schedule is not a contractual right under the standard Digital Access terms; it is negotiated in. Without the schedule, a future SAP team can read the order form as covering all nine document types at the contracted tier, and any future generation of a previously-unused document type is treated as a chargeable event. The schedule closes that exposure.
The schedule discipline is to map the nine document types against the actual integration topology, identify the types that are generated and the types that are not, and write the unused types into the exemption. The work takes one to two weeks of buyer-side analyst time per renewal cycle. The value is contractual certainty across the term.
The per-document price benchmarks
Across the Digital Access conversions we have negotiated, the per-document price at the ten-million-document tier ranges from approximately twelve dollars to thirty-six dollars depending on the buyer’s broader portfolio commitments, the contract vintage, and the conversion structure. The variance is wide because the pricing is volume-banded and bundled with broader commercial elements. The negotiation should be benchmarked against the buyer’s own prior pricing and against the contractual pricing in the master agreement, not against a notional market rate that does not reflect the bundled structure.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.