SAP / Digital Access
SAP / Digital Access

SAP Digital Access Adoption Program. Evaluated.

SAP's Digital Access Adoption Program turns indirect access into a document based line item. Evaluate it on a measured baseline, not SAP's first count, and it removes risk at a fair price.

Contact Us SAP Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP's Digital Access Adoption Program converts indirect access from a user based audit risk into a document based line item. Done well, it removes exposure at a fair price. Done badly, it locks in an inflated document baseline for years. This guide shows the difference.

Key takeaways

  • DAAP moves indirect access from user based licensing to a document based model counting nine SAP document types.
  • The program offers two paths, an adoption discount on future documents and a conversion credit for past indirect spend.
  • SAP's first document count routinely overstates billable volume by counting internal and duplicate flows.
  • An independent document baseline is the single largest lever on the final price.
  • DAAP is an offer, not an obligation, and is best negotiated inside a wider S/4HANA or RISE deal.
  • Future cost is controlled at the integration layer, where documents are created, not at the license desk.

Indirect access is the most disputed topic in SAP licensing. The 2018 shift to a digital access model was meant to make it measurable. DAAP is the on ramp SAP built to move customers across.

The program is genuinely useful. It also rewards buyers who measure and punishes buyers who accept SAP's first number.

What is the SAP Digital Access Adoption Program?

DAAP is SAP's structured offer to convert indirect, user based exposure into document based licenses, with commercial incentives to adopt now.

The document based model

Digital access prices on documents created in SAP by external systems. SAP counts nine document types. The count, not the number of integrated users, sets the license need.

  • Sales documents: orders and related sales records created through external channels.
  • Invoice and financial documents: billing and finance records generated by connected systems.
  • Purchase, manufacturing, and logistics documents: the remaining counted categories across the nine types.

The two DAAP paths

The adoption path discounts documents you license going forward. The conversion path credits prior user based indirect spend toward document licenses. The cheaper path depends on your volume and history.

Why SAP built it

SAP wanted to retire years of indirect access disputes and create a forecastable metric. The SAP software use rights documents set out how the model applies.

How does the DAAP conversion math work?

The math turns on three numbers: your measured documents, the path you choose, and the credit SAP grants for past spend.

DAAP adoption path versus conversion path

Factor Adoption path Conversion path
Best whenLow past indirect spendHigh past indirect spend
IncentiveDiscount on new documentsCredit for prior user licenses
Key riskInflated forward baselineCredit valued below real spend
Buyer leverMeasured document countAudited historical spend

Measure the document baseline first

Pull the real document counts from your own systems before SAP sizes the deal. Exclude internal and duplicate flows. This number anchors everything.

Value the credit honestly

On the conversion path, check that SAP credits your prior indirect spend at its real value, not a discounted token. The credit is negotiable.

What indirect access risk is DAAP meant to solve?

Indirect access is the use of SAP data by people or systems that do not hold a named SAP user license. It is the source of the largest surprise SAP bills.

The history of the dispute

High profile court cases in the late 2010s established that indirect use could trigger license fees. SAP then moved to the document model to make the exposure measurable rather than litigated.

From audit risk to line item

DAAP converts an unpredictable audit finding into a budgeted, forecastable cost. That is a real improvement, provided the baseline is accurate and the forward growth is controlled.

Where the common advice on the Digital Access Adoption Program is wrong

The common advice, often from SAP and some resellers, is that DAAP is a one time cleanup you should accept quickly to close indirect access risk. We disagree. In roughly six out of ten engagements we have run, the program was presented with a document count we measured down by a third or more, and a path recommendation that suited SAP rather than the buyer. The buyer side move is to measure your own documents first, model both paths independently, and fold digital access into a wider S/4HANA negotiation where you hold more levers. Speed favors SAP. Measurement favors you.

Editorial photograph of an analyst reviewing system integration document flows on a dashboard
Most billable document growth comes from a handful of high volume integrations. Naming them early is how buyers cap future digital access cost.
44%
Median cut to SAP document estimate
9
Document types SAP counts
1 in 2
Estates where conversion path won

