The SAP Digital Access Adoption Program. How to pick the cheaper path and avoid the cost traps.

DAAP offers two paths onto document licenses, and in our reviews neither won consistently. The deciding number is your past indirect spend, and both paths must be priced on a measured document count.

What does the SAP Digital Access Adoption Program offer, and who can use it?

DAAP converts indirect access from a user based audit exposure into a document based license line, and SAP adds commercial incentives for doing it now. The exposure becomes a line in the budget instead of a finding in the next audit. Taking the offer is optional.

SAP's program material limits it to SAP ERP and SAP S/4HANA on premises. SAP S/4HANA Cloud is excluded. The deal runs in two steps: first you and SAP agree how many documents your current use creates, then you choose the commercial incentive that prices them.

How does SAP measure the starting volume?

SAP offers two measurement routes. Which one you use shapes how much control you keep over the number that everything else is priced from.

• Estimation. You and SAP's Global License Audit and Compliance team estimate the documents created by current use, with SAP's evaluation service and the estimation tool in SAP Note 2644139 for ECC or SAP Note 2644172 for S/4HANA. SAP provides this support free of charge.
• SAP Passport. You implement the support packages that carry SAP Passport, which traces each call end to end so SAP senders and external senders can be told apart. The technical guide is SAP Note 2738406, and SAP gives only limited implementation help.

With the estimation route, SAP's team produces the first number, so run your own count alongside it.

Which documents does the model count?

The model counts nine document types, and only when an external system causes one to be created in SAP. The count of those documents sets the license need, whatever the number of integrated users behind them. Reads, updates and deletes are not counted.

Knowing which family a flow lands in is what makes a count auditable. Our digital access guide covers the metric in full, and the document explainer defines each type.

What are the two DAAP paths and which one is cheaper?

The adoption path discounts the documents you license going forward. The conversion path credits what you already spent on user based licenses for indirect use toward document licenses. Which is cheaper depends on how much you already spent: low past indirect spend favors adoption, high past spend favors conversion.

How is the adoption path priced?

SAP's program material offers two incentive options on the measured volume:

• Option A. License at least 115 percent of the estimated documents, and pay a license fee only for the 15 percent growth. It must go on a standalone order form.
• Option B. License 100 percent of the estimated documents at a 90 percent discount on digital access. This can sit on the same order form as other SAP products.

Standard volume discounts apply to both options, but special discounts cannot be added on top.

Before volume discounts, Option B costs 10 percent of list for today's volume, and Option A costs 15 percent of list for today's volume plus headroom. If you expect to need more than 5 percent growth that you would otherwise buy at list, Option A starts to pay.

How is the conversion path priced?

Conversion trades perpetual licenses you already own for digital access, with their value credited against the new documents. SAP's material names sales and service order and purchase order processing licenses, S/4HANA Enterprise Management user licenses, SAP named user licenses, and add ons such as Screen Personas, Gateway and mobility apps as eligible.

There is a condition that changes the comparison. SAP requires 100 percent of the previous maintenance base to be carried forward, and the new annual support fee must equal or exceed the old one. So conversion puts your past spend to work, but your annual support bill will not fall.

Why does the baseline have to come first either way?

Both paths are priced against a document count. Get the count wrong and you pick the wrong path and then overpay on it, two errors from one omission.

Independent measurement cut the billable document estimate by 30 to 55 percent, median 44 percent, once internal and duplicate flows were excluded from the count SAP opened with. No other single factor moved the final price as much.

• Pull the real document counts from your own systems before SAP sizes the deal, and treat the opening estimate as a claim to verify.
• Exclude internal and duplicate flows. Internal flows, such as batch jobs running under an interface user, and duplicates, such as messages replayed by middleware, made up most of the correction.
• Audit the prior indirect spend as a separate exercise. That figure decides the path, while the document count decides the price.
• Check the credit valuation on the conversion path. A credit valued at a discounted rate instead of at what you paid can reverse the comparison, and SAP will not point that out.

A worked example: one company, three answers

Say a hypothetical manufacturer faces an SAP opening estimate of 10,000,000 documents a year with a list value of $2,500,000.

Its own measurement, after excluding internal and duplicate flows, lands at 5,600,000 documents, in line with the median correction we saw, with a list value of $1,400,000. Over the years it bought $1,500,000 of named users and order processing licenses to cover interfaces.

On SAP's opening count, adoption looks $750,000 cheaper than conversion. On the measured count the answer flips: conversion needs no new license fee, and the $1,500,000 of old licenses stop sitting idle. Support follows the same pattern, since adoption adds support on the new licenses while conversion carries the old support base over to cover them.

The third row shows the other trap. If SAP values the credit at 60 percent of what was paid, adoption wins again by $360,000. A company that had spent only $100,000 on indirect licenses would face $1,300,000 on conversion at the measured count, so adoption is the clear choice there.

How do you check your own position before SAP does?

