SAP indirect access is priced on the documents your integrations create, not the users behind them. 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. This guide explains the document model, the nine counted types, the audit triggers, and the contract terms that cap the exposure.
The reason indirect access feels like a trap is that 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. You can see that footprint first. Everything below is about putting the buyer in possession of the numbers before the conversation starts.
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.
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.
Sizing 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.
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.
Audit 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.
Plan the indirect access question before the conversion, not during it. Buyers who arrive at the S/4HANA negotiation with a document count already in hand control the framing. Buyers who wait inherit SAP's number.
The 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.
How the dispute reached the document model
Indirect access did not start as a pricing model. It started as a disagreement about what a named user license covers. SAP contracts license use of the software, and for years the open question was whether a person using a connected non-SAP application was using SAP and therefore needed a license. Buyers and SAP read the same clauses differently, and the gap produced some of the most public licensing disputes in the enterprise software market.
The user-based view created a counting problem. If every external customer placing an order through a web shop needed a named user, the math was impossible, and the licensing did not reflect how modern systems actually connect. SAP responded by reframing the question around output rather than people. Instead of counting who used SAP, it would count what the use produced, which is the document.
That history matters for buyers because it explains why the document model is presented as a simplification. It is simpler to measure, but it does not automatically cost less. The model resolves the counting argument while leaving the commercial question wide open. The price per document and the volume are still negotiated, and that is where a prepared buyer makes the difference.
ECC versus S/4HANA: the timing that decides exposure
Most large estates still run on a mix of SAP ECC and S/4HANA, and the licensing question differs by where you sit. Under older ECC agreements, indirect use was often governed by named user terms and years of accumulated interpretation. The exposure was real but ambiguous, and many estates carried it without ever pricing it.
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 to be settled at conversion.
The buyers who manage this well separate the two decisions. They size indirect access on its own facts, then decide the timing of an S/4HANA move with that number in view rather than discovering it mid-conversion. Letting the technical project set the licensing timeline hands SAP the stronger position, because the pressure to complete the migration competes with the patience a fair document negotiation requires.
Common mistakes that raise the bill
The same avoidable errors recur across indirect access discussions. Knowing them in advance is the cheapest protection a buyer has.
| 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 |
Negotiating 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.
Building an integration map that holds up
The integration map is the evidence behind every number you present, so build it as a durable record rather than a one-off spreadsheet. List each non-SAP system that connects to SAP, the technical or service account it uses, the document types it creates, and the annual volume drawn from your own transaction history. Date each entry and tie it to the system owner who can confirm it.
Pay particular attention to the accounts that look like a single user but represent a whole external system. A middleware service account, an e-commerce connector, or an automation identity can each carry the document load of thousands of external interactions. These are the entries SAP will focus on, so they are the entries your map must document most carefully.
Keep the map current as the estate changes. A new integration, a migrated interface, or an automation rollout each shifts the document footprint, and a map that is twelve months stale is a weak foundation in a negotiation. Treat it as a living register owned by one team, the same discipline that keeps any compliance position defensible over time.
Where you can, attach the underlying query or report that produced each volume figure. A document count that points back to a named transaction report is far harder to dispute than a round number in a cell, and that traceability is what turns a spreadsheet into evidence SAP cannot easily wave away.
After the deal: keeping the count current
Settling the document model is not the end of the work. Digital access exposure grows with the business, so the position you negotiate needs maintenance to stay accurate and affordable. The contract terms you fixed for unit price and growth only protect you if you track the volumes they govern.
Set a regular internal review of document creation by integration, especially after any change to the connected systems. A quarterly check against your own counts catches growth before it becomes a true-up surprise and confirms that the no-double-counting rule is holding in practice. The estates that avoid indirect access shocks are the ones that measure continuously rather than once a contract cycle.
Record the agreed metric, the per-document price, and the measurement method where the next contract owner can find them. Account teams change and institutional memory fades, and a clear record of what was agreed protects the terms you worked to secure. The cost of indirect access is controllable, but only for the buyer who keeps counting after the ink dries.
What good looks like
A well-run indirect access position ends with every integration mapped, the document footprint sized on your own numbers, the metric and price fixed in the contract, and no retroactive exposure left open. Across more than 500 enterprise engagements, buyers we advise have negotiated over $2.4 billion in software contracts, with average savings of 38 percent, by setting the terms on measured facts rather than vendor assertions.
The buyers who do worst discover digital access for the first time in an SAP measurement. The buyers who do best size it years ahead, adopt the model on their own count, and treat the S/4HANA conversion as the moment to lock the terms.
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.