Source: Redress Compliance advisory engagement file, 2024 to 2025.

DAAP is not a form to sign. It is a measurement exercise that SAP would prefer you skip. The baseline is the whole game.

What buyer side moves work on a DAAP offer?

Four moves consistently improve a digital access outcome.

Move one. Measure independently

Run your own document count from source systems. Treat SAP's estimate as a claim to verify, not a fact to accept.

Move two. Bundle with the bigger deal

Fold digital access into the S/4HANA or RISE with SAP negotiation. More scope means more to trade.

Move three. Control creation at the source

Reduce billable documents by fixing integration patterns. Batching, deduplication, and interface design lower the count.

Move four. Cap forward growth

Negotiate price protection on future document tiers so growth does not reprice the whole estate.

Suggested reading

How should a buyer evaluate a DAAP proposal?

Evaluate it as a measurement and modeling exercise, in a fixed order.

Count, then compare

Establish the measured baseline, then model both paths against it. Never compare paths on SAP's number alone.

Time it with leverage

Bring DAAP into a moment where you have leverage, such as an S/4HANA conversion or a renewal, rather than under an audit clock.

What should a buyer do next?

  1. Extract the real document counts for all nine SAP document types from your own source systems.
  2. Exclude internal and duplicate flows to reach a defensible billable baseline.
  3. Model both the adoption path and the conversion path against that baseline.
  4. Value any conversion credit against your true historical indirect spend.
  5. Identify the high volume integrations that drive document growth and plan to control them.
  6. Fold digital access into a wider S/4HANA or RISE negotiation where possible.
  7. Negotiate price protection on future document tiers.
  8. Engage independent SAP advisory before accepting any digital access figure.

Frequently asked questions

What is the SAP Digital Access Adoption Program?

The Digital Access Adoption Program, or DAAP, is SAP's framework for moving customers from user based licensing of indirect access to the document based digital access model. It offers two paths, a credit on past use or a discounted purchase of documents, to regularize indirect access exposure.

How is SAP digital access measured?

Digital access is measured by documents created in SAP through external systems. SAP counts nine document types, including sales, invoice, purchase, and financial documents. The count drives the license requirement, not the number of external users touching the data.

What are the two DAAP options?

The two options are the adoption path and the conversion path. The adoption path gives a discount on documents you license going forward. The conversion path credits your existing user based indirect spend toward document licenses. Which is cheaper depends entirely on your document volume and past spend.

Does DAAP remove indirect access risk?

Partly. DAAP regularizes the historical exposure SAP can claim, but it does not stop future document growth from increasing cost. It converts an audit risk into a measurable, forecastable line item, which is usually better, but only if the baseline is accurate.

What is the biggest DAAP cost trap?

Accepting SAP's document count without an independent measurement. SAP's estimate often overstates billable documents by counting internal or duplicate flows. A measured baseline is the single largest lever on the final number.

Is DAAP mandatory?

No. DAAP is an offer, not an obligation. You can stay on user based indirect licensing, though SAP is steering customers toward the document model and prices it to encourage adoption, especially alongside an S/4HANA move.

Should DAAP be negotiated with the S/4HANA conversion?

Often yes. Bundling digital access into a wider S/4HANA or RISE negotiation gives more levers and more scope to trade. Resolving it in isolation, under audit pressure, usually costs more.

Can you exit or reduce digital access later?

Document licenses are typically perpetual or subscription entitlements that do not shrink automatically. You reduce future cost by controlling document creation at the integration layer, which is an architecture decision as much as a licensing one.

SAP RISE Negotiation Guide

The full SAP RISE negotiation guide from the SAP Practice.

SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the SAP RISE TCO calculator against your estate in under five minutes.
Open the Tool →

Indirect access is not a trap if you measure it. The buyers who lose are the ones who sign SAP's document count without checking their own.

Fredrik Filipsson
Co Founder and Group CEO, Redress Compliance