A common misconception about RISE with SAP is that it eliminates the audit exposure that characterises the on-premise estate. The reasoning runs that SAP operates the environment, SAP measures the consumption, and SAP charges the buyer based on contracted FUE units, so the traditional measurement-and-true-up cycle disappears. The reasoning is partly correct and partly wrong. RISE does eliminate certain audit surfaces — the buyer no longer runs USMM, LAW, or the standard measurement transactions. It introduces new audit surfaces in their place: FUE consumption against contracted entitlement, indirect-access measurement against integrated systems, BTP consumption against bundled allocation, and contractual compliance with the scope-of-use provisions. Across our SAP audit defence engagements we apply a consistent framework to the new audit surface.
What changes at the audit surface
The on-premise audit surface centres on the USMM and LAW measurement cycle: the buyer runs the measurement, the buyer submits the output, SAP analyses the output, the parties negotiate over the analysis. The RISE audit surface centres on FUE consumption: SAP runs the measurement on the managed environment, SAP reports the measured FUE consumption, and the buyer either accepts the report or challenges it. The structural shift is that the measurement instrumentation moves into SAP’s control.
The implication is that the buyer’s pre-submission inspection discipline — the cleanup, the cross-checking, the remediation — is no longer available in the same form. The buyer’s defensive posture must shift from pre-submission inspection to ongoing observability of consumption and to contractual provisions that constrain SAP’s measurement discretion. The RISE topic page covers the broader measurement model.
FUE consumption measurement
FUE consumption inside RISE is measured against the contracted FUE allocation. SAP-side instrumentation tracks the assigned users, classifies them by FUE-weight, and reports the consumption at defined intervals. The reported consumption against the contracted allocation determines whether the buyer is in compliance and whether true-up charges apply.
What the buyer must watch
Three things require buyer-side attention. First, the FUE-weight classification of users: the SAP-side classifier is not perfect, particularly for users with mixed activity profiles, and the buyer should validate the classification against its own usage data. Second, the user provisioning hygiene: assigning users into the FUE-weighted categories should be governed by the same dormant-user, role-mining, and reclassification discipline that the on-premise estate required. Third, the contractual definitions of FUE consumption: the contract should specify which user populations are measured, which activities count toward FUE consumption, and how disputes over classification are resolved. The RISE pricing model piece covers the FUE consumption mechanics in detail.
Indirect access inside RISE
The indirect-access exposure does not disappear inside RISE. Third-party systems that integrate with the RISE environment continue to consume SAP-licensable function, and SAP continues to measure the consumption. The measurement model inside RISE is typically Digital Access Documents (the per-document model introduced in the on-premise era), measured by SAP-side instrumentation on the RISE environment.
The contractual provisions vary. Some RISE contracts bundle a Digital Access allocation into the headline FUE pricing; some price Digital Access separately; some include audit rights specifically focused on indirect access that survive even where the FUE measurement is otherwise non-contentious. The buyer-side preparation is a documented indirect-access inventory: which third-party systems integrate with RISE, which documents each integration produces, and which scenarios produce measured Digital Access consumption. The indirect access advisory service covers the inventory framework.
BTP consumption audit
The BTP credits bundled inside RISE are consumed against the allocation and overage is billable separately. The consumption measurement is itself an audit surface: SAP-side instrumentation tracks BTP service consumption, reports against the allocation, and bills the overage. The buyer’s defensive posture is to validate the consumption reports against expected service usage, to identify anomalies that suggest mis-measurement or mis-categorisation, and to challenge the bills before settlement rather than after.
RISE moves the audit surface but does not eliminate it. The instrumentation moves into SAP’s control; the buyer’s defensive obligation moves into observability, classification validation, and contractual challenge. Buyers who accept SAP-reported consumption without independent validation are at a structural disadvantage they did not have on-premise.
Scope-of-use provisions
Beyond the consumption measurements, RISE contracts contain scope-of-use provisions that constrain what the buyer may do with the licensed environment: which user populations are entitled, which subsidiaries may use the environment, which integrations are permitted, which data may be processed. Each provision is a potential audit surface and each merits review at sign and during the contract life.
Common scope-of-use traps
Three traps recur. The first is undocumented entity expansion: the buyer’s corporate structure changes through acquisition or restructure, the new entities use the RISE environment, but the scope-of-use provisions were not updated. The second is undocumented user population expansion: new user populations gain access without the entitlement being updated. The third is integration scope creep: the integration inventory at sign was modest, but ongoing integration work has expanded the integrated surface beyond the contracted scope. Each trap produces a contractual breach exposure. The mid-term renegotiation piece covers the corrective process.
The negotiation at sign
The audit-related provisions in the RISE contract are negotiable at sign and difficult to revisit during the term. The provisions worth negotiating include: the FUE classification methodology and the buyer’s right to challenge classifications; the indirect-access measurement framework and any bundled Digital Access allocation; the BTP overage settlement terms and the right to challenge consumption reports; the scope-of-use provisions and the procedure for expanding scope without re-opening the contract; and the buyer’s audit-side rights to receive consumption data in usable form. Each provision is a defensible negotiation point and each carries five-year consequence. The RISE contract negotiation leverage white paper sets out the full negotiation framework. The retail RISE migration case file documents a buyer that worked through the audit-related provisions during a competitive selection.
— 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.
The follow-through
Inside RISE the audit narrative changes from a periodic measurement-and-true-up cycle to an ongoing observability-and-challenge model. Buyers who instrument the FUE consumption position themselves, who maintain a documented indirect-access inventory, and who challenge the SAP-side reports promptly when anomalies appear, retain the bulk of the leverage the on-premise model afforded. Buyers who treat RISE as audit-free find that the audit exposure has merely shifted from the measurement event to the consumption observability they never set up. The RISE exit terms piece covers the related provisions on the exit side that shape the buyer’s long-term position.