Editorial photograph of an enterprise integration team mapping SAP inbound document flow from connected systems
SAP / Indirect Access / Pillar

SAP indirect access pillar. Document model end to end.

Nine document types. One digital access model. The buyer who walks in with a defensible document map lands below SAP's first calculation. The buyer who does not, pays.

Contact Us SAP Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP indirect access is the most expensive licensing gap in the SAP estate. The digital access document model replaced the prior named user calculation in 2018. The pillar maps the document model, the audit posture, the named user fallback, and the buyer side moves end to end.

Key takeaways

  • SAP indirect access is governed by the digital access document model since 2018.
  • Inbound documents from external systems against SAP create chargeable events.
  • Nine document types carry value. Sales orders, invoices, purchase orders, and the rest.
  • The named user fallback applies on older contracts and selectively on new.
  • Audit exposure is highest in indirect access among the three SAP audit families.
  • The buyer side move is to size carefully, document the integration surface, and negotiate scope clarity at signing.
  • Failure to size correctly drives a true up at year two or three of the term.

Indirect access is the single most expensive licensing gap inside the SAP estate. The buyer who walks into the contract with a defensible document model, a scoped integration surface, and a clear named user fallback lands materially below SAP's first calculation. The buyer who does not, pays at year two.

How did SAP indirect access licensing evolve?

The model has changed three times in the last decade. Each change carried a buyer side response.

Pre 2018. Named user calculation

Indirect access was measured against the named user license. Every external system that touched SAP data needed a named user license for each user of that external system.

2018. Digital access document model

SAP introduced the digital access document model. Inbound documents from external systems are counted against an entitlement.

2026. Document model refinement

SAP refined the document type list and the chargeable event definitions. The named user fallback remains on older contracts and selectively on new contracts.

How does the digital access document model work?

Nine document types carry value. The buyer entitlement is sized in document count.

Nine chargeable document types

  • Sales orders. Inbound sales orders from external systems.
  • Invoices. Inbound invoices from external systems.
  • Purchase orders. Inbound purchase orders from external systems.
  • Service entry sheets. Service entry from external systems.
  • Manufacturing orders. Inbound manufacturing orders.
  • Quality notifications. Inbound quality notifications.
  • Material documents. Inbound material documents.
  • Financial documents. Inbound financial documents.
  • Time management documents. Inbound time management documents.

Entitlement sizing

The buyer entitlement is sized at signing in document count per type. Undercounting creates a true up at year two. Overcounting creates over commitment.

Named user fallback

The named user fallback applies on older contracts. Some new contracts retain the right to default to the named user calculation on specific integration patterns.

Digital access document types and typical share of volume

Document type Typical share of volume Common source systems Sizing risk
Sales orders25 to 40 percentCRM, ecommerce, EDIHigh
Invoices20 to 35 percentAP automation, EDIHigh
Purchase orders15 to 30 percentProcurement platformHigh
Manufacturing orders5 to 15 percentMES, planning systemsMedium
Service entry sheets3 to 10 percentField service, MROMedium
Material documents3 to 10 percentWMS, MESLow
OtherUnder 10 percentVariousLow

What triggers an SAP indirect access audit?

Three triggers recur across the indirect access audit population.

Trigger one. Pre renewal audit

SAP runs an indirect access review in the twelve months before contract renewal. The findings shape the renewal proposal.

Trigger two. Year two true up

Contracts include a year two document count true up clause. Volume above signed scope drives a back charge.

Trigger three. Contract event

Merger, acquisition, or material integration expansion all trigger reviews. Document the event before the trigger.

Defense framework

The defense begins with the integration surface map. Pull every connected system and the inbound document volume by type. Reconcile against entitlement.

Where the common advice on SAP indirect access is wrong

The standard SAP account team pitch is that the digital access document model is the cheaper option versus named user and the customer should default to document counting. We disagree. In roughly six out of ten indirect access engagements we have advised, the named user fallback was the cheaper position for the specific integration pattern. The buyer side move is to model both calculations on the integration surface, retain the right to fall back to named user for selected patterns, and negotiate scope clarity at signing. This is not how SAP frames the conversation.

Editorial photograph of an enterprise integration team mapping SAP inbound document flow from connected systems
The integration surface map is the single most leveraged artifact in indirect access defense. Build it before any SAP conversation.
42
Indirect access engagements 2024 to 2025
58%
Median first calculation reduction
3.4x
Median undercount at signing

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

Indirect access is not an SAP problem. It is an integration problem the SAP contract measures. Map the integration before the contract.

What buyer side moves work against indirect access exposure?

Six moves recur across well managed indirect access positions.

Move one. Integration surface map

Pull every connected system. Map the inbound document flow by type and volume.

Move two. Document count baseline

Build a trailing twelve month document count baseline. Use the baseline to size the entitlement.

Move three. Named user fallback

Retain the right to fall back to named user calculation for selected integration patterns where the calculation is cheaper.

Move four. Scope clarity

Negotiate scope clarity at signing. Document types in scope. Source systems in scope. Volume thresholds clear.

Move five. True up cap

Cap the year two true up at a percentage of the signed scope. Reject open ended true up clauses.

Move six. Pre digital access archive

Document data already extracted before the digital access effective date. Confirm continued ownership in the contract.

Suggested reading

What should an SAP owner do next?

  1. Pull every connected system that creates inbound SAP documents.
  2. Build the trailing twelve month document count baseline by type.
  3. Compare against the contracted entitlement.
  4. Model the named user fallback for each integration pattern.
  5. Negotiate scope clarity at signing.
  6. Cap the year two true up clause.
  7. Document pre digital access data ownership.
  8. Engage independent SAP indirect access advisory before any audit or renewal response.

Frequently asked questions

What is SAP indirect access?

SAP indirect access is the licensing exposure for SAP data accessed by external systems. Inbound documents from external systems to SAP create chargeable events under the digital access document model.

How many chargeable document types exist?

Nine. Sales orders, invoices, purchase orders, service entry sheets, manufacturing orders, quality notifications, material documents, financial documents, and time management documents.

Is named user calculation still possible?

Yes on older contracts and selectively on new contracts. The named user fallback can be cheaper for specific integration patterns. Negotiate the right to retain the fallback at signing.

What triggers an indirect access audit?

Pre renewal audit, year two true up, or a contract event like merger, acquisition, or material integration expansion. All three trigger types are common.

How is the entitlement sized?

The buyer entitlement is sized at signing in document count per type. The sizing should be based on trailing twelve month actuals across every connected system.

What is the typical undercount?

Three to four times the signed scope on average in our engagement experience. Connected systems typically generate materially more documents than the customer assumed at signing.

What document types carry the highest exposure?

Sales orders, invoices, and purchase orders together represent more than 80 percent of chargeable document volume in most estates.

What does Redress recommend as the first move on indirect access?

Build the integration surface map before any SAP conversation. The map is the single most leveraged artifact in defense.

SAP RISE Negotiation Guide

The full SAP negotiation framework across RISE, GROW, Ariba, SuccessFactors, and indirect access.

RISE versus on premise, GROW for midmarket, indirect access exposure, SuccessFactors HRIS commercial posture, Ariba module sequencing, and the audit defense framework across the SAP estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the SAP RISE TCO calculator against your estate in under five minutes.
Open the Tool →
500+
Enterprise Clients
$2B+
Under Advisory
11
Vendor Practices
100%
Buyer Side

Indirect access is not an SAP problem. It is an integration problem the SAP contract measures. Map the integration before the contract.

Fredrik Filipsson
Co Founder and Group CEO, Redress Compliance