Kept up to date

camt v04 → v08: what changes in November 2026

In November 2026, Swiss banks stop sending camt.052, camt.053 and camt.054 files in the 2009 version 04 and deliver only the 2019 version 08. The information stays the same, but several elements move: software that reads only the old version loses the bookings’ status and the payers’ names. Here are the dates, the changes element by element, and what to check.

· 3 min read
Share

In short

  • Swiss banks send only version 08 (ISO 20022 2019) of camt.052, camt.053 and camt.054 files from 14 November 2026 (the 13th at Zürcher Kantonalbank).
  • The same day, pain.001.001.03 payment files are refused: your software must produce pain.001.001.09, with structured addresses.
  • In the camt file, the status moves into <Sts><Cd>, the parties into <Pty>, and a UETR reference appears. Amounts, balances, transaction codes and the QR reference stay where they were.
  • There is usually nothing to do at the bank: it switches the delivery itself. The exception is PostFinance, where customers make the switch themselves in E-Finance before 14 November 2026. Either way, it is your software that needs checking.
  • To see which version you receive today, open a file in the free camt reader.

Not legal advice. This guide summarises the standards published by SIX and the banks’ notices on the date shown. The date and the terms that apply to you are your bank’s.

On this page
  1. The dates
  2. What changes in the camt file
  3. Is your software ready?
  4. And the payment files?
  5. In Filetable
  6. Frequently asked questions
  7. Official sources

The dates

Since November 2022, the Swiss financial centre has delivered ISO 20022 files in two versions side by side: the 2009 one, whose camt messages are numbered .04, and the 2019 one, numbered .08. The Swiss Payment Standards 2026, published by SIX, end this parallel phase: they take effect on 14 November 2026, and the SIC interbank platform releases its new version on 13 November 2026.

PostFinance
Version 08 only from
14 November 2026
Then
Every ISO delivery must be on the 2019 version; customers switch themselves in E-Finance
Migros Bank
Version 08 only from
14 November 2026
Then
Automatic switch to version 08, earlier on request
Graubündner Kantonalbank
Version 08 only from
14 November 2026
Then
Automatic switch to version 08, earlier on request
Zürcher Kantonalbank
Version 08 only from
13 November 2026
Then
Automatic switch to version 08 in mid-November, earlier on request
The switch to the 2019 version, as the banks announce it.

For another bank, the date is the one it announces. They all follow SIX’s calendar: the 2009 version is no longer supported after mid-November 2026.

What changes in the camt file

The statement holds the same information: the account, the balances, the bookings and their details. Some paths in the XML change, and that is where software written for version 04 goes wrong without necessarily stopping: it reads an empty status or no longer finds the payer’s name.

Message version
Version 04
camt.053.001.04
Version 08
camt.053.001.08, in the file’s namespace
Booking status
Version 04
<Sts>BOOK</Sts>
Version 08
<Sts><Cd>BOOK</Cd></Sts>
Debtor, creditor and ultimate parties
Version 04
<Dbtr><Nm>…</Nm></Dbtr>
Version 08
<Dbtr><Pty><Nm>…</Nm></Pty></Dbtr>
Unique end-to-end transaction reference (UETR)
Version 04
Absent
Version 08
<Refs><UETR> in each transaction’s details
Account currency
Version 04
Absent at PostFinance
Version 08
<Acct><Ccy>
Reporting source
Version 04
<RptgSrc>
Version 08
No longer used
Group header’s additional information
Version 04
SPS/1.7/PROD
Version 08
The guidelines’ version, such as SPS/2.0/PROD
The differences PostFinance lists between the old version and the 2019 one.

The same booking, a credit of CHF 250.35, in both versions:

camt.053.001.04
<Ntry>  <Amt Ccy="CHF">250.35</Amt>  <CdtDbtInd>CRDT</CdtDbtInd>  <Sts>BOOK</Sts>  <NtryDtls><TxDtls>    <RltdPties>      <Dbtr><Nm>Muster AG</Nm></Dbtr>    </RltdPties>  </TxDtls></NtryDtls></Ntry>
camt.053.001.08
<Ntry>  <Amt Ccy="CHF">250.35</Amt>  <CdtDbtInd>CRDT</CdtDbtInd>  <Sts><Cd>BOOK</Cd></Sts>  <NtryDtls><TxDtls>    <Refs><UETR>6f1e2b3c-4d5e-4f60-8a1b-2c3d4e5f6a7b</UETR></Refs>    <RltdPties>      <Dbtr><Pty><Nm>Muster AG</Nm></Pty></Dbtr>    </RltdPties>  </TxDtls></NtryDtls></Ntry>

