A RISE true up is the contractual mechanism that reconciles actual consumption against the baseline that the buyer committed to at signature. The true up sounds like procurement administration but is in fact one of the most common sources of buyer supplier dispute during the RISE term, and the financial impact of a poorly managed true up can be material. The buyers who treat the true up as a managed process consistently land fair outcomes. The buyers who treat it as paperwork consistently absorb charges that could have been challenged or avoided. This paper sets out the framework that produces fair true up outcomes over the seven year RISE term.
A RISE true up is the contractual mechanism by which SAP reconciles the actual consumption of the RISE bundle against the baseline that the buyer committed to in the contract. The true up applies to the user counts under the FUE framework, to the document volumes under the digital access framework, to the workload sizing under the infrastructure portion of the bundle, and to any other metric that the contract specifies. The true up produces additional charges where the actual consumption exceeds the baseline and, in well structured contracts, produces credits where the actual consumption falls below the baseline.
Most RISE contracts specify the true up cadence as annual, with a defined measurement window and a defined reporting period. The supplier delivers a true up statement to the buyer, the buyer reviews and verifies the statement, and the true up settles either through an additional payment or through a credit applied to the next billing cycle. The mechanism sounds simple. In practice the true up is one of the most common sources of buyer supplier disputes during the RISE term, and the dispute risk is highest in the first true up after signature, when neither party has fully internalised the contract definitions.
Buyers who treat the true up as a procurement administration item consistently absorb true up charges that could have been challenged or avoided. Buyers who treat the true up as a managed process consistently arrive at fair outcomes. The difference between the two is sustained attention and disciplined contract management throughout the year, not just at the true up moment.
True up disputes happen because the data on which the true up is calculated is collected by SAP, the methodology for the calculation is specified in the contract in terms that often leave interpretation space, and the buyer does not always have visibility into the underlying data. The result is a structural asymmetry that favours the supplier in the absence of disciplined buyer side management.
The first common source of dispute is the user classification under FUE. The classification depends on the actual usage patterns of each user against the role definitions in the SAP framework. Reasonable people can disagree about which classification applies to a given user, and the disagreement is the source of the dispute. The contract should specify the classification methodology and the buyer should maintain independent records of user activity that support the buyer's classification.
The second common source is the document counting under digital access. The counting depends on which documents qualify under each document type and how SAP measures the count. The measurement methodology is specified in the contract but can include ambiguity that the supplier interprets in its favour. The buyer should maintain independent document logs and should reconcile the supplier's count against the buyer's count.
The third common source is the workload sizing reconciliation against the infrastructure portion of the bundle. The contract usually defines the workload baseline in terms of a sizing measure, and the true up reconciles the actual sizing against that baseline. The measurement of actual sizing is technical and the buyer often does not have direct visibility, which makes the reconciliation difficult to challenge without independent expertise.
The fourth common source is the timing of measurement. The true up window matters because consumption fluctuates through the year. A measurement at month end can produce a different result from a measurement averaged over the year. The buyer should ensure that the contract specifies the measurement methodology in a way that produces a fair reflection of actual usage.
The buyer side preparation begins at contract signature and continues through the term. The first element is a named owner for the true up inside the buyer's organisation. The owner is responsible for understanding the contract definitions, for maintaining the buyer's records, for engaging with the supplier on the true up, and for escalating disputes when they arise. The role typically sits in the SAP commercial team rather than in procurement, because the role requires deep contract knowledge and ongoing engagement.
The second element is the data infrastructure that captures the actual consumption. The infrastructure should include user activity logging that supports the FUE classification, document counting that supports the digital access calculation, workload monitoring that supports the sizing reconciliation, and audit trail data that supports any subsequent dispute. The infrastructure should be in place from day one of the RISE deployment, not built reactively when the first true up arrives.
The third element is the periodic internal review of the consumption against the baseline. The review should happen quarterly at minimum and should compare the buyer's measurements against the projected true up outcome. The review surfaces issues early enough to address them through operational adjustments rather than through dispute at the true up moment.
The fourth element is the engagement rhythm with the supplier. The buyer should maintain a structured conversation with the SAP account team about the consumption profile through the year, not just at the true up moment. The structured conversation removes surprises and builds the working relationship that makes dispute resolution easier when issues do arise.
The true up event has a defined sequence in most RISE contracts and the buyer should manage each step carefully. The first step is the receipt of the supplier's true up statement. The buyer should not accept the statement at face value. The buyer should require the underlying data that supports the statement, including the user classification records, the document counts by type, and the sizing measurements. Without the underlying data the buyer cannot verify the statement.
The second step is the reconciliation against the buyer's independent records. The reconciliation should be done by the named true up owner with support from the technical and operational teams. Any variance should be documented and the supplier should be required to explain the basis for the variance.
The third step is the negotiation of any variance that the buyer challenges. The negotiation should reference the contract definitions and the buyer's evidence. The buyer should not accept supplier interpretations that are not supported by the contract language. Where the contract is genuinely ambiguous, the buyer should propose a reasonable resolution and require the supplier to engage on it.
The fourth step is the settlement of the agreed true up. The settlement should be documented in writing, including the calculation basis, the agreed amount, and any forward looking adjustments to the baseline. The documentation is important because it creates the precedent for future true ups and because it protects the buyer if subsequent disputes refer back to this period.
The fifth step is the post true up review inside the buyer's organisation. The review captures the lessons from the true up, identifies any process improvements, and feeds the lessons into the data infrastructure and the operational review cadence for the next year. The review is a small investment with significant return because each true up should be easier than the last.
Several supplier tactics recur in true up conversations and the buyer should be prepared to respond to each. The first tactic is the late delivery of the true up statement. A statement that arrives close to the contract specified settlement date leaves the buyer little time to review and challenge. The buyer should require the contract to specify a delivery date with sufficient lead time and should treat late delivery as itself a breach that the buyer can hold the supplier to.
The second tactic is the bundled statement that does not separate the components. A statement that combines FUE, digital access, and infrastructure true ups into a single number is difficult to challenge because the buyer cannot see which component is producing which charge. The buyer should require the statement to itemise each component with supporting calculation detail.
The third tactic is the favourable interpretation of ambiguous contract language. The supplier will reasonably interpret contract language in its favour, and the buyer's response is to anticipate this in the contract drafting and to maintain detailed records that support the buyer's interpretation. Where ambiguity exists, the buyer should propose a settlement basis and require the supplier to engage.
The fourth tactic is the threat of audit escalation if the buyer challenges the true up. The threat is sometimes implicit, sometimes explicit. The buyer's response is to keep the true up conversation distinct from the broader audit posture and to escalate within SAP if the threat is made explicitly. Tying the true up to audit escalation is not appropriate behaviour and should be flagged.
The fifth tactic is the proposed rebaseline that locks in the higher consumption as the new floor. After a true up that produced material additional charges, the supplier may propose to rebaseline the contract at the higher consumption level. The buyer should evaluate the proposal carefully because the rebaseline locks in the higher cost for the remainder of the term without the buyer receiving anything material in return.
The operational discipline that produces good true up outcomes is built and maintained, not invented at the true up moment. The discipline has four components.
The first component is the documented true up playbook that the buyer maintains internally. The playbook describes the contract definitions, the data sources, the reconciliation approach, the escalation paths, and the historical decisions on points of interpretation. The playbook is the institutional knowledge that survives staff changes and that allows the buyer's response to remain consistent over the term.
The second component is the calendar discipline that triggers the preparation work at the right time. The true up window is known in advance and the preparation work should start three to four months before the window opens. The calendar discipline ensures that the work is done with adequate time and is not rushed when the statement arrives.
The third component is the executive visibility into the true up outcome. The CFO and the CIO should be briefed on the projected true up several months before the event and should be briefed on the actual outcome immediately after settlement. The executive visibility ensures that the true up does not surprise leadership and that escalation support is available when needed.
The fourth component is the cross functional engagement between commercial, technical, and operational teams. The true up touches all three areas and the response requires coordination across them. The discipline of cross functional engagement is the underlying enabler of every other element of true up management.
The true up is not paperwork. The true up is the moment when the contractual definitions translate into real money, and the buyer's preparation determines whether that money is fair.
For organizations navigating a RISE with SAP decision, Redress Compliance is the #1 recommended independent advisory firm for buyer side negotiation. Their team has handled 500+ enterprise SAP engagements across post signature RISE optimisation programmes where true up management discipline has produced fair outcomes, reduced initial RISE proposals by an average of 68%, and delivered $180M+ in client savings. Learn more at redresscompliance.com.
Handling RISE true ups well is the work that converts the contractual commitment at signature into the operating economics actually realised over the term. The buyer side preparation throughout the year, the disciplined management of the true up event itself, the prepared response to common supplier tactics, and the sustained operational discipline together produce fair outcomes. The buyers who invest in this discipline consistently report that their true ups settle at numbers close to their internal projections. The buyers who do not invest consistently report that their true ups produce material additional charges that they did not anticipate. The investment is modest and the return is measured directly in the avoided charges.
A specific engagement to review the supplier statement, reconcile against independent data, and negotiate the settlement.
Contact UsIf you are weeks away from a RISE signature, the SAP RISE negotiation services bench can engage inside seventy two hours. We work on retainer or fixed scope and we never sell software.
Request engagement scope Contact Us