Electronic invoicing in Switzerland in 2026: QR invoice, archiving, accounting automation and Odoo (SME Guide)

Do you have an SME in Geneva and feel that "electronic invoicing" is a topic that keeps coming up? It's normal. Between QR invoices, PDFs sent by email, eBill, supplier portals, and the ERP promising automation... you can quickly end up with a patched system.

Let me be clear: in 2026, what protects you is not having a nice PDF. It's having a clean, traceable process, properly archived, and able to produce a VAT audit trail without breaking a sweat.

We're talking about Switzerland here (with a very Geneva perspective), SMEs, and Odoo when it makes sense.

Legal obligations and formats for electronic invoicing in Switzerland in 2026

Let's start by busting a myth: in Switzerland, "electronic invoicing" does not mean "a single format imposed on everyone" like in some neighboring countries. What the administration expects is a correct invoice (content), compliant retention (archiving), and traceability (audit trail). The medium (paper, PDF, EDI) is secondary... as long as you follow the rules.

What the law really expects from an invoice (and what puts you at risk)

A valid invoice is first and foremost one that allows you to understand the service and link it to the accounting.

Specifically, for VAT, you must be able to demonstrate:

• who is selling (your company, address, VAT ID if applicable)
• who is buying (client, address; for B2B this is quickly essential)
• what (clear description, not "miscellaneous services" over 12 lines)
• when (invoice date, service period if relevant)
• how much (amounts, discounts, conditions)
• VAT: applied rate (8.1%, 2.6% or 3.8%), taxable base, VAT amount, or exemption mention if applicable

The classic trap in Geneva: service companies invoicing "monthly flat fee" without specifying the period. At closing, you have to link the revenue to the right month, and it becomes an internal debate. Result? Adjustment entries, and sometimes unnecessary discussions during audits.

(source: Fedlex — Swiss VAT legislation (including archiving and digitization))

Electronic invoice: PDF, EDI, eBill... what matters?

In practice, we see four families:

• PDF sent by email: the most common. It works, but only if archiving and audit trail follow.
• Structured invoice (EDI / XML): useful when you have volume, large accounts, or portals that require a format.
• eBill: convenient for certain clients (often individuals, sometimes small structures). It doesn't replace your accounting: it mainly replaces the payment channel.
• Supplier/client portals: you upload or retrieve invoices on a platform. It's "electronic", yes, but it can be a nightmare if no one manages access and exports.

The common point: you must be able to prove the integrity and authenticity of the document, and retrieve it quickly.

QR invoice: mandatory? Yes... but not as you imagine

The QR invoice replaced the old payment slips since 2022. In 2026, if you invoice in Switzerland with a payment slip, it's QR.

Note the nuance: the QR invoice is not "the invoice". It's the payment part (QR code + data) integrated into an invoice.

What it changes for you:

• your bank details (IBAN) must be correct
• the reference (QR or SCOR) must be consistent with your reconciliation process
• if you want to automate, the QR invoice becomes your best ally

(source: QR invoice: end of old payment slips since 2022)

Table — Common formats and recommended usage for Geneva SMEs

Checklist — Is your invoice "clean" for VAT?

• Complete seller identity (company name, address)
• Client identity (at least name + address)
• Invoice date and, if useful, service period
• Clear description of goods/services
• Net amounts, VAT, total incl. VAT
• Correct VAT rate (8.1%, 2.6% or 3.8%) or exemption mention
• Currency indicated (CHF, EUR...)
• Payment terms (due date)
• Consistent payment reference (if QR)

Customer invoicing process: QR invoice, PDF, eBill and Odoo automation

A well-running customer invoicing is not "just click send". It's a chain: data → invoice → sending → payment → reconciliation → reminders → proof.

And that's where SMEs waste time: they have one tool to edit, another to send, a third to track payments... and no one knows which version is authoritative.

QR invoice: reference choice and impact on reconciliation

You have two logics:

• QR reference: widely used when you have a QR-IBAN account and want almost automatic reconciliation.
• SCOR reference: more flexible, often used with standard IBAN.

What we see in practice: companies change logic during the year (new bank, new software) without aligning the reference. Result? Payments arrive, but automatic reconciliation no longer matches. And someone ends up reconciling manually.

