Map your indirect and Digital Access exposure before SAP does.

RISE does not retire indirect access exposure

The first claim most buyers hear from their SAP account team during a RISE conversation is that moving to RISE simplifies licensing and eliminates indirect access concerns. This is not accurate. Indirect access, now most often priced under the Digital Access Adoption Program (DAAP) or its successor models, is a separate exposure that survives the move to RISE. It is calculated against document creation volumes by non SAP systems, and those volumes do not change because the SAP environment moved to a hyperscaler.

Across 500 engagements, the firm has reviewed indirect access exposure on hundreds of RISE proposals. In roughly two thirds of cases, the buyer underestimates exposure by a factor of three to ten. SAP, on the other side, often arrives at the indirect conversation late in the negotiation with a much larger number, when buyer leverage has already been spent. The result is a punitive supplemental order that adds to the RISE total. The fix is to measure first, negotiate during the RISE engagement, and lock the indirect terms inside the same contract.

Document volume, integration patterns, and licensing position

The exposure model is built bottom up from three data sources. First, a system inventory of every integration to and from SAP, including direct connections, middleware (PI, PO, BTP Integration Suite, MuleSoft, Boomi), event bus subscriptions, and custom interfaces. Second, the document volume created or read by those connections, measured against the nine SAP document categories that drive DAAP pricing (Sales, Purchase, Service, Financial, Time, Quality, Production, Material, and Inventory).

Third, the existing licensing position. We reconcile your current SAP entitlement, including any prior DAAP buyout, against actual measured document volume. The output is a forward looking exposure number, expressed in DAAP documents and in dollars, and a recommended negotiation position. Where exposure is high, the right move is often to fold a multi year DAAP cap into the RISE contract itself rather than carry a separate license item.

How the engagement runs

The engagement follows a four phase sequence, typically delivered in four to eight weeks depending on the size of the SAP estate and the number of non SAP systems in scope. Phase one is integration inventory and document mapping, conducted with the client architecture team. Phase two is volume measurement, using SAP standard reports (USMM, SLAW, and the Passport reports for document accounting) plus middleware logs.

Phase three is exposure modelling. We project document volumes forward across the seven year TCO horizon, build a DAAP tier scenario, and value the exposure at SAP list and at our benchmark negotiated rates. Phase four is the negotiation recommendation. This includes the proposed indirect terms to embed in the RISE contract, the language to require, and the financial value to claim back against the headline RISE figure as part of a bundled negotiation.

Patterns we see in nearly every engagement

Several patterns recur. Salesforce Service Cloud cases routinely create more Sales Documents in SAP than buyers realise, because each case escalation that opens a service order in SAP counts. Workday integrations create HR document flow that buyers tend to exclude from their internal estimate. ServiceNow change records, where they trigger SAP transports or notifications, can fall inside the document definition depending on configuration. Custom B2B portals frequently create Sales and Purchase documents at high volume.

On the SAP side, common findings include legacy Named User position that no longer reflects how the business uses the systems, prior DAAP buyouts that have lapsed in their pricing protection, and indirect language in the existing on premise contract that may or may not survive a conversion to RISE. We document each finding, value it, and bring it to the negotiation table with supporting evidence rather than as a position to be argued.

Deliverables

The engagement delivers four artifacts. First, the integration and document inventory, mapped to DAAP categories. Second, the seven year exposure forecast, with low, base, and high scenarios. Third, the recommended contract language for indirect and Digital Access protections to embed in the RISE order form, including caps, true up timing, and dispute procedure. Fourth, the negotiation brief: a partner ready summary that the client commercial team uses in the RISE negotiation itself.

Across recent engagements, indirect and Digital Access exposure work has averaged $3.4M in identified savings against the SAP standalone position, and has prevented an average of $1.8M in post signature supplemental orders. The exposure model also feeds directly into the seven year TCO model produced in the parallel TCO Modelling engagement (SVC.02), so the two services together give the buyer a unified financial picture before any commitment is made.

Begin with the integration inventory.

If you have a RISE proposal on the table and no current view of your indirect and Digital Access exposure, the first engagement step is a four week integration inventory. We coordinate with your architecture team, conduct the measurement, and return an exposure baseline before the RISE negotiation enters the contract phase.