1. List every interface that writes into SAP, with its technical user, message type and the document type it creates.
2. Measure volume by message type from middleware logs and IDoc monitoring in transaction WE02, over a full year so a peak season does not set the number.
3. Review technical users in SU01 and split any user that serves both an external interface and internal batch jobs.
4. Run the estimation tool from SAP Note 2644139 or 2644172 yourself, and compare its output with your own count before any meeting.
5. Rebuild the prior spend from your order forms and maintenance invoices: which licenses were bought to cover indirect use, and what you paid for each.

The measurement tools guide explains how to read the tool output.

What have we seen in recent DAAP negotiations?

Across roughly 25 to 35 SAP indirect and digital access engagements that I ran between 2024 and 2025, the conversion path beat the adoption path in roughly one in two cases. That result is why we never name a path before seeing a client's purchase history.

The split is structural. Adoption is priced off documents you will license going forward, so it suits a company with little historical indirect spend to reclaim. Conversion is priced off what you already paid for user based indirect access, so it suits a company that spent heavily under the old model.

• What predicted the winner. The purchase ledger, and nothing else we looked at.
• What did not. Industry, company size and SAP product mix.

The measured document volume almost never matched SAP's opening estimate, in either direction, and the correction came mostly from internal and duplicate flows. Digital access came up most often during an S/4HANA conversion, used by SAP as a bargaining point to enlarge the overall commitment. Our SAP indirect access pricing for 2026 page covers the price detail.

A path recommendation made before anyone has audited your prior indirect spend is a coin flip dressed as advice.

Why we do not default to the 90 percent discount

The advice buyers hear most often is to take the adoption discount while it lasts, because 90 percent off sounds like the best offer SAP makes on digital access. We disagree. In our reviews the two paths split almost evenly, which is what you would expect from a choice driven by purchase history rather than by any general rule.

A company holding many named users and order processing licenses bought for interfaces can do better with a full value conversion credit. Measure the count, rebuild the prior spend, and ask SAP to quote both paths on the same measured baseline.

Where is future digital access cost controlled?

Future cost is controlled at the integration layer, where documents are created, rather than at the license desk. Most billable growth comes from a handful of high volume integrations, and naming them early is what caps the forward cost.

The first volume becomes the floor

Whatever document volume you license at signature is the number the agreement carries forward. Sizing it against an unmeasured estimate locks that estimate in for the term, and under Option A the 15 percent headroom is calculated on it too.

Batching and deduplication reduce the count

The document count responds to interface design. Batching, deduplication and the choice of integration pattern change how many countable documents the same business activity creates.

• Remove replays. Middleware that retries a failed message can create the same order twice, and each copy counts.
• Summarize postings. An external billing system that posts one journal entry per transaction creates far more financial line items than one that posts a daily summary.
• Leave follow on documents to SAP. Only the initial document an external system creates is counted, so let SAP derive deliveries and postings from it instead of sending each one from outside.

What will the SAP account team say, and how should you answer?

• "The estimation tool output is your baseline." Ask for the document level extract behind it, and agree the number only after internal and duplicate flows are separated out.
• "Option B is the best deal we offer on digital access." It may be. Ask for it priced on your measured count and quoted next to a conversion with the credit valued at what you paid.
• "The credit follows our standard valuation." Ask for the valuation license by license, against the net price on your order forms, before you compare anything.
• "These terms are only available if you sign this quarter." Ask for the terms and their expiry date in writing. A deadline is a reason to finish the count quickly, not to accept SAP's number.

Which contract terms should you ask for in a DAAP deal?

• The measured baseline and how it was counted. Write the document volume, the measurement method and the excluded flows into the order form, so a later audit starts from the same number.
• Credit valuation per license. On conversion, list each license traded in and the credit it earns, so you can check it against what you paid.
• Treatment of unused credit. If the credit exceeds the documents you need, state where the balance goes, for example toward other SAP products on the same order.
• The resulting support fee. Conversion keeps the old maintenance base and cannot lower it, so have SAP state the new annual support figure before signature.
• Price protection on additional blocks. Fix the net rate for future document tiers for the term. Without it, crossing a tier boundary reopens the pricing you spent the negotiation settling.
• What happens on a move to RISE. Get in writing how the digital access licenses and any credit are treated if you later sign RISE with SAP.

How does DAAP fit an S/4HANA or RISE negotiation?

Treat digital access as one part of the larger S/4HANA or RISE deal rather than a side agreement. The wider the deal on the table, the more you have to trade against SAP's asks on digital access.

Sequence matters. The program covers SAP ERP and S/4HANA on premises contracts, so settle the conversion or adoption on that paper before any RISE signature. Our note on digital access in S/4HANA and RISE contracts covers the cloud side.

What to do next

1. Measure the document count from your own source systems. Exclude internal and duplicate flows before SAP sizes anything.
2. Audit the prior indirect spend separately. That is the figure that decides which of the two paths is cheaper for you.
3. Model both paths against the measured baseline. Never price them on the opening estimate, and never rely on SAP's comparison alone.
4. Name the high volume integrations. Fix the patterns that create countable documents, since that is where forward cost is controlled.
5. Write the credit, support fee and tier protection into the order form. Check each against your own numbers before signature.
6. Fold it into the S/4HANA or RISE negotiation. Our negotiation practice runs the measurement and models both paths with you.

Frequently asked questions