ISO 20022
International standard of electronic communication in financial systems
ISO 20022 – changes in payment formats
formats of all types of payments are to change within the next two years.
Within the next two years, the format of payments will change – ultimately, it will be governed by the uniform international ISO 20022 standard. Owing to the standard, data exchange between different systems will be easier. The standard will enable precise identification of transactions and their automatic booking.
Changes will affect all types of payments (domestic, international, internal, incoming and outgoing). Banks and their clients must prepare and align their financial and accounting systems with the new standard. The changes may require e.g. supplementing databases in financial and accounting systems or restructuring an entire interface for data exchange between a bank and its clients.
ISO 20022 – What is changing
Transfer forms and file formats change for:
transfers entered manually,
domestic and foreign transfers: SEPA, SWIFT, SORBNET, ELIXIR,
mass payments,
Collect – analytical accounting and Collect – aggregate accounting service reports,
direct debit,
bank statements: MT940, MT942 and MT950,
the MT101 service (request for transfer).
Plan the adjustment of your financial and accounting systems sufficiently in advance.
shedule of the changes in transfers
We are applying a transitional period during which both formats are available simultaneously to ensure that our clients have time to adjust their systems.
The schedule may change. Last update: 07.04.2026
For a description of the schedule, go to outgoing transfers
learn more about the changes
outgoing transfers
familiarise yourself with the changes in transfer forms
statements and reports
familiarise yourself with the new formats of statements and reports
integration
learn about the changes in the integration of transfers and statements
other products
learn about the changes to Collect – analytical accounting and Collect – aggregate accounting, direct debit, postal order and MT101
contact us if you need any help
We will gladly help you in the migration to the new standard (ISO 20022) and answer any questions you may have. You can contact the Corporate Client Centre Monday to Friday from 8 a.m. to 6 p.m.
call from the app
Tap the receiver icon in mBank CompanyMobile.
call us at:
22 6 273 273 – international and mobile calls
801 273 273 – landline calls
chat with us
Use the online assistant service. Log in to mBank CompanyNet and send a chat message. Our consultant will be happy to assist you.
How to prepare for the changes in transfer formats?
In order to execute transfers containing new data in the mBank CompanyNet system, enter new address data in a transfer and update the database of counterparties.
Check if your financial and accounting system or ERP system allows you to enter the necessary address data of counterparties.
If yes – enter the missing data in the system
If not – contact the system provider and implement necessary changes
Check if you can import transfers in the XML format (ISO 20022)
If yes – check if your file contains new split addresses of counterparties and if it is possible to import them into mBank CompanyNet, MultiCash or SWIFTNET.
If not or if you don’t know – contact the system provider and implement necessary changes.
CompanyConnect Classic (powered by mBank) and CompanyConnect Developer (interface customised for you) – refer to the item “If you import transfers from a financial and accounting system or an ERP system”, contact the company implementing the solution at your company and plan the implementation of necessary changes.
CompanyConnect Partner for the following systems: Comarch, Insert, Enova, SACE, SAP – contact the system provider and implement necessary changes
Check if your financial and accounting system or ERP system supports the CAMT.053 format.
If yes – request statements in the CAMT.053 format
If not – contact the provider of your system and ask if the import of CAMT.053 files is possible.
If you are not using MT940 yet, consider optimising the processing of bank statements. Should you have any questions, please contact the Corporate Customer Centre.
Q&A
The changes will affect domestic and international payments. They cover the scope of data that is provided when making payments on the online banking form, when importing files and in bank statements.
Data
It will be necessary to provide more information on the parties to a transaction in the form of structured data when executing transfers – separately the postal code, city, street name, house number, country, etc. Some data will be mandatory.
Importing transfers
Integrated mBank systems will eventually transition to the XML format, and other file import formats will be gradually discontinued (over several years).
Bank statements
We will support a new type of bank statements in the XML format: CAMT (CAMT.053.001.08 and CAMT.052.001.08). Similarly to transfers, bank statements will contain more information; align your financial and accounting or ERP systems accordingly. The legacy formats MT940 and MT942 will not contain full information sent in transfers. We recommend transitioning to the new CAMT formats.
Data exchange file structures (existing and new formats) are available here.
Schedules and detailed descriptions of changes are published on the webpages outgoing transfers and bank statements and reports.
We introduce the changes in a way that is as client-friendly as possible to make sure that clients have enough time to align their systems to the new formats. When introducing the changes, we apply a transitional period in which both the legacy and the new formats are available simultaneously. We prepare materials that present the scope of changes in great detail. We prioritise transparency in communication. We are organizing meetings with clients and webinars, during which we share information on the upcoming changes.
Depending on the product, the number of required fields may vary. If the imported file contains more fields in the address than we require in the transfer form, we will only import the data required in the transfer form.
The contractor name field will have a maximum of 70 characters.
Maximum number of address fields:
Street
Building number
Apartment number
Postal code
City - required field
Country - required field
Department
Division
Building name
Floor
PO box
District
County
Voivodeship
ISO 20022 is an international standard of electronic communication in financial systems. It was developed by the International Organization for Standardization (ISO) in order to standardise the exchange of data between various entities in the financial sector.
The standard defines formats of files and messages used to transfer information related to financial transactions, such as payments and bank statements.
Information exchange is based on XML files with a clearly defined data structure.Yes, all banks are obliged to align their systems with the new payment message formats.
SWIFT and the main central banks around the world decided to migrate all interbank cross-border payments and RTGS (Real Time Gross Settlement, i.e. Target 2) payments from the traditional MT standard to ISO 20022 XML (including statements).
The changes will affect domestic and international payments. They cover the scope of data that is provided when making payments on the online banking form, when importing files and in bank statements.
Data
It will be necessary to provide more information on the parties to a transaction in the form of structured data when executing transfers – separately the postal code, city, street name, house number, country, etc. Some data will be mandatory.
Importing transfers
Integrated mBank systems will eventually transition to the XML format, and other file import formats will be gradually discontinued (over several years).
Bank statements
We will support a new type of bank statements in the XML format: CAMT (CAMT.053.001.08 and CAMT.052.001.08). Similarly to transfers, bank statements will contain more information; align your financial and accounting or ERP systems accordingly. The legacy formats MT940 and MT942 will not contain full information sent in transfers. We recommend transitioning to the new CAMT formats.
To execute transfers in the ISO 20022 standard, files in the XML format will be required. Data exchange file structures (existing and new formats) are available here.
XML, which stands for Extensible Markup Language, uses tags that define how a text in a data file should be structured, stored and transported. XML was designed to be readable by both humans and machines. It is a highly configurable markup language, which is perfectly suited to the times in which data is of key importance.
Data exchange file structures (existing and new formats) are available here.
The new format was developed to standardise the exchange of data between various entities in the financial sector.
Additional data help the transaction parties to track the flow of funds more efficiently and to increase the possibility of process automation (including analytical processes).
Payments made using the new format which do not contain additional and required data will be rejected by the settlement system.
The XML format can be used to import all transfers except for Mass Payment and Mass Payment Plus transfers. We are planning to enable the import of those transfers in the XML format in 2025.
MultiCash and SWIFTNET systems enable the import of all payments in the XML format.
As for direct debits, we will enable the import of transfers in the XML format.
You can find more details in the schedule of changes.
Schedules and detailed descriptions of changes are published on the webpages outgoing transfers and bank statements and reports.
and the new (XML) formats will be used. You can switch to the new, broader dataset at your convenience. If you are unsure how to do it, please contact the Corporate Client Centre.
Yes, all financial and accounting and ERP systems must be aligned to the changes in the integration with mBank. Contact the provider of your financial and accounting or ERP system as soon as possible and schedule the work for 2025. Send the direct link to the integration website to your provider. We publish all information on the new formats for exchanging data with mBank there.
The provider/administrator of your financial and accounting system surely knows about the upcoming changes arising from ISO 20022. Contact the person responsible for the system directly to lay down the details, schedule and scope of the changes.
The changes we are introducing arise from external formal and legal requirements (including the AML requirements) and individual payment settlement systems. The extent of the changes is beyond our control. We align mBank’s systems and solutions to the new standards in advance to give our clients enough time to plan the necessary works in their systems.
The price of CAMTs available in the mBank CompanyNet and SWIFT systems will not differ significantly from prices for MT94x. The current Tariff of Banking Fees and Commissions is published here.We recommend that you plan the changes as early as possible in consultation with the provider of your financial and accounting or ERP system. If you do not align your system on time, you may have problems with transfer execution.
All the requirements of the new standard are available on the integration website. Should you have any questions, feel free to contact the Corporate Client Centre.When you can start depends on the type of payments or bank statements and reports. In the case of SEPA transfers, international transfers and bank statements, you can start using the new ISO 20022 standard today. Further changes will be introduced in line with the schedules presented on the webpages outgoing transfers and bank statements and reports.
We will inform you about the changes on mBank CompanyNet and on mBank’s website.To make sure that the solution you are using complies with the ISO 20022 standard, contact the provider of your financial and accounting or ERP system. The scope of data in individual transfers should be consistent with the structure of the ISO 20022 XML import file presented on the integration website. If you need help, contact the Corporate Client Centre.
Yes, as changes will affect all types of payments (domestic, international, internal, incoming and outgoing). Banks and their clients must prepare and align their financial and accounting or ERP systems with the new standard.
The latest data exchange file structures (legacy and new formats) are made available at. If you need help, contact the Corporate Client Centre.
After the transitional period, using the legacy payment formats and the new ISO 20022 formats that are not aligned with a wider scope of data may result in payments being rejected by mBank or the recipient’s bank.
We recommend that you transition to the new data formats as soon as possible. Please read the schedules published on the webpages outgoing transfers and bank statements and reports.
Should you have any questions, contact the Corporate Client Centre.
After the transitional period, using the legacy payment formats and the new ISO 20022 formats that are not aligned with a wider scope of data may result in payments being rejected by mBank or the recipient’s bank.
We aim to discontinue any other formats than XML (ISO 20022). We recommend that you transition to the new data formats as soon as possible. Schedules of changes are published on the webpages outgoing transfers and bank statements and reports.
The legacy payment formats do not contain data necessary to execute payments correctly. Using the legacy payment formats may result in payments being rejected by mBank or the recipient’s bank.
No, because the legacy payment formats do not contain all the data necessary to execute payments correctly. Using the legacy payment formats may result in payments being rejected by mBank or the recipient’s bank. We aim to discontinue any other formats than XML (ISO 20022). You can find the description of the format here: integration.
You can find the schedule of changes on the website bank statements and reports.
mBank or the recipient’s bank can reject a payment if the ISO 20022 files contain unstructured addresses or the necessary data is missing. We will ultimately support XML files (ISO 20022) containing structured addresses only. We recommend that you use the pain.001.001.09 format (ISO 20022).
You can find the description of this format in the integration tab.
You can find the schedule of changes on the website bank statements and reports.We are not planning to discontinue MT940 and MT942 files in the mBank CompanyNet and MultiCash systems. However, we cannot provide full transaction data in those files as they have insufficient space to include the new information sent in payments. We recommend that you integrate your financial and accounting and ERP systems with the new bank statements CAMT.053 (in place of MT940) and CAMT.052 (in place of MT942).
As per SWIFT’s recommendations, if you provide bank statements to other banks, we recommend that you migrate to CAMT.052 and CAMT.053. Contact you bank and check the schedule of changes. The deadlines for migrating to the new message types at mBank can be found on the website bank statements and reports.
Yes, the changes apply to all integrations with mBank.
Yes, the changes apply to all transfers regardless of the account type.
We are planning to enable the option to send CAMT files to banks via SWIFT in Q1 2025. We will inform you about the changes and how to apply for a format change in advance via mBank CompanyNet and on mBank’s website. Please check when your bank will be ready to receive CAMT.053 and CAMT.052 messages before you migrate to the new formats.
If you want to receive bank statements from mBank accounts in the new format:
if you use mBank CompanyNet, send us a message in the system,
if you use MultiCash, contact an advisor to sign a relevant amending annex to your agreement,
if you use SWIFTNET Korpo, contact an advisor to sign a relevant amending annex to your agreement.
At the end of the year we will give clients the option to enable the new bank statements in mBank CompanyNet. Currently, you can enable and disable MT940 and MT942 statements this way.
We are planning to enable the option to send CAMTs to other banks at the beginning of 2025.
If you want to send bank statements in the ISO 20022 format to other banks, make sure that your bank enabled this option.
Yes, the changes affect payroll transfers as well. If you send remuneration using mass transfers, the option to import orders in the XML format will be made available as per the schedule on the website outgoing transfers.
Until 14 November 2026, the service will continue to be available in its current form and communication standard.
From 15 November 2026, the only supported format will be pain.001.001.09.
We are ready to handle incoming request for transfer messages in the pain.001.001.09 format.
If your bank is prepared, you can switch to the new standard.
For the Collect – aggregate accounting service, we will enable the use of an analytical file in XML format.
For the Collect – analytical accounting service, we do not anticipate any changes.
All postings are made on the current account from which the statement is generated in MT940 or CAMT format.
We will provide information about the timelines for individual products on the other products page.
We are not planning to launch a test environment. We are working on a tool for checking the validity of an XML file. The Corporate Client Centre can also help you verify the structure of the transfer import files.
We are currently not planning any changes in the cut-off times for payments.
Please contact the Corporate Customer Centre.
Talk to an Online Assistant via the chat in mBank CompanyNet, tap the handset icon in the mobile app or dial 22 6 273 273, 801 273 273. You can contact us from Monday to Friday, from 8.00 am to 6.00 pm.Depending on the product, the number of required fields may vary. If the imported file contains more fields in the address than we require in the transfer form, we will only import the data required in the transfer form.
The contractor name field will have a maximum of 70 characters.
Maximum number of address fields:
Street
Building number
Apartment number
Postal code
City - required field
Country - required field
Department
Division
Building name
Floor
PO box
District
County
Voivodeship