SAP Digital Access is the licensing model SAP uses to charge for indirect use: documents created in your SAP system by other systems, rather than by people logging in. It prices nine defined document types, counted when they are created. On most modern Bills of Material it appears as a single line with a very large number on it, and that number is usually an estimate.
That last part is why it deserves scrutiny. A Digital Access line commits you to a document volume for years. If the estimate behind it is generous, you pay for documents that are never created. If it is tight, you carry true-up risk the first time an integration scales. Either way, the question is the same one we ask of every line on a Bill of Material: what is the stated basis, and does it reconcile to something you own?
What Digital Access actually covers
Named-user licences cover humans. Digital Access covers everything else that touches your SAP system: the e-commerce platform that creates sales orders, the supplier portal that posts purchase documents, the warehouse automation that generates material movements, the middleware that turns API calls into invoices.
Instead of trying to count the external users behind those systems, which was the source of years of indirect-access disputes, the model counts outcomes. When a third-party system causes one of nine document types to be created in SAP, that document counts. It counts once, at creation. Reading, updating or deleting it later does not create new charges, and some document types carry fractional weightings rather than a full count.
In principle this is a cleaner model than the user-based arguments it replaced. In practice, everything depends on the quantity.
How the number on your proposal was made
A Digital Access quantity arrives on a proposal in one of three ways:
- Measured. SAP provides estimation and measurement tooling that counts digital documents in your existing system. If your proposal quantity traces to a measurement note from your own landscape, it has a basis you can test.
- Modelled. An estimate built from assumptions about your integrations and volumes, often during a RISE or S/4HANA commercial process. The assumptions may be reasonable. They are still assumptions, and they are rarely written down on the proposal itself.
- Inherited. A figure carried over from an earlier negotiation round or a different deal construct, which nobody can trace anymore.
Only the first of these reconciles to a client-owned data source. In our reviews, it is also the least common.
The four things to test before signature
1. Is a basis stated at all?
The proposal should say how the document count was derived: from which measurement, over what period, with what growth assumption. If no basis is stated, that is a finding on its own. You cannot negotiate a number that has no stated origin; you can only haggle with it.
2. Does the basis reconcile to your own data?
Run the measurement in your own landscape, or have your basis team extract document-creation volumes from the systems that integrate with SAP. The test is simple: does the proposed annual quantity sit within sight of what your estate actually creates today, plus a growth rate you believe?
3. Does the quantity match your architecture, and its timing?
Digital Access volume follows integrations. If the rollout plan says the e-commerce integration goes live in year three, a document volume priced from day one is billing ahead of use. The reverse is more dangerous: an architecture that creates documents through a channel nobody mapped to the Digital Access line, discovered at audit rather than at signature.
4. What do the contract mechanics say about growth?
Document volumes grow. The clauses that matter are the ones that govern what happens when they do: how overage is measured and priced, whether unused volume carries value, and what rights you have to restructure the position at renewal. A good unit price with bad growth mechanics is not a good deal; it is a deferred one.
On our governance platform, a Digital Access line is treated like any other: the quantity must carry a stated basis, the basis must cite a document on file, and the exposure if the estimate is wrong is stated as a range, in both directions. If the register says the signed Digital Access agreement has been requested but not received, the register keeps saying so until the paper arrives.
Common questions
What is SAP Digital Access?
SAP Digital Access is SAP's licensing model for indirect use: when third-party applications, bots, or integrations create documents in an SAP system without a human logging in. Instead of licensing those external users, SAP charges for the documents their systems create, across nine defined document types.
How are Digital Access documents counted?
A document is counted once, when it is first created in the SAP system by indirect access. Subsequent reads, updates and deletes of that document do not create additional charges, and some document types carry fractional weightings. The quantity on a proposal is usually an annual estimate of documents created.
Do we need Digital Access if our users are already licensed?
Named-user licences cover humans logging in. Digital Access covers systems: e-commerce platforms, supplier portals, warehouse automation and middleware that create documents in SAP. Most modern estates need both, which is why the right question is not whether the line belongs on the Bill of Material, but whether its quantity has a stated, testable basis.
The short version
Digital Access is a reasonable model priced on an estimate. Treat the estimate as a claim to be tested, not a given. Ask for the stated basis, reconcile it to your own volumes, map it to your rollout timing, and read the growth mechanics before anyone signs. If the line on your Bill of Material cannot answer those four questions, it is not ready for signature.