Key Takeaways
- SAP's Digital Access model, introduced with DAAP in 2018, charges per document created by non-named users — a regime most enterprises have not fully measured or challenged.
- Independent measurement consistently finds that 40–70% of SAP's initial digital access claims are overstated, based on document classification errors, double-counting, or systems SAP designates as "indirect" that you contracted for differently.
- SAP uses USMM and the System Landscape Directory (SLD) to count digital access documents — but both tools can be configured, and the methodology is contestable.
- Optimisation means more than challenging SAP's numbers: it means redesigning integration architecture, reclassifying document types, and negotiating DAAP terms that reflect your actual business model.
- Enterprises that engage an independent adviser before SAP raises a digital access claim avoid 30–60% of potential exposure — engaging after a claim is raised costs significantly more.
SAP Digital Access Optimisation is one of the most financially significant — and least understood — opportunities in enterprise SAP licence management. Since SAP restructured its indirect access model under the Digital Access Adoption Programme (DAAP) in 2018, thousands of enterprises have been living with a licensing obligation they cannot precisely measure, cannot reliably defend, and in many cases, cannot even explain to their own board. This guide changes that.
The core problem is structural. SAP moved from a "named user for every touchpoint" indirect access model to a document-based Digital Access model, ostensibly to create predictability. What it actually created was a new class of liability: document-creation counts that SAP measures with its own tools, in ways that favour SAP, and that most enterprises simply accept without independent scrutiny. The result is systematic overpayment.
Our SAP licence optimisation advisory team has run forensic digital access reviews across more than 80 enterprise SAP estates. This guide draws on those engagements to give you a complete, actionable framework for understanding, measuring, challenging, and reducing your digital access costs in 2026.
What Is SAP Digital Access — and Why Does It Matter in 2026?
SAP Digital Access is a licensing framework that charges for documents created in an SAP system by non-named users — typically those accessing SAP via third-party applications, middleware, robotic process automation (RPA), IoT devices, or custom integration layers. Where older SAP contracts charged indirect access on a named-user basis (requiring a licence for every human or system "touching" SAP), Digital Access charges per document: per sales order, per purchase order, per goods receipt, per journal entry.
SAP introduced this model in 2018 under pressure from landmark indirect access disputes, most notably the Diageo case, in which a UK judge ruled that SAP's named-user indirect access model was being applied in ways that dramatically exceeded what the original contract language supported. DAAP was SAP's commercial response: a simplified, auditable, document-based model it could defend more easily in court — and charge for more consistently.
⚠ The DAAP Migration Trap
Many enterprises migrated to DAAP believing the new model would be cheaper or clearer than the old named-user indirect access liability. In practice, DAAP is often more expensive for digitally mature organisations with high document volumes and complex integration landscapes. If you signed a DAAP agreement without an independent review, you almost certainly overpaid.
In 2026, digital access remains the fastest-growing source of unexpected SAP licence cost for enterprises running hybrid landscapes — SAP ECC or S/4HANA on the backend, with Salesforce, ServiceNow, Workday, custom APIs, and automation layers at the front. Every one of those integration points is potentially a digital access liability. And most enterprise IT teams have no reliable mechanism to count the documents being created across all those touchpoints.
SAP's measurement tools — primarily USMM (User & System Measurement) and the System Landscape Directory (SLD) — are designed for SAP's benefit. They were not built to give enterprise buyers an independent, accurate view of their obligation. Understanding their methodology, and where it can be contested, is the foundation of effective SAP digital access optimisation in practice.
The Five Pillars of SAP Digital Access Optimisation
Digital access optimisation is not a single action — it is a structured programme with five distinct work streams that must be run concurrently, or in sequence, depending on whether you are in a pre-audit, audit-response, or strategic rightsizing mode.
1. Independent Measurement Before SAP Measures You
The single highest-return action any enterprise can take is to run its own digital access measurement before SAP raises a compliance claim. SAP's USMM methodology counts document creation events at the SAP application layer, but it cannot distinguish between documents created by systems you have licensed (including under existing indirect access provisions), documents counted twice due to retry logic or message queuing, and documents generated by technical background processes that have no business user equivalent.
Independent measurement, using a combination of ABAP extraction scripts, integration middleware logs, and SLD cross-referencing, consistently identifies 40–70% over-counting in SAP's initial figures. Enterprises that measure first, and present their own methodology to SAP, enter any DAAP negotiation from a position of credibility rather than a position of concession.
2. Document Type Classification and Re-scoping
DAAP covers nine document types: sales orders, purchase orders, production orders, plant maintenance orders, service orders, quality management notifications, inventory postings, goods receipts (goods issue), and journal entries. Not every document-creation event in your SAP system necessarily falls within the contracted DAAP scope. Key areas of challenge include:
- Documents created by SAP's own background jobs (batch input sessions, IDocs originating from SAP-to-SAP interfaces)
- Documents reversed, cancelled, or deleted immediately after creation without business consequence
- Documents created by systems that pre-date the DAAP agreement and may be subject to legacy contract provisions
- Documents created in test, development, or sandbox systems rather than production
- Documents originating from SAP-licensed middleware (e.g., SAP Integration Suite or SAP PI/PO) where indirect access is already covered
Expert Insight
In our experience, the "cancelled and reversed document" category alone typically reduces digital access document counts by 8–15%. These are documents that were created and immediately reversed — they never represented completed business transactions, but SAP's USMM tool counts them as chargeable events unless you explicitly contest the methodology in writing.
3. Integration Architecture Redesign
Some digital access liability is not challengeable — it reflects genuine business document volume created by legitimate third-party integrations. In those cases, the right approach is architectural: redesigning how third-party systems interact with SAP to minimise chargeable document-creation events without disrupting business processes.
This might mean moving from direct API calls that create SAP documents to event-driven architectures where SAP creates the document internally in response to a trigger that does not constitute a chargeable indirect access event. It might mean consolidating multiple integration points that each create documents into a single BTP (Business Technology Platform) integration that is licensed differently. Our SAP indirect access advisory team specialises in exactly this kind of architectural optimisation.
4. DAAP Contract Renegotiation
DAAP agreements signed in 2018–2021 were negotiated under conditions of extreme information asymmetry. SAP's sales teams had a playbook; most enterprise buyers had neither an independent adviser nor a clear understanding of their document volumes. The result was overpriced DAAP bundles with document caps that were either too high (wasted spend) or too low (exposure to true-up claims).
In 2025 and 2026, the renegotiation environment has shifted. SAP is under margin pressure. Competitors including Oracle, Microsoft, and Salesforce are actively competing for SAP's application revenue. Enterprises that can demonstrate accurate document count data, present a credible independent methodology, and structure a renegotiation at an opportune time in SAP's fiscal calendar can achieve DAAP pricing reductions of 20–45% compared to initial agreement terms.
Our SAP contract negotiation team has renegotiated DAAP agreements across industries from manufacturing to financial services. The negotiation leverage lies in the data — but also in knowing when and how to use it.
5. Proactive Compliance Positioning
Digital access optimisation is not just about reducing cost — it is about ensuring that when SAP does conduct a compliance review or measurement exercise, you are not surprised. Proactive compliance positioning means maintaining a running document count by integration point, documenting your measurement methodology, and establishing a clear paper trail that demonstrates good-faith compliance management.
Enterprises that maintain this posture are significantly harder for SAP audit teams to target with overreach claims, and significantly better positioned to resolve any compliance query quickly and cheaply. This posture is also essential groundwork for SAP audit defence if a formal audit is initiated.
How SAP Measures Digital Access — and Where the Methodology Fails
Understanding SAP's measurement methodology in detail is not optional if you are serious about digital access optimisation. SAP's primary measurement tool is the USMM transaction (User and System Measurement), which captures system-level data about document creation events. USMM runs at the SAP application layer and captures document counts across all configured document types.
| SAP Tool | What It Measures | Key Limitations |
|---|---|---|
| USMM | Named user count + document creation events (selected document types) | Cannot distinguish chargeable vs non-chargeable source systems; counts reversals; influenced by configuration |
| System Landscape Directory (SLD) | Third-party systems registered as connected to SAP landscape | Relies on customer registration; many third-party systems not visible; can be contested |
| License Administration Workbench (LAW) | Consolidates USMM data across multiple SAP systems for reporting to SAP | Consolidation logic can amplify counting errors from individual systems |
| STAR (SAP True-up Audit Review) | SAP's audit tool, deployed during formal compliance reviews | Proprietary methodology; not shared with customers; contestable if you have independent data |
SAP's own guidance acknowledges that USMM is not designed to provide a definitive audit-grade count of chargeable digital access documents — it is a measurement aid. But in practice, SAP's licensing teams use USMM output as if it were definitive, presenting it to customers as the authoritative basis for DAAP true-up claims. Challenging this framing requires independent data, independent methodology, and — critically — the contractual standing to insist on your own measurement approach.
For more detail on how to build an independent measurement case, see our article on measuring and challenging SAP digital access counts.
The Digital Access Audit: What to Expect and How to Prepare
A formal SAP digital access audit — triggered either by SAP's internal metrics showing your document counts appear high, or by a proactive audit notice — follows a broadly predictable pattern. Understanding that pattern is the first step to managing the outcome.
SAP will typically issue a written audit notice citing a contractual provision for "self-declaration" or "on-site measurement." The notice will request either that you run USMM and submit results within 30–60 days, or that SAP's audit team be granted access to your systems to run the measurement directly. The second option is significantly more dangerous — SAP's auditors have discretion in how they apply measurement methodology, and without independent oversight, you have no ability to contest their approach in real time.
Preparation steps if you receive a digital access audit notice:
- Engage independent advisers before responding to SAP. Your first response sets the tone. Advisers who understand DAAP contract language can identify leverage points before you commit to a methodology or timeline.
- Pull your own USMM and integration logs before SAP does. Understanding your own numbers before SAP presents theirs is non-negotiable.
- Review your original DAAP contract provisions. Many DAAP agreements contain measurement methodology provisions that SAP routinely ignores — these can be invoked to contest SAP's approach.
- Identify all third-party systems in scope. Not all systems connected to your SAP landscape are covered by DAAP. Document the technical architecture clearly before SAP's team begins their review.
Manufacturing Enterprise: DAAP True-Up Challenge
A global manufacturer with 12,000 SAP users and a heavily automated production environment received a DAAP true-up claim for €3.8M based on SAP's USMM measurement. Independent review identified that 52% of the claimed documents were either reversed production orders, IDocs originating from SAP's own middleware, or goods movements generated by SAP background jobs. The final agreed settlement: €1.1M — a 71% reduction from SAP's initial claim. The engagement paid for itself 18 times over.
Digital Access and S/4HANA Migration: A Critical Intersection
S/4HANA migration creates both risk and opportunity for digital access optimisation. The risk: migration projects typically involve significant changes to integration architecture, potentially triggering new digital access obligations that were not scoped in the original DAAP agreement. The opportunity: migration is one of the few moments when SAP is commercially motivated to revisit the entire licensing relationship, including DAAP terms.
Enterprises migrating to S/4HANA migration licensing must map digital access implications as part of the migration licensing review. Key questions:
- Will the new S/4HANA integration architecture create more or fewer DAAP-chargeable documents than the current ECC estate?
- Does the migration contract include provisions to re-baseline DAAP document volumes post-migration?
- Are there SAP BTP integration services in the migration architecture that could reduce digital access exposure by routing indirect access through SAP-licensed middleware?
- Has the migration project team been briefed on digital access implications of the new integration design?
These questions are rarely asked by SAP's migration team, because the answers often reduce SAP's revenue. An independent RISE with SAP advisory engagement that includes digital access scoping can protect tens of millions in long-term licence cost.
Digital Access Optimisation Roadmap: 12-Month Framework
The following framework represents the typical structure of a comprehensive digital access optimisation programme for an enterprise with 5,000–20,000 SAP users and a complex integration landscape.
| Phase | Timeframe | Key Activities | Expected Output |
|---|---|---|---|
| Discovery | Weeks 1–4 | USMM extraction, integration landscape mapping, DAAP contract review | Baseline document count by system and document type |
| Forensic Analysis | Weeks 5–8 | Document classification challenge, exclusion identification, SAP methodology contestation | Revised document count; identified exclusions (typically 30–60% reduction) |
| Architecture Review | Weeks 7–12 | Integration architecture assessment; BTP/PI/PO route analysis; redesign options | Architecture roadmap to reduce chargeable document creation |
| Commercial Engagement | Weeks 10–20 | DAAP renegotiation; settlement if audit in progress; renewal positioning | Revised DAAP agreement; financial recovery or cost avoidance |
| Ongoing Governance | Month 6 onwards | Quarterly document count review; change management for new integrations | Proactive compliance posture; no DAAP surprises |
Common Mistakes Enterprises Make with Digital Access
Across 80+ digital access engagements, we see the same mistakes repeated. Understanding them in advance is the most efficient way to avoid them.
Accepting SAP's USMM output without independent verification. SAP presents USMM data as if it were a water meter reading — objective and incontestable. It is neither. It is an application-layer count that is subject to configuration choices, double-counting artefacts, and methodology decisions that SAP has made in its own favour. Always run your own measurement.
Signing DAAP agreements without modelling actual document volumes. The most expensive digital access mistake is signing a DAAP agreement based on SAP's estimated volumes rather than your own measured reality. DAAP agreements typically have a fixed term (3–5 years) and escalating volume commitments. Overcommitting in Year 1 means years of unnecessary spend.
Treating digital access as an IT problem rather than a commercial one. Digital access optimisation requires commercial negotiation skills, contract law knowledge, and understanding of SAP's revenue priorities — not just ABAP extraction expertise. The most effective programmes combine technical measurement with commercial strategy.
Not engaging in advance of SAP's fiscal year-end. SAP's fiscal year ends December 31. Q4 is the period when SAP is most motivated to close deals — including DAAP renegotiations — and when the most significant commercial concessions are available. Enterprises that engage for renegotiation in October and November have significantly more leverage than those who engage in January. See our guide on the best time to negotiate with SAP.
Ignoring DAAP implications during digital transformation projects. Every new SaaS application, every automation initiative, every IoT deployment potentially creates new digital access liability. Enterprises that do not include a DAAP impact assessment in their digital transformation governance routinely discover multi-million-pound exposure years after the fact.
Specific Optimisation Strategies by Integration Type
Digital access optimisation strategies differ depending on the type of integration driving document creation. The following covers the most common scenarios.
Salesforce–SAP Integration
Salesforce-to-SAP integrations that create sales orders or journal entries are among the highest-value digital access optimisation targets. Key strategies include routing Salesforce-originated orders through an SAP Integration Suite (formerly SAP Cloud Platform Integration) layer, which may qualify for different licensing treatment, and reviewing whether the Salesforce–SAP interface contract pre-dates your DAAP agreement and is subject to legacy provisions.
RPA and Automation-Triggered Documents
RPA bots creating documents in SAP on behalf of human users are a contested area. SAP's position is that bot-created documents are chargeable under DAAP. The counter-position — which has been successfully argued in multiple engagements — is that bots acting as agents of named users, where those users hold valid SAP licences, are covered under the existing named-user licence. The key is documenting the relationship between the bot and the sponsoring named user.
IoT and Manufacturing Execution System (MES) Integration
High-volume document creation by IoT devices or MES systems is often the single largest driver of DAAP claims in manufacturing environments. The optimisation approach here is architectural: moving from direct document creation to event buffering and consolidation, reducing the per-document count without reducing the underlying business process integrity.
ERP-to-ERP Integrations
Large enterprises operating multiple ERP systems — SAP plus Oracle, SAP plus JD Edwards — frequently have ERP-to-ERP interfaces creating documents at high volume. These integrations pre-date DAAP in many cases and may be subject to legacy indirect access provisions that are more favourable than DAAP. Reviewing the original contract language is essential before accepting DAAP as the applicable framework.
How Much Are You Overpaying for Digital Access?
Our advisers have run independent digital access measurement reviews for more than 80 enterprise SAP estates. The average finding: enterprises overpay by 35–60% compared to their defensible DAAP obligation.
Book Your Free Digital Access Review →Frequently Asked Questions
Indirect access is the older model, in which any human user or system accessing SAP data or functions via a third-party application was required to hold a named SAP user licence. Digital Access, introduced via DAAP in 2018, replaced this with a document-based model that charges per document created by non-named users or systems. Digital Access was designed to be more transparent and predictable — but in practice it is frequently more expensive for digitally mature organisations.
Yes. USMM output is not contractually definitive — it is a measurement tool that SAP uses to support its licensing position. Most DAAP agreements include provisions for customer-submitted measurement data, and all DAAP agreements are subject to the general principles of contract interpretation. We have successfully contested USMM counts in more than 50 engagements, achieving an average reduction of 40–65% from SAP's initial position.
Proactively initiating a digital access review does not automatically trigger a formal audit. However, if you request a contract amendment to reduce your DAAP document commitment, SAP will request supporting data. This is why having independent measurement data prepared before engaging SAP commercially is critical — it prevents SAP from using your request as an opportunity to launch a broader compliance review.
RISE with SAP contracts include digital access components, but the specific terms vary significantly by negotiation. Many enterprises that migrated to RISE discovered that their digital access terms became less favourable than their pre-RISE DAAP agreement — particularly if the migration deal was negotiated without an independent adviser reviewing the DAAP provisions specifically. If you are considering RISE, or have recently signed a RISE agreement, a digital access audit of the RISE contract terms is strongly recommended.
Manufacturing (due to high-volume MES and IoT integration), retail (due to e-commerce and POS integrations creating orders at scale), and financial services (due to complex multi-system architectures and high-frequency transaction processing) consistently have the highest digital access exposure. However, any enterprise with significant third-party application integration and automation will have material DAAP liability.
Yes. SAP is commercially motivated to renegotiate DAAP agreements mid-term if doing so creates upsell opportunities or prevents a competitive threat. We have facilitated mid-term DAAP renegotiations in multiple scenarios, including where customers were actively evaluating competitive alternatives and where customers were facing S/4HANA migration decisions. The key is presenting a compelling commercial case and negotiating at the right time in SAP's fiscal calendar.