SAP integration landscape and indirect access exposure review
Advisory / Indirect Access Defense

SAP indirect access and digital access advisory, buyer side only

Redress Compliance provides SAP indirect access and digital access advisory for enterprises facing a document claim, a DAAP offer, or integrations that write into SAP. We rebuild SAP’s document count independently, build the contract defense, and settle on terms that stop repeat claims, for a fixed fee. In published cases, claimed exposure fell 40 to 89 percent.

Get a second opinion on your quote → Download the Digital Access Recommendations
89%Claim Removed, Published Case
15 daysTo Exposure Baseline
Fixed fee, agreed up front. Indirect access defense is a fixed fee scoped to the claim, never hourly and never a share of the exposure, so every dollar removed stays with you.
Home/SAP Services/Indirect Access Defense
How this engagement works1:45

What indirect access defense covers, and what it costs

Two minutes: why an indirect access claim bills you for software nobody logged into, how each connection is tested against your contract and the document model, and why the fee is fixed while the claim is not.

The presenters in this briefing are AI generated avatars. The service, the commercial terms, and the guidance are real, produced by Redress Compliance analysts from our client engagements.

Watch the briefingResearch briefing · 4:39

Digital Access Travels With You

Session 7 of the SAP RISE Migration Series. Nine document types, roughly one FUE per thousand documents, and the most expensive misconception in the RISE conversation: more than half of buyers assumed the move removed indirect access exposure. The first document volume becomes the renewal floor.

500+ Enterprise Clients Industry Recognized $2B+ Under Advisory 11 Vendor Practices 100% Independent
Watch the briefing · 3:48Optimize the Estate First: The SAP Work That Pays for the NegotiationSAP prices your future from your present, so a bloated estate converts into a bloated subscription. The user cleanup, engine and shelfware rationalization, resolving indirect access on...Open the full page, with the transcript →
Who needs this

Who needs SAP indirect access and digital access advisory?

You need SAP indirect access and digital access advisory when SAP raises a document claim, proposes the Digital Access Adoption Program, or asks pointed questions about third party systems touching SAP data. The figure is usually large, the method opaque, and finance wants to know how much of it is real.

It pays most before SAP asks. Three situations bring buyers to us:

  • Discovery: a CRM, an EDI gateway, an ecommerce platform, or a customer portal is suspected of creating documents in ECC or S/4HANA, and the exposure needs a number before SAP produces one.
  • Document license offer: SAP has proposed a move from named users to digital access documents, and the price needs sizing on real volumes rather than SAP estimates.
  • Live claim: SAP has issued a digital access claim, alone or inside an audit, and the count and pricing tier need contesting.
CIO and IT leadershipEnterprise architectsIT procurementGeneral counsel and legalSAP basis and integration teams
What we solve

Why is SAP’s indirect access number almost never the number?

SAP’s indirect access number is almost never right because the measurement counts what it can see, not what the rules charge for. Only the initial document created in SAP by an external system is chargeable, across nine document types, and updates, line items, and documents created by licensed users do not count.

  • Everything swept in: every interface, middleware connection, and external user touching SAP data counted, whether it creates a chargeable document or not.
  • Follow on records counted again: a sales order that becomes a delivery and an invoice looks like three documents to a naive count and is one chargeable event.
  • Coverage ignored: scenarios already covered by named user and engine licenses priced again as new liability.
  • Old contract language: read in whatever way maximizes the demand, decades after it was written.
  • Timing: the claim lands next to a renewal or migration, so the pressure to settle fast is part of the design.

In our 2026 pricing analysis, SAP measurement tools overcounted by 20 to 45 percent before duplicate and follow on records were filtered out. Buyers who scoped the measurement before SAP ran its own count paid 30 to 55 percent less.

How we do it

How does SAP indirect access defense work, step by step?

The defense runs four workstreams: inventory and classify the landscape, build the contract defense scenario by scenario, cost every resolution path, and control what reaches SAP. The exposure assessment report lands within 15 business days of complete landscape and measurement data.

