The final pricing checklist. Twelve tests to run before signature.

By the time a RISE with SAP negotiation reaches the closing window, the buyer team has typically spent four to six months on the commercial position. The FUE inventory is documented, the discount stack has been requested, the term length has been debated, the indexation cap has been argued, and the recalibration clause has been drafted and redrafted. The instinct at this point is to push the deal across the line. Resist the instinct. The week before signature is the week to run the final tests against the position, because the cost of catching a missing protection or a soft commitment in week twenty four is a tenth of the cost of catching it in year three of the contract. This article presents the twelve tests we apply to every closing position. None is exotic. All are routinely missed.

Test one. The FUE inventory is reconciled to the order form.

The FUE count on the SAP order form should match the inventory the buyer team built and validated. The discrepancy is often a hundred FUE or more, sometimes due to legitimate roundings, more often due to user roles that SAP categorised as professional that the buyer inventory categorised as functional or productivity. The discrepancy translates directly into committed cost over seven years. A hundred FUE difference at fifteen hundred dollars per FUE per year is more than a million dollars over the term. The reconciliation must be line by line, with each disputed user named, the role examined, and the categorisation evidenced. The order form FUE total is then locked against the reconciled inventory and signed off by the buyer team before the order form moves to the procurement queue.

Test two. The discount stack is named, layered, and quantified.

The discount stack should appear on the commercial summary the SAP team provides, with each layer named and quantified. The volume discount, the term discount, the strategic discount, and the discretionary discount each have separate magnitudes and separate logic. A summary that shows a single blended discount percentage is incomplete and should be sent back for itemisation. The itemised stack lets the buyer test whether the strategic and discretionary layers carry the magnitude the negotiation produced. It also exposes any quiet erosion of the discount layers in the final paperwork, which happens more often than the SAP team likes to admit when the legal and procurement teams take over from the account team in the closing weeks.

Test three. The term length matches the strategic position.

The term length on the order form should match the term length the buyer decided to commit to, not the term length the SAP account team prefers. A buyer who decided to commit to five years should not be looking at a seven year order form with a footnote that the seven year term was applied to deliver the agreed discount. The discount and the term are negotiated together but documented separately. The term lock is a separate decision from the discount lock, and the buyer should treat any drift between the two as a structural defect that requires correction before signature, not after.

Test four. The indexation cap is in the order form, not in a side letter.

The indexation cap, typically two to three percent per year, must appear in the order form itself. A side letter or an email confirmation is not equivalent. Side letters are sometimes lost in the SAP commercial systems, sometimes contested at the renewal cycle, sometimes overridden by later contractual amendments that the buyer signs without recognising the override. The cap should be drafted into the relevant pricing schedule of the order form, with the index named, the trigger defined, and the application scope limited to the layers the buyer agreed to. An uncapped indexation against the full bundle compounds quickly. A capped indexation against the application layer alone, with the infrastructure and managed services layers indexed separately on different rules, is a materially better outcome.

Test five. The volume commitments are sized against the documented growth.

Every volume commitment in the order form should map back to a documented growth scenario in the buyer planning materials. The FUE commitment maps to the workforce plan. The HANA storage commitment maps to the data growth model. The BTP credit commitment maps to the integration and extension roadmap. Where a commitment exceeds the documented growth, the gap is the buyer exposure. The exposure should be examined explicitly. A small gap is acceptable when the recalibration mechanism is robust. A large gap is unacceptable regardless of the recalibration mechanism, because the recalibration is bilateral and the SAP team rarely consents to the magnitude of downward adjustment the buyer would need to recover.

Test six. The recalibration clause is present, bilateral, and dated.

The recalibration mechanism should be present in the contract, bilateral in direction, dated to specific year three and year five measurement points, and tied to actual measured consumption rather than to SAP discretion. The drafting should specify the adjustment threshold, typically ten percent, above which the contracted volume adjusts. The drafting should also specify the methodology for the measurement and the dispute resolution path when the parties disagree on the measurement. A vague recalibration clause that requires SAP agreement to be triggered is structurally worse than no clause at all, because it creates the illusion of protection without the substance. The closing test is to read the clause aloud and confirm that a CFO reading it in year three would conclude that the adjustment is automatic, not negotiable.