(source: Practical guide QR invoice, references, accounting automation)

PDF: the simplest channel... and the trickiest

PDF is perfect if:

• you generate the PDF from your ERP
• you send it from the ERP (or at least log the sending)
• you archive the sent version

The classic trap: "we modify the PDF afterwards". A discount added manually, a line corrected, then resent. You've just created two versions. Which one is archived? Which one is accounted for? During audits, this is visible.

eBill: useful, but keep your internal discipline

eBill can reduce payment friction. Very good.

But keep a simple rule: the accounting invoice is the one issued by your system. eBill is a transmission/payment channel. If you let eBill become "the source", you lose control over invoice numbers, corrections, credit notes.

Odoo: where automation saves time (and where it can trap you)

Odoo can do a lot, but only if your base data is clean.

What works very well in SMEs:

• automatic and sequential numbering
• invoice templates by service type
• standardized payment terms
• automatic reminders (with clear rules)
• assisted bank reconciliation (when references are consistent)

What goes wrong:

• poorly configured items (wrong VAT rates, inconsistent accounting accounts)
• duplicate clients (two records, two addresses, two histories)
• users "patching" an invoice instead of issuing a credit note + re-invoicing

(source: Official Odoo Documentation — Electronic invoicing (EDI))

Step by step — Setting up a clean customer invoicing flow (SME)

1. Clean your client data

• one record = one client
• correct billing address
• billing email (not the salesperson's personal email)

2. Standardize your items/services

• clear labels
• correct product account
• correct VAT rate (8.1%, 2.6% or 3.8%)

3. Set a payment reference rule

• QR or SCOR, but not "depending on mood"

4. Validate an invoice template

• VAT mentions
• payment terms
• bank details

5. Define the validation circuit

• who can issue?
• who can cancel?
• who can issue a credit note?

6. Automate sending and archiving

• sending from ERP
• automatic archiving of the sent version

7. Reconcile payments weekly

• not "when there's time"

8. Remind with a simple logic

• D+5: reminder
• D+15: firm reminder
• D+30: blocking / legal action according to internal policy

Field observation (Geneva): the "gentle" reminder that costs dearly

We often see SMEs that don't dare to remind, especially when the client is "important". They wait 60 days, then get upset.

In our opinion, the best approach remains regular, factual, automated reminders. Not aggressive. Just consistent. The client quickly understands that your accounting is well kept.

Supplier invoices: receipt, integration and automation in the ERP

On the supplier side, the question is not "do I receive a PDF". You will receive them. The real question: how do you avoid manual entry and VAT errors.

The three real channels in SMEs

• PDF by email (comptabilite@…)
• Supplier portal (download)
• Scanned paper invoice (yes, it still exists)

The problem is not the channel. The problem is the lack of rules: who receives, who validates, who pays, who archives.

Integration into the ERP: what you need to capture

For a supplier invoice, you must capture:

• supplier (unique record)
• invoice date / receipt date
• amount and currency
• VAT (rate, amount)
• expense account / cost center if you track
• due date
• payment reference

And above all: the supporting document linked to the entry.

Automation: OCR, rules, and controls that prevent mistakes

Useful automation is:

• automatic reading (OCR) of amounts, dates, VAT
• allocation proposal based on history
• duplicate detection (same supplier + same number + same amount)
• validation workflow (budget manager)

Beware, classic trap: OCR reads "8.1" as "81" on a poorly printed invoice. If you have no control, you account for anything.

Table — Simple controls that prevent 80% of supplier errors

Checklist — "Clean" supplier circuit (without a factory)

• A unique email address for receipt (ex: invoices@)
• A manager per expense type (IT, rent, subcontracting...)
• Two-step validation if amount > CHF 5,000
• Strict rule on IBAN change (call supplier)
• Grouped payments 1 to 2 times per week
• Systematic bank reconciliation
• Automatic archiving of the invoice linked to the entry

Electronic archiving, compliance and audit trail: requirements and best practices

Archiving is the topic everyone postpones. Until the day:

• a client disputes an invoice
• a supplier claims a payment
• or the AFC requests VAT supporting documents

And then, if your documents are in mailboxes, "Downloads" folders, and a NAS without rules... good luck.

What "audit trail" really means

An audit trail is the ability to link:

• an issued/received invoice
• to the accounting entry
• to the payment
• and to the contract/order if necessary

You must be able to reconstruct the story without interpretation.

(source: Fedlex — Swiss VAT legislation (including archiving and digitization))

Retention duration and quality: don't try to outsmart

In Switzerland, retention of accounting documents and supporting documents is long-term. The point is not just "keep a PDF". It's keeping:

• a file readable over time
• with a filing structure
• with access rights
• with traceability of modifications

What we recommend in practice:

• PDF/A when possible
• standard naming (date_supplier_number_amount)
• indexing in the ERP (attachment linked to the entry)
• tested backups (not just "we have a backup")

Field anecdote: the audit at the worst time

A Geneva SME (services, 12 employees) receives a request for VAT supporting documents over an 18-month period. The internal accountant had "everything"... in their Outlook mailbox, sorted by folders.

Except in the meantime, Microsoft 365 migration, folders partially lost, and two employees left.

We ended up reconstructing the documents via suppliers, bank statements, and exports. Feasible, yes. Pleasant, no. And above all: billable time wasted.

Best archiving practices when using Odoo

If you use Odoo (or a similar ERP), the healthiest approach:

• each invoice (client/supplier) has its attachment in the ERP
• each payment is reconciled and visible
• accounting exports are locked by period (locking)
• user rights are limited (not everyone modifies everything)

And you keep a rule: no accounting entry without supporting document (except purely internal entries documented).

(source: Odoo in Switzerland: QR invoice, CAMT, bank reconciliation and error control (Ark Fiduciaire Article 2026))

3 decisions that change everything (and that we settle in meetings)

You want a system that works? You need to settle three topics. Not postpone them.

1) Who is "master" of the invoice: ERP or Word/Excel?

