RISE TCO and ESG reporting alignment.

The RISE with SAP business case used to be a purely financial conversation. In 2026 it is also an ESG conversation. The Scope 2 emissions from the hyperscaler running the RISE workload are reportable inside the buyer disclosure framework, the regional grid mix that feeds the hyperscaler region is a material input, and the SAP supplied sustainability claims have to be reconciled against the buyer audit grade reporting. The TCO model that does not include the ESG line is a model that produces an answer the sustainability officer will reject. The TCO model that includes the ESG line on the same level of rigour as the financial line is a model that survives both the CFO review and the sustainability disclosure cycle. This article documents the framework for the alignment.

Scope 2 emissions inside a RISE deployment

The RISE workload runs on hyperscaler infrastructure. The hyperscaler infrastructure draws electricity from the regional grid. The electricity draw produces Scope 2 emissions inside the buyer disclosure framework, because the buyer is the end user of the electricity, regardless of whether the hyperscaler or SAP is the contracting party for the infrastructure. The emissions are calculated against the kilowatt hour draw multiplied by the regional grid emissions factor, with adjustments for any contractually procured renewable energy.

The kilowatt hour draw is a function of the workload size, the hyperscaler power usage effectiveness ratio, the regional climate, and the utilisation profile of the workload across the day. A typical SAP S/4HANA workload on a hyperscaler region in temperate Europe draws approximately ninety to one hundred twenty kilowatt hours per million transactions, with the spread driven by the PUE differences between the hyperscalers. The same workload in a warmer region draws between one hundred ten and one hundred fifty kilowatt hours per million transactions, with the spread driven by the cooling overhead.

The regional grid emissions factor is published by the national grid operator. In Sweden, the factor sits below twenty grams of CO2 equivalent per kilowatt hour, because the grid is dominated by hydroelectric and nuclear. In Germany, the factor sits between three hundred and four hundred grams of CO2 equivalent per kilowatt hour. In coal heavy regions, the factor exceeds five hundred grams of CO2 equivalent per kilowatt hour. The hyperscaler region choice changes the Scope 2 line in the buyer disclosure by an order of magnitude. The choice is material to the disclosure even when the choice is immaterial to the financial line.

The PUE differential between hyperscalers

The hyperscaler power usage effectiveness ratio captures the overhead of cooling, lighting, and ancillary equipment against the compute draw. A PUE of one means the entire electricity draw is consumed by compute. A PUE of one point five means the cooling and ancillary equipment consumes fifty percent of the electricity that the compute consumes. The PUE varies by hyperscaler, by region, by season, and by the age of the data centre facility.

The current best in class PUE across the three major hyperscalers sits between one point one zero and one point one five for the newest facilities in temperate regions with seawater or aquifer cooling available. The current worst case PUE in the same hyperscalers sits between one point four five and one point six five for the older facilities in warmer regions. The PUE differential between the best case and the worst case is a fifty percent swing in the total kilowatt hour draw for the same workload, which translates directly into a fifty percent swing in the Scope 2 emissions.

The TCO model has to capture the PUE for the specific region the workload will run in, not the hyperscaler average. The hyperscaler average is a marketing number. The regional PUE is the operational number. A buyer who is making the hyperscaler decision on the ESG basis needs the regional PUE for the candidate regions, with the seasonal variation captured separately. The seasonal variation runs between five and fifteen percent for most regions, with the higher variation in regions that rely on outside air cooling for the cooler months.

Renewable energy procurement claims and the audit grade test

The hyperscalers and SAP both publish sustainability claims that assert the underlying infrastructure runs on renewable energy at scale. The claims are typically made on an annual net basis, where the hyperscaler matches the annual kilowatt hour consumption against the annual renewable energy procurement. The matching is geographically and temporally averaged, which is an accounting construct rather than an operational reality. The workload runs on the grid that supplies the data centre in the moment, regardless of where and when the matching renewable procurement was contracted.

The audit grade test is whether the renewable claim is recognised inside the buyer disclosure framework. The major disclosure frameworks differ on this point. The GHG Protocol Scope 2 market based methodology recognises the matching renewable procurement, subject to the contractual instrument quality. The location based methodology does not, and reports the emissions against the regional grid factor regardless of the matching. Most large enterprises report on both methodologies, with the market based number for the headline disclosure and the location based number for the audit trail.

The TCO model that integrates with ESG reporting has to capture both numbers. The market based Scope 2 line uses the hyperscaler supplied renewable matching, with the contractual instrument quality documented in the audit trail. The location based Scope 2 line uses the regional grid factor for the specific hyperscaler region and the workload utilisation profile. The two numbers may differ by a factor of ten. The difference is material to the disclosure conversation, and the buyer side leads need both lines visible inside the model.

