ISO20022 SWIFT CBPR+ update

In 2018, SWIFT launched the Cross-Border Payment & Reporting+ (CBPR+) program which aims at migrating the existing MT 1XX, 2XX, 9XX flows in the interbank space to MX/XML format, which is already used in the SEPA world today. All MT payment, reporting, investigation and other formats needed to be migrated to MX PACS, CAMT and PAIN formats. SWIFT has opted for a phased approach focusing on the PACS migration first. By 22 November 2025, MT payment instructions like MT103, MT200 and MT202 (COV) need to have migrated to their equivalent PACS formats (PACS.008 and PACS.009 (COV)) on the SWIFT FINplus service.

SWIFT has created a fallback solution for FIs who cannot migrate to MX PACS in time by opting for the SWIFT MT to MX conversion service. Although subject to additional validation rules, FIs can still send MT payment instruction formats and SWIFT can convert this into the PACS message equivalent. This means that banks connected to SWIFT will no longer receive incoming MT payments- related formats as this is no longer allowed. The Swift conversion service is payable and it is not clear for how long it will be made available. ING has been fully MX-ready since November 2025 and does not rely on the Swift conversion service.

SWIFT published in September 2025 an updated roadmap which defines a new end-date for other categories of messages within the scope of CBPR+, like payment initiation, exceptions and statements. The following picture summarises the updated roadmap, and the following sections provide some more details about each milestone.

Please find more information in this Opens in a new tabOpens a pdfCBPR+ roadmap.

*To prevent any repairs or rejections during the processing of your payment instruction messages, please ensure adherence to the SWIFT formatting guidance and the ING formatting recommendations.
 

According to the Swift CBPR+ guidance, one of the message types to be discontinued by 14 November 2026, is the interbank MT101 request-for-transfer message. ING will initiate a migration program to ensure that FI counterparties in scope of the above-mentioned guidance are migrated to the ISO 20022 MX CBPR+ pain.001.001.09 interbank message before the deadline.   

ING will comply with and adhere to the Swift Rulebook for Payment Initiation Relay (“Rulebook”) in its most recent applicable and published version, as updated from time to time. The Rulebook can be found on the Opens in a new tabSwift’s Document Centre.

Interbank payment initiation message flow has been set up between ING and financial institutions to support the following flows:

1. To initiate credit transfers via ING channels for the execution at your financial institution (debtor agent). In this case an ING entity acts as the forwarding agent.
2. To authorise an ING entity to execute credit transfers received from your financial institution (forwarding agent). In this case, an ING entity acts as the debtor agent.

Interbank Payment Initiation migration to new structured messages format will be initiated:

• In compliance with the ING interbank formats as described in Swift MyStandards, in the ING group Usage Guidelines - Interbank Payment Initiation Guidelines - CBPR+
• Subject to successful message format testing
• Subject to an interbank arrangement between ING and your financial institution. Prerequisites include:

• The accession to the Rulebook
• Communication of ING Code of Conduct (document to be shared from ING side, no signature required)
• RMAs in FINplus setup

When enabling PAIN format connection (per BIC 11), the existing FINplus RMA needs to be updated. ING is not yet ready to onboard the PAIN format in production. However, we can support basic testing in UAT. Please reach out to your ING Relationship Manager if you are interested in testing our PAIN format functionalities.

More information on above topics can be found Opens in a new tabhere.

The following guidelines on scoping can be found on swift.com:

CBPR+ aims at migrating cross-border payments and cash reporting messages on the Swift network used in the interbank space. This includes all messages exchanged between FIs (Swift Financial type), with Supervised and/or Non-Supervised user categories (SUPE and NOSU). MT message exchanges in the Swift for Corporates (SCORE) service will continue as they are for the foreseeable future. Closed User Groups operated by non-Swift entities (i.e. Payment Market Infrastructure Closed User Groups) will continue as they are for the foreseeable future. Other categories of MT messages (e.g. MT 3xx, 5xx) won’t be impacted and can therefore still be used after the end of coexistence.

Corporate entities are not subject to the CBPR+ initiative of SWIFT. However, if a question on certain topics/messages arise, please reach out to your ING Relationship Team.

• PACS

ING is fully incoming and outgoing PACS capable and had migrated the vast majority of its outgoing payment traffic to PACS in March 2023 already.
 

• CAMT

CAMT reporting formats – SWIFT has recently updated the timelines for MX CAMT reporting implementation. As of November 2027, it is mandatory to receive CAMT statements from (non) supervised financial institutions (SUPE and NOSU clients). As of November 2028, the MT (FIN)/CAMT (FINplus) coexistence periods ends and CAMT will be the only format allowed for payment reporting.

ING is currently able to offer CAMT MX reporting services to Financial Institutions loro account holders in several of its entities for the intraday and end-of-day reporting. Many of our entities offer an extended like-for-like MX report which means the CAMT contains the same attributes found in the MT report but is enriched with some key additional MX references for convenience (e.g. UETR, E2E ID).

These MX reporting services are available on an opt-in basis and, when enabling CAMT for a client (per BIC), the existing FINplus RMA needs to be updated. We highly advise organising basic testing upfront where reconciliation validation on the client side should be included. Please reach out to your ING Relationship Manager if you are interested in enabling and/or testing our new CAMT services.

More information on ING’s readiness for CAMT can be found in the table below or on the Swift website:
 

See also this Opens in a new tabStandards MT November 2025 – Standards Release Guide. (Swift account needed)