If your salespeople make quotes in Word and accounting redoes the invoice in the ERP, you pay twice.

Decision: quotes and invoices come from the same tool, period.

2) Payment reference: consistency or patchwork

If you change reference depending on the client, you kill reconciliation.

Decision: one rule, documented, applied.

3) Archiving: ERP, DMS, or shared folders?

Shared folders "can work"... until someone renames, deletes, or duplicates.

Decision: an archiving system with indexing and rights. Often the ERP is enough for an SME, sometimes a DMS is justified.

Practical case (Geneva) — Automate invoicing and reduce unpaid invoices

Geneva SME, 9 employees, IT B2B services.

• 120 client invoices per month
• average basket: CHF 1,450
• terms: 30 days
• payments: bank transfers
• previous tool: PDF invoices made in an editor + Excel tracking

Situation before

• Monthly time for invoicing + tracking: 18 hours
• Monthly time for bank reconciliation: 10 hours
• Unpaid > 60 days: CHF 38,000 on average
• Recurring errors: missing payment references, invoices resent "not received", poorly tracked credit notes

Implementation (simple process)

• Invoices issued from ERP with QR invoice
• Unique reference per invoice
• Sending from ERP (sending trace)
• Weekly bank reconciliation
• Automatic reminders at D+5 and D+15

Result after 3 months

• Monthly time for invoicing + tracking: 8 hours
• Monthly time for bank reconciliation: 3 hours
• Unpaid > 60 days: CHF 14,500

The gain is not magic. It comes from a basic thing: stop chasing information.

Section "frequent errors" + corrections (the ones we see all the time)

Error 1 — Invoice sent, then modified without trace

Symptom: the client has one version, you another.

Correction: you issue a credit note and a new invoice. Yes, it's cleaner. And yes, it saves you in case of dispute.

Error 2 — VAT at the wrong rate on mixed services

Symptom: an invoice mixes lines at 8.1% and 2.6%, but everything is at the same rate "for convenience".

Correction: item setup and control at issuance. If you sell goods and services, you must separate.

Error 3 — Inconsistent payment references

Symptom: unreconciled payments, reminders sent to clients who have paid.

Correction: a reference rule, and regular bank reconciliation. If you wait 2 months, you lose the benefit.

Error 4 — Supplier invoices paid without validation

