SAP Digital Access audit defense. How to respond, and how to cut the document count.

SAP Digital Access charges for documents that other systems create in SAP, so the bill follows a count you can check. An estimation note built before SAP fixes the number turns an opening demand into a figure you can defend.

When SAP raises Digital Access in an audit, the number on the table is a document count, and a document count can be checked line by line. Our advice is to build your own estimate from the integration architecture before SAP's figure hardens into the basis for a settlement or a conversion quote.

This page covers the audit response. For the licensing model itself, read the SAP Digital Access complete guide. For why indirect use leads findings this cycle, see SAP audit trends for 2026. The wider library sits in the SAP knowledge hub.

What is SAP Digital Access, and why does it drive audits?

SAP Digital Access is SAP's per document model for indirect use. It charges when a non SAP system creates a document in SAP, such as a webshop writing a sales order or a field service app opening a service ticket. SAP introduced it in April 2018 through the SAP Digital Access announcement.

Why does it sit at the center of SAP audits?

Almost every SAP customer has third party systems writing into the digital core: CRM, ecommerce, EDI, warehouse and field service tools. Because Digital Access turns that traffic into a countable charge, it has become the largest single exposure in most of the SAP audits we defend.

How does the model differ from the old user based view?

Before 2018, SAP licensed indirect access by named user. Every person behind an external system could, in theory, need an SAP license, and the scope was ambiguous and fought over. The SAP software use rights now describe a per document charge across 9 document types.

The change made the charge easier to count and easier for SAP to assert at scale. It also means you can test SAP's figure document by document, which a named user claim never allowed.

How does SAP count chargeable documents in an audit?

SAP counts the initial creation of a document in SAP when that creation starts outside SAP. Five of the nine types count per line item, and two of those five (financial and material documents) carry a 0.2 multiplier. The other seven types count at full weight.

Which document types carry which weight?

Read the last column as your audit checklist. Sales and service documents usually drive the estimate, so that is where the defense starts. A type that none of your interfaces can create should not appear in SAP's figure at all.

Is each document counted only once?

Yes. Only the initial creation is chargeable. Reads, updates and deletes add nothing, and documents that SAP derives inside SAP from an external document are not charged separately. An external sales order that triggers a delivery and an invoice inside SAP counts once, as the order.

Most of a Digital Access defense rests on that one rule. When an estimate charges a follow on invoice as if an external system created it, you remove it with the document flow as evidence.

What have we seen in Digital Access audits in 2024 and 2025?

We ran roughly 30 to 40 SAP Digital Access engagements in 2024 and 2025. On average, SAP's first estimate was 2 to 5 times the figure the customer could defend once we had mapped the real document flows. Three patterns came up again and again.

Across the same files, the median reduction we secured on SAP's estimate was 38 percent, and the typical gap between the first estimate and the defended count was 3 times. They are separate measures. The gap compares SAP's figure with the count our evidence supported, and the 38 percent is what came off SAP's figure in the agreed outcome.

How should you respond when SAP raises Digital Access in an audit?

Respond with your own estimate before SAP fixes the count. Whether it arrives in an audit report, a conversion proposal or a RISE with SAP quote, SAP's first estimate is an opening position. Acknowledge the request, agree the measurement scope in writing, and hold back any figure until your own count is ready.

What does a defended response involve?

1. Estimate independently. Build your own document count from the integration architecture, using SAP's tool output as one input among several.
2. Reconcile. Match the count to the integration map and find every duplicate creation path.
3. Challenge. Strip out reads, updates and follow on documents that were counted as initial creation.
4. Submit a defended figure. Present the reconciled number with the evidence behind each adjustment.

If the Digital Access question is part of a wider audit, our SAP License Audit Survival Guide covers the named user and LAW report side. The SAP license audit process page walks through each phase.

What will the SAP team say, and what should you say back?

• "The estimation tool output is your number." Ask for the document level extract behind it. Agree the count only after duplicates, follow on documents and SAP to SAP flows have been separated out.
• "The Adoption Program discount is only on the table this quarter." Ask for the offer in writing with the volume left open. SAP has extended the program past its published end dates before, and a deadline set by SAP's quarter should not decide your document count.
• "RISE will take care of indirect access." Ask where Digital Access sits in the RISE order form and which document volume the quote assumes.
• "Settling now avoids a larger compliance finding." Ask SAP to state the claimed exposure in writing, by document type and source system. You cannot assess a figure without its basis.

Should you take the Digital Access Adoption Program?

The SAP Digital Access Adoption Program offers a discounted route from a per user indirect position into the per document model. SAP's published terms give two options, and both are sized on your current estimated document volume.

• Option A. License at least 115 percent of current estimated volume and pay a license fee only for the 15 percent growth. In effect you pay 15 percent of list on current volume and get 15 percent headroom.
• Option B. License 100 percent of current estimated volume at a 90 percent discount, which works out to 10 percent of list with no headroom.

Both options price off the estimate, so an inflated estimate inflates what you license and the base for any later growth. Once the count is settled, Option A is the cheaper choice if you expect growth above 5 percent that you would otherwise buy at list.

