SAP Digital Access is the document-based licensing model that replaced indirect access. Rather than counting users, SAP counts business documents created by third-party systems across nine metered types: Sales Orders, Purchase Orders, Supplier Invoices, Customer Invoices, Goods Receipts, Outbound Deliveries, Inbound Deliveries, Billing Documents, and Production/Process Orders. Financial and Material documents are weighted at 0.2 each; all others count at 1.0 per document line. The compounding effect of line-item counting, integration sprawl, and aggressive audit enforcement has left many enterprises carrying unquantified exposure worth millions. This assessment covers financial exposure quantification, technology risk vectors, DAAP commercial strategy, and governance controls. Score each item as Compliant, Partial, or Unknown — treat any Unknown as a gap requiring immediate investigation.
Section 1
Exposure Quantification & Financial Modelling
01
Independent document volume measurement completed using SAP's estimation tool
High
Expert note: SAP provides an estimation report (available via SAP Notes for both ECC and S/4HANA) that scans your system and counts documents by type created via indirect processes. Do not rely on internal estimates or vendor-supplied figures. Independent measurement is the only way to establish a defensible baseline before commercial discussions begin. Organisations entering renewal or RISE conversations without this data are negotiating blind.
02
Financial exposure ceiling modelled at SAP list price (worst-case audit scenario)
High
Expert note: If SAP discovers unlicensed digital access in an audit, they charge full list price for all metered documents and backdate maintenance fees from the point of first non-compliant use. For a mid-market enterprise with 2–5 million documents per year, this can produce a claim of £4–12M before negotiation. Modelling the worst-case ceiling is a mandatory first step — it defines the DAAP conversion break-even point and anchors your negotiating mandate.
03
Document weighting factors correctly applied (0.2 for Financial and Material document types)
High
Expert note: SAP's weighting system counts Financial and Material documents at 0.2 each — meaning five of these types equal one full document credit. Sales Orders, Purchase Orders, Supplier Invoices, Customer Invoices, Goods Receipts, Outbound Deliveries, Inbound Deliveries, Billing Documents, and Production/Process Orders each count at 1.0 per line item. Misapplying weights in your exposure model leads to material miscalculation and either over-pays or under-declares in a DAAP conversion.
04
Three-year historical document creation trend modelled for volume growth projections
Medium
Expert note: Digital access exposure is not static — it grows as you add integrations, automate processes, and scale transaction volume. DAAP agreements typically require you to purchase 115% of current measured volume (Option A), so understanding the growth trajectory prevents you from under-licensing in year two or three. Organisations that signed DAAP based on snapshot volume without modelling growth have frequently faced true-up discussions within 18 months.
05
Digital access cost benchmarked against 10% ERP contract value rule of thumb
Medium
Expert note: A commonly applied benchmark is that unlimited SAP Digital Access licensing should cost approximately 10% of your annual SAP ERP contract value. If the cost modelled through document counting substantially exceeds this threshold, it signals either unusually high integration density or that a fixed-fee unlimited arrangement may be negotiable. Use this as a sanity check against SAP's per-document pricing output — not as a substitute for measurement-based analysis.
SAP Digital Access exposure averages £4–12M for mid-market enterprises.
Redress quantifies your liability and designs your DAAP strategy — buyer-side only.
Section 2
Technology & Integration Risk Vectors
06
eCommerce platform integration assessed for Sales Order and Billing Document creation
High
Expert note: B2C and B2B eCommerce platforms (Salesforce Commerce Cloud, Shopify Plus, SAP Commerce Cloud external integrations) that create SAP Sales Orders or Billing Documents are classic digital access liability sources. An enterprise processing 500,000 web orders per year with an average of 3 line items generates 1.5 million chargeable Sales Order documents. Map every storefront-to-SAP order creation flow and estimate annual line-item volume explicitly.
07
IoT and sensor-driven integrations creating SAP Goods Receipts or Production Orders identified
High
Expert note: Manufacturing, logistics, and energy companies frequently connect IoT sensors, SCADA systems, or warehouse management systems to SAP using middleware that auto-posts Goods Receipts, Production Orders, or Goods Issues on every event. A single production line posting 200 goods movements per shift, 20 shifts per week, generates over 200,000 Material documents per year. At a 0.2 weighting, this is still 40,000 equivalent documents — and many plants operate dozens of such lines.
08
AI, machine learning, and agentic automation tools audited for SAP document creation
High
Expert note: AI-powered invoice processing tools (Esker, Basware, Hypatos), procurement automation platforms, and emerging agentic AI systems that interact with SAP via API to create Purchase Orders, Supplier Invoices, or Goods Receipts are rapidly becoming the fastest-growing source of digital access documents. Many were deployed post-DAAP conversations, creating new unlicensed exposure. Require a DDLC impact assessment for every new AI/automation tool before SAP connectivity is enabled.
09
Customer and supplier self-service portals evaluated for indirect document creation
Medium
Expert note: Supplier portals (where vendors submit invoices or advance shipping notices), customer order portals, and dealer management systems frequently sit on non-SAP platforms that write back to SAP. Each supplier invoice created through a portal is a metered Supplier Invoice document. Organisations with large supplier bases and high invoice volumes — particularly in retail, manufacturing, and FMCG — face disproportionate exposure from portal-driven document creation. Count portal-origin documents separately from ERP-origin in your baseline.
10
Cloud iPaaS and middleware layers (MuleSoft, Azure Integration Services, Boomi) mapped to document types
High
Expert note: Integration Platform-as-a-Service tools serve as document-creation conduits — they receive events from source systems and create SAP objects as the target. The iPaaS layer itself is not the licence issue; the SAP document types it creates are. Many organisations have dozens of active MuleSoft or Boomi flows that create SAP objects, and these are rarely catalogued against the nine digital access document types. A complete middleware inventory mapped to DDLC scope is non-negotiable before any DAAP conversation.
11
GROW with SAP and cloud ERP scope verified against digital access rights
Medium
Expert note: SAP's GROW with SAP (the mid-market S/4HANA Cloud Public Edition package) includes standard digital access rights within the subscription for designated use cases. However, custom integrations built outside the standard scope — connecting non-SAP systems to SAP via APIs — may not be covered. Review your GROW contract annexes carefully for any exclusions on third-party-originated documents before building additional integrations against a GROW environment.
Section 3
DAAP Commercial Strategy & Negotiation
12
DAAP conversion economics modelled under both Option A and Option B structures
High
Expert note: SAP offers two DAAP conversion structures. Option A requires purchasing 115% of measured volume at list price but effectively charges for only 100% (an implied 13% headroom discount). Option B provides up to a 90% discount from list price on the initial conversion purchase. The better option depends entirely on your measured volume, growth trajectory, and list price at your tier. Never accept SAP's framing of which option suits you — model both independently before entering the DAAP conversation.
13
DAAP licence amnesty scope for historic exposure explicitly confirmed in writing
High
Expert note: The core value proposition of DAAP is that SAP forgives historic unlicensed indirect use — they will not back-charge for usage that occurred before the DAAP agreement date. However, this amnesty only applies to document types and integration patterns explicitly covered in the agreement. Any integration not named, any document type not listed, or any system not identified may be excluded from amnesty. Require your DAAP agreement to explicitly enumerate every covered integration and confirm amnesty scope in unambiguous contractual language.
14
DAAP volume cap stress-tested against measured usage plus 36-month growth scenario
High
Expert note: DAAP agreements cap covered volume at a defined level. Exceeding that cap triggers overage charges at rates that are frequently higher than the initial DAAP pricing. Organisations that signed DAAP based on current-year document volumes without projecting growth have faced unexpected overruns as transaction volumes grew through organic expansion, acquisitions, or new automation projects. Stress-test your DAAP cap against a 36-month growth scenario before signing — and negotiate a step-up mechanism rather than punitive overage pricing.
15
Post-DAAP overage pricing cap agreed and documented in contract
Medium
Expert note: SAP's standard DAAP terms are largely silent on post-conversion overage rates, which gives SAP pricing flexibility at true-up. Negotiate a contractually binding price cap on additional documents purchased beyond your DAAP volume ceiling — typically expressed as a defined percentage of the initial per-document rate. This single clause can reduce exposure in a growth scenario by several hundred thousand pounds and prevents SAP from using overage conversations as a commercial leverage point at renewal.
16
Unlimited digital access vs per-document DAAP pricing evaluated for your usage profile
Medium
Expert note: For high-volume enterprises — particularly those in manufacturing, retail, or logistics where document counts run into tens of millions per year — an unlimited digital access arrangement (typically priced as approximately 10% of total ERP contract value per year) can be significantly cheaper than per-document DAAP pricing. SAP does not volunteer this option proactively. If your modelled annual document volume generates a per-document DAAP cost above the 10% threshold, negotiate for an unlimited structure before agreeing DAAP terms.
17
DAAP scope exclusions and carve-outs reviewed for completeness
Medium
Expert note: DAAP agreements typically exclude static reads — third-party systems that read SAP data without creating or modifying metered documents are generally not in scope. Confirm that your DAAP documentation explicitly includes this carve-out, covering data warehouse extracts, reporting tool queries, and BI platform connections. Exclusions should also explicitly cover internal SAP-to-SAP document flows, which are licensed under standard named-user metrics and should never be double-counted under digital access rules.
DAAP amnesty only covers what is explicitly named in the agreement.
Redress reviews your DAAP scope before you sign — unlisted integrations remain fully exposed.
Section 4
Governance, Ongoing Risk Control & Audit Readiness
18
Digital Access Licence Owner formally assigned within SAM or IT procurement function
High
Expert note: Without a designated owner, digital access exposure accumulates silently as integration teams build new connections without licence awareness. The Digital Access Licence Owner should maintain the integration inventory, review all new SAP connectivity requests against the DDLC, report document volume trends to leadership quarterly, and serve as the primary contact in the event of an SAP audit notification. This role sits most naturally within Software Asset Management or IT Procurement, with a mandate that spans architecture, legal, and finance teams.
19
New integration approval process requires mandatory DDLC impact assessment before go-live
High
Expert note: The most cost-effective digital access risk control is a pre-deployment gate: every new integration that touches SAP must complete a one-page DDLC impact assessment before it goes live. This assessment asks whether the integration creates any of the nine metered document types, estimates annual volume, and confirms whether that volume is within existing DAAP scope or requires a contract amendment. Development teams resist this friction initially — but the cost of a single undetected high-volume integration entering production unlicensed dwarfs the investment in the gate process many times over.
20
Continuous document volume monitoring tooling deployed to detect emerging overruns
Medium
Expert note: Point-in-time document measurement is insufficient for organisations with dynamic integration environments. Continuous monitoring — whether through SAP's native Digital Access monitoring capabilities, third-party SAM tooling with SAP connectors, or a custom report scheduled monthly — provides early warning of volume trends approaching DAAP caps. This is particularly important after M&A activity, new RPA deployments, or seasonal spikes that could push cumulative annual counts above contracted thresholds. Alert thresholds set at 80% of DAAP cap provide adequate response time for commercial remediation before breach.
"We had completed a DAAP conversion and thought we were covered. Eighteen months later SAP surfaced a £3.2M claim on integrations that went live after the DAAP signature date and weren't covered by the amnesty. The governance gap cost more than the original conversion." — Head of SAP Centre of Excellence, European retail group
Interpreting Your Assessment Score
Count fully compliant items. Score Unknown answers as gaps. Any item in Section 1 or Section 4 marked Unknown should trigger immediate action regardless of overall score.
17–20
Controlled Position
Digital Access exposure well quantified and governed. Maintain quarterly monitoring and review DAAP scope annually as integrations evolve.
11–16
Moderate Exposure
Material gaps in measurement, commercial coverage, or governance. Commission an independent exposure quantification and DAAP strategy review within 60 days.
0–10
High Unquantified Risk
Significant unquantified exposure present. Do not enter SAP renewal, RISE, or audit conversations without independent advisory support. Contact Redress immediately.