Why DAAP Exists and What It Means for Indirect Access
SAP's Digital Access Adoption Program (DAAP) was born from one of the most contentious areas in enterprise licensing: indirect access. When third-party systems—an e-commerce platform, a CRM, a supplier portal—create business documents inside SAP, the question of who or what needs a licence became a minefield. High-profile disputes in the mid-2010s, including multi-million-pound court judgements, forced SAP to rethink its model.
In 2018, SAP introduced document-based licensing as an alternative: instead of counting every possible user who might touch SAP data, it would count the business documents (orders, invoices, deliveries) created by external systems. This was a step toward transparency, but it also created a new commercial lever. Organisations with high-volume integrations suddenly faced bills they had never budgeted for.
DAAP, launched in 2019, is SAP's incentive programme to accelerate adoption of the new model. Think of it as the "carrot" that accompanies the compliance-audit "stick." For customers, DAAP offers a one-time opportunity to legitimise all indirect usage at a steep discount and to wipe the slate clean on past unlicensed consumption. For SAP, it locks in recurring support revenue and shifts the customer base to a model it controls.
"DAAP is not philanthropy. It is a structured mechanism for SAP to monetise indirect access at scale — but when negotiated properly, it can deliver genuine value for the customer."
Understanding this dynamic is essential before you engage. DAAP is a negotiation, not an off-the-shelf transaction. Every element — the discount, the scope, the future-proofing clauses — is open to discussion if you know where to push.
How Document-Based Licensing Works Under DAAP
Under SAP's document-based model, the licensing metric shifts from named users to digital documents. SAP has defined nine categories of documents that require a Digital Access licence whenever they are created by an external system:
| Document Type | Typical Source | Volume Risk |
|---|---|---|
| Sales Order | E-commerce, CRM, EDI | High |
| Invoice (Sales) | Billing systems, portals | High |
| Purchase Order | Procurement platforms | Medium |
| Service Confirmation | Field-service apps | Medium |
| Manufacturing Order | MES, IoT systems | Medium |
| Material Document (Goods Movement) | Warehouse systems | High |
| Payment Document | Bank interfaces | Medium |
| Quality Inspection Lot | QMS, lab systems | Low |
| HR Master Data Record | ESS/MSS portals, HCM | Low |
DAAP wraps this model in a special one-time purchase programme with two headline options:
115 % of Current Volume
You license 115 % of measured usage but pay for only 15 %. Provides a built-in growth buffer at roughly an 85 % discount.
100 % of Current Volume
You license 100 % of measured usage at a 90 % discount. The absolute lowest initial outlay, ideal when volumes are stable.
One-Time Deal
DAAP pricing is typically available once. Any additional documents beyond the initial buy may revert to standard pricing unless you negotiate otherwise.
Crucially, DAAP also offers licence-conversion credits. If you previously purchased named-user licences or engine licences as a workaround for indirect access, you can trade those in. Their value offsets your DAAP cost — though SAP will usually insist that your total maintenance spend does not decrease.
The amnesty clause is the programme's most powerful draw: SAP commits to forgiving all past unlicensed indirect usage when you adopt DAAP. Without this, any compliance exercise could result in retrospective charges at full list price, plus back-dated maintenance. The amnesty removes that risk entirely — provided it is explicitly documented in the contract.
DAAP Cost Modelling and Risk Assessment
Adopting DAAP is fundamentally a financial decision. Before you approach SAP, you need a model that quantifies the opportunity and the risk. Here is a structured approach:
Measure Your Baseline Usage
Run SAP's Digital Access Estimation tool across every production system. Capture document counts by type and by interface. Include "quiet" integrations — that B2B gateway, the old logistics connector, the supplier portal nobody remembers. Clean the data: SAP's tools occasionally double-count, so validate totals against known transaction logs.
Forecast Future Demand
Engage business and IT leaders to map upcoming changes: new sales channels, IoT data feeds, acquisitions, cloud migrations. Build three scenarios — steady state, moderate growth (10–15 % p.a.), and aggressive growth (25 %+). Project document volumes over 3–5 years for each.
Compare Three Paths
Model the total cost of (a) adopting DAAP now, (b) doing nothing and risking an audit, and (c) restricting or eliminating problematic integrations. Include annual maintenance at 22 % of the net licence fee, plus any conversion credits that reduce upfront cost.
Quantify the Audit Risk
If you do nothing, estimate the compliance liability under a worst-case audit: full list price for all uncovered documents, plus 2–3 years of back-dated maintenance. For a mid-sized estate, this can easily reach 10–20 × the DAAP cost.
European Retailer: DAAP vs. Audit Exposure
Situation: A €4B European retailer with a high-volume e-commerce platform generating 1.2 million sales orders per year in SAP, plus 800,000 material documents from warehouse integrations.
DAAP analysis: Option B would cost approximately €180,000 (90 % off list) plus €39,600 annual maintenance. Total 3-year cost: €298,800.
Beyond hard costs, factor in intangibles: the executive distraction of defending an audit, reputational risk to IT leadership, and the benefit of a clean compliance posture for future SAP negotiations.
Critical Contract Terms to Negotiate
The discount is only one dimension of a DAAP deal. What separates a good deal from a great deal is the contract language. These are the terms you must negotiate before signing:
Scope of Coverage
The agreement must explicitly list every document type and system covered. Ambiguity allows SAP to claim an integration was excluded. Demand a definitive inventory of what is licensed.
Written Amnesty Clause
The waiver of past indirect-access claims must be in the contract — not verbal. This is the most valuable element of DAAP; treat it as non-negotiable.
Conversion Credits
List every retired licence by product code and credit value. Confirm that maintenance is transferred, not duplicated. Do not allow SAP to inflate your maintenance base post-conversion.
Future Pricing Protection
Secure the right to purchase additional document packs at the same (or near-same) discount. Without this, any growth beyond your initial buy reverts to list price — destroying the long-term economics.
Additional terms to pin down include overage allowances (negotiate a 10 % buffer before additional charges apply), maintenance rate locks (confirm 22 % of the discounted net fee, not the list fee), and cloud-transition alignment (if you move to RISE with SAP within 3–5 years, ensure DAAP investment can be credited or terminated without penalty).
Watch for definitions tied to external SAP policy documents ("as per SAP Note 2964747"). If the contract references a mutable policy, request that the version in effect at signing is attached and frozen. SAP's measurement methodology evolves — you do not want future changes applied retroactively.
"Every promise that is not in the four corners of the contract does not exist. SAP account executives change; contract language endures."
The DAAP Negotiation Playbook
Negotiating DAAP successfully requires preparation, timing, and discipline. The following playbook distils what works in the field:
Phase 1 — Internal Preparation
Before SAP knows you are interested, complete your usage audit, cost model, and risk assessment. Identify surplus licences eligible for conversion. Align IT, procurement, finance, and legal on your objectives, budget ceiling, and red lines. A unified internal team signals seriousness to SAP and prevents last-minute derailments.
Phase 2 — Timing and Leverage
Approach SAP when you hold leverage: during a larger purchase negotiation (S/4HANA migration, additional modules), at SAP's quarter-end or fiscal year-end (January and December), or when SAP is motivated to close deals. If SAP has announced a DAAP deadline, use it to your advantage — but do not panic. SAP has extended DAAP repeatedly; any "last chance" messaging is a sales tactic until the ink is dry.
Phase 3 — Anchor High
Frame your opening: "We understand DAAP has provided 85–90 % discounts to comparable organisations. We expect the same or better, given the size of our commitment." This anchors the conversation and prevents SAP from starting with a weaker offer. If SAP leads with 50–60 %, counter with your benchmark data.
Phase 4 — Negotiate Beyond Price
| Dimension | What to Push For | SAP's Likely Counter |
|---|---|---|
| Discount | 90 % off list (Option B) or equivalent | 80–85 % initially; expect to land 88–92 % |
| Growth protection | Same discount for 2–3 years on incremental purchases | "DAAP is one-time" — push for a defined right of first purchase |
| Amnesty | Explicit, unconditional, written | Verbal assurance — reject this and insist on contractual language |
| Conversion credits | Full investment value of retired licences | Partial credit — escalate if necessary |
| Cloud alignment | Credit toward RISE if migrating within 5 years | "We can discuss at the time" — push for at least a good-faith clause |
Phase 5 — Document Everything
After reaching a verbal agreement, send a detailed summary email: "As discussed, we will proceed with DAAP Option A for X documents at Y price (Z % discount), including amnesty for past indirect use, conversion of licences D valued at €N, and pricing protection for additional purchases at the same rate through [date]." This step ensures alignment and creates a reference point for the contract drafting team.
Phase 6 — Review the Contract Meticulously
Cross-reference every negotiated term against the order form. It is common for omissions or altered wording to appear. Mark up and return anything that deviates. A poorly worded contract can undermine weeks of negotiation. Do not sign until every commitment is reflected.
Common DAAP Pitfalls and How to Avoid Them
Underestimating Volume
Overlooking quiet integrations (B2B gateways, logistics connectors) leads to an immediate compliance gap. Run a comprehensive system scan before locking in numbers.
No Future Pricing Clause
Without growth protection, any increase beyond your DAAP buy reverts to full list price — potentially erasing the original savings entirely.
Over-Purchasing
Buying double the estimated need "just in case" means paying maintenance on shelfware indefinitely. Base decisions on realistic scenarios, not worst-case fears.
Global Manufacturer: The Monitoring Gap
Situation: A manufacturing group negotiated a strong DAAP deal covering 500,000 documents but implemented no ongoing monitoring process.
What happened: Over 18 months, regional IT teams introduced new integrations without central oversight. Document counts climbed 30 % above the licensed threshold.
Other pitfalls include poor internal communication (development teams connecting new tools to SAP without understanding the licensing impact), blindly accepting SAP's measurement output (known bugs in estimation tools can overcount), and ignoring the broader licence estate (converting licences for DAAP credit without confirming they are truly surplus).
🎯 DAAP Pitfall Prevention Checklist
- Comprehensive audit: Scan every production system and interface before signing.
- Growth buffer: Add 15–20 % headroom unless your landscape is genuinely static.
- Pricing protection: Secure contractual language for future purchases at the DAAP rate.
- Monitoring process: Establish quarterly document-count reviews from day one.
- Change-management gate: Require a licensing impact assessment for any new SAP integration.
- Verify SAP's data: Cross-check estimation-tool output against your own transaction logs.
Governance: Embedding DAAP into Ongoing Licence Management
Signing a DAAP deal resolves your current compliance position. Keeping it resolved requires operational governance. Treat your digital document count as a KPI with the same rigour you would apply to cloud-spend management:
Assign ownership. Designate a role within your SAM team or SAP Centre of Excellence to track digital-access consumption. This person owns the data, reports to IT leadership quarterly, and is consulted before any new SAP integration is approved.
Implement threshold alerts. Set internal triggers at 70 %, 85 %, and 95 % of your licensed document count. At 85 %, initiate budget discussions for additional licences. At 95 %, restrict new integration deployments until capacity is confirmed.
Maintain a live interface inventory. Every third-party system connected to SAP should be catalogued: what document types it creates, who owns it, and its current monthly volume. Update the inventory whenever a system is added, modified, or retired.
Optimise document creation. Work with technical teams to identify inefficiencies. Can individual micro-transactions be batched into a single order with multiple line items? Are duplicate entries being created by misconfigured middleware? Small architectural improvements can materially reduce document counts.
Conduct annual reconciliation. Run a formal true-up at least once a year. Compare actual usage against entitlements, report findings to finance, and plan any necessary procurement actions. Align this review with your SAP support-renewal cycle for maximum efficiency.
The Future of SAP Digital Access and DAAP
Several trends will shape the evolution of digital-access licensing over the next three to five years:
Cloud migration blurs the line. As organisations move to RISE with SAP or S/4HANA Cloud, indirect access is increasingly bundled into subscription metrics such as Full User Equivalents (FUEs). For customers fully on RISE, the traditional DAAP model may become redundant — but hybrid estates (part on-premise, part cloud) will face complex licensing overlaps that need careful management.
DAAP's lifespan is uncertain. SAP has extended the programme repeatedly since its 2019 launch. As of early 2026, there is no published end date. However, SAP could sunset DAAP with notice, particularly as the on-premise installed base shrinks. If you have significant indirect usage, delaying indefinitely carries risk.
Consumption-based models are coming. SAP, like most enterprise vendors, is moving toward pay-per-use pricing. Future licensing may charge by API call volume, data throughput, or transaction value rather than discrete document counts. Organisations that build flexible procurement frameworks today will adapt more easily.
Customer advocacy matters. User groups (ASUG, DSAG, UKISUG) have been instrumental in pushing SAP toward fairer licensing. Continued collective pressure may yield further concessions — more generous bundling in cloud subscriptions, relaxed measurement thresholds, or successor programmes to DAAP with improved terms.
Third-party tooling is maturing. Independent SAM tools for measuring and forecasting digital-access consumption are improving rapidly. Better customer-side data reduces the information asymmetry that has historically favoured SAP in compliance discussions.
Expert Recommendations: Making DAAP Work for You
Audit Before You Engage
Never approach SAP without a validated, independent measurement of your actual document volumes. SAP's own tools may overcount — your data is your leverage.
Time Your Approach
Align DAAP discussions with a larger SAP commercial event (renewal, migration, expansion). SAP is more flexible when more revenue is on the table.
Contract Over Conversation
Every commitment — amnesty, growth protection, conversion credits, cloud alignment — must be in the signed agreement. Verbal promises from account executives do not survive personnel changes.
Build Governance from Day One
Monitoring, threshold alerts, and change-management gates are not optional. They are the mechanism that ensures DAAP delivers long-term value instead of a single year of relief.
"The organisations that extract the most value from DAAP are those that treat it as a strategic programme, not a procurement transaction. Preparation, negotiation discipline, and ongoing governance separate seven-figure savings from seven-figure regrets."