Answer 8 questions to discover your indirect access exposure, understand your risk level, and get a personalised action plan before SAP does it for you.
9
Document Types SAP Counts
$1M+
Typical Audit Exposure
50-90%
Negotiable Discounts
Your ProgressQuestion 1 of 8
Question 1 of 8
🔌
How many third-party or non-SAP systems create transactions in your SAP environment?
Think CRM, e-commerce, procurement portals, EDI, WMS, IoT, HR platforms, financial systems, or any middleware that writes data into SAP.
None that I know of
All transactions are created directly by SAP users
1 to 3 systems
Limited integrations (e.g. CRM or a single e-commerce platform)
4 to 10 systems
Multiple integrations across different business functions
More than 10 systems
Heavily integrated landscape with many external data sources
Question 2 of 8
📈
Have you ever measured or estimated the volume of documents these external systems create in SAP each year?
SAP charges for 9 specific document types (sales orders, invoices, purchase orders, material movements, etc.) created by non-SAP systems.
No, we have never measured this
We have no visibility into indirect document volumes
We have a rough idea but no formal measurement
Estimated based on business volume, not SAP data
We ran SAP's estimation tool or a similar analysis
Used DAES, SAP Passport, or a third-party tool at least once
We monitor document volumes continuously
Regular reporting on indirect document creation is in place
Question 3 of 8
📜
Does your current SAP contract explicitly address Digital Access or indirect access licensing?
Digital Access is SAP's document-based licensing model introduced in 2018. Check whether your contract includes document entitlements, indirect use terms, or references to the 9 document types.
No, and I am not sure what it means
This is the first time I am hearing about this
No, our contract only covers named user licences
No document-based entitlements exist in our agreement
Yes, but I am not sure if the coverage is adequate
We have some Digital Access provisions but have not validated them
Yes, we have a Digital Access entitlement we actively manage
We know our document allowance and track consumption against it
Question 4 of 8
⚠️
Has SAP contacted you about a licence review, audit, or Digital Access assessment in the past 24 months?
SAP's Global License Compliance (GLAC) team actively identifies customers with indirect access exposure. They may frame it as a "free evaluation service" or reference the Digital Access Adoption Program.
No, we have had no contact from SAP on this topic
SAP mentioned Digital Access during a renewal conversation
It came up but was not the primary topic
SAP offered their free Digital Access Evaluation Service
They want to run their estimation tool on our system
SAP has initiated a formal audit or compliance review
We have received a formal licence review request
Question 5 of 8
📅
When is your next SAP contract renewal or S/4HANA migration planned?
SAP commonly uses renewals and S/4HANA migrations as leverage to force Digital Access adoption. The closer you are to renewal, the more urgently you need to address this.
Within the next 12 months
12 to 24 months from now
More than 24 months away
We recently renewed or migrated (addressed Digital Access)
Question 6 of 8
🤖
Have you deployed or are you planning RPA bots, AI agents, or automated workflows that interact with SAP?
Robotic Process Automation (RPA), AI-driven systems, and automated workflows that create, update, or read SAP documents can generate massive indirect access volumes that most organisations do not account for.
No, we do not use RPA or AI with SAP
We are considering or piloting automation
Early stage, not yet in production
Yes, we have RPA bots or automations in production
Active bots creating transactions in SAP
Yes, at scale, and we have not assessed the licensing impact
Multiple bots/automations running without licence review
Question 7 of 8
🌐
Do external users (customers, suppliers, partners) interact with your SAP system through portals, APIs, or third-party applications?
Supplier portals, customer self-service, e-commerce platforms, and partner integrations that create SAP documents (orders, invoices, etc.) all count as indirect access.
No external users interact with SAP
A small number of suppliers or partners
Under 100 external parties creating limited transactions
Hundreds or thousands of external parties via portals or APIs
Large-scale external access including e-commerce
High-volume consumer or B2B channels creating SAP transactions
Question 8 of 8
🛠
Do you have a governance process that evaluates SAP licensing impact before new integrations are deployed?
Every new system connected to SAP can trigger Digital Access costs. Without a review process, your indirect access exposure grows silently with every new project.
No, we have no such process
New integrations are deployed without licence impact review
It is informal or inconsistent
Sometimes considered but not a standard checkpoint
We review major integrations but not all
Large projects get a licence check, smaller ones do not
Yes, licence impact is a mandatory checkpoint for all SAP integrations
Formalised process with licence owner sign-off
Your Risk Report Is Ready
Enter your details below to view your personalised SAP Digital Access risk assessment, findings, and action plan.
Please use your company email. Public email addresses (Gmail, Yahoo, Outlook, etc.) are not accepted.
Only company email addresses are accepted.
By submitting, you agree to receive your personalised report and be subscribed to the Redress Compliance newsletter with SAP licensing insights. You can unsubscribe at any time. We will never share your data.
We are independent SAP licensing advisors who help enterprises measure, negotiate, and defend against Digital Access compliance claims. We have benchmarked hundreds of SAP deals and typically reduce exposure by 30-60%. Fixed-fee. Vendor-independent.