What Every CFO Should Ask Before Signing a RISE renewal

For many CFOs, the first RISE with SAP (SAP Cloud) contract was a transformation decision. The renewal is different. It is a financial governance decision.

By the time renewal discussions begin, the organization has usually moved beyond the strategic question of “Should we go to RISE?” The more important question becomes: Are we paying for the SAP environment we actually use, need, and can financially control over the next contract term?

That is where FinOps becomes essential.

RISE with SAP combines software, cloud infrastructure, technical services, and commercial subscription commitments into one bundled model. SAP positions RISE as a way to modernize ERP and simplify the journey to cloud ERP. But for the CFO, bundled does not automatically mean transparent. In fact, bundling can make it harder to see which cost drivers are growing, which services are being consumed, and where future true-up exposure may arise.

Before signing a RISE renewals, CFOs should ask five critical questions.

1. Do we have a clear baseline of what we bought, what we use, and what we no longer need?

A RISE renewal should never start with the supplier’s proposal. It should start with the customer’s own Effective License Position.

That means knowing the current SAP bill of materials, the contracted quantities, actual consumption, unused products, user classifications, engine metrics, Digital Access exposure, HANA usage, SAP public cloud consumption, and the financial value attached to each area. VOQUZ Labs’ visoryQ FinOps Manager is designed around exactly this governance model: importing the SAP bill of materials, consolidating measurements, assigning consumption to SAP products, and showing both quantitative and financial license consumption.

For a CFO, this matters because renewal negotiations are not only about unit prices. They are about avoiding the migration of shelfware, obsolete assumptions, and historical inefficiencies into a new multi-year subscription commitment.

2. Are our Full Use Equivalents based on real need or inherited assumptions?

RISE licensing is driven heavily by Full Use Equivalents, or FUEs. Under the FUE model, different user types consume different proportions of an FUE; for example, one FUE can correspond to one advanced user, five core users, or thirty self-service users, depending on the assigned usage category. SAP also describes the FUE model as a flexible concept for allocating users across different access levels in S/4HANA Cloud.

The CFO question is simple: Who validated the FUE number?

If the answer is “It came from the previous contract,” “It came from SAP’s proposal,” or “It was converted from ECC users,” there is a risk.

ECC license types, S/4HANA roles, RISE FUEs, and authorization-based measurements do not map neatly one-to-one. Overly broad roles and authorizations can push users into higher license categories even when their actual activity would justify a lower-cost classification.

This is why user optimization remains highly relevant even after moving to S/4HANA or RISE. VOQUZ Labs’ materials emphasize that user license management is still a relevant cost driver in RISE because incorrect user assignment can translate into unnecessary FUE consumption.

3. Can we separate software, infrastructure, services, and support costs?

One of the biggest financial challenges in RISE is that it combines several cost categories into a single commercial structure: software subscription, infrastructure, technical operations, service levels, and optional add-ons.

That can be convenient operationally, but risky financially.

The CFO should ask for transparency on the major components of the renewal. What portion of the cost is driven by FUEs? What is driven by infrastructure sizing? What is driven by additional systems, storage, disaster recovery, availability requirements, BTP, public cloud products, preferred success, or other support components?

The uploaded SAP licensing guide notes that RISE combines infrastructure, basic services, and software into a single contract, but also warns that additional storage, servers, and service requirements can escalate costs beyond the standard sizing assumptions. SAP’s own service-specification portal for S/4HANA Cloud private edition contains multiple roles-and-responsibilities and service-description documents, underlining that the operating model needs to be understood in detail rather than treated as a black box.

From a FinOps perspective, the CFO should not accept a renewal model that cannot explain cost movement. If usage grows by 10%, what happens to spend? If FUEs decrease, can the contract value decrease? If infrastructure needs change, can the environment be resized commercially, or is the company locked into the previous tier?

4. Are we managing SAP cloud consumption continuously or only at renewal time?

Traditional SAP license management was often annual and audit-driven. RISE renewals require a more continuous model.

FinOps is not a once-a-year spreadsheet exercise. It is an operating discipline that connects consumption, entitlement, budget, forecast, accountability, and corrective action. For SAP, this means quarterly or even monthly visibility into license consumption, public cloud consumption, business metrics, true-up risk, and financial exposure.

A strong SAP FinOps approach expands traditional license management into continuous financial governance. Instead of reviewing SAP usage only during annual measurement or renewal preparation, companies should regularly compare consumption across ECC, S/4HANA, RISE, public cloud, BTP, infrastructure, and services then translate that data into financial transparency, budget planning, and true-up risk management.

That is the shift CFOs should demand: from license measurement to SAP financial governance.

5. What happens at the next renewal if usage, business volume, or strategy changes?

The renewal being negotiated today will shape the company’s financial flexibility for years.

CFOs should challenge assumptions around growth, consolidation, divestments, acquisitions, system retirement, geographic rollout, business volume, and changes in SAP product strategy. A renewal that looks acceptable in year one may become expensive in year three if the company cannot reduce unused capacity, reallocate entitlements, or adjust consumption in line with actual business demand.

This is especially important because RISE changes the commercial risk profile from a historical perpetual-license model to an ongoing subscription commitment. The SAP licensing guide highlights that organizations should regularly review actual requirements under RISE because the subscription model creates an ongoing commitment rather than a one-time purchase.

A CFO should therefore ask: Can we forecast the financial impact of growth before it appears in an invoice?

A mature SAP FinOps model should be able to show where the organization is under-consuming, over-consuming, exposed to true-up, or carrying products that are no longer needed. It should also support what-if scenarios before negotiation, not after signature.

The CFO’s RISE Renewal Checklist

Before signing, every CFO should be able to answer:

• Do we have a current, reconciled SAP bill of materials?
• Do we know our actual consumption across users, engines, Digital Access, HANA, BTP, public cloud, and services?
• Do we have a quantified Effective License Position?
• Have FUEs been validated against actual usage and authorization structures?
• Can we identify shelfware and products out of use?
• Do we understand which contract components drive future cost increases?
• Do we know our true-up risk before SAP tells us?
• Can we model best case, expected case, and worst case for the next contract term?
• Do we have quarterly governance in place after signature?

If the answer to any of these questions is unclear, the company is not ready to sign. It may be ready to negotiate, but not to commit.

FinOps Turns RISE from a Contract into a Managed Financial Discipline

The biggest mistake in a RISE renewal is treating it as a procurement event. It is not.

It is a recurring financial governance model for one of the company’s most critical technology platforms.

The CFO’s role is to ensure that SAP costs remain explainable, controllable, and aligned with business value.

That requires more than a renewal proposal. It requires a reliable SAP FinOps baseline, continuous consumption measurement, financial risk reporting, and a clear view of how usage translates into contract value.

With visoryQ FinOps Manager, supported by samQ for usage-based SAP license optimization, organizations can move from reactive SAP contract management to proactive SAP cost governance. The goal is simple: know what you own, know what you use, know what it costs, and know what to change before the renewal is signed.