MT101 Message (Request for Transfer) Format Specification

This document describes the format and field rules for MT101 messages, to be processed by mBank S.A.
mBank S.A. acts only as executing bank.
The field description is based on SWIFT standards. All fields or filed options not listed in this description or mentioned as
“not supported”, although provided by SWIFT standards for MT101 messages, will not be processed /supported by mBank
S.A. and can cause a rejection of transactions or messages.
mBank S.A. accepts MT101 messages with single and multiple transactions.
The processing will always be carried out as an individual order since collective orders are not possible.
Via MT 101 messages can be settled domestic payment orders (including Tax and ZUS payment orders) and foreign
payment orders.

Symbols used in the field format description:

Status
M Mandatory
O Optional

Types of Characters Allowed

n Digits only
a Alphabetic letters, upper case only
x Any character of SWIFT character set
c Capital letters and decimal numbers respectively
d Decimal number
[…] Subfield is optional

Restrictions on the length of filed or subfield content, using the descriptions listed below:
nn Maximum length
nn-nn Minimum and maximum length
nn! Fixed length
nn*nn Maximum number of lines times maximum line length
Examples
2n up to 2 digits
3!a always 3 letters
4*35x up to 4 lines of up to 35 characters each

SWIFT character set:

abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/-?:().,'+{}
CR LF Space
Although part of the character set, the curly brackets are permitted as delimiters and cannot be
used within the text of user-to-user messages.
Character ”-” is not permitted as the first character of the line.
None of lines include only Space.

1/9
The MT 101 consists of two sequences:

Sequence A General Information is a single occurrence mandatory sequence and contains information to be applied to
all individual transactions detailed in sequence B.

Sequence B Transaction Details is a repetitive sequence; each occurrence provides details of one individual
transaction. Fields which appear in both sequences are mutually exclusive.

Sequence A- General Information

Tag Status Description Content Comments

Must be unique for each message (or chain of
messages).
This filed must not start or end with a slash “/” and
20 M Sender’s Reference 16x
must not contain two consecutive slashes “//”.Using a
space is not recommended.

Customer Specified
21R O 16x Not supported, ignored if present.
Reference
28D M Message Index/Total 5n/5n
50L O Instructing Party 35x Not supported, ignored if present.
Line 1: /Ordering Customer’s account number
preceded by slash “/” (IBAN format).
Line 2-4: Name & address of Ordering Customer.
/34x
50H M Ordering Customer 4*35x
Must be present in either Sequence A or in each
occurrence of Sequence B, but must never be in both
sequences, nor be absent from both sequences.

If used, must contain BREXPLPWXXX.

Account Servicing May be present in either Sequence A or in one or more

52A O 4!a2!a2!c[3!c]
Institution occurrences of Sequence B, but must not be present in
both sequences.

51A O Sending Institution 4!a2!a2!c[3!c] Not supported, ignored if present.

Date must be expressed as YYMMDD (year, month,
day).
This date may be future date.
30 M Requested Execution Date 6!n If a MT101 is received with an execution day in the
future it will be stored until execution day and then
processed.

25 O Authorisation 35x Not supported, ignored if present.

As the MT101 only contains one transaction, Ordering Customer needs only be present at once. It is either present in
Sequence A or in Sequence B.

In case of multiple MT101:

- as the same account will be used to book all transactions the Ordering Customer can be quoted in Sequence A

- if different accounts had to be used, the Ordering Customer (and its account) would be included in Sequence B.

2/9
Sequence B – Transaction Details (repetitive)

Tag Status Description Content Comments

21 M Transaction Reference 16x Must be unique for each transaction.
21F O F/X Deal Reference 16x Not supported, ignored if present.
Supported Instruction Codes:

”URGP” – value date for beneficiary’s bank D+1,

where D means a date of the Client’s payment order
execution by the Bank. Option available for
currencies: EUR, USD, GBP, CAD, CHF, CZK, DKK,
HUF, NOK, RON, RUB and SEK.

„RTGS” -
1) cross border payments – value date for
beneficiary’s bank D, where D means a date of the
Client’s payment order execution by the Bank.
Option available for currencies: EUR, USD and
GBP.
2) domestic payments (payments in PLN currency
addressed to the beneficiary’s account held in
another domestic bank) – settled through the
RTGS (SORBNET) system on day D, where D
means a date of the Client’s payment order
execution by the Bank, excluding transfers
directed to ZUS and US and other tax authorities.

