The nine SAP Digital Access document types

SAP’s 2018 introduction of the Digital Access model collapsed the indirect-access conversation into a single mechanic: pay per countable document created by external systems. The mechanic is operationally simpler than the named-user model that preceded it, but it shifts the measurement burden onto a definition exercise. Every Digital Access measurement starts with a count of documents by type, and the type definition determines whether a given system event is in scope at all. SAP’s audit team and the buyer’s SAM lead frequently disagree on classifications. The disagreements are worth multiples of millions on a midsize estate, and the buyer position that holds up at audit walks through each of the nine document types and applies the counting rule that the contract actually grants.

The nine document types

SAP’s Digital Access pricing model counts nine document types, defined in the SAP Digital Access price list and elaborated in supplementary product notes. The list has remained stable since 2018, though the counting rules behind each type have evolved through 2026. The types are sales documents, invoice documents, purchase documents, service and maintenance documents, manufacturing documents, material documents, quality management documents, time management documents, and financial documents.

Each type has a unit price, a counting rule, and a set of exemptions. The unit prices are roughly equivalent across types after volume tiers are applied, but the counting rules vary widely. Sales documents count per order line, invoice documents count per invoice header, purchase documents count per order line, and so on. The variance in counting rules is the principal source of measurement disputes.

Type one: sales documents

Sales documents include sales orders, returns, contracts, scheduling agreements, and quotations created by external systems. The counting rule is per line item in the sales document, not per document header. The distinction matters: a single order with twenty line items counts as twenty sales documents, not one. The exemption list includes intra-company transfers, free-of-charge transactions, and adjustments to existing orders that do not create new line items.

The most common measurement error in sales documents is double-counting orders that pass through a CPQ tool and create a draft sales order before the final order is created. SAP’s audit team will count both events if the audit log shows two distinct creates. The buyer position is that draft orders that are subsequently superseded by the final order are not separately countable. The position holds up at audit if the configuration logs are produced as evidence. The document counting article sets out the discipline in detail.

Type two: invoice documents

Invoice documents include outbound customer invoices, credit memos, and debit memos created by external systems. The counting rule is per invoice header, not per line item. The exemption list includes pro-forma invoices, internal billing adjustments, and recurring billing patterns that derive from a single contract event.

The most common error is counting invoices that are subsequently cancelled and re-issued. SAP’s audit team will count both events unless the cancellation document is mapped to the original. The buyer position is that a cancellation-and-reissue sequence is a single billing event for Digital Access purposes. The mapping discipline is straightforward but requires the configuration in S/4HANA to be set correctly, which is described in the SAP S/4HANA topic page.

Type three: purchase documents

Purchase documents include purchase orders, scheduling agreements, contracts, and request-for-quotation events. The counting rule is per line item. The exemption list includes purchase requisitions that have not been converted, framework agreements that do not generate purchase orders, and intra-company transfers between SAP-resident plants.

The largest measurement error in purchase documents is the treatment of purchasing automation tools that issue many small purchase orders on behalf of business users. SAP’s reading is that each automated purchase order is a countable document, even if the underlying business intent was a single sourcing event. The buyer position is that purchasing-automation patterns that are pre-approved at a higher level can be treated as a single document under the “originating business event” reading. The position is harder to win than the cancellation reading but has been successfully argued in our engagements.

Type four: service & maintenance documents

Service and maintenance documents include service orders, maintenance orders, service notifications, and maintenance notifications. The counting rule is per service order, not per service line. The exemption list includes preventive maintenance orders generated by the system on a defined schedule rather than by an external trigger, and warranty-related service orders that do not result in a billed event.

The most common error is over-counting maintenance orders generated by IoT-connected equipment that produces a service notification for every monitored event. The buyer position is that IoT-generated events that aggregate into a single service action are a single document. The position depends on the specific configuration of the IoT integration and the underlying contract language.

Type five: manufacturing documents

Manufacturing documents include production orders, planned orders, process orders, and inspection lots. The counting rule is per order, not per operation. The exemption list includes orders generated by internal MRP runs (because they are SAP-internal rather than externally-triggered), and orders for subcontracting that do not generate new finished goods.

Manufacturing is the document type with the largest legitimate exemption pool, because most production-order creation is SAP-internal. The largest measurement error is in plants where third-party manufacturing execution systems trigger orders directly. Those are external triggers and count under Digital Access. The discipline is to map each MES connection and count only the externally-triggered events.

Type six: material documents

Material documents include goods receipts, goods issues, transfer postings, and stock transfers triggered by external systems. The counting rule is per material document header. The exemption list includes goods movements that are automatically generated as a consequence of a sales or purchase document already counted under another type (to prevent double-counting), and transfers between SAP-resident storage locations.

The double-counting prevention is contractual but is often missed by SAP’s audit team in the opening claim. A sales-triggered goods issue should not be counted separately from the sales document line that triggered it. The buyer position paper line-items the linkages and removes the double counts. The SAP Digital Access Pricing Decoded white paper sets out the linkage map.

Type seven: quality management documents

Quality management documents include inspection lots, quality notifications, and certificates of analysis. The counting rule is per inspection lot. The exemption list includes inspections triggered by internal MRP processes and inspections that are part of a larger purchase or production transaction already counted.

Type eight: time management documents

Time management documents include time sheets, leave requests, and attendance records created by external systems. The counting rule is per time-record entry. The exemption list includes time records for users who hold a Professional or Limited Professional named-user licence, because those users’ time entries are covered by the named-user licence and not separately counted under Digital Access.

The named-user exemption is the largest single carve-out in the time-management type. Estates with widespread Professional licence coverage typically have no time-management Digital Access exposure at all. Estates with thin Professional coverage and heavy SuccessFactors or third-party time-tracking integration have the largest exposure. The pattern is described in our named user buckets article.

Type nine: financial documents

Financial documents include general ledger postings, accounts payable postings, accounts receivable postings, and asset-accounting postings triggered by external systems. The counting rule is per accounting document. The exemption list includes postings that are automatic consequences of other already-counted documents (invoices generating AR postings, goods issues generating GL postings), and intra-company financial postings.

Financial documents are the largest type by volume in most estates because every business transaction eventually produces a financial posting. The exemption discipline is essential. A naive count that includes the automatic financial consequences of sales and purchase documents will produce a number that is two to four times the contractually-correct figure.

The audit measurement sequence

SAP’s audit measurement of Digital Access uses the Passport tool, which runs against the production estate and produces a count of documents by type and by source system. The Passport count is the SAP-side opening number. The buyer-side counter-measurement runs the same extract but applies the exemption rules contract-by-contract, reads the linkages between document types, and removes double-counted events.

The variance between SAP’s Passport count and the buyer-side counter-measurement is typically 30-55 per cent on a midsize estate, with the buyer-side number being smaller. The variance is the negotiating range. The logistics firm Digital Access rebuilt case file describes a matter that closed at 38 per cent of the opening Passport count.

If you are sizing your Digital Access exposure ahead of a contract event or audit, the document-type breakdown is the starting point. The first conversation is at no cost. Our Digital Access negotiation service describes how we structure the engagement.