Named users or document licences? A comprehensive guide to choosing the right SAP licensing model, with cost analysis, break-even scenarios, and negotiation strategies.
See also: SAP Indirect Access 2025: Rules, Costs, Risk · DAAP: How to Evaluate, Negotiate, and Avoid Cost Traps
SAP licensing is at a crossroads. Many CIOs and IT Asset Managers are wrestling with whether to stick with the traditional Indirect Access model (licensing by named users) or switch to SAP's newer Digital Access model (licensing by digital documents).
This decision has major cost and compliance implications. Choose incorrectly, and you could face either skyrocketing licensing costs or steep audit penalties down the road.
The issue comes to a head during SAP licence audits, S/4HANA migration projects, and contract renewals. SAP audits now routinely scrutinise "indirect use," scenarios where third-party systems or external users access SAP data. Companies were shocked to discover that an e-commerce website feeding orders into SAP technically meant every customer required a user licence.
To address these challenges, SAP introduced Digital Access in 2018. This model aligns licensing fees more closely with actual system usage (documents and transactions) rather than headcount. As companies connect SAP to e-commerce portals, mobile apps, IoT sensors, and more, understanding the pros, cons, and costs of each model is more critical than ever.
Under SAP's legacy Indirect Access rules, any person or system that indirectly uses SAP must be covered by a Named User licence. If a third-party application accesses SAP data or functions, SAP considers it "use" requiring a licensed user, even if the person never logs into SAP directly.
SAP offers Professional Users (full access, most expensive), Limited Professional Users, and specific External/Employee Self-Service users. Regardless of type, the model ties licences to individuals, not transactions.
The e-commerce portal example. Customers place orders on your website, and those orders flow into SAP for processing. Under traditional rules, SAP could argue each customer is an indirect user. 1,000 customers = 1,000 named user licences needed. This scenario actually happened in cases like the SAP vs. Diageo lawsuit, which brought indirect use to mainstream attention.
Over-counting. A customer placing one order per year needs the same licence as a full-time user. High cost for large audiences: does not scale to hundreds or thousands of users.
Audit risk. Interfaces like CRM, supplier portals, and IoT can create unlicensed "back doors." Indirect usage is often unnoticed until surprise back-charges during an audit.
SAP's Digital Access model ties licences to the business documents created in SAP by indirect activity, not people. SAP identified nine specific document categories that count.
| The 9 Digital Access Document Types | ||
|---|---|---|
| Sales Documents | Purchase Documents | Invoice Documents |
| Manufacturing Documents | Material Documents | Quality Management Documents |
| Service & Maintenance Documents | Financial Documents | Time Management Documents |
If an external system creates one of these documents in SAP, it counts toward your licensed volume. Documents outside these nine categories do not require a licence. Reading data or updating existing records generally does not count. Only creating new documents matters.
DAAP incentives. SAP's Digital Access Adoption Program offers up to 90% discounts on initial document licence purchases and allows trade-in of existing named-user licences for credit. As of 2025, DAAP remains available with no fixed end date, but SAP reserves the right to sunset it. Leverage these incentives while they last.
| Scenario | Indirect Access (Named Users) | Digital Access (Documents) |
|---|---|---|
| 500 external users, light usage (partner portal) | ~500 Named User licences required. Cost grows per user. Infrequent users still need full licences. | Licence document volume (e.g. ~120K sales docs/yr). With DAAP discounts, per-document cost is far lower. |
| 10,000 orders/month via e-commerce (~120K/yr) | Licensing tens of thousands of customers individually is cost-prohibitive. Very high costs. | Licence ~120K sales document creations. With negotiated rates, far more economical for high volume. |
| 3 heavy-use system integrations (thousands of docs each) | Only 3 named user licences needed. Potentially cheaper if volume per user is extreme. | Could cost more than 3 named users if document volume is very high per integration. |
Break-even logic. Digital Access is cheaper when many users each create few documents. Named users win when few users each create many documents. For large populations of occasional users (customers, IoT devices), Digital Access is dramatically cheaper. For small numbers of heavy-use system accounts, named users may cost less. Model your own data to reveal your personal break-even point.
Even if you stay with named users, ensure your SAP contracts clearly define indirect use to avoid audit surprises. It should be unambiguous that your licences cover the specific indirect scenarios in play.
Keep SAP contracts and licence entitlements organised. Compliance is much easier when you can definitively say "We are entitled to X named users and Y digital documents." Assign ongoing ownership to the IT Asset Management or SAP Basis team for continuous monitoring.
Indirect Access = pay per user (even external or system users). Digital Access = pay per document/transaction (regardless of how many users contribute). Indirect ties licences to people; Digital ties them to the nine categories of business documents created in SAP by external systems.
Sales Documents, Purchase Documents, Invoice Documents, Manufacturing Documents, Material Documents, Quality Management Documents, Service & Maintenance Documents, Financial Documents, and Time Management Documents. If an external system creates one of these in SAP, it consumes your licence capacity. Documents outside these categories do not count.
Under Indirect Access, even read-only usage technically requires a named user licence. Under Digital Access, pure read-only actions generally do not count since no new document is created. Digital Access charges for creating documents, not retrieving or viewing them. Always clarify with SAP in your contract.
Yes. SAP extended DAAP multiple times and it currently has no fixed end date. Customers can still negotiate steep discounts (often 90% off) on initial document licence purchases. SAP could sunset the programme in the future, so leverage it sooner rather than later.
Yes. Many customers transition mid-contract via amendment. However, the best time is during a renewal or larger negotiation (S/4HANA migration, periodic true-up). Mid-term, SAP will sell you Digital Access licences and incorporate DAAP discounts. Clarify how SAP treats past indirect usage once you switch.
Generally, Digital Access. Portals involve many users each doing few things. Licensing each user is prohibitively expensive, whereas licensing document transactions is efficient. IoT is similar: thousands of devices creating material or maintenance documents are far cheaper under the document model. The named user model might only win if very few users generate extreme document volumes.
SAP asks you to run measurement programmes (USMM/LAW for users, document counts for Digital Access). They send detailed questionnaires about all interfacing systems. Auditors can analyse SAP logs to see which generic/interface accounts created documents. If unlicensed usage is found, you are asked to purchase licences retroactively, often with back-dated maintenance fees.