Note:
If tag 23E is blank or contains a code word other than
23E O Instruction Code 4!c[/30x]
‘URGP’ or ‘RTGS’, the payments are executed by the
Bank under the standard conditions i.e.:

- in the area not regulated by the Payment Services

Act dated 19 August 2011 (PSA)a, with value date
for the beneficiary’s bank D+2, where D means a
date of the Client’s payment order execution by the
Bank,

- in the area regulated by the PSA, with value date for

the beneficiary’s bank D+1, where D means a date
of the Client’s payment order execution by the Bank.

Exception are payments in PLN currency, where

settlement is performed always at the latest on the
next business day, counting from the day on which the
Bank accepts the Client's order.

„INTC” - applies only to cross border payments.

There is no preferential condition at mBank S.A. side
regarding this instruction code “INTC”. mBank S.A.
forwards this instruction directly to beneficiary’s bank
only.

Currency must be a valid ISO 4217 currency code.

The integer part of amount must contain at least one

Currency/Transaction digit. A decimal comma is mandatory and is included
32B M 3!a15d
Amount in the maximum length. The number of digits following
the comma must not exceed the maximum number
allowed for the specified currency.

50L O Instructing Party 35x See Sequence A.

/34x
50H M Ordering Customer Required if not in Sequence A.
4*35x
Account Servicing
52A O 4!a2!a2!c[3!c] See Sequence A.
Institution
56A O Intermediary 4!a2!a2!c[3!c] Not supported, ignored if present.
57A Option A: SWIFT Code of beneficiary bank.

or 4!a2!a2!c[3!c] Option A is preferred option!

O Account with Institution
For cross border payments in EUR to account within
EU/EEA, option A is mandatory

a
Payments subject to the Payments Service Act of 19 August 2011 – transfers for beneficiaries located in the territory of the states that are
members of the European Economic Area (countries of the European Union and Lichtenstein, Iceland and Norway) and executed in the
currencies of those countries

3/9
57D e.g.
:57A:COBADEFF370

Option D must only be used in exceptional

Option D : circumstances, that is, when the party cannot be
identified by a SWIFT Code.

[1!a][/34x] Line 1: //national clearing system code

4*35x Line 2-4: name and address of beneficiary bank
e.g.
:57D://PL10500099
ING BANK SLASKI
or or
4*35x Line 1-4: name and address of beneficiary bank.

e.g. :57D:UNION BANK OF CALIFORNIA N.A.

2110 HIGH STREET
SELMA, CA93662
Line 1: the beneficiary account number preceded
by slash “/”.
Line 2-4: the beneficiary name and address.
Highly recommended to provide full beneficiary data
(name & address).
[/34x]
59 M Beneficiary 4*35x For domestic payments IBAN or NRB account format is
mandatory.

For cross border payments – it is recommended to

provide the beneficiary’s account in the IBAN format
for the countries in which the standard is effective.

Details which are to be transmitted to the beneficiary

customer.
Highly recommended always to specify transaction
details!

Special formatting rules apply when filling in payment

details for Tax (US) and social security (ZUS)
payments in accordance with the Ordinance of the
Minister of Finanace.
70 O Remittance Information 4*35x See below tables for details:

Structure of the field “Remittance Information”

for US payments

Structure of the field “Remittance Information”

for ZUS payments

77B O Regulatory Reporting 3*35x Not supported, ignored if present.

Currency/Original
33B O 3!a15d Not supported, ignored if present.
Ordered Amount
OUR/SHA/BEN allowed

Cross border payments regulated by the PSA are

71A M Details of Charges 3!a executed only with the charging options SHA
(recommended) or OUR.
Option BEN will be automatically converted to SHA.

25A O Charges Account /34x Not supported, ignored if present.

36 O Exchange Rate 12d Not supported, ignored if present.

4/9
Structure of the field „ Remittance Information” for US payments

The data in the first line is a string of signs without separators, each fields are preceded by code words put between
slashes..

Field (code word) Status Format Field content Line

