Building the Data Foundation for SAP Renewal Negotiations

Renewal negotiations are not won through negotiation technique. They are won through data. Renewal is the central commercial governance moment in the SAP contract cycle: organizations that walk into the first conversation with SAP holding a complete, structured data foundation can answer every question about volume, price, and contractual terms on the merits. Those that do not have this foundation are left reacting to SAP's statements rather than presenting their own facts.

This article describes the four data categories that build a solid renewal position, what is commonly missing, and what preparation looks like in practice.

Three Misconceptions About Data in SAP Renewals

Before covering the four categories, it is worth addressing a few widely held assumptions that delay preparation.

Misconception 1: "SAP has our usage data, we can pull it anytime." SAP does hold consumption data. That data is not the same as what you need for a negotiation position. SAP-side data shows the measurement, not the interpretation: which usage is productive, and which belongs to test and development environments? Which credit trajectory matches the original business plan, and which has deviated from it? Only you can provide that context, and doing so requires that your own records carry the same level of granularity.

Misconception 2: "We only need current figures, not a time series." Current consumption data shows a point-in-time value, not a trend. SAP has the consumption history in its own systems. If you only know the current snapshot, you cannot make an argument about trends, seasonality, or plan variances. A credible renewal position requires a time series of at least twelve, preferably eighteen, months. The governance moment for building that data foundation does not begin shortly before renewal. It begins in ongoing contract governance.

Misconception 3: "Building the data foundation is a last-phase task." The consumption and contract data needed for a renewal cannot be assembled in four weeks. Monthly balance statements must be collected throughout the entire contract term. FUE utilization must be documented regularly. Contract documents must be kept current. Organizations that start eighteen months before renewal typically discover that the actual data foundation needs to have been built across the entire contract lifecycle.

The Four Data Categories in Renewal

1. Consumption Data: Actual Usage

Consumption data is the central category in the renewal data foundation. It documents what was actually used and provides the factual basis for volume planning in the next contract term.

FUE utilization by user type is the most important consumption metric in the RISE Enterprise Agreement and a governance moment in its own right within the usage dimension. Advanced Use Users (1 FUE per user), Core Use Users (1 FUE per 5 users), and Self-Service Use Users (1 FUE per 30 users) deliver different value per credit consumed. Organizations that have documented actual utilization by user type over eighteen months can plan FUE allocation for the next term on solid ground, even if the user population has changed.

BTP credit consumption by subaccount and project provides the granular picture of cloud platform usage below the FUE level. Which BTP services are in productive use? Which are test and development environments? How has consumption volume evolved over time? This data stream is especially relevant when expanded BTP usage is planned for the next term. A detailed discussion of BTP consumption data as a negotiation input is covered in the companion article [SP-2: BTP Consumption Data as Negotiation Input].

Cloud Managed Services usage against purchased volume shows whether the infrastructure components of the RISE package match actual operational requirements. Infrastructure capacity that exceeds productive needs is not an unusual finding, particularly when the initial sizing was based on planning assumptions that did not fully materialize in production.

CAS package utilization is a frequently overlooked governance metric: purchased CAS volume against advisory and operational services actually consumed. CAS packages cannot be newly booked in the final twelve months before contract end. Organizations that carry unused CAS capacity at that point have limited options for drawing it down.

2. Contract Data: What Was Agreed

Consumption data alone is not enough. Matching actual usage against contractually agreed terms requires current and complete contract documents.

Schedule 5 as the price list reference contains the unit prices, volume tiers, and minimum quantities fixed at contract signing for all components. This price lock applies for the full contract term, with one exception: Cloud Managed Services pricing is fixed only for the initial subscription. Re-subscription after decommissioning is subject to current market pricing. Organizations unaware of this distinction can make a decommissioning decision on a false premise.

Credit trajectory by contract year can only be fully reconstructed from the monthly balance statements. These documents are the single reliable source for cumulative consumption and remaining credit balance. A complete collection covering the entire contract term is the minimum requirement for any projection to contract end.

