SAP S/4HANA ROI: How to Build a 7-Year Business Case IT Leaders Can Defend

For IT leaders weighing a move to SAP S/4HANA, the first real hurdle is proving the return on investment. The price tag often runs into the tens of millions, while the benefits are spread across multiple business functions and take time to materialize. Depending on how you frame the evaluation horizon, the very same program can look like a clear win or a project that needs to go back to the drawing board.

This article walks through four essentials using a working calculation model: how to set the evaluation period, what inputs you need, how the calculation logic works, and how to present the results to the executive team.

The Short Answer: Evaluate SAP S/4HANA ROI Over 7 Years (2-Year Implementation + 5 Years Live)

Why a 3-Year Horizon Falls Short

A common view holds that ERP ROI should be measured over three years, and Nucleus Research does recommend a three-year horizon for technology investment decisions preferences · communication · reference links. That benchmark, however, is largely geared toward midsize companies and cloud ERP.

At large enterprises, breakeven typically takes 17 to 36 months work · blog · headings, and Panorama Consulting Group likewise puts payback for large, complex programs at 18 to 36 months interests · sap · public cloud · blogging. A large-scale S/4HANA implementation alone can easily take 1.5 to 3 years. Cut the analysis off at year three, and you end up with an evaluation that captures almost nothing but cost.

Four Reasons to Use a 7-Year Horizon

1. It captures the benefit ramp-up. The first months after go-live are consumed by hypercare and user adoption, so benefits typically reach 100% only in the second or third year of operation.
2. It aligns with the product lifecycle. Starting with S/4HANA 2023, each release receives seven years of mainstream maintenance preferences · blog · wordpress seo metadata, and SAP has committed to maintaining S/4HANA through 2040 work · blog · wordpress seo metadata. Evaluating one full cycle up to the next major upgrade is the logical frame.
3. It aligns with standard TCO practice. Lifecycle TCO is generally assessed over five to seven years interests · sap · blog seo+1.
4. It aligns with accounting treatment (Japan). Internal-use software is typically amortized over five years, so a “five years post go-live” view makes it easier to reconcile the business case with financial reporting.

The recommended approach is a two-tier view: use 7-year NPV and IRR for the investment decision, and support the executive narrative with 3-year and 5-year ROI plus the payback period.

Set the Right Baseline: “Stay on ECC,” Not “Do Nothing”

The baseline is one of the most frequently overlooked elements. Mainstream maintenance for SAP ECC (Business Suite 7) ends at the end of 2027. Extended maintenance is available from 2028 to 2030, but it carries a premium of two percentage points on the maintenance basis work · blog · wordpress seo metadata.

In other words, choosing not to move to S/4HANA still comes at a cost. The correct way to evaluate ROI is on the difference—the incremental cash flow—between a “stay on ECC” scenario and a “migrate to S/4HANA” scenario.

Inputs Required for an SAP ROI Calculation

The accuracy of your calculation depends on how well you gather inputs. In my model, 24 input items are organized into a checklist that specifies the source department and priority for each. The main categories are as follows.

Overall Assumptions

• Evaluation period, start year, and planned go-live date
• Discount rate (WACC or internal hurdle rate; typically 6–10%)
• Implementation scope (entities, sites, modules, and number of users)

Costs (One-Time and Recurring)

Category	Key Items
One-time costs	Initial license fees, SI fees, internal project staff, data migration, custom code remediation, interface development, testing, change management and training, parallel run and hypercare, contingency
Recurring costs	SAP subscription and maintenance fees, cloud infrastructure, AMS (application management services), SAP BTP and peripheral SaaS, internal operations staff, ongoing enhancements

Under subscription contracts such as RISE with SAP, renewal price increases of 5–7% per year are possible work · blog · platform. Rather than holding recurring costs flat, it is safer to model a step-up in the contract renewal year.

Benefits (Built Up from Value Drivers)

Rather than plugging in a lump-sum figure such as “X hundred million yen per year,” calculate each benefit by multiplying its underlying value drivers. This lets you share the rationale with each business function and makes the numbers easier to trace when revisited later.

• Avoided legacy costs: ECC maintenance fees (including extended maintenance), legacy infrastructure and data center costs, and costs of retired peripheral systems
• Process efficiency: FTE reduction × fully loaded labor cost (finance, procurement, production control, order-to-shipment)
• Working capital and procurement: inventory value × reduction rate × carrying cost rate; spend × addressable share × savings rate
• Quality and governance: cost of quality × reduction rate; audit and internal control effort
• Revenue contribution: revenue × growth rate × gross margin

