SAP digital access document explained.

A plain language explainer on the SAP digital access document model. The nine document types, how each one is counted and how to control the cost before it lands in a true up.

SAP digital access is the licensing model that priced indirect usage by documents instead of by named users.

It was announced in 2018, refined repeatedly, and is now the default treatment for indirect usage on most modern SAP estates.

This page explains the document model in plain language and lays out the moves buyers run to keep digital access cost under control.

What a digital access document actually is

Documents, not users

Under digital access SAP counts documents created in S/4HANA or ECC by non SAP systems.

An indirect named user is no longer the counting unit. The document is.

Who counts the documents

• SAP measurement engine runs the counts inside your S/4HANA or ECC system.
• Customer ITAM validates each run before submission.
• Sourcing negotiates the band and the unit price at renewal.

The nine document types and their weights

Document types that move the bill

• Sales document covers sales orders and quotations created from a connected channel.
• Invoice document covers AR and AP invoices generated from non SAP systems.
• Purchase document covers POs and contracts initiated from procurement front ends.
• Service and maintenance document covers service notifications and maintenance orders.

Document types that count less

• Manufacturing document covers production orders and confirmations.
• Material document covers goods movements outside the four primary types.
• Financial document covers accounting entries not already counted.
• Time management document covers HR time entries from non SAP systems.
• Quality document covers inspection lots created externally.

Digital access is a counting model. The buyer who validates the count is the buyer who controls the bill.

How pricing actually works in practice

Weighting matters more than total count

Each document type carries a weighting factor. The high weight types drive most of the cost.

Volume alone is not enough. Mix and weighting decide the bill.

Adoption credit

Customers moving from a named user indirect setup can claim an adoption credit.

The credit can offset the digital access bill for an initial term. The size depends on the prior indirect license footprint.

Banding and fixed price options

• Most enterprise deals price digital access in volume bands rather than purely per document.
• Negotiate a fixed price band that covers expected growth.
• Reset the band at each renewal based on measured usage.

Buyer side moves at the next renewal

Validate the measurement first

• Run the measurement in test before submitting any production run.
• Tag each connected system with the expected document flow.
• Reconcile the count to your operational data before discussion.

Fix the band in the order form

Move from open ended per document pricing to a fixed band that covers growth.

Add a true down right at each anniversary so the band can shrink as automation matures.

Suggested reading

• SAP Digital Access Advisory Service. Cross vendor reading from the wider library.
• Digital Access Impact. Cross vendor reading from the wider library.
• SAP RISE Negotiation Guide. Cross vendor reading from the wider library.

What to do next

1. Inventory every connected non SAP system that creates documents in S/4HANA or ECC.
2. Run the digital access measurement engine in a test client first.
3. Reconcile the document count to your operational data before any seller discussion.
4. Decide whether to claim the adoption credit and model the size.
5. Negotiate a fixed band that covers expected growth for the renewal term.
6. Add a true down right at each anniversary inside the order form.
7. Brief finance and the SAP architect together so the band reflects business plan growth.

Frequently asked questions

Is digital access mandatory?

No. Customers can keep the prior indirect named user model for their existing footprint. Most new deals use the document model because it priced better at most volume bands.

How many document types count?

Nine in total. Four drive most of the cost. Five carry a reduced weighting and rarely change the answer alone.

Can the count be challenged?

Yes. The measurement engine runs against your system but the count is yours to validate. We always recommend a test client run before any production submission.

What is the adoption credit?

A credit applied at the move from a named user indirect setup to the document model. It can offset the digital access bill for an initial period. The credit size depends on the prior indirect license footprint.

When should we revisit the band?

At every renewal and at any major automation event. Document volume tracks process automation. The band should not drift from real usage.