Indirect and digital access under RISE, complete guide.

Indirect and digital access under RISE with SAP is the surface where the most expensive surprises continue to land. The Digital Access Adoption Programme, known as DAAP, replaced the older indirect access model with a document based counting framework that priced access by the volume of documents generated rather than by the number of users behind the system that generated them. Inside RISE, that framework persists, but with new wrinkles. The hyperscaler topology, the BTP integration patterns, the SAP delivered managed service model, and the document counting methodology all interact, and the buyer who has not walked the surfaces will find them at the year one true up rather than during the negotiation. This pillar article walks the complete model, what triggers exposure, how to size the entitlement, the contractual rewrites that hold the line, and the post signature optimisation work that keeps the cost contained across the seven year term.

What indirect and digital access actually means inside RISE

Indirect access is the term SAP uses for any consumption of SAP delivered functionality by a system or a user that is not directly licensed for the named SAP product. Digital access is the modern framing, applied through the DAAP, which prices that consumption against a per document fee for the documents generated inside the SAP system through indirect channels. The document categories that the DAAP captures are sales, invoice, purchase, service entry, manufacturing, quality, financial, and material documents. Each document generated through an indirect channel is counted, and the count produces the digital access entitlement that the contract has to cover.

Inside RISE, the digital access model carries forward but with adjustments that the buyer side review has to capture. The first adjustment is that the RISE bundle includes a baseline digital access allocation, sized against the workload estimate. The second is that the overage rate, when the actual document volume exceeds the bundled allocation, applies at the SAP prevailing rate at the time of true up rather than at the rate inside the contract. The third is that the document counting methodology inside RISE is documented in the SAP technical configuration of the workload, which means that the counting can shift if the configuration is updated during the term. Each of these three adjustments is a surface where the cost can drift, and each one is recoverable through the negotiation.

The exposure surfaces inside a typical RISE deployment

The exposure surfaces inside a RISE deployment fall into seven categories. The customer portal that allows external users to place orders, raise service requests, or interact with the order to cash process. The supplier portal that allows external suppliers to respond to purchase orders, submit invoices, or interact with the procure to pay process. The mobile applications that connect employees and partners to the SAP system through native apps. The EDI integrations that connect the SAP system to trading partner systems through document exchange. The third party CRM or commerce platforms that interact with the SAP system through service calls. The custom integrations that connect bespoke or homegrown applications to the SAP system. The reporting and analytics layers that consume SAP data through service calls rather than through bulk extracts.

Each of these seven categories produces documents inside the SAP system that the DAAP counts. The buyer side review has to map the seven categories against the actual deployment, count the documents that each category produces in production, and size the digital access entitlement against the documented volume. The mapping is rarely complete in the SAP proposal, which sizes the entitlement against an indicative estimate rather than against the actual exposure. Across the firm engagement base, the actual document volume measured at year one of a RISE deployment runs between forty and sixty percent above the SAP proposed entitlement, and the gap is paid as overage at the SAP prevailing rate.

The document counting methodology is the leverage point

The DAAP counts documents using a methodology that the SAP technical configuration enforces. The methodology has rules around what constitutes a document, when a document is counted, how documents created through system to system traffic are treated, and how exclusions apply for documents that should not count against the entitlement. The methodology is documented in the SAP technical notes but it is not bound inside the standard RISE contract, which means that an update to the methodology during the term can shift the counted volume.

The buyer side rewrite documents the counting methodology inside the contract, with the rule set frozen at signature and any future change subject to buyer consent. The rewrite also documents the exclusions that the buyer organisation requires, including the exclusion for system to system traffic between SAP systems inside the same RISE deployment, the exclusion for documents created during the data migration into the RISE environment, the exclusion for documents created through SAP delivered support or operations activities, and the exclusion for documents that are corrected and reversed rather than persisted as production data. With these exclusions in place, the counted volume aligns with the actual business activity rather than with the system mechanics, and the drift across the term is bounded.

The overage rate has to be capped inside the contract

The single largest source of digital access cost drift across the firm engagement base is the overage rate. The standard RISE template defines the overage rate at the SAP prevailing rate at the time of true up, with no contractual cap and no fixed schedule. The mechanic compounds the exposure across the term as the document volume grows with the business and as SAP repositions the digital access pricing through periodic commercial updates. The compounding effect is consequential. Across the firm engagement base, a digital access overage paid at the prevailing rate runs between one and three times the in contract rate, and the gap accelerates across the term.

