CIO Playbook: Navigating Licensing for New SAP S/4HANA Embedded Features

1. Introduction: Why Embedded Feature Licensing Is the Most Misunderstood Risk in S/4HANA Migrations

SAP S/4HANA represents one of the largest technology transformations CIOs face in their careers. The financial commitment is substantial—often stretching into tens of millions of dollars across implementation, infrastructure, and licensing costs. Yet despite this magnitude, a critical risk consistently goes undetected until mid-implementation or post-go-live: the true scope and cost of licensing for embedded and add-on features.

When SAP marketed the transition from ECC to S/4HANA, the narrative emphasized consolidation and simplification. Core features that were once separate modules—Customer Relationship Management (CRM), Supplier Relationship Management (SRM), basic warehouse management—were embedded directly into the S/4HANA platform. SAP positioned this as a cost-saving benefit: fewer module subscriptions, tighter integration, faster deployment.

The marketing worked. According to Gartner's latest analysis (end 2024), only 39% of SAP's 35,000 ECC customers have made the jump to S/4HANA. However, of those who have migrated, a recurring pattern emerges during implementation: the boundary between what is included in the core licence and what requires separate, often expensive add-on subscriptions is far more blurred than CIOs were led to believe.

This playbook is designed to equip you with the knowledge, frameworks, and negotiation strategies to audit embedded licensing before migration, prevent budget overruns, and lock in pricing before go-live. We will walk through what is actually included in S/4HANA core, where costs materialise, and how SAP's commercial advisory specialists craft licensing structures that incentivize incremental adoption—even when features appear integrated into the product.

2. What Is Actually Included in the S/4HANA Core Licence

To understand the cost risks, we must first establish a clear baseline: what features are genuinely embedded in the S/4HANA core licence and carry no additional fees?

Embedded Features (Included in Core Licence)

SAP S/4HANA incorporates several capabilities that ECC customers were accustomed to licensing as separate modules. These are now embedded:

• Customer Relationship Management (CRM): Basic CRM functionality—accounts, contacts, opportunities, leads—is included. However, advanced CRM capabilities such as marketing automation, complex territory management, and sophisticated forecasting often trigger add-on licensing.
• Supplier Relationship Management (SRM): Procurement workflows, vendor management, and purchase order processing are embedded. Collaborative procurement and supplier network features require separate licensing.
• Basic Warehouse Management: Warehouse Management System (EWM) features are included. The distinction matters: basic in-bound and out-bound logistics are embedded; advanced slotting, labour management, and yard management require SAP Extended Warehouse Management licensing.
• Financial Management: Core GL, AR, AP, and asset accounting are included. Intercompany transaction management, parallel accounting, and advanced consolidation can trigger add-ons depending on implementation scope.
• Integrated HANA Runtime: S/4HANA runs on SAP HANA, and the database runtime licence is bundled into the core S/4HANA licence value. However, this is where many CIOs miss a critical cost line item (covered in Section 6).

What "Embedded" Actually Means

Embedded does not mean "free of all complications." SAP's approach is to include baseline functionality but layer governance, compliance, or performance features as separate line items. For example, SAP Joule AI—SAP's generative AI offering—comes in two tiers: base skills (included) and premium skills (not included and consumption-based).

The same pattern repeats across analytics, workflow automation, and industry solutions. A feature may be visible in the product interface, but unlocking its full capability set requires an additional subscription or consumption-based commitment.

3. The Embedded-to-Add-On Boundary: Where Costs Materialise

The distinction between embedded and add-on is where SAP's licensing becomes complex and where CIOs must apply rigorous audit discipline.

Line-of-Business (LoB) Solutions and Industry Solutions

SAP offers vertical-specific solutions built on top of S/4HANA. These are licensed separately as add-ons:

• SAP Industry Cloud for Utilities (managing meter-to-cash operations for energy companies)
• SAP Industry Cloud for Process Manufacturing (batch tracking, recipe management, compliance)
• SAP Industry Cloud for Life Sciences and Healthcare (clinical trial management, supply chain for pharmaceuticals)
• SAP Business Network for Logistics (multi-modal transportation, carrier integration)

These solutions are licensed separately from the core S/4HANA licence. Pricing varies but typically includes a recurring per-user or per-system fee, often with consumption-based components for transactional volumes.

