The ISO 20022 deadline of November 2026: a hard cut-off with no transition period left
For years, «ISO 20022» has been the kind of technical acronym a Swiss business owner could safely leave to the bank and the accounting software. That comfort is about to end. From mid-November 2026, banks in Switzerland will categorically reject payment orders that do not comply with the ISO 20022 standard, including any that still carry unstructured addresses. What has been a gentle migration since the Swiss QR-bill replaced the orange payment slip is turning into a firm cut-off. If your accounting or payroll software still produces old-format files, your outgoing payments will simply stop going through.
The good news for Swiss SMEs: this is entirely manageable, and for most it is a configuration matter rather than a project. But it needs to be checked now, not discovered on the day a supplier payment run bounces back.
What ISO 20022 actually is, in plain terms
ISO 20022 is the common language Swiss banks use for payment traffic. In practice it rests on a few standardised files that flow between your software and your bank:
- pain.001 is the outgoing payment order. This is the file your software generates when you pay suppliers, salaries or expense claims in a batch.
- camt.053 / camt.054 are the bank statement and the credit/debit advices that come back, allowing automatic reconciliation in your books.
- The Swiss QR-bill sits inside the same ecosystem and carries the structured payment data your customers scan to pay you.
When these pieces are correctly configured, money moves and reconciles with almost no manual entry. That is the whole point of the standard: fewer keystrokes, fewer errors, faster cash. It is the same logic that drives the wider digitalisation of SME finance, as we covered in our guide to supplier invoice management with Odoo.
The real change behind the deadline: structured addresses
The heart of the 2026 deadline is not the file format itself, which most software already handles, but the way addresses are encoded. Since 21 November 2025, addresses in the Swiss QR Code must be structured (type «S»): each element of an address, the street, house number, postal code, town and country, has to be stored in its own separate field rather than as one free-text block.
A transition period has applied since then, but it closes for good. From 14 November 2026 at the latest, payments containing unstructured (combined) addresses will be refused by the banks. Some institutions move even earlier: the Banque Cantonale de Fribourg, for example, will reject any payment order that is not ISO 20022-compliant from 2 November 2026.
For your business this has two sides. On the paying side, the master data of your suppliers and employees must carry properly split addresses. On the billing side, the QR-bills you issue to customers must be generated with structured addresses, or your clients' banks may reject them.
This is general information on a regulatory and banking evolution, not individual advice. Exact cut-off dates and technical requirements vary by bank; we recommend confirming the timeline with your own institution and having your setup reviewed.
What the ISO 20022 migration means for your accounting software
The migration touches every tool that generates or imports payment files: accounting, payroll and invoicing. Concretely, your system needs to be able to:
- generate outgoing payment files in the pain.001 format, with structured addresses;
- import bank statements automatically (camt.053) and post credit/debit advices to the right accounts;
- issue Swiss QR-bills with type «S» structured addresses on the customer side.
If you run a modern, well-configured ERP, most of this is already built in. In Odoo, for instance, ISO 20022 payments are handled natively, and recent versions have refined the batch-payment logic further, letting you set the charge bearer and even the instruction priority per individual payment inside a pain.001 file. As an official Odoo accounting partner, we see that the work is less about acquiring new technology and more about verifying that your data and settings are clean before the deadline.
Your ISO 20022 checklist to close before mid-November 2026
Rather than wait for a rejected payment run, walk through these points now:
- Confirm with your bank its exact ISO 20022 cut-off date, since some are ahead of the 14 November 2026 backstop.
- Check that your accounting and payroll software generates pain.001 files with structured addresses.
- Clean up your supplier and employee master data so that every address is split into separate fields.
- Verify that the QR-bills you send to customers use structured (type «S») addresses.
- Run a test payment batch and a test statement import well before the deadline, not on it.
None of these steps is heavy on its own. Together they are the difference between a November where nothing changes for you and one where your supplier and salary payments quietly stop clearing.
Turning a compliance deadline into a cash-flow advantage
It is easy to see ISO 20022 as one more regulatory chore. Seen differently, it is the moment your payment and reconciliation workflow finally becomes fully automated: outgoing payments generated in one click, bank statements posted without manual entry, QR-bills that reconcile themselves. The Swiss SMEs that treat November 2026 as a prompt to tidy their financial plumbing will come out of it faster and less error-prone, not merely compliant.
Frequently asked questions about the ISO 20022 deadline
When exactly is the ISO 20022 deadline in Switzerland?
Unstructured addresses in payments will be refused from 14 November 2026 at the latest, and some banks apply an ISO 20022 cut-off a little earlier. Confirm the precise date with your own institution.
What is a structured address (type «S»)?
It is an address where the street, house number, postal code, town and country are each stored in a separate field, rather than combined into a single free-text line.
Does my business need to change software?
Usually not. Most modern accounting tools, including Odoo, already support pain.001 and structured addresses. The task is to verify your configuration and clean your master data before the deadline.
Not sure your setup is ready for November 2026?
At DHAC, we review your payment and reconciliation flow end to end, checking your pain.001 configuration, cleaning up structured addresses, testing your batch runs and QR-bill output, and, where it helps, connecting it all inside Odoo so the whole cycle runs automatically. As an official Odoo partner combining Swiss accounting precision with digital tools, we make sure the deadline becomes a non-event for you. Book a first free, no-obligation consultation and leave with a clear picture of where you stand.
Sources
Swiss Payment Standards and QR-bill implementation guidelines, SIX Group. Payment standards and ISO 20022 migration for businesses, Banque Cantonale de Fribourg.