QR-bill
Standard in both directions: outgoing invoices carry the QR payment part with QR-IBAN and structured reference, incoming references clear automatically.
Spadoom AG, a Swiss SAP Gold Partner in Zug, implements SAP S/4HANA Public Cloud for SMEs in Switzerland and Italy with its own ERP team and connects it to sales, service and commerce with the same team. Every project starts with a five-day readiness check from CHF 12'000, credited against the implementation, which sets scope, timeline and a cost range. SAP quotes the subscription itself, usually under GROW with SAP.
S/4HANA Public Cloud (SAP Cloud ERP) is SAP’s ERP as software as a service: finance, procurement, sales, manufacturing, warehousing and logistics, operated by SAP with two releases a year. For an SME, size rarely decides whether it fits. The profile does. Product details, editions and licensing are on our S/4HANA Public Cloud page.
Spadoom implements the ERP with its own S/4HANA team and delivers Sales Cloud V2 and Service Cloud V2 with the same people. Spadoom is the only Swiss-headquartered SAP Gold Partner that delivers the ERP core and the complete CX stack with one team, so the seam between order, price and service case has one owner.
We also say when it does not fit. A single entity with simple processes is often better served by Dynamics 365 Business Central, a company whose administration centres on Swiss payroll by Abacus. The full decision guide with a ten-question checklist: ERP for Swiss SMEs: when S/4HANA Public Cloud pays off.
We publish no blanket price and no blanket duration for an ERP programme, because both depend on your scope. What we can publish: the fixed start, the phases, which steps have a known duration and what drives the cost in each one.
| Phase | Typical duration | What drives the cost |
|---|---|---|
| Readiness check | 5 days | Fixed price from CHF 12'000, credited against the implementation when you commission it. You receive findings, a target architecture, priorities and a phased plan with a cost range. |
| Fit-to-standard and scope | Set in the readiness check | Number of legal entities and countries, the scope items you activate, and how many processes you adapt to the standard instead of extending. |
| Configuration, data migration, extensions | Set after the readiness check | Quality of master data and open items, and extensions on SAP BAIP, the item most budgets underestimate. |
| Bank connectivity and payroll interface | Several weeks of elapsed time, so start in month one | Your bank’s onboarding and test cycle; where payroll runs and who owns the posting interface. Payroll is not part of S/4HANA Public Cloud. |
| Sales and service on the same customer master (optional) | 8 to 16 weeks, median 14 across our V2 projects | Number of integrations and countries. |
| Operation and releases | Two SAP releases a year | Internal time to review what is new, test your processes and sign off. |
| SAP subscription | Ongoing, usually under GROW with SAP | Quoted by SAP for your company. Users count as Full Use Equivalents (FUE); countries and scope add to it. SAP publishes no per-user list price. |
Calculate over five years and put subscription, implementation, payroll, integrations and internal time side by side. Only that total compares fairly with another ERP. The readiness check gives you the cost range for your scope.
The Swiss country version covers more than its reputation suggests. Our consultant Marek Budik sorts it into standard, configuration and out of scope in Swiss localisation in S/4HANA Public Cloud.
Standard in both directions: outgoing invoices carry the QR payment part with QR-IBAN and structured reference, incoming references clear automatically.
Tax procedure, current rates and the statutory return are standard. Acquisition tax on foreign services, the net tax rate method and cross-border place of supply need documented decisions before configuration.
CHF as local currency with EUR and USD alongside, parallel currencies for group reporting, ISO 20022 payment files. Connecting your bank is configuration and takes several weeks.
German, French, Italian and English side by side, per user. We run workshops, training and documentation in all four.
Data protection under the nDSG alongside the GDPR belongs to the default scope of a Swiss project, not to a change request.
Not in the product. Swiss payroll runs in SAP SuccessFactors Employee Central Payroll or at a provider, and many SMEs keep their Swissdec-certified payroll. Plan the posting interface as its own workstream.
Spadoom serves customers in Switzerland, Germany, Austria and Italy. Colleagues in our office in Cornate d’Adda near Monza complete the team, and we hold workshops and write training material and documentation in Italian.
S/4HANA Public Cloud ships country versions. According to SAP, GROW customers receive tax, statutory reporting and e-government updates for 60 countries as part of operations. Which Italian requirements your entity has, and which scope items cover them, we check per entity in the readiness check instead of promising it on a web page.
Italy has mandated structured B2B e-invoicing through SDI (Sistema di Interscambio) since 2019. How your Italian entity reaches SDI from the ERP is a design decision in the project, just like bank connectivity. On the purchasing side, SAP Business Network handles SDI centrally (procurement).
Perhaps your company belongs to an Italian or DACH group, or owns a sales company in Italy. Several entities and countries in one system is the strongest signal for S/4HANA Public Cloud. When the group headquarters keeps its own ERP, a two-tier setup puts the subsidiary on Public Cloud.
Published projects, each with the scope we actually delivered. We do not count a CX integration as an ERP implementation.
Beverages and consumer goods
Sales and Service Cloud V2 live in three months, connected to S/4HANA Public Cloud via SAP Integration Suite, plus our work in parts of MM and SD in Cloud ERP. The three months refer to the Sales and Service platform.
Read the story →Building technology and wholesale
SAP Integration Suite as the central hub between the online shop and S/4HANA: prices and stock in real time, orders flow back into the ERP without manual work.
Read the story →Packaging manufacturing · Thurgau
From zero to a 360-degree customer view in five months: Sales Cloud V2 in production, with customer data from Excel, Outlook and SAP ECC brought together.
Read the story →The expertise behind SkyCell’s five-month Public Cloud project is now at Spadoom. Spadoom took over assets and most of the workforce from Actum Digital Schweiz, where the SkyCell project was delivered.
GROW with SAP (on sap.com now SAP GROW) is SAP’s bundle for companies new to SAP, built on S/4HANA Public Cloud. It starts with packages for finance, supply chain or HR that you extend later without reimplementing; SAP GROW Fast offers a predefined scope for a quick start. RISE with SAP is aimed at existing SAP customers moving off an on-premises ERP. Pascal Strnad, more than twelve years at SAP, explains the difference in GROW with SAP vs RISE with SAP.
Still on SAP ECC? For SAP ERP 6.0 with enhancement packages 6 to 8, mainstream maintenance ends on 31 December 2027 and optional extended maintenance runs to the end of 2030; for enhancement packages 0 to 5 it already ended in 2025. Public Cloud means a new implementation, not a system conversion: you adopt standard processes and migrate master data and open items. The ECC 2027 navigator shows the dates with sources and a path finder in six questions; the transformation page shows the target picture.
ERP and CX do not have to go live at the same time. We agree one target architecture and deliver in stages, as described in rolling out S/4HANA Public Cloud and Sales Cloud V2 together.
Your contact
SAP S/4HANA Public Cloud Specialist Seller
Talk to the person who is responsible, not to a sales queue.
Spadoom. Spadoom AG is a Swiss SAP Gold Partner in Zug whose own S/4HANA team implements S/4HANA Public Cloud and whose CX team connects it to Sales and Service Cloud V2 and Commerce. It is the only Swiss-headquartered SAP Gold Partner that delivers the ERP core and the complete CX stack with one team. The start is a five-day readiness check from CHF 12'000.
Yes, if the profile fits. SAP sells it to companies of any size through GROW with SAP. It pays off with several entities or countries, complex manufacturing or logistics, a parent on SAP, or sales and service that need live ERP data. For a single entity with simple processes, a leaner ERP often fits better.
Two parts. SAP quotes the subscription in its offer, counted in Full Use Equivalents; there is no public per-user list price. The implementation depends on entities, countries, scope items, data migration and extensions. Our readiness check (5 days, from CHF 12'000, credited against the project) gives you a cost range for your scope.
There is no honest blanket number; we set the timeline after the readiness check. One example from our team’s experience: SkyCell’s Public Cloud project took five months, delivered at Actum Digital Schweiz; most of that team now works at Spadoom. Sales and Service Cloud V2 on top take 8 to 16 weeks, median 14.
For a company new to SAP that wants to work on the standard, usually yes. GROW is built on S/4HANA Public Cloud and starts with packages for finance, supply chain or HR. Existing SAP ECC customers are offered RISE with SAP, but can also start fresh on the public edition. Decide the edition first, the bundle follows.
Yes, both are standard in the Swiss country version: QR-bill in both directions, ISO 20022 payment files and the Swiss VAT return. The configuration work lies in bank connectivity and VAT edge cases such as acquisition tax.
No. Payroll runs in SAP SuccessFactors Employee Central Payroll or at an external provider and posts into finance. Many Swiss SMEs keep their Swissdec-certified payroll. Plan the posting interface as a separate workstream.
Yes. Spadoom serves customers in Italy, has an office in Cornate d’Adda near Monza and works in Italian. Country requirements such as electronic invoicing through SDI are checked per entity in the readiness check and designed into the project.
Yes, as a new implementation. Public Cloud does not support a system conversion from ECC: you adopt standard processes and migrate master data and open items. For EHP 6 to 8, ECC mainstream maintenance ends at the end of 2027 with optional extended maintenance to the end of 2030; for EHP 0 to 5 it ended in 2025.
A first conversation with a senior consultant, not a sales pitch. You learn whether the profile fits, which starting point makes sense and what the readiness check covers. If SAP is not the right answer, we say so.
Discuss your ERP project