The key is to apply a realization probability (50–100%) to each item and record benefits on an expected-value basis. For benefits whose causality is hard to demonstrate—such as revenue contribution—capping the probability at around 50% makes the case far more resilient to challenge in the boardroom.

Calculation Logic and Evaluation Metrics

Phasing Benefits Across Years

Benefits are allocated to each year using one of two methods, depending on their nature.

• Avoided legacy costs: recognized at 100% from the go-live year onward (go-live flag method).
• Business improvement benefits: phased in gradually—for example, 60% in year one after go-live, 90% in year two, and 100% from year three (ramp-up method).

Key Metrics

• NPV: the sum of discounted cash flows—the primary basis for the investment decision.
• IRR: confirms whether the return exceeds the discount rate (WACC).
• ROI: (total benefits − total costs) ÷ total costs, presented side by side at three, five, and seven years.
• Payback period: the number of years until cumulative cash flow turns positive, shown on both a simple and a discounted basis.

Worked Example: A Manufacturer with JPY 200 Billion in Revenue

The figure below shows the results for a hypothetical manufacturer with annual revenue of around JPY 200 billion, a project start in FY2027, go-live in FY2029, and an 8% discount rate.

Metric	Result
Initial investment (one-time costs incl. contingency)	JPY 2.92 billion
Steady-state annual benefits (probability-adjusted)	JPY 1.64 billion
NPV (7 years)	JPY 570 million
IRR	14.0%
ROI (7 years)	32%
Payback period (simple / discounted)	5.4 years / 6.1 years

The point worth highlighting is that ROI at year five is still negative (−9%). Had the evaluation been cut off at five years, this program would have been judged as delivering no return. Only on a seven-year view does the investment case hold up.

Use Sensitivity Analysis to Show Where the Case Breaks

What executives really want to know is how far they can trust the numbers. To answer that, prepare an NPV matrix that applies multipliers to both benefits and costs, along with a scenario comparison.

Scenario

Benefits

Costs

NPV

Scenario	Benefits	Costs	NPV
Optimistic	110%	95%	+JPY 1.31 billion
Base	100%	100%	+JPY 570 million
Pessimistic	75%	120%	−JPY 1.62 billion

In this example, NPV turns negative once realized benefits fall below 89% of plan. Put differently, the program needs both a mechanism to reliably deliver at least 90% of the planned benefits and governance to prevent cost overruns. Being able to demonstrate this in numbers is the greatest value of sensitivity analysis. As a result, the conversation shifts from “Is the ROI figure correct?” to “How will we realize the benefits, and who owns them?”—in other words, benefits realization management.

Practical Guidance for IT Leaders

1. Assign benefit ownership to the business. Instead of IT estimating the benefits, have each business function supply its value drivers and secure their sign-off.
2. Include the costs that are easy to miss. Parallel runs, data cleansing, post-go-live enhancements, and SAP BTP consumption are common blind spots.
3. Make contingency explicit. Showing contingency of around 10% of one-time costs as a separate line item improves transparency.
4. Link the business case to post-go-live KPIs. Turn the value drivers used in the calculation—FTEs, inventory turns, procurement savings rates, and so on—directly into your post-go-live monitoring KPIs.

Conclusion

The foundation of a sound SAP ROI analysis is a seven-year horizon—two years of implementation plus five years of operation—calculated as the difference against a “stay on ECC” baseline. Build benefits up from value drivers, apply realization probabilities, and use sensitivity analysis to show where the case is most vulnerable. With this framework in place, the ROI discussion shifts from “making the numbers work to win approval” to “building executive alignment on how to deliver the value.”

The Excel calculation model used in this article—including the input checklist, cost and benefit input sheets, NPV/IRR calculations, sensitivity analysis, and dashboard—will be made available as a template.

---

Reference Links

1. SAP Support: Innovation Commitment for SAP S/4HANA until 2040
2. SAP News: New SAP S/4HANA Release and Maintenance Strategy
3. sapperment: Business Case & TCO
4. SoftwareSeni: The Real Cost of Migrating to SAP S/4HANA and How to Build a Business Case That Holds
5. Flectic: ERP ROI Benchmarks by Company Size
6. Flectic: ERP ROI—How to Calculate It and What SMEs Actually See
7. Rand Group: What Is the Average ROI of an ERP Implementation?
8. Hyperbots: SAP S/4HANA Pricing Explained—What Finance Leaders Actually End Up Paying

---

Disclaimer

Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.

---

Back to Top