Contents
Key takeawaysWhat digital access licensesThe nine document typesPricing and a worked exampleWhy first counts run highConvert or stay on named usersContract terms to ask forWhat we saw in 2024 and 2025What to do nextFAQSAP digital access licenses documents that external systems create in SAP, at $0.40 each at list. The rate is fixed and the discount unpublished, so the money is in scoping the count and negotiating the net rate.
- Documents, not people. Nine document types count when a third party or custom system creates them in SAP, while named users still cover people in SAP GUI and Fiori.
- Two types carry a lighter weight. Financial and material documents count at 0.2 per line item, while sales, invoice and purchase documents count at full weight per line item.
- Each document counts once. Creation is the only charge; reads, updates, deletes and follow on documents created inside SAP cost nothing.
- First counts run high. In most of our reviews the first count sat 20 to 40 percent above the scoped number, driven by shared technical users, replays, SAP to SAP flows and phantom types.
- The discount is the negotiation. List is $0.40 for every type, sold in tiered blocks, and the unpublished discount off that rate decides the bill.
- Carve the conversion and time it. Convert the two or three types that carry your volume, keep the rest on named users, and decide before any RISE signature.
This guide is for the people who will sit across from SAP when a digital access count arrives: what is licensed, how it is counted and priced, and how to decide whether to convert.
What is SAP digital access, and what does it license?
SAP digital access licenses the documents that third party and custom systems create in SAP, rather than the people behind those systems. A storefront checkout, an EDI channel or a warehouse robot writing an order into S/4HANA is the licensable event. The person who clicked "buy" on your website never needs an SAP user.
That makes the exposure a question of architecture. Two companies with identical headcount can carry digital access exposure that differs by a factor of ten, because the bill depends on how many external systems write into the digital core and how chatty those integrations are.
Why did SAP move from users to documents?
User based indirect access claims had turned toxic. Diageo lost to SAP in the UK High Court in 2017, and AB InBev faced a claim it settled out of court. SAP launched digital access in 2018 with a countable measure and a pledge to keep audit findings separate from sales negotiations.
The 2018 announcement also said SAP would not pursue back maintenance for under licensing tied to indirect access, for customers who engage with it proactively and in good faith. That assurance belongs in your order form, where a later audit team can read it.
How does digital access sit alongside named users?
Named user licensing still covers the people who log in through SAP GUI and Fiori, and digital access covers what systems create. The two models coexist on the same contract, so a conversion leaves your named users where they are. Our SAP licensing guide covers the named user tiers and reclassification rights.
Digital Access Travels With You
Which documents count under SAP digital access?
Nine document types count, and only when a non SAP system triggers their creation. Sales, invoice and purchase documents count per line item at full weight. Financial and material documents count per line item at a 0.2 multiplier. The other four count once per document.
| Document type | Counted at | Multiplier | Typical 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 document | Document | 1.0 | Field service systems |
| Manufacturing document | Document | 1.0 | MES and IoT platforms |
| Quality management document | Document | 1.0 | Quality tools |
| Time management document | Document | 1.0 | Workforce systems |
| Financial document | Line item | 0.2 | Posting engines |
| Material document | Line item | 0.2 | Logistics and warehouse feeds |
Use the last column as a checklist. Each row names the class of system that usually writes that document type, so your integration inventory tells you which types you actually generate before anyone counts. An interface you cannot name is an interface you cannot exclude. For the definitions behind each row, see our digital access document explainer.
How do the multipliers change the count?
They change how many chargeable documents you have, never the price of one. One million external sales order lines are one million chargeable documents, while one million financial posting lines are 200,000. Posting heavy industries get a structural discount from the 0.2 weight, and order heavy businesses feel the full rate per line on sales, invoice and purchase documents.
What never counts?
- Reads. Queries, reporting and data lake extraction create no document, so they create no charge.
- Updates and deletes. SAP counts a document once, at creation. Changing or cancelling it later adds nothing.
- Follow on documents. When an external sales order triggers a delivery, a material document and an invoice inside SAP, only the order counts.
- SAP to SAP flows. Documents moving between two licensed SAP systems are excluded by definition. SAP tags calls with a technical identifier, the SAP Passport, to tell SAP senders from non SAP senders.
The read boundary is the exclusion most often left to a sales presentation. The contract section below covers how to get it into writing.
SAP Digital Access licensing brief
The scoping method, block pricing and the conversion decision, worked both ways.
Get the white paper →How much does SAP digital access cost?
The list rate is $0.40 per chargeable document, the same for all nine types, sold in blocks against a tiered volume schedule where the unit price falls with volume. The discount off list is unpublished, and that is where the negotiation happens. At list, 20 million chargeable documents cost $8 million before a single point of discount.
Model the bill in three steps. Take the scoped line items per type, apply the multiplier, and multiply by the net rate SAP quotes in writing. The estimate on a sales slide is a starting position, and it is usually built on an unscoped count.
A worked example: the same company before and after scoping
Say a hypothetical distributor runs a webshop, EDI invoicing, a supplier portal, a third party posting engine and a warehouse system, and its first count looks like the left side of the table below. The right side shows the same company after scoping.
| Source and document type | First count, lines | Multiplier | Chargeable, first count | Chargeable, scoped | What scoping removed |
|---|---|---|---|---|---|
| Webshop, sales | 3,000,000 | 1.0 | 3,000,000 | 2,700,000 | 300,000 middleware replays |
| EDI, invoice | 1,200,000 | 1.0 | 1,200,000 | 1,200,000 | Nothing |
| Supplier portal, purchase | 500,000 | 1.0 | 500,000 | 500,000 | Nothing |
| Posting engine, financial | 6,000,000 | 0.2 | 1,200,000 | 700,000 | 2,500,000 lines from internal batch jobs on a shared technical user |
| Warehouse feed, material | 4,000,000 | 0.2 | 800,000 | 400,000 | 2,000,000 lines sent from a licensed SAP system |
| Quality documents in the estimate | 300,000 | 1.0 | 300,000 | 0 | No interface creates this type |
| Total | 7,000,000 | 5,500,000 | 1,500,000 documents |
At the $0.40 list rate, the first count costs $2,800,000 and the scoped count $2,200,000. The scoping alone is worth $600,000 at list. If SAP then prices the scoped count at 60 to 80 percent off list, the net rate is $0.16 to $0.08 and the bill falls to between $880,000 and $440,000.
In this example, sales and invoice lines make up 3,900,000 of the 5,500,000 scoped documents, and the financial and material lines shrink sharply once the 0.2 weight and the exclusions apply.
What will the SAP account team say, and how should you answer?
- "The estimation tool output is your number." Ask for the document level extract behind it, then agree the count only after shared technical users, replays and SAP to SAP flows are separated out.
- "The list price is the same for every customer." That is true of the rate card and says nothing about your price. Ask for the net rate per block in writing, and a price hold on additional blocks for the contract term.
- "Convert everything now, the adoption offer could end." Convert the types that carry your volume and keep the rest under named users, then compare that quote with the blanket one.
- "You can sort out digital access after you sign RISE." The adoption credits run on on premises paper, so the order of signatures decides whether you keep them.
Why do SAP digital access counts come in too high?
In most of our reviews, the first document count sat 20 to 40 percent above the number that held up after scoping, whoever produced it. The overstatement was never random. It came from four recurring causes, each of which scoping removes.
- Shared technical users. One account serving external interfaces and internal batch jobs pushes internal work into the indirect count. The fix is a dedicated technical user per integration.
- Middleware replays. Messages replayed after a timeout each create a countable document. Deduplicate them during scoping, or you pay for them for as long as the license runs.
- SAP to SAP flows. Documents moving between two licensed SAP systems get counted as indirect access. Once identified, they are excluded by definition.
- Phantom document types. Types that no interface in your environment can create stay in estimates because no one checked the interface list against the nine types.
How do you check your own count before SAP does?
Start from your own systems and let SAP's numbers confirm yours. These sources produce a count both sides can verify:
- The integration inventory. List every interface that writes into SAP, with its technical user, message type and target document type. Middleware logs and IDoc monitoring in transaction WE02 show volume by message type.
- Technical users. Review system and communication users in SU01 and note which ones serve more than one integration.
- SAP's estimation tool. SAP delivers it through SAP Note 2644139 for ECC and SAP Note 2644172 for S/4HANA. SAP also offers a free Digital Access Evaluation Service.
- SAP Passport. Check that SAP senders pass the Passport identifier, using the technical guide in SAP Note 2738406. Where it is missing, SAP to SAP documents get logged as if an external system created them.
- USMM. Run the named user measurement alongside, so both halves of the contract are modeled on the same data.
Our compliance tools guide works through USMM, LAW and the estimation notes step by step, and the measurement tools guide covers how to read the output.
Which mistakes cost buyers the most?
- Accepting the first count. In the worked example that is $600,000 at list for documents the company did not need to license.
- Fixing the count once and leaving the architecture alone. If shared technical users stay in place, the next measurement inflates again.
- Letting a peak period stand for the year. If the estimate extrapolates from a busy quarter, such as a retail holiday season, the annual count and the blocks you buy are sized for the peak. Check the measurement window before you agree the number.
Should you convert to digital access or stay on named users?
Model both, because neither is the right default. Staying on named user terms for indirect use is sometimes cheaper, particularly where the indirect user population is small and the document volume is high. Conversion wins when many external systems create modest volumes that would otherwise need a large population of named users.
The Digital Access Adoption Program, launched in 2019, sets the conversion price for existing indirect use. It offers two options:
- Option A. License at least 115 percent of current estimated volume and pay only for the 15 percent growth.
- Option B. License 100 percent of current estimated volume at a 90 percent discount.
SAP extended the program late in 2022 with no set end date, and it can withdraw it at any time. Our adoption program guide compares the two options.
Why converting everything is usually the expensive choice
The common advice is to convert all indirect use while the adoption discount lasts. We disagree, because real volume clustered in two or three document types across our reviews, so the blanket conversion overbuys.
The better course is a carved conversion that covers the concentrated types and keeps the rest under named users. Tabled together with an alternative integration architecture, carved conversions priced 60 to 80 percent off list.
How does the answer change with company size?
A company with 500 SAP users, one webshop and a handful of EDI partners usually has a short interface list. The work is quick, and the decision often comes down to one or two document types. Staying on named user terms can be cheaper here when only a few people sit behind those integrations.
A group with 20,000 users, marketplaces, IoT feeds and dozens of partner integrations has the opposite profile. Volumes are large, replays and shared technical users are common, and the tier position in SAP's volume schedule matters. Scoping is worth the most here, and so is a carved conversion.
What happens to digital access when you move to RISE with SAP?
The adoption program credits apply to on premises contracts, so convert under the program before any RISE signature, or carry your existing terms into RISE deliberately and in writing. After the RISE signature, the discount has no contract to apply to. Our note on digital access in S/4HANA and RISE contracts covers the cloud side.
Which contract terms should you ask SAP for?
Ask for terms that fix how the count is made, since the rate card is the same for everyone and the count is where most of the money sits.
- A written read boundary. Reporting, analytics and data lake extraction sit outside the document count. This stops a later auditor treating read traffic as creation.
- A named SAP to SAP exclusion. List your licensed SAP systems by name, so documents they send are excluded regardless of how a tool tags them.
- The counting method. Once at creation, follow on documents excluded, replays deduplicated, and the measurement tool and system scope agreed.
- Net rate per block and a price hold. Additional blocks at the same net rate for the contract term, so growth is not priced at list.
- The back maintenance assurance. SAP's 2018 statement that it will not pursue back maintenance for past indirect use, written into the order form with your conversion.
- What carries over to RISE. Written confirmation of how your digital access licenses and any conversion credit are treated if you later sign RISE.
What have we seen in SAP digital access reviews in 2024 and 2025?
Roughly 25 to 35 SAP digital access and indirect use reviews sit behind this page. In most of them the first count, whoever produced it, came in above the number that survived scoping. Dedicated technical users, replay deduplication, SAP to SAP exclusions and a walk of the interface list removed the difference.
Volume also concentrated in two or three types, which is why carved conversions priced better than blanket ones. Sequencing mattered as much as the count. The conversion, and the credits it carries, had to be decided on the on premises contract, because none of it carries into the RISE agreement.
SAP lists one rate for every document, so the money is made or lost in how the documents are counted and in the discount you negotiate.
If a count has already arrived uninvited, read our audit survival guide before you reply. For the liability arithmetic on indirect use under the older user based model, see the indirect access guide.
What to do next
- Walk the interface list against the nine types. Name every system that writes into SAP and the document type it creates, before any count is discussed.
- Scope the count before accepting anyone's. Dedicate technical users, deduplicate replays and exclude SAP to SAP flows.
- Write the read boundary into the contract. Put reporting and data lake extraction outside the count explicitly.
- Model both paths. Price named user terms against a carved conversion of your concentrated types, using the net rate SAP quotes in writing.
- Convert before RISE, or carry the terms on purpose. The adoption program runs on on premises paper, so decide before the RISE signature.
- Get help with the model if you need it. Our SAP practice runs the count and both pricing paths with you, for a fixed fee.
Has SAP raised indirect or digital access? Our SAP indirect access defense team, led by former SAP insiders, answers it for a fixed fee.
Frequently asked questions
What is SAP digital access?
It is SAP's model for licensing indirect use by counting documents instead of users. When a storefront, an EDI channel or a robot creates one of nine defined document types in the digital core, that creation is the licensable event. People who log in through SAP GUI or Fiori stay on named user licenses, and both models run on one contract.
What does a digital access document cost?
The list rate is $0.40 per chargeable document for all nine types, sold in blocks on a tiered volume schedule where the unit price drops as volume grows. SAP does not publish the discount, so it has to be negotiated. At list, 20 million chargeable documents come to $8 million, which is why every point off the rate matters.
Which documents count under digital access?
Sales, invoice and purchase documents per line item at 1.0, service, manufacturing, quality management and time management documents once per document at 1.0, and financial and material documents per line item at 0.2. A document counts only at creation, and anything SAP spawns from it internally is free.
Why do digital access counts come in too high?
Because the raw measurement cannot tell intent. A technical user shared by an interface and an internal batch job makes internal work look external, middleware retries look like new orders, SAP to SAP traffic without a Passport looks third party, and estimates keep document types nothing in your environment creates. Each has to be separated out during scoping.
Should we convert to digital access or stay on named users?
Decide it with numbers for your own interfaces. Named user terms can be cheaper when few people sit behind high volume integrations. When conversion is right, a partial one covering the concentrated types usually beats converting everything, and it should be signed on your on premises contract before any RISE agreement.
Does reading SAP data trigger digital access charges?
No. A charge arises only when a non SAP system causes one of the nine document types to be created, so queries, reports and extraction into a data lake are outside the count. Ask for that boundary in the contract text, since audits read undocumented flows in SAP's favor.
Is the SAP Digital Access Adoption Program still available?
SAP extended it late in 2022 without an end date, and it can withdraw it at any time. Its two options are licensing 115 percent of estimated volume and paying only for the growth, or licensing 100 percent at a 90 percent discount. Confirm availability with SAP in writing before you plan around it.