The SAP Digital Access Adoption Program — what it actually buys

The Digital Access Adoption Program, usually abbreviated DAAP, is the named structure under which SAP offers existing customers a discounted conversion from the old indirect-access exposure to the Digital Access document model. It has existed in named form since 2018 and has been revised quietly several times since. In 2026 it remains the route most enterprises will eventually take to settle the long tail of indirect-access risk built up across two decades of integration. It is not a giveaway, and it is not a settlement template. It is a structured commercial offer with two attractive headline numbers, several quieter consequences, and a small number of questions every buyer needs answered before signing the paper.

What DAAP actually offers

The headline structure of DAAP, simplified to the elements that matter commercially: an amnesty on historical indirect-access usage in exchange for a baseline Digital Access purchase priced per document, a discount on the per-document rate that is significantly below the negotiated list, and an allowance for the buyer to count a certain proportion of documents as “non-chargeable” under defined categories (initial creation by certain non-SAP source systems, internal back-and-forth between SAP systems, etc.). The buyer commits to a baseline annual document volume at the discounted rate, and the agreement covers both the historical exposure and a fixed-volume forward subscription.

The mechanics are not a secret — they are described in SAP’s own published Digital Access documentation, summarised on the SAP Digital Access topic page. The negotiation question is not whether the structure exists. It is whether the structure, on the terms SAP offers them to your specific situation, is the right answer for your specific landscape.

The two attractive numbers

The two numbers SAP will put forward to make the offer attractive: first, the percentage discount on the per-document price, which can be in the 65 to 90 per cent range depending on volume and timing; second, the percentage of the calculated indirect-access opening claim that is waived as part of the conversion. The combined headline economics — "we are reducing your exposure by eighty per cent and giving you a deep discount on the forward subscription" — sound very attractive in isolation. In every DAAP we have worked across our engagements, the attractive headline is real but is not the most important number on the paper.

The quieter numbers on the same page

The numbers that matter as much or more: the baseline annual document volume the buyer commits to, the price escalator on years two through five, the definition of what counts as a chargeable document, the carve-outs for system-to-system traffic, the treatment of read-only access, and the renewal mechanism at the end of the initial term. We have seen DAAP agreements where the buyer accepted an attractive year-one rate against an inflated baseline volume that locked in years of overpayment, and DAAP agreements where the per-document price was reasonable but the carve-out definitions were so narrow that ordinary business traffic was reclassified as chargeable mid-cycle.

The baseline volume question

The baseline is the most important single number. It is the volume the buyer is contractually committed to consume per year, priced at the discounted per-document rate. If the buyer’s actual document volume is below the baseline, the buyer pays the baseline anyway. If the buyer’s actual document volume is above the baseline, the overage is priced at the overage rate, which is typically higher than the baseline rate. The right baseline is the actual document volume measured against the negotiated definitions, with a small contingency for genuine growth. The wrong baseline is the volume SAP proposes, which is typically derived from a conservative reading of the buyer’s integration topology and is often substantially higher than actual.

The document categories that matter

Digital Access counts nine document types: sales documents, purchase documents, invoice documents, manufacturing documents, material documents, quality documents, time-management documents, financial documents, and service documents. The per-document price applies per category, with different categories carrying different rates. The chargeable-versus-non-chargeable question turns on which system created the document, which system updated it, and whether it represents a logical “initial creation” or a derived event. The category-by-category mechanics are in our counting digital access documents piece.

The negotiation work is to argue each category individually. A landscape with heavy purchase-order automation from a third-party MRP system will produce a very different baseline depending on whether those purchase documents are read as initial creations (chargeable) or as system-to-system transfers (often carved out). Each category needs an evidenced position.

The one-way door question

DAAP is described by SAP as an “adoption” programme, and it is. Once the buyer has signed a DAAP agreement, the historical named-user indirect-access exposure is settled and the buyer has committed to the per-document model going forward. There is no contractual route back to a pure named-user reading. The buyer’s integrations are now priced per document for the life of the agreement and its successors. This is not necessarily a bad outcome — for many landscapes, the per-document model is more predictable and more economical than a contested named-user reading — but it is a structural choice that should be made deliberately rather than as a sequel to accepting a headline discount.

The negotiation playbook for a DAAP offer

The negotiation pattern we apply on a DAAP offer, in order:

First, build the independent measurement. Run the document-volume measurement on the buyer side, against the negotiated definitions, before accepting any baseline from SAP. The measurement is technical work, not a negotiation step; the output is the buyer’s view of what the actual chargeable volume looks like under each plausible definition.

Second, argue the definitions before the price. The per-document price is meaningless if the document count is inflated. The definitions and carve-outs are where the real money is. We typically secure category-level carve-outs that reduce the baseline by 25 to 45 per cent against SAP’s opening position.

Third, negotiate the baseline against the measured volume plus a defined growth allowance, not against SAP’s opening proposal. The baseline should be the buyer’s number, with the SAP number reserved as an overage threshold.

Fourth, fix the price escalator. The year-one rate is attractive; the year-three and year-five rates need to be in the contract at a defined cap, not subject to renegotiation.

Fifth, document the historical-amnesty scope explicitly. The amnesty should cover all integrations active in the audited period, not only those listed in an exhibit. Exhibit-limited amnesties leave residual exposure that surfaces in the next cycle.

When DAAP is the right answer, and when it is not

DAAP is the right answer when the buyer has a large, complex integration topology with a customer-facing element, when the indirect-access opening claim is in the eight-figure-plus range, and when the document volume is genuinely measurable. It is the wrong answer when the buyer’s integrations are predominantly read-only or backend system-to-system, when the document volume is small relative to the named-user count, or when the buyer has a credible substantive defence under the named-user reading. Across our engagements, we recommend DAAP for roughly 55 to 65 per cent of indirect-access matters and recommend a substantive defence under the named-user model for the remainder. The decision is case-by-case, not policy. The detail is in the Digital Access Conversion Playbook white paper and the distributor digital access conversion case file.

If you have a DAAP offer on the table, or are facing an indirect-access notification where DAAP will be the SAP-proposed settlement vehicle, the priority is the independent document-volume measurement before any baseline is accepted. We work alongside in-house procurement and basis teams under engagement letter; the first conversation is at no cost. The Digital Access negotiation service page describes how we structure the work, and the middleware risk piece is the companion read for the upstream context.