Editorial photograph of an SAP procurement team reviewing a Digital Access document count and a buyer side conversion analysis on the boardroom screen
Article · SAP · Digital Access

Count documents. Not users.

SAP moved from named user indirect access to document based Digital Access in 2018. Eight years on, the conversion math still favors SAP. The buyer side that counts documents before SAP does controls the renewal.

Read the Article SAP Services
9Document types
2018Model launched
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP runs two indirect use models at once. Named user indirect access for legacy use, and document based Digital Access for new use. The buyer side that counts documents first controls the conversion.

Key Takeaways

What this article delivers

  • Two models coexist. Named user indirect access protects legacy contracts. Digital Access prices new indirect use by document.
  • Nine document types drive the bid. Sales, invoice, purchase, service, manufacturing, quality, time, material, and financial documents.
  • The count is buyer side work. SAP runs the count last. You run it first, or you pay the SAP number.
  • DAAP discounts closed in 2021. Bespoke conversion terms continue for documented scope.
  • Audit risk shifts, it does not vanish. Document creation source matters as much as raw volume.
  • Median recovery sits near 15 percent. Independent counting and scope tests move the number.

How did SAP move from indirect access to Digital Access?

SAP priced indirect use by named user for two decades. Disputes followed, and the SAP v Diageo judgment crystallised the risk for large estates.

SAP introduced the document based model in 2018. The SAP announcement of the document based model reframed indirect use as a count of documents, not a count of people.

What changed for the buyer

The unit of value moved from human seats to created documents. That sounds simpler. In practice it moved the audit surface into systems that most license managers do not watch.

  • Old model: count humans who touch SAP through a non SAP system.
  • New model: count documents that external systems create inside SAP.
  • Net effect: integration design now drives the license bill.

What are the nine Digital Access document types?

SAP counts nine initial document types. The SAP licensing trust center lists them as the basis for the Digital Access metric.

The nine Digital Access document types and where they originate

Document typeTypical sourceCounting risk
SalesCRM, ecommerce, EDIHigh volume, often duplicated
InvoiceBilling, EDIHigh volume
PurchaseProcurement, marketplacesMedium
ServiceField service, ticketingMedium
ManufacturingMES, shop floorHigh in process industries
FinancialBanks, treasury feedsFrequently overstated

Which document types inflate fastest

Sales, invoice, and financial documents drive most disputes. Machine generated feeds create volume that a human never sees yet a meter still counts.

How does the Digital Access conversion math work?

SAP measures created documents, applies a per document price, then offers a conversion discount. The RISE with SAP product page ties the model into RISE commercial terms.

The discount that closed

The Digital Access Adoption Program offered conversion discounts of 25 to 90 percent against list. The program closed in 2021. Bespoke conversion terms continue where scope is documented.

  • Step one: measure created documents over a defined period.
  • Step two: remove duplicates and system to system noise.
  • Step three: price the net count and bundle it into the renewal.

Where the common advice on Digital Access conversion is wrong

The standard SAP account team pitch is that Digital Access is simpler and cheaper than named user indirect access, so you should convert early. We disagree. In roughly two out of three conversions we have benchmarked, the first SAP document count ran far above the defensible number, and early conversion locked customers into that inflated baseline. The buyer side move is to run an independent count first, strip duplicate and system generated documents, and only then decide whether conversion beats keeping named user indirect access for legacy scope. Converting before you measure hands SAP the baseline that prices every future year.

SAP procurement and IT team reviewing a Digital Access document count by source system on a shared screen
Most of the priced volume hides in machine generated feeds. The count that strips them controls the bid.

What document counting traps inflate the bid?

The meter counts documents, not value. Several common patterns push the count up without adding any business benefit.

Three traps we see most

  • Duplicates: retries and reposts count more than once unless filtered.
  • System to system: internal integrations create documents that no external party requested.
  • Historical backfill: migration loads inflate the measured period.

Each trap is defensible with evidence. The customer that brings the evidence sets the count. The customer that does not pays the SAP number.

