You are registered. Your guide is ready. Read the full 2026 edition of the SAP Indirect Access Playbook below.
Prepared by Atonement Licensing · buyer-side advisory · last reviewed June 2026. Figures are clearly labelled indicative ranges. The 12-million-document benchmark estate used below is a representative scenario for illustration, not a quote, and document weightings and pricing are SAP's to publish.
Executive summary
SAP indirect access is priced on the documents your integrations create, not the users behind them, and the cost is invisible until SAP surfaces it. Your named user counts look clean while interfaces, middleware, and bots quietly create documents that fall under the digital access metric, a calculation entirely separate from the named user base you already pay for. Buyers who map every non-SAP connection, count the document types it generates, and size that footprint before SAP measures it routinely cut the first digital access number SAP puts forward.
On a representative estate with eight non-SAP systems writing to SAP and around 12 million chargeable documents a year, an exposure counted without mapping, double counting transactions a named user already covers and weighting every type at full value, models near $2.6M per year (indicative). The same estate, once integrations are mapped, duplicates removed, and the no-double-counting boundary applied, models near $1.5M per year (indicative), roughly a 40 percent reduction on the same business activity. The difference is not a discount; it is the cost of arriving with your own count instead of SAP's.
This guide explains the document model and the nine counted types, where exposure hides in third-party connections, how to size your footprint before any measurement, the Digital Access Adoption Program and its conversion credits, the audit triggers and the S/4HANA timing that decides everything, and the contract terms that cap the risk. Read it before your next true-up or conversion, not after the measurement letter arrives.
Indirect access and digital access, explained
Indirect access is the long-standing idea that a non-SAP system or a person using one can consume SAP functionality without holding a named user license. A web shop that posts orders into SAP, a logistics platform that reads inventory, or a bot that creates invoices all touch SAP data without a person logging in. For years, how to license that use was unclear and heavily disputed.
Digital access is SAP's answer. Rather than count the external users or systems, SAP prices the documents created in the SAP system as a result of the indirect interaction. The model is defined in the SAP Software Use Rights and applies to the contracts that adopt it. The shift matters because it changes the question from who is using SAP to how many documents the integration produces.
For buyers, the model is both clearer and riskier. It is clearer because document counts are measurable. It is riskier because a small number of high-volume integrations can generate document counts that translate into a large license figure, entirely separate from the named user base you already pay for.
The nine document types SAP counts
SAP digital access counts the initial creation of nine document types. Reads do not count, and additional line items within a document do not multiply the count. Only the first creation of each document is priced, which makes the type and the volume of documents the two variables that matter.
| Document type | Typical source of indirect creation |
|---|---|
| Sales document | E-commerce platforms and order capture systems posting orders |
| Invoice document | Billing engines and third-party invoicing tools |
| Purchase document | Procurement systems raising purchase orders |
| Service document | Field service and ticketing platforms |
| Manufacturing document | Shop-floor and MES systems |
| Material document | Warehouse and logistics platforms moving stock |
| Quality management document | Inspection and quality systems |
| Financial document | Treasury, expense, and external finance tools |
| Time management document | Workforce and time-capture systems |
The pricing weights these types, with several lower-value types counted at a fraction of a full document. The practical consequence is that two estates with similar transaction volumes can carry very different exposure depending on which document types their integrations create.
Action. Obtain the published document-type weighting and map each integration to the types it creates before assuming a transaction volume translates into cost; the type mix drives the bill as much as the raw count.
Unsure how SAP would count your integrations? Our advisors size it with you before SAP does.
SAP Licensing ExpertsWhere exposure hides
The exposure rarely sits where buyers expect. It is not the obvious interface but the quiet one that accumulates documents. Three sources account for most surprises.
Integration platforms and middleware
Middleware such as SAP Process Integration, SAP Integration Suite, or a third-party bus often acts as the technical user that writes documents into SAP. From SAP's view, the documents created through that channel are in scope regardless of how many human users sit behind it. A single integration account can carry the document load of an entire external system.
E-commerce and customer-facing systems
Order capture is the classic high-volume source. A consumer-facing web shop that posts thousands of sales documents a day generates a document count that can exceed the cost of the named users who manage the orders internally. The same applies to customer portals that create service or financial documents.
Automation and bots
Robotic process automation and scripted integrations create documents at machine speed. Because a bot is not a person, it holds no named user license, so every document it creates falls to the digital access model. Automation projects that look like efficiency wins can quietly build licensing exposure if nobody is counting the documents.
The accounts that look like a single technical user, a middleware service identity, an e-commerce connector, an automation login, are precisely the ones SAP focuses on, because each can carry the document load of thousands of external interactions. They are invisible on a named user report and decisive on a digital access measurement. Inventory every service account that writes to SAP before anyone else does.
Action. List every middleware bus, e-commerce connector, and automation identity that writes to SAP, and tag each with the document types it creates; the highest-volume sources are the ones that never appear as people.
4Sizing your document footprint before SAP does
You cannot negotiate a number you did not calculate. Before any true-up or S/4HANA conversation, build your own estimate of digital access documents so that any SAP measurement can be tested against a baseline you control.
| Step | What to do | Why |
|---|---|---|
| 1. Inventory integrations | List every non-SAP system that writes to SAP, including middleware and bots | You cannot count what you have not mapped |
| 2. Map document types | For each integration, record which of the nine types it creates | Type drives the weighting and the price |
| 3. Estimate volumes | Pull annual creation counts from your own transaction data | Volume is the other half of the calculation |
| 4. Apply the weighting | Weight each type and total the figure | Produces an independent exposure number |
| 5. Compare | Test any SAP measurement against your baseline | The better-documented number sets the terms |
SAP provides estimation and measurement tooling for digital access, and it is worth understanding what those tools count. Run your own numbers first so that you read SAP's report as a comparison rather than a verdict. When the two diverge, the side with the clearer document mapping holds the stronger position.
Chargeable documents a year created by eight non-SAP systems on the indicative benchmark estate, none of which appear on the named user report (indicative).
The modelled annual difference between an unmapped count and a mapped, de-duplicated one on that same estate, the value of arriving with your own number (indicative).
Action. Build your own weighted document count from internal transaction reports before any true-up or S/4HANA conversation, and keep the underlying queries so each figure traces back to a named report.
You cannot negotiate a number you did not calculate. The buyer who counts first reads SAP's measurement as a comparison, not a verdict.5
The Digital Access Adoption Program and conversion credits
SAP offers the Digital Access Adoption Program to move customers from user-based indirect licensing to the document model. The program provides a conversion credit against historical indirect use, intended to lower the cost of adopting the document metric. For many estates it is the route by which indirect access finally gets priced.
The program can be a reasonable path, but the terms decide whether it helps. The credit is calculated from a baseline of documents, and that baseline is exactly what you should size independently first. Adopting the model on SAP's measured figure without your own count risks locking in an exposure that a careful mapping would have reduced.
Treat the program as a negotiation, not a form to sign. Confirm the document baseline, the credit applied, the price per document, and how future growth is handled. A conversion that is fair on day one can become expensive if the contract does not address volume increases on terms you can predict.
Action. Treat the adoption program as a negotiation, not a form: confirm the document baseline, the credit applied, the per-document price, and the growth mechanism before committing.
6Audit triggers and the S/4HANA question
Indirect access surfaces in predictable moments. A standard SAP measurement, the System Measurement using USMM and the License Administration Workbench, can flag external use. A renewal or a true-up brings the question to the table. Most of all, an S/4HANA conversion is the point at which SAP expects digital access to be adopted, because the move resets the commercial relationship.
That makes the conversion both a risk and an opportunity. It is a risk because indirect use that was tolerated under ECC gets priced on the way to S/4HANA. It is an opportunity because you can size your footprint, choose the document model deliberately, and negotiate the terms as part of a larger deal rather than as an isolated compliance finding.
The timing is the whole game. Under older ECC agreements, indirect use was often governed by named user terms and years of accumulated interpretation, real exposure carried without ever being priced. S/4HANA is the reset point: SAP positions the document model as the standard for new and converted agreements, so the move is the moment indirect use becomes a line item. The conversion credit and the adoption program exist precisely to bridge that gap, which tells you SAP expects the question settled at conversion. Buyers who manage this well separate the two decisions, sizing indirect access on its own facts, then choosing the S/4HANA timing with that number in view rather than discovering it mid-migration, where the pressure to finish competes with the patience a fair document negotiation requires.
Size on your facts
Build the independent, weighted document count while you still control the timeline, so the metric is set on your numbers, not the migration's deadline.
Set the model deliberately
Adopt the document model and the conversion credit on a baseline you verified, folded into the wider S/4HANA commercial deal rather than priced as an isolated finding.
Hold the terms
Track document creation against the agreed metric quarterly, so growth is managed under the price hold rather than discovered at the next true-up.
Action. Plan the indirect access question before the conversion, not during it; arrive at the S/4HANA negotiation with a document count already in hand and you control the framing.
7The contract terms that cap the risk
The document model is only as safe as the contract that defines it. Several terms decide whether digital access stays predictable or becomes an open liability.
| Term | What it protects |
|---|---|
| Defined document scope | Pins exactly which document types and events are counted |
| Price per document hold | Caps the unit price for the term so volume growth is predictable |
| Growth and true-up mechanics | Sets how increases are measured and priced, with no retroactive penalty |
| No double counting | Confirms documents are not charged where a named user already applies |
| Audit method | Agrees the measurement tool and the basis, so the count is repeatable |
The most important protection is the no-double-counting principle. Where a transaction is already covered by a named user, it should not also generate a chargeable document. Confirm that in writing, because the cost of an unclear boundary lands on the buyer.
The most common avoidable errors are predictable, and knowing them in advance is the cheapest protection a buyer has. The document model itself settled the counting argument, not the price: it is a measurement method you still negotiate around, not a fixed tariff, so every mistake below is a place where the buyer quietly hands SAP the stronger number.
| Mistake | Why it costs | Better move |
|---|---|---|
| Accepting SAP's document count without your own | Locks in a figure you never tested | Build an independent count first |
| Ignoring middleware and bots | The highest-volume sources go unpriced until SAP finds them | Inventory every technical user that writes to SAP |
| Adopting the document model under migration pressure | Rushes the most consequential pricing decision | Size and negotiate before the conversion deadline |
| Leaving double counting unaddressed | Pays twice where a named user already covers the transaction | Write the no-double-counting rule into the contract |
| No price hold on the document unit | Future growth reprices at SAP's discretion | Cap the per-document price for the term |
Action. Pin the document scope, a per-document price hold, the growth mechanism, and above all the no-double-counting rule in writing; an unclear boundary is always paid for by the buyer.
8Negotiating the digital access deal
Once you hold an independent document count, the negotiation follows a familiar shape. The two variables that move the cost are the price per document and the way future volume is treated, and both are open to negotiation rather than fixed by the model.
Anchor the discussion on your measured footprint, not SAP's estimate. Present the integration map and the document counts in the same units SAP uses, so the conversation is about the facts rather than the method. A buyer who arrives with a documented number sets the starting point, and the starting point shapes the result.
Negotiate the unit price as you would any volume purchase, with deeper discounts at higher committed volumes and a hold across the term. Address growth explicitly: agree how increases are measured, how often, and at what price, so a successful year of trading does not produce an unexpected licensing bill. Where a renewal or an S/4HANA deal is in play, fold the digital access terms into that larger negotiation so the document model is one element of a single outcome rather than a separate compliance charge.
The evidence behind every number is the integration map: a durable, dated register of each non-SAP system that connects to SAP, the service account it uses, the document types it creates, and the annual volume drawn from your own transaction history, with the underlying query attached so each figure traces back to a named report. Keep it current, owned by one team, and reviewed quarterly, because digital access exposure grows with the business and a map that is twelve months stale is a weak foundation in any negotiation. Record the agreed metric, the per-document price, and the measurement method where the next contract owner can find them; the cost of indirect access is controllable only for the buyer who keeps counting after the ink dries.
Action. Anchor the negotiation on your measured footprint in SAP's own units, negotiate the unit price and the growth mechanism together, and fold the result into the wider renewal or S/4HANA deal rather than accepting it as a standalone compliance charge.
Map every integration, size the document footprint on your own weighted count, fix the metric, the per-document price hold, the growth mechanism, and the no-double-counting rule in the contract, and settle it at the S/4HANA conversion where the leverage is highest. The buyers who do worst discover digital access for the first time in an SAP measurement; the buyers who do best arrive years ahead with their own number and adopt the model on their own terms. Across more than 500 enterprise engagements, buyers we advise have negotiated over $2.4 billion in software contracts at average savings of 38 percent by setting terms on measured facts rather than vendor assertions.
Key takeaways
- Digital access prices documents, not users. It is separate from your named user spend.
- SAP counts the creation of nine document types, weighted by type.
- Exposure hides in middleware, e-commerce, and automation, not on the user report.
- Size your document footprint before SAP measures it for you.
- The adoption program is only as good as its baseline and its growth terms.
- An S/4HANA conversion is when indirect use gets priced, so plan ahead of it.
- Fix the document scope, the unit price, and the no-double-counting rule in the contract.
Frequently asked questions
What is the difference between SAP indirect access and digital access?
Indirect access is the older concept: a non-SAP system or user touches SAP data without a named user license. Digital access is SAP's pricing model for it, which counts the documents created in SAP by those interactions rather than the users or systems behind them.
Which documents does SAP digital access count?
SAP digital access prices nine document types, including sales, purchase, invoice, service, manufacturing, material, quality management, financial, and time management documents. Only the initial creation of a document is counted, not subsequent reads or line items.
How do we size our SAP digital access exposure before SAP does?
Identify every non-SAP system that writes to SAP, map which document types each integration creates, and estimate annual document volumes from your own transaction data. That gives you an independent figure to test any SAP measurement against.
What is the Digital Access Adoption Program?
It is SAP's program for moving from user-based indirect licensing to the document model, offering conversion credit against past indirect use. The credit can lower the cost of adoption, but the terms and the baseline matter, so model the outcome before committing.
Does an S/4HANA conversion change indirect access risk?
Yes. A move to S/4HANA is the moment SAP usually expects you to adopt the digital access model, so it is the point at which indirect use gets priced. Size your document footprint before the conversion so the metric is set on your numbers.
Get this guide applied to your SAP estate. Confidential assessment within one business day.
Book a 30 minute callRelated reading: the SAP digital access guide, indirect versus digital access, and the complete SAP licensing guide. See also our ranking of the top software negotiation consulting firms.