How SAP Digital Access Impacts S/4HANA and RISE with SAP Contracts

What SAP Digital Access Actually Is

SAP Digital Access — formally known as Document-based Digital Licence Compliance (DDLC) — is the licensing metric SAP introduced in 2018 to resolve the chronic ambiguity of indirect access. Before DDLC, SAP's licence agreements required a named user for every individual who accessed SAP data, including through third-party systems. This meant a Salesforce CRM user who triggered a sales order in SAP could theoretically require an SAP licence. The resulting dispute history was ugly — SAP's £54 million settlement with Diageo in 2017 was the most public example, but it was far from isolated.

DDLC replaced the user-based indirect access model with a document-based one. Instead of licensing people, you now license the business documents that external systems create in SAP: sales orders, purchase orders, invoices, delivery documents, and a defined list of others. Each document type has a per-document price. Volume packs are sold in tiers — the more you commit, the lower the per-unit rate — and SAP also offers unlimited flat-fee licences benchmarked at approximately 10% of your total S/4HANA licence value per year.

The critical point most procurement teams miss: DDLC did not eliminate indirect access risk. It monetised it. The obligation to license external system interactions did not disappear — it was converted into a measurable, auditable volume commitment that SAP's automated tooling can now enforce with precision.

How DDLC Pricing Works in Practice

SAP sells Digital Access licences in two primary structures. The first is per-document volume packs, typically sold in blocks of 1,000 documents per year, with tiered pricing that rewards higher commitments. At small volumes — say 1,000 to 5,000 documents — unit prices are relatively high. At millions of documents annually, the per-unit cost can fall well below $1. The second structure is an unlimited flat-fee licence, which SAP benchmarks at roughly 10% of your annual S/4HANA licence value. For a large ERP deployment, this can represent $500,000 to $3 million per year.

SAP uses SAP Passport logs and dedicated audit scripts to detect which documents were created by external systems rather than native SAP users. The technical traceability has improved significantly — SAP's audit teams can pull this data retroactively, meaning the exposure begins accumulating from the moment external systems go live, not from the moment you sign a DDLC agreement.

Two negotiated settlement options we have seen SAP offer in disputes are illuminating. Option A — the "115% option" — requires you to licence 115% of your estimated indirect document volume but charges you only for the 15% overage buffer, delivering an effective 85% discount on the excess. Option B — the "90% discount option" — licences 100% of current usage at 10% of list price. Both options confirm one thing SAP would prefer buyers not know: DDLC list prices are almost never what sophisticated buyers actually pay, but only those who negotiate from a position of knowledge access these rates.

Where S/4HANA On-Premise and RISE Contracts Diverge

The relationship between Digital Access and your contract changes significantly depending on whether you are on S/4HANA on-premise, S/4HANA Private Edition (formerly RISE with SAP Private Edition, now rebranded as SAP Cloud ERP Private), or S/4HANA Public Cloud.

S/4HANA On-Premise

On S/4HANA on-premise, Digital Access is a separately negotiated and separately invoiced item. It is not automatically included in your standard named-user licence fees. If you have not explicitly purchased DDLC entitlements and your third-party systems — Salesforce, ServiceNow, Workday, Coupa, custom web portals, EDI connections — are creating documents in SAP, you are accumulating unlicensed indirect access exposure. The risk accumulates silently and grows with every integration go-live.

RISE with SAP (Private Edition)

SAP markets RISE with SAP as an "all-inclusive" bundle, and its sales narrative frequently implies that Digital Access is covered. The actual contractual reality is more nuanced. RISE subscription agreements do include some Digital Access allowances, but the included volume is typically sized to match the user footprint at deal close — not your actual integration landscape. High-volume external touchpoints, particularly EDI connections processing millions of purchase orders or logistics documents annually, routinely exceed the included entitlements.

The critical contractual protection most RISE buyers do not obtain: written confirmation from SAP — not from your account executive verbally, but as a contract amendment — that specific integrations and their expected document volumes are covered within the subscription fee. Without this, you are exposed to a DDLC claim that SAP can raise at any annual true-up or at renewal.

SAP's fiscal year ends September 30. Q4, running July through September, is when quota pressure peaks and deal terms are most negotiable. This is also when SAP is most likely to offer DDLC coverage as a concession to close a RISE deal. Buyers who understand this timing dynamic can extract significantly better contractual protection than those who engage outside Q4.

S/4HANA Public Cloud

In the Public Cloud (SaaS) model, SAP's standard integration APIs are designed with DDLC in mind, and many common integration scenarios are covered within the subscription. However, custom integrations that create documents outside the standard API surface can still trigger DDLC obligations. The key verification step is confirming with SAP in writing which APIs generate licensable documents and which do not.

The Audit Mechanism: How SAP Detects Exposure

SAP's audit process for Digital Access is technically precise. SAP Passport is a tracing protocol embedded in SAP's NetWeaver infrastructure that records the origin system identifier for every business document created. When an external system calls an SAP BAPI, RFC, or web service to create a document, the SAP Passport captures the calling system's client ID. SAP's audit scripts correlate these client IDs against your licensed system landscape to identify documents created by external systems that are not covered by DDLC entitlements.

