SAP Digital Access exemptions, explained.

The Digital Access licensing model collects revenue from the nine document types SAP defines as chargeable. What sits outside those nine is, in principle, not part of the chargeable surface. The principle is easier to state than to defend: SAP’s opening audit position frequently sweeps adjacent document categories, system-generated technical records, and intra-document-flow events into the count. The defensible exemption schedule is the contractual instrument that prevents that sweep. This article describes how that schedule works, what should be in it, and how the negotiation usually goes.

The nine chargeable documents

The Digital Access model identifies nine chargeable document categories: sales documents, service documents, purchase documents, financial documents, time-management documents, material documents, master-data documents, quality-management documents, and manufacturing documents. The categories are coarse, and the contractual definition of each is finer than the headline name suggests. Most of the interpretive work in any Digital Access negotiation happens inside these definitions. A clear summary is in our document-counting article.

Anything that falls outside the nine categories is, in the standard contractual reading, not part of the chargeable count. The challenge is that the audit team’s counting tools sometimes pick up records that are technically inside one of the nine categories but contractually exempt because of how they were generated, the upstream document they relate to, or the technical configuration of the system.

The default exemptions

Three exemption categories are essentially default under the standard Digital Access order form. First, documents generated by named, licensed SAP users acting in their own session are not Digital Access documents. They are direct human postings, covered by the named-user licence. Second, documents that originate inside SAP and stay inside SAP — system-internal transformations, reposting events, downstream document-flow steps such as a delivery against an order — are not multiplicative under the standard reading. The original document was chargeable; the downstream propagation is not.

Third, certain technical record types — idoc envelopes, change-document logs, system-control records — are not chargeable Digital Access documents under the standard reading because they are infrastructure records rather than business documents. SAP’s opening audit position sometimes counts these; the exemption argument is contractual rather than technical, and is usually accepted on a properly structured response.

The conditional exemptions

Beyond the defaults, several conditional exemption categories matter to most estates and are worth negotiating into the order form explicitly rather than leaving to the standard reading. The first is the read-only flow — data extracted from SAP for use by a downstream consumer (analytics, BI, master-data replication) that does not create or update SAP documents. The Digital Access model is silent on read-only, and the buyer-side reading is that read-only flows are not part of the chargeable surface. The argument is more robust when written into the schedule.

The second is the intra-document-flow exemption. A purchase order that triggers a goods receipt, a goods movement, and a financial posting will produce four documents in SAP. Under the chargeable surface, only the originating purchase document is normally chargeable in a properly framed schedule. The downstream events are propagations of the same business transaction. Writing this into the order form prevents future re-reads of the count. The pattern is discussed in our indirect-to-digital migration article.

The integration-to-integration exemption

Some estates pass documents between non-SAP applications via SAP middleware without those documents being intended for posting into SAP at all. SAP’s tools sometimes log these in-flight documents and the audit team has, in some cases, included them in the chargeable count. The exemption argument is that documents that are in-flight only and not posted are not Digital Access documents. The contractual position is strong; writing it into the schedule prevents the argument.

The negotiation arc

The Digital Access negotiation typically opens with SAP’s tooling producing a count and the buyer responding with a contractual reading of which categories should be in scope. The opening gap is usually substantial — thirty to fifty per cent of the tooling count is often eliminable on contractual grounds. The negotiation then moves to two adjacent topics: the tier pricing for the chargeable count and the schedule of exemptions for the contract term.

The exemption schedule is the more durable lever. Tier pricing is renegotiable at the next contract event; the exemption schedule, if properly drafted, persists for the contract term and forecloses re-counting. The schedule should list, by document category and by integration pattern, what is included, what is excluded, and the conditions under which a category that is currently excluded could become included. The methodology is in our Digital Access negotiation service page and in the Digital Access topic page.

What the order form should say

An order form that protects the buyer position should include, at minimum, four specific exemption provisions. A read-only flow exemption that excludes data flows that do not create or update SAP business documents. An intra-document-flow exemption that defines the originating document as the chargeable event and excludes downstream propagations. A technical-record exemption that excludes idoc envelopes, change-document logs, and system-control records from the count. And a re-measurement protection that fixes the tier price per document category for the contract term and prevents mid-term reclassification of an exempt category as chargeable.

These four provisions, drafted together, foreclose most of the audit-time argument over the chargeable count. Without them, the count is a matter of SAP’s tooling and the buyer’s ability to argue against it at audit time. With them, the count is a matter of the contract. The Digital Access document strategy white paper covers the drafting in detail.

The audit-time reality

At audit time, the buyer’s strongest argument is that the chargeable surface is defined by the order form, not by SAP’s tooling. If the order form has the four exemption provisions, the conversation is short. If it does not, the conversation reverts to the standard contractual reading, which is still defensible but more contested. Most of our active Digital Access engagements involve estates where the original order form was signed without the exemption provisions and where the audit team is now pressing on the count.

The defensive position in that scenario is contractual rather than technical. The standard reading of the Digital Access model supports the read-only argument, the intra-document-flow argument, and the technical-record argument. The position is robust enough to anchor a settlement. The methodology is the same as in the indirect-access settlement examples article, and the larger framework is covered in our audit response sequence article.

The volume distribution problem

Most estates running Digital Access have a heavily skewed document distribution: a small number of high-volume document categories produce most of the count, and a long tail of low-volume categories produces the remainder. The exemption schedule should address both. The high-volume categories need tight definitions to prevent over-counting; the tail needs an aggregated treatment so that low-volume categories do not consume disproportionate negotiation time at the next audit.

The conversion case

For estates considering the conversion from pre-2018 indirect-use exposure to Digital Access, the exemption schedule is the principal contractual instrument. The conversion economics depend on the chargeable count, and the chargeable count depends on the exemption schedule. A well-drafted schedule turns the conversion into a measured, capped, and defensible entitlement; a poorly drafted schedule turns it into a different shape of exposure. The global-retailer conversion case file documents one such conversion in full.

If the order form was signed without the exemption provisions and the audit team is now pressing on the count, the highest-value step is to define the buyer-side reading of the standard contractual position before responding to the count. The conversation is then anchored on a defensible reading, not on the count.

The economic case for the schedule

Across our $180M+ in client savings on SAP matters, Digital Access exemption work has produced settlements in the range of forty to seventy per cent reduction from SAP’s opening count, depending on the maturity of the order form and the strength of the contractual reading. The 68% firm-wide average reduction across all heads of claim is broadly representative. The work that produces the reduction is contractual: defining the exemption schedule, reading it into the order form, and anchoring the audit-time conversation on the schedule rather than on the tooling. The contract negotiation service covers the drafting and the audit-time defence together.