Public sector RISE negotiation. Additional protections.

Public sector RISE with SAP negotiations carry structural requirements that private sector deals do not. The buyer is spending public money, operating under procurement frameworks set by statute, and answering to oversight bodies that review contract terms with scrutiny that private boards rarely apply. The standard RISE order form, designed for commercial buyers, does not address several of these requirements without modification. The work in this article is to document the additional protections that public sector buyers should negotiate into a RISE contract, the reasons each protection matters, and the negotiation sequence that produces a contract the auditor general or equivalent oversight body will accept.

The protections that matter most for public sector

Six protections appear repeatedly in public sector RISE engagements. They appear because the underlying drivers, public accountability, statutory procurement frameworks, audit oversight, parliamentary scrutiny, data sovereignty requirements, and citizen service continuity obligations, exist in every public sector RISE conversation. Naming the six protections gives the negotiation team the agenda it needs to enter the SAP conversation.

The first protection is enhanced data sovereignty language. Public sector buyers operate under requirements that data remains within defined geographic boundaries, often a single country or a regional bloc, with specific commitments about the location of processing, storage, backups, and support access. The standard RISE language addresses data residency at a high level. Public sector requires the language to specify the named hyperscaler region, the named SAP data centre, the support access geography, and the backup location. Each commitment must appear with a contractual obligation, not as a best effort statement.

The second protection is the audit access right. Public sector oversight bodies, including auditors general, parliamentary committees, and sectoral regulators, retain the right to audit IT systems that process public information. The RISE contract must provide for that audit access, on reasonable notice, with defined scope, and without the contract carrying penalties for the buyer cooperating with the audit. The standard RISE order form rarely addresses audit access at this depth. The buyer adds the language.

The third protection is the data extraction commitment. Public sector buyers face citizen service continuity obligations that private sector buyers do not. A RISE exit must preserve the ability to continue delivering services to citizens during the transition. The contract must specify the data formats available for extraction, the timeline within which extraction must complete, the testing and validation support during the extraction, and the operational handover from RISE to the successor environment. Each commitment is named in the contract, not implied.

The fourth protection is the change control framework. Public sector procurement frameworks frequently require that contract changes follow defined approval processes that include external oversight. The RISE contract must accommodate these processes, with change requests handled through the buyer's framework rather than through SAP's standard change request mechanism. The contract names the process, names the timelines, and names the approval authorities.

The fifth protection is the price transparency commitment. Public sector buyers operate under transparency requirements that may include public disclosure of contract pricing, comparison to benchmark pricing, and reporting on contract changes. The RISE contract must permit the buyer to comply with these requirements without breaching confidentiality terms. The contract language confirms the disclosure rights explicitly.

The sixth protection is the conflict of interest framework. Public sector buyers must avoid contractual relationships that create conflicts with other public bodies or with regulatory functions. The RISE contract must include language confirming that the buyer can require SAP to disclose any potential conflicts, can require remediation of identified conflicts, and can terminate the contract if conflicts cannot be remediated. The protection is rarely present in the standard order form and almost always required by the public sector procurement framework.

How SAP responds to public sector requirements

SAP has experience with public sector contracts and carries internal mechanisms to accommodate public sector requirements. The standard SAP response to public sector requests is to acknowledge the request, propose a public sector adapted version of the contract, and accept many of the structural modifications without substantial resistance. The accommodation is not free. The public sector contract frequently arrives at a higher price point than a comparable private sector deal, reflecting the additional administrative and operational obligations SAP takes on.

The buyer assessment of the price premium is twofold. The first assessment is whether the premium is proportionate to the actual additional obligations. A premium of three to five percent for the documented additional protections is generally proportionate. A premium of ten percent or more usually reflects either an overestimate of the additional obligation or an SAP attempt to recover margin elsewhere in the contract. The second assessment is whether the additional protections are real or are window dressing. Public sector contracts sometimes arrive with extensive additional language that does not deliver substantive additional protection on close reading. The legal team scrutinises the language to confirm that each protection has operational substance.