SAP's program terms cover SAP ERP and SAP S/4HANA, and they exclude SAP S/4HANA Cloud. Our Adoption Program guide compares the two in detail.

How do you check your own document count before SAP does?

Start from your own systems and treat SAP's output as a figure to test. These sources give a count both sides can verify:

• SAP's estimation tool. SAP delivers it through SAP Note 2644139 for ECC and SAP Note 2644172 for S/4HANA. Run it yourself so you see the same raw output SAP sees.
• IDoc and interface monitors. Transaction WE02 shows IDoc volume by message type, and SXMB_MONI does the same for SAP PI and PO messages. Middleware logs fill the gaps for API traffic.
• Technical users. Review communication and system users in SU01 or SUIM. A technical user shared by an external interface and an internal batch job pulls internal work into the indirect count.
• SAP Passport. Check that your SAP systems pass the Passport identifier on calls to each other. Where it is missing, SAP to SAP documents can be logged as if an external system created them.
• Document flow. Use the document flow on sales orders and invoices to prove which documents SAP derived internally from one external original.

The Digital Access measurement tools guide covers how to read the tool output against these sources.

What does a defended estimate look like in numbers?

A defended estimate is SAP's gross figure minus every adjustment you can prove with your own logs. Say a hypothetical distributor receives an SAP estimate of 6,000,000 chargeable documents a year, after weighting. It runs a webshop, order management middleware, EDI invoicing, a posting engine and a licensed SAP warehouse system.

The defended count of 1,600,000 is 27 percent of SAP's figure, so the first estimate was about 3.75 times the defended one. The duplicate path alone removed 25 percent of the counted volume. An adjustment without logs or document flow behind it will not survive SAP's review, so collect the evidence as you go.

How do you reduce Digital Access exposure before an audit?

Exposure falls when the document count falls, so change the integrations that create the documents. Each change should leave evidence behind, because SAP will measure again.

Which changes cut the count?

• Remove duplicate paths. Find cases where two integrations create the same document, and switch one of them off.
• Consolidate integrations. Route document creation through fewer, cleaner interfaces, each with its own technical user.
• Batch creation where it cuts the count. Create documents in batches where the process allows, rather than one per transaction. A daily summary posting in place of one financial posting per sale reduces line items. Grouping the same sales lines under fewer order headers does not, because sales documents count per line item.

Why we would not settle on the estimation tool figure

A common recommendation is to run SAP's estimation tool, accept the figure it returns and take the Adoption Program discount to close the indirect access question. We disagree.

In our engagements the tool counted gross document creation, including duplicate paths, downstream documents and integration artifacts, so its figure overstated the chargeable volume by a wide margin. A discount applied to an inflated count still charges you for documents your systems never created. Build the independent estimate first, then weigh the program against a number you trust.

Digital Access follows a countable quantity, and a countable quantity can be tested. SAP's first estimate is its opening bid.

What does a Digital Access estimation note include?

The estimation note is the document that holds your defense together. It records the count and the reasoning behind every reduction, so SAP's reviewers can follow each step.

What goes into the note?

• Integration inventory. Every system that creates documents in SAP, and the interface and technical user it uses.
• Document mapping. Which document type each integration creates, and at what yearly volume.
• Duplication analysis. Where the same document is created by more than one path.
• Defended count. The reconciled chargeable figure, with the evidence for each adjustment.

Which terms should the settlement include?

• The counting method. Initial creation only, follow on documents excluded, replays removed. This stops the next measurement from reopening the same argument.
• A named SAP to SAP exclusion. List your licensed SAP systems by name, so documents they send stay out of the count however a tool tags them.
• A read boundary. Reporting and data extraction create no documents. Write that down so a later audit team cannot treat read traffic as creation.
• A release for past use. The settlement or conversion should close indirect use claims for all prior periods.
• Price for growth. Additional document blocks at the same net rate for the contract term, so growth is not priced at list.

Our guide to negotiating SAP license audit settlements covers how these terms fit the wider settlement.

Does moving to RISE with SAP remove Digital Access exposure?

No. Digital Access applies inside RISE as well. A RISE conversion often uses the Digital Access estimate as part of the credit calculation, so an overstated estimate flows into the price of the new contract. Defend the estimate before the conversion is priced.

If you are weighing both, settle the Adoption Program question before you sign RISE, or write into the RISE contract how your existing Digital Access licenses carry over. Our note on Digital Access in S/4HANA and RISE contracts covers the cloud side.

What to do next

1. Build the integration inventory. List every system that creates documents in SAP, with its interface and technical user.
2. Map volumes to document types. Record which type each integration creates and how many per year.
3. Remove duplicate creation paths. Switch off the second path and keep the evidence.
4. Write the estimation note first. Complete your own count before you request or accept an SAP estimate.
5. Reconcile and challenge. Compare SAP's figure with your defended count, and contest each gap with evidence.
6. Price the Adoption Program last. Weigh both options only against a number you have defended.
7. Get independent help before you accept a figure. Our independent SAP advisory team builds the note with you, and Vendor Shield subscribers get Digital Access defense as part of the service.

Frequently asked questions