A comprehensive guide to SAP's document-based licensing model for indirect access: how the nine document types work, how SAP calculates costs, common pitfalls that inflate spend, cost optimisation strategies, proven negotiation tactics, audit safeguards, and how to align Digital Access with your business roadmap.
This guide is part of our SAP Digital Access Complete Guide series. See also: Digital Access Advisory Service | SAP Audit Defence Service | SAP Contract Negotiation Service.
In the past, SAP licensing was primarily based on named users. In today's landscape, numerous systems and devices connect to SAP indirectly through APIs and integrations. An e-commerce site feeding orders into SAP, sensors automatically updating inventory, partner portals creating service requests. Traditional user licences do not fit these scenarios.
This came to a head in the Diageo lawsuit in 2017, where the company was found liable for approximately 54 million pounds in fees for allowing thousands of Salesforce users to indirectly use SAP. SAP's response was the Digital Access model: instead of charging by user, SAP charges by the number of documents created in the system by external (indirect) sources.
| Why It Matters | Detail |
|---|---|
| Integration is everywhere | If your SAP connects to web portals, partner systems, cloud apps, or IoT devices, you are in Digital Access territory. Every new interface could trigger licensable SAP documents |
| Audit risk is growing | SAP has become aggressive in auditing indirect use. Without a proper Digital Access licence, a routine audit could reveal thousands or millions of unlicensed documents and a significant bill |
| S/4HANA migrations | Many enterprises moving to S/4HANA or RISE with SAP are being pushed to adopt Digital Access as part of the deal. SAP uses these junctures to "clean up" licensing |
| Cost control imperative | Indirect usage will only increase as businesses become more digital. Getting a handle on Digital Access now means you can forecast and cap SAP costs rather than chasing them |
| Document Type | Examples | Counting Method | Weighting |
|---|---|---|---|
| Sales Documents | Sales orders, quotes | Per line item (each line = 1 document) | 1.0x |
| Invoice Documents | Billing documents | Per line item | 1.0x |
| Purchase Documents | Purchase orders, requisitions | Per line item | 1.0x |
| Service and Maintenance | Service orders, maintenance requests | Per document (each = 1) | 1.0x |
| Manufacturing Documents | Production orders | Per document | 1.0x |
| Quality Management | Quality notifications, inspections | Per document | 1.0x |
| Time Management | Time entries, confirmations | Per document | 1.0x |
| Financial Documents | Financial postings, journal entries | Per line item x 0.2 weight | 0.2x (5 lines = 1 doc) |
| Material Documents | Inventory movements, goods issues | Per line item x 0.2 weight | 0.2x (5 lines = 1 doc) |
If one external action triggers a cascade of documents in SAP, you only pay for the first originating document. An external web order creating a Sales Order which then generates a Delivery and Invoice internally counts as one Sales Document. Follow-on documents are not charged again. Purely read-only interactions (APIs querying SAP for data without creating records) do not count towards Digital Access.
| Pricing Element | Detail |
|---|---|
| Document packs | Sold in blocks of 1,000 documents/year. The more you purchase, the lower the per-document unit price. Small volumes carry high unit cost (potentially several dollars per document); very large volumes drive unit cost well under $1. After negotiation, many enterprises pay effective rates in the cents per document |
| True-up for overuse | If you exceed your purchased volume, you buy additional blocks at contracted rate (if negotiated) or list price (if not). Over-purchased capacity generally cannot be refunded or carried forward |
| Annual maintenance | Approximately 20% of licence value annually. Ensure maintenance is calculated on the discounted price you actually paid, not list price. This is a common negotiation point with significant long-term impact |
| Flat-fee unlimited licence | For very high or unpredictable usage: fixed annual fee typically approximately 10% of overall SAP licence value. Caps exposure regardless of volume. Makes sense for major digital platforms, large IoT estates, or explosive integration growth |
In cloud subscription models, indirect usage is typically bundled into overall subscription metrics (FUEs). Confirm how indirect use is covered to avoid double-paying. If transitioning from on-premises, clarify what happens to your Digital Access investment. Obtain a commitment that remaining value can be converted into the RISE contract.
| Pitfall | Detail |
|---|---|
| Incorrect volume forecasts | Underestimate and face unplanned true-up bills or audit findings. Overestimate and pay maintenance on unused capacity. Both are expensive |
| Double-counting documents | Only the originating document from an external trigger should count. SAP's tools may count follow-on documents if not configured correctly, making usage appear 2-3x higher than reality |
| Mixing indirect vs direct usage | Documents created by internal SAP users should not consume Digital Access licence. Without tagging or logging to distinguish internal from external creation, you will overcount and overpay |
| Misidentifying document types | Only the nine defined categories count. Master data updates, custom objects, and non-standard transactions may not require Digital Access. Grey areas must be clarified with SAP in writing |
| Underestimating "small" documents | Financial and Material documents count at 0.2x weighting but IoT and automation generate millions. 5,000 material movements = 1,000 documents. It adds up fast |
| Seasonal and spike usage | Year-end rushes, monthly financial closes, and one-time events (data migrations) can blow annual quota early if not planned for |
| Hidden integrations | Legacy systems, shadow IT, new cloud apps, and partner software quietly creating SAP documents outside your forecasts, then discovered in audit |
| Ignoring contract details | Vague definitions of counting methods, measurement tools, and compliance terms leave too much to SAP's interpretation. Get everything in writing |
| Step | Action | Detail |
|---|---|---|
| 1 | Establish a usage baseline | Run SAP's Digital Access estimation reports or use third-party tools. SAP offers a free evaluation service. Be cautious: SAP's tool can over-count (including internal activity or follow-on documents). Complement with your own analysis: identify technical user IDs and API accounts, then query document creation volumes over the last 12 months |
| 2 | Implement tracking and tagging | Enable SAP Passport functionality to tag transactions initiated via external APIs. Alternatively, work with Basis/security team to mark and monitor external integration user accounts. Goal: reliably separate documents created externally from those created by internal SAP users |
| 3 | Run internal monitoring and self-audits | Do not wait for SAP to audit you. Establish quarterly or monthly internal reviews. Set automated alerts when approaching licensed limits. Catching a trend (10% month-over-month growth) early allows you to investigate, optimise, or plan additional purchases before running out of capacity |
| 4 | Forecast with multiple scenarios | Collaborate with business units. Create conservative (business as usual), target (expected growth), and aggressive (high success) scenarios. Licence for the target scenario plus buffer. Handle the aggressive case through contract terms (flexible expansion options, pre-agreed overage rates) |
| 5 | Optimise integration architecture | Work with IT architects to reduce document footprint. Batch or consolidate updates so one combined document replaces ten separate ones. Filter trivial updates that do not need real-time SAP posting. Streamlining data exchanges directly saves licence cost |
| Strategy | Detail |
|---|---|
| Know your numbers first | Never enter negotiation without your own usage analysis. SAP will present an "estimate" often inflated to sell more. Counter with your measured baseline and forecast. Demonstrating knowledge of actual usage positions you as an informed counterpart |
| Leverage volume for discounts | Make scale a centrepiece. Reference benchmarks where per-document prices dropped below $1 at volume. 50-90% off list price is not unusual, especially when bundling Digital Access within a larger deal. SAP's DAAP offered up to 90% discounts. Even if ended, use it as a precedent |
| Build in growth protections | Negotiate a 10-15% overage buffer without penalty; pre-agreed rates for additional blocks at the same discount; tiered pricing baked in. Alternatively, negotiate a cost cap or evaluate the unlimited flat-fee model |
| Bundle with other SAP purchases | If also purchasing other SAP products, migrating to S/4HANA, or expanding footprint, bundle the Digital Access discussion into the larger deal. End-of-quarter and end-of-year negotiations yield significantly better pricing |
| Lock down maintenance and renewal | Ensure maintenance fees are based on discounted price, not list. Cap escalation on future additions. Cap renewal increases (no more than 3% annual). Do not accept an attractive first-year price that escalates significantly at renewal |
Accepting SAP's initial volume estimate and list pricing without independent validation. In every engagement where we have run our own baseline analysis, the client's actual document volumes have been materially different from SAP's estimate, usually lower. That difference, combined with aggressive volume-tier negotiation, typically reduces the Digital Access cost by 60-85% compared to the initial SAP proposal.
| Safeguard | Detail |
|---|---|
| Explicit definitions and measurement | Contract should clearly list the nine document types, definitions (referencing SAP notes), and which tools or reports measure consumption. Document whether unique transaction types or edge cases are included or excluded. Never leave measurement method open-ended |
| Audit true-up terms | Have audit findings treated as normal true-up, not a breach. Include language allowing purchase of additional blocks at pre-agreed discounted rate, not list price. Set reasonable window (e.g. 30 days) to purchase additional licences |
| Past usage resolution | If adoption resolves historical indirect access exposure, include explicit amnesty language. You do not want SAP coming back later for fees before the Digital Access agreement was signed. The agreed licences should cover past indirect use through the contract date |
| Regular reporting and self-assessment | Negotiate periodic usage reviews with SAP: quarterly reports or annual checkpoint to voluntarily true-up. This collaborative approach catches issues early and reduces likelihood of formal audit. Assign an internal compliance owner |
| Scenario | What to Negotiate |
|---|---|
| Mergers and acquisitions | Include terms allowing extension to new entities or volume increases at predefined rates. Post-merger, document volumes may double. Budget for this or secure first-negotiation rights at similar pricing |
| Divestitures | Ensure you can transfer or reallocate Digital Access licences to a spun-off entity (or reduce count accordingly). Negotiate one-time adjustment or credit provision if divestiture is foreseeable |
| Digital initiatives | Launching D2C store, IoT-enabled services, or partner portal? Model the document impact and discuss with SAP during negotiation. Get explicit confirmation planned use cases are within scope |
| Cloud transitions (RISE) | Clarify what happens to your Digital Access investment. Obtain commitment that remaining value converts into the RISE contract or that the RISE subscription metric accurately accounts for external usage. Do not pay twice |
| Automation, RPA, and AI | RPA bots logging into SAP directly may use named user licences; AI calling via API counts as Digital Access. Avoid language restricting licences to "human" users. Model document impact from planned automation |
| Mistake | Detail |
|---|---|
| Accepting the first offer | SAP's initial quote is based on list prices and conservative estimates. Customers who accept consistently overpay by 50-80% |
| Not modelling in-house | Signing based on SAP's assurances or guesswork, then discovering actual usage is completely different. Do spreadsheet analysis for multiple scenarios before committing |
| Overlooking named user overlap | Digital Access covers only nine document types created indirectly. It does not eliminate named user requirements. Ensure you are not double-paying where a partner has both direct access and creates documents via integration |
| Ignoring ongoing maintenance | 20% annual maintenance adds up. If pegged to list price rather than discounted amount, you pay more over time than initial savings suggested |
| Unclear true-up terms | Vague overage handling means SAP could argue excess constitutes non-compliance at list price. Nail down process, pricing, and timeframes before signing |
| Not including all use cases | Discussing only e-commerce and overlooking logistics interface, cloud HR feed, or IoT pipeline. SAP will charge separately for anything not covered. Bring complete integration inventory |
| Skipping audit protection clauses | Overconfidence leads to omitting protective clauses. Always specify audit handling, true-up at contracted rates, and past usage resolution regardless of relationship |
SAP's licensing model will continue to evolve. As SAP pushes RISE and S/4HANA Cloud, expect Digital Access to be increasingly absorbed into cloud subscription metrics. The document-based model may eventually be replaced by consumption-based pricing more natively integrated into RISE's commercial structure. Organisations negotiating today should ensure contracts accommodate this transition without penalty.
SAP may expand the nine document types to cover new scenarios driven by AI, machine learning, and hyper-automation. Build contract language that pins document types to current definitions and requires mutual agreement for changes. SAP may also develop industry-specific pricing (transaction-based for retail, event-based for manufacturing IoT) that could offer better alignment but also new complexity.
SAP Digital Access is SAP's document-based licensing model for indirect access. It charges when third-party systems, websites, mobile apps, IoT devices, or external users create business documents in SAP. Rather than counting individual external users (impractical for e-commerce or IoT), SAP counts specific business documents. There are nine defined document types, and the licence is purchased in annual document packs at tiered pricing. It replaces the older, more ambiguous "indirect access" approach that led to disputes like the Diageo case.
SAP does not publish official per-document pricing. At small volumes, list prices can be several dollars per document. At large volumes, per-document costs drop well under $1. After negotiation, many enterprises pay $0.10-$0.50 per document. Discounts of 50-90% off list are common, particularly when bundled with larger SAP purchases. The key is never accepting SAP's initial proposal without independent volume validation and aggressive pricing negotiation.
No. Digital Access only counts documents representing business transactions created in the system. Read-only interactions (APIs querying data, displaying information, extracting reports without creating or modifying records) do not consume licence. Only the nine defined document types count, and only when created by an external source. SAP only counts the first originating document in a process chain.
You are expected to true-up by purchasing additional document blocks. If your contract includes pre-agreed overage rates, you buy more at a known cost. If silent on overage handling, SAP could argue excess constitutes non-compliance at list price. This is why negotiating explicit true-up terms (pre-agreed rates, 30-day purchase window, 10-15% buffer without penalty) is essential before signing.
In RISE, you do not typically purchase Digital Access as a separate document-count licence. Indirect usage is factored into overall subscription metrics, typically measured through Full Usage Equivalents (FUEs). The indirect access cost is effectively bundled. However, heavy API usage drives up subscription requirements. Always confirm how indirect use is covered, ensure you are not double-paying, and clarify what happens to existing Digital Access investment when transitioning.
Whether adopting Digital Access for the first time, negotiating a renewal, preparing for an SAP audit, or transitioning to RISE, our SAP licensing specialists help enterprises measure accurately, negotiate aggressively, and build contracts that protect against audit exposure and cost surprises. 100% vendor-independent. Fixed-fee engagement.
Digital Access Advisory ServiceIndependent SAP advisory. Digital Access measurement. Document-based licensing negotiation. Audit defence. 100% vendor-independent, fixed-fee engagement.