When a French company opens a subsidiary in Geneva or an industrial group deploys SAP at their Zurich site, there’s a strong temptation to replicate the parent company’s ERP configuration. This is an expensive mistake. Switzerland is not just another European market: it’s outside the European Union, applies three distinct VAT rates, mandates QR-invoices since 2022, and requires commercial documents to be produced in the canton’s language — German, French, or Italian depending on the case.
This guide reviews Swiss regulatory constraints that directly impact ERP configuration, presents essential local vendors, and details common mistakes by international companies discovering these specifics after go-live.
Why Switzerland is a special case for ERP
Switzerland combines four particularities that distinguish it from all European ERP markets.
Outside the European Union. Despite bilateral agreements, Switzerland doesn’t apply EU VAT directives, the ViDA e-invoicing regulation, or IFRS accounting standards on a mandatory basis. Each cross-border flow between a Swiss entity and an EU entity generates customs declarations, certificates of origin, and import VAT that the ERP must handle natively.
Three VAT rates. The standard rate is 8.1%, the reduced rate 2.6% (food, medicine, books, newspapers), and the special hospitality rate 3.8%. These rates are set by the Federal Tax Administration (FTA) and change at irregular intervals — the last revision was January 1, 2024. A poorly configured ERP that applies French rates or doesn’t distinguish the hospitality rate generates erroneous VAT declarations from the first quarter.
Mandatory QR-invoice. Since September 30, 2022, the old red and orange payment slips (BVR) are no longer accepted by Swiss banks. Any invoice issued in Switzerland must include a QR-invoice section compliant with SIX Group’s standard (Swiss financial infrastructure). The ERP must generate the Swiss QR Code in ISO 20022 format, with the beneficiary’s QR-IBAN and structured payment data.
Contractual multilingualism. Switzerland has four national languages (German, French, Italian, Romansh). In practice, an ERP deployed for a company active in multiple cantons must produce invoices, purchase orders, and reports in the recipient’s language. This isn’t a matter of user comfort — it’s a commercial and sometimes legal obligation, particularly in cantonal public markets.
Swiss VAT: three rates and their configuration pitfalls
Swiss VAT is administered by the FTA and operates on a quarterly declaration system (or semi-annually for small taxpayers). Foreign companies generating more than CHF 100,000 in turnover in Switzerland must register for Swiss VAT and appoint a fiscal representative.
What the ERP must handle
- Three rates active simultaneously: 8.1% (standard), 2.6% (reduced), 3.8% (accommodation). The applicable rate depends on the nature of the service, not the client.
- Deductible input tax: the Swiss mechanism is similar to French deductible VAT, but the forms and declaration codes are different. The ERP must map each transaction to the correct FTA code.
- Net tax debt rate method (TDFN): SMEs with turnover below CHF 5.005 million can opt for this simplified method, which applies a sectoral flat rate instead of the actual calculation. The ERP must support both methods.
- Cross-border operations: a sale from France to a Swiss client may be exempt from French VAT (export) but subject to Swiss import VAT. The ERP must handle self-liquidation and associated customs declarations.
The rate change trap
Switzerland modifies its VAT rates by popular vote. The shift from 7.7% to 8.1% on January 1, 2024, caught many companies whose ERP didn’t have a mechanism for managing rates by effective date. Good ERP configuration anticipates historized rates: each rate is linked to a validity period, and invoices issued after the change date automatically apply the new rate, even if the order was placed before.
Mandatory QR-invoice: end of payment slips and ERP adaptation
The migration to QR-invoices is the biggest change in the Swiss payments landscape in twenty years. The standard, developed by SIX Group in collaboration with Swiss banks, completely replaces paper payment slips.
QR-invoice structure
A compliant QR-invoice comprises three elements:
- Payment header with creditor details, amount, and currency (CHF or EUR).
- Swiss QR Code — a QR code in the format defined by SIX, containing all structured payment data (QR-IBAN, reference, additional information).
- Receipt section — a detachable part on the right side of the invoice, reproducing the QR code data in plain text.
What the ERP must produce
The ERP must generate the billing PDF with the integrated QR-invoice section, respecting exact positioning and dimension specifications defined by SIX. Margins, QR code size (46 × 46 mm), and font (sans-serif, 8-10 pt) are standardized. A poorly formatted or positioned QR code will be rejected by the debtor’s banking software.
Swiss vendors (Abacus, Bexio, Klara) natively integrate QR-invoice generation. International ERPs (SAP, Odoo, Sage) require a complementary module or specific development — and this is often where hidden costs appear.
Reference types
The QR-invoice supports three reference types:
- QR-reference (QRR): 27-digit structured reference number, compatible with the former ISR system. Requires a QR-IBAN.
- Creditor Reference (SCOR): reference according to ISO 11649 standard, usable with an ordinary IBAN.
- No reference (NON): no structured reference — discouraged for automatic reconciliation.
The ERP must support at minimum the QRR type for the Swiss domestic market and the SCOR type for international transactions.
DE/FR/IT multilingualism: interface and document constraints
Swiss multilingualism is not a “nice-to-have”. For a company operating in multiple linguistic regions, it’s an operational and commercial necessity.
Three levels of ERP multilingualism
User interface. Zurich collaborators work in German, those in Lausanne in French, those in Lugano in Italian. The ERP must allow each user to choose their interface language without affecting underlying data. Swiss vendors handle this natively. International ERPs generally support it, but translations of specialized modules (payroll, Swiss accounting) are sometimes incomplete.
Outbound documents. This is the critical point. An invoice sent to a Bern client must be in German, an invoice for a Geneva client in French. The ERP must generate the same document in the recipient’s language, adapting not only free text but also field labels, payment terms, and legal notices. Per-language configuration on the client record is essential.
Chart of accounts and reporting. The Swiss chart of accounts (based on the SME framework from veb.ch or Swiss GAAP RPC for large companies) uses German labels in German-speaking cantons and French in Romandy. The ERP must support a multilingual chart of accounts — each account has a label in each language, and reporting displays in the user’s language.
Abacus: the unavoidable German-speaking leader
Abacus Research, founded in 1985 in St. Gallen, is the most established ERP vendor in German-speaking Switzerland. Its AbaClik product and Abacus ERP suite cover accounting, payroll, HR management, invoicing, and CRM.
Abacus strengths
- Native Swiss localization: multi-rate VAT, QR-invoice, SME chart of accounts, and Swiss GAAP RPC are integrated without additional modules.
- Complete Swiss payroll: Swiss payroll is a complex domain (26 cantons = 26 different withholding tax regimes, AHV, BVG, UVG). Abacus handles everything and produces compliant annual salary certificates.
- Dense partner network in German-speaking Switzerland: over 300 certified resellers and integrators.
- Cloud and on-premise: Abacus offers AbaWeb (SaaS mode hosted in Switzerland) and on-premise deployment for companies requiring data sovereignty.
Abacus limitations
- Weak presence in Romandy: the interface and documentation are primarily developed in German. The French version exists but French-speaking support is less responsive.
- Closed ecosystem: integrations with third-party tools (e-commerce, international CRM) are less fluid than with open-source vendors or major cloud ERPs.
- Cost: Abacus pricing is adapted to the Swiss market (high purchasing power), making it expensive compared to cloud alternatives like Bexio.
For whom?
Abacus suits Swiss SMEs and mid-market companies (50-500 employees) with their center of gravity in German-speaking Switzerland, managing complex Swiss payroll and wanting a local ERP with impeccable German support.
Bexio: the cloud-native for Romandy and German-speaking SMEs
Bexio, founded in Rapperswil-Jona in 2013, is the most popular cloud management platform among Swiss small businesses. Acquired by Mobiliar (Swiss insurer) in 2021, it offers accounting, invoicing, contact management, project management, and bank connectivity — all in a browser.
Bexio strengths
- Quick adoption: the interface is designed for non-accountants. A 5-20 person SME can be operational within days.
- Native QR-invoice: compliant QR-invoice generation is integrated, with automatic bank reconciliation via direct bank connections.
- Bilingual DE/FR: Bexio natively supports German and French, covering the majority of the Swiss market.
- Open API: Bexio offers a documented REST API allowing connection of e-commerce tools (Shopify, WooCommerce), POS solutions, or business apps.
- Accessible pricing: starting at CHF 35/month for the basic plan, Bexio is significantly cheaper than Abacus.
Bexio limitations
- No payroll module: Bexio doesn’t handle Swiss payroll. You must connect a third-party tool (Swisssalary, Run my Accounts) or outsource.
- Not suitable for complex structures: multi-entity, inter-company consolidation, and advanced analytical accounting are not part of the offering.
- Limited Italian: Ticino (Italian-speaking Switzerland) coverage is less developed.
For whom?
Bexio is ideal for Swiss micro and small SMEs (1-30 employees) looking for a simple, quick-to-deploy tool that’s natively compliant with Swiss regulations — without the complexity or cost of a full ERP.
Klara and Run my Accounts: SME alternatives
Klara, launched by Helvetia (insurer), targets Swiss micro-enterprises and freelancers. The tool covers simplified accounting, QR invoicing, and basic administrative management. Its main advantage: free for basic functions, funded by cross-selling insurance products. Klara suits freelancers and sole proprietors who don’t need inventory management or multi-currency.
Run my Accounts offers an original model: automated accounting combined with bookkeeping service. The company sends its documents (invoices, bank statements) and Run my Accounts books them via a software platform assisted by accountants. It’s a hybrid between an ERP and an outsourced accounting firm, suitable for companies that don’t want to manage their accounting internally.
SAP and Odoo in Switzerland: localization available?
SAP in Switzerland
SAP has its global headquarters in Walldorf (Germany) but has a strong presence in Switzerland, particularly among large companies and the pharmaceutical sector (Novartis, Roche). SAP S/4HANA and SAP Business One offer Swiss localizations covering multi-rate VAT, QR-invoice (via certified partners), and Swiss chart of accounts. Swiss payroll is handled by SAP HCM or SAP SuccessFactors with CH localization modules.
The caveat: SAP localization for Switzerland is maintained by a partner ecosystem, not by SAP directly. Quality and responsiveness depend on the chosen integrator. Realistic minimum budget: CHF 80,000-150,000 for SAP Business One in Switzerland, excluding payroll.
Odoo in Switzerland
Odoo has a Swiss localization module (l10n_ch) covering chart of accounts, multi-rate VAT, and QR-invoice. The module is maintained by the community and Swiss partners like Camptocamp (Lausanne) or Brain-Tec (Zurich). Swiss payroll is not covered by the standard module — specific development or a third-party tool is required.
Odoo advantage: lower entry cost (from CHF 20,000-40,000 for SME implementation), and open-source code flexibility allows fine-tuning flows to Swiss specifics. Disadvantage: localization maintenance depends on the community, which can create lag during regulatory changes (like the 2024 VAT rate revision).
Customs and non-EU: what your ERP must handle
This is the point that international companies systematically underestimate. Switzerland is not in the EU, and each physical flow of goods between the EU and Switzerland is an export/import operation.
Customs flows to configure in the ERP
- Export declaration (EU side): the ERP must generate data for customs declaration (SAD/EX) with nomenclature codes (HS/CN), customs value, and certificates of origin.
- Import declaration (Swiss side): via the Federal Office for Customs and Border Security’s (FOCBS) e-dec system. The ERP or freight forwarder must transmit the electronic declaration.
- Swiss import VAT: 8.1% (or reduced rate depending on goods) calculated on CIF value. Recoverable as input tax if the company is registered for Swiss VAT.
- Certificates of origin: to benefit from the EFTA-EU free trade agreement, goods must be accompanied by a certificate of origin (EUR.1 or origin declaration on invoice). The ERP must store and produce these documents.
- Multi-currency management: transactions between EU entities (EUR) and Swiss entities (CHF) require exchange rate management, conversion differences, and periodic revaluations.
Five common mistakes by international companies in Switzerland
1. Deploying the home country ERP as-is. The French chart of accounts (PCG) is not compatible with the Swiss chart of accounts. VAT codes are different. Billing formats are not the same. A separate instance or tenant with dedicated Swiss localization is required.
2. Ignoring Swiss payroll. Swiss payroll is radically different from other countries: 26 cantonal withholding tax scales, AHV/AI/APG contributions, occupational pension (LPP), accident insurance (LAA/LAAC). No foreign payroll module can be “adapted” — a native Swiss module or specialized provider is required.
3. Forgetting the QR-invoice. Invoices sent to Swiss clients without a QR-invoice section can no longer be paid through standard banking channels. Swiss clients literally return these invoices to the sender.
4. Underestimating multilingualism. Sending a French invoice to a Zurich client or a German invoice to a Geneva client is perceived as unprofessional. In cantonal public markets, it’s grounds for elimination.
5. Neglecting customs. Goods flows between the EU and Switzerland are not intra-community deliveries. The absence of customs declarations exposes the company to FOCBS penalties and goods blocking at the border.
Checklist: choosing an ERP for Switzerland
| Criteria | Abacus | Bexio | Klara | SAP | Odoo |
|---|---|---|---|---|---|
| 3-rate VAT | Native | Native | Native | Via localization | Via l10n_ch |
| QR-invoice | Native | Native | Native | Via partner | Via module |
| Swiss payroll | Complete | No | No | Via CH module | Non-standard |
| Multilingual DE/FR/IT | DE/FR | DE/FR | DE/FR | DE/FR/IT/EN | Multilingual |
| Multi-entity | Yes | No | No | Yes | Yes |
| Customs/export | Partial | No | No | Complete | Via module |
| Typical annual budget | CHF 15-80K | CHF 420-2K | Free-CHF 500 | CHF 80-300K | CHF 20-60K |
For a Swiss subsidiary of an international group, two strategies are viable:
- Local Swiss ERP (Abacus or Bexio) connected to the group ERP via API or middleware. Advantage: native compliance, rapid deployment. Disadvantage: one more system to maintain.
- Group ERP extension (SAP, Odoo) with Swiss localization. Advantage: simplified consolidation. Disadvantage: localization cost, dependence on Swiss partners, regulatory lag risk.
The choice depends on the subsidiary’s size, Swiss transaction volume, and the importance of group consolidation. For a subsidiary of fewer than 30 people, Bexio connected to the central system is often the fastest and least risky solution. For an industrial subsidiary of 100+ people with complex payroll, Abacus or SAP with Swiss localization are better suited.
Before deciding, consult guides on ERP migration and the total cost of ownership of an ERP to frame your budget and timeline.
