Table of contents
ISO 20022 for Corporates
Why is Swift focusing on corporates adopting ISO 20022?
One of Swift’s priorities is extending the rich data across the payment chain. This will help banks and corporates streamline their cross-border payments by maintaining data integrity end to end, leading to improved reconciliation, better forecasting of payment flows and improved working capital management.
By making our new FINplus service available to the corporate community, we’ve now introduced a payment instruction and cash reporting standard for corporates enabling them to reap the rewards of ISO 20022.
How does ISO 20022 improve treasury processes?
ISO 20022 helps to reduce payment friction, streamline reconciliation by using structured remittance information, increase the accuracy of cash flow forecasting, and improve working capital through richer and structured data that allows forecasting future inbound and outbound payment flows.
Use cases can be found in our ebook "Supercharge your payments business with ISO 20022". The use case "Strengthen corporate treasury activities" goes into corporates specifically.
Can corporates and banks that are part of SCORE exchange ISO 20022 messages?
Swift is setting the richer ISO 20022 data standard end-to-end, and supporting with communication channels and complementary services as part of the evolution of the SCORE offering to ensure high-quality data capture and delivery.. The introduction of SCORE+ enables ISO 20022 payment exchanges within the SCORE framework. In practice, this means that beyond the existing SCORE-supported channels, such as FIN and FileAct, SCORE+ allows users to exchange ISO 20022 payments over FINplus. Migrating FIN flows to FINplus allows corporates and banks to benefit from network validation and will benefit from orchestration provided by the Transaction Manager in the future.
Payment initiation (pain.001, pain.002) and cash reporting (camt.052, camt.053 and camt.054) are live and available, and Payment Cancellation (camt.059 and camt.029) will be available from November 2026. The exchange of the ISO 20022 messages between SCORE participants is subject to a specific RMA.
Can corporates and banks in MA-CUGs exchange ISO 20022 messages?
Under the CBPR+ scope, all payment instructions exchanged with SUPE and NOSU now use ISO 20022, as the migration deadline was November 2025. Traffic within MA-CUGs was also subject to this requirement.
Exceptions remain:
- Users of SCORE - corporates and banks can continue to send and receive MTs such as MT 101, MT940 and MT942 after November 2025 within the SCORE service.
- Members of MI-CUGs (Market Infrastructure CUGs administered by customers) can continue to send and receive MTs such as the MT 103 and MT 202 after November 2025. These MI-CUGs will migrate when customers decide.
For information on how to access if your traffic must be migrated to CBPR+ visit our Knowledge Base tip.
As a corporate in the SUPE/NOSU user category, do I need to migrate my MT 101 traffic to ISO 20022?
As per CBPR+ scope, all payment instructions exchanged by SUPE and NOSU are now expected to use ISO 20022. From November 2026:
- MT 101 (multiple) is End of Life - NAK
- MT 101 (single) will be subject to contingency processing (automatic bootstrap applied, MT101 to pain.001 conversion subject to additional FIN validation, fees will apply)
For information on how to assess if your traffic must be migrated to CBPR+ visit our Knowledge Base tip. For information on whether to send pain.001 or pacs.008 messages visit our Knowledge Base tip.
Note that while migration from MT to ISO 20022 is not mandatory for corporates (listed as CORP, TRCO, MCCO) at this time, we strongly encourage corporates to adopt ISO 20022 now to unlock the full benefits of rich and structured data.
ISO 20022 message types
Which payment initiation flows are covered by the ISO 20022 standard for corporate payments?
The usage guidelines support both cross border and domestic unitary payment instructions that corporates can transmit to their financial institution as pain.001 (and with corresponding pain.002 as Customer Payment Status Report).
The main drivers behind the design of the specifications were to target treasury flows that happen over FIN today, as they are in line with CGI-MP recommendations, while ensuring continuous compatibility with CBPR+ (Cross-Border Payments and Reporting Plus), HVPS+ (High-Value Payments Plus) and IP+ (Instant Payment Plus).
Which cash reporting messages are covered with the ISO 20022 standard for corporate payments?
The usage guidelines support both cross border and domestic unitary cash management & reporting messages (camt.052/053/054) that corporates can receive from their financial institutions.
The main drivers behind the design of the specifications were to target treasury flows that happen over FIN today, as they are in line with CGI-MP recommendations, while ensuring continuous compatibility with CBPR+ (Cross-Border Payments and Reporting Plus), HVPS+ (High-Value Payments Plus) and IP+ (Instant Payment Plus).
From November 2026, SCORE+ usage guidelines will also support payment cancellation messages (camt.055 and camt.029).
Will bulk payments be covered?
Swift continues to work with the Corporates Working Group to define and prioritise the roadmap for the next messages to be covered with the ISO 20022 standard for corporate payments. Bulk payments continue to be a topic of interest in those discussions.
The roadmap will be communicated during our community webinars. To stay in the know, make sure your operational contacts are up to date and that you have updated your commercial communications preferences in the Swift Preference Centre.
Messaging services
Can SCORE participants continue to use FIN beyond November 2025, the migration deadline of ISO 20022 for CBPR+ payments?
Financial institutions have now completed their migration to ISO 20022 for interbank cross-border payment instructions. Corporates are not mandated to make the change, but Swift strongly encourages corporates to adopt ISO 20022 as soon as possible to benefit from the rich and structured data capabilities enabled by ISO 20022 as it provides a unique opportunity to simplify and improve the end-to-end process.
Message exchanges in the Swift for Corporates (SCORE) service will remain unchanged for the foreseeable future. However, we do encourage corporates to speak with their banks and technology partners so that all parties can align on their ISO 20022 migrations and any anticipated or required changes.
For more details on the interbank migration, please refer to our Knowledge Base tip.
How does FINplus compare to FIN?
FINplus is the Swift store-and-forward, message-processing service that supports the secure and reliable exchange of ISO 20022 messages between Swift users and corporates. It enables financial institutions that are currently using the FIN service to exchange financial transactions in MT format, with the necessary environment to exchange the richer ISO 20022 format messages.
FINplus allows for exchanging ISO 20022 messages with Swift network and message validation, a centralised translation service with legacy FIN formats, etc. Additionally, Transaction Manager will be able to capture data from FINplus flows and maintain its integrity throughout the chain.
For more information, read the FINplus Service Description or enroll in the course ISO 20022 for payments with the Moving from FIN to FINplus: Fundamentals.
SCORE participants can continue to use FIN as they do today. However, we will consider this channel as a legacy channel between corporates and banks.
Read the FINplus Service Description
How does FINplus compare to FileAct?
FileAct serves as a proprietary channel facilitating communication between corporates and their banks. The accuracy, and validity of content in files sent by FileAct depends on the bilateral agreement and validation of senders and receivers. FINplus allows for exchanging ISO 20022 messages with Swift network and message validation, a centralised translation service with legacy FIN formats, etc. Additionally, Transaction Manager will be able to capture data from FINplus flows and maintain its integrity throughout the chain.
SCORE participants can continue to use FileAct as they do today. However, we will consider this channel as a propriety host to host channel between corporates and banks.
November 2026 – Hybrid/Structured Address Requirements
What is changing with postal address requirements, and when does this apply?
From 14 November 2026, aligned with CBPR+ and HVPS+ and the community transition towards ISO 20022, fully unstructured postal addresses will no longer be accepted in cross-border payment messages. After this date, where an address is required, it must be provided in either a fully structured or hybrid format. Payments that contain unstructured addresses will be rejected.
What is a “hybrid postal address” and why was it introduced?
A hybrid postal address allows a combination of structured address elements and a limited amount of unstructured text. At a minimum, the structured part must include:
- Town Name, and
- Country Code (ISO 2-letter)
Any remaining address information may be included in up to two unstructured address lines, provided these do not duplicate structured fields. Hybrid format was introduced to give the industry a transition path for systems that cannot yet produce fully structured addresses.
Does this mean corporates now need to collect beneficiary bank address details?
No, in most cases, nothing changes. If a corporate continues to instruct payments using the beneficiary bank’s BIC, there is no requirement to provide or maintain the bank’s postal address. Address requirements only apply when a bank or agent is identified by name and address instead of a BIC. This means corporates generally do not need to source beneficiary bank addresses from supplier invoices.
Which parties’ addresses are affected by the November 2026 requirement?
Where an address is required, the hybrid or structured requirement applies to:
- The Creditor (beneficiary)
- The Debtor (where applicable in the message)
- The Ultimate Debtor / Ultimate Creditor (if used)
- Agents, only when a BIC is not provided
In all cases, the minimum requirement is a structured Town Name and Country Code.
What does this mean for corporates using MT101?
For corporates using MT messages or other non-ISO 20022 communication protocols, they must ensure that address data includes Town Name and Country as structured elements, even when submitted via semi-structured fields.
Example using the MT101 Field 59 (F-option) format for a hybrid postal address:
:59F:/BE30001216371411
1/JOHN SMITH
2/HOOGSTRAAT 6, 18TH FLOOR
3/BE/BRUSSELS, 1000
Where:
1/=Name (JOHN SMITH)
2/=Address Line (HOOGSTRAAT 6, 18TH FLOOR)
3/=Country Code (BE), Town Name (BRUSSELS), and Postal Code (1000)
Are there any new mandatory fields for MT101 Request for Transfer messages in 2026, and what is changing with the hybrid address requirement?
No, there are no changes to the mandatory MT101 fields. Corporates must continue to populate the same required fields defined in the MT101 standard. Including the ordering customer, beneficiary, amount, execution date and charges.
However, Option F must be used for Field 50a (Ordering customer) and Field 59 (Beneficiary customer) where providing an address.
Option H for Field 50a (Ordering customer) and No Letter Option for Field 59 (Beneficiary customer) must no longer be used where providing an address.
Do fields 56a: (Intermediary Institution) and 57a: (Account with Institution) become mandatory in MT101 messages from November 2026, and are there any new address requirements for these fields?
No, fields 56a and 57a do not become mandatory. Their use remains conditional, dependent on the payment routing scenario agreed with the bank. There is no new obligation to populate these fields as part of the hybrid/structured address requirements.
However, SR2026 brings updated formatting rules if these fields are used and an address is provided. In such cases:
- Fully unstructured addresses are no longer permitted
- Any name‑and‑address information must follow a pseudo‑structured (hybrid) format, including at least a Country Code and Town Name
- These rules apply only when the bank or agent is identified by clearing code and/or name and address, not when identified by BIC. Here, Option D must be used and the second, third, or fourth line must be formatted as "3/CC/TOWN NAME", where CC is a valid ISO country code and TOWN NAME is a valid town name for the institution.
If we move to SCORE+ pain.001, how do address requirements apply?
For pain.001 payment initiation, Swift provides SCORE+ usage guidelines that support both hybrid and fully structured postal addresses when messages are sent over FINpus.
The same principles apply:
- At least Town Name and Country Code must be structured
- Hybrid addresses may include up to two unstructured address lines.
Migrating to pain.001 is strongly recommended to simplify compliance and improve straight through processing (STP).
Transaction Manager
Will payment initiation and cash reporting flows become visible in Transaction Manager?
Transaction Manager orchestrates payments on the Swift network by guaranteeing that complete rich data is protected and shared end-to-end based on the community-agreed business validation rules, data integrity rules and visibility rules.
It is directly embedded into our messaging systems meaning that you benefit from it for all your in-scope transactions. You do not need to opt-in to benefit from Transaction Manager. For more information, read the Transaction Manager Business Processing Rules.
Payment initiation and cash reporting in ISO 20022 are currently out of scope for Transaction Manager, but we plan to extend the transaction management orchestration in the future.
APIs
Will payment initiation over API be possible?
We plan to introduce API connectivity for connected corporate–to-bank payment initiation flows after a successful pilot, based on the same usage guidelines that apply to the ISO 20022 payment initiation messages.
Will cash reporting over API be possible?
Corporates and their banks now have access to Instant Cash Reporting, our new standardised cash reporting API. Through our multi-bank API gateway, corporates can request and view account balance information, statements, and transaction summaries from the banks that support this API. All of this data will be available in the ISO 20022 messaging format, nearly instantly and in a structured, consistent way.
Companies that adopt Instant Cash Reporting will be better placed to streamline reconciliation, improve the accuracy of their cash forecasts, and enhance the quality of their data.
How to get ready to exchange ISO 20022 flows on FINplus
How can corporates on SCORE, and their vendors/partners, prepare to exchange ISO 20022 flows on FINplus?
The best way to prepare is to refer to our readiness materials:
- FINplus Service Description
- ISO 20022 for Financial Institutions Customer Adoption Guide
- FINplus for Corporates Usage Guidelines[AO1]
- ISO 20022 for Corporates fact sheet
How can banks on SCORE, and their vendors/partners, prepare to exchange ISO 20022 flows on FINplus?
The best way to prepare is to refer to our readiness materials:
- ISO 20022 for Financial Institutions Customer Adoption Guide
- ISO 20022 for Corporates SCORE Customer Adoption Guide
- FINplus Service Description
- FINplus for Corporates Usage Guidelines
- ISO 20022 for Corporates fact sheet
The GUI requires no technical integration and provides a preview of the real-time, end-to-end view of cross-border payments across multiple banks.