Premium AI Units and Consumption-Based Pricing

One of the most consequential shifts in SAP licensing post-2024 is the move toward consumption-based pricing for advanced AI capabilities. SAP offers Premium AI Units at €5–€10 per unit, sold in bundles of approximately 100 units. These units are used when invoking premium skills in SAP Joule, SAP's generative AI assistant embedded in S/4HANA.

Here is the risk: SAP heavily markets Joule as a core modernisation capability. Marketing materials show AI-powered supply chain optimisation, generative insights for finance, and predictive procurement. Yet these premium capabilities are not included in the base S/4HANA licence. Every time a user invokes a premium skill—for example, asking Joule to forecast demand based on ERP data—that consumption is charged against the organisation's Premium AI Unit allocation.

As organisations scale AI adoption, this consumption cost becomes material. A large enterprise rolling out Joule across 500 users could easily consume €50,000+ annually in Premium AI Units, depending on adoption depth.

HANA Database Runtime Licence: A Hidden Line Item

S/4HANA runs exclusively on SAP HANA. Technically, the HANA database runtime licence is bundled into the core S/4HANA licence value. However, SAP calculates this as 15% of total S/4HANA software value. Many CIOs do not realise they are paying for this component until they attempt to size database infrastructure or negotiate renewals.

For a €10 million annual S/4HANA licence commitment, €1.5 million of that is database runtime. This line item is critical to understand during scoping because it compounds with size: larger instances mean larger database footprints, which means higher runtime costs as a percentage of the total investment.

4. SAP Analytics Cloud: The Embedded Analytics Trap

SAP's most common embedded licensing surprise involves analytics. S/4HANA includes basic transactional reporting and Fiori dashboards. However, advanced analytics—enterprise-wide reporting, predictive analytics, and integrated planning—via SAP Analytics Cloud (SAC) requires a separate per-user subscription.

The Real-World Pattern: A Manufacturing Company's €280,000 Surprise

A European manufacturing company with 400 users across finance, supply chain, and operations assumed all analytics shown in S/4HANA demos were included in the core licence. Mid-implementation, they discovered that the planned SAP Analytics Cloud rollout—critical for monthly financial close, demand planning, and inventory optimisation—required separate per-user subscriptions for 400 users. At typical SAC pricing (~€700 per user annually), this added €280,000 per year to the total cost of ownership, a cost that had not been budgeted and was not anticipated during the business case.

This pattern repeats across industries. CIOs approve S/4HANA on the assumption that "all the analytics we saw in the demo are included." In reality, basic dashboards are included; comprehensive analytics require SAC, which is a distinct licence with its own per-user pricing model.

SAC Pricing and Adoption Scaling

SAP Analytics Cloud licensing is straightforward but expensive at scale. Typical per-user annual costs range from €500 to €1,500 depending on the user type and geography. Enterprise licences (allowing unlimited users) are available but typically start at €200,000+ annually, making per-user licensing more cost-effective for organisations under 300 concurrent users.

The adoption risk is real: once SAC is deployed, usage tends to expand. Finance teams build additional planning models, supply chain adds demand sensing dashboards, and plant operations creates real-time KPI boards. Each expansion uses more SAC users and features, pushing costs upward year-on-year.

5. BTP Credits and Joule AI: The Consumption Cost That Scales with Adoption

The second major consumption-based risk involves SAP's Business Technology Platform (BTP) and Joule AI premium skills. Understanding this cost model is essential for forecasting total cost of ownership post-2025.

Base Skills vs. Premium Skills: The Joule AI Licence Stratification

SAP Joule is SAP's generative AI offering, integrated into S/4HANA and other SAP cloud products. Joule comes with base skills—fundamental AI capabilities such as summarising documents, generating email drafts, and providing AI-powered help documentation—included in the S/4HANA subscription.

Premium skills, however, are NOT included. These include:

• Generative demand forecasting (AI predicts demand based on historical data and external signals)
• Supply chain exception handling (AI identifies and suggests resolutions for procurement exceptions)
• Generative financial insights (AI identifies anomalies and trends in GL accounts and profitability data)
• Dynamic procurement recommendations (AI suggests suppliers and contract terms based on spend patterns)
• Custom AI models trained on your data (organisation-specific predictive models)

