When DAAP makes sense and when it does not.

The Digital Access Adoption Programme, commonly known as DAAP, is one of the most actively promoted SAP programmes for customers with indirect access exposure. The pitch is straightforward. Move from named user licensing to the document model, accept a multi year commitment, and receive a meaningful discount on the published document pricing. For some buyers this is the right answer. For others it is a costly commitment that locks in exposure that did not need to be accepted. This paper sets out the situations where DAAP makes sense, the situations where it does not, the commercial structure that the buyer should understand, and the decision framework that produces a defensible choice.

01.What DAAP actually is

The Digital Access Adoption Programme, commonly abbreviated as DAAP, is the SAP programme that allows existing customers to transition from named user licensing for indirect access to the document based digital access pricing model. The programme has been in market since 2018 in various forms and has evolved over time. The current version offers a discount on the document pricing in exchange for committing to the document based model and to a defined audit and reporting framework.

DAAP is positioned by SAP as a remediation pathway for customers with indirect access exposure under their existing licensing. The discount can be material, the audit framework provides certainty, and the move to the document model aligns the licensing with how modern integrated estates actually work. For some customers, DAAP is the right answer. For others, DAAP is a costly commitment that locks in exposure that did not need to be accepted.

The decision to enter DAAP should be made on the basis of the customer's specific exposure profile, the alternative remediation options available, and the longer term commercial direction. The default position of the SAP account team will often be to recommend DAAP because it produces a clean and predictable revenue line. The buyer's position should be more nuanced and should reflect the buyer's actual interests rather than the supplier's.

02.When DAAP makes sense

DAAP makes sense in five specific situations. The first is when the customer has significant unresolved indirect access exposure under existing licensing, the exposure has been quantified, and the cost of resolving it through DAAP is materially lower than the cost of resolving it through any other available pathway. In this situation, DAAP is a genuine remediation tool and the discount produces real value.

The second situation is when the customer's integration architecture is genuinely document heavy and the document model fits the operating reality. Buyers whose estates run high volumes of sales orders, purchase orders, invoices, and similar documents through integrations to non SAP systems often find that the document model is the natural fit and that DAAP is the efficient route into it.

The third situation is when the customer wants the audit certainty that DAAP provides. The DAAP framework specifies how SAP can audit the document counts, what reporting is required, and what the dispute resolution process looks like. For customers who prioritise certainty over absolute cost minimisation, the framework has value.

The fourth situation is when the customer's roadmap includes additional integrations that would otherwise create new exposure under the existing licensing model. DAAP can be the right answer when the roadmap will scale the document volume materially, because the unit pricing under DAAP is lower than under the standard digital access framework.

The fifth situation is when the customer is approaching a RISE conversion and the indirect access exposure needs to be resolved before the conversion. DAAP can be the bridge that takes the exposure off the table before the RISE contract is signed, simplifying the negotiation and reducing the contractual scope.

03.When DAAP does not make sense

DAAP does not make sense in five specific situations. The first is when the customer's exposure under existing licensing is limited or arguable. Buyers sometimes enter DAAP on the assumption that the exposure is real and material, when in fact the licensing position is defensible and the DAAP commitment locks in cost that did not need to be paid. The buyer should test the exposure thoroughly before accepting DAAP as the remedy.

The second situation is when the customer's integration architecture is genuinely document light and the move to document pricing increases the cost rather than reducing it. Buyers with mostly human user driven integrations may find that the document model is the wrong fit and that the named user model produces lower long term cost.

The third situation is when the customer has alternative remediation pathways that produce a better outcome. Technical remediation, renegotiation under existing licensing, or restructured integration architectures can sometimes resolve the exposure at lower cost than DAAP. The buyer should evaluate the alternatives before committing.

The fourth situation is when the customer is concerned about the long term direction of the document pricing model. SAP has adjusted the document pricing framework periodically, and the trajectory has been upward. Buyers who are sceptical of the supplier's pricing direction may prefer to keep optionality rather than commit to a multi year DAAP arrangement.