The cost of catching a missing protection in week twenty four is a tenth of the cost of catching it in year three.

Test seven. The BTP entitlement is sized and itemised.

The BTP entitlement in the order form should be itemised by service, not bundled as a single capacity unit allocation. The integration suite entitlement, the extension suite entitlement, the analytics entitlement, and the process automation entitlement each have separate consumption profiles and separate overage rates. A bundled entitlement obscures the consumption pattern and creates surprise invoices when one component runs hot while others sit idle. The itemised entitlement also gives the buyer the option to negotiate the overage rate separately for each service, which is significantly more achievable than negotiating a single blended overage rate across the bundle.

Test eight. The infrastructure mark up is explicit, not implicit.

The hyperscaler infrastructure layer carries an SAP mark up that varies from fifteen to thirty five percent against the underlying hyperscaler list price. The mark up is rarely visible on the order form because the infrastructure cost is presented as bundled. The buyer should require the SAP team to disclose the infrastructure mark up in writing, either in the commercial summary or in a closing memorandum. The disclosure does not necessarily change the bundled price the buyer pays, but it establishes the baseline for the year three optimisation conversation, the renewal cycle, and any exit scenario that the buyer might face in years six and seven.

Test nine. The currency and FX exposure is examined and accepted.

The contract is denominated in a primary currency. If the buyer operates across multiple jurisdictions, the currency choice creates FX exposure on the home currency invoices that are funded against the contracted obligation. The exposure should be quantified in the closing memorandum, with a scenario showing the bundled cost in home currency at the spot rate, at a ten percent FX move in each direction, and at a twenty percent FX move. The exposure is not always negotiable, but it should be accepted with eyes open rather than discovered in year two when the home currency drifts.

Test ten. The discretionary discount is not contingent on side conditions.

The discretionary discount in the stack is sometimes presented with side conditions that are not documented as conditions, such as reference participation, executive engagement at SAP events, or favourable case study language. The conditions are typically presented verbally by the account team and rarely appear in the contract. The buyer position should be that the discount applies regardless of subsequent buyer behaviour and is not subject to clawback if a side condition is not delivered. The position should be confirmed in writing in the closing memorandum.

Test eleven. The expansion pricing is locked.

Expansion pricing is the unit rate that applies when the buyer adds FUE, storage, BTP credit, or other entitlement above the contracted volume during the term. SAP standard expansion pricing typically reverts to a higher rate than the contracted unit rate, sometimes by twenty to forty percent. The buyer position should be that expansion pricing follows the contracted unit rate, with a defined ceiling on any uplift. The position should be drafted into the order form as a separate clause, dated to the contract term, and quantified explicitly.

Test twelve. The exit provisions are present and operational.

Exit provisions cover the data portability obligation, the assistance obligation, the duration of the assistance, the pricing of the assistance, the documentation obligation, and the transition window. The provisions should be readable, dated, and operational. The closing test is to ask whether the buyer team could execute the exit using the contract language alone in the event of a dispute that prevented cooperative behaviour from the SAP team. If the answer is no, the provisions are decorative rather than operational, and the buyer should require additional language before signature.

Conclusion.

The twelve tests above sit at the end of the negotiation, not the beginning. They are designed to catch the structural defects that creep into a deal in the closing weeks, when fatigue, momentum, and the executive desire to close the procurement cycle combine to push the buyer team toward signature. Each test takes an hour or less to run. The investment is trivial compared with the cost of finding a missing protection in year three. The discipline of running the checklist also has a secondary benefit. It signals to the SAP commercial team that the buyer is engaged at depth, paying attention to construction, and unwilling to accept softening of the position in the closing window. The signal alone has commercial value. The actual catches the checklist produces are the additional return on the discipline.