Each invocation of a premium skill consumes BTP Credits. Organisations can purchase Premium AI Units (bundles of ~100 credits) at €5–€10 per unit. Once purchased, these units are consumed as users invoke premium skills. The consumption model is transparent but can be difficult to forecast pre-implementation.

Consumption Forecasting Challenges

A critical issue: CIOs have limited visibility into how much consumption their organisation will actually generate. SAP provides calculators and benchmarks, but real-world adoption patterns often exceed these models. A procurement team that uses generative procurement recommendations daily across 50+ sourcing scenarios per person per month will generate substantial Premium AI Unit consumption—possibly tens of thousands of euros annually for a mid-market organisation.

The risk is amplified because Premium AI Unit consumption is discovered post-implementation. Organisations launch Joule with high visibility and excitement. Usage grows faster than anticipated. By the time consumption reports are reviewed at contract renewal, substantial sunk costs have accumulated, and re-negotiating down is difficult.

6. Digital Access: The Document-Based Trigger Most CIOs Miss

One of the least visible SAP licensing rules involves Digital Access Licensing. This rule applies when third-party systems or external partners create, view, or access documents within SAP systems.

How Digital Access Licensing Is Triggered

SAP allows organisations to deploy SAP interfaces and APIs that allow external systems—custom applications, partner platforms, non-SAP ERPs—to create or read records in S/4HANA without requiring those systems to purchase SAP user licences. However, there is a cost: Digital Access Licensing applies to these interactions.

Typical scenarios that trigger Digital Access fees:

• A customer portal built on non-SAP technology allows customers to place orders, which creates purchase orders in S/4HANA. Each customer interaction via the portal triggers a Digital Access event.
• A supplier portal (managed by a third-party provider) allows suppliers to view purchase orders and shipments in SAP. Each supplier login and document view is a Digital Access event.
• An embedded finance system or business intelligence platform integrates with S/4HANA to pull GL balances and transaction data. Each API call or data extraction is a Digital Access event.
• A legacy ERP system in a subsidiary initiates EDI transactions that create sales orders in the S/4HANA central instance. Each EDI message creates a Digital Access event.

Pricing and Scale Risk

Digital Access Licensing is typically priced as a per-transaction or per-gigabyte-accessed fee, depending on the integration pattern. For organisations with high-volume supplier or customer integrations, these costs can accumulate quickly. A mid-market company with 500 active supplier partners creating purchase orders daily could generate 2,500–5,000 Digital Access events monthly, translating to €5,000–€10,000 in monthly licensing costs if not properly managed or negotiated.

The risk compounds because Digital Access Licensing is often not surfaced during implementation scoping. Integration architects focus on technical feasibility and rarely quantify the licensing impact of their design decisions. By the time the organisation launches supplier or customer portals, the Digital Access commitment is in place and difficult to unwind.

7. Clean Core and the LoB Extension Cost Model

In August 2025, SAP formalised the "Clean Core" framework, a classification system for custom code that fundamentally changed the licensing economics of S/4HANA extensions.

What Is Clean Core?

Clean Core is SAP's guidance framework for managing custom code and extensions in S/4HANA. Rather than modifying core SAP functionality (a practice that tied organisations to complex upgrade paths in ECC), Clean Core encourages organisations to classify custom development into four tiers:

• A-Extensions: Pre-certified SAP extensions that do not require custom development and have guaranteed support.
• B-Extensions: Configurable SAP extensions using SAP-provided tools (such as SAP Build) with moderate complexity and guaranteed support.
• C-Extensions: Custom code deployed outside the core S/4HANA system, typically on SAP Business Technology Platform (BTP) or third-party platforms, with conditional support.
• D-Extensions: Custom code that modifies core SAP objects, the riskiest classification, with limited support and upgrade implications.

The Licensing Consequence: BTP Becomes a Recurring Cost

Here is where Clean Core directly impacts licensing costs: any custom code classified as C or D (especially C, which is the most common custom extension approach) must run on SAP BTP. BTP is a cloud platform with consumption-based pricing—organisations pay for compute, storage, and integration capabilities consumed by their extensions.

As of mid-2025, SAP unbundled "Premium Plus" licensing and moved Joule AI premium and Datasphere add-ons to optional add-ons. However, this does not apply to BTP compute. Custom code moved to BTP becomes a new, recurring cost that organisations must forecast and budget for annually.

