SAP digital access replaced the old indirect use disputes with a document based model. It is clearer, but the counting and the conversion choices still decide whether you overpay.
SAP digital access licenses the documents that non SAP systems create in SAP, and the cost turns on which documents are counted and which conversion path you choose, not on user headcount.
SAP digital access licenses the documents that third party and custom systems create in an SAP system, rather than the humans behind those systems. It was SAP's answer to years of indirect use disputes. If a web storefront, an EDI channel, or a warehouse robot writes a document into S/4HANA, that write is the licensable event.
Named user licensing still covers the people who log in through SAP GUI or Fiori. Digital access covers everything else that creates one of nine defined document types. The two models coexist on the same contract, which is why conversion is a modeling exercise, never a default.
The buyer side implication is architectural. Your exposure is set by how many external systems write into SAP and how chatty those integrations are, not by how many employees you have. Two companies with identical headcount can carry digital access exposure that differs by a factor of ten.
The model was announced in April 2018 as ERP pricing for the digital age, moving from contested user based indirect claims to a countable, document based measure. SAP paired the launch with a pledge to separate audit findings from sales negotiations after the Diageo and AB InBev disputes turned indirect pricing toxic.
A charge arises when a non SAP system triggers the creation of one of the nine document types inside the SAP digital core. The usual sources are EDI order intake, ecommerce checkouts posting sales orders, third party logistics confirmations, manufacturing execution systems writing production and goods movement documents, and middleware that replays messages after failures.
Reading SAP data from outside does not create a document, so pure reporting and data lake extraction patterns sit outside the document count. That boundary is worth writing into the contract explicitly rather than trusting slideware.
Digital access counts nine document types, and two of them, financial and material documents, are charged at one fifth the rate of the other seven. The multipliers and the line item counting rule decide who wins and who loses under this model.
SAP defines the nine types and their factors in its Digital Access Adoption Program overview. Five of the nine are counted at line item level, not header level, which multiplies the count for order heavy businesses.
The nine digital access document types
| Document type | Counted at | Multiplier |
|---|---|---|
| Sales document | Line item | 1.0 |
| Invoice document | Line item | 1.0 |
| Purchase document | Line item | 1.0 |
| Service and maintenance document | Document | 1.0 |
| Manufacturing document | Document | 1.0 |
| Quality management document | Document | 1.0 |
| Time management document | Document | 1.0 |
| Financial document | Line item | 0.2 |
| Material document | Line item | 0.2 |
Multiply the raw line item count by the type multiplier to get chargeable documents. One million externally created sales order line items are one million chargeable documents. One million financial posting line items are only 200,000 because of the 0.2 factor.
SAP sells documents in tiered volume blocks on the price list, so the net unit price falls as volume rises. SAP does not publish the unit price, but at cents per document the totals still reach seven figures once external line items run into the tens of millions.
Model your bill as scoped line items, times multiplier, times the tier price SAP quotes in writing.
Documents are counted once at initial creation, not on every read or update, as described in SAP's digital access overview. This is the key fairness feature of the model and a frequent point of confusion.
Creation is attributed by the user that performed the write. Documents created by dialog users in SAP screens fall under named user licensing; documents created through technical or communication users acting for external systems fall into the digital access count. That attribution logic is exactly where raw counts go wrong.
A technical user that a basis team also uses for internal batch jobs drags thousands of internal documents into the indirect bucket. Middleware retries after timeouts create the same order twice. Both inflate the count, and neither reflects licensable use.
The common advice is to convert to digital access as soon as SAP raises indirect use, because the document model sounds cleaner. We disagree. In roughly half the cases we benchmarked, the first document count was overstated by 20 to 40 percent, and conversion at that inflated number locked in cost that staying on named user would have avoided.
The buyer side move is to measure and scope the real document volume first, strip internal SAP to SAP flows and duplicates, then compare both paths on lifetime cost. Convert only when the scoped document model genuinely beats your existing entitlement.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Digital access is a fair model measured badly. Fix the measurement and most of the bill goes with it.
Two 2017 disputes, SAP UK v Diageo and a reported claim of about 600 million dollars against AB InBev, made user based indirect pricing untenable and pushed SAP to launch the document model a year later. They are why digital access exists.
In SAP UK Ltd v Diageo Great Britain Ltd [2017] EWHC 189 (TCC), SAP claimed roughly 54.5 million pounds after Diageo connected two Salesforce based applications to SAP through SAP PI. In February 2017 the High Court held that the people using those front ends needed SAP named user licenses under the contract wording.
Liability was established, damages were left for later assessment, and the parties settled confidentially.
The AB InBev dispute never reached a public judgment. SAP pursued the brewer in arbitration during 2017 on an indirect use claim reported at around 600 million dollars, and the matter settled confidentially in 2018. The size of the number, against one of SAP's largest customers, did the reputational damage.
The lasting lesson is that contract wording decides indirect access disputes, because the Diageo ruling turned on the named user definition Diageo had signed, not on fairness. Broad definitions get enforced. The fix is contractual scoping at signature, not argument at audit.
Indirect access to digital access: the timeline
| Date | Event | Why it matters |
|---|---|---|
| February 2017 | Diageo ruling, High Court | Named user wording enforced against Salesforce front ends |
| 2017 | AB InBev arbitration claim | A reported 600 million dollar indirect use demand, settled in 2018 |
| April 2018 | Digital access launched | Document based pricing replaces user based indirect claims |
| April 2019 | DAAP launched | Conversion incentives: growth only fees or a 90 percent discount |
| 2020 to 2021 | DAAP extended to December 2021 | Uptake lagged; SAP kept the window open |
| 2022 onward | DAAP extended indefinitely | Terms remain available, strongest when tied to S/4HANA moves |
| 2026 | S/4HANA and RISE conversions peak | Digital access becomes a standard line in every conversion deal |
Convert only if the scoped document model beats your current entitlement on lifetime cost, because the Digital Access Adoption Program discounts the entry price, not the trajectory. Conversion is not automatically cheaper.
DAAP launched in April 2019 with two routes. Under the growth option you license at least 115 percent of your current estimated document volume and pay only for the 15 percent growth, so the baseline enters free. Under the discount option you license at least 100 percent of current use and receive a 90 percent discount on those licenses.
The fine print matters. DAAP requires a standalone order form, applies to SAP ERP and on premise S/4HANA, not the SaaS editions, and SAP's published terms state the standard volume discount is not negotiable inside the program. It was extended to December 2021 and then kept open indefinitely, which removes deadline pressure.
You measure it with SAP's own estimation notes and the SAP Passport framework, run on your terms before any audit or conversion conversation. Whoever produces the first credible number anchors the negotiation.
For estimation, SAP ships report notes for each platform: SAP Note 2644139 for ECC and SAP Note 2644172 for S/4HANA. You feed the report a timeframe and the list of technical users that represent external interfaces, and it estimates documents by type. SAP also offers a free Digital Access Evaluation Service built on the same notes.
For actual measurement, SAP Passport tags inbound calls end to end so documents created by external systems are marked at creation; the prerequisites sit in SAP Note 2738406. Passport separates direct from indirect creation far more precisely than the estimation reports, which is why mature buyers move to it before signing anything.
Measurement toolset at a glance
| Tool | What it does | Watch item |
|---|---|---|
| SAP Note 2644139 (ECC) | Estimates document counts by type from history | Only as good as the technical user list you feed it |
| SAP Note 2644172 (S/4HANA) | Same estimation logic for the S/4HANA core | Rerun after scoping; first pass includes internal flows |
| SAP Passport (Note 2738406) | Tags external document creation at the source for real measurement | Needs support package levels and middleware coverage |
| Digital Access Evaluation Service | Free SAP run sizing based on the estimation notes | The output lands in SAP's CRM; treat it as a disclosed number |
The estimation reports count whatever the technical users created, including internal batch work, migration loads, and retry duplicates. In the reviews behind this guide, that is precisely how first counts ended up 20 to 40 percent too high. Clean the user list, exclude SAP to SAP traffic, deduplicate, and only then let a number leave the building.
Digital access wins when many external people each create few documents, and named user licensing wins when a handful of interfaces push millions of line items. The crossover is arithmetic, not philosophy.
Under the old reading, every human behind a third party front end needed a named user. A customer portal with 5,000 registered buyers who each place a few orders a year was ruinous per user but is trivial per document: 5,000 buyers at 40 order line items each is 200,000 documents. The document model was built for exactly that pattern.
Reverse the shape and the answer flips. One EDI hub posting 50 million line items a year replaced a handful of humans, so a legacy contract covering it with a few technical named users may be far cheaper than 50 million documents. Never convert an estate whose volume sits in machine to machine bulk without running this comparison.
Which model is cheaper by integration pattern
| Pattern | People behind it | Documents per year | Usually cheaper |
|---|---|---|---|
| Customer or supplier portal | Thousands | Low per person | Digital access |
| Ecommerce storefront | Anonymous buyers | Scales with orders | Digital access, cap the tiers |
| EDI bulk trading | Very few | Tens of millions | Often the legacy position |
| RPA and bots | None | Varies by process | Model both; attribution is contested |
| Financial postings at scale | Few | Huge, but at 0.2 factor | Digital access more often than expected |
The conversion math changes shape with scale: small estates rarely justify the move, midsize estates hinge on scoping quality, and large estates live or die on tier pricing and the 0.2 factor. The following profiles are illustrative models, not client data.
Three illustrative conversion profiles
| Profile | Scoped documents per year | Likely route | Watch item |
|---|---|---|---|
| Midsize manufacturer, EDI plus MES | 1 to 2 million | Often stay on named user terms | Do not convert to fix a problem you do not have |
| Consumer goods group, ecommerce plus 3PL | 15 to 25 million | DAAP 90 percent discount option | Fix future tier pricing before signing |
| Global bank or insurer, posting heavy | 60 million line items, 12 million after the 0.2 factor | DAAP growth option at S/4HANA conversion | Confirm the 0.2 factor is stated in the order form |
At the small end, a scoped one to two million documents rarely produces a bill that justifies reopening the contract, so the leverage move is to document the count and keep the legacy terms. The moment SAP raises indirect use in an audit, that documented count is your defense.
At the top end the decision is dominated by two clauses: whether the 0.2 multiplier for financial and material documents is written into the order form, and what price the next volume tier carries. A bank that models 60 million raw line items but 12 million chargeable documents has an entirely different negotiation than the raw count suggests.
The S/4HANA or RISE conversion is the one moment SAP will trade digital access terms for migration commitment, so bundle the document question into the bigger deal instead of settling it standalone. SAP wants the conversion signed; you want the indirect question closed forever.
Add a measurement clause: an agreed annual self measurement using the estimation notes or Passport, with results shared under the contract instead of through audit. That converts digital access from a standing audit threat into a metered utility, which is what SAP claimed it was building, as covered in our SAP audit survival guide.
SAP digital access licenses the documents that non SAP systems create in an SAP system, rather than the people behind them. It replaced contested user based indirect use claims with a countable measure.
Digital access counts nine document types. Sales, invoice, and purchase documents carry the heaviest weighting, while material, time, and quality documents weigh the least.
No. Documents are counted once at initial creation. Subsequent reads and updates are not re charged, which is the core fairness feature of the model.
It is an SAP program that offered conversion credits for customers moving from named user indirect licensing to the document based model. Conversion is not automatically cheaper.
Only after measuring your real, scoped document count and comparing both paths on lifetime cost. In many cases staying on named user licensing is cheaper than converting.
No. Document flows between SAP systems are not indirect access and should be excluded before any count. Including them inflates the number significantly.
Initial counts are often overstated by 20 to 40 percent because they include internal flows and duplicates from integration retries. Scoping and deduplication reduce the number.
No. Digital access coexists with named user licensing. It addresses system created documents, while named users still cover the people who log in and transact.
Yes. SAP extended DAAP indefinitely after its original December 2021 end date, so the growth option at 115 percent and the 90 percent discount option both remain available. Leverage is strongest when the conversion rides inside an S/4HANA or RISE deal.
The English High Court held in February 2017 that Diageo's Salesforce based front ends required SAP named user licenses under the contract wording, on a claim of roughly 54.5 million pounds. The ruling made contract definitions decisive and pushed SAP to launch document based pricing in 2018.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.
The document model rewards the buyer who measures carefully and punishes the one who converts on a number nobody checked.
