SAP S/4HANA

You won't find a price for SAP S/4HANA on sap.com. Every edition ends in "Request a quote". That tells you who SAP is selling to: companies where the ERP decision is a multi-year programme, signed by the board, delivered by a partner.

SAP S/4HANA is SAP's current-generation ERP, launched in February 2015 as the successor to SAP ERP (ECC) and built to run only on SAP's in-memory HANA database. It covers finance, procurement, sales, supply chain, manufacturing, asset management, project management and HR processes, with industry-specific variants across the range. In 2026 SAP markets it under the SAP Cloud ERP umbrella, which can make the product names confusing. Here's how they map.

What S/4HANA Is in 2026: Three Ways to Run It

SAP S/4HANA Cloud Public Edition. Multi-tenant SaaS, run and updated by SAP. You adopt SAP's preconfigured best-practice processes and extend through APIs and side-by-side apps rather than modifying the core. It receives two releases a year, named by date: release 2608 was in SAP's early-release sessions in summer 2026, with AI assistants and agents as the main theme. SAP sells it mainly through GROW with SAP, aimed at midsize and fast-growing companies.

SAP Cloud ERP Private (formerly S/4HANA Cloud Private Edition). A privately managed S/4HANA that SAP runs "from infrastructure to application". It can run on a hyperscaler, in a private data centre or in a sovereign cloud. You keep much more freedom to configure and extend than in Public Edition. It's the core of RISE with SAP, SAP's package for moving existing on-premise customers to the cloud, which now includes AI assistants for system analysis, custom-code remediation, data migration, configuration, testing and rollouts.

SAP S/4HANA on-premise. You license it, host it and run it, as with classic SAP. On-premise and private-cloud releases follow a two-year cycle with feature packs every six months, and from the 2023 release onwards each release gets seven years of mainstream maintenance. The current release line is S/4HANA 2025; its first feature pack (FPS01) was reported in March 2026. SAP has committed to maintaining S/4HANA until at least 2040.

Across the cloud editions, SAP's AI assistant Joule and Joule Agents are now central to the pitch, for anomaly detection, reconciliation, approvals and supply chain planning.

Editions and Pricing (October 2026)

Short version: pricing is quote-based for every edition. SAP publishes no list price for S/4HANA Cloud Public Edition, SAP Cloud ERP Private or on-premise licences, and the product pages route to "Request a quote" or a sales contact (checked October 2026).

What you can know before talking to sales:

