SAP digital access prices documents, not users. The model traces back to the Diageo judgment. Read the mechanics, the weighting, and the buyer moves before the next SAP measurement.
SAP digital access prices nine document types created in the SAP core by outside systems. Weighting varies, the rules trace back to the Diageo judgment, and the exposure hides in integrations. This guide maps the document types, the weighting, the history, and the buyer moves that contain it.
Indirect access has been the most contested area of SAP licensing for a decade. The dispute is simple to state. A third party system uses SAP data or function without its own SAP license. SAP wants to be paid for that use.
The 2018 digital access model reframed the charge around documents. To understand why the model exists, start with the case that forced the change.
The Diageo judgment turned indirect access from a theory into a number. It put a court endorsed price on the exposure.
In SAP UK Ltd v Diageo Great Britain Ltd, the English court found that Diageo systems calling SAP through a Salesforce front end required SAP licenses. The exposure ran into the tens of millions of pounds.
The ruling proved that named user terms could capture indirect use. Every large SAP buyer reread its contract. SAP responded with the document model to offer a clearer alternative.
SAP launched the Digital Access Adoption Program to ease the transition. It discounted measured conversion volume heavily so buyers could move off the user based exposure.
Digital access scope covers nine document types. They do not carry equal weight, and SAP sets out the categories in its software use rights material.
Document weighting and where the volume comes from
| Type | Weight | Common source system |
|---|---|---|
| Sales | Full | Ecommerce, CRM, EDI |
| Invoice | Full | Billing engines |
| Purchase | Full | Procurement portals |
| Manufacturing | Reduced | MES and IoT |
| Time and material | Reduced | Workforce and logistics |
You cannot price indirect access without an integration map. The map is the first deliverable in every defense.
List every system that writes documents into SAP. Ecommerce, EDI, supplier portals, and bots sit here. These drive most chargeable volume.
Record systems that only read SAP data. Read only access can still raise questions, so document the data flow direction for each link.
The common advice is to treat digital access as a pure compliance problem and to convert quickly to remove the risk. We disagree. In our mappings, the document model is a commercial lever, not just a compliance fix. SAP account teams open with the broadest possible reading of the Diageo precedent and the widest document count. In roughly half the negotiations we saw, that opening count fell by 30 to 50 percent once we produced a complete integration map and challenged the included records. The buyer side move is to map first, contest the count, and convert only on a number you have verified line by line.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Diageo did not invent indirect access. It put a number on it. Since then every SAP integration is a licensing question, and the buyer who maps it owns the answer.
Eleven moves recur in well managed SAP estates. The order matters.
Digital access is the SAP licensing model that charges for documents created in the SAP core by non SAP systems. It replaced the older approach of licensing each external user or device behind an integration.
The Diageo case was a 2017 English court judgment that found third party systems calling SAP required SAP licenses. It put a court endorsed price on indirect access and pushed SAP to launch the document model.
Nine document types fall inside digital access scope. Sales, invoice, purchase, service, and maintenance carry full weight, while manufacturing, quality, time, and material carry a reduced multiplier.
Weighting matters because the document mix changes the bill. Shifting volume into reduced weight types, or proving records belong there, lowers the chargeable total without changing the underlying business activity.
It was an SAP offer that discounted measured conversion volume so buyers could move from user based indirect exposure to the document model. It rewarded buyers who measured and converted during the transition window.
Integration mapping is important because you cannot price what you have not mapped. A complete map of inbound and outbound links sets the true scope and prevents the vendor count from going unchallenged.
Read only access can still raise questions, so it must be documented. Pure read only links often fall outside the chargeable document definition, but the data flow direction has to be recorded to make that case.
Convert only after a full integration map and an independent count. Conversion can be the cheaper path, but converting on the vendor opening number locks in volume that a clean map would have removed.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Indirect access is not solved by a clause. It is solved by a map. The buyer who maps the estate sets the terms of the conversation.