The fifth situation is when the customer is in the early stages of a RISE conversion and the indirect access exposure can be bundled into the RISE negotiation. In this case, DAAP can be the wrong remedy because the RISE negotiation produces better commercial leverage than the DAAP discount.

04.The commercial structure of DAAP

DAAP is structured as a discount on the published document pricing in exchange for a multi year commitment to the document model. The discount has varied over time and varies by region, by customer size, and by negotiation, but it is typically meaningful when expressed against the list price. The commitment is to the model rather than to a specific document volume, although the contract usually includes provisions for true ups if the actual volume exceeds the baseline.

The contract structure includes a baseline document count, a defined audit and reporting framework, and a true up process for documents above the baseline. The baseline is set by the SAP audit of the customer's current document volume, and the buyer should verify the audit basis before accepting the baseline.

The pricing for documents above the baseline is set in the contract and is typically at the discounted DAAP unit price rather than at the list price. The buyer should negotiate the unit price for incremental documents because that is where the cost increase will land if the volume grows.

The contract usually includes a renewal mechanism at the end of the initial term. The renewal pricing is the place where buyers most often face surprises, and the contract should establish constraints on renewal pricing that protect the buyer from arbitrary increases.

05.The DAAP entry process

The DAAP entry process has four steps and each requires buyer side discipline. The first step is the exposure assessment. SAP will conduct an audit of the customer's document volume and indirect access exposure. The buyer should be present in this audit, should challenge the methodology where appropriate, and should not accept the audit findings without independent verification.

The second step is the commercial negotiation. The discount level, the baseline, the incremental pricing, the audit cooperation provisions, and the renewal mechanism are all negotiable. The default proposal that SAP brings will reflect the supplier's preferred position. The buyer should run a structured negotiation that addresses each element.

The third step is the contract drafting. The DAAP contract is a defined SAP template but the template includes negotiable provisions. The buyer should review the contract clause by clause, should require changes where the language is ambiguous, and should ensure that the audit cooperation provisions are workable in practice.

The fourth step is the operational implementation. The DAAP contract requires the buyer to maintain document counting and reporting infrastructure. The infrastructure should be in place before the contract takes effect, and the operational team should be trained on the reporting requirements. The post signature failures most often occur because the operational implementation was treated as a tail end activity rather than as part of the contract delivery.

06.The decision framework

The decision framework brings the assessment together into a structured choice. The first input is the quantified exposure under existing licensing. This is the baseline against which any DAAP discount must be evaluated.

The second input is the cost of DAAP over the contract term, including the baseline cost, the projected incremental cost based on the buyer's roadmap, and the projected renewal cost. The full term cost is what matters, not the headline first year cost.

The third input is the cost of alternative remediation pathways. Technical remediation, renegotiation under existing licensing, RISE bundling, and other paths should each be costed and compared against DAAP.

The fourth input is the strategic alignment with the buyer's roadmap. The buyer should consider whether DAAP fits the longer term direction of the SAP relationship and whether the multi year commitment leaves the buyer in the right strategic position at the end of the term.

The fifth input is the executive risk appetite. DAAP locks in a commercial structure for a defined period. Buyers with low appetite for multi year commitments may prefer the optionality of remaining outside DAAP even when the headline comparison favours entry. The decision is for the executive committee, supported by the analytical inputs.

DAAP is the right answer when the exposure is real, the document model fits, and the discount is meaningful. DAAP is the wrong answer when any of the three is missing. The default recommendation is the supplier's preferred position, not the buyer's.

07.Conclusion

DAAP is a useful tool for some customers and a costly trap for others. The decision should be made on the basis of the quantified exposure under existing licensing, the full term cost of DAAP, the cost of alternative remediation pathways, the strategic alignment with the buyer's roadmap, and the executive risk appetite. The buyers who treat DAAP as the default response to an SAP audit finding consistently commit to terms that were not optimal. The buyers who run a structured assessment consistently produce a decision that fits the actual situation, whether that decision is to enter DAAP or to remain outside it. The work to do the assessment well is modest and the consequences of getting the answer right are measured in millions over the term.