SAP Digital Access audit findings, patterned.

SAP audit findings on Digital Access exposures cluster into a recognisable set of patterns. The patterns repeat across estates and across audit teams, in part because they reflect the inherent ambiguities of the document model and in part because the audit team’s counting tools tend to over-include rather than under-include. Recognising the patterns at the point of receipt accelerates the defensive response and shortens the negotiation. This article describes the five most common audit-finding patterns we encounter, the contractual or technical argument that addresses each, and the structural remedy that closes the matter for the contract term.

Pattern one — downstream document multiplication

The most common finding pattern is the multiplication of documents along an SAP-internal document flow. A purchase order in SAP triggers a goods receipt, a goods movement, and a financial posting. The audit team’s tooling produces a count that includes all four documents, even where only the originating purchase document was actually generated by an external system. The remaining three are SAP-internal propagations.

The defensive argument is that the originating document is the chargeable event under a properly constructed reading of the Digital Access schedule, and the downstream propagations are not separately chargeable. The argument is robust because it reflects the business reality of the document flow and because the alternative reading would produce double-counting on virtually every transaction. The structural remedy is an intra-document-flow exemption written into the order form. The pattern is covered in our document-counting article.

Pattern two — the technical-record sweep

The second pattern is the inclusion of technical records — idoc envelopes, change-document logs, system-control records, application logs — in the chargeable count. The tooling sweeps these because they are records in the SAP database; the buyer’s reading is that they are infrastructure, not business documents.

The defensive argument is contractual: the Digital Access schedule defines chargeable documents as business documents, not technical records. The schedule’s nine categories — sales, service, purchase, financial, time, material, master, quality, manufacturing — describe business artefacts, not the technical wrappers around them. The structural remedy is a technical-record exemption written into the order form, listed by record type. The discussion is expanded in our Digital Access exemptions article.

Pattern three — the read-only inclusion

The third pattern is the inclusion of read-only data flows in the chargeable count. The audit team identifies that data is leaving SAP for use by a downstream BI, analytics, or master-data system, and treats the data movement as a chargeable Digital Access event.

The defensive argument is that the Digital Access schedule is silent on read-only flows. The chargeable document types are creation and update events on business documents in SAP; read-only flows are extractions from SAP that do not create or update SAP documents. The buyer-side reading is that read-only flows are outside the chargeable surface. The argument is contractually strong and is usually accepted on a properly framed response. The structural remedy is a read-only carve-out in the order form. The methodology overlaps with the indirect-access read-only argument covered in our middleware risk article.

The master-data sub-pattern

A sub-pattern of the read-only inclusion is the master-data replication finding. The audit team identifies that master-data records are being replicated out of SAP to other systems and counts the replication events as chargeable Digital Access documents. The defensive argument is that master-data replication is a read-only flow that does not create or update SAP documents on the SAP side. The argument is the same as the broader read-only carve-out applied to a specific document type.

Pattern four — the tier mis-classification

The fourth pattern is the application of the wrong tier price to the chargeable document count. The Digital Access tier schedule defines several pricing tiers, with the unit price decreasing as volume increases. The audit team’s tooling sometimes applies the higher tier price to the full document count rather than to the marginal documents at that tier. The result is an over-statement of the chargeable exposure.

The defensive argument is the standard reading of the tier schedule: tier pricing is marginal, not blended. The remedy is contractual rather than technical: a re-statement of the chargeable exposure at the correct tier mathematics. The structural protection is a tier-pricing clarification written into the order form so the calculation is unambiguous at any future audit. The pricing tiers article covers the tier mathematics in detail.

Pattern five — the baseline drift

The fifth pattern is more contractual than technical. The audit team produces a Digital Access measurement that, in absolute terms, exceeds the previous measurement by a wide margin, and attributes the increase to growth in chargeable activity. The buyer’s analysis often reveals that the increase is a change in measurement methodology, a change in the counting tool’s configuration, or an inclusion of integration patterns that had previously been excluded.

The defensive argument is that the variance is a methodology change, not a chargeable-activity change. The remedy is a baseline-reconciliation memo that reconciles the new measurement against the prior one and isolates the methodology variance from the activity variance. The structural protection is a re-measurement protection clause in the contract that fixes the measurement methodology for the contract term. The pattern is discussed in our internal compliance program article.

The defensive response shape

An effective defensive response to a Digital Access audit finding addresses each applicable pattern with the contractual or technical argument it requires. The response should be structured: a finding-by-finding analysis that identifies the pattern, the contractual reading, and the buyer-side counter-position. The structure prevents the response from being read as a generic dispute and forces the audit team to engage with each finding on its merits.

The methodology is the same as for any structured audit response: the audit response sequence article covers the broader framework, the Digital Access negotiation service covers the engagement model, and the Digital Access document strategy white paper covers the contractual analysis.

The structural remedies

Across the five patterns, four structural remedies address the bulk of the recurring risk. An intra-document-flow exemption that defines the originating document as the chargeable event. A technical-record exemption that excludes technical wrappers from the count. A read-only carve-out that excludes extraction flows from the chargeable surface. And a re-measurement protection that fixes the tier pricing and the measurement methodology for the contract term.

The four remedies, drafted into the order form, foreclose most of the audit-time argument over the count. Without them, every audit is a re-argument of the same set of patterns. With them, the audit is a measurement against an unambiguous chargeable surface. The drafting work is contained: a single round of contractual negotiation that produces a durable instrument. The global retailer case file documents one such drafting effort in full.

If a Digital Access audit finding has just arrived and the patterns above are recognisable in it, the next step is the structured finding-by-finding response. The response is contained; the protection it produces lasts the contract term.

The economic case

Across our $180M+ in client savings, Digital Access findings have produced settlements consistent with the 68% firm-wide average claim reduction. The pattern recognition is the upstream work; the contractual response is the downstream work; the structural remedy is the lasting work. The work compounds across audit cycles: an estate that has addressed the five patterns once does not re-litigate them at the next audit. The Digital Access negotiation service page covers the full engagement model, and the Digital Access topic page covers the contractual context.