SAP indirect and digital access is the biggest unbudgeted line in most SAP estates. This report reads how the exposure arises, how SAP prices it, and the buyer side moves that hold the realized settlement well below the opening claim.
SAP indirect and digital access is the biggest unbudgeted line most SAP estates carry. This report reads how the exposure arises, how SAP prices it, and the buyer side moves that hold the realized settlement well below the opening claim.
This report combines the SAP indirect access engagements our team ran between 2024 and 2025 with the public record on SAP digital access. The proprietary numbers come from the SAP licensing and trust center and our Redress Compliance advisory engagement file across roughly 180 to 220 renewals and audits.
All numbers are framed as defensible bands rather than precise points. Two estates of the same headline size can sit two or three multiples apart on document throughput, and an honest range is more useful to a buyer than a false average.
The scope is on premise ECC, S/4HANA, and RISE with SAP contracts where indirect or digital access has either surfaced as an audit risk or been quoted into a renewal. The metric throughout is the document, the unit SAP uses to bill digital access, not the older named user proxy.
The vertical mix in our engagement set ran roughly 30 percent retail and consumer goods, 25 percent discrete and process manufacturing, 20 percent financial services and insurance, 15 percent public sector, and 10 percent other. The mix matters because document patterns differ sharply by industry.
The report does not cover the legacy SAP Application Access by named user license, named user category math, or BusinessObjects licensing in any depth. Each of those carries its own audit pattern.
The focus here is the indirect and digital access exposure that has become the largest unplanned line on most SAP renewals. The named user model still matters, and it intersects with digital access, but it is treated as a parallel topic.
Indirect access is the use of SAP functionality or data by people or systems that do not hold a direct SAP named user license. Digital access is the 2018 SAP commercial model that prices that use by counting nine specific document types created in the SAP system, rather than counting the people behind them.
The reason the line is large is the same reason it is hidden. Most SAP estates have grown around dozens of integrations, portals, and bots that move data in and out of the core. Each of those interactions can create a chargeable document, and the buyer is rarely measuring them the way SAP can.
Before 2018 the question was whether a person using a non SAP system to read or write SAP data still needed an SAP named user license. SAP's public position was that they did. The buyer often disagreed, and a series of large public disputes followed.
Those disputes were never really about whether use occurred. They were about whether the same use should be paid for twice and how the boundary should be drawn between a person and a process.
SAP introduced digital access to replace the named user argument with a document metric. Nine outcome documents are counted, including sales orders, invoices, purchase orders, service orders, manufacturing orders, quality notifications, material documents, financial documents, and time management documents.
The framing is that the buyer pays once for the outcome, regardless of which system created it. In practice the metric is still negotiated, but the unit of measurement has shifted from people to documents created.
The modern SAP estate is wrapped in integrations. Customer portals create sales orders. Online sales platforms post invoices. Field service apps log time. Each of those moves can create an SAP document, and the volumes scale with business activity rather than seat count.
That is why a buyer can keep the named user count flat for years and still see a six or seven figure digital access claim arrive at the next renewal. The seat budget and the document budget have decoupled.
The first myth is that digital access is only about external users. It is not. Internal bots, batch jobs, and middleware components that post documents into SAP also create digital access exposure under the 2018 model.
The second myth is that read only integrations are free. Reading SAP data does not by itself trigger a document, but most read only integrations end up writing back, and that is where the meter starts.
The third myth is that the line can be priced precisely up front. It cannot. The negotiation is about the band, the methodology, and the contractual cap, not a single line number that holds across the term.
The shift from named users to documents was not a marketing redesign. It followed several years of public disputes in which the named user argument failed to scale to modern integration patterns. The document model was SAP's response to a measurement problem that had outgrown the original license.
In 2017 a UK court ruled that Diageo's use of a Salesforce portal that read SAP data did create an indirect use case requiring SAP licenses. The decision crystallized the commercial risk of the named user argument for a generation of CIOs and procurement leaders. Within a year SAP had published the digital access alternative.
The AB InBev settlement reinforced the same point at a much larger scale. The combination made it clear that the named user metric did not protect either side from very large surprise claims when integrations multiplied.
SAP introduced the document metric and the Digital Access Adoption Program, known as DAAP, to give existing customers a structured path to the new model. DAAP offered discounts in exchange for the conversion, with the size of the discount tied to how clean the buyer's measured document throughput was at conversion time.
DAAP is not free. It is a commercial path that exchanges a future indirect access argument for a known document fee today, often with a stepped uplift schedule attached. The decision to enter DAAP is itself a negotiation, not a forms exercise.
The nine SAP digital access documents are sales, invoice, purchase, service, manufacturing, quality, financial, material, and time documents. Each created document counts once, regardless of how many systems or people are involved in producing it.
The intent is to remove the named user double count. The risk is that an integration that produces several document types from one business event multiplies the count, which is one of the largest sources of exposure on estates with deep integration footprints.
The headline model has not changed. The negotiating posture has. SAP has refined how digital access is quoted inside RISE with SAP, how DAAP discounts are graded, and how the measurement requests are written. The buyer's playbook has had to evolve with it.
One quiet change is the growing use of digital access as part of the RISE bundle commercial conversation. The metric is the same. The leverage point shifts, because the buyer is also negotiating bundle scope, contract term, and exit rights at the same table.
Exposure usually arises in the same handful of patterns. The exact shape depends on industry, but the integration types are common across most SAP estates and account for the bulk of document creation.
Customer portals, partner portals, online sales sites, and supplier networks all touch SAP. When a partner submits a purchase order through a portal, the SAP system records a purchase order document and the digital access meter advances by one. The same pattern repeats for sales orders, invoices, and service notifications.
The portal owner often sees the SAP write as an implementation detail. The SAP commercial team sees it as a document. That gap is where most surprise exposure is born.
Robotic process automation creates a particularly visible audit pattern. A bot that posts hundreds of journal entries a day on behalf of a finance team produces hundreds of financial documents, and the SAP system has no way to tell that the bot is acting for a single human owner.
Each bot run looks like its own activity. SAP's defensible position is that the bot is an integration, and the documents count as if produced by an independent process. The buyer's defensible position is that the underlying business event is one transaction, not many, but the burden of proof sits with the buyer.
The growth of integration platforms, including SAP Integration Suite, MuleSoft, Boomi, and custom enterprise service buses, has multiplied the document creation rate inside SAP. Each integration that creates an SAP document on receipt of an external event adds to the digital access meter.
The implication for procurement is that the digital access exposure now grows with the integration roadmap, not just the user count. A program that simplifies the customer experience by adding three new digital channels can quietly multiply the document volume.
Industrial estates with heavy IoT footprints face an additional exposure. Field telemetry that creates SAP service notifications, quality notifications, or manufacturing orders contributes to the document count, and a chatty sensor fleet can produce surprising volumes once aggregated.
The good news is that telemetry is one of the easier patterns to instrument, because the integration boundary is well defined. The bad news is that few buyers had thought of it as an SAP license consumer before the digital access model arrived.
Electronic data interchange is a long established pattern that quietly produces large document counts. EDI orders, invoices, and shipment notifications all create SAP documents on receipt. Estates with hundreds of EDI partners can carry document volumes that dwarf their internal user population.
EDI exposure tends to be sharply concentrated in a few high volume partner relationships, which makes the baseline easier to model once it is being measured. The barrier is usually that no one has thought to measure it.
Finance teams often route bank statements, payment files, and tax filings through automated workflows. Each can create SAP financial documents at scale. These flows are easy to overlook because they were never thought of as integrations in the first place.
The risk is concentration. A single batch payment run on a busy month end can produce a step change in financial documents, and one quiet quarter masks the spike. Annual measurement smooths the picture but also disguises it.
SAP prices digital access per document on a tiered schedule that decreases the per document rate at higher volumes. The schedule is negotiable, and the realized rate inside a structured renewal usually sits well below the opening list rate.
The headline rate ranges from a few cents to less than one cent per document, depending on volume tier and the buyer's relationship. The list rate matters less than the tier boundaries, because the difference between two adjacent tiers can outweigh the difference between two adjacent rates.
This makes the volume estimate as important as the price. A document count that lands at the bottom of a tier costs the buyer the full tier without the benefit of its scale, which is a structural reason to plan the count, not let it happen.
The Digital Access Adoption Program offers a structured discount in exchange for a clean conversion. The discount is largest when the buyer can demonstrate a defensible baseline and a clean estate inventory. It shrinks when the conversation starts after SAP has already measured the buyer.
The implication is the same as the rest of the negotiation. Whoever counts first sets the floor. A buyer who arrives with measured documents takes the larger DAAP track. A buyer who arrives without one takes whatever SAP measured.
Indirect access typically surfaces through the annual system measurement, the SAP LAW report, or a direct audit notice. The measurement asks the buyer to disclose integrations, document volumes, and external user populations. The answers, signed by the buyer, become the starting point for any commercial discussion.
The single most expensive thing a buyer can do is to fill in the measurement under time pressure with estimates. Those estimates are then anchors for the SAP opening claim, and the negotiation runs from there.
RISE with SAP bundles cloud infrastructure, S/4HANA, and a managed service into one subscription, but it does not eliminate the indirect access discussion. SAP's RISE positioning still prices digital access alongside the bundle. The metric and the conversation move into the new contract rather than ending in the old one.
The practical effect is that a RISE migration is also a digital access negotiation, and the buyer who prepares for both at once gets a better outcome than the buyer who treats RISE as a transformation conversation only.
The single highest leverage clause in a digital access contract is the annual uplift cap on the document volume baseline. Without it, the baseline can move every year on SAP's reading of the integration footprint, and the buyer reopens the negotiation each cycle.
A well drafted cap fixes the document baseline at the contract level, bounds the growth, and gives the buyer a working number to budget against. It does not eliminate the negotiation, but it converts it from open ended to bounded.
Named user license versus digital access, key differences
| Dimension | Named user model | Digital access model |
|---|---|---|
| Unit of measurement | People with logon access | Documents created in SAP |
| Scales with | Headcount | Business activity and integration volume |
| Audit signal | User type classification | Document throughput by type |
| Buyer leverage | Reclassification, cleanup, license type swap | Baseline measurement, scope of integrations, tier negotiation |
| Common surprise | Misclassified power users | Bots, EDI, and portals that produce more documents than expected |
| RISE treatment | Folded into bundle, FUE math | Still priced separately on document tiers |
The standard advice from many SAP account teams and several partners is that buyers should wait for SAP to quantify the indirect access exposure and then negotiate the number down. We disagree. In the indirect access cases we have defended, the buyers who measured their own document throughput before any SAP conversation settled at roughly 40 to 60 percent of the opening exposure, because they controlled the baseline. The buyers who let SAP measure first settled much higher and spent the rest of the engagement arguing about a number they did not own. The buyer side move is to instrument the integrations, count the documents, and walk into the room with a defensible number rather than reacting to SAP's.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A defensible baseline is not the most precise document count possible. It is the count a buyer can stand behind on the record, with a clear method and a stated tolerance. SAP rarely disputes a baseline that is methodically built and clearly explained. SAP almost always disputes a baseline that is improvised under pressure.
The first decision is scope. List every integration that touches the SAP system, even ones thought to be irrelevant, and mark which of the nine digital access document types each one can create. This step alone surfaces sources of exposure most teams had not modeled.
The second decision is the time window. A representative window has to include peak periods, because a baseline drawn from a quiet quarter understates exposure and a baseline drawn from a peak overstates it. A twelve month window with seasonal adjustment is the most defensible default.
Four to eight integrations usually produce most of the documents on a mid market estate. The right move is to instrument those first and accept a known approximation on the smaller ones, rather than chase a full estate inventory that delays the baseline.
Document the method used for each integration. A clean methodology note is worth more in the negotiation than a sharper number with a vague provenance, because SAP's challenge will be the method, not the number.
The baseline has to be reproducible. Pull the underlying logs, save the integration configuration as it was at the time of measurement, and capture the document type counts in a single artifact. The artifact is what survives the negotiation, not the verbal recall of who counted what.
This is the difference between a number that holds in a negotiation and a number that does not. SAP's commercial team will press until the supporting evidence appears, and a well evidenced baseline ends that part of the conversation quickly.
Every measured baseline carries some uncertainty. The right posture is to state the tolerance up front, with a clear band rather than a single line. A baseline that says four point two to four point six million documents per year carries more weight than one that says four point four million on the nose.
The band signals method, not weakness. A baseline without a stated tolerance gets treated as either too precise to believe or too vague to use. The band fixes both problems and resets the conversation onto methodology.
A baseline is not a one off artifact. The integration footprint changes, the business changes, and the document volume drifts. The right cadence is a refresh at least every twelve months, with an interim recount whenever a new integration goes live.
The cost of refreshing is small once the method is established. The cost of not refreshing is that the next SAP measurement compares against a baseline the buyer no longer recognizes, and the negotiation moves back to SAP's number.
Exposure varies more by integration footprint than by headline industry, but industry shapes which integrations dominate. The variance between estates of similar size is wide enough that a per industry average is only directional.
Retail estates carry heavy online sales and EDI traffic. Sales orders dominate the document mix, with invoices a close second, and the document volume tracks revenue rather than headcount. A retailer with five thousand stores can produce more documents than a manufacturer with ten times the SAP user count.
The defensive move for retail is to model the document volume against revenue growth in the renewal forecast, not against the seat count. A flat seat count and rising revenue is the classic profile for an indirect access surprise.
Manufacturing estates carry heavy supplier portal traffic and EDI volumes, plus a growing IoT contribution from connected production lines. Material documents and manufacturing orders dominate the mix, with quality notifications appearing as a third large contributor in regulated industries.
The structural risk is that a digitization initiative that adds plant connectivity also adds document volume, often outside the scope of the SAP renewal forecast. The two budgets have to be modeled together rather than separately.
Financial services estates carry heavy bot and RPA workloads, often built around finance operations and reconciliation. Financial documents dominate, and the document volume is more sensitive to operational decisions than to revenue. A single new RPA workflow can double the document count for a specific document type.
The watch for financial services is the bot inventory itself. A clear list of automation flows, with the SAP document types each one creates, is the single most useful artifact for a renewal conversation in this segment.
Public sector estates often carry deep EDI traffic with statutory partners and large portal populations. Service and material documents tend to dominate, and the document volume is shaped by mandates as much as by business growth.
The complicating factor is procurement timing. Public sector renewals often run on a fixed cycle that does not allow the buyer to time the conversation around an SAP quarter, which raises the value of measurement and lowers the value of timing alone.
Utility and telecommunications estates carry concentrated meter reading and customer billing flows. Material documents and financial documents dominate, and the document volume scales with the customer base, not with the SAP user count, in line with the retail pattern but more cyclical.
The leverage for utilities is the seasonal flow of the billing cycle. A baseline that captures the peak month, the average month, and the trough month gives a cleaner negotiating position than a single annual figure.
Named user licenses and digital access are two separate metrics under the same SAP estate. They interact, and a buyer who treats them as independent often pays for the same activity twice. The cleanest defensive posture treats them as one combined exposure with two meters.
A named user who logs in and creates a document creates a digital access document and consumes a named user license. Under the 2018 rules SAP no longer charges separately for the document if a named user with the right license type created it.
The exposure arises when the named user is wrongly classified, the user is dormant but still licensed, or the documents are actually created by an integration that posts on a named user's behalf. Each scenario is a small leak that adds up over a five year term.
A clean user review reclassifies users to the right SAP user type, removes dormant users, and reassigns batch and integration users to the right technical category. The work is unglamorous and decisive. It cuts the named user bill and reduces the digital access overlap at the same time.
The right cadence is annual. The right scope is every active and historical user, not just the recent additions. Most of the wins come from the historical population, because that is where the misclassification has been compounding.
SAP's commercial team is entitled to count a document once. Buyers who cannot show which documents were created by named users will be charged twice, because there is no record to point at. The buyer's evidence has to identify the named user behind each high volume document type.
This is one of the few areas where investing in user logging directly pays back. The cost of capturing user attribution on documents is small. The savings on the next renewal can be a multiple of that cost.
Under RISE with SAP, named users are converted to Full User Equivalents, known as FUE. The conversion math is itself a negotiation, and a clean named user baseline is the highest leverage input. Buyers who walk into the conversion with a clean named user inventory get better FUE math.
The two negotiations should be run in sequence with full visibility on both. Closing the named user cleanup first, then the digital access baseline, then the FUE conversion, gives the buyer three controlled levers rather than one tangled one.
Contract clauses are the difference between an exposure that resets every renewal and one that stays bounded. Five clauses do the heavy lifting on indirect and digital access. Negotiating all five gives the buyer a contract that can be defended for the term, not just for the next cycle.
The cap fixes how much the contracted document baseline can move year over year, usually in the band of three to seven percent. Without a cap, SAP can reset the baseline at every renewal on its own reading of the integration footprint, and the negotiation never ends.
The cap is the single highest leverage clause on this topic. It converts an open ended exposure into a bounded one and lets the buyer model the cost out across the contract term. A buyer who closes without a cap has not closed the negotiation, only delayed it.
The methodology clause specifies how the document count is measured, which sources are authoritative, and which windows are sampled. Without it, the next measurement is whatever SAP says it is. With it, the buyer can challenge a result that deviates from the agreed method.
The method should reference the buyer's measurement framework, not SAP's. A clause that names the buyer's tooling and time window gives the buyer the ability to repeat the measurement and show its work. SAP rarely disputes a method that is in the contract.
An audit notice clause sets the notice period and the response window in months rather than days. A buyer who has weeks to respond is reactive. A buyer who has months can build a fresh baseline and bring it into the audit on equal footing.
The right window is at least six months from notice to response, with a defined extension if the integration footprint has materially changed. Without this clause, an audit cycle gets compressed into a few weeks of crisis response.
A co terminus renewal date aligns the digital access renewal with the rest of the SAP estate. Without it, the buyer runs separate renewal conversations on separate clocks and loses the leverage of bundling them. With it, the negotiation becomes one event and the buyer's portfolio leverage scales.
Co termination also reduces administrative load and audit risk. One renewal cycle, one measurement, one negotiation, is far cheaper to run than three of each.
Swap rights let the buyer reallocate document volume across document types or move volume between affiliates without buying new licenses. Estates with shifting integration patterns benefit from these rights, because the buyer does not lose flexibility as the technology stack evolves.
Without swap rights, every change to the integration footprint can require a new commercial conversation. With them, the buyer's day to day operational decisions stay inside the contract envelope.
The shape of the settlement runs along a predictable timeline. Understanding the timeline helps the buyer time the measurement and the response, rather than reacting to whichever document arrives next.
The trigger is usually one of three things. Either SAP issues a formal audit notice, the annual system measurement returns a flagged result, or a renewal cycle opens with a new digital access quote attached. Each trigger has its own clock and its own response window.
The trigger sets the cadence. An audit notice is the longest, often spanning six to nine months. A measurement flag runs over three to six months. A renewal cycle is bounded by the term end date and is the most time pressured of the three.
Discovery is where SAP gathers the integration footprint and the buyer either contributes a measured baseline or accepts SAP's. This is the most important phase commercially, because the baseline written into the record here anchors every later conversation.
The buyer who has prepared a measured baseline arrives at discovery with the evidence. The buyer who has not arrives at discovery as the responder. The first arrives with a position. The second arrives with a problem.
SAP follows discovery with an opening commercial quote. The quote almost never reflects the lower band of the exposure. It reflects the upper band that survives discovery, plus a margin that anticipates negotiation. The number is real, but it is not yet final.
The right response is neither acceptance nor outright rejection. It is a structured counter that references the measured baseline, the methodology, and the contractual mechanics. That counter sets up the negotiation, instead of waiting for SAP to set it up.
Negotiation moves through three to six rounds in our experience, with a typical span of six to twelve weeks. The early rounds anchor methodology. The middle rounds settle volume bands. The last rounds settle the rate, the cap, and the contract clauses.
Most buyers focus on the headline rate. The realized settlement is far more sensitive to the band, the cap, and the renewal trigger conditions than to the line rate. A clean rate on an open band ends up larger than a high rate on a tight band.
Settlement is recorded in either an addendum to the existing SAP contract or a new digital access agreement, often layered into a broader renewal. The contract carries the agreed baseline, the cap, the methodology, and the audit response terms. Without all four, the negotiation reopens next cycle.
The buyer who closes settlement without the methodology and audit response terms written into the contract has only delayed the next argument. The buyer who closes with all four has bounded the exposure for the term and made the next renewal a smaller event.
SAP sets the opening claim. The integrations set the floor. The buyer who counts the documents first decides where the settlement lands.
SAP indirect access is the use of SAP functionality or data by people or systems that do not hold a direct SAP named user license. It covers portals, online sales sites, bots, and integration platforms that read or write SAP data. The 2018 digital access model re prices indirect access by counting documents created.
SAP digital access is the commercial model SAP introduced in 2018 to price indirect access by document. Nine document types are counted, covering sales, invoice, purchase, service, manufacturing, quality, financial, material, and time documents. The aim is to remove the named user double count.
It arises through integrations that create SAP documents on behalf of external systems or automated processes. The most common patterns are online sales orders, EDI invoices, customer and supplier portals, and RPA bots. A typical mid market estate carries four to eight integrations that drive most of the exposure.
SAP prices digital access per document on a tiered rate. The headline rate is not where the negotiation settles. The realized rate inside a structured renewal sits well below the list rate, and the tier boundary matters more than the line rate. The volume estimate that sets the tier is the largest lever.
Build a baseline over a representative twelve month window with seasonal adjustment. Inventory every integration that touches SAP, map each to the nine document types, instrument the four to eight largest directly, and document approximations on the rest. Save the configurations and logs as a single evidence artifact.
Probably not at zero. The realistic goal is to bound the exposure and shift the conversation from an open ended liability to a measured commercial discussion. Buyers who instrument the integrations and bring a measured baseline first settle at roughly 40 to 60 percent of the SAP opening claim.
No. RISE with SAP bundles infrastructure and S/4HANA with a managed service, but digital access is still priced separately inside the RISE contract. A RISE migration is therefore also an indirect access negotiation. A buyer who treats them as one conversation gets a better outcome.
Slow the response and stage the engagement. Acknowledge the audit without conceding a number, request the basis for SAP's measurement, and produce the buyer's own baseline against the same nine document types. The first defensible measurement on the record is the one the negotiation runs from.
The Digital Access Adoption Program is SAP's structured conversion path from the older indirect access discussion to the document model, with a discount tied to the baseline at conversion. DAAP is worth taking when the buyer has measured first and can show a clean estate. It is rarely worth taking on SAP's timeline alone.
The most useful clauses are a capped uplift on document volume growth, a defined methodology for measurement, an audit notice and response window in months not days, and a co terminus renewal date with the rest of the SAP estate. Without these, the exposure resets every cycle.
The integration map, the document baseline method, the SAP opening claim band by industry, the DAAP decision framework, and the renewal clause checklist that holds the realized settlement well below the opening exposure.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for SAP, procurement, and finance leaders running the next renewal or audit.
SAP sets the opening claim. The integrations set the floor. The buyer who counts the documents first decides where the settlement lands.
