What Is SAP Indirect Access?
SAP indirect access — officially rebranded by SAP as "Digital Access" since 2018 — refers to the licensing obligation that arises when third-party systems interact with SAP data without a human user logging into SAP directly. If your Salesforce system creates an order in SAP, or your e-commerce platform triggers a goods receipt, or an IoT device records a production confirmation — SAP may argue these interactions require additional licensing.
For the broader context of SAP commercial management, see the SAP Pricing Benchmarks overview.
The commercial significance of indirect access is substantial. SAP has pursued major litigation over indirect access, including a landmark 2017 case against Diageo (settled), and numerous other disputes. Organizations that have not audited their indirect access position carry financial exposure they may not discover until SAP raises it — at the worst possible moment in a negotiation.
Direct vs. Indirect Access: The Distinction
SAP's licensing framework is built around the assumption that every interaction with SAP data is performed by a licensed user. Direct access means a human user logs into SAP (via SAP GUI, Fiori, or other SAP interface) to perform a transaction. Indirect access means a non-SAP system (CRM, API, middleware, RPA, IoT device) performs a transaction in SAP — potentially without any human interaction at the moment of the transaction.
Audit Your Indirect Access Exposure
Before your next SAP renewal or RISE negotiation, know exactly what your indirect access exposure is — so SAP can't ambush you with their numbers.
SAP's Digital Access Model Explained
In 2018, SAP introduced the Digital Access model as a more structured approach to pricing indirect access. Instead of relying on named user licenses for every non-human interaction, Digital Access prices by document type and document volume — the number of specific document types created in SAP via indirect channels over a 12-month period.
Document Types Subject to Digital Access
| Document Type | SAP Code | Risk Level | Typical Trigger Systems |
|---|---|---|---|
| Sales Order | VA01 | High | Salesforce CPQ, e-commerce, EDI, custom portals |
| Purchase Order | ME21N | High | Ariba (non-SAP), Coupa, custom procurement systems |
| Delivery Document | VL01N | High | WMS systems, 3PL integrations, IoT triggers |
| Goods Receipt / GI | MIGO | Medium | WMS, IoT, automated production systems |
| Invoice (FI Posting) | FB60/FI | Medium | AP automation, OCR invoice processing |
| Material Master Changes | MM02 | Lower | PIM systems, product catalog integrations |
| Plant Maintenance Order | IW31 | Medium | Field service platforms, IoT predictive maintenance |
| Production Order | CO01 | Medium | MES systems, automated production scheduling |
Digital Access Benchmark Pricing
SAP's list pricing for Digital Access is published in their price list, but organizations that accept list pricing are significantly overpaying. Our benchmark data from 60+ indirect access negotiations and settlements shows that negotiated rates are 40–60% below SAP's list in the majority of cases.
Document Type Pricing: List vs. Benchmark Negotiated
| Document Type | SAP List Price (Per 1K Docs/Year) | Median Negotiated (Per 1K) | Best-in-Class (Per 1K) |
|---|---|---|---|
| Sales Order | $420–$580 | $210–$290 | $140–$200 |
| Purchase Order | $360–$520 | $180–$260 | $120–$180 |
| Delivery Document | $280–$420 | $140–$210 | $95–$150 |
| Goods Receipt | $240–$360 | $120–$180 | $80–$130 |
| FI Posting (Invoice) | $220–$320 | $110–$160 | $75–$120 |
| Plant Maintenance Order | $260–$400 | $130–$200 | $85–$140 |
| Production Order | $300–$440 | $150–$220 | $100–$160 |
"SAP came to us with a $4.2M indirect access claim during our renewal negotiation. We had audited our document volumes ourselves three months earlier and knew exactly what our exposure was. We settled at $1.1M. The difference was preparation — and benchmark data showing what comparable organizations had settled at."
Real-World Indirect Access Exposure Scenarios
To illustrate the financial scale of indirect access exposure, the following scenarios are based on actual deal data from our benchmark database (all figures anonymized):
Scenario A: Manufacturer with Salesforce CPQ
A manufacturing company with $800M revenue uses Salesforce CPQ to configure and quote products. CPQ creates sales orders directly in SAP via an API integration. Annual document volumes: 420,000 sales orders, 380,000 delivery notes.
- SAP list pricing exposure: $420K/year (sales orders) + $308K/year (delivery) = $728K/year
- Median negotiated settlement: $364K/year
- Best-in-class outcome (benchmark data leverage): $240K/year
- Annual saving from benchmark-based negotiation vs. list: $488K
Scenario B: Retailer with E-commerce Integration
A retail group processes 2.1 million consumer orders per year through its e-commerce platform, which creates SAP sales orders, delivery documents, and financial postings automatically.
- SAP list pricing exposure: $2.8M–$4.0M/year across document types
- Median negotiated settlement: $1.4M–$2.0M/year
- Best-in-class outcome: $900K–$1.4M/year
- Annual saving vs. list: $1.4M–$2.6M
Quantify Your Indirect Access Exposure
Know your numbers before SAP does. We'll help you audit document volumes, map integration points, and calculate your exposure at list and negotiated rates.
How SAP Identifies and Pursues Indirect Access Claims
SAP's mechanism for identifying indirect access exposure has evolved. The primary vectors through which SAP discovers potential indirect access situations are SAP audit programs (License Audit and LAW tool reports), RISE migration assessments (SAP uses the S/4HANA readiness assessment to identify indirect access), renewal negotiation conversations (SAP sales teams may raise indirect access claims during renewal discussions to create settlement urgency), and voluntary disclosure encouraged during "Digital Access Adoption" programs.
SAP's Digital Access Adoption Program
SAP has offered a "Digital Access Adoption" program that provides legacy customers with a pathway to move to the new model, often with a degree of amnesty for historical underpayment. Organizations that participate proactively typically achieve 35–50% better settlement terms than those responding to an audit-triggered claim. The program has windows — it is not available continuously — and terms vary by market and SAP relationship tier.
Proactive Indirect Access Management
The organizations that manage indirect access most effectively do so proactively rather than reactively. A proactive indirect access management program involves:
- Integration mapping: Catalog every non-SAP system that has an API, RFC, BAPI, or other programmatic connection to your SAP systems. Include both inbound (writing to SAP) and outbound (reading from SAP) connections.
- Document volume measurement: Use SAP's built-in reporting (transaction SLSC or equivalent) to measure actual document volumes created via indirect channels over the past 12 months.
- Exposure calculation: Apply both list and negotiated benchmark pricing to calculate your current exposure range.
- Risk prioritization: Not all indirect access is equally likely to trigger an SAP claim. Prioritize high-volume, high-risk document types (sales orders, purchase orders, delivery documents) for remediation or contractual settlement.
- Incorporate into renewal strategy: Bundle indirect access settlement into broader SAP renewal or RISE migration negotiations — where you have maximum leverage — rather than addressing it in isolation.
- Never accept SAP's initial indirect access claim without independent verification of document volumes
- Benchmark negotiated settlements in your industry before committing to a settlement value
- Use indirect access resolution as a component of a broader SAP commercial negotiation — not as a standalone transaction
- Retroactive claims (for historical underpayment) are typically negotiable — SAP rarely pursues full retroactive value when faced with a well-prepared counter
- Contract prospective Digital Access terms into your settlement — don't just pay for the past without capping future exposure
Related Resources
