S/4HANA Add-Ons and HANA Database Licensing Costs: The Hidden Costs You Must Budget For

Why SAP S/4HANA Budgets Break Down

SAP presents S/4HANA migration as a strategic upgrade that modernises the enterprise core while simplifying the licensing model. Both claims contain partial truths, but the commercial reality of an S/4HANA transition involves a licensing landscape that is materially more complex — and more expensive — than the migration proposal suggests.

The core problem is structural: SAP's sales process leads with transformation narrative and migration tooling. It does not lead with a complete, itemised view of the licensing costs that arise when a mid-size or large enterprise is fully deployed on S/4HANA. Those costs emerge later — sometimes during contract negotiation, sometimes after go-live — and they are the primary driver of budget overruns on SAP transformation programmes.

Based on our advisory work across more than 80 SAP engagements, the typical organisation underestimates S/4HANA licensing cost by 30 to 45 percent. The hidden layers that account for this gap are predictable and avoidable with proper pre-negotiation analysis. This article identifies every major cost category you must include in your S/4HANA budget and explains the commercial logic behind each.

Cost Layer 1: HANA Database Licensing

S/4HANA is not a database-agnostic product. Unlike SAP ECC, which ran on a range of third-party databases including Oracle, Microsoft SQL Server, IBM DB2, and MaxDB, S/4HANA runs exclusively on SAP HANA. For organisations migrating from ECC on a non-HANA database, this is a new licensing cost line that is frequently omitted from initial migration budgets — because SAP's sales teams focus on the application licences, not the database fees underneath them.

HANA Runtime versus HANA Full-Use

SAP offers two flavours of HANA licensing for S/4HANA customers. The HANA Runtime licence is restricted use: it permits HANA to be used exclusively as the database for S/4HANA and explicitly prohibits access by non-SAP applications. The fee for HANA Runtime is approximately 15 percent of the S/4HANA application licence value. For an organisation with $2 million in S/4HANA application licences, the runtime database fee would be roughly $300,000 — plus annual maintenance of 18 to 22 percent on that amount, adding another $54,000 to $66,000 per year in perpetuity.

The HANA Full-Use licence removes the restriction: it permits any application — including non-SAP analytics tools, custom applications, and third-party integrations — to access data held in the HANA database. Full-Use is licensed in memory blocks (typically 64 GB increments), and the per-block cost varies significantly by commercial tier. At illustrative list pricing, a 256 GB HANA environment could carry a capital licence cost in excess of $400,000, with annual maintenance compounding on top.

The critical compliance risk: organisations that purchase HANA Runtime but subsequently allow non-SAP tools to query HANA — even indirectly through SAP's BW/4HANA or SAC reporting layers — may technically be in breach of the Runtime licence scope. SAP has identified this as an audit risk vector in several engagements we have supported, particularly where BI tools were connected to HANA during migration testing and never formally decommissioned from production.

Cost Layer 2: Functional Add-On Engine Licensing

S/4HANA's modular architecture separates base application functionality from advanced functional capabilities that SAP calls "engines." This is not arbitrary product design — it is a licensing mechanism that allows SAP to charge separately for advanced features of functional areas that ECC customers previously accessed through a single application licence.

Extended Warehouse Management (EWM)

In SAP ECC, Warehouse Management (WM) was included in the core application licence for most logistics-oriented deployments. In S/4HANA, SAP has introduced Extended Warehouse Management (EWM) as a separately licensed engine that replaces the basic WM capability for organisations requiring advanced warehousing functionality. EWM is priced by a transaction-volume metric (warehouse orders or warehouse tasks, depending on the contract), and for organisations with high warehouse throughput, this cost can run into hundreds of thousands of pounds annually.

Organisations that have assumed their existing WM capability would carry forward into S/4HANA at no incremental cost are regularly surprised to discover that the S/4HANA equivalent requires a separately licensed engine. The functional gap between S/4HANA basic warehouse management and EWM is not negligible — the basic offering is missing capabilities that many logistics-intensive businesses rely on — which means organisations often have no practical choice but to purchase EWM.

Transportation Management (TM)

SAP Transportation Management — covering freight order management, carrier selection, shipment tendering, and transportation costing — was historically a separate SAP product. In S/4HANA, TM integration is tighter but the commercial model is still additive: organisations that require full TM functionality must license it separately. The pricing model is typically based on transportation-relevant shipment documents, and for logistics companies or manufacturers with high shipment volumes, this is a six-figure annual commitment.

Manufacturing and Planning Engines

SAP's Advanced Planning and Optimisation (APO) capability — covering demand planning, supply network planning, and production planning — has been redesigned in S/4HANA as the Integrated Business Planning (IBP) module, which is a separate cloud subscription. Organisations that are migrating APO functionality to S/4HANA must budget for IBP separately, and IBP's subscription pricing is entirely independent from the on-premise S/4HANA licence. This creates a mixed on-premise and cloud licensing model that has its own renewal and commercial management challenges.

Cost Layer 3: Digital Access and Indirect Access

Digital access — SAP's formalised licensing model for document creation via non-SAP systems — is one of the most commercially significant licensing changes in the S/4HANA era. Prior to 2018, SAP's indirect access rules were broadly enforced through audit findings, creating significant uncertainty about the cost of integrating third-party applications with SAP. In 2018, SAP introduced the Digital Access add-on, which provides a formal licensing framework for indirect access but does not reduce the total cost — it replaces unpredictable audit exposure with a structured fee model.

