integration
changes in the integration of transfers and statements
As regards the integration between mBank’s systems and our clients’ financial and accounting systems or ERP systems, we will ultimately transition to XML formats in line with ISO 20022.
The changes will cover:
the import of transfers
bank statements
Ultimately, we will only allow the import of transfers in the XML (ISO 20022) PAIN.001.001.09 format, whereas other formats will be gradually withdrawn (over the course of a few years).
We will inform you in advance about the specific dates of the changes and the withdrawal of non-XML formats.
change of transfer import structures
Learn what file types will replace the ones used so far
|
Your system |
Current file type |
New file type |
Is the change mandatory? |
|
mBank CompanyNet |
import of transfers in the ELIXIR-O format |
yes | |
|
import of transfers in the BRESOK2 format | |||
|
import of transfers in an individual format | |||
|
MultiCash / EBICS |
PLI |
yes | |
|
PLS | |||
|
PLA | |||
|
RFT/MT101 | |||
|
SWIFTNET Korpo |
MT101 – SWIFT message directly from the client |
yes | |
|
SWIFT (MT101) |
MT101 – a SWIFT message from the client’s bank |
XML (ISO 20022) PAIN.001.001.09 |
|
Your system |
Current file type |
New file type |
Is the change mandatory? |
|
mBank CompanyNet |
import of transfers in the ELIXIR-O format |
yes | |
|
import of transfers in the BRESOK2 format | |||
|
import of transfers in an individual format | |||
|
MultiCash / EBICS |
PLI |
yes | |
|
PLS | |||
|
PLA | |||
|
RFT/MT101 | |||
|
SWIFTNET Korpo |
MT101 – SWIFT message directly from the client |
yes | |
|
SWIFT (MT101) |
MT101 – a SWIFT message from the client’s bank |
XML (ISO 20022) PAIN.001.001.09 |
Learn what file types will replace the ones used so far
|
file source |
current file type |
new file type |
is the change mandatory? |
|
mBank CompanyNet |
MT940 |
|
recommended |
|
MT942 |
recommended | ||
|
MultiCash / EBICS |
MT940 |
recommended | |
|
MT942 |
recommended | ||
|
SWIFTNET Korpo |
MT940 |
recommended | |
|
MT942 |
recommended | ||
|
SWIFT/CBPR+ |
MT940 |
Mandatory from Q4 2028 | |
|
MT942 |
Mandatory from Q4 2028 | ||
|
files showing debits/credits in mBank accounts received via SWIFT or via another bank’s system |
MT940 |
CAMT.053.001.08 |
recommended |
|
MT942 |
CAMT.052.001.08 |
recommended | |
|
MT941 |
CAMT.052.001.08 |
recommended | |
|
MT950 |
CAMT.053.001.08 |
recommended |
|
file source |
current file type |
new file type |
is the change mandatory? |
|
mBank CompanyNet |
MT940 |
|
recommended |
|
MT942 |
recommended | ||
|
MultiCash / EBICS |
MT940 |
recommended | |
|
MT942 |
recommended | ||
|
SWIFTNET Korpo |
MT940 |
recommended | |
|
MT942 |
recommended | ||
|
SWIFT/CBPR+ |
MT940 |
Mandatory from Q4 2028 | |
|
MT942 |
Mandatory from Q4 2028 | ||
|
files showing debits/credits in mBank accounts received via SWIFT or via another bank’s system |
MT940 |
CAMT.053.001.08 |
recommended |
|
MT942 |
CAMT.052.001.08 |
recommended | |
|
MT941 |
CAMT.052.001.08 |
recommended | |
|
MT950 |
CAMT.053.001.08 |
recommended |
requirements regarding the beneficiary’s address
We recommend that you always provide the beneficiary's full address. If you don’t provide the beneficiary's address, the payment may be rejected by mBank, intermediary banks, or the beneficiary's bank.
These requirements apply to import files in the pain.001 format sent to us.
|
order type |
beneficiary’s country |
beneficiary’s address |
comments |
|---|---|---|---|
|
SWIFT (international) |
worldwide |
required |
the beneficiary’s address must
|
|
SEPA/ EuroEkspres (international in EUR) |
European Economic Area (EEA) |
optional |
the beneficiary’s address, if provided, must
|
|
non-EEA country |
required |
the beneficiary’s address must
| |
|
SORBNET (domestic) |
Poland |
optional |
the beneficiary’s address, if provided, should
you can provide the beneficiary’s address in an unstructured form
the beneficiary’s address will be appropriately processed and forwarded to the beneficiary’s bank |
|
Elixir/Express Elixir (domestic) |
Poland |
optional |
the beneficiary’s address, if provided, should
you can provide the beneficiary’s address in an unstructured form
the beneficiary’s address will be appropriately processed and forwarded to the beneficiary’s bank |
|
order type |
beneficiary’s country |
beneficiary’s address |
comments |
|---|---|---|---|
|
SWIFT (international) |
worldwide |
required |
the beneficiary’s address must
|
|
SEPA/ EuroEkspres (international in EUR) |
European Economic Area (EEA) |
optional |
the beneficiary’s address, if provided, must
|
|
non-EEA country |
required |
the beneficiary’s address must
| |
|
SORBNET (domestic) |
Poland |
optional |
the beneficiary’s address, if provided, should
you can provide the beneficiary’s address in an unstructured form
the beneficiary’s address will be appropriately processed and forwarded to the beneficiary’s bank |
|
Elixir/Express Elixir (domestic) |
Poland |
optional |
the beneficiary’s address, if provided, should
you can provide the beneficiary’s address in an unstructured form
the beneficiary’s address will be appropriately processed and forwarded to the beneficiary’s bank |
file validation and import
If one order in a batch is invalid, the execution of the entire batch depends on the type of orders in the file and the import settings.
|
type of orders in the file |
partial import flag
|
result of an invalid order |
|---|---|---|
|
signed orders authorised |
not applicable
|
entire file is rejected one invalid order causes all orders in the file to be rejected |
|
unsigned orders (unauthorised) with the partial import flag
|
YES |
only invalid orders are rejected all other orders will be correctly imported |
|
unsigned orders (unauthorised) without the partial import flag |
NO
|
entire file is rejected one invalid order causes all orders in the file to be rejected |
|
type of orders in the file |
partial import flag
|
result of an invalid order |
|---|---|---|
|
signed orders authorised |
not applicable
|
entire file is rejected one invalid order causes all orders in the file to be rejected |
|
unsigned orders (unauthorised) with the partial import flag
|
YES |
only invalid orders are rejected all other orders will be correctly imported |
|
unsigned orders (unauthorised) without the partial import flag |
NO
|
entire file is rejected one invalid order causes all orders in the file to be rejected |
infotip
Detailed information on errors and the reasons for rejection of individual orders is available in the import report.