Information about formats

From November 2025, Swift will require banks to gradually replace MT messages with MX messages. The MT101 (for initiation) will be replaced by pain.001; the MT940 and MT942 will be replaced by camt.053 and camt.052, respectively. Swift also requires that MX messages comply with the ISO 20022 standard of 2019. The new standard contains more details, more flexibility, and is more richly structured. This offers new opportunities for reporting, compliance, and automation.

Rabobank already supports the latest pain messages, but camt messages are still in accordance with the 2009 standard. Rabobank's ambition is to be fully ready to receive and send the current MX files by the second quarter of 2025.

In consultation with market parties, the bank will determine an appropriate end date for the support of MT messages. This end date is of course important for Financial Institutions, ERP and accounting packages, and the many thousands of organizations that use our services.

In the last quarter of 2024, detailed format descriptions will be presented on the Swift MyStandards page and summarized on this website. At the beginning of 2025, we will communicate the date on which we will completely phase out MT messages. Do you have questions about this change? Send them to ISO20022@rabobank.nl.

As of March 18, 2024, the new pain format (version 2019) can be used for payment orders. From that date, the new versions of these MX formats for payments and direct debits will be supported via Rabo Business Banking, Rabo Direct Connect, and SWIFT FileAct.

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 type of MX message is suitable for all types of payment orders:

This file format has the same function as pain.001 and will be phased out over time.

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).

This file format is based on the ISO 20022 format of 2009; we expect to offer the 2019 version in the second quarter of 2025. A pain.002 file can be used to provide information about accepted and processed batches. This is only available for SEPA payments via the RDC/SWIFT Fileact channel. In this application, the format is called 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 2009; we expect to offer the 2019 version of this format in the second quarter of 2025. 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 format will be phased out over time. Like the camt.052, the MT942 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 2009; we expect to offer the 2019 version of this format in the second quarter of 2025. 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 will be phased out over time. Like the camt.053, the MT940 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.

In this document, you will find a description of the transaction type codes that are reported in your download formats MT940 and MT942.

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