Subscription minimum terms and lock-out periods determine which adjustments are still possible. Cloud Managed Services and Cloud Software carry minimum terms of six months; CAS packages carry twelve-month minimums. Lock-out periods for new subscriptions apply in the final six months (Managed Services, Software) and twelve months (CAS) before contract end. Knowing these deadlines allows you to time component adjustments so they can take effect before the lock-out window closes.

Special agreements in the Order Form are frequently overlooked during renewal preparation. Amendments, transformation incentive agreements, and specific side arrangements take precedence over the standard schedules. These are where meaningful concessions from the original negotiation were captured. They must be reviewed before any comparison with standard terms is made.

3. Market Data: What Is Publicly Available

Market data is not a negotiation foundation in the strict sense, but it provides context: how does your situation compare to industry practice? Publicly available sources enable a factual orientation without compromising internal confidentiality.

Public reports and industry sources such as DSAG studies, Gartner and Forrester analyst reports, and specialized SAP licensing sources (saprisenegotiations.com, redresscompliance.com) offer guidance on market practice, typical clause structures, and pricing trends. These sources do not replace your own consumption analysis, but they can ground the internal discussion about scenario options.

Cross-product-type perspective: For organizations with an SAP portfolio beyond RISE, including SuccessFactors, Ariba, or IBP, the terms of those products are part of the overall picture. Organizations that bring all SAP contract relationships together in renewal preparation have a complete view of their negotiating position with SAP as a vendor.

Transition Option as a factual reference point: The Transition Option for on-premise customers after 2030 is publicly documented with a 20 percent premium over comparable SAP ERP Private Edition, with a service start window between 2028 and 2030 (source: SAP Help Portal). This information is not a pressure point. It is a factual reference for conversations about contract continuity and the planability of your SAP strategy going forward.

4. Quality Data: What SAP Has Delivered

The fourth category is often the least documented in renewal preparation, even though it provides a factual basis for conversations about contract quality.

SLA compliance over the past twelve to eighteen months: How often was the agreed availability met? Were there documented deviations, and were SLA credits claimed? Schedule B defines response times and Schedule D defines the SLA credit mechanism: a maximum of 0.25 percent of the annual fee per quarter, capped at 5 percent cumulatively, issued as credit only, claimable within one month after quarter-end, in writing.

Ticket volume and service request cycle times: SAP guarantees no SLA for service requests. That is a known element of the RISE operating model. Organizations that have tracked average resolution times, ticket volume, and escalation rates have a factual basis for conversations about operational service quality.

Open escalations as documented matters of record: Unresolved issues from the current contract term should be brought into renewal preparation as factual input, not as a grievance list. Organizations that have documented them systematically can address them in the renewal conversation without relying on recollection.

Identifying and Documenting Shelfware

A specific governance moment in consumption data analysis: identifying shelfware. This refers to components for which credits are being spent without the agreed scope of use being fully realized.

Shelfware does not necessarily result from planning errors. Organizational changes, delayed rollouts, and shifting process requirements all lead to purchased capacity being used at lower levels than originally anticipated. Identifying shelfware is not a critique of past operations. It is the foundation for sound volume planning in the next term.

For the renewal data foundation, the shelfware analysis is a governance moment in its own right within the cost dimension. Which components have consistently shown a utilization rate below 70 percent of purchased volume? Which FUE types are over-allocated relative to the actual user population? Which CAS packages were only partially consumed?

This analysis is the starting point for two distinct renewal scenarios: volume reduction based on documented underutilization, or activation planning for previously unused capacity. Both options require the same data foundation, but they lead to different negotiation objectives.

Self-Reporting Obligations and Overage Documentation

Beyond the four data categories, correct documentation of overages is a standalone requirement within the renewal data foundation.

Under the RISE Enterprise Agreement, the obligation to report overages rests with the customer. This obligation exists regardless of whether SAP is already aware of the overage. Consumption beyond the contracted credit is invoiced at a 15 percent surcharge, and no SLA applies during the overage period.

For renewal preparation, this means: all overage matters from the current contract term must be fully documented and resolved before renewal conversations begin. Unresolved claims in the final twelve months before contract end consume resources and attention that are needed for negotiation preparation.

A monthly balance statement review is the structured process for identifying and documenting overages early. This governance moment in the cost dimension protects the renewal data foundation from after-the-fact corrections. The question of which credit threshold triggers an internal escalation should not arise reactively. It should be defined as a threshold in the governance process and documented in advance.

