SAP Digital Access Adoption Program (DAAP): How to Evaluate, Negotiate, and Avoid Cost Traps

What DAAP Is — and What It Is Not

SAP's Digital Access Adoption Program is a structured commercial offer that allows SAP ECC and S/4HANA customers to legalise existing indirect access exposure under the document-based licensing model at a steep discount. The programme emerged after the 2017 Diageo ruling, when SAP acknowledged that enforcing indirect access claims at full list price against thousands of customers simultaneously was operationally and reputationally untenable.

DAAP gives customers two entry paths. Option A lets you estimate your current annual document count from indirect use and purchase 115 percent of that volume, paying only for 100 percent — effectively securing 15 percent additional headroom at zero cost, an 85 percent effective discount off list. Option B lets you purchase licences for 100 percent of current indirect usage while paying only 10 percent of list price — a 90 percent discount — but with no built-in growth buffer.

What DAAP is not: it is not an amnesty for future non-compliance, it does not cap your growth costs beyond the initial commitment, and it does not automatically cover all integration scenarios. Customers who treat DAAP as a blanket fix without modelling their forward document trajectory frequently find themselves back at SAP's negotiating table within three years.

The Three-Step Exposure Assessment

Before choosing an option or entering any commercial conversation with SAP, you need a clean picture of your actual indirect access exposure. This requires three sequential steps.

Step 1 — Identify All External Integration Points

Map every non-SAP system that creates documents in your SAP landscape. This includes CRM platforms feeding sales orders, e-commerce storefronts generating purchase orders, warehouse management systems writing goods receipts, payroll engines posting time confirmations, and any custom middleware or RPA bots that interact with SAP via API, RFC, BAPI, or IDoc. The list is usually longer than IT believes — particularly after years of organic integration growth. In our experience with mid-size enterprises, 30 to 40 percent of integration points are undocumented at the start of any DAAP evaluation.

Step 2 — Run the SAP Estimation Tool, Not USMM

SAP's traditional measurement tool USMM was designed for user counting and engine licensing — it has no meaningful role in Digital Access measurement. For DAAP purposes, the relevant tools are the Digital Access Estimation Tool and the SAP Passport mechanism. The Estimation Tool counts documents by type across your system landscape without complex installation. SAP Passport works differently: it tags all internally originated documents, so anything without a tag is classified as externally created and therefore chargeable. This passive tagging approach makes Passport the more conservative — and typically higher — of the two counts, and the one SAP's audit team will use if you reach a dispute.

Run both tools. The delta between them is your negotiation buffer: it represents documents that Passport classifies as external but which the Estimation Tool correctly attributes to internal processes or auto-generated document chains. For ECC systems, SAP Note 2992090 governs Digital Access measurement. For S/4HANA systems, use SAP Note 2999672.

Step 3 — Model Three Scenarios

Before entering commercial discussions, model the financial outcomes under three scenarios: DAAP adoption now, continued non-compliance with estimated audit risk, and integration redesign to reduce document counts. The comparison is almost always decisive. For a mid-size enterprise generating 4 million indirect documents annually, DAAP adoption at 10 percent of list might cost €200,000 to €400,000 upfront plus 22 percent maintenance annually. An audit settlement for the same volume at full list price — with three years of back maintenance — typically lands between €4 million and €8 million. The DAAP pathway is the rational choice in almost every scenario involving material indirect usage.

Option A vs Option B: The Decision Framework

The choice between DAAP options is not purely mathematical — it depends on your growth trajectory, your ECC-to-S/4HANA migration timeline, and your confidence in the measurement methodology.

When Option A Is the Right Choice

Option A — purchase 115 percent of volume, pay for 100 percent — makes sense when your current document counts are growing and you expect volume to increase by more than 10 percent over the next two to three years. The 15 percent built-in headroom delays any top-up conversation with SAP. It is also preferable when your measurement methodology has uncertainty: if you are not fully confident in the Estimation Tool output, the additional buffer absorbs counting errors without triggering a compliance breach. Customers in high-growth industries — retail, logistics, manufacturing with expanding e-commerce integration — consistently favour Option A.

When Option B Is the Right Choice

Option B — purchase 100 percent of usage at 10 percent of list — is optimal when your integration landscape is stable or contracting. Companies consolidating systems ahead of an S/4HANA migration, or actively retiring legacy integrations, often see document volumes plateau or decline. Paying 10 percent of list for a precisely sized commitment, and renegotiating any growth component as part of the broader S/4HANA deal, yields a lower total cost than locking in 15 percent additional capacity you will never use.

The Migration Context Changes the Calculus

If you are planning an S/4HANA migration within the next three to four years — and only 39 percent of SAP's 35,000 ECC customers have licensed S/4HANA as of end 2024, meaning the majority have not yet made this transition — your DAAP sizing must account for a fundamentally different licensing baseline post-migration. Under RISE with SAP, Digital Access is typically included within the subscription for standard integration scenarios. A DAAP commitment made today under ECC may represent over-investment if your S/4HANA contract covers the same use cases. Always model the post-migration position before locking in multi-year DAAP volumes.

The Cost Traps SAP Does Not Advertise

DAAP's headline discounts obscure several structural cost problems that accumulate after the initial commitment is signed.

Trap 1 — Measurement Tool Over-Counting

SAP's Passport tool classifies any document without an internal origin tag as externally created and therefore chargeable. In practice, this over-counts in several common scenarios: documents created by batch jobs running under technical user accounts rather than named users, follow-on documents auto-generated by workflow steps that Passport cannot distinguish from external triggers, and documents posted via RFC connections where the Passport stamp was not implemented at integration build time. We have seen Passport counts run 30 to 60 percent above the actual externally-driven volume in complex enterprise landscapes. Never accept SAP's raw Passport output as the basis for DAAP sizing without independent validation.