Is your software ready?

  1. Look at the version of the files you receive now. Open a recent statement in the camt reader: it says whether it is version 04 or 08, and shows the bookings as software should read them.
  2. Ask your software vendor whether it reads camt.053.001.08 and camt.054.001.08, and whether it produces pain.001.001.09. A recent release usually does; a custom program needs checking.
  3. Test before the date. Most banks deliver version 08 on request already. PostFinance lets you switch the version yourself in E-Finance, and switch back if needed.
  4. Have the software read one file of each kind you receive: the end-of-day statement (camt.053) and, if you use them, the QR-bill credit notifications and batch bookings (camt.054).

If you write the code that reads the files yourself, the two changes that break reading are the status, to read in Sts/Cd, and the parties, to read in Dbtr/Pty and Cdtr/Pty. A robust reader accepts both forms during the transition: ours does.

And the payment files?

The payment orders your software sends to the bank change the same day. The pain.001.001.03 file is no longer accepted: it must be pain.001.001.09. Status reports move from pain.002.001.03 to pain.002.001.10.

With the new version, the Swiss Payment Standards require structured or hybrid addresses for every party: the town (TwnNm) and the country (Ctry) always in their own elements. SIX leaves banks free to keep accepting unstructured addresses, but some refuse them from 14 November 2026, Migros Bank for one. The safe course is to store your suppliers’ addresses in structured form now.

pain.001.001.09, structured address
<Cdtr>  <Nm>Muster AG</Nm>  <PstlAdr>    <StrtNm>Bahnhofstrasse</StrtNm>    <BldgNb>1</BldgNb>    <PstCd>8001</PstCd>    <TwnNm>Zürich</TwnNm>    <Ctry>CH</Ctry>  </PstlAdr></Cdtr>

In Filetable

In Filetable, a camt.053 statement imports into a table, then each booking is matched to its invoice by your rules: you check only what is left. The camt reader is free and needs no account: the file is read in your browser and sent nowhere.

Frequently asked questions

Do I need to do anything at my bank?

Usually not: Migros Bank, Zürcher Kantonalbank and Graubündner Kantonalbank switch the delivery to version 08 themselves on the date. PostFinance asks that every delivery be switched to the 2019 version before 14 November 2026, which is done in E-Finance. Either way, it is your software that needs checking.

What is the exact date?

SIX’s Swiss Payment Standards 2026 take effect on 14 November 2026, the date PostFinance, Migros Bank and Graubündner Kantonalbank give. Zürcher Kantonalbank announces 13 November 2026, the day of the SIC platform release. The date that counts is your bank’s.

How do I know which version my statements are in?

Open a file in the camt reader, or search the file for the text camt.053.001.: the ending, 04 or 08, gives the version.

Does the QR reference of QR-bills change?

No. The QR reference stays in RmtInf/Strd/CdtrRefInf/Ref, of type QRR, and the ISO 11649 creditor reference of type SCOR. What changes around it is the booking’s status and the element that wraps the payer’s name.

Is the MT940 statement going away too?

Not yet. The MT940, the MT942 and the MT101 order have no fixed end date, according to Zürcher Kantonalbank. It still advises moving to camt files: SIX develops the standards further only in their 2019 version.

Official sources

Every rule in this guide is read from these texts, as published on Fedlex, the Confederation's official collection of laws. .

In the product

Bring your documents. Build your workspace.

Create your workspace in a few minutes, upload a first batch and watch it organize itself.

Invoices
Bank statements
Contracts
Payslips
Receipts
Orders
Delivery notes
Quotes

Your cookies, your choice

We use a few cookies to run the site and, with your consent, Google Analytics (audience measurement). Nothing starts until you choose. No advertising measurement, no cross-site tracking. Cookie policy