The hyperscaler region choice as a disclosure surface

The hyperscaler region choice inside a RISE deployment is typically presented as a latency and data residency decision. In ESG terms, it is also a Scope 2 decision. A region in the Nordic countries, with a grid dominated by hydroelectric, produces a Scope 2 line that is between five and fifteen times lower than the same workload in a region with a coal heavy grid. The latency and data residency drivers may select a different region. The ESG driver, viewed independently, would select the Nordic region in most cases.

The buyer side discipline is to capture the ESG driver as a documented criterion in the hyperscaler region decision, alongside latency, data residency, and cost. The criterion is weighted by the materiality of the workload to the overall Scope 2 line of the buyer enterprise. For a buyer with a heavy industrial Scope 1 emissions profile, the SAP workload Scope 2 may be immaterial, and the ESG driver may carry low weight. For a buyer with a services business and a low Scope 1 profile, the SAP workload Scope 2 may be the largest line in the disclosure, and the ESG driver may carry high weight.

The materiality assessment is done before the region decision is made, with the ESG team at the table. The output is a documented region preference, with the weighting against the other criteria, that the procurement team carries into the RISE negotiation. The SAP account team will accommodate the region preference if it is presented as a hard requirement with a documented basis. The account team will work against the region preference if it is presented as a soft preference without the basis.

Reporting alignment between the RISE TCO and the disclosure cycle

The disclosure cycle and the RISE TCO model have different time horizons. The disclosure cycle runs on an annual basis, with the financial year boundary as the closing date. The RISE TCO model runs on a seven year horizon, with the contract anniversary as the closing date. The reconciliation between the two requires the TCO model to break the annual ESG line out by financial year, with the workload sizing, the utilisation profile, the PUE, and the grid factor captured separately for each year.

The reconciliation also requires the disclosure framework alignment to be settled at the start of the contract, not at the end of the first reporting year. The framework choice between location based and market based is a strategic decision that travels across the contract term, and it has to be documented in the contract supporting paperwork rather than left to the post signature reporting cycle. A buyer who reports on market based methodology needs the contractual right to the hyperscaler supplied renewable energy attribution. A buyer who reports on location based methodology needs the contractual right to the regional grid data.

The contractual rights are negotiable inside the RISE contract. The standard SAP template does not include them. The buyer side counter is to add the rights as part of the ESG reporting schedule attached to the RISE contract, with the data formats, the reporting cadence, the audit trail obligations, and the attribution rights documented in the schedule. With the schedule in place, the disclosure cycle aligns with the operating reality of the contract, and the year on year reporting consistency that the audit team requires becomes deliverable.

The ESG line in the boardroom conversation

The board level conversation around RISE includes the ESG line in 2026 in a way that it did not in 2022. The audit committee asks for the Scope 2 line. The sustainability committee asks for the regional grid mix. The investor relations team asks for the disclosure framework. The board level pack that does not include the ESG line is a pack that gets sent back, and the negotiation that does not include the ESG criterion is a negotiation that closes on a contract that the disclosure cycle cannot support.

The discipline of the ESG alignment runs in parallel with the discipline of the financial TCO model. The same independent benchmarks, the same sensitivity bands, the same contract surface mapping, applied to the ESG line alongside the financial line. The two lines are integrated in the boardroom version of the model, with the seven year totals presented for both the cost and the emissions, with the hyperscaler region choice carrying the joint weighting, and with the disclosure framework alignment documented inside the RISE contract supporting paperwork.

Two lines in the model, one decision

The seven year RISE TCO model that closes the deal in 2026 is the model that carries two lines side by side. The financial line, sourced from independent benchmarks, sensitivity tested, and bound through the contract surfaces. The ESG line, sourced from the hyperscaler PUE and regional grid factor, sensitivity tested for the disclosure framework choice, and bound through the contractual data rights. The two lines together drive the hyperscaler region decision, the workload sizing decision, and the contract negotiation sequence.

Across the firm engagement base, the integration of the ESG line into the RISE TCO model has shifted the hyperscaler region decision in approximately one in three deals. The shift produces a Scope 2 emissions line that is between three and ten times lower than the default region, with a financial cost differential that is typically within five percent of the default. The integration is the discipline that allows the buyer side leads to defend the contract at the audit committee, the sustainability committee, and the investor relations review, all in the same boardroom cycle.