SAP Digital Access, the count is negotiable and the rate is not
Digital access licenses the documents that third party and custom systems create in SAP, rather than the humans behind them: a storefront checkout, an EDI channel, or a warehouse robot writing into S/4HANA is the licensable event. Two companies with identical headcount can carry exposure differing by a factor of ten, because the exposure is architectural, set by how many external systems write in and how chatty they are.
Prepared by Redress Compliance · August 7, 2026 · SAP advisory. Based on 25 to 35 digital access and indirect use reviews run 2024 to 2025.
Executive summary
The first count is always too high. In most of our reviews, the first document count sat 20 to 40 percent above the defensible number, and the overstatement was never random: technical users shared between external interfaces and internal batch jobs pushed internal work into the indirect bucket, middleware replayed messages after timeouts with every replay counted, document flows between two licensed SAP systems were counted as indirect, and document types no interface in the estate could create stayed in the estimate because nobody walked the interface list.
Nine types, two multipliers, five counted per line item. Seven document types carry a 1.0 multiplier and two, financial and material documents, count at 0.2, cutting posting heavy industries a structural discount; sales, invoice, and purchase documents count at line item level, multiplying the count for order heavy businesses. Documents count once at creation only: reads never charge, follow on documents spawned inside SAP never recharge, and the reporting and data lake boundary is worth writing into the contract explicitly.
The rate is $0.40 and the discount is the entire negotiation. List is uniform across all nine types, sold in blocks against a tiered volume schedule, and the discount off it is unpublished, which makes it the whole argument: twenty million chargeable documents is $8 million at list before a single point moves. Model the bill as scoped line items, times multiplier, times the net rate SAP quotes in writing, never the estimate on the slide.
The conversion is a modeling exercise, never a default. Named user licensing still covers the people logging in through GUI and Fiori, the two models coexist on the same contract, and staying on named user terms is sometimes cheaper than converting. The adoption program credits run on on premise paper, which sets the sequencing rule: convert under the program before any RISE signature, not after, because the conversion leverage does not survive the move.
The nine types, counting level, and multiplier
| Document type | Counted at | Multiplier | The common source system |
|---|---|---|---|
| Sales document | Line item | 1.0 | Ecommerce, CRM, EDI |
| Invoice document | Line item | 1.0 | Billing engines |
| Purchase document | Line item | 1.0 | Procurement portals |
| Service, manufacturing, quality, time documents | Document | 1.0 | Field systems, MES and IoT, quality tools, workforce systems |
| Financial document | Line item | 0.2 | Posting engines |
| Material document | Line item | 0.2 | Logistics feeds |
Where the count inflates, four mechanisms
- Shared technical users: one account serving external interfaces and internal batch jobs pushes internal work into the indirect bucket, separated by dedicating accounts per integration.
- Middleware replays: messages replayed after timeouts each create a countable document, deduplicated in the scoping or paid forever.
- SAP to SAP flows: documents moving between two licensed SAP systems counted as indirect access, excluded by definition once identified.
- Phantom document types: types no interface in the estate can create, surviving in estimates because nobody walked the list against the table above.
The SAP Digital Access licensing brief
The full model: the nine types, the scoping method that removes the 20 to 40 percent, the block pricing, and the conversion decision worked both ways.
Get the white paper →Convert or stay, the modeling that decides
The model exists because user based indirect claims turned toxic, Diageo and AB InBev among them, and SAP paired the 2018 launch with a countable measure and a pledge separating audit findings from sales negotiations. The buyer decision is genuinely two sided: named user terms sometimes beat conversion, particularly where the indirect population is small and the document volume high, and the conversion prices under the adoption program's credit routes for existing indirect use, on on premise paper, before any RISE signature. The concentration finding from the wider practice compounds the choice: real volume clusters in two or three types, so the blanket conversion overbuys, and the carved conversion, the concentrated types converted with the rest under named users, priced 60 to 80 percent off list with an alternative architecture tabled. The scoping tooling, USMM, the estimation notes, and SAP Passport, produces the count both sides verify, worked in the compliance tools guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across digital access reviews, 2024 to 2025
Roughly 25 to 35 SAP digital access and indirect use reviews sit behind this page, and in most of them the first document count, whoever produced it, sat above the defensible number:
Removed by scoping: dedicated technical users, replay deduplication, SAP to SAP exclusions, and the interface walk.
Before a single point of discount, which is why the unpublished discount is the argument worth having.
The sequencing rule caps the file: the adoption program is on premise paper, so the conversion decision, and the credits it carries, executes before the RISE signature or the leverage transfers to a contract where none of it applies. The named user side of the same estate, the tiers and the reclassification rights, sits in the SAP licensing guide, the audit posture when a count arrives uninvited in the audit survival guide, and the indirect access liability arithmetic in the indirect access licensing analysis.
Your first five moves
- Walk the interface list against the nine types, because an interface you cannot name is a document type you cannot exclude.
- Scope the count before accepting anyone's: dedicated technical users, replay deduplication, and SAP to SAP exclusions remove the 20 to 40 percent.
- Write the read boundary into the contract, reporting and data lake extraction outside the count explicitly, never on slideware trust.
- Model both paths: named user terms against the carved conversion at the concentrated types, priced at the net rate quoted in writing.
- Convert before RISE, or carry the terms deliberately, because the adoption program is on premise paper. The SAP practice runs the model with you.
Frequently asked questions
What is SAP digital access?
The model licensing documents that third party and custom systems create in SAP, rather than the humans behind them: a storefront, EDI channel, or robot writing one of nine defined document types into the digital core is the licensable event. Named user licensing still covers people logging in through GUI and Fiori, and the two models coexist on the same contract.
What does a digital access document cost?
$0.40 at list per chargeable document, uniform across all nine types, sold in blocks against a tiered volume schedule where the net unit price falls with volume. The discount off list is unpublished and is the entire negotiation: twenty million chargeable documents is $8 million at list, and the multipliers change how many documents you have, not the price of one.
Which documents count under digital access?
Nine types: sales, invoice, and purchase documents at line item level and full rate, service, manufacturing, quality, and time documents at document level, and financial and material documents at line item level with a 0.2 multiplier. Documents count once at creation, reads never charge, and follow on documents spawned inside SAP are not recharged.
Why do digital access counts come in too high?
Four recurring mechanisms: technical users shared between external and internal work pushing batch jobs into the indirect bucket, middleware replays each creating a countable document, flows between two licensed SAP systems counted as indirect, and document types nothing in the estate can create surviving in estimates. First counts sat 20 to 40 percent above the defensible number in most reviews.
Should we convert to digital access or stay on named users?
Model it, never default: staying on named user indirect terms is sometimes cheaper, real document volume concentrates in two or three types making blanket conversions overbuy, and the carved conversion, concentrated types converted with the rest under named users, priced best. The adoption program credits apply on on premise paper, so the decision executes before any RISE signature.
Does reading SAP data trigger digital access charges?
No: reads, reporting, and data lake extraction patterns sit outside the document count, because the charge arises only when a non SAP system triggers creation of one of the nine types. The boundary is worth writing into the contract explicitly rather than trusting presentations, since undocumented flows are exactly what audits interpret expensively.
