Solution
The Swiss invoicing chain
Swiss invoicing rests on formats that change on announced dates: QR-bill, ISO 20022, structured address. A homegrown tool still producing the old format stops the day the bank stops accepting it.
The invoice, from quote to reconciliation
Format deadlines are met
QR-bill versions and payment schemas have published cut-over dates. They are tracked and applied before the date, not after the first rejection.
Reconciliation happens on its own
The reference carried by the invoice comes back in the bank statement. The payment attaches to the invoice, with no manual comparison of two screens.
Addresses are clean before sending
The structured address no longer accepts a free-text line. The check happens at entry rather than when the bank sends the file back.
Reminders go out without being remembered
Due dates tracked, reminders drafted, and the decision to send stays yours. A late payment shows up within the week rather than the quarter.
In practice
- QR-bills generated at the version in force, with the structured address checked at entry
- Payment and direct-debit files on the current ISO 20022 schema, validated before submission
- Bank statements taken in automatically, with reconciliation by reference
- Reconciliation gaps presented for a decision, rather than settled silently
- Due dates tracked and reminders drafted, with sending left as a human decision
- Entries pushed to accounting, in the format it already accepts
Systems involved
- Swiss banks, by file or over a direct banking channel
- Bexio, Abacus, Sage and other accounting packages
- ERP and line-of-business software, over APIs or exchange files
- Electronic invoicing portals
- Your sales system, when the invoice is already born there
Service lineApplications and integration →
Which flows
The same work, against each sector’s own constraints. Every card opens the full sector.
Logistics and supply chain
Freight invoicing
QR-bill at the version in force, payment files on the current schema and reconciliation by reference, at volumes beyond manual checking.
Retail and e-commerce
Invoicing and collection
QR-bill at the version in force, structured addresses checked at entry, and the payment attached to the invoice without comparing two screens.
How it runs
Current state
What produces an invoice at present, in which format, and what the bank already rejects silently.
Issuing
QR-bill at the version in force, addresses checked, and a test batch run past the bank before anything real goes out.
Collection
Statements taken in, references reconciled, and the gaps raised with someone rather than absorbed.
Format watch
Published cut-over dates are tracked, and the change is applied ahead of the deadline rather than at the first incident.
Dependencies and next steps
Test the fit: The Swiss invoicing chain
Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.
Describe the situation