For organisations with significant custom development—particularly large enterprises with 50–200 custom objects in their ECC systems—this BTP consumption cost can represent €20,000–€100,000+ annually, depending on extension complexity and data volume.

8. Governance Framework: How CIOs Should Audit Embedded Licencing Pre-Migration

To prevent embedded licensing surprises, CIOs must establish a structured pre-migration audit framework. Here is a governance approach that has proven effective across multiple migrations:

Phase 1: Baseline Current Licensing

Start by comprehensively documenting all current ECC module and add-on licensing:

• Document every SAP module licence (CRM, SRM, EWM, etc.) currently deployed, per-user counts, and annual costs.
• Identify all third-party analytics tools (Business Objects, Cognos, Qlik, Tableau) integrated with ECC. These tools often become redundant post-S/4HANA if SAP Analytics Cloud is adopted, but if not planned, organisations continue paying for legacy tools alongside new SAP licensing.
• List all integration platforms and middleware (MuleSoft, Dell Boomi, Informatica) used to connect ECC to downstream systems. Post-migration, integration patterns may change, affecting licensing costs for these tools.
• Quantify total current module, tool, and integration licensing spend. This becomes your baseline cost to compare against S/4HANA licensing proposals.

Phase 2: Feature Parity Assessment

Map each ECC feature and functionality you currently use to the S/4HANA equivalent. For each feature, determine:

• Is this feature embedded in S/4HANA core licence?
• Is a separate add-on licence required?
• Is this feature available only via a third-party integration?
• Can this functionality be decommissioned post-migration to reduce licensing costs?

Use SAP's official licensing documents (the SAP Price List and SAP Product Availability Matrix) as your source of truth, not sales presentations or RFP responses. Request that your SAP account team provide a formal "Feature Licence Mapping" document that maps your specific feature list to S/4HANA licences.

Phase 3: Data Volume and User Growth Forecasting

Consumption-based and per-user costs depend on forecasting. For each consumption-based licence component, forecast:

• SAP Analytics Cloud: How many users will require SAC access? Project growth over 3–5 years, accounting for business expansion, new geographies, and digital transformations that increase analytics demand.
• Premium AI Units: Estimate frequency of premium AI skill usage per user per month. Multiply by total user base and Premium AI Unit cost per invocation. This is inherently uncertain; add a 20–30% contingency buffer.
• Digital Access Licensing: Identify all planned integrations, portals, and third-party access patterns. Estimate monthly transaction volumes for each integration. Request SAP's Digital Access Licensing calculator to convert transaction volume to annual cost.
• BTP Compute: If planning custom extensions, estimate the number and complexity of extensions. Collaborate with your BTP architect to forecast annual compute, storage, and integration costs.

Phase 4: Licensing Impact Model

Build a comprehensive licensing cost model that projects annual licensing spend under three scenarios: Conservative (minimal add-on adoption), Baseline (expected adoption), and Growth (optimistic expansion). Include:

Compare this projected S/4HANA cost against your current ECC licensing cost. If the comparison shows material increases (more than 10–15% year-on-year), investigate opportunities to reduce licensing costs before migration (e.g., rationalising analytics, reducing custom extensions, limiting Digital Access integrations).

9. Negotiation Strategy: Locking In Add-On Pricing Before Go-Live

The key to preventing embedded licensing budget overruns is negotiating and locking in pricing for all add-on and consumption-based components before go-live. Here is the proven negotiation framework:

Pre-Negotiation: Leverage and Timeline

SAP's commercial advisory specialists have maximum pricing authority in Q4 (July–September), when SAP's fiscal year ends and teams are incentivised to close deals. Additionally, SAP has incentive authority for new, large, or strategic accounts. Timing your licensing negotiation 4–6 months before planned go-live aligns you with SAP's commercial calendar, when discounts are deepest.

Prepare a total cost of ownership (TCO) model that quantifies the pricing impact of each add-on licence decision. If SAP's proposed pricing results in a 30% increase in annual software costs, your TCO model should make that visible. The conversation shifts from "here is what SAP recommends" to "here is what your business case can support."

Negotiation Topics and Tactics