• Cloud editions are subscriptions. Licensing advisers describe the user metric as Full Usage Equivalents (FUE), where different user types (heavy professional users, lighter functional or self-service users) count as fractions of an FUE. The exact weights are set in your contract, so read the order form carefully.
• GROW with SAP promotes "simplified packages" with "transparent, fixed-scope pricing". It's still a quote, but a more packaged one.
• RISE with SAP bundles the private-cloud subscription, infrastructure, technical operations and transformation tooling in one contract.
• On-premise follows the classic model: licences plus annual maintenance, with named-user metrics, and your own (or your outsourcer's) infrastructure and Basis team.

Hidden costs aren't hidden so much as unpublished: partner fees, data migration, testing, change management, integration with non-SAP systems and, for on-premise, HANA-ready hardware. Ask every bidder to price them separately.

One date matters if you're on old SAP. Mainstream maintenance for SAP Business Suite 7 (ECC) ends at the end of 2027. Optional extended maintenance runs to the end of 2030, at a premium of two percentage points on your maintenance base. If you're a Spanish ECC customer, that date should shape your plans now.

Strengths

• Scale and depth. Multi-company, multi-currency, multi-country operations with deep finance, controlling, logistics and manufacturing. Few ERPs cover as much in one system.
• Industry coverage. SAP's GROW pages cite preconfigured processes for over 25 industries and regulatory logic for over 190 countries.
• Real-time finance on one data model. The Universal Journal and HANA's in-memory design mean finance and operations report from the same tables, not from copies reconciled later.
• Long-term support commitment. Maintenance to at least 2040 and seven-year mainstream windows per on-premise release make long planning horizons possible.
• A large partner and talent market. In Spain, as elsewhere, you can find SAP consultants for almost any module. They're not cheap, but they exist.

Limitations

• Cost and opacity. No public prices, complex metrics and multi-year commitments. Negotiation skill matters as much as functional fit.
• Implementation effort. Even "fast" cloud projects need serious partner involvement, data cleansing and testing. Large ECC migrations with many countries and lots of custom code can run for years.
• Public Edition's discipline. You get continuous updates and a clean core, but you give up modifying standard code. Companies with heavily customised processes can find this hard.
• Talent cost. SAP skills are specialised and not cheap, and you'll need them after go-live too.
• Overkill for most SMEs. For a 20-person Spanish company, the overhead of an SAP project rarely pays back.

Spain: Verifactu, SII and Localisation

SAP has long supported Spanish requirements, mostly through its eDocument framework, now delivered as SAP Document and Reporting Compliance (DRC).

• SII: SAP's eDocument Spain troubleshooting guide (KBA 2872857, last updated October 2025) has dedicated sections for the SII tax register books, the Canary Islands books (IGIC) and FACe e-invoicing to public administrations. It applies to SAP ERP and SAP S/4HANA on-premise.
• Verifactu: the same SAP guide includes a dedicated Verifactu section. Integration guides describe DRC as the component that generates the invoice records, QR code and AEAT submission on S/4HANA, with activation through standard configuration on the cloud editions.
• ECC: customers still on ECC use the eDocument framework with SAP Document Compliance, on-premise edition, described by integrators as a separately licensed add-on. Confirm licensing with SAP before planning.
• TicketBAI: isn't listed in that SAP guide's sections. If you invoice from the Basque Country, ask your partner for the exact solution and references.

Deadlines: under Real Decreto-ley 15/2025, Verifactu applies from 1 January 2027 for corporate income tax payers and 1 July 2027 for other taxpayers. SAP customers already filing through SII are outside Verifactu's scope. SII remains mandatory for companies with turnover above €6 million, those in REDEME and VAT groups. Smaller subsidiaries not on SII need a working Verifactu set-up.

Is DRC included in your licence, or a separate subscription? It depends on edition and contract, and SAP doesn't publish it. Get it in writing.

Implementation: Time, Cost Drivers, Partners

SAP doesn't usually implement alone. Projects run through partners, from global consultancies to Spanish SAP integrators, using SAP's SAP Activate methodology and "fit-to-standard" workshops.

• Public Edition via GROW: SAP markets fast starts. Its product page claims "30 days or less for delivery of initial scope", with a footnote that activation time varies, and it showcases a logistics customer that went live in 52 days. Treat these as best-case vendor examples for limited scope.
• Private Edition via RISE: most projects are conversions or selective migrations from ECC, where custom code, data volume and the number of countries drive timeline and cost.
• On-premise: the same as Private, plus infrastructure and Basis operations you own.

Main cost drivers: the amount of custom ABAP code to remediate, data quality, the number of legal entities and countries, integrations, testing and the internal team you free up for the project.

Who Should (and Shouldn't) Choose SAP S/4HANA

Good fit:

• Large Spanish and multinational groups with many legal entities, complex supply chains or manufacturing.
• Existing ECC customers facing the 2027 maintenance deadline.
• Fast-growing midsize companies that expect to become multinational and accept SAP's standard processes (Public Edition via GROW).
• Companies already filing SII that want compliance handled inside the ERP.

Look elsewhere if:

• You're a small or medium Spanish business with straightforward processes. Odoo or a Spanish ERP will cost a fraction of the price.
• You need heavy customisation but want SaaS simplicity; Public Edition won't allow the former.
• You can't fund a partner-led project or retain SAP skills after go-live.

Bottom line? S/4HANA is the safe choice for complex, international operations and the default path for ECC customers. Budget like it's a programme, not a software purchase, and get every licence component, DRC included, priced in writing.