integration

Współpraca korporacje

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

XML (ISO 20022) PAIN.001.001.09

yes

import of transfers in the BRESOK2 format

import of transfers in an individual format

MultiCash / EBICS

PLI

XML (ISO 20022) PAIN.001.001.09

yes

PLS

PLA

RFT/MT101
(debiting either mBank’s accounts (active MT101) or the accounts of other banks (passive MT101))

SWIFTNET Korpo

MT101 – SWIFT message directly from the client

XML (ISO 20022) PAIN.001.001.09

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

XML (ISO 20022) PAIN.001.001.09

yes

import of transfers in the BRESOK2 format

import of transfers in an individual format

MultiCash / EBICS

PLI

XML (ISO 20022) PAIN.001.001.09

yes

PLS

PLA

RFT/MT101
(debiting either mBank’s accounts (active MT101) or the accounts of other banks (passive MT101))

SWIFTNET Korpo

MT101 – SWIFT message directly from the client

XML (ISO 20022) PAIN.001.001.09

yes

SWIFT (MT101)

MT101 – a SWIFT message from the client’s bank

XML (ISO 20022) PAIN.001.001.09

 

search results