• SAP Analytics Cloud Per-User Discounting: SAC is negotiable, especially if bundled into a larger S/4HANA deal. Request tiered per-user rates (e.g., €400–€450 per user for the first 300 users, then declining by geography or user tier). Lock in multi-year rates to prevent annual increases.
• Premium AI Unit Bundling: Rather than purchasing Premium AI Units à la carte, negotiate a fixed annual commitment (e.g., €100,000 annually in Premium AI Units) with the right to reallocate unused units. Include a true-up provision: if actual consumption exceeds €100,000, SAP can charge for overages, but at a discounted rate negotiated in advance.
• Digital Access Licensing Caps: Request a per-transaction price cap and a monthly maximum commitment. For example: "Digital Access Licensing is €1 per transaction, capped at €X per month, regardless of transaction volume." This prevents surprise bills from higher-than-anticipated portal or integration usage.
• BTP Compute Estimation and Contingency: Work with your SAP technical architect to estimate monthly BTP consumption costs. Include a 20–30% contingency. Lock this into the contract as a maximum monthly commitment with true-up provisions similar to Premium AI Units.
• SAC Enterprise Licence Evaluation: If you anticipate 300+ SAC users, explore whether an enterprise licence (unlimited users) is more cost-effective than per-user licensing. Enterprise licences often start at €200,000–€300,000 annually and can be more economical at scale.

Contract Language and Escape Clauses

Include specific contract language that protects your organisation from consumption surprises:

• Consumption Review Clause: "Beginning six months after go-live, SAP will provide monthly consumption reports for Premium AI Units, Digital Access, and BTP compute. If cumulative consumption in any category exceeds the forecast by more than 15%, the parties will meet to adjust the following year's commitment."
• Feature Licence Mapping Addendum: Include the "Feature Licence Mapping" document as a contract exhibit. This document specifies which features are included in core and which require add-ons. Amendments to this mapping require mutual written consent.
• Pricing Stability: Lock in per-user, per-unit, and per-transaction pricing for a minimum of three years. Annual increases should be capped at cost-of-living adjustments (typically 2–3% annually).
• Migration Credits Offset: SAP offers migration credits to organisations transitioning from ECC. These credits are typically 10–30% reductions on Year 1 and Year 2 licence costs and decrease ~10% annually. Negotiate to use these credits to offset add-on licence costs (SAC, Premium AI) rather than core S/4HANA costs.

10. Conclusion: Taking Control of Embedded Licensing

SAP S/4HANA migrations represent transformational investments for most organisations. The core licence is substantial, but the true financial risk lies in the blurred boundary between embedded and add-on features. SAP Analytics Cloud, Premium AI Units, Digital Access Licensing, BTP compute, and emerging consumption-based models create a licensing ecosystem that is far more complex than the legacy ECC module structure.

CIOs who treat embedded licensing as a "we will deal with it after migration" issue inevitably face budget overruns, stakeholder frustration, and missed cost-optimisation opportunities. The organisations that succeed are those that:

• Audit comprehensively pre-migration, using a structured governance framework that baselines current costs and maps every feature to its S/4HANA equivalent and licensing impact.
• Forecast conservatively, building consumption-based cost models for SAC, Premium AI Units, Digital Access, and BTP, with contingency buffers for adoption variability.
• Negotiate aggressively, leveraging SAP's commercial calendar (Q4), your migration size and strategic importance, and total cost-of-ownership models to secure multi-year pricing stability and consumption caps.
• Contract precisely, documenting feature-to-licence mappings as contract exhibits and including consumption review clauses, escape provisions, and pricing escalation caps.
• Monitor continuously, reviewing consumption data monthly post-go-live and adjusting adoption strategies if actual usage trajectories exceed forecasts.

The post-2024 SAP licensing landscape has shifted decisively toward consumption-based and per-user models that reward high adoption but penalise poor forecasting. For an organisation deploying S/4HANA across 1,000+ users, the difference between a Conservative and Growth licensing scenario across SAC, Premium AI, and BTP can easily exceed €5–€10 million over a five-year period.

This playbook has equipped you with the frameworks, terminology, and negotiation strategies to take control of this risk. The boundary between embedded and add-on is not a mystery—it is a deliberate commercial strategy. Audit it, forecast it, and negotiate it before you sign your migration agreement. The investment in this discipline during pre-migration will yield substantial savings and eliminate the unpleasant surprises that plague less-prepared migrations.