When an SAP indirect-access exposure is real, the buyer has more options than the audit team usually presents. The default conversion offer is to switch the buyer onto the Digital Access document model and to settle the historical exposure at SAP-defined tier pricing. The default is sometimes the best option; it is rarely the only one. Across the matters we have worked, the conversion landscape has four distinct paths, each with its own economic logic, contractual mechanics, and operational consequences. This article describes the four, the conditions under which each is the best fit, and the order-form discipline that makes any of them work.
Option one — Digital Access conversion
The conversion to Digital Access is the option SAP usually leads with. The buyer’s indirect-use exposure under the pre-2018 contract is converted to a measured Digital Access entitlement under the post-2018 document model. The contractual mechanics are an amendment to the existing agreement plus an order form that specifies the chargeable documents, the tier pricing, and the entitlement volumes.
The economic case is favourable when the integration topology is dominated by a small number of measurable document types and when the document volumes are stable or predictable. The case is unfavourable when the topology is dominated by read-only flows, by very high-volume telemetry, or by integration patterns where the chargeable surface is ambiguous. The methodology is in our indirect-to-digital migration article and in the Digital Access topic page.
Option two — contractual amendment without conversion
The second option, used less often but often the better trade for the right estate, is to amend the existing pre-2018 contract to clarify the indirect-use position without converting to Digital Access. The amendment defines, in writing, which integration patterns are within the indirect-use scope, which are not, and the pricing or entitlement that applies. The buyer remains on the pre-2018 model but with the contractual ambiguity resolved.
The economic case is favourable when the pre-2018 indirect-use clause is contractually weak in SAP’s favour, when the integration topology does not lend itself to a clean document model, or when the buyer wants to preserve optionality for a future RISE conversion in which the indirect-use position would be re-papered anyway. The contractual lever is the same as in any major contract negotiation: the cost of the amendment is paid in concessions elsewhere in the renewal. The pattern is covered in our contract clauses article.
Option three — scope exclusion
The third option is to exclude specific integration patterns from the chargeable surface by contractual mechanism, leaving the rest of the estate on whichever pricing model applies. The exclusion typically covers read-only flows, very high-volume telemetry, or integration patterns where the document-counting logic is mismatched to the business reality. The mechanism is a schedule to the order form that defines the excluded patterns and the conditions under which the exclusion holds.
The economic case is favourable when one or two integration patterns dominate the audit-time exposure but do not, on a contractually defensible reading, belong in the chargeable surface. The exclusion is often the lowest-cost remedy: it changes nothing about the rest of the estate, it resolves the specific dispute, and it survives the contract term. The Digital Access exemptions article covers the exclusion mechanics on the post-2018 model.
The read-only exclusion
The most common scope exclusion is the read-only carve-out. Data flows that move SAP-originated data to a downstream BI, analytics, or master-data system without creating or updating SAP documents are usually defensible as outside the chargeable surface. Writing the carve-out into the order form is the contractual instrument that makes the position durable. The pattern is documented in our middleware risk article.
Option four — license remediation
The fourth option, sometimes appropriate for estates with very narrow indirect-access exposure, is to remediate the exposure by adjusting the licensed population rather than by converting the model. If the exposure is driven by a defined population of non-SAP users who derive direct benefit from SAP data, the population can sometimes be licensed under named-user provisions at a cost lower than the conversion economics would imply.
The economic case is favourable when the exposed population is small, well-defined, and stable. The case is unfavourable for the typical modern integration topology, where the exposed surface is the document flow rather than the user population. The licensing remediation is the historical answer to indirect-use exposure and is now usually the wrong shape, but it remains the right answer in a narrow set of cases. Our named-user buckets article covers the licensing mechanics.
The economic comparison
Across the four options, the economic comparison runs on three dimensions: the up-front cost of the conversion or remediation, the steady-state run-rate cost over the contract term, and the optionality preserved for future contract events. The Digital Access conversion typically has a moderate up-front cost, a measurable steady-state cost, and modest optionality. The contractual amendment has a low up-front cost, a steady-state cost similar to the current run rate, and high optionality. The scope exclusion has a very low up-front cost, a steady-state cost equal to the current run rate, and moderate optionality. The license remediation has a variable up-front cost, a low steady-state cost on the remediated population, and low optionality.
The choice between the four depends on the specifics of the estate, the contractual position, and the buyer’s strategic outlook. A blanket recommendation is not possible; the methodology for the choice is in our indirect-access advisory service page and in the indirect-access white paper.
The order-form mechanics
Each of the four options is implemented through specific order-form mechanics. The Digital Access conversion is implemented through an amendment to the master agreement plus an order form that specifies the chargeable documents, tiers, and entitlements. The contractual amendment is implemented through a written amendment to the master agreement that clarifies the indirect-use position. The scope exclusion is implemented through a schedule to the order form that defines the excluded patterns. The license remediation is implemented through a purchase order under the existing master agreement.
The mechanics matter because they determine the durability of the conversion. An amendment to the master agreement is more durable than a schedule to an order form; a schedule is more durable than a side letter; a side letter is more durable than a verbal understanding with the SAP-side account team. The drafting discipline is to push the position as high up the contract hierarchy as the SAP-side can accept. The post-audit settlement tactics article covers the hierarchy.
The RISE connection
For buyers in the path of a future RISE conversion, the indirect-access position will be re-papered as part of the RISE order form. The optionality consideration is whether the conversion option taken now will survive the RISE re-papering, or whether it will be subsumed into the new contract. The Digital Access conversion is usually portable into RISE; the contractual amendment is usually re-negotiated; the scope exclusion is usually re-presented in the new schedule; the license remediation is usually re-counted. The RISE conversion negotiation article covers the re-papering question.
The conversion to Digital Access is the option SAP leads with. It is sometimes the right answer. It is not always the right answer. The contractual amendment, the scope exclusion, and the license remediation each have a fit profile, and the buyer’s position is stronger when all four are on the table.
If an SAP indirect-access exposure is on the table now, the first analytical step is to compare the four options against the specifics of the estate. The cost of the analysis is contained; the cost of the wrong conversion compounds for the contract term.
The economic case for the comparison
Across our $180M+ in client savings, the difference between the conversion option SAP led with and the conversion option that actually fit the estate has been one of the larger sources of value. The 68% average claim reduction across audit matters includes a meaningful contribution from the choice of conversion path. The work of running the comparison is contained: a four-to-six week analytical engagement that produces a defensible recommendation. The global retailer case file documents one such comparison in full.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.