What makes this particularly consequential is retroactivity. SAP Passport logs are retained in SAP systems and can be extracted going back multiple years. An audit that begins in 2026 can produce a compliance claim covering indirect access from 2023 or 2024, before any DDLC conversation occurred. We have seen this pattern repeatedly — organisations that assumed their RISE subscription covered all integrations receiving retroactive claims covering 24 to 36 months of unlicensed document creation.

A Client Pattern We See Regularly

A mid-market manufacturing company — approximately 4,000 SAP users — signed a RISE with SAP Private Edition agreement in 2023. The deal was negotiated on a tight timeline driven by the EHP 6 mainstream maintenance deadline pressure. The RISE subscription covered the standard user footprint. The company had twelve active integrations: Salesforce for CRM (generating sales orders), a Coupa instance for procurement (generating purchase orders), EDI connections with three major customers (generating inbound delivery documents), and several legacy custom applications feeding inventory and financial posting documents.

None of the integration document volumes were scoped into the DDLC entitlement within the contract. The company's account executive had verbally confirmed that RISE "covers everything." At the first annual review, SAP's internal licence measurement tools — deployed as part of the RISE infrastructure management — surfaced 2.3 million unlicensed indirect documents from the prior twelve months. SAP's initial claim, at list price, exceeded €1.8 million. The eventual negotiated settlement was significantly lower, but legal and advisory costs, business disruption, and the distraction of senior management from strategic priorities consumed resources that a properly negotiated contract would have avoided entirely.

The lesson is not that RISE is a bad model. It is that RISE contracts require the same rigorous licence scoping as on-premise agreements, and that verbal assurances from account executives have no contractual standing.

What to Negotiate Before Signing

Digital Access contract protection requires specific language, not general assurances. The following items should be non-negotiable in any S/4HANA or RISE negotiation where third-party integrations exist.

Integration Landscape Annexe

Require a signed annexe listing every third-party system that will create documents in SAP, the document types each system generates, and the estimated annual volume for each. SAP must confirm in writing — within the body of the agreement or a signed amendment — that these integrations and volumes are covered by the licence fees being paid. This annexe does two things: it limits your exposure to the scoped landscape, and it creates a contractual baseline for any future dispute.

DDLC Volume Cap or Unlimited Entitlement

If your integration landscape generates high volumes, negotiate an unlimited DDLC entitlement rather than a volume cap. The benchmark price of approximately 10% of your annual S/4HANA licence value is a starting point, not a ceiling. Properly contested, we have seen unlimited DDLC entitlements agreed at 6 to 7% of licence value for customers with strong negotiating leverage — typically those signing large, multi-year RISE commitments or those with credible alternative options.

Measurement Methodology Agreement

The contract should specify which SAP tool will be used to measure Digital Access consumption, the frequency of measurement, and the process for challenging disputed measurements. Without an agreed measurement methodology, SAP retains the right to define the rules of the audit after the fact — a position that consistently favours the vendor.

New Integration Rights

Negotiate the right to add new integrations and new document volumes within a defined threshold — say 20% above the scoped baseline — without triggering additional DDLC charges during the contract term. Enterprise integration landscapes grow, and a rigid volume cap that cannot accommodate legitimate business growth creates a ratchet mechanism that benefits SAP at every renewal.

Compatibility Rights Verification

Prior to 2025, some SAP customers relied on compatibility rights — contractual provisions from legacy agreements that covered certain indirect access scenarios without DDLC charges. Many of these compatibility rights expired on December 31, 2025, for EHP 0–5 customers. If you have been relying on compatibility pack provisions, you need to verify explicitly whether those rights carry forward into your S/4HANA or RISE contract, or whether you are now exposed to DDLC charges on integrations that were previously covered.

Five Priority Actions for SAP Customers

1. Map Your Integration Landscape Before Any SAP Conversation Begins. Know which external systems create documents in SAP, which document types they generate, and approximate annual volumes before SAP raises the topic. Buyers who arrive at negotiations with this data in hand are not reactive — they control the conversation.

2. Demand Written DDLC Coverage, Not Verbal Assurance. Account executive promises are not contracts. Any DDLC coverage claim must appear in the signed agreement or a signed amendment. If SAP resists putting coverage commitments in writing, that resistance is your most important signal about the actual terms being offered.

3. Run a DDLC Measurement Before SAP Does. Use SAP's own measurement tools — or engage an independent SAP licensing specialist — to quantify your current indirect access exposure before SAP raises the topic in an audit or renewal context. Knowing your own number gives you negotiating leverage; not knowing it hands SAP the advantage.

4. Do Not Accept RISE as "All-Inclusive" Without Verifying What Is Included. RISE with SAP is a bundle, but the bundle's scope is defined by contract, not by marketing language. Review the specific DDLC entitlements in the order form and the general terms. If the order form does not specify covered document volumes, the coverage is likely inadequate.

5. Engage Independent SAP Commercial Advisory Specialists Before Renewal. SAP's account team is optimised to maximise SAP's revenue at each negotiation point. An independent advisory team with no SAP affiliation — whose compensation is not tied to which product you buy — provides the counterweight that DDLC negotiations require.