Workstream 01
Exposure assessment
The full SAP landscape reviewed: interfaces, middleware, RFC connections, IDoc flows, APIs, and third party applications, with an independent document count baseline built by document type.
Workstream 02
Contractual defense analysis
Named user definitions, use rights, and legacy agreement language analyzed for coverage arguments, with SAP's position rated scenario by scenario so you know where to hold.
Workstream 03
Settlement strategy
Digital access licensing, DAAP conversion, legacy licensing, and contested resolution each costed, with a settlement target, walk away position, and terms that prevent repeat claims.
Workstream 04
Audit response and negotiation
A communication protocol governing what reaches SAP, written reviews of all correspondence and proposals, and preparation ahead of every meeting through to resolution.

A typical engagement, week by week

Workstream
W1W2W3W4W5W6W7W8W9W10W11W12
Audit response protocol
Landscape and interface data handover
Exposure assessment and document baseline
Contractual defense analysis
Settlement strategy and cost models
Negotiation to resolution
Pacing follows the statement of work: the exposure assessment report lands within 15 business days of complete landscape and measurement data, with the defense memo and settlement strategy following. Resolution runs on the claim's clock, managed rather than endured. Navy bars are analysis and build, gold diamonds mark a deliverable handover, gray bars run on demand. Weeks are indicative for a typical estate; renewal dates and vendor deadlines set the real clock.
DeliverableWhat it contains
Exposure assessment reportThe full interface inventory, risk classification per scenario, an independent document count baseline, and the comparison against SAP's figures.
Defense position memoThe contractual arguments per scenario, a strength rating for each, and the recommended line of defense.
Settlement strategy paperScenario cost models across digital access, DAAP, legacy licensing, and contested paths, with target and walk away figures and required terms.
Audit response protocolWho communicates with SAP, what is shared and when, and written reviews of every data request and response.
Proposal assessments to closeA written assessment of each SAP proposal and meeting preparation briefs through to resolution.

At the negotiation stage we use five counter moves on every SAP digital access conversation:

  • Anchoring: our independent count goes on the table first, so SAP’s figure is argued against evidence.
  • Scope: static, system, and inbound documents separated so only chargeable creations remain.
  • Carve out: scenarios covered by existing licenses removed from the claim.
  • Sequencing: the claim resolved before, or separately from, the renewal or RISE decision.
  • Ring fence: a side letter that keeps the settled outcome from following into the renewal or any successor agreement.

Every settlement carries release language for past use and clear definitions for future scenarios. Monitoring rules then go to your SAM team, so the next count starts from your number.

Why it works

Why do independent document counts come in lower?

Independent counts come in lower because they apply the licensing rules to your actual document flows, where SAP’s tooling applies them to everything it can see. In order driven businesses, sales and invoice documents drove 60 to 80 percent of chargeable volume in our reviews, so the verification effort goes there first.

We also know when the Digital Access Adoption Program genuinely helps and when it is a conversion tool wearing a discount. In our reviews neither of its two paths won consistently, so we price both on the same measured count.

No vendor money touches the advice. We have no reseller agreements, no referral fees, and nothing to gain from you licensing more documents than the evidence requires.

Client results

What results has our SAP indirect access defense delivered?

Published SAP indirect access outcomes range from a 40 percent exposure cut to 89 percent of a claim removed. Every figure below comes from a case study on this site.

Your senior team

Who leads your SAP indirect access defense?

Fredrik Filipsson, co founder and Group CEO, leads indirect access work with Mietske van Ravesteijn, our SAP Commercial Lead. Indirect access defense is one of the areas Mietske leads.

Fredrik began at Oracle in license management services, running audit and compliance engagements, and later held senior commercial roles at IBM and SAP. He co founded Redress Compliance in 2018 and advises enterprise buyers on SAP, Oracle, and Java licensing.

Read Fredrik’s profile or meet the management team.

Fees

How much does SAP indirect access defense cost?

SAP indirect access defense is a fixed fee, scoped to the claim and agreed before we start. It covers all four workstreams, up to four advisory calls, and email support through the term, and we never bill by the hour.

We never take a share of the exposure. If the claim is resolved inside a renewal or RISE deal, the negotiation part can run on a success fee of 25 percent of what we save you, with you keeping 75 percent and paying nothing if we save nothing.