The buyer side rewrite caps the overage rate at the year one rate, with a maximum annual uplift defined inside the contract across the remainder of the term. The cap applies to the overage rate that would be charged if document volume exceeds the bundled allocation, and the rate is bound regardless of any commercial repositioning that SAP applies to the broader digital access pricing during the term. The combined effect of the methodology rewrite and the overage cap consistently produces between five and twelve percent of the seven year contract value across the firm engagement base, with the higher end concentrated in deals carrying high transaction volume.

The bundled allocation has to be sized against the actual exposure

The bundled digital access allocation inside the RISE proposal is sized against the SAP estimate. The estimate is consistently conservative on the documents that the third party integrations produce, the customer portal generates, and the EDI volume creates. The buyer side review has to rebuild the estimate from the actual deployment scope rather than accepting the SAP supplied number. The work has three steps. The deployment scope is documented, with each of the seven exposure surfaces named and the integration boundaries captured. The document volume that each surface produces is measured against the existing system telemetry where the data is available, and modelled against industry benchmarks where the data is not. The combined volume is sized into the bundled allocation, with a defined growth assumption across the term.

The right sized allocation may be larger or smaller than the SAP proposed number, but in either case it is grounded in the actual deployment rather than in the SAP estimate. The firm has seen deals where the right sized allocation came in below the SAP proposed number, with the contract closing at the lower allocation and the cost saving recognised at signature. The firm has also seen deals where the right sized allocation came in above the SAP proposed number, with the buyer side leads using the documented exposure to negotiate a larger bundled allocation at the in contract rate rather than paying overage in year one. Either way, the work is to ground the entitlement in the deployment rather than in the assumption.

Post signature optimisation work keeps the cost contained

The work does not end at signature. The actual document volume in production has to be monitored, the integration patterns that produce documents have to be reviewed for optimisation opportunities, and the contract has to be exercised at the true up cycles to recover the value the negotiation has put in place. The firm runs post signature digital access optimisation work for clients that have signed the contract with the rewrites in place, and the work consistently surfaces between two and five percent of additional value across each true up cycle.

The optimisation work has four components. The document generation patterns are reviewed against the integration architecture, with attention to integrations that produce documents at higher volume than the business activity warrants. The reduction work targets the integration design, with adjustments to the document creation logic that reduce the counted volume without affecting the business outcome. The exclusion claims are exercised against the contract terms, with documentation that supports the exclusion of system to system traffic, corrected and reversed documents, and migration related documents. The true up cycle is run against the documented volume and the contracted rate, with attention to the calculation methodology and the supporting evidence that the cycle has to produce.

The renewal protection has to extend the digital access discipline

The digital access work survives into the renewal if the contract carries the right renewal protection. The renewal calculation for digital access inside the RISE renewal typically resets to the SAP prevailing rate, which means that the in contract rate the original negotiation established is at risk at renewal. The buyer side rewrite extends the renewal calculation protection to the digital access surface, with the renewal rate set at the closing year contract rate plus a defined annual uplift, capped inside the original contract.

The rewrite also extends the methodology and exclusion documentation into the renewal, with the rule set carrying forward unless explicitly renegotiated. The renewal cycle becomes an opportunity to update the methodology against the deployment as it has evolved across the term, with the buyer side leads carrying the leverage to refine the rules rather than accepting an SAP supplied reset. The renewal protection ensures that the value the original negotiation captured does not erode at the renewal point, and that the buyer carries the same leverage into the renewal as into the original signature.

The complete model is a discipline rather than a clause

The complete digital access model under RISE is a discipline that runs from the deployment scope mapping at the start of the negotiation through to the post signature optimisation and the renewal protection across the seven year term. It is not a single clause to negotiate, and it is not a single number to argue. The work is the methodical mapping of the seven exposure surfaces, the documented counting methodology, the contractually capped overage rate, the right sized bundled allocation, the post signature optimisation, and the renewal calculation protection. Each layer compounds the effect of the others, and the combined effect across the seven year term is consequential. Across the firm engagement base, a RISE deal closed without the digital access discipline produces a cumulative cost premium of between fifteen and twenty eight percent over the term against the same deal closed with the discipline applied. The discipline is the difference between a digital access line that compounds against the buyer and a digital access line that holds. The work begins with the deployment scope and the contract rewrite, and it continues through the operational life of the agreement. The buyer side leads that walk the surfaces, document the methodology, cap the overage, right size the bundle, run the optimisation, and protect the renewal close a RISE deal where digital access is a managed cost line rather than an unbounded exposure. The complete model is the method, and the method is the negotiation.