How RISE changes indirect access economics.

Indirect access has been the most contested line item on SAP customer balance sheets for the past decade. Under classic on premise SAP licensing, an indirect access exposure could materialise from any third party system that read data from or wrote data to the SAP digital core. Under RISE with SAP, the framing changes. The Digital Access Adoption Programme, the bundling of certain document classes into the FUE construct, and the operational reality of the cloud delivery model produce a different economic pattern. Some exposures collapse. Others persist in a new form. A few new ones appear that did not exist under the previous licensing regime. The buyer team that does not map these changes ends up with a contract that either over commits or fails to address a real exposure.

The classic indirect access model, briefly.

Under the classic licensing model, indirect access was measured by SAP through manual audits and through the licence audit workbench. Any human or system that consumed SAP data through a third party tool was considered to be a user of the SAP system and required to be licensed accordingly. The result was a continuous audit posture in which the buyer never quite knew where the exposure stood. The Digital Access Adoption Programme introduced a document based counting framework that converted the user based exposure into a transaction based exposure, with nine document classes counted at defined prices per document.

The economic effect was significant. A buyer who had a large indirect user footprint but a modest document volume could often reduce the exposure by switching to the document counting model. A buyer with the reverse profile, modest indirect users but very high transaction volumes, often found the document model worse than the user model. The choice between the two models, and the negotiation around the document price per class, was a major component of every renewal between 2019 and 2024.

What changes under RISE.

Under RISE with SAP, the FUE construct subsumes the user based licensing question for users who access the system through SAP front ends. The document counting framework remains in place for indirect access from third party systems. The crucial commercial change is that the document fee schedule is folded inside the RISE subscription, not invoiced separately. The buyer no longer pays a separate digital access invoice. The buyer pays a single RISE subscription that includes an entitlement of documents per year, with overage pricing applied above the entitlement.

The entitlement is constructed during the RISE negotiation. The SAP account team typically proposes an entitlement based on the existing run rate plus a growth assumption. The negotiation lever is the size of the entitlement, the growth assumption, the overage price, and the cap on overage exposure. Each of these is negotiable, and each has a measurable effect on the seven year cost.

The reduced exposure for traditional read interfaces.

Under RISE, a category of indirect access exposure effectively disappears. Read only access from analytics tools, reporting tools, and downstream data warehouses, where the data is extracted from the SAP system and consumed elsewhere, is generally not counted as a chargeable document event. The buyer who has been carrying licence reserves for these read interfaces can release them at the point of conversion to RISE. The released reserve is a real economic benefit, often two to four percent of the seven year RISE TCO for buyers with significant analytics footprints.

The change does not eliminate the exposure entirely. Read access that triggers downstream document creation, or that operates through certain integration patterns, can still consume documents. The mapping has to be done case by case. The general direction, however, is that the analytics integration pattern that was a persistent source of indirect access risk under classic licensing is largely neutralised under RISE.

The persistent exposure for transactional integrations.

Transactional integrations remain fully exposed. Any third party system that creates documents in the SAP digital core, such as a customer facing portal that creates sales orders, a supplier portal that creates purchase orders, or an EDI gateway that creates inbound or outbound documents, generates document events that are counted against the RISE entitlement. The economic question is not whether the document is counted. It is what price applies to the document and what entitlement covers it.

The buyer team should map every transactional integration during the RISE negotiation. The map should identify the integration, the document class generated, the current annual volume, and the projected volume across the RISE term. The map becomes the basis for the entitlement negotiation. Without the map, the buyer is negotiating against an SAP forecast that the buyer cannot independently validate. With the map, the buyer is negotiating from a position of knowledge.

The new exposure from cloud native integrations.

RISE introduces a category of exposure that did not exist in the classic environment. Cloud native integrations, particularly through SAP BTP services and through the SAP Integration Suite, generate document events that are counted differently than the equivalent on premise integration. A workflow that previously ran inside an SAP on premise system using ABAP code and an RFC call may now run through a BTP service that creates discrete document events in the digital core. The same business process generates more counted documents under RISE than under the previous model.

The buyer team should review the planned BTP usage and the planned integration topology during the RISE negotiation. Where the cloud native pattern will generate elevated document counts, the entitlement and the overage price need to reflect that. The SAP account team is generally aware of the effect. The account team does not always volunteer the calculation. The buyer team that asks for the worked example before signing captures the entitlement that is appropriate for the topology.

The Digital Access Adoption Programme, the bundling of certain document classes into the FUE construct, and the operational reality of the cloud delivery model produce a different economic pattern.

The negotiation levers, in order of value.

For most enterprise RISE deals, the indirect access economics can be optimised through four levers, in approximate order of value. The first lever is the entitlement size, set at a level that covers the projected document volume across years one through seven, with a small buffer rather than a large reservation. Over reservation transfers buyer cost to SAP margin. Under reservation creates overage risk. The right answer is the run rate plus a documented growth factor.

The second lever is the overage price. The standard overage rate is typically two to three times the entitlement unit rate. The buyer should negotiate the overage rate down toward parity with the entitlement rate, particularly for document classes where growth is most likely. The third lever is the cap on overage exposure per year, which protects the buyer from a runaway document count caused by an integration defect or an unexpected business event. The fourth lever is the right to recalibrate the entitlement at year three and year five based on actual run rate.

Conclusion.

RISE does not eliminate indirect access exposure. It restructures it. Read only analytics integrations largely fall out of scope. Transactional integrations remain fully in scope but on a clearer counting basis. Cloud native BTP integrations introduce a new pattern of document generation that the buyer team must model explicitly. The negotiation levers, the entitlement size, the overage price, the cap, and the recalibration right, are well understood by the SAP commercial team. The buyer who maps every integration, documents the run rate, and negotiates each lever captures the economic benefit of the change. The buyer who treats indirect access as resolved by the move to RISE often discovers, two years into the contract, that the resolution was less complete than assumed.