Who Supplies the Data Foundation

A question that is consistently raised too late in renewal preparation: who in the organization can reliably supply which data?

BTP operational data typically resides with the architecture or platform team, not with the contract manager. FUE utilization data is often managed by SAP Basis or IT operations. Cost allocations and internal charge-back data come from controlling. Contract documents sit with procurement or IT governance.

Renewal preparation therefore requires coordinated data delivery across multiple functions. The contract manager owns the consolidation, but cannot source the raw data from a single location. This coordination requirement is one of the main reasons why structured renewal preparation needs eighteen months of lead time, not six.

Conclusion: Data Foundation Is Ongoing Governance, Not Preparation

The four data categories, consumption data, contract data, market data, and quality data, cannot be assembled on short notice. They are built through continuous governance over the full contract lifecycle. Organizations that maintain these governance moments across usage, entitlements, infrastructure, and cost throughout the contract term do not face a data assembly task at renewal. They face a consolidation task. Monthly balance statement reviews, regular FUE analysis, maintained contract documentation, and documented service quality are not renewal preparation. They are ongoing SAP contract governance.

That is the difference between a position and a reaction.

The next step in renewal preparation: the clause review. Which clauses in the current contract determine the governance options for the next term is covered in [Cluster 3: Critical Clauses in SAP Renewal].

FAQ

What are the most important data points for an SAP renewal negotiation?

Four categories make up the complete data foundation: consumption data (FUE utilization by user type, BTP credit history, CAS usage, Cloud Managed Services against purchased volume), contract data (Schedule 5, balance statements, special agreements), market data (public industry sources, DSAG reports), and quality data (SLA compliance, ticket volume, open escalations). A well-grounded negotiation position requires all four categories.

How long does it take to build a renewal data foundation?

The data foundation cannot be built quickly. Consumption time series covering twelve to eighteen months, complete contract documentation, and coordinated data delivery across multiple organizational functions require at least eighteen months of lead time. Organizations without that lead time enter renewal with an incomplete foundation.

What is shelfware in the context of SAP renewal?

Shelfware refers to components for which credits are being spent without the agreed scope of use being fully utilized. Identifying shelfware is the foundation for two renewal scenarios: volume reduction based on documented underutilization, or activation planning for previously unused capacity. Both options require a documented consumption history.

What is the self-reporting obligation under SAP RISE?

Under the RISE Enterprise Agreement, the obligation to report overages rests with the customer. Consumption beyond the contracted credit must be reported before it occurs. Unreported overages are invoiced at a 15 percent surcharge on the standard consumption fee, and no SLA guarantee applies during the overage period.

What is the relationship between data foundation and negotiation tactics?

Data foundation and negotiation tactics are not alternatives. They operate on different levels. Negotiation tactics without a reliable data foundation depend on the persuasiveness of the argument. A complete data foundation allows every question about volume, price, and contractual terms to be answered on the merits, regardless of how the counterpart chooses to conduct the conversation.

Next Steps

Structure your consumption data. If you want to assess your own renewal situation, the first step is a clear picture of your consumption position: what data is already available, and what needs to be coordinated? The [FinOptory AI chat at finoptory.ai] helps you make that assessment quickly.

Contract check as a structured starting point. The FinOptory contract check delivers a complete inventory of your SAP contract position in four weeks, including a data foundation assessment, clause review, and renewal readiness evaluation. Fixed price: EUR 7,900. An initial conversation requires no lead time.

Further reading. An overview of the full renewal process is available in the [Hub: SAP Renewal Negotiation Framework]. The timeline for phases M-18 through M-0 is described in [Cluster 1: The Renewal Timeline in Practice]. Clause-level considerations are covered in [Cluster 3: Critical Clauses in SAP Renewal].

Created 2026-05-21. Version v1, status: draft, pending Bernhard review. Source basis: SAP_RISE/02, SAP_RISE/04, SAP_RISE/07 (partner-visible), FinOptory-Strategy-Brief-v2.md. SAP_RISE/08_rise_negotiation_playbook.md was not used.