number of
field :70:
/TI/ Identification M /TI/1!c14c Type and number of the payer ‘s Identyfication can 1
type and content take one of the following values:
N – NIP,
P – PESEL,
R – REGON,
1 – Series and number of Polish Identity card,
2 – Series and number of passport,
3 – Other identity document.
Up to 14 alphanumeric characters.

/OKR/Period - Year, M /OKR/2!n1!a4n Period - Year, type of period and number of period 1
Type of period and for which payment is made.
number of period for
which payment is The first part of the field “Period” contains two
made characters of the year (in two-digit format, e.g. 12
for 2012).
The second part contains one of the following
“Period Type”:
R – year,
P – half-year,
K – quarter,
M – month,
D – decade,
J – day
The third part contains the period number:
When Period type is:
• R – the number of period is omitted,
• P – it requires the two-character space to be
filled with the value 01 or 02,
• K – it requires the two-character space to be
filled with the value 01,02,03 or 04,
• M – it requires the two-character space to be
filled with the value from 01 to12,
• D – it requires the first two-character space to
be filled in the value 01,02,03 and the next
two-character space with a value from 01-12
range.
• J – it requires the first two-character space to
be filled in with a value from 01 – 31 range,
corresponding to a given day, and the next
two-character space with a value from 01-12
range corresponding to a given month.
•
/SFP/Tax form M /SFP/6c Tax form: PIT37, VAT7,CIT2, AKC2A, CIT, VAT, AKC, 1
GL, KP, PPE, PN, SD, PCC, OS, INNE.

/TXT/Description O /TXT/40x Free text explaining payment, up to 40 2

alphanumeric characters.

Example:

:70:/TI/N1070002939/OKR/12M01/SFP/CIT2
/TXT/ Podatek CIT2

5/9
Structure of the field „Remittance Information” for ZUS payments

Filed Status Format Field content Line

number of
filed :70:
Payer’s NIP (tax M 10!n Payer’s NIP must be entered without separators. 1
identification
number)
Type and number of M 1!c14!c Type and number of additional Identification of the 2
additional payer. Additional identifier type, can take one of the
Identification of the following values:
payer
P – PESEL,
R – REGON,
1 – ID card number
2 – Passport number
This field can be left blank (if the second identifier
has not been given). Values should be entered
without dashes, spaces, etc.
• If the type is „P” identifier must be a formally
valid PESEL number.
• If the type is „R” – identifier must be a formally
valid REGON number.
• If the type is 1 – it is part of the series and
number of the identity card.
• If the type is 2 – it is part of the series and
number of passport.
Note: If the type is 1 or 2 – the identifier can not be
blank (spaces are treated as lack of content) and
can not be longer than 14 characters.

Type of payment, M 1!c4!n2!n2!n Field „Type of payment” ,” Declaration” and 3

Declaration type and „Declaration number” must be filled as following:
number „Type of payment” must contain one of the
following values:
”A” – Additional charge paid by the payer,
”B” – Additional charge paid by the payer
”D” – Additional payment,
”E” – Execution Costs,
”M”– Period longer than 1 month,
”S” – Fee for 1 month,
”T” – Deferred Payment Date or
”U” – Instalment plan.
Filed „Declaration” must contain year and month
in format „RRRRMM” (where RRRR>1998 and
01<=MM<=12).
Field „Declaration number” :
- if „Type of payment” = ”S” or ”M” value of filed
”Declaration number” is from range 01-89,
- if „Type of payment” = ”A”, ”B”, ”D”, ”E”,
”T” or ”U” takes one of the following values :
”01”,”40”,”51”,”70” or ”80”.

Decision O 15x If „Type of payment” = ”S” or ”M” line can not be 4

number/Contract filled.
number/Enforcemen
t title number If „Type of payment” = ”A”, ”B”, ”D”, ”E”, ”T”, ”U”
the field value should be other than space.

Example:

:70:1070002939
R350535626
S20110501

6/9
Examples:
1) Single MT101 messages:
Domestic payment order
(Without SWIFT- Header)

:20:1106210404010000
:28D:1/1
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:52A:BREPLPWXXX
:30:110621
:21:2011062100000002
:32B:PLN369,85
:57A:PKOPPLPWW16
:59:/PL22102010680000321000052142
BENEFICAIRY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:FAKTURA VAT 11/06/05
:71A:SHA
-}

ZUS payment order

(Without SWIFT- Header)

