SAP indirect access, resolved. A tech firm case study.

A global technology firm cut its SAP indirect access exposure by 40 percent in six months through document classification, a disciplined digital access adoption, and a renewal that locked the protection in.

What triggered the SAP indirect access audit?

SAP raised an indirect access audit against the firm's integration document flow, opening from the position that every document created through the 40 third party integrations fell inside licensable scope. The estate made that an expensive assumption: 18 million integration documents a year against an S/4HANA core with 3,000 active users.

The exposure calculation reached a material seven figure number. The client engaged buyer side advisory within days of the notice, which preserved the full six month response window.

Why does the default audit position overcount?

The default position counts every document a connected system touches, including reads, duplicates, and documents that never trigger a licensable event. SAP's own digital access model, documented through the SAP Support Portal, licenses nine defined document types, which is exactly where the defense begins.

How did document classification cut the claimed exposure?

Classification mapped the 18 million annual documents against the nine document types in SAP's digital access model and removed everything that did not create a licensable document. The claimed exposure fell 40 percent before any commercial conversation. SAP publishes the framework and its agreements through the SAP agreements library.

1. Inventory every integration and its document flows at the interface level.
2. Map each flow to the digital access document types, separating creates from reads.
3. Remove duplicate counting where one business event generated multiple technical documents.
4. Quantify the corrected document baseline with evidence the auditor could verify.

What fell out of the count?

Read only traffic, technical duplicates, and documents created by licensed named users working through middleware fell out. Each category was defensible under the framework, which is why the corrected baseline held through negotiation.

Why did digital access beat named user licensing here?

Document based digital access priced the corrected flow far below what equivalent named user licensing implied, because the integrations created high volumes from few logical actors. The estate's economics matched the model SAP describes for S/4HANA integration scenarios.

Adoption program mechanics mattered, and SAP describes the commercial model across its ERP portfolio pages. Crediting and discount structures for moving to digital access reduced the net cost of the protective position substantially.

• Volume fit: high document volume from few actors favors document pricing.
• Predictability: a measured document baseline beats estimating future named users.
• Audit closure: adopting the framework closed the contested theory, not just the number.

When would named user licensing have won?

Named user licensing wins when integrations act for identifiable humans who already hold appropriate licenses. About a third of the firm's flows fell there, and classifying them out of document scope was part of the 40 percent reduction.

What sealed the resolution at the renewal table?

The resolution closed inside the renewal rather than as a standalone settlement, trading committed spend SAP wanted against the protective scope the client needed. The indirect access matter closed without a material penalty payment, and the renewal paper carried the document license scope, growth headroom, and clarified definitions.

• Scope language: the order form named the document types and the measurement method.
• Headroom: document volume growth bands prevented an immediate repeat exposure.
• Definitions: integration patterns in use were described, removing the ambiguity the audit exploited.

What did the six month timeline look like?

Months one and two built the classification evidence. Months three and four corrected the baseline with the auditor. Months five and six negotiated the commercial close inside the renewal. Starting at the notice date is what made the sequence possible.

Where the common advice on SAP indirect access is wrong

The standard advice when the audit letter lands is to negotiate a digital access purchase quickly and make the problem go away. We disagree. In roughly 15 of the 20 plus SAP indirect access matters Fredrik Filipsson advised in 2024 to 2025, the audit document count collapsed 25 to 45 percent under disciplined classification, and in this engagement the claimed exposure fell 40 percent before a single license was priced. The buyer side move is to classify first, buy second, and fold the close into the renewal where SAP has something to gain. Paying the opening number is not resolution; it is tuition.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Inventory every third party integration and its document flows now, before any audit.
2. Map flows to the digital access document types and separate creates from reads.
3. Quantify your corrected document baseline and archive the evidence.
4. Model digital access against named user licensing on the corrected numbers.
5. Identify your next renewal event as the commercial close point.
6. Engage buyer side advisory at the audit notice, not after the first findings.

White Paper · SAP

SAP indirect access. The digital access framework

Read it free.

Read the white paper

Frequently asked questions

What result did this SAP indirect access engagement deliver?

The claimed indirect access exposure fell 40 percent in six months and the matter closed without a material penalty payment. Classification, digital access adoption, and a renewal based close delivered the outcome.

How big was the SAP estate in this case study?

The estate ran S/4HANA core with 3,000 active users, 40 third party integrations, and roughly 18 million integration documents per year. The audit position initially counted the full document flow as licensable.

What is document classification in an indirect access defense?

Classification maps every integration document flow against the nine document types in SAP's digital access model, removing reads, duplicates, and flows covered by licensed named users. It is the step that corrects the inflated audit count.

Why resolve indirect access inside a renewal?

A renewal gives SAP commercial upside to trade against protective terms, which standalone settlements lack. In our engagement file, renewal based closes were consistently faster and cheaper than isolated settlements.

Does adopting digital access always make sense?

No. Document pricing wins when high volumes come from few logical actors; named user licensing wins when integrations act for already licensed humans. The corrected baseline decides, which is why classification comes first.

How fast must you respond to an indirect access audit notice?

Engage within days. The six month sequence in this case, classification, baseline correction, then commercial close, only fits if the work starts at the notice date rather than after the auditor's first findings.