ERP Implementation, Switzerland

Where Swiss ERP implementations tend to slip

Swiss projects rarely fail on core accounting. They slip on details that sit between the software, the bank, the fiduciary and the language regions, and these are often left until the final weeks. The patterns I watch for:

• Bank connectivity tested late. QR-bill references and payment files work in the integrator's test system but have never been sent to, or read from, your actual banks.
• VAT codes nobody outside the project has seen. The setup looks reasonable, yet the fiduciary first sees the figures after the first return is due.
• Layouts in one language. German documents are finished early, while French or Italian versions appear in the last days with untranslated labels.
• Partner apps treated as part of the core. A Swiss app for banking or payroll postings has its own vendor and update cycle, and nobody owns it after go-live.
• Design decisions by default. Busy process owners skip workshops, so the integrator configures what seems sensible.

None of this needs a large team to prevent. It needs someone on the client side who keeps a list, asks for evidence and makes sure the right person signs off each decision. That is the role I play, building on the requirements and selection work described on my Swiss ERP selection page.

Overseeing the integrator without getting in the way

A good Swiss integrator welcomes an organized counterpart on the client side, because decisions arrive faster and testing is better prepared. My aim is to make the project easier for both sides, not to audit every hour.

In practice that means a short weekly working session with the integrator's project manager, a steering meeting with your sponsor at an agreed rhythm, and three shared logs: decisions, risks and change requests. I review design documents and configuration demos against the requirement list and mark each item as agreed, open or changed. Where the integrator proposes a workaround, I check whether it creates manual work for your staff after go-live.

Change control matters in Switzerland for a simple reason: many offers are priced on assumptions, and every extra layout, interface or report moves the total. Each request is logged with its business reason, the integrator's estimate and the effect on the plan, then decided by your sponsor. Requests that can wait go into a later-phase backlog rather than being squeezed into the current budget.

I do not configure the system myself on integrator-led projects, and I do not take over their responsibility for delivery. The general approach is set out under ERP implementation.

Migrating from Swiss packages and spreadsheets

Many Swiss companies starting an ERP project are leaving a domestic accounting package such as Abacus, Bexio, Sage or Banana, often alongside spreadsheets for stock, projects or pricing. The migration plan has to respect how those sources hold data, and it needs owners on your side as well as on the integrator's.

I review the mapping templates and the plan for trial loads, then check the results with your finance and operations staff:

• Customers and suppliers with correct IBANs, QR-IBANs where used, VAT numbers and language codes for documents.
• Open receivables and payables, including QR references on open invoices so later payments still match.
• Opening balances by account and by currency, agreed to the legacy trial balance.
• Stock quantities and values by location, agreed to the last count.
• The history you have decided to keep, and where older periods remain readable for audit.

Each trial load ends with a reconciliation signed by the data owner. If figures do not agree, the cause is found and fixed in the mapping or the source, not patched in the new system. For a fuller checklist see my ERP migration checklist and the data migration service.

Testing bank files, VAT and multilingual documents

User acceptance testing in a Swiss project should prove the flows that touch the outside world, not only the screens inside the ERP. The scenario scripts are drafted with the managers who own each process, and in a Swiss project they always include:

• A full receivables cycle: invoice with QR-bill, payment received through the bank statement import, automatic match and the resulting balance.
• A payables cycle: supplier QR-bill captured, approved and paid in a payment file accepted by each of your banks, using a test or validation service where the bank offers one.
• VAT scenarios agreed with your fiduciary, run through to the report they will use, including imports and foreign currency sales.
• A period-end routine with currency revaluation and the key management reports.
• Documents printed in each language your customers receive, checked by a staff member who works in that language.

Defects go into one log with severity rules, and I triage them with the integrator so real defects, training needs and new requests are separated. UAT ends with agreed sign-off criteria, not with a date. The method in detail is on my ERP testing and UAT page.

Go-live, payroll handoff and hypercare

Many Swiss companies keep payroll in a separate Swiss payroll package or with an external provider and bring only the postings into the ERP. Before go-live I make sure the handoff is designed and tested: which accounts and cost centers receive the payroll journal, who imports it, how differences are reconciled and who signs it off each period.

The cutover itself follows a written plan with owners for every step: freezing the old system, final loads of open items and balances, switching bank connections, activating user access and confirming the first invoices and payment runs. Your finance lead and fiduciary agree in advance which period-end the switch should follow, so the old and new systems do not split a VAT period awkwardly.

Hypercare starts on day one: a short daily check-in, one issue log, clear priorities for anything blocking invoicing or payments, and escalation to the integrator where configuration is at fault. It ends when agreed exit criteria are met, including a completed first period-end close. All of this runs remotely, with your key users providing hands-on help at each site; a visit can be added by arrangement. Training material in German, French or Italian is prepared by your team or the integrator. More on the wider Swiss picture is on the Switzerland overview and the Swiss ERP consultant page.