The procurement framework requirements

Most public sector buyers operate under a procurement framework that specifies the process by which a contract of this size must be procured. The framework requirements vary by jurisdiction, by sector, and by contract value, but several patterns recur. The framework usually requires a competitive procurement process, with multiple suppliers invited to bid against a defined specification. The framework usually requires evaluation against documented criteria. The framework usually requires approval at a defined authority level. The framework usually requires public reporting of the contract award.

The RISE conversation must accommodate the framework requirements rather than substitute for them. Public sector buyers that engage SAP directly, without running the framework competition, frequently encounter procurement audit findings that delay or invalidate the contract. The discipline is to run the framework competition first, with RISE as one of the evaluated options, and to make the SAP selection decision through the framework rather than around it.

The framework competition does not require the buyer to disengage from SAP during the procurement period. The buyer can run the framework competition with SAP as the incumbent, with other suppliers as challengers, and with the analytical work the negotiation team has done feeding into the framework evaluation criteria. The framework outcome confirms the SAP selection on a defensible basis.

Working with the auditor general or equivalent oversight body

The auditor general, or the equivalent oversight body in the jurisdiction, will review the RISE contract either before signature or shortly after. The review covers the procurement process, the contract terms, the pricing benchmark, the data protection arrangements, and the exit provisions. The review can produce findings that require contract modification, that delay implementation, or that prompt additional public disclosure.

The disciplined buyer engages the oversight body early in the negotiation, not after signature. The early engagement allows the oversight body to identify concerns while the negotiation is open, which is easier to address than concerns raised after the contract is signed. The early engagement also signals to the SAP team that the contract will be reviewed by an external body, which often produces more flexibility on the structural protections than the standard private sector negotiation would.

The engagement format varies by jurisdiction. In some cases the oversight body provides a formal pre approval opinion. In other cases the engagement is informal, with the oversight body advising on the structural framework without committing to a final position. Either format adds value to the negotiation. The buyer that runs the negotiation in isolation from the oversight body, then presents the signed contract for review, accepts the risk of post signature findings that the early engagement would have avoided.

Pricing benchmarks for public sector RISE

Public sector pricing benchmarks for RISE sit close to private sector benchmarks for comparable size organisations, with the modest premium documented above for the additional protections. The discount available against SAP list pricing usually runs between thirty and fifty percent for public sector deals, which is consistent with the private sector envelope. The total contract value per Full User Equivalent runs within ten percent of the private sector equivalent.

The benchmarks matter because public sector buyers often face internal questions about whether the price they have negotiated is comparable to what the private sector achieves. The benchmark data answers the question, defends the contract against audit findings on pricing, and informs the renegotiation conversation at renewal. Public sector buyers should request benchmark data as part of the negotiation, either from independent advisors or from peer organisations through framework procurement channels.

One pattern that public sector buyers should watch is the bundled BTP allocation. The standard RISE bundle includes BTP credits sized against a private sector consumption pattern, which does not match the public sector profile. Public sector buyers typically consume BTP credits at lower volumes and against different use cases than the bundle assumes. Rebalancing the BTP allocation against actual consumption produces material savings without affecting the operational outcome.

Conclusion: public sector RISE is the same negotiation with more protections

Public sector RISE negotiations are the same negotiation as private sector RISE negotiations, with additional protections layered on top to accommodate the public accountability framework. The protections add structure to the contract, occasionally add a modest price premium, and protect the buyer organisation from the audit and oversight risks that come with spending public money. The buyer that approaches the negotiation as a standard RISE deal with public sector wrappers will produce a contract that meets the framework requirements. The buyer that approaches the negotiation as a fundamentally different exercise will overcomplicate the conversation and produce a contract that is harder to negotiate without delivering substantively more protection. The structure documented in this article reflects observed practice across public sector engagements at the firm.