Indirect access, the buyer who counts documents first controls the settlement
SAP indirect and digital access is the biggest unbudgeted line most SAP estates carry: indirect access is the use of SAP functionality by people or systems without direct named user licenses, and digital access is the 2018 model pricing that use by counting nine document types created in the system rather than the people behind them. The exposure is a baseline problem before it is a negotiation problem, and the buyer who instruments the integrations and counts the documents first holds the settlement.
Prepared by Redress Compliance · August 8, 2026 · SAP advisory. Based on 180 to 220 SAP renewals and audit defenses supported 2024 to 2025.
Executive summary
The opening claims ran 3 to 6 times the measured truth. SAP opening claims on indirect or digital access ran 3 to 6 times the buyer's measured throughput before any negotiation began, with claims of 40 to 60 million documents on mid market estates appearing regularly in audit conversations.
And the claim and the baseline were rarely within an order of magnitude of each other.
The realized settlement, when the buyer brought a measured baseline first, landed at roughly 40 to 60 percent of the opening exposure on document count alone.
The baseline is buildable, because the volume concentrates. Four to eight integrations produced 70 to 85 percent of the document volume on every estate we measured, which means a credible baseline does not require instrumenting every system: the customer portals creating sales orders.
The commerce platforms posting invoices, the field service apps logging time, and the middleware writing financial documents carry the count, and the estate that meters those handful of pipes knows its number before SAP proposes one.
The metric shifted from people to documents, and the budgets decoupled.
Digital access counts nine outcome document types, sales orders, invoices, purchase orders, service orders, manufacturing orders, quality notifications, material documents, financial documents, and time management documents.
Created in SAP regardless of which system originated them: a buyer can hold the named user count flat for years and still meet a six or seven figure digital access claim, because document volume scales with business activity rather than seats.
And the seat budget and document budget no longer move together.
The three myths cost more than the metric.
Digital access is not only about external users, internal bots, batch jobs, and middleware posting documents create the same exposure.
Read only integrations are not automatically free, since reads do not trigger documents but most read only integrations end up writing back, and that is where the meter starts.
And the line cannot be priced precisely up front, it is negotiated, which is why the defensible number matters more than the perfect one. RISE and S/4HANA do not remove indirect access, they re price it and shift where the documents are counted.
From named users to documents, what changed
| Era | The metric | The exposure pattern |
|---|---|---|
| Before 2018, indirect access | Named users, argued | Whether a person via a non SAP system needed a license |
| 2018 onward, digital access | Nine document types, counted | System traffic, regardless of who or what created it |
| The modern estate | Documents from integrations | Volume scaling with business activity, not seats |
| RISE and S/4HANA | The same documents, repriced | The exposure shifted and re priced, never removed |
The line is large for the same reason it is hidden.
Most SAP estates grew around dozens of integrations, portals, and bots moving data in and out of the core, each interaction able to create a chargeable document, and the buyer rarely measures them the way SAP can: the pre 2018 disputes were never about whether use occurred.
They were about paying twice and where the boundary between a person and a process sits, and the document metric answered the argument by changing the unit rather than settling the question.
Building the baseline, four to eight pipes
- Inventory the integration footprint: every system writing into SAP, with the handful of high volume pipes identified, because 4 to 8 of them carry 70 to 85 percent of the count.
- Instrument the document creation: meter the nine document types at the integration boundary, the measurement SAP will otherwise perform for you.
- Classify the write backs: the read only integrations that quietly write, where the free assumption meets the meter.
- Count the internal automation: bots, batch jobs, and middleware posting documents, the exposure the external user myth misses.
- Bring the number to the table first: the defensible baseline that settled at 40 to 60 percent of opening claims running 3 to 6 times higher.
The indirect and digital access brief
The document counting method, the integration instrumentation, the DAAP evaluation, and the settlement sequence worked end to end.
Get the white paper →The settlement, and where the clauses land
The negotiation runs on the baseline gap: SAP opens with its measurement or its estimate, the buyer counters with instrumented throughput.
And the settlement lands between them in proportion to the credibility of the buyer's number, which is why the 40 to 60 percent outcomes belonged exclusively to the estates that counted first.
The contract layer decides the future exposure, document band definitions, growth treatment, and the RISE and S/4HANA conversion terms where the exposure re prices rather than disappears.
The named user cleanup that intersects the document metric runs in the SAP audit defense framework, where digital access exposure ran 2 to 4 times internal estimates on integrated landscapes; the full document model in the digital access guide and the indirect access pillar.
And the RISE commercial event most settlements now fold into in the deployment models analysis.
- 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 SAP engagements, 2024 to 2025
Across roughly 180 to 220 SAP renewals and audit defenses our team supported between 2024 and 2025, the SAP opening claim and the buyer's measured baseline were rarely within an order of magnitude of each other:
Opening indirect and digital access claims against measured throughput.
Of document volume from 4 to 8 integrations, making the baseline buildable.
The vertical mix behind the bands, roughly 30 percent retail and consumer goods, 25 manufacturing, 20 financial services, 15 public sector, matters because document patterns differ sharply by industry.
Two estates of identical headline size sitting multiples apart on throughput, which is why the report frames bands rather than averages.
The strategic read is unchanged across every vertical: the exposure is a baseline problem before it is a negotiation problem, the concentration makes the baseline a bounded project rather than an estate wide one.
And the buyer who arrives with a defensible count negotiates the settlement while the buyer who arrives without one receives it.
Your first five moves
- Map the integration footprint and find your 4 to 8 pipes, where 70 to 85 percent of the volume lives.
- Instrument the nine document types at the boundary, the count SAP will otherwise run for you.
- Audit the read only integrations for write backs, where the free assumption meets the meter.
- Count the bots and batch jobs, the internal exposure the external user myth conceals.
- Bring the measured number to the table first, the move that settled at 40 to 60 percent of claims. The SAP practice runs the baseline with you.
Frequently asked questions
What is SAP indirect and digital access?
Indirect access is the use of SAP functionality or data by people or systems without direct named user licenses.
Digital access is the 2018 commercial model pricing that use by counting nine document types created in SAP, sales orders, invoices, purchase orders, service orders, manufacturing orders, quality notifications, material documents, financial documents, and time management documents.
Regardless of which system created them.
How large are SAP indirect access claims?
Opening claims ran 3 to 6 times the buyer's measured throughput in our engagements, with claims of 40 to 60 million documents on mid market estates appearing regularly in audit conversations.
The realized settlement, when the buyer brought a measured baseline first, landed at roughly 40 to 60 percent of the opening exposure on document count alone.
How do you measure SAP digital access exposure?
By instrumenting the integrations and counting documents at the boundary, and the concentration makes it tractable: four to eight integrations produced 70 to 85 percent of document volume on every estate we measured, so the baseline is a bounded project covering the customer portals.
Commerce platforms, field service apps, and middleware that actually write into SAP.
Are read only SAP integrations free of digital access?
Reading SAP data does not by itself trigger a document, but most read only integrations end up writing back, and that is where the meter starts: the write back audit is a core baseline step.
The related myth, that digital access is only about external users, fails the same way, since internal bots, batch jobs, and middleware posting documents create identical exposure under the 2018 model.
Does moving to RISE or S/4HANA remove indirect access?
No: RISE with SAP and S/4HANA re price the exposure and shift where the documents are counted, they do not remove it, and the conversion terms are where the future liability is actually negotiated.
The document metric follows the estate into the new contracts, which is why the measured baseline matters as much at the RISE negotiation as at the audit.
How do you settle an SAP indirect access claim?
From your own count: the settlement lands between SAP's opening number and the buyer's instrumented throughput in proportion to the credibility of the buyer's baseline, and the 40 to 60 percent outcomes belonged exclusively to estates that counted first.
The contract layer then bounds the future, document band definitions, growth treatment, and conversion terms, because the claim settles once but the meter keeps running.