30+
SAP conversions benchmarked
15%
Median recovery on conversion
45%
Top count reduction achieved

Source: Redress Compliance advisory engagement file, 2024 to 2025.

The customer that lets SAP count the documents pays the SAP price. The buyer side that runs the count first controls the conversion. The first count wins the negotiation.

Buyer side SAP reviewer
ECC and S/4HANA conversion engagements

What buyer side moves work at renewal?

Treat Digital Access as a renewal lever, not a standalone purchase. The leverage is highest when the document price sits inside a wider commercial discussion.

Levers that move the number

  • Independent count: bring your own measurement to the table.
  • Scope tests: challenge which documents are truly indirect use.
  • Bundle: fold the conversion into a multi year renewal for a better unit price.

What to do next

  1. Map every non SAP system that creates documents inside SAP.
  2. Run an independent count for a representative period before any SAP measurement.
  3. Strip duplicates and system to system documents, and keep the evidence.
  4. Decide per scope whether Digital Access beats keeping named user indirect access.
  5. Bundle any conversion into the wider renewal, never as a standalone line.
  6. Hold the defensible count as the baseline for every future year.
  7. Review integration design before adding new external systems.

Frequently asked questions

What is the difference between indirect access and Digital Access?

Indirect access was the named user model that counted humans using non SAP systems that called SAP. Digital Access is the document based model that counts documents external systems create inside SAP. Both still exist for different scope.

When did SAP introduce Digital Access?

SAP launched Digital Access in 2018. It followed indirect use disputes and offered a document based alternative to named user indirect access licensing.

Which nine document types count for Digital Access?

Sales, invoice, purchase, service, manufacturing, quality, time management, material, and financial documents. Sales, invoice, and financial documents drive most disputes.

Does Digital Access replace named user licensing?

No. Digital Access applies to indirect use by external systems. Named user licensing still applies to humans accessing SAP through SAP GUI, Fiori, or other SAP interfaces.

What discount did the Digital Access Adoption Program offer?

The program offered conversion discounts of 25 to 90 percent against list, depending on documented exposure. It closed in 2021, though bespoke conversion terms continue.

Do all SAP customers need to convert to Digital Access?

No. Existing customers can keep named user indirect access for legacy scope. New indirect use after 2018 falls under Digital Access by default unless contracted otherwise.

What is the typical recovery on a Digital Access conversion?

Median recovery sits near 15 percent through independent counting, scope tests, and bundled commercial terms. The recovery depends on counting before SAP runs its measurement.

How does Redress engage on Digital Access?

Redress runs the document counting, the conversion math, and the negotiation inside the Vendor Shield subscription. The work spans ECC, S/4HANA, and RISE with SAP.

How Redress engages

Redress runs this work inside the Vendor Shield subscription, the Renewal Program, and the benchmarking service.

Read the SAP indirect and digital access guide, the SAP API indirect access changes briefing, the SAP services page, and the SAP knowledge hub.

Estimate your conversion exposure with the SAP RISE TCO calculator.
Open the SAP TCO Calculator →
Lead Download

Take the SAP RISE Negotiation Guide into your next review.

Pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.

More Reading

More from this practice.

Vendor Knowledge →
SAP RISE negotiation guide cover
SAP · White Paper
SAP RISE Negotiation Guide
RISE and S/4HANA commercial terms.
14 min read
SAP advisory service
SAP · Service
SAP Advisory
Buyer side advisory across SAP.
8 min read
SAP knowledge hub
SAP · Hub
SAP Knowledge Hub
ECC, S/4HANA, and contract intelligence.
9 min read
Vendor Shield subscription
Program · Subscription
Vendor Shield
Always on advisory across publishers.
7 min read
SAP renewal team reviewing a Digital Access conversion analysis

Count the documents. Control the bid.

We run SAP Digital Access conversions across ECC and S/4HANA estates. Median 15 percent recovery through independent counting, scope tests, and bundled commercial terms.

Buyer side intelligence, monthly.

Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active SAP decisions.