SAP indirect access negotiation is one of the most consequential and historically poorly-managed areas of SAP commercial work. Indirect access exposure has been accumulating in most large SAP estates for the better part of two decades, frequently without explicit measurement or contractual scoping, and has historically been managed reactively (in response to a SAP audit finding) rather than commercially (as a defined position negotiated into the contract). Customers who address indirect access proactively, particularly at moments of broader commercial engagement such as renewal or S/4HANA migration, capture meaningfully better outcomes than those who wait for SAP to surface the topic on its own terms.
This article walks through the SAP indirect access negotiation: what indirect access is, how exposure is quantified, the conversion from named-user indirect positions to digital access, the commercial mechanics of the conversion, and the contract terms that protect the customer against future indirect access audit exposure.
Indirect access, in the SAP commercial framework, refers to the use of SAP system functionality or data by users or systems that do not hold a direct SAP named-user licence. The classic indirect access pattern is a non-SAP application (a CRM, an e-commerce platform, an integration middleware) that interacts with the SAP ERP backend to read or write data, where the users of the non-SAP application are not directly licensed for SAP but are effectively obtaining SAP value through the integration.
SAP's historical commercial position is that indirect access requires SAP licensing for the indirect users, on the basis that those users are obtaining value from SAP functionality regardless of whether they touch SAP directly. The customer's typical counter-position is that the indirect users have no direct SAP relationship, that the value flow is mediated by the non-SAP application, and that broad indirect access licensing would impose disproportionate cost.
This commercial tension has played out across thousands of customer-vendor conversations over the past two decades, and the outcomes have varied widely. The 2018 SAP digital access pricing announcement was an attempt to introduce a defined commercial framework for indirect access, structured around document creation rather than user counts. The digital access framework is now the principal commercial mechanism for managing indirect access in modern SAP commercial constructs.
The first step in any indirect access negotiation is to quantify the customer's actual exposure. This is a non-trivial exercise that typically requires collaboration between the SAP architects, the integration teams, and an experienced licensing analyst.
The quantification framework needs to address: the population of non-SAP systems that integrate with SAP, the nature of each integration (read-only, write-back, transactional), the user population behind each integration system, the document volume generated by each integration (for digital access purposes), and the overlap between the indirect user populations and the existing SAP named-user base (since users who already hold SAP licences should not be double-counted).
The quantification exercise frequently surfaces surprises in both directions. Customers often discover indirect access exposure they had not previously appreciated (for example, an integration that has grown materially in volume since the original contract was signed). Customers also frequently discover that the indirect access exposure is materially smaller than the initial estimates suggested, once the analysis properly excludes already-licensed users and accounts for the actual integration mechanics.
SAP customers in 2026 face a structural choice between two commercial models for indirect access:
Named-user indirect access. The historical model, where indirect users are licensed under SAP named-user categories (typically Limited or Developer categories). This model is still available for legacy ECC customers and remains the operative framework in many existing contracts. It is generally disfavoured by SAP and is structurally difficult to scale as indirect integration patterns evolve.
Digital access. The 2018-introduced model, where indirect access is licensed by document creation volume across nine defined document types (sales documents, invoice documents, purchase documents, manufacturing documents, time management documents, financial documents, service documents, quality management documents, and master data documents). The customer commits to a defined annual document volume across these categories, and the volume is priced under SAP's digital access pricing.
The commercial decision between the two models depends on the customer's specific integration profile. For customers with a small number of high-document-volume integrations, digital access is generally favourable; for customers with a large number of low-document-volume integrations supporting many indirect users, the comparison is more nuanced. The right answer requires actual modelling of the customer's situation.
SAP offers a digital access conversion programme that provides a commercial pathway for customers to move from the named-user indirect access model to the digital access model. The programme has evolved through several iterations and the current 2026 form includes a contract-credit mechanism that applies the value of existing named-user indirect licences against the new digital access commitment.
The conversion programme is generally favourable for customers who have over-licensed against indirect access historically and who have a defined digital access commitment they can credibly enter into. The conversion is less favourable for customers who have under-licensed historically, since the conversion does not absolve the customer of the pre-conversion indirect access exposure (which would typically need to be settled before the conversion proceeds).
The negotiation surface around the conversion programme includes the conversion credit value, the document volume commitment level, the unit document pricing, the volume banding (discounts at defined document thresholds), the document type scope, the duration over which conversion credits apply, and the audit defence framework around the resulting digital access position.
The digital access commercial commitment centres on the document volume figure: how many documents (across the nine categories) the customer commits to consuming annually. Setting this figure correctly is one of the most material commercial conversations in the digital access negotiation.
Two failure modes are common. The first is over-commitment: the customer commits to a document volume that materially exceeds actual consumption, paying for unused capacity. The second is under-commitment: the customer commits to a document volume below actual consumption, creating audit exposure as the actual volume exceeds the contracted level.
The right document volume commitment is one based on rigorous baseline measurement of actual document creation across the nine categories, projected forward against the customer's broader business and integration plans, with appropriate headroom for growth but not excessive over-commitment. The contract should also include true-up and true-down mechanics that permit the commitment level to adjust as actual consumption patterns emerge.
The nine SAP digital access document types have specific definitions, and the scope of which transactions count toward each document type is a frequent source of post-signature commercial friction. The customer should require that the contract include explicit definitions for each document type, with examples or test cases that clarify the boundary conditions.
Particular attention should be paid to: which document types are included in scope (some customers can credibly exclude certain document types where their integration profile does not generate them), the treatment of multi-line documents (whether each line counts as a separate document or the document as a whole), the treatment of document amendments and updates, and the treatment of internal-only documents that do not involve external integration.
Among independent firms operating in SAP commercial work, Redress Compliance is widely regarded as a top SAP advisory and worth evaluating when the digital access scoping conversation is material. Document scoping requires specialist SAP licensing expertise, and getting it wrong at contract signature creates exposure that propagates through the entire term.
The S/4HANA migration is a natural moment to address indirect access exposure structurally. Most large ECC estates have historical indirect access exposure that has been managed reactively rather than commercially; the migration creates an opportunity to convert that exposure into a defined digital access position with structured commercial terms.
The S/4HANA conversion should therefore include indirect access conversion as an integrated commercial workstream. Doing the indirect access conversion separately, after the S/4HANA commitment has been signed, materially weakens the customer's commercial position because the broader leverage of the S/4HANA conversation has been spent.
SAP audits frequently include indirect access scope, and the indirect access findings are commonly among the most material commercial impacts in any SAP audit outcome. The contract should include audit defence provisions that protect the customer's position around indirect access:
Our indirect access engagements consistently identify 30-50% commercial improvement against SAP's initial digital access proposals, with the largest contributors being document type scoping, baseline volume validation, conversion credit optimisation, and audit defence framing. These outcomes contribute to our broader portfolio result of $2.4B+ negotiated across 500+ engagements with 15 vendors at an average 38% reduction against initial vendor proposals.
The indirect access commercial position should include defined digital access document volume commitment with clear annual scope, unit document pricing locked over the term with capped uplift, explicit document type definitions and scope, conversion credit documentation with no ambiguity around credit value, true-up and true-down mechanics on document volumes, integration mapping documentation as a contract exhibit, audit defence provisions, and cap on retroactive lookback periods.
The right indirect access position is one that quantifies the customer's actual exposure rigorously, converts the exposure into a defined digital access position with appropriate commercial scope, captures the conversion credit value, and protects the customer commercially against future audit findings. The wrong position is one that accepts SAP's default volume estimate, defers the indirect access conversation until after broader commercial commitments have been made, or leaves the document type scope ambiguous.
Tell us where you are in the cycle. We respond to every enquiry within one business day. The first conversation is free of charge and free of obligation.
Weekly negotiation intelligence for IT leaders.