Description of export formats for bank statements
Description of MT940 and MT942 statement formats
About symbol legends:
LENGTH
| Legend | Description |
|---|---|
| nn | Maximum length |
| nn! | Fixed length |
| nn-nn | Minimum and maximum length |
| nn*nn | Maximum number of lines multiplied by maximum length |
TYPES OF SYMBOLS
| Legend | Description |
|---|---|
| n | Only numbers (0-9) |
| a | Only uppercase Latin letters (A-Z) |
| c | Only capital letters and numbers |
| x | Allowed characters for the table «Х» |
| e | Space |
| d | Decimal number (separating sign - comma must be specified and at least one digit before comma; length includes comma). Delimiter of digit groups that delimits each 3 characters is not applied. |
ALLOWED CHARACTERS FOR TABLE «Х»
a-z A-Z 0-9 - / : ( ) . , ' + ? Space
BRACKETS
| Legend | Description |
|---|---|
| [ ] | Optional subfield |
| Block delimiter |
CODE WORDS AND IDENTIFIERS
Only capital letters and numbers
About fields and subfields
For all default fields and subfields (unless otherwise specified in a particular case), the following rule applies:
- the field contains ALL subfields in the specified sequence without separating characters (except for “/” and “//”, if required).
About square brackets:
Consider the following example.
Example of the format of some field: 16х[/4x]
Square brackets within which an expression is specified to indicate that this subfield is optional.
Read the example above as follows:
there should be 16 characters of X set, after that “/” may or may not follow with 4 characters of X formats.
Thus, the valid character set for this format will be:
- abcdghskulooredf/er83
- qwer MNLK2eeeqqq Invalid characters will be:
- qwertyasdfghjklmmndddjerrrew
- abcdghskulooredf/er83sdsds
Square brackets delimiting the format of a subfield indicate that it is optional in that field. For example, if the format of a field is — 16х[/4x], it must contain up to 16 characters of set X, and the next 4 characters of set X, preceded by slash “/” are optional and therefore may be missing. The field format can be represented with two or more lines: 3!n 6!n In this case, information lines must be delimited with characters «CrLf». (CrLf is in fact a line delimiter.)
About the SWIFT statement format (mt940, mt942) what is responsible for and how it is issued
МТ 940 client account statement (SWIFT-RUR format).
| Status | Field number | Field name | Content/Options |
|---|---|---|---|
| M | 20 | Transaction reference | 16x |
| O | 21 | Related reference | 16x |
| M | 25 | Account number | No letter option or P |
| M | 28C | Statement number/Order number | 5n |
| M | 60a | Opening balance | F or M |
---> | |||
| O | 61 | Account activity line | 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x] [34x] |
| O | 86 | Information for the account holder | 6*65x |
| ---! | |||
| M | 62 | Closing balance (accounted funds) | F or M |
| O | 64 | Closing available balance (available funds) | 1!a6!n3!a15d |
---> | |||
| O | 65 | Future available balance | 1!a6!n3!a15d |
| ---! | |||
| O | 86 | Information for the account holder 6*65x |
---> means the beginning of a repeating block
---! means the end of a repeating block
M = Mandatory, O = Optional
The table gives an overview of the message.
Field 20
forma 2!a6!n6!n
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 | 2!a | yes | "GL" Constant |
| 2 Statement date | 6!n | yes | Statement date [YYMMDD] |
| 3 Serial number of the main statement | 6!n | yes | Number from 000001 to 999999 in a cycle (each statement +1) |
Field 25
format [11с]/20!n/3!a
subfield delimiter - constant "/"
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Bank SWIFT code | 11c | No | "RZBMRUMM" Constant |
| 2 20-characters account number | 20!n | Yes | [Statement: Account №] |
| 3 Account currency ISO 4217 (letters) | 3!a | No | |
| 4 BIC of the Bank of the current account | 9!n | No |
Field 28C
format 5!n
there is no subfield delimiter
| subfield | format | mandatory | value | note |
|---|---|---|---|---|
| 1 Statement number | 5!n | Yes | 5 characters, if less, the missing initial positions are replaced with "0" |
Field 60a
with suffix F when uploading a statement in one message
with suffix M when dividing a statement into several messages
format 1!a6!n3!a15d
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Debit/Credit | 1!A | Yes | Constant "C" if Opening balance >=0 Constant "D" if Opening balance <0 |
| 2 Date of Opening balance | 6!N | No | Statement date [YYMMDD] |
| 3 Account currency ISO 4217 | 3!A | Yes | |
| 4 Value of Opening balance | 15D [rub, kop] | Yes |
In the first or only statement message, field 60 is used with option F to indicate the initial opening balance. If the statement is represented with more than one message, in all messages except the first one, this field is used with option M and contains an intermediate opening balance.
Field 61 (Account activity line) (L1 - first line, L2 - second line):
there is no subfield delimiter
format 6!n[4!n]1!a15d1!a3!c16x[//16x] [34x]
| line | subfield | format | mandatory | value |
|---|---|---|---|---|
| L1 | 1 Value date | 6!n | Yes | [YYMMDD] |
| L1 | 2 Entry date | 4!N | No | Document date [MMDD] |
| L1 | 3 Debit/Credit | 1!A | Yes | "D" or "C" |
| L1 | 4 Entry amount | 15D | Yes | [rub, kop] |
| L1 | 5 Transaction type code | 1!A3!C | Yes | [ FXXX ] или [ NXXX ] |
| L1 | 6 Reference for the account holder | 16X | Yes | |
| L1 | 7 Reference of the account service provider | [//16X] | No | |
| L2 | 8 Additional information | 34X | No | Value Condition[Statement.Appendix: PNAR Flag] NOT filled in |
Field 86 (Information for the account holder) in the format “MT940-SEPA” (sepa by default):
subfield delimiter - constant “?”, field size 86 6*65X
| subfield | format | mandatory | value | example (constants in bold) |
|---|---|---|---|---|
| GVC Transaction code | 3!N | Yes | Yes | 020?here and below, the last question mark is the subfield delimiter |
| 00 GVC code explanation | 27A | No | Constant "00" + + GVC code explanation from subfield 1 | 00Payment order? |
| 10 Registration number | 10N | No | Constant "10" | 10? |
| 20-29 Payment reference | 27 max. 10*27C including signature | No | Payment reference divided into (no more than) 10 parts of 27 characters each with constants "20" - "29" at the beginning and a delimiter with constant "?" at the end of each part (the last part ends with a delimiter between subfields) | 20payment of insurance contributions for?21 compulsory medical ?22 insurance for Q3 2020 VA?23С free ?24?25?26?27?28?29? |
| 30 SWIFT BIC of the counterparty's bank | 12C | No | Constant "30" + BIC | 30987654321? |
| 31 IBAN of the counterparty | 34C | No | Constant "31" + Account number of the counterparty | 314070281000000000 0001? |
| 32-33 Name of the counterparty | 27max 2*27C | No | Name of the counterparty divided into (no more than) 2 parts of 27 characters each with constants "32" and "33" at the beginning and a delimiter with constant "?" at the end (the last part ends with a delimiter between subfields) | 32FTD in the Voronezh region ? 33(IFTS of Russia for Levoberezhno? |
| 34 SEPA return codes | 3!N | No | Constant "34" | 34? |
| 35 | 27X | No | If UPI is available, Constant "35" + first 27 characters of UPI | 350? or 3554954985423? |
| 60 TIN of the counterparty | 27C | No | Constant "60" + TIN of the counterparty | 601234567890? |
| 61 Document number | 27C | No | Constant "61" + Document number | 6154242? |
| 62 SPC-code | 27C | No | Constant "62" + SpeedUPC code | 62? |
| 63 Payment reference | 27C | No | Constant "63" + continuation of fields 20-29(if there is not enough space) + constant "Income code" + space + Income code | Income code ? |
Field 86 in NZP mode "Old format (/ORD/[INN][OrderingName]/NPP/[DocNumber]/NPK/[IncomeCode]/[NZP/[Details of payment])"
field size 6*65X Subfield delimiter "/"
| subfield | format | mandatory | value | example |
|---|---|---|---|---|
| 1 Information about the payer | 2*65X | No | Constant = "/ORD/" + If there is a TIN of the counterparty OR a Name of the counterparty: If there is a TIN of the counterparty: "INN"+(space)+TIN of the counterparty + If available Name of the counterparty: "INN"+(space)+TIN of the counterparty | /ORD/INN 3663052143 FTD in the Voronezh region (IFTS of Russia for Levoberezhno) |
| 2 SPC code | 4 X | No | Constant "/SPC/" + SpeedUPC code | |
| 3 Payment number | 6X | No | Constant "/NPP/"+Payment number | /NPP/393 |
| 4 UPI | 27Х | No | Constant /UIP/+ UPI | /UIP/0 |
| 5 Code payment reference | 1N | No | Constant "/NPK/" + Income code | |
| 6 Payment reference | 4*65X | No | Constant "/NZP/" + Payment reference | /NZP/payment of insurance contributions for compulsory medical insurance for Q3 2020 VAT free |
Field 62 (Closing balance)
with suffix F when uploading a statement in one message M when deviding a statement into several messages:
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Credit/Debit | 1!A | Yes | Constant “C” if Closing balance >= 0 Constant “D” if Closing balance < 0 |
| 2 Date | 6!N | Yes | Statement date [YYMMDD] |
| 3 Account currency ISO 4217 | 3!A | Yes | |
| 4 Value of Closing balance | 15D | Yes | [rub, kop] |
Field 64 (Closing available balance) (generated for uploading to one file OR the final message in the series):
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Credit/Debit | 1!A | Yes | Константа "C" - если Доступный остаток >=0, Constant D if available balance <0 |
| 2 Date of Closing balance | 6!N | Yes | [YYMMDD] |
| 3 Account currency ISO 4217 | 3!A | Yes | |
| 4 Value of available balance | 15D | Yes | [Statement: Available balance] |
Examples of mt940
Example 1 Extract without SEPA transliteration
Description:
The statement was unloaded as a whole one, without dividing into parts.
Date of the statement - 21.10.14 (YY.MM.DD)
Rouble account of a LLC
Opening balance - 0 roubles
The statement contains 3 rouble payment orders (GVC 020, SWIFT NTRF):
:20:GL211014000001
:25:RZBMRUMM/4070281000000XXXXXXX
:28C:00222
:60F:C211014RUB0,00
:61:2101410142D1000,00NTRF3ce-9553e9871837//190321PCIN044330
P/O 223,4070281000000XXXXXY
:86:020?00Payment Order?10?20VAT 12%?21?22?23?24?25?26?27?28?29?30044 525700?314070281000000XXXXXY?32ООО ХХХХХХХХ?33?34?35?60123 4567890?61705?62?63Income code ?
:61:2009220922D1000,00NTRF3ce-9553e9871837//190321PCIN044335
P/O 223,4070281000000XXXXXY
:86:020?00Payment Order?10?20VAT 12%?21?22?23?24?25?26?27?28?29?30044 525700?3140702810700001470239?32ООО ХХХХХХХХ?33?34?35?60123 4567890?61705?62?63Income code ?
:61:2009220922C1000,00NTRF3ce-9553e9871837//190321PCIN046130
P/O 223,40702810000001459280
:86:020?00Payment Order?10?20VAT 12%?21?22?23?24?25?26?27?28?29?30044 525700?3140702810700001470239?32ООО ХХХХХХХХ?33?34?35?60123 4567890?61705?62?63Income code ?
:62F:D200922RUB3000,00
:64:C200922RUB11005,77
Example 2 Statement without transliteration in old format (nzp)
Description:
Service account 4070281000000XXXXXX
The statement was unloaded as a whole one, without dividing into parts.
Statement date - 21.10.14 (YY.MM.DD)
Rouble account of a LLC
Opening balance - 0 roubles
The statement contains 3 rouble payment orders(GVC 020, SWIFT NTRF):
:20:GL211014000001
:25:RZBMRUMM/4070281000000XXXXXXX
:28C:00222
:60F:C211014RUB0,00
:61:2101410142D1000,00NTRF3ce-9553e9871837//190321PCIN044323
P/O 223,4070281000000XXXXXXY
:86:/ORD/INN 1234567890 УФК по Воронежской области (ИФНС России по Левобережному району г.Воронежа)/NPP/706/UIP/0/NZP/оплата УСН за 4 квартал 2020 г. НДС не облагается
:61:2009220922D1000,00NTRF3ce-9553e9871837//190321PCIN044345
P/O 223,4070281000000XXXXXXY
:86:/ORD/INN 1234567890 УФК по Воронежской области (ИФНС России по Левобережному району г.Воронежа)/NPP/706/UIP/0/NZP/оплата УСН за 4 квартал 2020 г. НДС не облагается
:61:2009220922C1000,00NTRF3ce-9553e9871837//190321PCIN044227
P/O 223,4070281000000XXXXXXY
:86:/ORD/INN 1234567890 УФК по Воронежской области (ИФНС России по Левобережному району г.Воронежа)/NPP/706/UIP/0/NZP/оплата УСН за 4 квартал 2020 г. НДС не облагается
6804648?61706?62?63Код дохода ?
:62F:D200922RUB3000,00
:64:C200922RUB11005,77
МТ 942 Interim transaction report (SWIFT-RUR format).
| Status | Field number | Field name | Content/Options | № | № in SWIFT UHB |
|---|---|---|---|---|---|
| M | 20 | Transaction reference | 16х | 1 | 1 |
| O | 21 | Related reference | 16х | 2 | 2 |
| M | 25 | Account number | 35х | 3 | 3 |
| M | 28С | Statement number/Order number | 5n[/5n] | 4 | 4 |
| M | 34F | Determination of the minimum debit amount or debit and credit amount | 3!a[1!a]15d | 5 | 5 |
| O | 34F | Determination of the minimum loan amount. | 3!a[1!a]15d | 6 | 6 |
| M | 13D | Date/time indication | 6!n4!n1!x4!n | 7 | 7 |
---> | |||||
| O | 61 | Account activity line | 6!n[4!n]2a[1!a]15d1!а3!c16x[//16x] [34x] | 8 | 8 |
| O | 86 | Information for the account holder | 6*65х | 9 | 9 |
| ---! | |||||
| O | 90D | Number and amount of entries | 5n3!a15d | 10 | 10 |
| O | 90C | Number and amount of entries | 5n3!a15d | 11 | 11 |
| О | 86 | Information for the account holder | 6*65х | 12 | 12 |
| M = Mandatory, O = Optional |
Field 20
format 2!a6!n6!n
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 | 2!a | Yes | GL Constant |
| 2 Statement date. | 6!n | Yes | Statement date [YYMMDD] |
| 3 Serial number of the main statement | 6!n | Yes | Number from 000001 to 999999 in a cycle (each statement +1) |
Field 25
format [11с]/20!n/3!a
subfield delimiter - constant "/"
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Bank SWIFT code | 11c | No | "RZBMRUMM" Constant |
| 2 20-characters account number | 20!n | Yes | |
| 3 Account currency ISO 4217 (letters) | 3!a | No | |
| 4 BIC of the Bank of the current account | 9!n | No |
Field 28C
format 5!n
there is no subfield delimiter
| subfield | format | mandatory | value | note |
|---|---|---|---|---|
| 1 Statement number | 5!n | Yes | 5 characters, if less, the missing initial positions are replaced with “0” |
Field 34F
format 3!a[1!a]15d
there is no subfield delimiter
| subfield | format | mandatory | value | note |
|---|---|---|---|---|
| 1 Currency | 3!a | Да | 5 characters, if less, the missing initial positions are replaced with “0” | |
| 1 Debit or credit | 5!n | No | D - debit, С- credit | |
| 1 Amount | 5!n | Yes |
Field 13D
Current date/time
format 6!n4!n1!x4!n
there is no subfield delimiter
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 Date | 6!n | Yes | [YYMMDD] |
| 2 Time | 4!n | Yes | Time [HH:mm] |
| 3 Time zone delimiter | 1!x | Yes | + or - |
| 4 | 4!n | Yes | [Z] 0300 for Moscow |
Field 61 (Account activity line) (L1 - first line, L2 - second line):
there is no subfield delimiter
format 6!n[4!n]1!a15d1!a3!c16x[//16x]
[34x]
| line | subfield | format | mandatory | value |
|---|---|---|---|---|
| L1 | 1 Value date | 6!n | Yes | [YYMMDD] |
| L1 | 2 Entry date | 4!N | No | Document date [MMDD] |
| L1 | 3 Debit/Credit | 1!A | Yes | "D" or "C" |
| L1 | 4 Entry amount | 15D | Yes | [rub, kop] |
| L1 | 5 Transaction type code | 1!A3!C | Yes | [ FXXX ] or [ NXXX ] |
| L1 | 6 Reference for the account holder | 16X | Yes | |
| L1 | 7 Reference of the account service provider | [//16X] | No | |
| L2 | 8 Additional information | 34X | No | Value Condition[Statement.Appendix: PNAR Flag] NOT filled in |
Field 86 (Information for the account holder) in the format “MT940-SEPA” (sepa by default):
subfield delimiter - constant “?”, field size 86 6*65X
| subfield | format | mandatory | value | example (constants in bold) |
|---|---|---|---|---|
| GVC Transaction code | 3!N | Yes | Yes | 020?here and below, the last question mark is the subfield delimiter |
| 00 GVC code explanation | 27A | No | Constant "00" + + GVC code explanation from subfield 1 | 00Payment order? |
| 10 Registration number | 10N | No | Constant "10" | 10? |
| 20-29 Payment reference | 27 max. 10*27C including signature | No | Payment reference divided into (no more than) 10 parts of 27 characters each with constants "20" - "29" at the beginning and a delimiter with constant "?" at the end of each part (the last part ends with a delimiter between subfields) | 20payment of insurance contributions for?21 compulsory medical ?22 insurance for Q3 2020 VA?23С free ?24?25?26?27?28?29? |
| 30 SWIFT BIC of the counterparty's bank | 12C | No | Constant "30" + BIC | 30987654321? |
| 31 IBAN of the counterparty | 34C | No | Constant "31" + Account number of the counterparty | 314070281000000000 0001? |
| 32-33 Name of the counterparty | 27max 2*27C | No | Name of the counterparty divided into (no more than) 2 parts of 27 characters each with constants "32" and "33" at the beginning and a delimiter with constant "?" at the end (the last part ends with a delimiter between subfields) | 32FTD in the Voronezh region ? 33(IFTS of Russia for Levoberezhno? |
| 34 SEPA return codes | 3!N | No | Constant "34" | 34? |
| 35 | 27X | No | If UPI is available, Constant "35" + first 27 characters of UPI | 350? or 3554954985423? |
| 60 TIN of the counterparty | 27C | No | Constant "60" + TIN of the counterparty | 601234567890? |
| 61 Document number | 27C | No | Constant "61" + Document number | 6154242? |
| 62 SPC-code | 27C | No | Constant "62" + SpeedUPC code | 62? |
| 63 Payment reference | 27C | No | Constant "63" + continuation of fields 20-29(if there is not enough space) + constant "Income code" + space + Income code | Income code ? |
Field 90D. Number and amount of entries
Number and amount of debit entries
there is no subfield delimiter
format 5n3!a15d
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 number | 5n | Yes | Number of debit entries |
| 2 currency | 3!a | Yes | example: 0RUB0,00 |
| 3 amount | 15d | Yes | 1RUB1000,00 |
Field 90C. Number and amount of entries
Number and amount of credit entries
there is no subfield delimiter
format 5n3!a15d
| subfield | format | mandatory | value |
|---|---|---|---|
| 1 number | 5n | Yes | Number of credit entries |
| 2 currency | 3!a | Yes | example: 0RUB0,00 |
| 3 amount | 15d | Yes | 1RUB1000,00 |
Description of 1C statement format
For statements in 1C format, the ClientBank format is used.
Up-to-date information on the specification description is provided on 1C official website.