SAP Licence Cost Modelling: How to Build a 5-Year Forecast for SAP Spend

Why 5-Year SAP Cost Forecasting Is Non-Negotiable in 2026

Every CFO in 2026 faces the same impossible conversation: ECC is dying. SAP Support ended on December 31, 2025, and your SAP environment must migrate. Now.

But to where? S/4HANA on-premise? RISE with SAP? A hybrid cloud model? Each path carries wildly different cost profiles, and SAP's commercial team will push whatever maximizes their revenue, not your total cost of ownership.

This is why a defensible 5-year SAP cost forecast matters more now than ever. You're not forecasting a static environment. You're forecasting uncertainty, risk, and SAP's relentless ability to escalate pricing faster than your business grows.

A proper 5-year forecast does three things: First, it gives your finance team a baseline against which to challenge SAP's proposals. Second, it reveals which cost drivers are controllable and which aren't—so you know what to defend. Third, it exposes the break-even point where cloud actually becomes cheaper than on-premise, which is rarely where SAP claims it is.

The Cost Categories SAP Doesn't Prompt You to Model

SAP's own TCO models—the ones their sales team will throw at you during cloud migration discussions—omit the cost categories that actually matter most to your enterprise. This is deliberate. SAP's TCO calculators are designed to make cloud migration look inevitable.

Here's what SAP conveniently leaves out:

• Escalation factors beyond the headline rate: SAP quotes 5% annual maintenance escalation on your RISE subscription, but that's just the baseline. Indirect access costs, Digital Access fees, and BTP consumption charges escalate faster than core license maintenance—often 8-12% annually.
• True-up and settlement exposure: Under RISE with SAP and Named User licensing, SAP measures your actual users and consumption quarterly. A business expansion, acquisition, or temporary spike in usage triggers financial settlements you didn't budget for. Most enterprises face 3-7% unplanned licensing costs annually from true-ups alone.
• License measurement and audit defense: SAP runs audits. When they find indirect access exposure—users accessing the system through middleware, reporting tools, or workflow automation—they charge you for Named Users you didn't know existed. Your 5-year model must include an audit reserve: budget 1-2% annually for measurement and settlement costs.
• Transformation and system remediation: If you migrate to cloud, SAP's services team will charge you to redesign custom code, rewrite interfaces, rebuild authorizations, and retrain BASIS staff. This is often bundled in transformation services fees that dwarf the year-one license cost.
• Change management and organizational impact: S/4HANA upgrades and cloud transitions require your team to change processes. That means temporary staff augmentation, consulting hours, and lost productivity while people learn new workflows.

Building Your ELP Baseline: Where Every Forecast Must Start

Before you can forecast SAP spend, you must know exactly what you own today. This is your ELP: Effective License Position.

Your ELP is not what you think you're licensed for. It's what you're actually entitled to, based on your contracts, purchase orders, and maintenance agreements. Most enterprises are horrified when they audit their own ELP: they discover they're under-licensed, over-licensed in the wrong ways, or carrying legacy licenses nobody is using.

To build your ELP baseline accurately:

1. Collect every SAP contract, amendment, and PO from the past 5 years: License agreements stack. You may have old contracts with different Terms of Acceptance than current agreements. You may have perpetual licenses mixed with subscription licenses. You may have industry-specific or country-specific licensing terms that are buried in amendments.
2. Reconcile against your LAW record: SAP's License Administration Workbench (LAW) is your single source of truth for what SAP thinks you own. Compare your contracts against LAW. Discrepancies often reveal negotiation leverage.
3. Map your actual usage against your licensing position: Run a System Measurement Agent (SMA) or equivalent forensic measurement tool to count Named Users, quantify indirect access, and measure engine-based usage. Compare measured usage to your licensed position. This gap is critical: it shows you where you have coverage and where you're exposed.
4. Identify your USMM exposure: Unrestricted use of SAP Standard Measure (USMM) is often baked into your license agreements but not explicitly called out. USMM entitles you to measure and license entire systems—not per Named User, but per system footprint. If your contract includes USMM, your licensing costs may be dramatically different than your current model assumes.

The 5-Year Forecast Framework: Year-by-Year Breakdown

Now that you have your ELP baseline, here's how to build a defensible 5-year model:

Year 1: Baseline Maintenance Escalation + Migration Costs

If you're staying on ECC while planning an upgrade, Year 1 costs are straightforward: your current annual maintenance fee × 1.05 (5% SAP escalation). But most enterprises are in transition, so add migration costs: assessment work, consulting, licensing remediation, and parallel running if you're moving to a new environment.

Migration costs typically run 10-20% of year-one recurring license fees. If your annual SAP licensing cost is $2M, budget $200-400K for migration services in Year 1.

Year 2: New System Stabilization + Indirect Access Exposure

By Year 2, your new system (S/4HANA, RISE, hybrid) is in production. Maintenance escalates again (5%). But now you add an indirect access reserve. The first audit or measurement cycle reveals users or systems you didn't account for. Budget 3-5% for indirect access discovery and settlement in Year 2.

Year 3-5: Full Cost Run-Rate + Escalation Momentum

By Year 3, your new system is fully stable. But cost escalation compounds:

• Core maintenance: 5% annual escalation (this is SAP's published rate, but real escalation often runs 6-7%)
• Indirect access true-ups: 5-7% escalation (SAP escalates these faster than core maintenance)
• Digital Access documents (if licensed separately): 8-12% escalation
• BTP consumption (if on cloud): 10-15% escalation, as your team discovers new BTP-enabled applications and workloads migrate to the cloud layer
• Preferred Success premium (if required by RISE): 7-9% escalation

By Year 5, your blended escalation across all cost categories may easily be 6-8% compound annually. This is what SAP's marketing team never shows you.

Notice how the blended growth rate compounds to 9.3% over the 5-year period, even though core maintenance is only 5%. This is the cost profile most enterprises miss in their initial forecasts.

How SAP's Own TCO Models Are Built to Push Cloud Migration

SAP's TCO calculators—the web tools SAP sales teams use in pitch meetings—are engineered to make cloud look cheaper than on-premise. This is not accidental.

SAP's TCO models systematically underestimate on-premise costs and overestimate on-premise TCO by:

• Capitalizing hardware and amortizing over 5 years, which looks like a lower annual cost than the actual cash outlay.
• Using low estimates for internal BASIS staff, often assuming one senior DBA can manage multiple systems (unrealistic).
• Ignoring security patching and infrastructure upgrades, which run 15-20% of total infrastructure costs annually.
• Omitting data center power, cooling, and network costs, which escalate faster than license costs in a hyperscaler environment.

Meanwhile, SAP's TCO models consistently underestimate cloud costs by:

• Using low consumption assumptions for BTP, Digital Access, and add-on modules. SAP assumes you'll only use base features, not premium capabilities.
• Omitting transformation and custom code remediation from the cost baseline. They call it a "one-time cost," not a recurring cost driver.
• Assuming you'll achieve promised efficiency gains immediately. In reality, cloud migration absorbs 6-12 months of reduced productivity as teams relearn processes.

Modelling BTP, SuccessFactors, Digital Access, and License Growth

Most 5-year forecasts fail because they model core license costs correctly but miss the secondary modules and cloud add-ons that compound the total.

BTP (Business Technology Platform) Consumption

If you're moving to RISE with SAP, you get a BTP entitlement. But most enterprises discover they need more BTP credits than their baseline entitlement provides. Custom analytics, integrations, and low-code applications consume BTP resources. Budget 15-30% growth in BTP consumption annually as your team learns what BTP enables.

SuccessFactors and HR Cloud Seats

If you're licensing SuccessFactors or other SAP cloud modules per user, model employee growth plus the cost of on-boarding contractors and temp workers. These are usually licensed separately from core SAP and escalate faster (8-10% annually) than core license maintenance.

Digital Access Documents

If your contract includes Digital Access licensing (often a per-document or per-user fee for advanced reporting and analytics), assume growth as your BI team discovers new use cases. Budget 10-15% annual growth in document licensing.

License Growth from Business Expansion

If your business is growing—new employees, new locations, new product lines—your SAP footprint grows. Model headcount growth and map it to SAP-licensed roles. Typically, 1-2% annual headcount growth translates to 2-3% SAP license growth (not all new headcount needs SAP access, but some roles require multiple licenses).

Sensitivity Analysis: Planning for SAP's Commercial Tactics

Your base-case forecast assumes SAP behaves consistently and escalates at published rates. But SAP has levers to increase costs faster than your base case assumes.

Build three scenarios:

Best Case (20% probability)

SAP escalates at published rates (5% for core maintenance), you successfully negotiate down indirect access exposure, and you achieve efficiency gains that reduce license growth. Total 5-year cost: baseline × 1.25.

Base Case (50% probability)

This is your primary forecast. SAP escalates at 5-6%, indirect access discovery costs 4%, and license growth tracks business expansion. Total 5-year cost: baseline × 1.40.

Worst Case (30% probability)

SAP escalates aggressively (7% for core, 10%+ for indirect access and BTP), an audit uncovers material measurement exposure, and you're forced to remediate quickly. Total 5-year cost: baseline × 1.55.

Most enterprises should plan for the worst-case scenario and negotiate license terms that cap escalation, limit true-up exposure, and define indirect access clearly.

When and Why to Bring in Independent Advisors

A 5-year SAP cost forecast is complex work. It requires forensic contract knowledge, understanding of SAP's measurement and licensing rules, and access to actual usage data. Most enterprises should engage independent advisors for at least the contract and ELP analysis portion of the forecast.

Here's why: SAP's account team has a structural conflict of interest. They profit if your costs increase. Your internal IT team knows your systems but often lacks detailed knowledge of SAP's commercial rules. Only an independent advisor—one with no relationship to SAP and no incentive to drive your costs up—can build a forecast that actually protects your interests.

Independent advisors should:

• Audit your contracts for hidden escalation clauses and unfavorable true-up terms.
• Analyze your current ELP and identify where you're exposed to measurement risk.
• Run forensic measurement to quantify indirect access and compare against your licensing position.
• Build your 5-year forecast with actual data, not SAP's assumptions.
• Validate SAP's proposals against your forecast and challenge unrealistic cost reductions.

Frequently Asked Questions

Related Articles