ERP for Swiss SMEs: When SAP S/4HANA Public Cloud Pays Off and When It Does Not

TL;DR: S/4HANA Public Cloud pays off for a Swiss SME because of its profile, not its size. Clear signals for it: several entities or countries, complex manufacturing or logistics, a parent on SAP, sales and service that need live ERP data, and the will to work on the standard. Clear signals against it: one entity with simple processes, payroll at the heart of the administration, and nobody willing to own two releases a year. The checklist below gets you to an answer in ten questions.

I have worked on eleven SAP S/4HANA Public Cloud projects. In first meetings with Swiss SMEs the same question comes up almost every time, usually within the first fifteen minutes: “Aren’t we too small for SAP?”

The question is understandable, but it leads you astray. Size rarely decides. What decides is how your business is built and where it will grow over the next five years.

Here is how to tell the difference.

The short answer

S/4HANA Public Cloud pays off when at least two of these apply: you run several entities or countries, your value creation sits in manufacturing, warehousing and logistics, your parent or key partners work with SAP, sales and service need prices and stock in real time, and you want standard rather than custom-built.

It does not pay off if you are a single entity with simple trading or service processes, if payroll is the heart of your administration, or if nobody in your company wants to carry the release rhythm of a cloud ERP. Then Microsoft Dynamics 365 Business Central or Abacus is often the more honest choice.

What S/4HANA Public Cloud brings to an SME

The facts first, so the discussion stands on solid ground:

• A complete ERP from the cloud: finance, procurement, sales, manufacturing, warehousing and logistics, operated by SAP. SAP ships two releases a year to every customer, currently listed as 2602 and 2608 in SAP Help.
• A Swiss country version in the standard, including QR-bill in payables, receivables and sales and Swiss VAT.
• An entry in packages: through SAP GROW you start with finance, supply chain or HR and add more later without reimplementing. SAP GROW Fast also offers a predefined scope for a quick start.
• Clean core: you do not modify the core. Extensions use released tools in the system or run side by side on SAP BTP. That is why the system stays current without upgrade projects.

More on the product is on our S/4HANA Public Cloud page. How SAP’s GROW and RISE bundles fit together is explained by Pascal Strnad in GROW with SAP vs RISE with SAP.

Five signals that it pays off

1. You run several entities or countries

This is the strongest signal. A subsidiary in Germany, a sales company in Italy, a holding in Switzerland: as soon as intercompany, group reporting and several country localisations come into play, a local ERP per country gets expensive. S/4HANA Public Cloud handles this in one system, with group reporting in the product and regulatory updates that SAP delivers for 60 countries.

2. Manufacturing, warehousing and logistics get complex

When planning lives in Excel next to the ERP, batches and serial numbers need tracking, or several warehouses have to work together, a lean system hits its limits. This is exactly where SAP is deep: manufacturing, logistics, warehousing and asset management on SAP Best Practices.

3. Your parent or your key partner works with SAP

As the Swiss subsidiary of an SAP group, S/4HANA Public Cloud as a second tier is often the best answer: a complete ERP of your own, connected to headquarters for the few processes that genuinely cross the boundary. The four decisions behind it are in our article on two-tier ERP.

4. Sales and service need live ERP data

When field sales asks for stock by phone, or service cannot see which machine was delivered when, the problem sits at the seam between ERP and CRM. SAP Sales Cloud V2 and Service Cloud V2 read accounts, prices, stock and orders from S/4HANA. That seam is our daily work: we deliver ERP and CRM from one team.

5. You want standard instead of custom-built

Anyone maintaining a system adapted over many years knows the bill: every modification a risk at the next update, every person with the knowledge a single point of failure. If you are willing to adapt processes to the standard, that is not a loss. It is the main benefit of the public edition.

Four honest cases where it does not pay off

One entity, simple processes, Microsoft 365 everywhere. Business Central is then often the better and cheaper choice. Microsoft delivers the Swiss localisation itself and publishes per-user prices. Our comparison with Business Central says so plainly.

Payroll is the core of your administration, and the business stays in Switzerland. Fiduciaries, construction, services with many hourly wages: here Abacus is strong with its Swissdec-certified payroll. More in the comparison with Abacus.

Nobody wants to carry the release rhythm. Two releases a year means someone reviews what is new, tests your own processes and signs off. It is not a big effort, but it needs a name against it. If your team is two people who are already fully booked, say so in the business case, not in month nine of the project.

Your competitive edge sits in a process no standard covers. Then check whether it can be built as an extension on SAP BTP. If not, the public edition is not your system.

What SME projects often forget

Payroll. It is not part of S/4HANA Public Cloud. SAP documents the integration with SAP SuccessFactors Employee Central Payroll, which transfers payroll postings into finance. Many SMEs keep their existing payroll. Both work, but it takes a decision and an owner.

The bank. QR-bill and payment files are standard. Connecting your bank is still configuration and often takes longer than planned. Start early.

The data. Migrating customers, suppliers, materials and open items is rarely hard technically, but it is always a matter of discipline. Whoever moves old data uncleaned takes the old problems along.

The expiry date of today’s system. If you still run SAP ECC: mainstream maintenance ends at the end of 2027. Our ECC 2027 hub shows the dates with sources and a six-question path finder.

The checklist: ten questions for your decision

Answer each question yes or no. Honestly, not the way you would like it to be.

#	Question	Yes / No
1	Do we run more than one entity or country today, or will we in three years?
2	Does our parent, our key customer or our key supplier work with SAP?
3	Does a good part of planning, warehousing or logistics run in Excel next to the ERP?
4	Do sales or service need prices, stock and orders in real time?
5	Are we willing to adapt processes to the standard rather than the other way round?
6	Is there one person who reviews and signs off two releases a year?
7	Do our current custom developments give us little competitive advantage?
8	Have we decided where payroll will run and who owns the posting interface?
9	Does our current system have an expiry date (end of maintenance, vendor, key person)?
10	Have we calculated implementation and operation over five years, not just the licence?

How to read the result:

• 7 to 10 yes: S/4HANA Public Cloud is a serious candidate. The next step is to analyse your processes against the standard.
• 4 to 6 yes: It can fit, but it depends on the no answers. Clarify those first, especially questions 5, 6 and 8.
• 0 to 3 yes: A leaner ERP will probably serve you better. That is not a failure, it is a good decision.

What it costs, honestly

SAP publishes no per-user list price for S/4HANA Public Cloud; the subscription is in SAP’s offer. For the implementation I give no number without an analysis, because any number without your scope would be theatre.

What I can say: calculate over five years and put everything side by side. Subscription, implementation, payroll, integrations, internal time for tests and releases. Only that total can be compared with another ERP.

The next step

If the checklist puts you in the upper half: our S/4HANA readiness assessment takes five days, starts at CHF 12’000 and is credited against the transformation if you commission it. Afterwards you know which of your processes the standard covers, where extensions are needed and what scope is realistic.

If you would rather just talk first: write to us. We will also tell you when SAP is not the right choice.