Symptom: "we paid, we'll see later". Then you discover an erroneous invoice.

Correction: simple workflow: mandatory validation before payment, and IBAN change control.

Error 5 — Archiving in the mailbox

Symptom: when the person leaves, the history leaves with them.

Correction: centralized archiving linked to the accounting entry. The mailbox is for receiving, not for storing.

Internal controls: the minimum viable to sleep well

You don't need an 80-page manual. You need short, applied rules.

Sales side controls

• locked sequential numbering
• VAT rate validation by item type
• mandatory credit note in case of correction
• automatic reminders with documented exceptions

Purchase side controls

• duplicate detection
• two-level validation above a threshold
• IBAN control
• weekly bank reconciliation

Cross control

• monthly closing with period locking
• journal export and backup

Odoo in SMEs: concrete settings we fix from the start

Here are the topics that avoid 80% of "it doesn't work" tickets.

Chart of accounts, taxes, and products

• consistent product/expense accounts
• taxes configured by default on items
• documented exceptions (export, exemptions, etc.)

Sequences and journals

• one sequence per document type (invoice, credit note)
• separate journals if you have multiple entities

Bank reconciliation and bank files

Reconciliation becomes really effective when:

• your invoices have clean references
• you import structured statements
• you handle exceptions weekly

(source: Odoo in Switzerland: QR invoice, CAMT, bank reconciliation and error control (Ark Fiduciaire Article 2026))

Documents to prepare if you want to switch to "proper" invoicing in 30 days

Want to move fast? Prepare this before touching the setup.

• client list (legal name, address, billing email)
• supplier list (name, IBAN, email)
• standard payment terms
• invoice template (mentions, logo, details)
• list of items/services with VAT rate
• validation rules (who validates what)
• reminder policy (timing, tone, exceptions)

FAQ on electronic invoicing, QR invoice and accounting automation (Switzerland, France, SMEs, individuals, Odoo, free tools, 2026 obligations)

1) Is electronic invoicing mandatory in Switzerland in 2026?

For most SMEs, the obligation is mainly about content compliance, retention and traceability. You can invoice in PDF, EDI, via portal, as long as the invoice is correct and properly archived. Requirements may vary depending on your clients (large accounts, public sector) who sometimes impose a format.

(source: Fedlex — Swiss VAT legislation (including archiving and digitization))

2) Is the QR invoice mandatory for all payments?

If you use a payment slip in Switzerland, it's QR. If you invoice without a slip (for example, transfer with IBAN and free reference), you can technically do without, but you often lose in automation and reconciliation quality.

(source: QR invoice: end of old payment slips since 2022)

3) PDF by email: is it considered a valid electronic invoice?

Yes, if the document contains the necessary mentions and if you archive it in a compliant way, with an audit trail. The problem is not the PDF. The problem is the PDF that's missing, modified, or not linked to the entry.

4) Is Odoo enough to manage QR invoice, bank reconciliation and automation?

Often yes for an SME, provided you correctly set up taxes, sequences, journals, and have discipline on payment references and workflows. If you have complex EDI requirements or multiple portals, sometimes connectors are added.

(source: Official Odoo Documentation — Electronic invoicing (EDI))

5) I have clients in France: do I need to issue a French format?

It depends on your contractual relationship and client requirements. Many French clients accept a PDF, some require a structured format via their platform. In practice, we often manage two flows: Switzerland (QR + PDF) and export (PDF/EDI as requested). Keep a rule: your accounting must remain consistent and archived in the same place.

6) Are there free tools to create QR invoices?

Yes, there are generators and banking solutions. Handy. But if you have volume, the real cost is not QR editing: it's tracking, reconciliation, archiving, and corrections. A free tool that forces you to re-enter in accounting costs you more than you realize.

(source: Practical guide QR invoice, references, accounting automation)

References

• Practical guide QR invoice, references, accounting automation
• Official Odoo Documentation — Electronic invoicing (EDI)
• Fedlex — Swiss VAT legislation (including archiving and digitization)
• Odoo in Switzerland: QR invoice, CAMT, bank reconciliation and error control (Ark Fiduciaire Article 2026)
• QR invoice: end of old payment slips since 2022