Compare your options

Who should handle an SAP indirect access claim: Redress, a Big Four firm, an SAP partner, or your team?

The key test is whether the advisor gains from you licensing more documents. Each option has strengths, and the table sets them out neutrally.

TestRedress ComplianceBig Four consultancySAP partner or resellerIn house team
Independence100 percent buyer side: zero vendor affiliations, no reseller agreements, no referral feesIndependent of SAP sales; other units of the firm may hold SAP alliance or implementation workPart of the SAP sales channelFull
Conflicts of interestNone; the fee you pay is the only revenueWorth checking before engagingEarns margin or project revenue from the purchase that follows the settlementNone, but internal deadlines can push toward settling early
SAP specific experienceFormer SAP commercial staff and a file of SAP audits, indirect access claims, and RISE dealsStrong technical benches; SAP commercial depth varies by teamDeep product knowledge, seen from the sell sideKnows the estate best; sees SAP claims rarely
How fees workFixed fee agreed up front; 25 percent success fee option on negotiation work; never hourlyUsually day rates or time and materialsOften folded into license or project pricingStaff time

For a neutral checklist, read our guide on how to choose a software licensing advisor.

What changed

What changed for SAP indirect access in 2025 and 2026?

The digital access metric did not change, but the surface it measures keeps growing. Four points matter this year:

  • APIs grow the count: every external API that writes to SAP can add documents, and in our reviews new APIs added 10 to 30 percent to measured volume within a year of go live.
  • DAAP has two paths: adoption discounts documents you license going forward, while conversion credits licenses you already bought, but conversion carries the full maintenance base forward. Read our DAAP evaluation guide.
  • RISE does not remove it: indirect access sits outside the RISE bundle in most variants, and the first document volume you license becomes the floor for the term.
  • Audits carry it: indirect access was the largest single claim in about three out of four SAP audits we defended in 2024 and 2025.

For the full model, read the SAP indirect access guide. If an audit is running alongside the claim, see SAP audit defense; if the claim is tied to a migration, see S/4HANA migration licensing or RISE with SAP advisory. To map exposure before SAP asks, our SAP licensing consultants build the full license position.

Frequently asked questions

What do buyers ask about SAP indirect access?

What is SAP indirect and digital access?

SAP indirect access is use of SAP data by third party systems, interfaces, middleware, or external users rather than licensed named users. SAP now charges for it through digital access, which licenses documents created in SAP by external systems across nine document types.

How much does SAP indirect access defense cost?

It is a fixed fee, scoped to the claim and agreed before work starts. We never bill by the hour and never take a share of the exposure, so every dollar removed from the claim stays with you.

How fast do we see the exposure number?

The exposure assessment report typically lands within 15 business days of complete landscape and measurement data, with the defense memo and settlement strategy following on the schedule the claim demands.

Are you independent of SAP?

Yes. We have zero vendor affiliations, no reseller agreements, and no referral fees, and nothing to gain from you licensing more documents than the evidence requires.

Is the Digital Access Adoption Program a good deal?

Sometimes. DAAP offers adoption or conversion, and in our reviews neither path won consistently, so both must be priced on a measured document count rather than SAP's estimate. Conversion also keeps the full maintenance base.

Does moving to RISE remove our indirect access exposure?

No. Indirect access sits outside the RISE bundle in most variants, and the first document volume you license becomes the floor for the term, so settle the count before or during the move.

What if an SAP audit is already running?

The response protocol comes first, so nothing further reaches SAP unreviewed. The exposure baseline and defense position are then built inside the audit timeline, and every finding is answered from evidence rather than urgency.

What data do you need from us?

The integration landscape: interfaces, middleware, RFC and IDoc flows, APIs, and third party applications touching SAP, plus your SAP contracts, system measurement history, and any SAP correspondence or estimation tool output.

Advisory team preparing a vendor negotiation

Answer the claim with your number, not theirs

An independent baseline, a scenario by scenario defense, and settlement terms that close the issue for good. That is the difference between a demand and a negotiation.

Negotiation intelligence, monthly

One letter a month. Negotiation moves, audit signals, and price book shifts.