The Shift from On-Premise to Cloud Licensing
Traditionally, SAP customers bought perpetual licences and ran software on their own infrastructure. With the cloud, SAP has transitioned to a subscription-based model that fundamentally changes how you budget and manage licensing.
| Dimension | On-Premise (Traditional) | Cloud (SaaS Subscription) |
|---|---|---|
| Payment model | One-time perpetual licence + ~22% annual maintenance | Recurring annual/monthly subscription fees |
| What is included | Software usage rights only (hosting and support separate) | Software, hosting, infrastructure, standard support bundled |
| Accounting treatment | CapEx (upfront) + OpEx (maintenance) | OpEx only (recurring) |
| Ownership | You own the licence perpetually (can run unsupported) | No ownership. Stop paying, lose access. |
| Upgrades | Major upgrade projects every 3 to 7 years (your cost) | Continuous updates included. Always on latest version. |
| Scalability | Requires new licence purchases + hardware | Scale up/down at renewal or mid-term (with contract terms) |
| Long-term cost | Front-loaded; cheaper over 7+ years | Lower initial cost; often more expensive over 5 to 7+ years |
Cloud licences are more flexible (scalable annually) but create a permanent budget item that grows with usage. Over 5 to 7 years, subscriptions often cost more than equivalent on-premise ownership. Understanding each product's metrics is essential for accurate cost forecasting.
Key SAP Cloud Products and Their Licence Metrics
SAP's cloud portfolio uses at least five distinct licensing metrics across its major products. Each metric drives cost differently and requires its own governance approach.
| SAP Cloud Product | Primary Metric | How It Works | Indicative Pricing |
|---|---|---|---|
| SuccessFactors (HR Suite) | Per Employee Per Month (PEPM) | Subscription based on average employee count. Each module priced separately. True-up if headcount exceeds contracted level. | ~$7 to $10 PEPM per module. Core HR for 5,000 employees ≈ $420K to $600K/year. |
| Ariba (Procurement) | Managed Spend or Documents | Buyer subscription based on annual spend through platform (tiered %) or document/transaction volume. Supplier-side fees separate. | ~0.2 to 0.5% of managed spend. $100M spend ≈ $200K to $500K/year (tiered). |
| Concur (Travel & Expense) | Per Active User Per Month | Subscription based on employees who file expense reports or book travel. Packages for Expense and Travel sold separately. | ~$5 to $10/user/month. 3,000 travellers ≈ $180K to $360K/year. |
| S/4HANA Cloud (ERP) | Full Usage Equivalents (FUE) | FUE bundles user types: 1 FUE = 1 power user OR 5 casual users OR 30 self-service users. Flexible user mix within FUE pool. | Per FUE per year. 50 FUEs ≈ $50K to $150K/year depending on edition. |
| BTP (Business Technology Platform) | Consumption Credits | Buy annual credit pool; allocate to any BTP service (integration, database, analytics). Each service consumes credits at defined rates. | Annual credit commitments from $50K to $500K+. Pay-as-you-go or committed. |
| Analytics Cloud | Per User Per Month | Business User or Planning User subscriptions. Capacity-based options for larger deployments. | ~$20 to $35/user/month depending on user type. |
Product-by-Product Licensing Details
SuccessFactors: Employee-based. Modules (Employee Central, Recruiting, Performance & Goals, Learning) each priced per employee per month. Scales directly with workforce size. Enterprise suites bundle modules at a discount versus à la carte.
Ariba: Spend and transaction-based. Buyer modules use tiered spend or document metrics. Higher percentage on the first tranche, decreasing at volume. Supplier-side network fees are separate (membership plus transaction %). See our Ariba licensing guide for details.
Concur: Active user-based. Pay for employees who actually file expense reports or book travel. Some deals use report/trip count instead. Costs scale with traveller population.
S/4HANA Cloud: FUE model. Full Usage Equivalents provide flexibility. Change user mix without buying new licences as long as total FUEs suffice. Public edition is pure SaaS; Private edition (via RISE) allows more customisation. For the FUE model in detail, see RISE with SAP vs BYOL Contractual Differences.
BTP: Consumption credits. Cloud credit pool spent across any BTP service. Flexible but requires continuous monitoring to avoid exceeding credits. Unused credits may or may not roll over depending on contract terms.
€12M saved over 3 years — hybrid SAP support strategy.
SAP Cloud Licensing Advisory
Our independent SAP advisory team helps CIOs benchmark cloud subscription pricing, negotiate better terms across SuccessFactors, Ariba, Concur, and S/4HANA Cloud, identify shelfware and over-provisioning, and build governance frameworks for ongoing cloud cost optimisation.
SAP Advisory Services →Cost Implications and Real-World Examples
Understanding the financial impact of SAP cloud licensing requires modelling real scenarios. Below is an illustrative example for a mid-size enterprise.
Mid-Size Enterprise Example (5,000 Employees)
| SAP Cloud Service | Metric | Volume | Annual Cost (Illustrative) |
|---|---|---|---|
| SuccessFactors Core HR | ~$85/employee/year | 5,000 employees | $425,000 |
| Concur Expense | ~$5/user/month | 3,000 travellers | $180,000 |
| Ariba Buying | ~0.5% of spend | $50M annual spend | $250,000 |
| Total Annual Cloud Cost | $855,000 | ||
| 5-Year Total | $4,275,000 | ||
Cloud vs On-Premise 5-Year Comparison
| Cost Component | Cloud (5 Years) | On-Premise (5 Years) |
|---|---|---|
| Initial licence / Year 1 | $855,000 (subscription) | $3,000,000 (perpetual licence purchase) |
| Annual recurring | $855,000/year | ~$660,000/year (22% maintenance) |
| 5-Year total | $4,275,000 | $6,300,000 |
| Infrastructure | Included in subscription | Additional (servers, data centre, admin staff) |
| Upgrades | Included. Continuous delivery. | Major project every 3 to 7 years (additional cost) |
Cloud costs scale linearly with usage (employees, spend, users). On-premise costs are front-loaded and mostly fixed. A static environment may cost less on-prem long-term; a rapidly growing or changing environment benefits from cloud's pay-as-you-go model. Always run a 5 to 10 year TCO comparison factoring in growth projections.
Key Considerations
RISE with SAP bundles. RISE packages S/4HANA Cloud, BTP services, and migration tools into a single subscription (measured in FUEs). SAP claims ~20% lower TCO than on-prem. Validate with your own numbers. Compare RISE to à la carte licensing before committing. See RISE vs BYOL Contractual Differences.
Pricing is not public. SAP cloud pricing is highly negotiable and based on volume and bundling. Initial quotes have significant room for improvement. Benchmarking against market data and competitive alternatives is essential.
SAP Licensing Intelligence — Stay Ahead
Monthly advisory on SAP cloud cost optimisation, renewal tactics, and contract benchmarks delivered to enterprise IT leaders.
No spam. Unsubscribe at any time. View past editions →
Pros and Cons of SAP Cloud Licensing
"The cloud pricing conversation is not about whether cloud is cheaper. It is about whether cloud delivers enough operational value to justify the long-term cost premium. The answer depends entirely on your organisation's growth trajectory, IT maturity, and appetite for infrastructure management."