SAP's indirect access regime — now formalised as Digital Access — remains the single largest source of unbudgeted licence spend for SAP customers. Unlike named-user or processor metrics, digital access charges accrue silently through third-party integrations, automation scripts, and custom interfaces. Many organisations only discover the exposure during an SAP audit or a RISE with SAP migration conversation, at which point leverage has shifted entirely to the vendor. This assessment covers the nine document types metered under SAP's Digital Access Adoption Programme (DAAP), integration architecture risks, S/4HANA migration implications, BTP connector usage, and contract protections. Score each item as Compliant, Partial, or Unknown. Treat unknowns as gaps.
Section 1
Digital Access Fundamentals
01
Document type inventory completed
High
Expert note: SAP meters nine document types: Sales Orders, Purchase Orders, Supplier Invoices, Customer Invoices, Goods Receipts, Outbound Deliveries, Inbound Deliveries, Billing Documents, and Production/Process Orders. If you have not catalogued which external systems create or modify these objects, exposure is unquantified.
02
Document volume baseline established
High
Expert note: Digital access fees are calculated on document-creation volume, not user count. Without a baseline count of documents created by non-licensed actors, you cannot model exposure or verify SAP's metering data during an audit.
03
DDLC contract clause reviewed
High
Expert note: The Digital Documents Licence Clause (DDLC) was introduced in 2018 and tightened in 2023. Customers still operating under older named-user contracts without a DDLC addendum face a contractual grey zone — SAP treats the absence of explicit permission as unlicensed indirect use.
04
DAAP programme enrolment assessed
Medium
Expert note: SAP's Digital Access Adoption Programme offered time-limited DAAP discounts (typically 15–25%) to customers converting indirect use to digital access licences. Verify whether your agreement references DAAP terms and whether any expiry dates apply.
05
Document counting methodology agreed
High
Expert note: SAP counts documents at line-item level for some types and header level for others. Disagreements over counting methodology drove many of the largest audit settlements. Ensure any agreed measurement approach is documented in writing.
Hidden Digital Access exposure averages £4–12M for mid-market SAP customers.
Redress quantifies your liability before SAP does — buyer-side only.
Section 2
Integration Architecture
06
Third-party integrations mapped to document types
High
Expert note: Every ERP integration, middleware layer, or RPA bot that creates SAP documents is a potential digital access liability. Map each integration to the specific document types it touches and estimate annual volume.
07
SAP BTP connector usage licensed
Medium
Expert note: SAP Business Technology Platform connectors that write back to SAP S/4HANA or ECC can trigger digital access charges. BTP is often procured separately from core SAP licences — confirm whether connector-generated documents are within scope.
08
API-based integrations reviewed
High
Expert note: REST and SOAP API calls that create core business documents through SAP's integration suite are within digital access scope. Third-party developers often build integrations without licence awareness; review all active API registrations.
09
EDI transactions analysed for document creation
Medium
Expert note: Electronic Data Interchange feeds from suppliers, logistics providers, or trading partners frequently auto-create SAP Purchase Orders, Supplier Invoices, or Goods Receipts. EDI volume can be substantial — one 3PL customer had 4.2 million metered documents per year.
10
RPA bots inventoried and document impact quantified
High
Expert note: Robotic Process Automation tools (UIPath, Automation Anywhere, SAP Build RPA) that interact with SAP to create or modify metered documents generate digital access charges. Many RPA deployments were built before digital access was understood and have never been audited for licence impact.
Section 3
S/4HANA & RISE Implications
11
S/4HANA migration impact on digital access modelled
High
Expert note: Migrating to S/4HANA or RISE with SAP often triggers a complete licence renegotiation. SAP sales teams use migration conversations to reclassify integration patterns as digital access use and introduce new charges. Baseline your current digital access exposure before migration discussions begin.
12
RISE commercial terms include digital access rights
Medium
Expert note: RISE with SAP subscription bundles do not automatically include unlimited digital access. Verify whether your RISE contract scope explicitly covers document types generated by existing third-party integrations.
13
Legacy ECC integration patterns reviewed pre-migration
Medium
Expert note: Integrations built for ECC often require re-architecture for S/4HANA. Re-architecture is an opportunity to redesign connections that avoid metered document creation — but only if licence implications are considered during the technical design phase.
14
SAP Integration Suite scope confirmed
Medium
Expert note: SAP Integration Suite (formerly CPI) is frequently included in RISE packages but with volume caps. Exceeding Integration Suite throughput thresholds can trigger overage charges that are contractually separate from digital access fees.
15
Clean core strategy assessed for licence impact
Low
Expert note: SAP's clean core mandate discourages custom ABAP enhancements in S/4HANA. Moving customisations to BTP extensions may shift document creation into digital access scope. Model this before committing to an extension strategy.
Hidden Digital Access exposure averages £4–12M for mid-market SAP customers.
Redress quantifies your liability before SAP does — buyer-side only.
Section 4
Audit Risk & Contract Protections
16
LAM (Licence Audit Management) process prepared
High
Expert note: SAP's LAM audit process requires customers to run measurement tools and submit results. Unlike Oracle LMS, SAP typically runs LAM with less adversarial framing — but the financial exposure is identical. Prepare a response process before an LAM request arrives.
17
Historical digital access exposure calculated
High
Expert note: SAP can claim back charges for indirect use going back to the date of the DDLC clause or, in disputed cases, the commencement of the integration. Calculate historical exposure so you enter any audit discussion knowing your worst-case number before SAP presents theirs.
18
Contractual audit rights restricted
Medium
Expert note: Review whether your SAP contract limits audit frequency (e.g. once per 12 months) or requires advance written notice. Many standard SAP contracts include audit rights without frequency restrictions — a negotiation opportunity at renewal.
19
SAP Digital Access pricing benchmarked
Medium
Expert note: Digital access document pricing varies significantly by customer size, industry, and negotiation leverage. Without benchmark pricing, you cannot assess whether SAP's proposed settlement or DAAP offer represents fair value. Redress maintains a pricing database across 500+ engagements.
20
Contractual protections for future integrations included
Low
Expert note: Negotiate blanket digital access rights for defined integration categories (e.g. all integrations with licensed SAP systems) rather than point-in-time settlement of current exposure. Future integrations built without this protection will re-open the liability cycle at the next audit.
"We entered the SAP migration conversation thinking RISE solved our indirect access problem. It didn't — we had £8M of unquantified digital access exposure that SAP surfaced on day one of commercial negotiations." — CIO, FTSE 250 manufacturing group
Interpreting Your Assessment Score
Count fully compliant items. Unknown answers should be treated as gaps for scoring purposes.
17–20
Strong Position
Digital access exposure well controlled. Maintain annual review cadence as integrations evolve.
11–16
Moderate Exposure
Material gaps identified. Prioritise HIGH-risk items and commission an independent SAP licence review within 90 days.
0–10
High Exposure
Significant unquantified risk present. Do not enter SAP commercial negotiations or RISE discussions until exposure is independently assessed. Contact Redress immediately.