Trap 2 — Perpetual Maintenance on the Net Licence Fee

Annual maintenance at 22 percent of the net licence fee applies to all Digital Access licences acquired through DAAP. On a €300,000 DAAP commitment, that is €66,000 per year in perpetual maintenance — regardless of whether your actual document volumes change. Customers focused on the upfront DAAP discount frequently neglect to model the total maintenance obligation and find themselves paying more over a ten-year horizon than the original licence fee itself.

Trap 3 — Growth Pricing Exposure After Commitment

The generous DAAP discount applies only to the initial commitment. Any additional document volumes required beyond the contracted quantity must be purchased at standard commercial terms — typically 50 to 70 percent off list rather than 85 to 90 percent. Customers who size their DAAP commitment conservatively to minimise upfront cost, then experience document growth, face top-up pricing at materially worse rates. Size generously on the initial commitment, or negotiate a contractual right of first refusal at DAAP-equivalent discounts for a defined growth tranche.

Trap 4 — Back-Maintenance Forgiveness Not Guaranteed in Writing

SAP routinely represents verbally that DAAP adoption provides a clean slate: past indirect usage will not be back-charged. This representation should be in the signed contract, not in a sales presentation. Several clients have encountered SAP audit teams who claimed that DAAP only covered the forward period, not historical usage, because the amnesty language was absent from the Order Form. Insist on explicit written language covering all indirect usage prior to the DAAP effective date for every system and document type covered by the agreement.

Negotiation Benchmarks and Tactics

The DAAP programme is not a fixed price list — it is a negotiating framework, and SAP's opening offer is rarely its best offer.

Opening Position vs Achievable Outcome

SAP's initial DAAP proposal commonly targets 50 to 60 percent off list price. Well-prepared customers with credible volume data and alternative leverage — including S/4HANA migration commitments, competitive vendor conversations, or documented audit defence arguments — routinely achieve 88 to 92 percent discounts. The spread between opening position and achievable outcome is larger in DAAP negotiations than in almost any other SAP commercial context.

SAP's Fiscal Year as Leverage

SAP's fiscal year ends September 30. Q4 — July through September — is when SAP's direct sales force is under maximum quota pressure. DAAP discussions initiated in June and concluded in August or early September consistently achieve better discount rates than Q1 or Q2 negotiations. If your timeline allows, align your DAAP entry to SAP's quarter-end pressure cycle.

Bundling with Broader SAP Negotiations

DAAP discussions that occur in isolation give SAP's sales team limited motivation to improve commercial terms beyond the programme floor. Bundling DAAP adoption with S/4HANA licensing conversion, BTP credit commitments, or multi-year maintenance renewals creates competitive pressure and gives SAP's deal desk a larger transaction to justify additional discount authority. Customers who bundle DAAP with S/4HANA migration commitments consistently achieve the strongest combined commercial outcomes.

A Client Pattern: Manufacturing Sector

A mid-size European manufacturer running SAP ECC with 12 external integrations — including a Salesforce CRM, a third-party warehouse management system, and a custom B2B portal — ran an initial Passport measurement and found 7.2 million chargeable documents annually. SAP's DAAP proposal priced this at approximately €580,000 at a 60 percent discount.

Independent validation of the Passport output identified 2.3 million documents as misclassified — generated by internal batch processes that Passport tagged as external due to a technical user account configuration. Correcting the count to 4.9 million documents, and rerunning the negotiation with an S/4HANA migration commitment for the following year, yielded a final DAAP settlement of €168,000 — 71 percent below SAP's initial figure, inclusive of back-maintenance forgiveness and an explicit growth buffer through the migration date.

Contract Language Checklist

Before signing any DAAP-related Order Form, verify that the following provisions are explicitly included in the contract — not just referenced in verbal presentations or email exchanges.

• Historical amnesty clause: SAP waives all claims for indirect access prior to the DAAP effective date for the document types and systems covered by the agreement.
• Measurement methodology definition: The contract specifies which measurement tool and which SAP notes govern document counting, preventing SAP from switching to a more conservative methodology at a future audit.
• Growth purchase rights: A contractual right to purchase additional document volumes at DAAP-equivalent discounts for a defined period (minimum 24 months) beyond the initial commitment.
• RISE with SAP transition credit: If you migrate to RISE within the DAAP commitment period, unused Digital Access document capacity is credited against or applied to the RISE subscription, preventing double-payment.
• Document type scope definition: Explicit listing of which of the nine chargeable document types are covered by the DAAP commitment, preventing scope expansion arguments at audit time.

The Forward View: DAAP in the S/4HANA Era

DAAP's commercial terms were designed for the ECC-to-S/4HANA transition period, and SAP's broader strategy is to migrate indirect access licensing into the subscription economics of RISE with SAP. For the 61 percent of SAP's 35,000 ECC customers who have not yet licensed S/4HANA, DAAP remains the most cost-effective path to legalising indirect access exposure. Gartner projects 17,000 companies will not be ready for the S/4HANA migration by 2027, and the Horváth 2025 survey of 200 enterprises found only 37 had completed migration — with more than 60 percent over budget and behind schedule.

This extended ECC tail means DAAP will remain relevant for a substantial portion of the SAP customer base through 2027 and beyond. But the programme's terms are subject to change, and SAP has adjusted DAAP commercial parameters multiple times since 2018. The practical implication: structure DAAP now to bridge to your S/4HANA migration without creating a double-payment scenario. The right DAAP agreement is not just a compliance fix — it is a commercial instrument that, structured correctly, reduces your total SAP cost of ownership through the migration cycle and beyond.