What an ERP has to handle in Switzerland
The points below decide whether a system is usable in Switzerland. We list them so you can assess any offer against them — ours included. And because the question always comes: below is where each topic actually stands with us, including what is not finished yet.
VAT: method, rates, returns
Liability starts at CHF 100,000 of worldwide turnover. From there, the choice between the effective method and flat tax rates, with a standard rate of 8.1%, a reduced rate of 2.6% and a special rate of 3.8% for accommodation. An ERP has to handle both methods, derive the return from the underlying documents, and treat acquisition tax on foreign services correctly.
Accounting under the Code of Obligations
Chart of accounts, journal, closing and retention under the CO — records and books traceable for ten years. For groups, additionally: keep several entities separate while still consolidating for reporting.
QR-bill
Since October 2022 the QR-bill is the payment standard; payment slips are gone. In practice: invoices carrying the Swiss QR Code, a reference depending on the bank relationship, and on receipt automatic matching via that reference instead of hunting through statements.
eBill and payment traffic
Invoices delivered straight into the customer’s e-banking, payment orders and statements in ISO 20022 format. The value is not in sending but in reconciliation: open items that close without manual rework.
Payroll and social insurance
Payroll runs, OASI/AHV, accident and daily-sickness insurance, withholding tax, salary certificates, and the electronic declaration to the compensation office. If payroll does not live in the ERP, it needs at minimum a clean interface into accounting.
Multi-currency and languages
CHF as the accounting currency, EUR in sales or purchasing, exchange differences at closing. And the daily reality: customer documents in German, French or Italian out of the same system.
Where we stand today
| Topic | Status |
|---|---|
| Swiss QR-bill Exists as a plugin and works; activated per tenant. | available |
| VAT (MWST) returns Specified against the official FTA forms (rates 8.1% / 2.6% / 3.8%, effective method and flat rates). | in progress |
| Accounting under the Code of Obligations (Swiss chart of accounts) The Swiss ledger is being built on a test tenant. | in progress |
| Multi-currency CHF / EUR Present in the model; we show where it stands for your case in the demo. | partial |
| eBill Not implemented yet. | planned |
| Payroll and Swissdec declarations Not implemented yet; today through an interface to the payroll system. | planned |
Status: August 2026. We also write down what is missing — the vendor who can do everything is usually the one who explains it later.
Frequently asked questions
Is AgReSy a Swiss product?
The product is developed by a team in Romania; the contracting party for Swiss customers is a group company in the canton of Zug. Contract, CHF invoicing and your point of contact therefore stay in Switzerland.
Can the data stay in Switzerland?
Yes. The platform can be operated in a private environment or on-premise, which includes a Swiss data centre. It is an operating model, not an add-on module.
How long does an implementation take?
It depends on how many processes are modelled and on the state of the legacy data. Because the system is configured rather than programmed, the first productive area is usually reached in weeks rather than quarters. We commit to a date only after the process discussion.
What does AgReSy cost for an SME with 20 employees?
Licensing is per organisation and by module scope, not per user — adding employees does not automatically increase the licence. The order of magnitude for your case comes from the cost calculator or from a conversation.
Does our fiduciary work inside the system?
Yes, that is the intended setup: the company and the trustee work with different permissions on the same data, instead of sending files between two systems.