Information about formats

Swift and the European Payments Council (EPC) have announced that the changes that were scheduled for 15 November 2026 have been postponed.

A new deadline has not yet been established. The postponement gives organizations more time to complete their migration. However, the changes will still be implemented at a later date. We therefore recommend continuing with the migration. By transitioning to ISO 20022 formats in a timely manner and using structured address data where required, you can avoid time pressure and potential risks when new deadlines are announced.

The impact for Rabobank is as follows:

A payment batch is processed as a SEPA Credit Transfer (SCT) by default. For payment instructions in euros, you can also choose an Instant Payment or EuroSelect payment in the pain.001 file.

Instant Payment

For an Instant Payment, include the following fields in the pain.001 file:

Enter the value INST in the Code (Cd) field. The payment is processed 24 hours a day, 7 days a week. The status is available immediately.

Not all banks in the SEPA area support Instant Payments. If a bank cannot process the payment as an Instant Payment, the payment will be rejected. If too many payments are rejected, the entire payment batch will be rejected.

EuroSelect payment

Use a EuroSelect payment in the following situations:

The cut-off time for an SCT is 14:30. Between 14:30 and 15:00, Rabobank processes the payment on a best-effort basis only.

Do you want to submit a payment as a EuroSelect payment? Enter the value URGP in the ServiceLevel (SvcLvl) field.

This page contains general and additional information about changes to payment orders, direct debits and MT940 statements. If you received a message from us about this in May 2026, this information provides further explanation in relation to that message.

For each topic, we have listed the frequently asked questions:

• FAQ – Address requirements

• FAQ – Discontinuation of MT messages

Do you also hold accounts with another bank that you access via Rabobank, or is account information from your Rabobank account forwarded to another bank? In that case, two different deadlines apply: one for you as a customer and one for the banks involved. This document provides a visual explanation with important points to consider. We also recommend contacting the other bank for more information about their planning related to these changes.

If, after consulting the frequently asked questions and/or reading the information on this page, you still have questions or are unsure what these changes mean for you, please contact your regular contact person or support team.

MT messages are being replaced by XML files in accordance with the ISO 20022 standard. For initiation files (payment instructions), this means that the MT101 will be replaced by pain.001. Account and transaction reporting via MT940 and MT942 will be replaced by camt.053 and camt.052 respectively.

As of 15 November 2026, Rabobank will discontinue support for MT formats. We therefore advise you to switch to XML files. Our recommendation is to use the 2019 versions, which are pain.001.001.09, camt.052.001.08, and camt.053.001.08.

Are you already using XML? Then you are not required to move to the 2019 version. The 2009 versions (pain.001.001.03, camt.052.001.02, and camt.053.001.02) will remain supported at least until November 2029. Another option is to use an accounting software connection, provided your accounting package supports this.

Impact on Your Organization

The impact of this change depends on the messages your organization currently uses. There are three scenarios:

1. Does your organization already use a Rabobank accounting integration or XML files based on the ISO 20022 standard from 2019? Then you don’t need to do anything!
2. Does your organization currently use XML files based on the ISO 20022 standard from 2009? Then we recommend switching to the most recent ISO standard (2019). It is also possible to continue using the 2009 standard, provided you ensure addresses are included in a structured format.
3. Does your organization still use MT messages? Then migrate to an accounting integration or an XML format. In the latter case, the best option is the 2019 version.

These changes will require time and effort. Rabobank advises you to quickly check which version(s) of the ISO standard your accounting solution supports. Based on that, you can start working on the desired scenario in time.

For Europayments, address details are optional. However, if you include them after 15 November 2026, they must at least contain the city and country; the remaining address fields may be structured or unstructured.

For Worldpayments, it is already mandatory to include the address details of both the payer and the beneficiary. From 15 November 2026 onwards, these addresses must at minimum include the city and country, and any additional address fields must also be structured. In addition, extra requirements may apply for specific countries and banks. You can find the country specific exceptions here (Dutch only).

If you would like detailed information about the requirements for addresses, please read the following document.

This file format is based on the ISO 20022 standard of 2019. This type of MX message is now also suitable for all types of payment instructions:

This file format is based on the ISO 20022 standard of 2009. This type of MX message is suitable for all types of payment orders:

This file format is based on the ISO 20022 standard of 2019. This file can only be used for direct debits within the Eurozone (SEPA Direct Debits).

The pain.002 version 10 includes two variants:

Compared to previous versions, this pain.002 has been extended with new statuses. In addition to the existing status codes, this version provides more detailed feedback on the processing of batches and payment instructions.

This file format is based on the ISO 20022 standard of 2009.

A pain.002 file can be used to provide information about accepted and processed batches. This can only be done for SEPA payments via the RDC/SWIFT Fileact channel. In this application, the format is referred to as a 'positive pain'.

A pain.002 file can also be used to indicate which transactions in a file with payments or direct debits will be rejected for a technical or functional reason. In this scenario, the format is called a ‘negative pain’.

With this file, you know before the execution date which transactions will be rejected. Unlike the positive pain, the negative pain provides status information about almost all types of payments:

This file format is based on the ISO 20022 standard of 2019. The camt.052 contains information about the bookings made on the account during the current day (intraday).

In Rabo Business Banking (RBB) this format is available per 14th August 2025.

This file format is based on the ISO 20022 standard of 2009. The camt.052 contains information about the bookings made on the account during the current day (intraday).

Please see “Other Formats” for Transaction type codes.

This file format is based on the ISO 20022 standard of 2019. The camt.053 contains information about the bookings and balance on the account over closed book days (end of day or EOD).

In Rabo Business Banking (RBB) this format is available per 1st July 2025.

This file format is based on the ISO 20022 standard of 2009. The camt.053 contains information about the bookings and balance on the account over closed book days (end of day or EOD).

Please see “Other Formats” for Transaction type codes.

This format contains information about the bookings made on the account (both end of day and intra-day). A CSV file is a fairly simple format that is relatively easy to import into Excel. CSV is less suitable for use in combination with a professional accounting solution. We recommend choosing an automated link between the bank and the accounting package. Manual import of transactions is best done with camt.053 files.

This format contains an overview of transactions of credit cards which were issued from February 12, 2020.

This concerns CSV-files from other applications, which you can use to import data into the 'Payment address book' of Rabo Business Banking. We provide the following tips:

This format contains an overview of the costs regarding business payment transactions.

This document provides an overview of the transaction type codes used in the MT940/942 and camt.052/053 download formats. The same overview is also available via Rabobank's public MyStandards portal as part of the camt format specifications.

This format is based on the ISO 20022 standard en is suitable for SEPA Direct Debit and SEPA Credit Transfer.