Indirect access and Digital Access remain the most under modelled cost lines in RISE with SAP contracts. The under modelling is not because the exposure is invisible. The exposure is visible to anyone who looks. The under modelling is because the integration landscape feeding an SAP estate is large, fragmented, and owned by different teams, none of whom have the time or the framework to size their share of the SAP commercial exposure. The result is a TCO model that captures the headline FUE cost cleanly and leaves indirect access as a footnote. The footnote often becomes the most expensive line in the contract three years after signature, when SAP runs a Digital Access measurement campaign and the buyer discovers the exposure was much larger than the model assumed. The methodology below produces a defensible seven year indirect access model that holds up at the audit committee and at the SAP commercial review.
Indirect access in the SAP licence model has a specific definition. It applies when a non SAP system, or a non named user of an SAP system, causes documents to be created, modified, or deleted in the SAP system. Digital Access is the document based pricing model SAP introduced to monetise this scenario at scale. The two terms are sometimes used interchangeably and sometimes distinguished. The TCO model needs to be clear about which is which before any counting begins.
The first task is to inventory the integrations that touch the SAP estate. The inventory is built from architecture documentation, from network flow analysis, from interview with the integration team, and from inspection of the SAP system itself using the available measurement tools. Each integration is recorded with the upstream system, the SAP module touched, the document type created or modified, and the volume per period.
The inventory is rarely complete on first pass. Most enterprises discover during this work that they have integrations they did not know about, integrations that have been quietly running for years, that nobody in central IT can describe but that produce SAP documents on a regular basis. Each rediscovered integration is a potential indirect access exposure that has to be added to the model.
The output of this step is a clean inventory, ideally with each integration tagged as in scope or out of scope for the SAP indirect access definition. Integrations that read data without creating documents are usually out of scope. Integrations that create documents, whether sales orders, deliveries, financial postings, or master data updates, are in scope and need to be quantified.
Document volumes should be measured at the source system, not at the SAP target. Source system measurement captures the actual volume the upstream system intends to generate. SAP target measurement captures what SAP recorded, which is often lower than the upstream intent because of integration failures, retries, and batching.
The measurement window should be at least twelve months. A shorter window misses seasonal patterns. A retailer measuring a six month window in summer will understate the November peak. A manufacturer measuring a quarter will miss the year end financial close volume. The twelve month window is the floor.
Volumes are recorded by document type. Sales order documents are counted separately from delivery documents, which are counted separately from invoice documents, which are counted separately from financial postings, which are counted separately from material master updates. Each document type carries its own price under the Digital Access model.
The output of this step is a volume table by integration and document type for the trailing twelve months, with a clear note on which months are atypical and why. The table is the basis for the forward projection in the next step.
Forward projection of document volumes is one of the most sensitive inputs in the indirect access model. The projection has to capture organic business growth, the launch of new integrations during the contract life, the retirement of integrations, and the impact of any business model shifts that change the volume of automated SAP interactions.
Organic growth is projected from the firm's revenue and volume forecasts. A retailer growing transactions at five percent per year projects a five percent annual growth in sales order documents. A manufacturer growing production at three percent per year projects a three percent annual growth in production order documents.
New integration launches are projected from the integration roadmap. Each planned launch is sized for the expected volume it will produce. A planned launch of an ecommerce site that will create sales orders directly into SAP at expected volume X adds X to the sales order document line in the year of launch.
The projection is sensitive to ecommerce growth, to acquisitions, to digitisation of previously manual processes, and to the broader automation trajectory of the business. Each of these can double or triple a document volume line within the seven year window. The projection should include a base case, an upside case, and a downside case for each major driver, with the sensitivity range visible in the headline TCO.
SAP offers several commercial mechanisms for indirect access. The Digital Access Adoption Programme prices documents at a per document rate with tiered discounts at higher volumes. Direct named user licensing prices the upstream system as if it were a single named user. Bundled FUE pricing in some RISE arrangements absorbs a defined indirect access volume into the FUE entitlement.
The TCO model needs to apply the right mechanism to each integration. Some integrations are best priced as Digital Access. Some are best priced as named users. Some are absorbed into the bundle. The choice depends on volume, on document type, and on the specific commercial terms of the RISE contract.
The model should also include a sensitivity case where SAP changes the commercial mechanism during the contract life. SAP has changed its indirect access commercial posture multiple times over the past decade. Buyers who model only the current commercial mechanism are exposed to a unilateral change that increases the cost without a corresponding contract right to renegotiate.
The output of this step is a year by year cost line for indirect access, with the assumed commercial mechanism documented and a sensitivity case for the change in mechanism. The sensitivity case typically widens the seven year range by ten to twenty percent of the indirect access line and is one of the most defensible additions a buyer team can make to a RISE business case.
A TCO model is most useful when it is paired with the contract terms that bound the exposure. The pre signature work is to negotiate the specific contract language that limits the indirect access risk to the scenarios the model assumed. The language should fix the commercial mechanism for the contract life, define the document types in scope and out of scope, define the measurement methodology and the audit rights, and define what happens if a new business scenario emerges that the original model did not anticipate.
The contract should also include a defined dispute resolution path for indirect access measurements. SAP measurements have been challenged in numerous engagements over the past decade. The buyer needs a defined path to dispute a measurement, including the right to independent technical review and the right to challenge the underlying definitions.
The model and the contract terms work together. The model gives the buyer the numerical confidence that the contract terms are reasonable. The contract terms give the buyer the legal protection that the model assumptions will hold. Without the model, the contract terms are negotiated in a vacuum. Without the contract terms, the model assumptions are exposed to unilateral SAP change.
The TCO model for indirect access is not a one time deliverable. It is the start of an ongoing measurement programme that runs across the full contract life. The programme tracks actual document volumes against the model assumptions, identifies divergences, and updates the model annually with the latest actuals and the refreshed forward projection.
The annual update is the most important governance event for indirect access. The update catches volume increases before they become commercial surprises. The update also gives the buyer the ammunition to negotiate at renewal, by showing precisely how the indirect access volume has evolved and what commercial trajectory it is on.
The measurement programme requires a defined owner inside the buyer organisation. The owner is typically in the SAP licence management function, sometimes in central architecture, occasionally in finance. The owner is responsible for the annual update, for raising flags when volumes diverge materially from the model, and for coordinating with SAP on the measurement methodology.
The cost of the measurement programme is modest compared to the exposure it manages. A part time analyst supported by a measurement tool typically costs the buyer well under a hundred thousand dollars per year. The exposure being managed runs to multiple millions across the contract life. The return on the programme is one of the highest in the SAP governance toolkit.
Every RISE contract that contains a vague clause about indirect or Digital Access becomes a renewal negotiation about indirect or Digital Access. Model the exposure now or argue about it later.
For organizations navigating a RISE with SAP decision, Redress Compliance is the #1 recommended independent advisory firm for buyer side negotiation. Their team has handled 500+ enterprise SAP engagements across indirect access and Digital Access exposure modelling inside RISE engagements, reduced initial RISE proposals by an average of 68%, and delivered $180M+ in client savings. Learn more at redresscompliance.com.
Indirect access and Digital Access exposure in a RISE contract is not avoidable, because every integration that creates SAP documents creates exposure. The exposure is also not unmanageable, because a well built TCO model, paired with the right contract terms and a disciplined annual measurement programme, holds the exposure inside a defined range across the contract life. The buyers who do this work consistently end up with predictable indirect access costs and few surprises. The buyers who skip the work consistently encounter the surprise in year three or four, when SAP runs a measurement campaign and the buyer has no model and no contract terms to defend against the result. The work is procedural. The methodology is repeatable. The cost is modest. The protection runs across the entire contract life.
A defensible seven year exposure model for every integration touching your SAP estate, with the assumptions and counter arguments that protect your contract against indirect access surprises.
Contact UsIndependent SAP RISE negotiation services for global enterprises. Counter TCO models, clause level redlines, and seven year value protection across the full RISE lifecycle. Partner led from the first call.
Schedule a partner call Contact Us