Description of the import file format
| Designation | Description |
|---|---|
| Designation of symbols | |
| nn | Max length. |
| nn! | Fixed length. |
| nn-nn | Minimal and max length. |
| nn*nn | Max number of lines multiplied by max length. |
| Symbol designation | |
| n | Numbers only(0-9). |
| a | Uppercase letters only:(A-Z). |
| с | Uppercase letters and numbers only. |
| x | "If the value of field 20 begins with transliteration feature “+”, then characters listed in General requirements of the SWIFT standard are acceptable, as well as cyrillic letters. If there is no “+” in the field 20, then characters of standard set for ELBRUS text fields are allowed: йцукенгшщзхъфывапролджэячсмитьбюЙЦУКЕНГШЩЗХЪФЫВАПРОЛДЖЭЯЧСМИТЬБЮёЁ qwertyuiopasdfghjklzxcvbnmQWERTYUIOPASDFGHJKLZXCVBNM !"#$%&'()*+,-./0123456789:;\<=>?@[]/'^_ЄєЇїЎў°№¤{ |
| e | Space. |
| D | A decimal number. Separating sign is a comma or a hyphen, and is required. There must be at least one digit before the comma. Length includes a separator. Separator of groups of digits, separating 3 digits each, is not used. |
Examples
| Designation | Description |
|---|---|
| 16x | Up to 16 characters from the set of allowed characters |
| 3!a | Always 3 letters only |
| 4*35x | Up to 4 lines, each up to 35 sets of allowed characters |
| 20!n | Always 20 digits only |
A set of permitted characters according to the SWIFT standard:
a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ‘ + CR LF Space
Format and rules for importing Payment order fields
| Field MT103/ Subfield | Field format | Value | Mandatory | Examples |
|---|---|---|---|---|
| :20: Reference Senders | 16x | +154 | No | :20:+154 |
| :26T: Code of type operation | 1!a2!n | Yes, if there is :77B: | :26T:S03 | |
| Subfield 1: constant “S” | 1!a | S | Yes | |
| Subfield 2: Type | 2!n | 03 | Yes | |
| :32A: Value Date, Currency, and Interbank Settlement Amount | 6!n3!a12n1 x2n | Yes | :32A:140710RUB200,52 :32A: 080115RUB150,00 :32A: 080115RUB150, :32A: 080115RUB150 | |
| Subfield 1: Date: | 6!n | 140710 | Yes | |
| Subfield 2: Currency | 3!a | RUB | Yes | |
| Subfield 3: Amount | 12n1x(«,» or «-»)2n | 200,52 | Yes | |
| :50a: Payer Options K and F only | with__option K: /20!n 3!a12n[.3!a9c] 3*35х with option F: /20!n 1!n/3!а12n[. 3!a9c] 3*1!n/33х | Yes | :50K:/407028102000000000 00 INN5504036333.KPP33160 | |
| 1001 Test client ООО :50F:/423018108000000000 00 1/FoDOROVA ELENA KONSTANTINOVNA 2/UL. NAGORNAa, D.12 50F:/40702810700000000225 1/INN7744001258.KPP980678956 1/KOMPANIa MEJDUNARODNYE AVIALINII 2/TVERSKAa-aMSKAa 25 3/RU/G.MOSKVA | ||||
| For option K | ||||
| Subfield 1: Account number | /20!n | 40702810200000000000 | Yes | |
| Subfield 2: INN or KIO.KPP | INN12n[.K PP4!n2!с3!n or .KPP1!n– constant 0] | Yes | ||
| Subfield 2.1: INN or KIO.KPP | INN12n | INN550403 6333 | Yes | |
| Subfield 2.2: KPP | [.KPP4!n2!с3!n или .KPP1!n– constant 0] | .KPP331601 001 | No | |
| Subfield 3: Name of the payer | 3*35х | Test client ООО | Yes, if the setting is "Fill in name of the payer from file” | |
| For option F | ||||
| Subfield 1: Account number | /20!n | 40702810200000000000 | Yes | |
| Subfield 2: | General | 1/INN77440 | ||
| (Payers name) (digital code/details) | 01258.KPP9 80678956 1/KOMPANIa MEJDUNARODNYE AVIALINII 2/TVERSK AaaMSKAa 25 3/RU/G.MOSKVA | |||
| Subfield 2.1: INN or KIO.KPP | General format: 1/[INN12n[. KPP9c]] | 1/INN77440 01258.KPP9 80678956 | ||
| Subfield 2.1.1: INN or KIO.KPP | INN12n | INN774400 1258 | Yes | |
| Subfield 2.1.2: KPP | [.KPP4!n2!с3!n or .KPP1!n– constant 0] | .KPP980678956 | No | |
| Subfield 2.2: Name of the payer | 1/33x | 1/KOMPANIa MEJDUNARODNYE AVIALINII | Yes, if the setting is "Fill in name of the payer from file” | |
| :52a: Option D only Sender Bank | //RU9!n[.20 !n] [4*35x] | Yes | :52D://RU044525700.30101 810200000000700 ZAO Raiffeisenbank Moscow city | |
| Subfield 1: ID code | General format: //2!a9!n[.20!n] | Yes | ||
| Subfield 1.1: Payment system ID of Bank of Russia | 2!a | RU | Yes | |
| Subfield 1.2: BIC | 9!n | 044525700 | Yes | |
| Subfield 1.3: Correspondent account | [.20!n] | .30101810200000000700 | No | |
| Subfield 2: Name of the payer’s bank and address | [4*35x] | ZAO Raiffeisenbank Moscow city | No | |
| :57a: (Option D only) Recipents Bank | //RU9!n[.20 !n] [4*35x] | No | :57D://RU044525593.30101810200000000593 АО ALFABANK Moscow city | |
| Subfield 1: ID code | General format: //2!a9!n[.20!n] | Yes | ||
| Subfield 1.1: Payment system ID of Bank of Russia | 2!a | RU | Yes | |
| Subfield 1.2: BIC | 9!n | 044525593 | Yes | |
| Subfield 1.3: Correspondent account | [.20n] | .30101810200000000593 | No | |
| Subfield 2: Name of the recipient’s bank and address | [4*35x] | АО ALFABANK Moscow | No | |
| :59: Recipient | [/20!n] [3!a12n[.3!a4!n2!с3!n]] 3*35х | Yes | :59:/40702810000000000008 INN7733011111.KPP773301001 ZАО Company and friends | |
| Subfield 1: Account number | [/20!n] | 40702810000000000008 | No | |
| Subfield 2: INN or KIO.KPP | General format: [INN12n[.KPP4!n2!с3!n]] | No | ||
| Subfield 2.1: INN or KIO of the recipient | INN12n | INN773301 1111 | No | |
| Subfield 2.2: KPP of the recipient | [.KPP4!n2!с3!n] | .KPP773301 001 | No | |
| Subfield 3: Recipient’s name and address | 4*35х | ZАО Company and friends | Yes | |
| :70: Payment details | 4*35x | {VO70060} Salary transfer to non-residents for November 2014 according to payroll Statement No. 1 dated 01/11/14. VAT(18) - 0-00. | Yes | '(VO70060)' Salary transfer to non-residents for November 2014 according to payroll Statement No. 1 dated 01/11/14. VAT(18) – 0-00. |
| :72: Info from the payer to recipient | General format: 6*35x | Yes | :72:/RPP/347.140708.5.ELEK. 090324.05 /UIP/1234567890123456789 | |
| 0 :72:/RPP/346.140708.5.BESP. 090324.05 /NZP/18 НДС=2343-88 :72:/RPP/346.140708.5. . 090324.05 /NZP/18 VAT=2343-88 | ||||
| Subfield 1: Details of payment document | General format: /RPP/6n.6!n.1!n.4!а[.6!n][.2!n] | Yes | ||
| Subfield 1.1: Number of payment document | 6n | 346 | Yes | |
| Subfield 1.2: Date of payment document | .6!n Format: YYMMDD | .140708 | Yes | |
| Subfield 1.3: Priority of payment document | .1!n | .5 | Yes | |
| Subfield 1.4: Payment type | .4!а | .ELEK | Yes | |
| Subfield 1.5: Date of payment | [.6!n] | .090324 | No | |
| Subfield 1.6: Type of operation | [.2!n] | .05 | No | |
| Subfield 2: UPI | /UIP/25x | 12345678901234567890 | No | :72:/RPP/11.200519.5.ELEK.02 /NPK/1 /NZP/transfer under employment contract n13 not subject to VAT |
| Subfield 3: Code of income type | /NPK/1n | 1 | No | |
| Subfield 4: Payment purpose (Continuation of field 70) | /NZP/30x4*35x | 18%VAT=2343-88 | No | |
| :77B: Mandatory reporting | General format: 3*35x Subfield format is a value between characters “N<subfield number>/” up to “/N” or end of the line. | Yes, if there is :26T: | :77B:/N10/ПЦ/N4/98765432109876543210 /N5/11250563000/N6/BF/N 7/МС.05.2013 /N8/123456/N9/01.01.2013 | |
| Subfield 1: Corresponds to field 104 of the settlement of the Bank of Russia | /N4/20!n or 1!n (constant 0) | 98765432109876543210 | Yes | |
| Subfield 2: Corresponds to field 105 of the settlement of the Bank of Russia | /N5/11n | 11250563000 | Yes | |
| Subfield 3: Corresponds to field 106 of the settlement of the Bank of Russia | /N6/2!с or 1!n (constant 0) | BF | Yes | |
| Subfield 4: Corresponds to field 107 of the settlement of the Bank of Russia | /N7/2!c.2!n. 4!n or /N7/8!х or /N7/1!n (constant 0) | МС.05.2013 | Yes | |
| Subfield 5: Corresponds to field 108 of the settlement of the Bank of Russia | /N8/15х | 123456 | Yes | |
| Subfield 6: Corresponds to field 109 of the settlement of the Bank of Russia | /N9/2!n.2!n.4!n Format: DD.MM.YY ГГ or /N9/1!n (constant 0) | 01.01.2013 | Yes | |
| Subfield 7: Corresponds to field 110 of the settlement of the Bank of Russia | /N9/2!c or /N9/1!n (constant 0) | PC | No |
MT103 Transliteration Rules
The need for reverse transliteration is determined by the value in the field :20:
- If the field contains the first character "+", then the text was transliterated into Latin when preparing the MT103 file and it is required to perform reverse transliteration when importing into Cyrillic.
- If the field does not contain the first character "+", then the text was not transliterated in Cyrillic when preparing the MT103 file and it is not required to perform transliteration during import.
Reverse transliteration rules are described in the Transliteration Table in the “Cyrillic text after reverse transliteration” column and apply to fields and subfields of message text block only.
Service symbols are transliterated without changing into corresponding service symbols.
These are not subject to reverse transliteration:
- Service part of the message: header, trailers, field numbers, field options and limiting field numbers colons, characters <Line Feed>,<Carriage Return>.
- Fields consisting of code words or other codes, in accordance with SWIFT standards.
- Fields with option A, identifying participants of settlements.
- Latin characters, enclosed in apostrophes. When transliteration from Latin into Cyrillic, apostrophes are removed.
- Code words enclosed between two slashes “/”.
Transliteration table, version RUR6
| Original Cyrillic text | Latin text after transliteration | Cyrillic text after reverse transliteration | Notes |
|---|---|---|---|
| А | A | А | |
| Б | B | Б | |
| В | V | В | |
| Г | G | Г | |
| Д | D | Д | |
| Е | E | Е | |
| Ё | о | Ё | Lowercase Latin |
| Ж | J | Ж | |
| З | Z | З | |
| И | I | И | |
| Й | i | Й | Lowercase Latin |
| К | K | К | |
| Л | L | Л | |
| М | M | М | |
| Н | N | Н | |
| О | O | О | |
| П | P | П | |
| Р | R | Р | |
| С | S | С | |
| Т | T | Т | |
| У | U | У | |
| Ф | F | Ф | |
| Х | H | Х | |
| Ц | C | Ц | |
| Ч | c | Ч | Lowercase Latin |
| Ш | Q | Ш | |
| Щ | q | Щ | Lowercase Latin |
| Ъ | x | Ъ | Lowercase Latin |
| Ы | Y | Ы | |
| Ь | X | Ь | |
| Э | e | Э | Lowercase Latin |
| Ю | u | Ю | Lowercase Latin |
| Я | a | Я | Lowercase Latin |
| ' | j | ' | Lowercase Latin |
| ’ | j | ' | Lowercase Latin |
| ‘ | j | ' | Lowercase Latin |
| ` | j | ' | Lowercase Latin |
| ' | Apostrophe in transliterated text is a sign of a keyboard switch: RUS → ENG or ENG → RUS | ||
| 0 | 0 | 0 | |
| 1 | 1 | 1 | |
| 2 | 2 | 2 | |
| 3 | 3 | 3 | |
| 4 | 4 | 4 | |
| 5 | 5 | 5 | |
| 6 | 6 | 6 | |
| 7 | 7 | 7 | |
| 8 | 8 | 8 | |
| 9 | 9 | 9 | |
| ( | ( | ( | |
| ) | ) | ) | |
| ? | ? | ? | |
| + | + | + | |
| № | n | № | Lowercase Latin |
| # | n | № | Lowercase Latin |
| % | р | % | Lowercase Latin |
| & | d | & | Lowercase Latin |
| , | , | , | |
| / | / | / | |
| - | - | - | |
| . | . | . | |
| : | : | : | |
| Space | Space | Space | Space |
| ! | b | ! | Lowercase Latin |
| $ | s | $ | Lowercase Latin |
| ; | v | ; | Lowercase Latin |
| \ | / | / | |
| / | / | ||
| _ | z | _ | Lowercase Latin |
| = | r | = | Lowercase Latin |
| < | ( | ( | |
| > | ) | ) | |
| [ | ( | ( | |
| ] | ) | ) | |
| See exceptions in | |||
| { | ( | ( | comments |
| } | ) | ) | |
| ” | m | ” | Lowercase Latin |
| “ | m | ” | Lowercase Latin |
| « | m | ” | Lowercase Latin |
| » | m | ” | Lowercase Latin |
| * | f | * | Lowercase Latin |
| @ | f | * | Lowercase Latin |
| ^ | f | * | Lowercase Latin |
| ~ | f | * | Lowercase Latin |
Comments
- Apostrophe encountered in the original text must be transliterated by lowercase letter “j”. Apostrophe encountered in the transliterated text is the sign of a keyboard switch: RUS/ENG – ENG/RUS.
- Curly brackets encountered in the original text must be transliterated to round brackets, which must not be converted by reverse transliteration. The exception is the use of curly brackets when indicating the type of currency transaction code in payment purpose. In messages, MT103 applies only to field 70. Based on clarifications of the Bank of Russia, symbols of curly brackets, which limit coded information of the currency transaction in the field “Payment purpose” of the Payment Order, must be replaced by round brackets via transliteration from Cyrillic to Latin in field 70 of SWIFT message. In case of reverse transliteration, round brackets are replaced by curly brackets. The base is the combination of characters arranged as follows, appear from the first position of field 70 of SWIFT message: apostrophe — round bracket – VO < Code> [PS] — round bracket —apostrophe. Optional subfield [PS<transaction passport number>] does not apply after 6 months from the date of approval of this document.
- There is no reverse transliteration rule for “W” and “w” characters in the transliteration table, but the list of allowed SWIFT characters contains them. It is assumed that if MT103 file contains these characters in the fields and subfields of the text block, they will not be transliterated into Cyrillic.