:20:1106210404010000
:28D:1/1
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:52A:BREPLPWXXX
:30:110621
:21:2011062100000002
:32B:PLN369,85
:57A:NBPLPLPW
:59:/ 78101010230000261395200000
ZAKLAD UBEZPIECZEN SPOLECZNYCH
UBEZPIECZENIE ZDROWOTNE
STREET
CITY
:70:1070002939
R350535626
S20110501
:71A:SHA
-}

US payment order
(Without SWIFT- Header)

:20:1106210404010000
:28D:1/1
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:52A:BREPLPWXXX
:30:110621
:21:2011062100000002
:32B:PLN369,85
:57A:
:59:/ 56101010100166232222000000
URZAD SKARFBOWY
STREET
CITY
:70:/TI/N1070002939/OKR/12M01/SFP/VAT7
/TXT/ VAT7 ZA STYCZEN
:71A:SHA
-}

7/9
Foreign payment order
(Without SWIFT- Header)

:20:1106210100000003
:28D:1/1
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:52A:BREPLPWXXX
:30:110621
:21:2011062100000003
:32B:EUR955,55
:57A:CITIGB2LXXX
:59:/ IT40S0542811101000000123456
BENEFICAIRY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:FAKTURA VAT 11/06/06
:71A:SHA
-}

Multiple MT 101 with single debit account

(Without SWIFT- Header)

:20:1106210100000003
:28D:1/1
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:52A:BREPLPWXXX
:30:110621
:21:2011062100000003
:32B:PLN955,55
:57A: PKOPPLPWW16
:59:/PL22102010680000321000052142
BENEFICAIRY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:FAKTURA VAT 11/06/06
:71A:SHA
:21:2011062100000004
:32B:PLN1055,55
:59:/PL65102056980000598645620125
BENEFICAIRY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:REMITTANCE INFORMATION 1
REMITTANCE INFORMATION 2
REMITTANCE INFORMATION 3
REMITTANCE INFORMATION 4
:71A:SHA
21:2011062100000005
:32B:PLN1002,10
:59:/ PL73101010230000261395300000
BENEFICAIRY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:REMITTANCE INFORMATION 1
REMITTANCE INFORMATION 2
REMITTANCE INFORMATION 3
REMITTANCE INFORMATION 4
:71A:SHA
-}

8/9
Multiple MT 101 with multiple debit accounts
(Without SWIFT- Header)

20:1106210404010010
:28D:00001/00001
:30:110624
:21:4252170
:32B:PLN10,56
:50H:/PL64114010100000123456001001
SPOLKA POLAND SP. Z O.O.
AL. 3 MAJA 30
PL-70-214 SZCZECIN
:57A:CHEKDE81XXX
:59:/PL22102010680000321000052142
BENEFICIARY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70: REMITTANCE INFORMATION 1
REMITTANCE INFORMATION 2
REMITTANCE INFORMATION 3
REMITTANCE INFORMATION 4
:71A:SHA
:21:4252171
:32B:USD39,87
:50H:/PL37114010100000123456001002
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:57A:BKTRUS33060
:59:/123456789
BENEFICIARY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:INVOICE 56/2011
:71A:OUR
:21:4252172
:32B:EUR4,80
:50H:/PL10114010100000123456001003
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:57A:CHEKDE81XXX
:59:/DE89970400440532013000
BENEFICIARY NAME 1
BENEFICIARY NAME 2
STREET
CITY
:70:2170/A
:71A:SHA
:21:4252173
:32B:PLN2000,00
:50H:/PL64114010100000123456001001
ORDERING CUSTOMER NAME1
ORDERING CUSTOMER NAME2
STREET
CITY
:59:/PL73101010230000261395300000
ZAKLAD UBEZPIECZEN SPOLECZNYCH
BENEFICIARY NAME 2
STREET
CITY
:70:1070002939
R350535626
S20110501
:71A:SHA
-}

mBank S.A., ul. Senatorska 18, 00-950 Warszawa, entered in the commercial register of the National Court Register kept by the District Court for the Capital City of Warsaw,
12th Commercial Division, under KRS 0000025237, Tax Identification Number (NIP): 526-021-50-88, with its fully paid-up share capital amounting to PLN 168,555,904
as at 1 January 2013.

9/9