The conversion path beat the adoption path in roughly one estate in two, so any DAAP recommendation made before your prior indirect spend is measured is a coin flip
Two paths, one of which is cheaper for you. Which one it is depends on a number sitting in your own purchase history, and nobody advising you has looked at it yet.
Prepared by Redress Compliance · August 17, 2026 · SAP advisory. 25 to 35 SAP indirect and digital access engagements, 2024 to 2025.
Executive summary
The conversion path beat the adoption path in roughly one estate in two. Which makes a blanket recommendation either way wrong about half the time, whoever is giving it and however confidently.
The two paths are decided by your history, not by your forecast. Adoption discounts the documents you licence going forward, while conversion credits prior user based indirect spend. High past spend favors the second.
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.
Both paths have to be modeled against the same measured baseline. Comparing them on the vendor opening count picks the wrong path and inflates it at the same time, which is the compound version of the same mistake.
What are the two DAAP paths and which one is cheaper?
DAAP converts indirect access from a user based audit exposure into a document based licence line. It offers two routes to get there, and they are priced from different things.
The adoption path discounts the documents you licence going forward. The conversion path credits prior user based indirect spend toward document licences. Which is cheaper turns on how much you already spent.
| Factor | Adoption path | Conversion path |
|---|---|---|
| Cheaper when | Past indirect spend was low | Past indirect spend was high |
| What the incentive is | A discount on newly licensed documents | A credit for prior user licences |
| The risk it carries | An inflated forward baseline, locked for years | The credit valued below what you actually paid |
| Your lever | The measured document count | The audited historical spend |
| How often it won | Roughly half the estates reviewed | Roughly half the estates reviewed |
A path recommendation made before anyone has audited your prior indirect spend is a coin flip dressed as advice. The two paths split almost evenly across the estates reviewed, which is what you would expect from a choice driven by purchase history rather than by industry. The number that decides it is in your own records.
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 overpay on it, which is 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. That is the single largest lever on the final price.
- Pull the real document counts from your own systems before SAP sizes the deal, treating the opening estimate as a claim to verify.
- Exclude internal and duplicate flows, which is where most of the 30 to 55 percent correction comes from.
- Audit the prior indirect spend as a separate exercise, because that figure decides the path while the document count decides the price.
- Check the credit valuation on the conversion path, since a credit granted at a discounted token rather than at real value quietly reverses the comparison.
The SAP digital access recommendations
The document baseline method, both DAAP paths modeled against it, and the clause language that caps forward growth at the integration layer.
Get the brief →What the digital access engagements showed
Across roughly 25 to 35 SAP indirect and digital access engagements Fredrik Filipsson ran between 2024 and 2025, the conversion path beat the adoption path in roughly half of estates.
That is the finding that matters most, because it makes the standard advice unusable. A recommendation that names a path before it has seen your purchase history is right about as often as a coin.
The reason is structural. The adoption path is priced off documents you will licence going forward, so it favors an estate with little historical indirect spend to reclaim.
The conversion path is priced off what you already paid for user based indirect access, so it favors the estate that spent heavily under the old model. Nothing about industry, size, or product mix predicts which of those you are. Only the ledger does.
Underneath the path question sits the count. The measured document volume almost never matched the SAP opening estimate, and independent measurement cut the billable figure by 30 to 55 percent, median 44 percent, once internal and duplicate flows were excluded. The model counts nine document types, and the count rather than the number of integrated users sets the licence need.
Digital access was raised most often during an S/4HANA conversion, used as leverage to enlarge the overall commitment. That timing is the buyer opportunity as much as the vendor one, because a wider deal carries more to trade. The metric reference sits at the digital access guide and the pricing detail at SAP indirect access pricing.
- Your quote benchmarked against 500,000+ real closed deals, adjusted for size, region, and industry
- Both paths priced against measured document volume rather than the vendor count
- Every risky clause flagged with the exact quote, the page, and the replacement language
Where is future digital access cost actually controlled?
At the integration layer, where documents are created, rather than at the licence 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 licence at signature is the number the agreement carries forward. Sizing it against an unmeasured estimate locks that estimate in for the term.
Batching and deduplication reduce the count
The document count responds to interface design. Batching, deduplication, and integration patterns change how many countable documents the same business activity creates.
Price protection on future tiers
Negotiate protection on future document tiers so growth does not reprice the whole estate. Without it, crossing a tier boundary reopens the pricing you spent the negotiation settling.
What the nine document types cover
The counted categories group into three families, and knowing which one a flow lands in is what makes a count auditable.
- Sales documents, the orders and related sales records created through external channels.
- Invoice and financial documents, the billing and finance records generated by connected systems.
- Purchase, manufacturing, and logistics documents, which make up the remaining counted categories across the nine types.
What the SAP engagements showed, 2024 to 2025
Across roughly 25 to 35 SAP indirect and digital access engagements:
Which makes a blanket recommendation either way wrong about half the time, since purchase history rather than anything general decides it.
Off the SAP opening document estimate after independent measurement excluded internal and duplicate flows.
The full range of that correction ran 30 to 55 percent, and the measured document count almost never matched the opening estimate in either direction.
Digital access was raised most often during an S/4HANA conversion, used as leverage to enlarge the overall commitment rather than settled on its own.
Watch the briefing · 4:39Digital Access Travels With YouNine document types, roughly one FUE per thousand documents, and why the first volume becomes the floor.
Your first five moves
- Measure the document count from your own source systems, excluding internal and duplicate flows, before SAP sizes anything.
- Audit the prior indirect spend separately, because that is the figure that decides which of the two paths is cheaper for you.
- Model both paths against the measured baseline, never against the opening estimate and never on the vendor comparison alone.
- Name the high volume integrations and fix the patterns that create countable documents, since that is where forward cost is controlled.
- Fold it into the S/4HANA or RISE negotiation. The negotiation practice runs the measurement and models both paths with you.
Frequently asked questions
What is the SAP Digital Access Adoption Program?
A structured SAP offer that converts indirect, user based exposure into document based licences, with commercial incentives to move now. It replaces an unpredictable audit finding with a budgeted line item.
Which DAAP path is cheaper?
It depends entirely on your prior indirect spend. The conversion path beat the adoption path in roughly one estate in two across the engagements reviewed, so neither is a default.
Why can nobody tell you the path in advance?
Because the deciding number is in your purchase history rather than in anything general about SAP, your industry, or your size. Adoption favors low past spend, conversion favors high past spend.
How wrong is the opening document count?
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.
How many document types does the model count?
Nine. The count of documents created in SAP by external systems, rather than the number of integrated users, is what sets the licence need.
What happens if you compare paths on the vendor number?
You make two errors from one omission. The inflated count can flip which path looks cheaper, and it then prices the path you picked against volume you do not have.
Is DAAP compulsory?
No. It is an offer rather than an obligation, and it is best negotiated inside a wider S/4HANA or RISE deal where there is more scope to trade.
When does SAP usually raise digital access?
Most often during an S/4HANA conversion, used as leverage to enlarge the overall commitment. That timing cuts both ways, because a wider deal gives the buyer more to trade as well.
Where is future digital access cost controlled?
At the integration layer where documents are created, not at the licence desk. Most billable growth comes from a handful of high volume integrations, and batching and deduplication reduce the count.
Why does the first document volume matter so much?
Because it becomes the floor the agreement carries forward. A volume sized against an unmeasured estimate locks that estimate in for the term, which is the trap in every consumption style conversion.