How Digital Access Works

Under the Digital Access model, SAP charges per document created in S/4HANA as a result of actions in non-SAP systems. The key document types include sales orders, deliveries, goods movements, production orders, purchase orders, financial accounting documents, and service orders. For an organisation that uses Salesforce to create sales orders that flow into S/4HANA, each SAP sales order document generated through that integration triggers a Digital Access fee. Similarly, IoT-driven goods movements, e-commerce platforms processing in S/4HANA, or custom applications creating financial documents all fall under this model.

The per-document pricing varies by document type and commercial tier. SAP publishes guidance on document-type pricing in Passport Advantage and its pricing documentation, but the effective cost depends heavily on document volumes. For high-volume manufacturing or logistics environments, the annual Digital Access cost can match or exceed the core application maintenance fee. We have supported organisations that discovered mid-migration that their integration architecture would generate $500,000 to $1.5 million in annual Digital Access fees that were not in the original budget.

Legacy Indirect Access Risk on Existing Integrations

Organisations that are migrating to S/4HANA on a brownfield or bluefield path retain their existing integration architecture during the transition. If those integrations involve non-SAP systems creating or modifying SAP data, and the organisation has not previously addressed indirect access licensing, the S/4HANA migration provides SAP with an opportunity to regularise the indirect access position — at commercial terms dictated by SAP's current pricing model. We strongly advise clients to conduct an integration audit before beginning any S/4HANA commercial negotiation, to ensure the indirect access liability is quantified and addressed proactively rather than reactively.

Cost Layer 4: Annual Maintenance and Support Fees

SAP's standard annual maintenance rate is 22 percent of the net licence value for Enterprise Support, and 18 percent for Standard Support (which provides reduced service levels). The choice between Enterprise Support and Standard Support has been a recurring negotiation point in SAP engagements — SAP's position is that Enterprise Support is required for S/4HANA, though the contractual underpinning of this requirement is not always as absolute as SAP represents.

The compounding effect of maintenance fees on total cost of ownership is frequently underestimated in migration business cases. A $5 million S/4HANA application licence (including HANA runtime, add-on engines, and Digital Access entitlement) carries annual maintenance of $900,000 to $1.1 million from day one. Over a ten-year ownership period, the maintenance cumulative cost approaches the initial licence cost — representing total investment of $9 to $11 million on a $5 million initial outlay, before inflation adjustments or any additional licence expansion.

SAP has historically applied annual maintenance increases of 2 to 3 percent in line with contractual CPI provisions. In practice, maintenance negotiations have delivered flat or slightly reduced rates when combined with new licence commitments, but achieving sustained maintenance reduction requires active commercial management at each renewal cycle.

Cost Layer 5: RISE with SAP Cloud Subscription Surcharges

For organisations adopting S/4HANA via RISE with SAP — SAP's cloud-first migration bundle that combines software, infrastructure, and support in a single subscription — the cost structure differs from on-premise licensing but introduces its own hidden cost categories. RISE bundles are priced on a per-SAPS (SAP Application Performance Standard) basis, and the baseline subscription covers a defined compute and memory allocation.

Organisations frequently find that their actual production workload requirements exceed the baseline RISE allocation, requiring uplift to a higher performance tier at incremental cost. Additional charges arise for non-production environments (quality assurance, development, sandbox), which are priced separately from the production subscription. High availability and disaster recovery configurations, business continuity testing environments, and batch processing peaks can all generate overrun charges that were not visible in the initial RISE proposal.

Additionally, RISE with SAP does not automatically include all the functional add-on engines discussed above. EWM, TM, IBP, and other separately licensed capabilities must still be negotiated and budgeted as distinct add-ons within the RISE commercial framework. The cloud deployment model does not eliminate the add-on cost structure — it changes how they are packaged and invoiced, but the underlying commercial obligation remains.

Negotiation Strategy: How to Control These Costs

Understanding the full cost landscape is the prerequisite for effective negotiation. Organisations that enter S/4HANA negotiations without a detailed model of their HANA database requirements, add-on engine consumption metrics, Digital Access document volumes, and maintenance fee trajectory are negotiating blind. SAP's commercial teams are highly experienced at presenting proposals that are commercially optimised from SAP's perspective — buyers who have not done equivalent preparation consistently pay more than they need to.

The most effective approach to S/4HANA cost control combines three elements. First, a pre-negotiation licence audit that maps current ECC entitlements to the S/4HANA equivalent, identifies which add-on engines are genuinely required versus aspirational, and quantifies the Digital Access exposure based on the intended integration architecture. Second, independent benchmarking of SAP's proposed pricing against market reference data from comparable organisations — discount norms, maintenance rate norms, and add-on engine pricing norms are all knowable through market intelligence. Third, a negotiation strategy that sequences commitments appropriately — avoiding over-commitment to RISE or cloud terms before the full cost of on-premise equivalents is understood, and ensuring that Digital Access and add-on engine pricing is locked in as part of the migration agreement rather than deferred to post-go-live commercial conversations.

Redress Compliance has supported organisations through every stage of SAP S/4HANA commercial negotiation — from pre-negotiation licence analysis through to final agreement review and ongoing maintenance management. Our approach is entirely buyer-side: we do not take fees from SAP and we have no commercial relationship with any implementation partner, ensuring that our analysis reflects your interests without compromise.