Guide · SAP
SAP indirect and digital access. The buyer side guide.
A walkthrough of SAP indirect and digital access for buyers. How the model works, where the count inflates, how to defend an audit, and the renewal levers that cut spend.
A walkthrough of SAP indirect and digital access for buyers. How the model works, where the count inflates, how to defend an audit, and the renewal levers that cut spend.
A buyer side walkthrough of SAP indirect and digital access. How the model works, where the count inflates, how to defend an audit, and the renewal levers that cut spend.
Indirect access is use of SAP through something that is not an SAP interface. A non SAP system reads or writes SAP data, and SAP expects a license for that use. The SAP licensing trust center sets the framework.
Buyers signed for named users and later found their integrations triggered extra license demands. The SAP v Diageo judgment showed how large the exposure could grow.
SAP counts created documents across nine types, then prices the net volume. The RISE with SAP product page links the count to RISE terms.
How the nine document types map to risk
| Document type | Where it comes from | Inflation risk |
|---|---|---|
| Sales | Ecommerce, EDI, CRM | High |
| Invoice | Billing engines | High |
| Financial | Bank and treasury feeds | High |
| Purchase | Procurement tools | Medium |
| Service | Field and ticketing | Medium |
| Material | Warehouse and logistics | Low to medium |
SAP measures over a defined period. A migration backfill or a peak trading month can distort that window. The SAP announcement of the document based model framed this document based model when it launched.
Conversion is a decision, not a default. It can simplify licensing, but only if the baseline count is defensible.
The standard advice from SAP and many partners is that every customer should convert to Digital Access because it is the future model. We disagree. In roughly two out of three reviews, the SAP first count was high enough that converting on that number cost more than keeping named user indirect access for legacy scope. The buyer side move is to split the estate, convert only the scope where the defensible document count is genuinely cheaper, and hold legacy named user rights where they price better. A model is not cheaper just because it is newer. The count decides, not the label.
Defense starts before the notice arrives. Know your integrations and hold your own count.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Audit defense is not an argument about price. It is an argument about what counts. Win the definition of a countable document and the price follows.
Indirect access is most negotiable at renewal, when SAP wants the wider commitment. Use that moment.
Indirect access is use of SAP data through a non SAP system rather than an SAP interface. SAP expects a license for that use, priced either by named user or by Digital Access documents.
Indirect access is the named user model. Digital Access is the document based model introduced in 2018. They cover the same activity but price it differently.
SAP measures created documents across nine types over a defined period, removes nothing by default, and prices the volume. The buyer should strip duplicates and system noise first.
No. Convert only the scope where the defensible document count is cheaper than named user rights. Keep legacy named user indirect access where it prices better.
Yes. SAP can request a measurement of indirect use. A defensible position needs an integration inventory and evidence of duplicate and system to system documents.
Median recovery sits near 15 percent. Independent counting and scope tests drive most of it, and bundled renewals add further unit price improvement.
At renewal, when SAP wants the wider commitment. That is when document price, conversion terms, and future caps are most negotiable.
RISE folds Digital Access into a subscription model. The counting logic is the same, so the same independent count and scope tests still apply.
Redress runs this guide as live work inside the Vendor Shield subscription and the Renewal Program.
Read the SAP indirect access vs Digital Access licensing briefing, the SAP API indirect access changes guide, the SAP services page, and the SAP knowledge hub.
Pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
We run SAP indirect and digital access reviews across ECC, S/4HANA, and RISE. Median 15 percent recovery through independent counting and bundled renewals.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active SAP decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
