Twenty-two pages on the indirect-access background, the nine document types, the counting methodology, the conversion credit, audit posture, integration-point inventory, the RISE and S/4HANA interaction and the renewal posture inside the SAP commercial relationship.
The SAP indirect-access dispute predates the Digital Access programme by a decade. Through the 2010s, SAP asserted that named-user licences were required for any human or system that read or wrote SAP data, including data accessed through third-party applications. The Diageo High Court judgement of 2017 and the Anheuser-Busch InBev arbitration that followed gave commercial substance to the dispute and crystallised the publisher-side exposure for SAP buyers across the world.
The SAP commercial response was the Digital Access programme, introduced in 2018. The programme replaced the indirect-named-user logic with an outcome-based count: the licence price scales with the number of documents created in SAP by indirect sources, not with the number of users behind the integration. The reframing was simultaneously a commercial concession (the named-user uplift was no longer the only path) and a commercial pivot (a new countable basis was now in scope).
The Admodum reading is that Digital Access removes one form of indirect-access exposure and introduces another. The buyer-side defence on Digital Access is structurally similar to the buyer-side defence on the named-user reconciliation: classify the integration, count the documents, contest the counts where the architecture supports the contest, and value the conversion credit at the negotiation table. This paper sets out that protocol across nine sections.
SAP defines nine document types inside the Digital Access price schedule. The nine types are intended to span the principal indirect-access patterns inside the SAP transactional surface and to provide a countable basis for licence sizing.
The price schedule sets a per-document licence price for each type, with discount tiers at higher document volumes. The pricing is broadly uniform across the nine types but the document populations differ materially across types and across estates; the high-volume types in most enterprises are the Sales Document, the Invoice Document and the Material Document.
The Digital Access count is an annual count of documents created in SAP by indirect sources. The count is performed against the SAP transactional record over a full year, with each document type counted once at creation. Document amendments and counter-leg postings are not counted; only the original creation event triggers the count.
The SAP Passport is the technical mechanism by which the system attributes a document to an indirect source. Documents created by a user via the standard SAP GUI carry an SAP Passport identifying the user; documents created via a third-party integration carry an SAP Passport identifying the integration. The counting tool reads the Passport and produces the Digital Access count by document type and by source.
Where the Passport coverage is incomplete (older systems, custom integrations not registered for Passport, indirect document creation through non-standard interfaces), SAP publishes an Estimation Note that allows the count to be estimated from the document tables directly. The Estimation Note approach is broader than the Passport-based approach and can over-count documents where the underlying logic includes counter-leg postings that should be excluded.
The Admodum buyer-side document-discovery protocol runs the Estimation Note against the buyer’s SAP transactional record, then runs a second-pass review that classifies each document by integration source, by document type and by counter-leg exclusion eligibility. The output is the buyer-side Digital Access position, against which the SAP audit position is compared. The two positions usually differ; the gap is the negotiation surface.
The Digital Access Adoption Programme conversion credit is the SAP-side commercial sweetener that encourages buyers to adopt Digital Access in place of the legacy named-user position. The credit converts a defined percentage of the existing named-user spend into Digital Access entitlement, with the conversion ratio published at programme level and the credit applied against the buyer’s Digital Access purchase.
The credit is meaningful but is not free. The Adoption Programme typically requires the buyer to commit to Digital Access for a defined term, to refrain from claiming indirect-access through the legacy named-user position, and to bring the document count into line with the SAP audit position at a defined cadence. The credit is therefore a commitment in exchange for entitlement, and the buyer-side valuation of the credit must price the commitment alongside the entitlement.
The buyer-side valuation runs three reads. The first is the conversion ratio against the named-user spend at risk; this is the credit headline. The second is the document count at programme entry against the document count at programme exit, which captures the commitment cost. The third is the renewal posture at programme expiration, which captures the negotiation surface at the next term.
The Admodum experience is that the credit is favourable inside a narrow band of buyer profiles: estates with a substantial named-user uplift exposure, estates with a manageable document count, and estates with a clear architectural direction (typically RISE or S/4HANA migration) inside the conversion-credit term. Outside that band, the credit is less favourable and the buyer should price the alternative paths carefully.
SAP audits the Digital Access surface on a similar cadence to the named-user audit programme. The audit instrument is the Self-Declaration questionnaire, supplemented by direct execution of the SAP-published audit script against the buyer’s SAP transactional record. The questionnaire requests confirmation of the integration inventory, the document count by type and the conversion credit position.
The buyer-side audit-defence protocol mirrors the Microsoft SAM audit-defence protocol set out in the Microsoft SAM Audit Defence paper: read the engagement letter, contest the scope, control the script execution, run the parallel evidence file and frame the closing memorandum. The differences are in the document-counting mechanic rather than in the underlying defence DNA.
The SAP audit script reads the buyer’s SAP transactional record and produces a Digital Access count. The script can be executed by the buyer (with the output shared with the auditor) or by the auditor (with the buyer’s SAP team providing access). The Admodum posture is that the script is executed by the buyer, with the output reviewed by the buyer’s legal and licensing team before transfer to the auditor. The buyer’s SAP basis team should not allow direct execution by the auditor inside the production system.
Where the script output exceeds the buyer-side document-discovery protocol output, the gap is the basis for the dispute. The Admodum buyer-side reading is that the gap is sometimes a counter-leg exclusion error, sometimes a Passport-attribution error and sometimes a legitimate undiscovered indirect-source population. The buyer-side task is to identify which of the three drives each line of the gap and to negotiate accordingly.
The integration-point inventory is the buyer’s structured record of every third-party application, custom integration, EDI gateway, RPA platform and middleware bus that creates documents in SAP. The inventory is the input to the document-discovery protocol and the bargaining basis for the conversion credit negotiation.
The inventory typically includes the Salesforce-to-SAP integration (Sales Documents and Invoice Documents), the Workday-to-SAP integration (Time Management Documents and Financial Documents in payroll posting), the ServiceNow-to-SAP integration (Service & Maintenance Documents and Sales Documents in B2B service request flows), custom EDI gateways (Sales, Invoice and Purchase Documents from trading-partner flows), and RPA platforms posting Material Documents and Financial Documents from automated processes.
The buyer-side reduction discipline asks four questions of each integration: (a) is the document actually created by the integration or by an SAP-internal counter-leg? (b) is the document a Digital Access document or is it inside an excluded class? (c) can the integration architecture be modified to reduce the document creation (batched documents, deferred posting, summary documents)? (d) is the integration retained at the next architectural cycle or is it deprecated under the application portfolio plan?
A well-run reduction discipline typically removes a meaningful percentage of the auditor-default document count. The reduction is not negotiation; it is licensing engineering. The conversion credit negotiation then runs against the reduced count.
The Digital Access construct carries forward into the RISE migration economics and the S/4HANA conversion. The document count is the same on either side of the migration; the conversion credit interacts with the RISE bundle and with the S/4HANA named-user reclassification.
Inside the RISE economics paper, the Digital Access component sits inside the RISE bundle as a defined sub-line, with the document quantum agreed at the RISE signature date and the renewal cadence aligned to the RISE term. The Admodum posture inside RISE is to negotiate the Digital Access quantum independently from the RISE bundle headline, so the Digital Access component is contestable at the next RISE renewal on its own merits.
Inside the S/4HANA conversion paper, the Digital Access count is computed against the S/4HANA transactional record from the cutover date forward. The conversion credit is sometimes re-stated at the cutover date, depending on how the conversion programme is structured; the buyer-side discipline is to verify that the credit is preserved across the cutover and is not absorbed into the broader S/4HANA conversion arithmetic.
The Digital Access renewal posture is sized to the document growth trajectory across the term and the broader SAP commercial relationship. The headline question at renewal is the over-consumption schedule, the discount tier and the conversion credit treatment at the next term.
The over-consumption schedule is the price at which documents created above the committed quantum are licensed at renewal. The schedule should match the committed-quantum price; where SAP proposes a step-up, the buyer-side discipline is to resist the step-up unless the conversion credit covers a material part of the difference.
The discount tier is the price band at which the committed quantum is licensed. The Digital Access price schedule carries volume tiers that improve with scale; the buyer-side discipline is to commit at the band that matches the trailing-year document count, not at the band that matches the projected growth ambition.
The conversion credit at renewal is sometimes re-stated, sometimes carried forward and sometimes extinguished, depending on the structure of the original Adoption Programme. The buyer-side discipline is to read the credit treatment language carefully at the original commitment and to anchor the renewal conversation on the credit position rather than letting the credit slip into the renewal arithmetic uncontested.
The closing posture protocol is built around the SAP commercial reading set out in the SAP practice page, runs inside the Renewal Programme on a fixed fee, contingency or annual retainer basis, and is closely coupled to the Audit Defence Programme where the Digital Access dispute is open.
The SAP Digital Access paper sits inside the SAP cluster of the Admodum white paper library. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across more than seventy Digital Access engagements inside the firm’s SAP cluster. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer, depending on the buyer’s posture at the Self-Declaration date. The full case studies library carries Digital Access engagement summaries; the blog publishes the running practice analysis.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, General Counsel, SAP basis lead or sourcing team on a private call. Engagements run as fixed fee, contingency or annual retainer.