Swiftstandard

SWIFTStandards
Category 2 Financial Institution Transfers

For SWIFTStandards MT October 2007
Message Reference Guide

Standards Release Guide - February 2007
This reference guide contains the category 2 message text standards, including a detailed description of the scope, the format specifications, the rules, the guidelines, and the field specifications of each message type .
5 February 2007
Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007
Copyright
Copyright S.W.I.F.T. SCRL ("SWIFT"), avenue Adle 1, B-1310 La Hulpe, Belgium, or its licensors, 2007 . All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices. Confidentiality This publication may contain SWIFT or third-party confidential information. Do not disclose this publication outside your organisation without the prior written consent of SWIFT. Disclaimer The information in this publication may change from time to time. You must always refer to the latest available version. SWIFTStandards Intellectual Property Rights (IPR) Policy - End-User License Agreement SWIFTStandards are licensed subject to the terms and conditions of the SWIFTStandards IPR Policy - End-User License Agreement, available at www.swift.com > Standards > More information. Translations The English version of SWIFT documentation is the only official version. Trademarks and Patents SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady, and Accord are trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived service and product names, including SWIFTSolutions, SWIFTWatch, and SWIFTSupport are tradenames of S.W.I.F.T. SCRL. SWIFT is the trading name of S.W.I.F.T. SCRL . Other product or company names in this publication are tradenames, trademarks, or registered trademarks of their respective owners. 5 February 2007
Message Reference Guide - Standards Release Guide - February 2007
Introduction
Introduction
Summary of Changes
Added Message Types
n.a.
Removed Message Types

n.a.
Modified Message Types

MT 200 MT 201 MT 202 MT 203 MT 205 MT 206 MT 207 MT 210 MT 256
5 February 2007
Category 2 Message Types

The following table lists all message types defined in category 2. For each message type, there is a short description, an indicator whether the message type requires authentication (Y/N), the maximum message length on input (2,000 or 10,000 characters), whether the use of the message requires registration with SWIFT for use in a message user group (Y/N) and wether value date ordering (VDO) can be requested for the message (Y/N). Value date ordering criteria are described in section 5.4.6 of the General Information volume.
MT
MT Name Financial Institution Transfer for its Own Account Multiple Financial Institution Transfer for its Own Account General Financial Institution Transfer Multiple General Financial Institution Transfer Financial Markets Direct Debit Message Financial Institution Transfer Execution Cheque Truncation Message Request for Financial Institution Transfer
Purpose Requests the movement of the Senders funds to its account at another financial institution Multiple of the MT 200
Authen.
Max. Length 2,000
MUG
VDO
200
201
2,000
202 203
Requests the movement of funds between financial institutions Multiple of the MT 202
Y Y
2,000 2,000
N N
Y Y
204 205 206
Claims funds from SWIFT member banks Further transmits a transfer request domestically Conveys information about one or more truncated cheques in order to debit or obtain credit under usual reserve Requests to debit an ordering financial institutions account held at the receiving financial institution or the account servicing financial institution Notifies the Receiver that it will receive funds for the Senders account Informs the Sender of one or more previously sent MT 206s of non-payment of one or more truncated cheques. It may also be used to specify dishonoured items that result in reversing a previous payment settlement Advises an account owner of charges, interest or other adjustments
Y Y Y
2,000 2,000 10,000
Y N Y
Y Y Y
207
10,000
210 256
Notice to Receive Advice of Non-Payment of Cheques
Y Y
2,000 10,000
N Y
Y Y
290
Advice of Charges, Interest and Other Adjustments
2,000
Category 2 Message Types
MT
MT Name Request for Payment of Charges, Interest and Other Expenses Request for Cancellation Queries Answers
Purpose Requests payment of charges, interest or other expenses Requests the Receiver to consider cancellation of the message identified in the request Requests information relating to a previous message or amendment to a previous message Responds to an MT 295 Queries message or an MT 292 Request for Cancellation or other message where no specific message type has been provided for a response Contains formats defined and agreed to between users and for those messages not yet live Contains information for which no other message type has been defined
Authen.
Max. Length 2,000
MUG
VDO
291
292 295 296
Y Y Y
2,000 2,000 2,000
N N N
N N N
298 299
Proprietary Message Free Format Message
Y Y
10,000 2,000
N N
N N
Note:
A Message User Group (MUG), for the purposes of this book, is a group of users who have voluntarily agreed to support the specified message type and have registered with SWIFT to send or receive the specified message type. These messages are indicated in the preceding table in the column MUG. Registration is free of charge. To register to use one or more message types, submit a registration request (Register to a Message User Group) through www.swift.com. To withdraw from a MUG, use the Deregister from a Message User Group request. These forms are available on www.swift.com > Ordering & Support > Ordering. To get the list of other members of a particular MUG, send an MT 999 to the Customer Implementation team (SWHQBEBBCOS).
5 February 2007
Euro - Impact on Category Message Standards

See the SWIFTStandards General Information volume for full details of the Euro-Related Information (ERI) and the impact on SWIFTStandards FIN message types.
MT 200
MT 200 Financial Institution Transfer for its Own Account

MT 200 Scope
This message type is sent by an account owner to one of its account servicing institutions. It is used to request the movement of funds from an account that the Receiver services for the Sender to an account that the Sender has, in the same currency, with another financial institution.
MT 200 Format Specifications

MT 200 Financial Institution Transfer for its Own Account Status M M O O M O Tag 20 32A 53B 56a 57a 72 Field Name Transaction Reference Number Value Date, Currency Code, Amount Senders Correspondent Intermediary Account With Institution Sender to Receiver Information M = Mandatory O = Optional 16x 6!n3!a15d [/1!a][/34x] [35x] A or D A, B or D 6*35x Content/Options No. 1 2 3 4 5 6
MT 200 Network Validated Rules

There are no network validated rules for this message type.
MT 200 Usage Rules

The beneficiary of this transfer is always the Sender. The Receiver and the account with institution are normally in the same country. In those cases where the account owner wishes to instruct its account servicing institution either to transfer funds between two accounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its several accounts at an account with institution, the MT 202 General Financial Institution Transfer or the MT 203 Multiple Financial Institution Transfer must be used. In those cases where the sender wants the account servicing institution to do a book transfer the MT 202 General financial institution transfer or the MT 203 Multiple financial institution transfer must be used.
MT 200 Field Specifications
5 February 2007
1. Field 20: Transaction Reference Number

FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).
2. Field 32A: Value Date, Currency Code, Amount

FORMAT Option A 6!n3!a15d (Date) (Currency) (Amount)
PRESENCE Mandatory DEFINITION This field specifies the value date, currency and amount to be transferred. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).
3. Field 53B: Senders Correspondent

FORMAT Option B [/1!a][/34x] [35x] (Party Identifier) (Location)
MT 200
PRESENCE Optional DEFINITION This field specifies the account of the Sender which is to be debited. USAGE RULES In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Sender and the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with the Party Identifier only. When there is a single direct account relationship, in the currency of the transaction, between the Sender and the Receiver, and this is the account to be used for reimbursement, field 53B must not be present.
4. Field 56a: Intermediary

FORMAT Option A Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Name & Address)
PRESENCE Optional DEFINITION This field identifies a party between the Receiver and the account with institution through which the transaction must pass. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code)
5 February 2007
HK IE IN IT PL PT RT SC ZA
3!n 6!n 11!c 10!n 8!n 8!n
Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
6!n 6!n
UK Domestic Sort Code South African National Clearing Code
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code
10
MT 200
RT RU SC SW SW ZA 9!n 6!n 3..5n 6!n 6!n
Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
5. Field 57a: Account With Institution

FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address)
5 February 2007
11
PRESENCE Mandatory DEFINITION This field identifies the financial institution to which the funds (owned by the Sender and originally placed with the Receiver) are to be transferred. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
12
MT 200
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT RT RU SC SW SW ZA 9!n 6!n 3..5n 6!n 6!n 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
5 February 2007
13
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
6. Field 72: Sender to Receiver Information

FORMAT 6*35x (Narrative - Structured Format)
The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]]
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party identified in the field. CODES One or more of the following codes may be used, placed between slashes (/): ACC INT PHON Instructions following are for the account with institution Instructions following are for the intermediary Please advise account with institution by phone
14
MT 200
PHONIBK REC TELE TELEIBK
Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication.
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
MT 200 Examples
Example 1 Financial Institution Transfer for its Own Account with an Account With Institution
Narrative Value 24 May 2002 UBS, Zrich requests ABN Amro Bank, Amsterdam, to transfer euro 1,000,000 to its account at ING Bank, Amsterdam. The reference for this transaction is 23/200516DEV. Information Flow
5 February 2007
15
SWIFT Message Explanation Sender Message type Receiver Message text Transaction reference number Value date/currency code/amount Account with institution (1) End of message text/trailer 20:23/200516DEV 32A:020524EUR1000000, 57A:INGBNL2A UBSWCHZH80A 200 ABNANL2A Format
16
MT 200
(1) The Senders account at the account with institution is to be credited with the funds.
Example 2 Financial Institution Transfer for its Own Account with an Intermediary
Narrative Value 24 May 2002, Bank Austria, Vienna, requests Chase Manhattan Bank, New York, to transfer US Dollars 1,000,000 to its account at Citibank N.A., Miami, through Citibank N.A., New York. Bank Austria requests Chase to debit account 34554-3049 for this transfer, using reference 39857579. Information Flow
SWIFT Message Explanation Sender BKAUATWW Format
5 February 2007
17
Explanation Message type Receiver Message text Transaction reference number Value date/currency code/amount Senders correspondent (1) Intermediary Account with institution (2) End of message text/trailer :20:39857579 200 CHASUS33
Format
:32A:020524USD1000000, :53B:/34554-3049 :56A:CITIUS33 :57A:CITIUS33MIA
(1) The Senders account which is to be debited at Chase Manhattan Bank, New York. (2) The Senders account at the account with institution which is to be credited with the funds in the transfer.
18
MT 201
MT 201 Multiple Financial Institution Transfer for its Own Account

MT 201 Scope
This multiple message type is sent by an account owner to one of its account servicing institutions. It is used to request the movement of funds from an account that the Receiver services for the Sender to several accounts that the Sender has, in the same currency, with other financial institutions.

The MT 201 consists of two types of sequences: The first sequence provides details of the transaction between the Sender and Receiver, ie, the value date and total amount to be transferred, the Senders correspondent and any other information about this transaction, as necessary. The second sequence, which must appear at least twice and, in order to expedite processing, not more than ten times. It provides details of each transaction between the Receiver and a financial institution to which the funds will be transferred. Each sequence includes a TRN, the amount and currency code to be transferred, the identification of the financial institution(s) to which the funds will be transferred and any other information about the transaction, as necessary. MT 201 Multiple Financial Institution Transfer for its Own Account Status M M O O -----> M M O M O -----| M = Mandatory O = Optional 20 32B 56a 57a 72 Transaction Reference Number Currency Code, Amount Intermediary Account With Institution Sender to Receiver Information 16x 3!a15d A or D A, B or D 6*35x 5 6 7 8 9 Tag 19 30 53B 72 Sum of Amounts Value Date Senders Correspondent Sender to Receiver Information Field Name 17d 6!n [/1!a][/34x] [35x] 6*35x Content/Options No. 1 2 3 4
5 February 2007
19

C1 The amount in field 19 must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01). C2 The currency code in the amount field 32B must be the same for all occurrences of this field in the message (Error code(s): C02). C3 The repetitive sequence must appear at least twice, but not more than ten times (Error code(s): T11,T10).
MT 201 Usage Rules

Where the account owner wishes to instruct its account servicing institution either to transfer funds between two accounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its several accounts at an account with institution, the MT 202 General Financial Institution Transfer or the MT 203 Multiple General Financial Institution Transfer must be used. In those cases where the sender wants the account servicing institution to do a book transfer the MT 202 General financial institution transfer or the MT 203 Multiple financial institution transfer must be used. The beneficiary of each transfer is always the Sender.

1. Field 19: Sum of Amounts
FORMAT 17d (Amount)
PRESENCE Mandatory DEFINITION This field contains the sum of all amounts appearing in each occurrence of field 32B in the message. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32B (Error code(s): C03,T40,T43).
2. Field 30: Value Date

FORMAT 6!n (Date)
20
MT 201
PRESENCE Mandatory DEFINITION This field specifies the value date for all transactions in the message. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).
3. Field 53B: Senders Correspondent

PRESENCE Optional DEFINITION This field specifies the account of the Sender which is to be debited. USAGE RULES This field should be used when the Receiver services more than one account for the Sender in the currency of the transactions. In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Sender and the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with the Party Identifier only. When there is a single direct account relationship, in the currency of the transaction, between the Sender and the Receiver, and this is the account to be used for reimbursement, field 53B must not be present.

5 February 2007
21
PRESENCE Optional DEFINITION This field specifies additional information which applies to every transaction in the message. CODES One or more of the following codes may be used, placed between slashes (/): ACC INT PHON PHONIBK REC TELE TELEIBK Instructions following are for the account with institution Instructions following are for the intermediary Please advise account with institution by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
22
MT 201

FORMAT 16x
PRESENCE Mandatory DEFINITION The Transaction Reference Number (TRN) specifies the reference assigned by the Sender to unambiguously identify the message. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES A different TRN must be assigned to each transaction in the message.
6. Field 32B: Currency Code, Amount

FORMAT Option B 3!a15d (Currency) (Amount)
PRESENCE Mandatory DEFINITION This field specifies the currency and amount to be transferred in each individual transaction within the message. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).

5 February 2007
23
PRESENCE Optional DEFINITION This field specifies the party between the financial Receiver and the account with institution through which the transaction must pass to reach the account with institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
24
MT 201
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations.(Error code(s): C05).
5 February 2007
25
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

PRESENCE Mandatory DEFINITION This field specifies the financial institution to which the funds (owned by the Sender and originally placed with the Receiver) are to be transferred. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code
26
MT 201
BL CC ES FW GR HK IE IN IT PL PT RT SC ZA
8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n
German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
6!n 6!n
CODES with option D: AT AU BL CC CH CP ES FW GR HK 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong
5 February 2007
27
IE IN IT PL PT RT RU SC SW SW ZA
6!n 11!c 10!n 8!n 8!n
Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
9!n 6!n 3..5n 6!n 6!n
Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
28
MT 201

PRESENCE Optional DEFINITION This field contains additional information which applies to the transaction specified. CODES One or more of the following codes may be used, placed between slashes (/): ACC INT PHON PHONIBK REC TELE TELEIBK Instructions following are for the account with institution Instructions following are for the intermediary Please advise account with institution by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended.
5 February 2007
29
Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
MT 201 Examples
Narrative Value 28 May 2002, UBS, Zrich requests ABN Amro Bank, Amsterdam, to transfer euro 61,000 to its accounts at the following financial institutions: ING Bank, Amsterdam SNS Bank Nederland NV, Amsterdam ABN Amro Bank, Rotterdam Crdit Lyonnais, Paris Deutsche Bank AG, Frankfurt by telex through ING Bank, Amsterdam EUR EUR EUR EUR EUR 5000, 7500, 12500, 6000, 30000,
Information Flow
30
MT 201
SWIFT Message Explanation Sender Message type Receiver UBSWCHZH80A 201 ABNANL2A Format
5 February 2007
31
Explanation Message text Sum of amounts in the message Value date Transaction reference number (1) (1) Currency code and amount Account with institution Transaction reference number (2) (1) Currency code and amount Account with institution Transaction reference number (3) (1) Currency code and amount Account with institution Transaction reference number (4) (1) Currency code and amount Account with institution Transaction reference number (5) (1) Currency code and amount Intermediary Account with institution Sender to Receiver information End of message text/trailer :19:61000, :30:020528 :20:1234/22 :32B:EUR5000, :57A:INGBNL2A :20:1235/22 :32B:EUR7500, :57A:BBSPNL2A :20:1227/23 :32B:EUR12500, :57B:ROTTERDAM :20:1248/32 :32B:EUR6000, :57A:CRLYFRPP :20:1295/22 :32B:EUR30000, :56A:INGBNL2A :57A:DEUTDEFF :72:/TELE/
Format
(1) There are 5 requests for transfer within the message
32
MT 202
MT 202 General Financial Institution Transfer

MT 202 Scope
This message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the financial institution of the beneficiary institution. It is used to order the movement of funds to the beneficiary institution. This message may also be sent to a financial institution servicing multiple accounts for the Sender to transfer funds between these accounts. In addition it can be sent to a financial institution to debit an account of the Sender serviced by the Receiver and to credit an account, owned by the Sender at an institution specified in field 57a.

MT 202 General Financial Institution Transfer Status M M -----> O -----| M O O O O O M O 32A 52a 53a 54a 56a 57a 58a 72 Value Date, Currency Code, Amount Ordering Institution Senders Correspondent Receivers Correspondent Intermediary Account With Institution Beneficiary Institution Sender to Receiver Information M = Mandatory O = Optional 6!n3!a15d A or D A, B or D A, B or D A or D A, B or D A or D 10 6*35x 11 4 5 6 7 8 9 13C Time Indication /8c/4!n1!x4!n 3 Tag 20 21 Field Name Transaction Reference Number Related Reference 16x 16x Content/Options No 1 2
5 February 2007
33

C1 If field 56a is present, then field 57a must also be present (Error code(s): C81).
MT 202 Usage Rules

All parties to the transaction must be financial institutions. The transfer of funds between the ordering institution and the beneficiary institution is always related to another transaction. Field 21 must refer to this transaction. If the Sender wishes to instruct the Receiver to debit its account serviced by the Receiver and to credit one of its several accounts at an institution specified in field 57a, field 58A must contain the number of the account to be credited and the name of the Sender. If the Sender wishes to instruct the Receiver that funds are to be moved between two accounts owned by the Sender and serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A the number of the account to be credited and the name of the Sender.

FORMAT 16x
2. Field 21: Related Reference

FORMAT 16x
PRESENCE Mandatory
34
MT 202
DEFINITION This field contains a reference to the related transaction CODES If the Sender is not the originator of the transaction and no related reference is received, the code NONREF must be used in this field. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES If the related message is an MT 103 Single Customer Credit Transfer, this field will contain the field 20 Senders Reference of that MT 103. In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary institution, eg, the common reference in an MT 300 Foreign Exchange Confirmation, field 21 of an MT 202 General Financial Institution Transfer, an MT 205 Financial Institution Transfer Execution or an MT 400 Advice of Payment.
3. Field 13C: Time Indication

FORMAT Option C /8c/4!n1!x4!n (Code)(Time indication)(Sign)(Time offset)
PRESENCE Optional DEFINITION This repetitive field specifies one or several time indication(s) related to the processing of the payment instruction. CODES One of the following codes may be used, placed between slashes (/): CLSTIME RNCTIME SNDTIME The time by which the funding payment must be credited, with confirmation, to the CLS Banks account at the central bank, expressed in Central European Time (CET). The time at which a TARGET payment has been credited at the receiving central bank, expressed in Central European Time (CET). The time at which a TARGET payment has been debited at the sending central bank, expressed in Central European Time (CET).
5 February 2007
35
NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). Sign is either + or - (Error code(s): T15). Time offset is expressed as HHMM, where the hour component, ie, HH, must be in the range of 00 through 13, and the minute component, ie, MM, must be in the range of 00 through 59. Any HH or MM component outside of these range checks will be disallowed (Error code(s): T16). USAGE RULES The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal Time - ISO 8601). EXAMPLE Assume a financial institution in London is sending a payment instruction on 5 January related to CLS in which it indicates that money has to be funded to CLS bank by 09.15 CET. Time indication field will be completed as follows: :13C:/CLSTIME/0915+0100 Explanation: 0915 is the time by which the money has to be funded to CLS bank. It has been agreed that CLSTIME is to be indicated in CET (see codes above). + 0100 is the offset of CET against UTC in January (ie during winter time). If the same instruction had been sent on 10 June (ie during summer time), time indication field would have been completed as follows: :13C:/CLSTIME/0915+0200 Offsets of local time zones against UTC are published in the green section of the BIC Directory.

PRESENCE Mandatory DEFINITION This field specifies the value date, currency and amount to be transferred. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).
36
MT 202
Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).
5. Field 52a: Ordering Institution

PRESENCE Optional DEFINITION This field specifies the ordering institution when other than the Sender of the message. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR)
5 February 2007
37
PT SC
8!n 6!n
Portuguese National Clearing Code UK Domestic Sort Code
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT RU SC SW SW 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
38
MT 202
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender of an initial MT 202 is also the ordering institution, ie, this field is not used, that Sender will be identified in this field in any subsequent messages as the ordering institution. This field must be forwarded to the beneficiary institution. The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the ordering financial institution has no BIC.
6. Field 53a: Senders Correspondent

PRESENCE Optional DEFINITION This field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender instructs the Receiver to transfer funds between two accounts owned by the Sender and serviced by the Receiver, this field must be used with option B to identify the account to be debited. If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver (or branch of the Receiver when specified in field 54a), then field 53a must be present.
5 February 2007
39
When field 53a is present and contains a branch of the Sender, the need for a cover message is dependent on the currency of the transaction, the relationship between the Sender and the Receiver and the contents of field 54a, if present. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Senders correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of the Receiver. In this case, the Receiver will be paid by its branch in field 53a. In all other cases, when field 53a is present, a cover message, ie, MT 202/203 or equivalent non-SWIFT, must be sent to the financial institution identified in field 53a. When field 53B is used to specify a branch city name, it must always be a branch of the Sender. The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and Receiver, in the currency of the transfer, will be used. The use and interpretation of fields 53a and 54a is, in all cases, dictated by the currency of the transaction and the correspondent relationship between the Sender and the Receiver relative to that currency.
7. Field 54a: Receivers Correspondent

PRESENCE Optional DEFINITION This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender and Receiver, in the currency of the transfer, will be used. In those cases where field 54a contains a branch of the Receiver, and is not preceded by field 53a, or field 53a contains an account of the Sender serviced by the Receivers branch, the Receiver will claim reimbursement from its branch. If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender, the Receiver will claim reimbursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationship between the Sender and the Receiver.
40
MT 202
In all other cases where field 54a contains a branch of the Receiver, the Receiver will be paid by its branch in field 54a. A branch of the Sender must not appear in field 54a. If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver, field 54a must not be present. Field 54a containing the name of a financial institution other than the Receivers branch must be preceded by field 53a; the Receiver will be paid by the financial institution in field 54a. The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and the Receiver relative to that currency.

PRESENCE Optional DEFINITION This field specifies the financial party between the Receiver and the account with institution through which the transaction must pass to reach the account with institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong
5 February 2007
41
IE IN IT PL PT RT SC ZA
6!n 11!c 10!n 8!n 8!n
6!n 6!n
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT RT 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
42
MT 202
RU SC SW SW ZA
9!n 6!n 3..5n 6!n 6!n
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

5 February 2007
43
PRESENCE Conditional (C1) DEFINITION This field identifies the financial institution, when other than the Receiver, which will pay or credit the beneficiary institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
44
MT 202
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations.(Error code(s): C05).
5 February 2007
45
USAGE RULES When field 57a is not present, it means that the Receiver is also the account with institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
10. Field 58a: Beneficiary Institution

PRESENCE Mandatory DEFINITION This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient of the funds being transferred. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code
46
MT 202
6!n 6!n
5 February 2007
47
6!n 11!c 10!n 8!n 8!n
9!n 6!n 3..5n 6!n 6!n
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender instructs the Receiver to either credit one of several accounts owned by the Sender at an institution specified in field 57a, or transfer funds between two accounts owned by the Sender and serviced by the Receiver, option A must be used to specify the account to be credited and the name of the Sender. It is strongly recommended that when clearing payments take precedence over book transfer and book transfer is requested, Party Identifier be used to specify the account of the beneficiary. When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.
48
MT 202
When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver. CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF INS INT PHON PHONBEN PHONIBK REC TELE TELEBEN TELEIBK Instructions following are for the account with institution Information following is for the beneficiary The instructing institution which instructed the Sender to execute the transaction Instructions following are for the intermediary Please advise account with institution by phone Please advise/contact beneficiary/claimant by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the beneficiary/claimant by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
5 February 2007
49
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
MT 202 Examples
Example 1 MT 202 as a Cover Payment
Narrative Value 27 May 1998, Franz Holzapfel G.m.b.H. orders Bank Austria, Vienna, to pay pounds sterling 1,285.40 into H.F. Janssens account (number 125-00698) with ABN Amro Bank, Amsterdam. Bank Austria sends two SWIFT messages: A. A customer transfer request to ABN Amro Bank, Amsterdam, using reference 494934/DEV. B. A cover message for the Pounds Sterling payment, which is provided through its account number 15158000 at Midland Bank, London. Information Flow
50
MT 202
Message A SWIFT MT 103 Single Customer CreditTransfer

SWIFT Message, MT 103 Explanation Sender Message type Receiver Message text Senders reference Bank operation code Value date/currency code/amount :20:494934/DEV :23B:CRED :32A:980527GBP1285,40 BKAUATWW 103 ABNANL2A Format
5 February 2007
51
Explanation Currency/Instructed Amount Ordering customer Senders correspondent (1) Beneficiary customer Details of charges End of message text/trailer :33B:GBP1285,40
Format
:50K:FRANZ HOLZAPFEL GMBH VIENNA :53A:MIDLGB22 :59:/125-00698 H.F. JANSSEN LEDEBOERSTRAAT 27 AMSTERDAM :71A:SHA
(1) Field 53A indicates the institution which is to provide the funds to the Receiver on behalf of the Sender.
Message B SWIFT MT 202 Cover Message

Information Flow
52
MT 202
SWIFT Message, MT 202 Explanation Sender Message type Receiver Message Text Transaction reference number Related reference (1) Value date/currency code/amount Account used for reimbursement Beneficiary institution End of message text/trailer :20:213804/887 :21:494934/DEV :32A:980527GBP1285,40 :53B:/15158000 :58A:ABNANL2A BKAUATWW 202 MIDLGB22 Format
(1) The related reference is the Senders Reference of the MT 103 Customer Credit Transfer.
Example 2 MT 202 with Time Indication

Narrative On 5 January, a CLS settlement member (BANKGB2L) receives an instruction from CLS Bank to fund JPY 5,000,000 by 07.00 AM CET to CLS Bank. BANKGB2L sends an MT 202 to their JPY nostro correspondent (BANKJPJT), indicating that the funds need to be credited to CLS Bank by 07.00 AM CET. Information Flow
5 February 2007
53
SWIFT Message In the MT 202 which BANKGB2L sends to its JPY correspondent BANKJPJT, it can indicate the time by which BANKJPJT has to credit the funds to CLS bank as follows: :13C:/CLSTIME/0700+0100 whereby 0700 is the time by which the funds have to be credited to CLS Bank. By convention CLS time instructions are quoted in CET. +0100 is the offset (during wintertime) of CET against UTC. Upon receipt of the MT 202, BANKJPJT can recalculate the CET time indication into its local time by comparing the offset in 13C to its own offset against UTC. Japan is UTC +0900, therefore BANKJPJT knows it has to process the instruction before 15.00 local time in Japan. Offsets of local delta time zones against UTC are published in the green section of the BIC directory.
54
MT 203
MT 203 Multiple General Financial Institution Transfer

MT 203 Scope
This multiple message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the financial institution(s) of several beneficiary institution(s). The message contains several transactions. It is used to order the movement of funds to each beneficiary institution. This message may also contain order(s) for the movement of the Senders own funds in favour of itself. This is the case when the Receiver services multiple accounts for the Sender and the funds are to be transferred between these accounts. In addition, it can be sent to a financial institution to debit an account of the Sender serviced by the Receiver and to credit an account owned by the Sender at an institution specified in field 57a.

The MT 203 consists of two types of sequences: The first sequence provides details of the transaction between the Sender and Receiver, ie, the value date and total amount to be transferred, as well as any other information about this transaction, as necessary. The second sequence must appear at least twice and, in order to expedite processing, not more than ten times. It provides details of each transaction between the Receiver and a financial institution to which the funds will be transferred. Each sequence includes a TRN, the reference of the related transaction, the amount and currency code to be transferred, the identification of the beneficiary institution and any other institution(s) through which the funds will pass and any other information about the transaction, as necessary. MT 203 Multiple General Financial Institution Transfer Status M M O O O O -----> M M M O 20 21 32B 56a Transaction Reference Number Related Reference Currency Code, Amount Intermediary 16x 16x 3!a15d A or D 10 7 8 9 Tag 19 30 52a 53a 54a 72 Sum of Amounts Value Date Ordering Institution Senders Correspondent Receivers Correspondent Sender to Receiver Information Field Name 17d 6!n A or D A, B or D A, B or D 6*35x Content/Options No. 1 2 3 4 5 6
5 February 2007
55
Status O M O -----|
Tag 57a 58a 72
Field Name Account With Institution Beneficiary Institution Sender to Receiver Information
Content/Options A, B or D
No. 11
A or D 12 6*35x 13
M = Mandatory O = Optional

C1 The amount in field 19 must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01). C2 The currency code in the amount field 32B must be the same for all occurrences of this field in the message (Error code(s): C02). C3 The repetitive sequence must appear at least twice, but not more than ten times (Error code(s): T11,T10). C4 If field 56a is present in a transaction, then field 57a must also be present (Error code(s): C81).
MT 203 Usage Rules

All parties to the transactions must be financial institutions. If the Sender wishes to instruct the Receiver to debit its account serviced by the Receiver and to credit one of its several accounts at an institution specified in field 57a, field 58A in the related sequence must contain the number of the account to be credited and the name of the Sender. If the Sender wishes to instruct the Receiver that funds are to be moved between two accounts owned by the Sender and serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A, in the sequence relating to this order, must specify the number of the account to be credited and the name of the Sender. Each transfer of funds between the ordering institution and a beneficiary institution is always related to another transaction. Field 21 must refer to this transaction.
56
MT 203

FORMAT 17d (Amount)
PRESENCE Mandatory DEFINITION This field contains the sum of all amounts appearing in each occurrence of field 32B in the message. NETWORK VALIDATED RULES The integer part of the Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32B (Error code(s): C03,T40,T43).

FORMAT 6!n (Date)
PRESENCE Mandatory DEFINITION This field specifies the value date for all transactions in the message. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).

PRESENCE Optional
5 February 2007
57
DEFINITION This field specifies the ordering institution when other than the Sender of the message. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option D: AT AU BL CC CH 5!n 6!n 8!n 9!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier
58
MT 203
CP ES FW GR HK IE IN IT PL PT RU SC SW SW
4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender of an initial MT 203 message is also the ordering institution ie, this field is not used, that Sender will be identified in this field in any subsequent messages as the ordering institution. This field must be forwarded to each beneficiary institution. The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the ordering financial institution has no BIC.
5 February 2007
59
PRESENCE Optional DEFINITION This field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender instructs the Receiver to transfer funds between two accounts owned by the Sender and serviced by the Receiver, this field must be used with option B to identify the account to be debited. The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender and Receiver, in the currency of the transfer, will be used. If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver (or branch of the Receiver when specified in field 54a), then field 53a must be present. When field 53a is present and contains a branch of the Sender, the need for a cover message is dependent on the currency of the transaction, the relationship between the Sender and the Receiver and the contents of field 54a, if present. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Senders Correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of the Receiver. In this case, the Receiver will be paid by its branch in field 53a. In all other cases, when field 53a is present, a cover message, ie, MT202/203 or equivalent non-SWIFT, must be sent to the financial institution identified in field 53a. When field 53B is used to specify a branch city name, it must always be a branch of the Sender. The use and interpretation of fields 53a and 54a is, in all cases, dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency.
5. Field 54a: Receivers Correspondent
60
MT 203
PRESENCE Optional DEFINITION This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender and Receiver, in the currency of the transfer, will be used. In those cases where field 54a contains a branch of the Receiver, and is not preceded by field 53a, or field 53a contains an account of the Sender serviced by the Receivers branch, the Receiver will claim reimbursement from its branch. If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender, the Receiver will claim reimbursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationship between the Sender and the Receiver. In all other cases where field 54a contains a branch of the Receiver, the Receiver will be paid by its branch in field 54a. A branch of the Sender must not appear in field 54a. If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver, field 54a must not be present. Field 54a containing the name of a financial institution other than the Receivers branch must be preceded by field 53a; the Receiver will be paid by the financial institution in field 54a. The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency.
5 February 2007
61
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party identified in the field. CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF INS INT PHON PHONBEN PHONIBK REC TELE TELEBEN TELEIBK Instructions following are for the account with institution Information following is for the beneficiary The instructing institution which instructed the Sender to execute the transaction Instructions following are for the intermediary Please advise account with institution by phone Please advise/contact beneficiary/claimant by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the beneficiary/claimant by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.
62
MT 203
USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.

FORMAT 16x
PRESENCE Mandatory DEFINITION The Transaction Reference Number (TRN) specifies the reference assigned by the Sender to unambiguously identify the message. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES A different TRN must be assigned to each transaction in the message.

FORMAT 16x
5 February 2007
63
PRESENCE Mandatory DEFINITION This field contains a reference to the related transaction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES If the related message is an MT 103 Single Customer Credit Transfer, this field will contain the field 20 Senders Reference of that MT 103. In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary institution, eg, the common reference in an MT 300 Foreign Exchange Confirmation, field 21 of an MT 202 General Financial Institution Transfer or MT 400 Advice of Payment. If the Sender is not the originator of the transaction and no related reference is received, the code NONREF must be used in this field.

PRESENCE Mandatory DEFINITION This field specifies the currency and amount to be transferred for the transaction in the sequence. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).

64
MT 203
PRESENCE Optional DEFINITION This field specifies the financial party between the Receiver and the account with institution through which the transaction must pass to reach the account with institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
5 February 2007
65
66
MT 203
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

PRESENCE Conditional (C4) DEFINITION This field specifies the financial institution, when other than the Receiver, which will pay or credit the beneficiary institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code
5 February 2007
67
6!n 6!n
68
MT 203
6!n 11!c 10!n 8!n 8!n
9!n 6!n 3..5n 6!n 6!n
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When field 57a is not present, it means that the Receiver is also the account with institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
5 February 2007
69

PRESENCE Mandatory DEFINITION This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient of the funds being transferred. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
70
MT 203
SC ZA
6!n 6!n
5 February 2007
71
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender instructs the Receiver to either credit one of several accounts owned by the Sender at an institution specified in field 57a, or transfer funds between two accounts owned by the Sender and serviced by the Receiver, option A must be used in the related sequence to specify the account to be credited and the name of the Sender. It is strongly recommended that in those cases where clearing payments take precedence over book transfer and book transfer is requested, the Party Identifier be used to specify the account number of the beneficiary institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

72
MT 203
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or other party specified. This information is relevant to the specific transaction in the sequence. CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF INS INT PHON PHONBEN PHONIBK REC TELE TELEBEN TELEIBK Instructions following are for the account with institution Information following is for the beneficiary The instructing institution which instructed the Sender to execute the transaction Instructions following are for the intermediary Please advise account with institution by phone Please advise/contact beneficiary/claimant by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the beneficiary/claimant by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field.
5 February 2007
73
Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
MT 203 Examples
Narrative Value 28 May 2002, UBS, Zrich requests ABN Amro Bank, Amsterdam, to transfer euro 5,000,000 as follows: ING Bank NV, Amsterdam in favour of Morgan Guaranty Trust Co., New York SNS Bank Nederland NV, Amsterdam in favour of Mellon Bank, London Citibank, Amsterdam in favour of Citibank, New York Dresdner Bank AG, Frankfurt EUR EUR EUR EUR 500,000 1,500,000 1,000,000 2,000,000
Information Flow
74
MT 203
SWIFT Message Explanation Sender Message type UBSWCHZH80A 203 Format
5 February 2007
75
Explanation Receiver Message text Sum of amounts in the message Value date Transaction reference number (1) (1) Related reference Currency code and amount Account with institution Beneficiary institution Transaction reference number (2) (1) Related reference Currency code and amount Account with institution Beneficiary institution Transaction reference number (3) (1) Related reference Currency code and amount Account with institution Beneficiary institution Transaction reference number (4) (1) Related reference Currency code and amount Beneficiary institution End of message text/trailer :19:5000000, :30:020528 :20:2345 :21:789022 :32B:EUR500000, :57A:INGBNL2A :58A:MGTCUS33 :20:2346 :21:ABX2270 :32B:EUR1500000, :57A:BBSPNL2A :58A:MELNGB2X :20:2347 :21:CO 2750/26 :32B:EUR1000000, :57A:CITINL2X :58A:CITIUS33 :20:2348 ABNANL2A
Format
:21:DRESFF2344BKAUWW :32B:EUR2000000, :58A:DRESDEFF
76
MT 203
(1) There are 4 transfer orders within the message
5 February 2007
77
MT 204 Financial Markets Direct Debit Message

Note: The use of this message type requires Message User Group (MUG) registration.
MT 204 Scope
This message is sent by an exchange or clearing house, or another financial institution to a SWIFT member or submember, to instruct the Receiver of the message to debit the account(s) of a third party specified in the message and to pay or credit the corresponding amount in favour of the Sender of the message.

The MT 204 consists of two types of sequences: Sequence A Common Elements - Reimbursement Details, is a single occurrence sequence and contains default information which is valid for all individual transactions described in sequence B and the total amount to be reimbursed. Sequence B Transaction Details, is a repetitive sequence. Each occurrence gives the details concerning one debit. MT 204 Financial Markets Direct Debit Message Status Tag Field Name Content/Options No.
Sequence A Common Elements - Reimbursement Details M M M O O O 20 19 30 57a 58a 72 Transaction Reference Number Sum of Amounts Value Date Account With Institution Beneficiary Institution Sender to Receiver Information 16x 17d 6!n A, B or D A or D 6*35x 1 2 3 4 5 6
-----> Repetitive Sequence B Transaction Details M O M M O -----| 20 21 32B 53a 72 Transaction Reference Number Related Reference Transaction Amount Debit Institution Sender to Receiver Information 16x 16x 3!a15d A, B or D 10 6*35x 11 7 8 9
78
MT 204
Status
Tag
Field Name M = Mandatory O = Optional
Content/Options
No.

C1 The amount in field 19 must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01). C2 The currency code in the amount field 32B must be the same for all occurrences of this field in the message (Error code(s): C02). C3 The repetitive sequence must not appear more than ten times (Error code(s): T10).
MT 204 Usage Rules

This message requires the implementation of special procedures, its use is governed by bilateral agreements between counterparties. In order to be able to send or receive this message, the interested customers need to formally request SWIFT to be activated within the FIN subapplication group which controls the use of this message.

FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES This field is intended to ensure proper cross referencing of all related sequences, as well as to provide a unique reference. This reference should normally be quoted in any related reimbursement payments, eg, MT 202 General Financial Institution Transfer, MT 910 Confirmation of Credit and/or MT 950 Statement Message when reimbursement is by a single net amount.
5 February 2007
79

FORMAT 17d (Amount)
PRESENCE Mandatory DEFINITION This field specifies the sum of the amounts appearing in each occurrence of field 32B. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32B (Error code(s): C03,T40,T43).

FORMAT 6!n (Date)
PRESENCE Mandatory DEFINITION This field specifies the value date which the Receiver is requested to apply to all individual transactions in the message. This value will, subject to bilateral agreement, determine the value date to be applied to the reimbursement made by the Receiver in favour of the Sender of the message. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).

80
MT 204
PRESENCE Optional DEFINITION This field identifies the financial institution at which the Sender wishes to receive reimbursement from the Receiver. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
CODES with option D: AT 5!n Austrian Bankleitzahl
5 February 2007
81
AU BL CC CH CP ES FW GR HK IE IN IT PL PT RT RU SC SW SW ZA
6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n
Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
9!n 6!n 3..5n 6!n 6!n
82
MT 204
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //RT, //IN or //CP is used, it should appear only once and in the first of the fields 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.

PRESENCE Optional DEFINITION This field identifies the beneficiary institution, which is always the Sender. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW 5!n 6!n 8!n 9!n 8..9n without 9 digit code Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire
5 February 2007
83
GR HK IE IN IT PL PT RT SC ZA
7!n 3!n 6!n 11!c 10!n 8!n 8!n
HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
6!n 6!n
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR)
84
MT 204
PT RT RU SC SW SW ZA
8!n
Portuguese National Clearing Code Pay by Real Time Gross Settlement
9!n 6!n 3..5n 6!n 6!n
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //RT, //IN or //CP is used, it should appear only once and in the first of the fields 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.

5 February 2007
85
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party identified in the field. CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF CUST CUSTMAR CUSTVAR HOUSE HOUSEMAR HOUSEVAR METALS MKTMAR MKTMKR MKTVAR MMPLDG OPTPREM REC TENDER VARIATN XMGN Instructions following are for the account with institution Information following is for the beneficiary The amount to be debited corresponds to a margin call on segregated customer (client) trades/account The amount to be debited corresponds to initial/original margin on customer trades (customer account margin) The amount to be debited corresponds to variation margin on customer trades (customer account variation) The amount to be debited corresponds to a margin call on house trades (proprietary funds) The amount to be debited corresponds to initial/original margin on house trades (house account margin) The amount to be debited corresponds to variation margin on house trades (house account variation) Metals call The amount to be debited corresponds to initial/original margin on market-maker (specialist) trades/account (market-maker account margin) The amount to be debited corresponds to a margin call on market-maker (specialist) trades/account The amount to be debited corresponds to variation margin on market-maker (specialist) trades/account (market-maker account variation) Market-maker pledge Options premium Instructions following are for the Receiver The amount to be debited corresponds to a payment in respect of a tender (delivery) General variation Cross-margin account (covers positions hedged, offset or spread over two exchanges)
86
MT 204
XMGNMAR XMGNVAR
Cross-margin account margin (for initial/original margin) Cross-margin account margin (for variation margin)
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards.

FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the specific transaction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES This reference should normally be quoted in any related reimbursement payments, eg, MT 202 General Financial Institution Transfer, MT 910 Confirmation of Credit and/or MT 950 Statement Message when reimbursement is by individual amount(s), sent to the Sender.
5 February 2007
87

FORMAT 16x
PRESENCE Optional DEFINITION This field contains a reference attributed by the debit institution to the related transaction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES This reference would normally be quoted in any related MT 900 Confirmation of Debit or MT 950 Statement Message, sent to the debit institution.
9. Field 32B: Transaction Amount

PRESENCE Mandatory DEFINITION This field specifies the currency and the amount to be debited to the debit institution identified in field 53a of the same sequence. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).
10. Field 53a: Debit Institution

FORMAT Option A Option B [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] (Party Identifier) (BIC) (Party Identifier) (Location)
88
MT 204
Option D
[/1!a][/34x] 4*35x
(Party Identifier) (Name & Address)
PRESENCE Mandatory DEFINITION This field specifies the financial institution which is to be debited with the transaction amount. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES Optional Party Identifier may be used to specify the account number to be debited. Option A must be used whenever possible. Option D must only be used in exceptional circumstances, ie, when the debit institution cannot be identified by a BIC, and when there is a bilateral agreement between the Sender and Receiver permitting its use. Unless qualified by an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party specified. This information is relevant to the specific transaction in the sequence.
5 February 2007
89
CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF CUST CUSTMAR CUSTVAR HOUSE HOUSEMAR HOUSEVAR METALS MKTMAR MKTMKR MKTVAR MMPLDG OPTPREM REC TENDER VARIATN XMGN XMGNMAR XMGNVAR Instructions following are for the account with institution Information following is for the beneficiary The amount to be debited corresponds to a margin call on segregated customer (client) trades/account The amount to be debited corresponds to initial/original margin on customer trades (customer account margin) The amount to be debited corresponds to variation margin on customer trades (customer account variation) The amount to be debited corresponds to a margin call on house trades (proprietary funds) The amount to be debited corresponds to initial/original margin on house trades (house account margin) The amount to be debited corresponds to variation margin on house trades (house account variation) Metals call The amount to be debited corresponds to initial/original margin on market-maker (specialist) trades/account (market-maker account margin) The amount to be debited corresponds to a margin call on market-maker (specialist) trades/account The amount to be debited corresponds to variation margin on market-maker (specialist) trades/account (market-maker account variation) Market-maker pledge Options premium Instructions following are for the Receiver The amount to be debited corresponds to a payment in respect of a tender (delivery) General variation Cross-margin account (covers positions hedged, offset or spread over two exchanges) Cross-margin account margin (for initial/original margin) Cross-margin account margin (for variation margin)
90
MT 204
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards.
MT 204 Examples
Example 1 The Exchange and the Member have a Common Correspondent Bank
Narrative The Chicago Mercantile sends an MT 204 to Northern Trust with the instruction to debit the account of Merrill Lynch and to credit its account 1234-ABC, with value date September 21st 1998. Information Flow
5 February 2007
91
SWIFT Message, MT 204 Explanation Sender Message type Receiver Message text Message reference number Sum of amounts Value date Beneficiary institution Transaction reference number Related reference :20:XCME REF1 :19:50000, :30:980921 :58A:/1234-ABC XCMEUS4C :20:XCME REF2 :21:MANDATEREF1 XCMEUS4C 204 CNORUS44 Format
92
MT 204
Explanation Transaction amount Debit institution End of message text/trailer :32B:USD50000, :53A:MLNYUS33
Format
The common correspondent bank sends confirmations of credit and debit to the exchange (MT 910) and exchange member (MT 900) as shown below: SWIFT Message, MT 910, Confirmation of Credit Explanation Sender Message type Receiver Message text Transaction reference number Related reference Account identification Value date/currency code/amount Ordering institution End of message text/trailer :20:MB REF A :21:XCME REF1 :25:ACCOUNT ID OF XCME :32A:980921USD50000, :52A:XCMEUS4C CNORUS44 910 XCMEUS4C Format
SWIFT Message, MT 900, Confirmation of Debit Explanation Sender Message type Receiver Message text Transaction reference number Related reference :20:MB REF B :21:MANDATEREF1 CNORUS44 900 MLNYUS33 Format
5 February 2007
93
Explanation Account identification Value date/currency code/amount Ordering institution End of message text/trailer
Format :25:ACCOUNT ID OF MLNY :32A:980921USD50000, :52A:XCMEUS4C
Example 2 The Exchange does not want to use the account relationship with the common correspondent and wants the funds to be transferred to another institution
Narrative The Chicago Mercantile Exchange asks its member Merrill Lynch International Bank, New York to put up a margin of 50,000 USD. The Northern Trust Company is the settlement bank of Merrill Lynch at the Chicago Mercantile Exchange. The Chicago Mercantile sends an MT 204 to Northern Trust with the instruction to debit the account of Merrill Lynch and to credit its account serviced by First National Bank of Chicago in Chicago with a value date September 21st, 1998. Information Flow
94
MT 204
SWIFT Message, MT 204 Explanation Sender Message type Receiver Message text Transaction reference number Sum of amounts Value date Account with institution Message reference number Related reference Transaction amount Debit institution End of message text/trailer :20:XCME REF1 :19:50000, :30:980921 :57A:FNBCUS44 :20:XCME REF2 :21:MANDATEREF1 :32B:USD50000, :53A:MLNYUS33 XCMEUS4C 204 CNORUS44 Format
5 February 2007
95
MT 205 Financial Institution Transfer Execution

MT 205 Scope
This message is sent by the Receiver of a category 2 transfer message, ie, MT 200, 201, 202, 203 or 205, directly or through correspondent(s), to another financial institution located in the same country as the Sender. It is used to further transmit a funds transfer instruction domestically.

MT 205 Financial Institution Transfer Execution Status M M -----> O -----| M M O O O M O 32A 52a 53a 56a 57a 58a 72 Value Date, Currency Code, Amount Ordering Institution Senders Correspondent Intermediary Account With Institution Beneficiary Institution Sender to Receiver Information M = Mandatory O = Optional 6!n3!a15d A or D A, B or D A or D A, B or D A or D 6*35x 10 4 5 6 7 8 9 13C Time Indication /8c/4!n1!x4!n 3 Tag 20 21 Field Name Transaction Reference Number Related Reference 16x 16x Content/Options No. 1 2

C1 If field 56a is present, then field 57a must also be present (Error code(s): C81).
96
MT 205

FORMAT 16x

FORMAT 16x
PRESENCE Mandatory DEFINITION This field contains a reference to the related transaction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES If the previous message is an MT 202, 203 or 205, this field contains the field 21 Related Reference of that message. If the previous message is an MT 200 or 201, this field contains the field 20 Transaction Reference Number of that message.
3. Field 13C: Time Indication

FORMAT Option C /8c/4!n1!x4!n (Code) (Time indication) (Sign) (Time offset)
5 February 2007
97
PRESENCE Optional DEFINITION This repetitive field specifies one or several time indication(s) related to the processing of the payment instruction. CODES One of the following codes may be used, placed between slashes (/): CLSTIME RNCTIME SNDTIME The time by which the funding payment must be credited, with confirmation, to the CLS Banks account at the central bank, expressed in Central European Time (CET). The time at which a TARGET payment has been credited at the receiving central bank, expressed in Central European Time (CET). The time at which a TARGET payment has been debited at the sending central bank, expressed in Central European Time (CET).
NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). Sign is either "+" or "-" (Error code(s): T15). Time offset is expressed as HHMM, where the hour component, ie, HH, must be in the range of 00 through 13, and the minute component, ie, MM, must be in the range of 00 through 59. Any HH or MM component outside of these range checks will be disallowed (Error code(s): T16). USAGE RULES The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal Time - ISO 8601). EXAMPLE Assume a financial institution in London is sending a payment instruction on 5 January related to CLS in which it indicates that money has to be funded to CLS bank by 09.15 CET. Time indication field will be completed as follows: :13C:/CLSTIME/0915+0100 Explanation: 0915 is the time by which the money has to be funded to CLS bank. It has been agreed that CLSTIME is to be indicated in CET (see codes above). + 0100 is the offset of CET against UTC in January (ie during winter time). If the same instruction had been sent on 10 June (ie during summer time), time indication field would have been completed as follows:
98
MT 205
:13C:/CLSTIME/0915+0200 Offsets of local time zones against UTC are published in the green section of the Bic Directory.

PRESENCE Mandatory DEFINITION This field specifies the value date, currency and amount to be transferred. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).

PRESENCE Mandatory DEFINITION This field identifies the ordering institution from the initial message. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT 5!n Austrian Bankleitzahl
5 February 2007
99
AU BL CC ES FW GR HK IE IN IT PL PT SC
6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n
Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC)
100
MT 205
IN IT PL PT RU SC SW SW
11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES If there was no ordering institution specified in the initial message, the Sender of that message will be the ordering institution in this message. This field must be forwarded to the beneficiary institution. The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the ordering financial institution has no BIC.

5 February 2007
101
PRESENCE Optional DEFINITION This field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Sender and the Receiver, and one of these accounts is to be used for reimbursement, the account to be credited or debited must be indicated in field 53a, using option B with the account number line only. If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver, then field 53a must be present. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Senders Correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of the Receiver. In this case, the Receiver will be paid by its branch in field 53a. When there is a single direct account relationship, in the currency of the transaction, between the Sender and the Receiver, and this is the account to be used for reimbursement, field 53a must not be present. When field 53B is used to specify a branch city name, it must always be a branch of the Sender. The use and interpretation of field 53a is, in all cases, dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency.

PRESENCE Optional DEFINITION This field specifies the financial party between the Receiver and the account with institution through which the this transaction must pass to reach the account with institution.
102
MT 205
CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
CODES with option D: AT AU BL CC 5!n 6!n 8!n 9!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number
5 February 2007
103
CH CP ES FW GR HK IE IN IT PL PT RT RU SC SW SW ZA
6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n
CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
9!n 6!n 3..5n 6!n 6!n
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier.
104
MT 205
The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

PRESENCE Conditional (C1) DEFINITION This field specifies the financial institution, when other than the Receiver, which is to pay or credit the beneficiary institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code)
5 February 2007
105
HK IE IN IT PL PT RT SC ZA
3!n 6!n 11!c 10!n 8!n 8!n
Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
6!n 6!n
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code
106
MT 205
RT RU SC SW SW ZA 9!n 6!n 3..5n 6!n 6!n
Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When field 57a is not present, it means that the Receiver is also the account with institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

5 February 2007
107
PRESENCE Mandatory DEFINITION This field specifies the ultimate recipient of the funds being transferred. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT RT SC ZA 6!n 6!n 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement UK Domestic Sort Code South African National Clearing Code
CODES with option D: AT 5!n Austrian Bankleitzahl
108
MT 205
AU BL CC CH CP ES FW GR HK IE IN IT PL PT RT RU SC SW SW ZA
6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n
Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Pay by Real Time Gross Settlement
9!n 6!n 3..5n 6!n 6!n
5 February 2007
109
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement (RTGS), the code //RT should appear in the optional Party Identifier. The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it is used with option D, it may be followed by another domestic clearing code. If the initial transfer message is an MT 200 or 201, this field will be identical to the contents of field 52a in this message. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party identified in the field. CODES One or more of the following codes may be used, placed between slashes (/): ACC BNF Instructions following are for the account with institution Information following is for the Beneficiary
110
MT 205
INS INT PHON PHONBEN PHONIBK REC TELE TELEBEN TELEIBK
The instructing institution which instructed the Sender to execute the transaction Instructions following are for the intermediary Please advise account with institution by phone Please advise/contact beneficiary/claimant by phone Please advise intermediary by phone Instructions following are for the Receiver Please advise the account with institution by the most efficient means of telecommunication Please advise the beneficiary/claimant by the most efficient means of telecommunication Please advise the intermediary by the most efficient means of telecommunication
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field. Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
MT 205 Examples
Narrative Deutsche Bank, Frankfurt, receives the following MT 202 General Financial Institution Transfer from UBS, Zrich.
5 February 2007
111
Explanation Sender Message Type Receiver Message Text Transaction Reference Number Related Reference Value Date/Currency Code/Amount Account With Institution Beneficiary Institution End of Message Text/Trailer
Format UBSWCHZH80A 202 DEUTDEFF
:20:203998988 :21:394882 :32A:020528EUR1121,50 :57A:DEUTDEHH :58A:OSCBDEH1
Information Flow
112
MT 205
As a result of this message, Deutsche Bank, Frankfurt, sends an MT 205 to Deutsche Bank, Hamburg: SWIFT Message Explanation Sender Message Type Receiver Message Text Transaction reference number :20:3004GH3882 Format DEUTDEFF 205 DEUTDEHH
5 February 2007
113
Explanation Related reference (1) Value date/currency code/amount Ordering institution (2) Beneficiary Institution End of Message Text/Trailer
Format :21:394882 :32A:020528EUR1121,50 :52A:UBSWCHZH80A :58A:OSCBDEH1
(1) Related reference of the transaction which resulted in this message, ie, field 21 of the MT 202. (2) As there was no ordering institution in the MT 202 which resulted in this message, the Sender of the MT 202 will become the ordering institution.
114
MT 206
MT 206 Cheque Truncation Message

MT 206 Scope
This message is sent from the beneficiarys financial institution, directly or through one or more other financial institutions, to the issuers financial institution to convey information about one or more truncated cheques, in the same currency. It is used to debit or obtain credit under usual reserve. In case of travellers cheques, this message may also be sent to a travellers cheque issuer. This message may not be used to convey information about truncated cheques sent on a collection basis.

The MT 206 consists of three types of sequences: Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individual cheques detailed in sequence B. Sequence B Cheque Details is a repetitive sequence where each occurrence provides details of an individual cheque. Sequence C Settlement Information is a non-repetitive sequence and contains settlement information applicable to all cheques detailed in sequence B. MT 206 Cheque Truncation Message Status Tag Field Name Content/Options No.
Mandatory Sequence A Common Elements M M M O O 20 28E 23E 17A 52a Senders Reference Message Index/Total Cheque Type Cheque Truncation Indicator Safekeeper 16x 5n/4!c 4!c[/30x] 1!a A, C or D 1 2 3 4 5
----->Mandatory Repetitive Sequence B Cheque Details M O O O 44A 21D 21E 29a Transaction Reference Number Cheque Number Cheque Reference Number Code Line 65x 35x 35x F or G 6 7 8 9
5 February 2007
115
Status M O O O O O O O -----|
Tag 32J 58a 25 26E 30 39C 52a 72 Cheque Amount
Field Name 15d
Content/Options
No. 10
Issuers Financial Institution Issuers Account Number/Code Represented Cheque Entry Date of Issue/Encashment Place of Issue/Encashment Safekeeper Sender to Receiver Information
A, C or D 11 35x 12 2n 13 6!n 14 4*35x 15 A, C or D 16 6*35x 17
Mandatory Sequence C Settlement Information O O O O 32A 57a 58B 19 Value Date, Currency Code and Sum of Settlement Amounts Account With Institution (for Settlement) Beneficiary Institutions Account (for Settlement) Settlement Amount M = Mandatory O = Optional 6!n3!a15d 18 A, C or D 19 [/1!a][/34x] [35x] 17d 21 20

C1 If field 23E contains TRAV, then either field 21D or field 29a must be present, but not both (Error code(s): E11). C2
116
MT 206
If field 23E contains GENC or OTHR and there is no field 29a, the following fields must be present (Error code(s): E19): field 58a Issuers Financial Institution field 25 Issuers Account Number/Code field 21D Cheque Number If field 23E in sequence A contains GENC or OTHR, and if field 29a in sequence B is ... Not present then field 21D in sequence B is ... then field 25 in sequence B is ... then field 58a in sequence B is ...
Mandatory
Mandatory
Mandatory
If field 29a is present, the following fields must not be present (Error code(s): E20): field 58a Issuers Account Number/Code field 21D Cheque Number If field 23E in sequence A contains GENC or OTHR and if field 29a in sequence B is ... Present then field 21D in sequence B is ... then field 25 in sequence B is ... then field 58a in sequence B is ...
Not allowed
Optional
Not allowed
C3 When field 52a is present in sequence A, it must not be present in any occurrence of sequence B. Conversely, if field 52a is present in any occurrence of sequence B, it must not be present in sequence A (Error code(s): D64). If field 52a in sequence A is ... Present Not present then field 52a in any occurrence of sequence B is ... Not allowed Optional
If field 52a in any occurrence of sequence B is ... Present Not present
then field 52a in sequence A is ... Not allowed Optional
5 February 2007
117
C4 Field 32A must only be present if field 28E contains the code LAST or ONLY (Error code(s): E21). If field 28E in sequence A contains ... LAST MORE ONLY then field 32A in sequence C is ... Mandatory Not allowed Mandatory
C5 Field 19 must only be present if field 28E contains the code MORE or LAST (Error code(s): E22). If field 28E in Sequence A contains ... LAST MORE ONLY then field 19 in Sequence C is ... Mandatory Mandatory Not allowed
C6 When field 28E contains ONLY, the amount specified in field 32A must be equal to the sum of all occurrences of field 32J in sequence B (Error code(s): E23). When field 28E contains MORE or LAST, field 19 must be equal to the sum of all occurrences of field 32J in sequence B (Error code(s): E24).
MT 206 Usage Rules

The MT 206 can only be sent and/or received by financial institutions which have registered with SWIFT to send and/or receive the MT 206/MT 256. If a registered user receives an MT 206 without bilateral agreement with the Sender, the Receiver should query the message according to normal banking practice. When sending a large number of truncated cheques, it may not be possible to fit them all into one MT 206. In that case: Additional MTs 206 must be sent, and they are chained using field 28E. All fields present in sequence A except field 28E must be repeated and contain exactly the same content. Field 32A of the last message must contain the sum of all fields 19 of all chained messages. Field 23E must contain the same value in all messages. The currency code in fields 32A of all messages must be the same. The use of this message is subject to bilateral/multilateral agreements between Sender/beneficiarys financial institution and Receiver of the truncation message and where necessary, between the issuers financial institution and the issuer.
118
MT 206

1. Field 20: Senders Reference
FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the instruction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :20:Ref254
2. Field 28E: Message Index/Total

FORMAT Option E 5n/4!c (Message Index) (Total)
PRESENCE Mandatory DEFINITION This field specifies the message number and where it is positioned in a chain of messages, or it specifies that it is the only message. CODES Total must contain one of following codes (Error code(s): T97): LAST MORE ONLY This is the last message in a chain of messages. More messages are following; this is not the last message in the chain of messages. This is the one and only message, ie, no chain of messages.
5 February 2007
119
USAGE RULES It is recommended that messages be sent in sequence. All messages belonging to the same sequence must have exactly the same senders reference in field 20. When more than one message is needed to convey all information, this field chains different messages by specifying the sequence number in the total number of messages. EXAMPLE The first message is :20:Ref254 :28E:1/MORE and the second is :20:Ref254 :28E:2/MORE and the third and last message is :20:Ref254 :28E:3/LAST
3. Field 23E: Cheque Type

FORMAT Option E 4!c[/30x] (Type) (Other Code)
PRESENCE Mandatory DEFINITION This field specifies the type of cheque that has been truncated. CODES Type must contain one of following codes (Error code(s): T47): GENC OTHR TRAV General cheques. Other type of cheque. This will be followed by a bilaterally agreed code to specify the type of cheque. Travellers cheques.
120
MT 206
NETWORK VALIDATED RULES Subfield 2, Other Code, may only be used after the code OTHR (Error code(s): D81). USAGE RULES The code OTHR may only be used when bilaterally agreed. When used, Other Code, must also be present. EXAMPLE :23E:GENC
4. Field 17A: Cheque Truncation Indicator

FORMAT Option A 1!a (Indicator)
PRESENCE Optional DEFINITION This field specifies whether or not the paper cheque is being sent separately. CODES Indicator must contain one of the following codes (Error code(s): T36): N Y The paper cheque is following. The paper cheque remains at the place of truncation.
USAGE RULES This field must be used if this is not covered by the bilateral/multilateral agreement and otherwise must not be present. EXAMPLE :17A:Y
5. Field 52a: Safekeeper

FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address)
5 February 2007
121
PRESENCE Conditional (C3) DEFINITION This field identifies the party at which all truncated cheques, ie, the originals, are securely stored. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option C or D: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl
122
MT 206
CC CH CP ES FW GR HK IE IN IT PL PT RU SC SW SW
9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the safekeeper has no BIC. EXAMPLE :52A:GEBABEBB
5 February 2007
123
6. Field 44A: Transaction Reference Number

FORMAT Option A 65x
PRESENCE Mandatory DEFINITION This number is generated by the beneficiarys financial institution to identify the transaction that this truncated cheque represents. EXAMPLE :44A:abc-1234
7. Field 21D: Cheque Number

FORMAT Option D 35x
PRESENCE Conditional (C1 and C2) DEFINITION This field contains the number of the cheque, which is normally inserted on the cheque by the issuers financial institution. EXAMPLE :21D:000024014014612
8. Field 21E: Cheque Reference Number

FORMAT Option E 35x
PRESENCE Optional DEFINITION This field contains the reference of the cheque generated by the beneficiarys financial institution.
124
MT 206
USAGE RULES The cheque reference number is usually the archive reference (microfilm) and is as such used as a link to the physical item. EXAMPLE :21E:888014612
9. Field 29a: Code Line

FORMAT Option F Option G 4*35z 9*1!n/33z (Full Code Line) (Index) (Partial Code Line)
PRESENCE Conditional (C1) DEFINITION This field contains all the information from the code line, ie, the encoded line generally located at the bottom of the cheque which in most cases can be read optically or magnetically, of the original cheque. USAGE RULES This field can be subdivided into its different parts with option G using an index to separate them, or it can be completely unstructured, untreated and unaltered using option F. It may contain any character defined in the z character set. The z character set contains the characters of both the x and y character set extended with the characters {, @, _ @ and #: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 .,-()/=+:?!"%&*<>;{ {@_# @# Cr Lf Space It is highly recommended to take great care when using the character string CrLf, since these characters are used by the network to indicate an end of field or subfield. Since option F only has 4 subfields, five CrLf in the code line would cause a NAK by the network. Also, within option G, after a CrLf, a number and a slash are expected. EXAMPLE Looking at the cheque from left to right, if the code line on the cheque is xxxxxx yyyyyyyyyyy zzzzzz then this field can be used as follows:
5 February 2007
125
with option G: :29G: 1/xxxxxx 2/yyyyyyyyyyy 3/zzzzzz with option F: :29F:xxxxxx yyyyyyyyyyy zzzzzz
10. Field 32J: Cheque Amount

FORMAT Option J 15d (Amount)
PRESENCE Mandatory DEFINITION This field contains the amount of the cheque being truncated (without the currency code). NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32A (Error code(s): C03,T40,T43). EXAMPLE :32J:10000,
11. Field 58a: Issuers Financial Institution

PRESENCE Conditional (C2) DEFINITION This field identifies the issuers financial institution.
126
MT 206
CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC ZA 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portugese National Clearing Code UK Domestic Sort Code South African National Clearing Code
CODES with options C or D: AT AU BL CC CH 5!n 6!n 8!n 9!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier
5 February 2007
127
CP ES FW GR HK IE IN IT PL PT RU SC SW SW ZA
4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n 6!n
CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portugese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES Option A must be used whenever possible. Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. EXAMPLE :58A:ABNANL2A
128
MT 206
12. Field 25: Issuers Account Number/Code

FORMAT 35x (Account)
PRESENCE Conditional (C2) DEFINITION This field identifies the issuer based on the account number appearing on the cheque. EXAMPLE :25:BE33123456789012
13. Field 26E: Represented Cheque Entry

FORMAT Option E 2n (Number)
PRESENCE Optional DEFINITION This field specifies the number of times a cheque has been previously presented without being honoured. EXAMPLE :26E:1 this cheque has been presented once before
14. Field 30: Date of Issue/Encashment

FORMAT 6!n (Date)
PRESENCE Optional
5 February 2007
129
DEFINITION This field contains the date written on the cheque when it was prepared by the issuer. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). USAGE RULES In the case of travellers cheques, this is the date of encashment. EXAMPLE :30:990102
15. Field 39C: Place of Issue/Encashment

FORMAT Option C 4*35x (Place)
PRESENCE Optional DEFINITION This field specifies the place where the cheque was issued. USAGE RULES In the case of travellers cheques, this is the place of encashment. EXAMPLE :39C:MANCHESTER GREAT BRITAIN
16. Field 52a: Safekeeper

FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Account) (Party Identifier) (Name & Address)
130
MT 206
PRESENCE Conditional (C3) DEFINITION This field identifies the party at which the truncated cheque, ie, the original, is securely stored. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option C or D: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl
5 February 2007
131
CC CH CP ES FW GR HK IE IN IT PL PT RU SC SW SW
9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the safekeeper has no BIC. EXAMPLE :52A:GEBABEBB
132
MT 206

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party identified in the field. CODES One or more of the following codes may be used, placed between slashes (/): MANU OTHR REMI STAL TRAN Manual operation (automated truncation not possible) This code is followed by a bilaterally agreed code or other bilaterally agreed structured information This code is followed by bilaterally agreed remittance information We think this cheque is stale dated but we still ask for payment Transaction Type code (any sub-codes to be agreed upon bilaterally)
USAGE RULES Field 72 must never be used for information for which another field is intended. Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended. Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash //. Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the last information in this field. It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field.
5 February 2007
133
Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention. This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message Standards. In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash. EXAMPLE :72:/STAL/
18. Field 32A: Value Date, Currency Code and Sum of Settlement Amounts
PRESENCE Conditional (C4) DEFINITION This field contains the value date which is to be applied to the funds that must be debited from the Receivers account, or credited to the Senders account, or the account of another party as specified in the bilateral agreement (see also the checklist on value dates). This is followed by, first the (common) currency for all the truncated cheques, and then the sum of all settlement amounts. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). USAGE RULES If messages are chained, ie, field 28E does not contain ONLY, this field must contain the sum of all occurrences of field 19 in the chained messages. EXAMPLE message 1: :28E:1/MORE ... :19:10000, message 2: :28E:2/MORE ... :19:5000, message 3: :28E:3/LAST ... :32A:990106USD18000, :19:3000,
134
MT 206
or message 1: :28E:1/ONLY ... :32A:990106USD12500
19. Field 57a: Account With Institution (for Settlement)

PRESENCE Optional DEFINITION This field identifies the account with institution at which the Sender wants to have the funds credited. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES FW GR HK 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong
5 February 2007
135
IE IN IT PL PT SC ZA
6!n 11!c 10!n 8!n 8!n 6!n 6!n
Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portugese National Clearing Code UK Domestic Sort Code South African National Clearing Code
CODES with options C or D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT RU SC 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portugese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code
136
MT 206
SW SW ZA
3..5n 6!n 6!n
Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES This field may only be used where the settlement is not following the same route as the cheque truncation message. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. Option A must be used whenever possible. Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. EXAMPLE :57A:MIDLGB2L
20. Field 58B: Beneficiary Institutions Account (for Settlement)

PRESENCE Optional DEFINITION This field specifies the account number of the financial institution which is the ultimate recipient of the funds being transferred. USAGE RULES The Party Identifier is to be used to specify the account to be credited, where: there are multiple direct account relationships in the currency of the transaction between the Sender and account with institution one of these accounts is to be used for reimbursement there is no bilaterally agreed account.
5 February 2007
137
EXAMPLE :58B:/123-45678
21. Field 19: Settlement Amount

FORMAT 17d (Amount)
PRESENCE Conditional (C5) DEFINITION If messages are chained, ie, field 28E does not contain the code ONLY, this field contains the settlement amount for this message. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32A, if present (Error code(s): C03,T40,T43). EXAMPLE :28E:9/MORE ... :32J:5300 :32J:5000 ... :19:10300,
MT 206 Mapping
Mapping of an MT 206 into a subsequent MT 206 (Receiver of first MT 206 becomes Sender of the second MT 206)
138
MT 206
Mapping of an MT 206 into a subsequent MT 202. (The Receiver of the MT 206 has a direct account relationship with the account with institution of the Sender in field 57a.)
Mapping of an MT 206 into a subsequent MT 202. (The Receiver of the MT 206 has no direct account relationship with the account with institution of the Sender in field 57a.)
5 February 2007
139
* If there is no direct account relationship between the party specified in field 57a of the MT 206 and the Receiver of the MT 206, then the Receiver of the related MT 202 becomes the common correspondent between the party specified in field 57a of the MT 206 and the Receiver of the MT 206. The party specified in field 57a of the MT 206 becomes field 57a of the related MT 202.
MT 206 Examples
Example 1 Travellers Cheques sent via an MT 206 with an Account With Institution
Narrative On December 1st 1998, Standard Bank of South Africa, Johannesburg (SBZAZAJJ), encashes and truncates the following Thomas Cook travellers cheques: TRN Cheque 1 Cheque 2 Cheque 3 Cheque 4 Cheque 5 Cheque 6 981201ABCD123456 9812010EFGH111123 9812010IJKL235693 981201ZZZZ123456AA 981201XXXX258950 981201YYYY569333 Cheque Number GB11111111 HB22222222 EB33333333 GB66666666 HB88888888 EB99999999 Amount GBP20, GBP50, GBP10, GBP20, GBP50, GBP10,
Standard Bank of South Africa wants the funds to be remitted on its account (555-888-9) with Natwest, London (NWBKGB2L) with value date 981207.
140
MT 206
Since Thomas Cook, London, has a multiple direct account relationship with Midland Bank, London (MIDLGB22), it will reimburse SBZAZAJJ using their account 123456 held with Midland Bank. As per its bilateral agreement, SBZAZAJJ safekeeps the original paper cheques. For the purpose of this example, two MT 206 are sent, each containing three items. Message A SWIFT MT 206 Cheque Truncation Message Information Flow
SWIFT Message, MT 206 (1) Explanation Sender SBZAZAJJ Format
5 February 2007
141
Explanation Message type Receiver Message text Senders reference Message index/total Cheque type Safekeeper Transaction reference number Cheque number Cheque amount Date of issue/encashment Transaction reference number Cheque number Cheque amount Date of encashment Transaction reference number Cheque number Cheque amount Date of encashment Settlement amount End of message text/trailer 206 COOKGB22
Format
:20:981201123456AA :28E:1/MORE :23E:TRAV :52A:SBZAZAJJ :44A:981201ABCD123456 :21D:GB11111111 :32J:20, :30:981201 :44A:9812010EFGH111123 :21D:HB22222222 :32J:50, :30:981201 :44A:9812010IJKL235693 :21D:EB33333333 :32J:10, :30:981201 :19:80,
SWIFT Message, MT 206 (2) Explanation Sender Message type SBZAZAJJ 206 Format
142
MT 206
Explanation Receiver Message text Senders reference Message index/total Cheque type Safekeeper Transaction reference number Cheque number Cheque amount Date of encashment Transaction reference number Cheque number Cheque amount Date of encashment Transaction reference number Cheque number Cheque amount Date of encashment Value date, currency code and sum of settlement amounts Account with institution Beneficiary institutions account Settlement amount End of message text/trailer COOKGB22
Format
:20:981201123456AA :28E:2/LAST :23E:TRAV :52A:SBZAZAJJ :44A:981201ZZZZ123456AA :21D:GB66666666 :32J:20, :30:981201 :44A:981201XXXX258950 :21D:HB88888888 :32J:50, :30:981201 :44A:981201YYYY569333 :21D:EB99999999 :32J:10, :30:981201 :32A:981207GBP160, :57A:NWBKGB2L :58B:/555-888-9 :19:80,
5 February 2007
143
Message B SWIFT MT 202 General Financial Institution Transfer Information Flow
SWIFT Message, MT 202 Explanation Sender Message type Receiver Message text COOKGB22 202 MIDLGB22 Format
144
MT 206
Explanation Transaction reference number Related reference Value date, currency code and amount Senders correspondent Account with institution Beneficiary institution End of message text/trailer
Format :20:IPD/00001/PAIDS :21:981201123456AA :32A:981207GBP160, :53B:/123456 :57A:NWBKGB2L :58A:/555-888-9 SBZAZAJJ
Example 2 General Cheques sent via an MT 206

Narrative On 8 January 2002, the following cheques are truncated by the Fortis Bank, Brussels (GEBABEBB): Cheque 1: Kreissparkasse in Siegburg (WELADED1), EUR 1000, cheque number 0007206657588 account 3869999 issued on 011212 in Oostende in favour of CMB, reference 3855026. Cheque 2: Stadtsparkasse in Dusseldorf (DUSSDEDD), EUR 500, cheque number 000721111 account 45678912 issued on 011214 in Namur in favour of Sofitel Wepion, reference 3855027. TRN Cheque 1 Cheque 2 3855026 3855027 Cheque Number 0007206657588 0000721111 Amount EUR1000, EUR500, Issuers A/C 3869999 45678912
Handling of the cheques is centralised in Fortis Bank, Brussels which truncates these cheques and sends them that same day to its German correspondent, Westdeutsche Landesbank Girozentrale, Dusseldorf (WELADEDD). There exists a bilateral agreement between Fortis Bank, Brussels and Westdeutsche Landesbank Girozentrale, Dusseldorf. As per this agreement, for cheques in euro, the Westdeutsches euro account held with Fortis Bank, Brussels will be debited with value date D+4. Information Flow
5 February 2007
145
SWIFT Message, MT 206 Explanation Sender Message type Receiver Message text Senders reference Message index/total :20:291342/0071115 :28E:1/ONLY GEBABEBB 206 WELADEDD Format
146
MT 206
Explanation Cheque type Cheque truncation indicator Safekeeper Transaction reference number Cheque number Cheque amount Issuers financial institution Issuers Account Number/Code Transaction reference number Cheque number Cheque amount Issuers financial institution Issuers account number/code Value date, currency code and total settlement amount End of message text/trailer :23E:GENC :17A:Y :52A:GEBABEBB :44A:3855026
Format
:21D:0007206657588 :32J:1000, :58A:WELADED1 :25:3869999 :44A:3855027 :21D:000721111 :32J:500, :58A:DUSSDEDD :25:45678912 :32A:020114EUR1500,
MT 206 Checklist
It is strongly recommended that the following checklist be used by financial institutions as a basis for setting up bilateral or multilateral agreements for processing truncated cheques. It is recommended that all items listed be covered in the bilateral or multilateral agreements. In order to further facilitate the setting up of these agreements, common procedures have been defined which financial institutions may choose to override. The checklist is not intended to provide an exhaustive list of items nor does SWIFT claim any responsibility for it. Topics may include:
Currency & amount

Specify minimum and maximum amounts per type of cheque Specify currencies accepted per type of cheque Set out the procedure to follow when there is a discrepancy between the code line and another field, eg, the amount Unless otherwise agreed, cheque truncation messages are expressed in either the currency of the sending or the receiving country. If financial institutions wish to accept third currencies this should be bilaterally agreed.
5 February 2007
147
Rules & regulations covering cheque truncation

Enumerate (inter)national laws and regulations Specify regulatory reporting requirements Specify the period within which a cheque can be protested, per type of cheque/place of issue (see also Dates and Time frames) Specify data or fields in the MTs 206 and 256 that are mandatory for legal purposes and processing requirements Define stale date List the criteria for cheque truncation An existing cash letter agreement could be extended to cater for cheque truncation as well. This may simplify the new agreement.
Responsibility
Endorsement issue - Agree on procedures to follow, eg, normally the beneficiarys financial institution must endorse that the party that cashes the cheque is the legitimate beneficial party Back of cheque - Since it is very difficult to automatically truncate this information, the truncation agreement should make it the truncating partys responsibility to ensure that the truncated cheques contain all legally required endorsements. Define the responsible parties at each stage of the whole process, eg, whether or not the beneficiarys financial institution can determine stale dated cheques. Also the agreement should establish the party responsible for verifying certain parts, eg, Code Line, of the truncated cheque. The capture and verification of the Code Line are key elements to the success of check truncation. Therefore, establish ways of avoiding bad code lines such as: using a specific control key to help manual keying when the code line is unreadable avoiding double truncation of a cheque through automatic checking at the point of capture.
Paper cheque
Specify which party must safekeep the original Agree the period the original must be kept Agree whether or not the cheque (or a copy) must be sent to the drawee bank and if so when Agree the route the paper cheque must follow, if any (where it differs from the truncation route).
Supported types of truncated cheques

Agree bilateral codes to indicate the type of electronic cheque/model/format.
Charges
Define the types of charges, per type of cheque, the currency and the amount Define the charging period, eg, once a month Unless otherwise agreed, charges will always be expressed in the same currency as the transaction amount(s) and settlement amount of the message.
Settlement
Where there is a direct account relationship between the Sender and Receiver of the MT 206, ie, field 57a is not present, the MT 206 can be used as a financial message to request to credit the account of the Sender automatically. If field 57a is present, an MT 202 must be sent to the party specified in that field. Whatever the agreement, transactions contained in a message will always be booked as a single entry.
148
MT 206
Administration
Define the contact address, eg, postal address, department, telephone number, fax number, to be used in the event of questions.
Dates and Time frames

Agree on the time frame required by the Receiver of the MT 206 to execute the payment of valid truncated cheques. This time frame starts at an agreed cut-off time for receipt of incoming messages by the Receiver. Messages received before the cut-off time, will receive final settlement on a pre-agreed day which is a (number of) day(s) following the day of receipt (day of receipt = D). For messages received after cut-off time, the final settlement time frame will be based on D+1. D is the basis for calculating the value date, ie, date when the funds are available to the Beneficiary. Agree the time frames for sending back charges. Determine the period in which items may be returned/dishonoured, and how such items should be conveyed, eg, CD-ROM, diskette, Internet, mail.
Remittance Information
Agree whether any, and if so which, information should be conveyed in field 72 through the use of bilaterally agreed codes.
5 February 2007
149
MT 207 Request For Financial Institution Transfer

MT 207 Scope
This message is used to move funds from the ordering financial institutions account, serviced at the receiving financial institution or at the account servicing institution, or from an account(s) owned by the ordering institution for which the initiating institution has explicit authority to debit, eg, a subsidiary account. It can be used to order the movement of funds: between the ordering institutions accounts, or in favour of a third party, either domestically or internationally. The message is sent by a financial institution on behalf of the ordering financial institution, ie, the account owning financial institution, or on behalf of the initiating financial institution. It is subsequently received by a financial institution and processed by this receiving financial institution or another account servicing financial institution. The complete chain of parties and the transaction flow is illustrated by the following figure:
150
MT 207
The parties mentioned in the chain are not necessarily different entities. The first column of the table below shows the parties that can be omitted in an MT 207. The second column specifies the party which assumes the role of the party in the first column, when it is not present:
5 February 2007
151
If the following party is missing... Initiating institution Account servicing institution Intermediary Account with institution
Its function is assumed by ... Ordering institution Receiver Account with institution Receiver

The MT 207 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. MT 207 Request for Financial Institution Transfer Status Tag Field Name Content/Options No.
Mandatory Sequence A General Information M O M M O M O O 20 21R 28D 30 51A 52G 52a 72 Senders Reference Specified Reference of the Ordering Institution Message Index/Total Requested Execution Date Initiating Institution Ordering Institution Account Servicing Institution Sender to Receiver Information 16x 16x 5n/5n 6!n [/1!a][/34x] 4!a2!a2!c[3!c] /34x 4!a2!a2!c[3!c] A or C 6*35x 1 2 3 4 5 6 7 8
----->Mandatory Repetitive Sequence B Transaction Details M -----> O -----| 23E Instruction Code 4!c[/30x] 10 21 Transaction Reference 16x 9
152
MT 207
Status M O O M -----|
Tag 32B 56a 57a 58a
Field Name Currency/Transaction Amount Intermediary Account With Institution Beneficiary Institution 3!a15d
Content/Options
No. 11
A or D 12 A, C or D 13 A or D 14
M = Mandatory O = Optional

C1 In each occurrence of Sequence B: If field 56a is present then field 57a must also be present (Error code(s): D65). If field 56a is ... Present Not present Mandatory Optional then field 57a is ...
MT 207 Usage Rules

If field 21R is present in sequence A, and field 28D indicates that more than one message is chained for this request for transfer instruction, the currency code must be the same for all occurrences of field 32B in sequence B of all chained messages. In case field 23E identifies with a code a sweeping (CMSW), topping (CMTO) or zero balancing (CMZB) operation, the transaction amount in field 32B can equal zero. In case field 28D indicates that messages are chained, all messages belonging to the same chain must have exactly the same senders reference in field 20. In case field 28D indicates that messages are chained, sequence A must be repeated and be identical for all messages belonging to the same chain.

5 February 2007
153
FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES The reference must be unique for each message (or chain of messages) and is part of the message identification and transaction identification which is to be used in related queries, cancellations, etc.
2. Field 21R: Specified Reference of the Ordering Institution

FORMAT Option R 16x
PRESENCE Optional DEFINITION This field specifies the reference to the entire message assigned by either the: initiating institution, when present or ordering institution, when the initiating institution is not present. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES When this field is present, the ordering institution requests a single debit entry for the sum of the amounts of all transactions in the instruction, even if this instruction is chained in several messages. If the field is not used, all debit items are posted individually.
3. Field 28D: Message Index / Total
154
MT 207
FORMAT Option D 5n/5n (Message Index)/(Total)
PRESENCE Mandatory DEFINITION This field chains different messages by specifying the sequence number in the total number of messages. USAGE RULES Both the message index and the total number of messages allow the receiver to check that all transactions to be executed have been received.
4. Field 30: Requested Execution Date

FORMAT 6!n (Date)
PRESENCE Mandatory DEFINITION This field specifies the date on which all subsequent transactions should be initiated by the executing bank. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). USAGE RULES This is the date on which the ordering institutions account is to be debited.
5. Field 51A: Initiating Institution

FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC)
PRESENCE Optional
5 February 2007
155
DEFINITION This field identifies the institution which is authorised by the ordering institution/account servicing institution to order all the transactions in the message. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations.(Error code(s): C05). USAGE RULES This field must only be used when the initiating institution is not also the ordering institution. Optional Party Identifier must not be used.
6. Field 52G: Ordering Institution

FORMAT Option G /34x 4!a2!a2!c[3!c] (Account) (BIC)
PRESENCE Mandatory DEFINITION This field identifies the account owning financial institution whose account is to be debited with all transactions in sequence(s) B. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES Account contains the account number of the ordering institution at the Receiver or at the account servicing institution. BIC contains the identification of the ordering institution.
7. Field 52a: Account Servicing Institution

FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Party Identifier)
156
MT 207
PRESENCE Optional DEFINITION This field specifies the account servicing institution - when other than the Receiver - which services the account of the ordering institution to be debited. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n Without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option C: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code
5 February 2007
157
BL CC CH CP ES FW GR HK IE IN IT PL PT RU SC SW SW
8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The coded information contained in field 52a should be meaningful to the Receiver of the message. Option A is the preferred option. If the account servicing institution cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double slash //.
158
MT 207

FORMAT 6*35x (Narrative - Structured Format )
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver, ie, Sender of the original message regarding the reason for a return, ie, reversal, rejection or revocal. CODES The codes REJT or RETN must be used in this field in the first position of the first line, placed between slashes (/). It is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. NETWORK VALIDATED RULES The first element in line 1 must contain either code /RETN/ or /REJT/ (Error code(s): D82). USAGE RULES The Reject/Return mechanism is used to reject or return all the transactions within the MT 207 message. For returns or rejections of a single transaction within the MT 207 (ie, sequence B), the MT 295 should be used as per the Standards Usage Guidelines.
9. Field 21: Transaction Reference

FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the unambiguous reference for the individual transaction contained in a particular occurrence of sequence B.
5 February 2007
159
NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). USAGE RULES In transaction specific queries, cancellations, etc., the Senders reference together with the content of this field provides the transaction identification.
10. Field 23E: Instruction Code

FORMAT Option E 4!c[/30x] (Instruction Code) (Additional Information)
PRESENCE Optional DEFINITION This field specifies instructions for the subsequent parties in the transaction chain. CODES One of the following codes must be used (Error code(s): T47). CMSW CMTO This transaction contains a cash management instruction, requesting to sweep the account of the ordering institution. This transaction contains a cash management instruction, requesting to top the account of the ordering institution above a certain floor amount. The floor amount, if not pre-agreed by the parties involved, may be specified after the code. This transaction contains a cash management instruction, requesting to zero balance the account of the ordering institution. This transaction contains a payment that is made in settlement of a trade, eg, foreign exchange deal, securities transaction. This transaction contains a payment that should be settled via a net settlement system, if available. Used for bilaterally agreed codes/information. The actual bilateral code/information needs to be specified in Additional Information. This transaction requires the beneficiary to be contacted by telephone and should be followed by the appropriate telephone number. This code is meant for the institution closest to the beneficiary institution This transaction contains a payment that should be settled via a real time gross settlement system, if available. This transaction contains a time sensitive payment which should be executed in an expeditious manner.
CMZB CORT NETS OTHR PHON
RTGS URGP
160
MT 207
NETWORK VALIDATED RULES Additional Information is only allowed when Instruction Code consists of one of the following codes: CMTO, PHON or OTHR (Error code(s): D66). In each occurrence of Sequence B: when this field is used more than once, the following combinations are not allowed (Error code(s): D67). CMSW CMSW CMTO CORT CORT CORT NETS with with with with with with with CMTO CMZB CMZB CMSW CMTO CMZB RTGS
In each occurrence of Sequence B: when this field is repeated, the same code word must not be present more than once with the exception of OTHR. The code word OTHR may be repeated (Error code(s): E46). USAGE RULES To facilitate the receiving banks processing when multiple codes are used, the codes must appear in the following order: instructions for the receiver of the message (CMSW, CMTO, CMZB, CORT, URGP) codes impacting the routing or composition of the resulting payment message (NETS, RTGS) codes containing instructions for one of the following parties in the transaction chain (PHON) information codes ( OTHR)
11. Field 32B: Currency/Transaction Amount

PRESENCE Mandatory DEFINITION This field specifies the currency and amount of the subsequent transfer to be executed by the Receiver.
5 February 2007
161
NETWORK VALIDATED RULES Currency must be the same for all occurrences of this field (Error code(s): C02). Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).

PRESENCE Optional DEFINITION This field specifies the financial institution between the Receiver and the account with institution, through which the transaction must pass to reach the account with institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC)
162
MT 207
IT PL PT SC
10!n 8!n 8!n 6!n
Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
5 February 2007
163
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES The intermediary may be a branch or affiliate of the Receiver or the account with institution, or an entirely different financial institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP or //IN is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier of field 56a, 57a or 58a. Option A is the preferred option. Option D must only be used in exceptional circumstances: when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver. Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considerations.

PRESENCE Conditional (C1) DEFINITION This field specifies the financial institution - when other than the Receiver - which services the account for the beneficiary institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//):
164
MT 207
with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with options C and D: AT AU BL CC CH CP ES FW GR 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code)
5 February 2007
165
HK IE IN IT PL PT RU SC SW SW
3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n 3..5n 6!n
Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When field 57a is not present, it means that the Receiver is also the account with institution. When one of the codes //FW (with or without the 9-digit number), //AU, //CP or //IN is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier of field 56a, 57a or 58a. Option A is the preferred option. Option D must only be used in exceptional circumstances: when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver. Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considerations.
166
MT 207
PRESENCE Mandatory DEFINITION This field specifies the beneficiary financial institution of the subsequent operation from the particular occurrence of sequence B. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR HK IE IN IT PL PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
5 February 2007
167
168
MT 207
USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //CP or //IN is used, it should appear only once and in the first of the fields 56a, 57a and 58a of the payment instruction. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier of field 56a, 57a or 58a. Party Identifier may contain the beneficiary financial institutions account number. If the message is used to request the transfer of funds between the ordering financial institutions accounts, this field must contain the BIC of this institution. Option A is the preferred option. Option D must only be used in exceptional circumstances: when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver. Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considerations.
MT 207 Examples
Narrative The Canadian Imperial Bank of Commerce, Canada (CIBCCATT) owns a euro account (account number 123456) at Deutsche Bank, Frankfurt (DEUTDEFF). The Canadian Imperial Bank of Commerce is a customer of Deutsche Bank, Toronto (DEUTCATT) and instructs this bank via a proprietary link to ask Deutsche Bank, Frankfurt to make a euro payment to Banco Bilbao Vizcaya Argentaria, Madrid, via an RTGS system, using CIBCCATTs EUR account at DEUTDEFF . Information Flow
5 February 2007
169
SWIFT Message Explanation Sender Message type Receiver Message text - General Information Senders Reference Message Index/Total Requested Execution Date Ordering Institution Message text - Transaction Details 1 Transaction Reference :21:REFBOF123 :20:ABCDEF :28D:1/1 :30:020110 :52G:/123456 CIBCCATT DEUTCATT 207 DEUTDEFF Format
170
MT 207
Explanation Instruction Code Currency/Transaction Amount Beneficiary Institution End of message text/trailer :23E:RTGS :32B:EUR500000, :58A:BBVAESMM
Format
5 February 2007
171
MT 210 Notice to Receive

MT 210 Scope
This message type is sent by an account owner to one of its account servicing institutions. It is an advance notice to the account servicing institution that it will receive funds to be credited to the Senders account.

MT 210 Notice to Receive Status M O M -----> M M O O O -----| M = Mandatory O = Optional 21 32B 50a 52a 56a Related Reference Currency Code, Amount Ordering Customer Ordering Institution Intermediary 16x 3!a15d C, No letter option or F C or no letter option A or D A or D 4 5 6 7 8 Tag 20 25 30 Field Name Transaction Reference Number Account Identification Value Date 16x 35x 6!n Content/Options No. 1 2 3

C1 The repetitive sequence must not appear more than ten times (Error code(s): T10). C2 Either field 50a or field 52a, but not both, must be present in a repetitive sequence (Error code(s): C06). If field 50a is... Present Not allowed then field 52a is ...
172
MT 210
If field 50a is... Not present Mandatory
then field 52a is ...
C3 The currency code must be the same for all occurrences of field 32B in the message (Error code(s): C02).

FORMAT 16x
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the instruction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :20:oref1000
2. Field 25: Account Identification

FORMAT 35x (Account)
PRESENCE Optional DEFINITION This field identifies the account to be credited with the incoming funds.
5 February 2007
173
USAGE RULES This field is used when the Receiver services more than one account for the Sender.

FORMAT 6!n (Date)
PRESENCE Mandatory DEFINITION This field contains the value date of all incoming funds specified in this message. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).

FORMAT 16x
PRESENCE Mandatory DEFINITION This field contains the content of field 20 Transaction Reference Number, or other reference, eg, Common Reference, of the related transaction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :21:ref1234

174
MT 210
PRESENCE Mandatory DEFINITION This field specifies the currency and amount to be received. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).
6. Field 50a: Ordering Customer

FORMAT Option C No letter option Option F 4!a2!a2!c[3!c] 4*35x 35x 4*35x (BEI) (Name & Address) (Party Identifier) (Name & Address)
With Option F, for Subfield 1 (Party Identifier) Line Format 1 or Line Format 2 must be used: /34x 4!a/30x (Account) (Code) (Identifier)
or
With Option F, for Subfield 2 (Name & Address) the following Line Format must be used for all lines: 1!n/33x (Number) (Details)
PRESENCE Conditional (C2) DEFINITION This field specifies the ordering party when it is not a financial institution. CODES With option F - Subfield 1 - Line Format 2 (Code) (Identifier): one of following codes must be used (Error code(s): T55). ARNU CCPT Alien Registration Number Passport Number The code followed by a slash, / must be followed by the ISO country code, a slash, / and the Alien Registration Number . The code followed by a slash, / must be followed by the ISO country code, a slash, / and the Passport Number.
5 February 2007
175
CUST
Customer Identification Number Drivers License Number Employer Number International Business Entity Identifier National Identity Number Social Security Number Tax Identification Number
The code followed by a slash, / must be followed by the ISO country code, a slash, /, the issuer of the number, a slash, / and the Customer Identification Number. The code followed by a slash, / must be followed by the ISO country code, a slash, /, the issuing authority, a slash, / and the Drivers License Number. The code followed by a slash, / must be followed by the ISO country code, a slash, /, the registration authority, a slash, / and the Employer Number . The code followed by a slash, / must be followed by the International Business Entity Identifier. The code followed by a slash, / must be followed by the ISO country code, a slash, / and the National Identity Number. The code followed by a slash, / must be followed by the ISO country code, a slash, / and the Social Security Number. The code followed by a slash, / must be followed by the ISO country code, a slash, / and the Tax Identification Number.
DRLC EMPL IBEI NIDN SOSE TXID
CODES With option F - Subfield 2 ( Name & Address): each line when present must contain one of the following codes (Error code(s): T56). 1 Name of the ordering customer Address Line The number followed by a slash, / must be followed by the name of the ordering customer (where it is recommended that the surname precedes given name(s)). The number followed by a slash, / must be followed by an Address Line (Address Line can be used to provide for example, streetname and number, or building name). The number followed by a slash, / must be followed by the ISO country code, a slash / and Town (Town can be complemented by postal code (for example zip), country subdivision (for example state, province, or county). The number followed by a slash, / must be followed by the Date of Birth in the YYYYMMDD format. The number followed by a slash, / must be followed by the ISO country code, a slash / and the Place of Birth. The number followed by a slash, / must be followed by the ISO country code, a slash, /, the issuer of the number, a slash, / and the Customer Identification Number . The number followed by a slash, / must be followed by the ISO country code, a slash, / and the National Identity Number . The number followed by a slash, / is followed by information completing the Identifier provided in field 50F, subfield 1 - line format 2
Country and Town
4 5 6
Date of Birth Place of Birth Customer Identification Number National Identity Number Additional Information
7 8
176
MT 210
NETWORK VALIDATED RULES The BIC must be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information on about BEIs .(Error code(s): T27,T28,T29, T45, E57). With option F, Subfield 1 (Party Identifier), one of the following line formats must be used (Error code(s): T54) : Line format 1 :/34x (Account) Line format 2 :4!a/30x (Code) (Identifier) With option F, Subfield 2 (Name & Address), the following line format must be used for all lines :1!n/33x (Number) (Details) . USAGE RULES If the account number of the ordering customer is present, it must be stated in Account. With option F - Subfield 1 - Line Format 2 (Code) (Identifier), if additional space is required for providing the Identifier of the ordering customer, one of the following options must be used: 1. First option (preferred): Identify the ordering customer with a different identifier where the length is not an issue. 2. Second option: Continue the information under Subfield 2 (Name & Address) using code 8 (See example 5) . With option F Subfield 2 ( Name & Address): Each code must appear on a separate line . Codes must appear in increasing numerical order. Codes may be repeated if more than one line is needed to provide the information indicated by the code for example 2 lines for address details. Code 2 must not be used without code 3 and vice versa. Code 4 must not be used without code 5 and vice versa. The use of code 8 is only allowed to continue information on the identification of the ordering customer provided under Subfield 1 - Line Format 2. EXAMPLE Option F - Example 1 :50F:/12345678 1/SMITH JOHN 2/299, PARK AVENUE 3/US/NEW YORK, NY 10017 Option F - Example 2 :50F:/BE30001216371411 1/PHILIPS MARK 4/19720830 5/BE/BRUSSELS Option F - Example 3 :50F:DRLC/BE/BRUSSELS/NB0949042 1/DUPONT JACQUES 2/HIGH STREET 6, APT 6C 3/BE/BRUSSELS
5 February 2007
177
Option F - Example 4 :50F:NIDN/DE/121231234342 1/MANN GEORG 6/DE/ABC BANK/1234578293 Option F - Example 5 :50F:CUST/DE/ABC BANK/123456789/8-123456 1/MANN GEORG 2/LOW STREET 7 3/DE/FRANKFURT 8/7890 This means that the customer identification number of Mann Georg assigned by ABC Bank is123456789/8-1234567890.

PRESENCE Conditional (C2) DEFINITION This field specifies the ordering party when it is a financial institution. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (//): with option A: AT AU BL CC ES FW GR 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code)
178
MT 210
HK IE IN IT PL PT SC
3!n 6!n 11!c 10!n 8!n 8!n 6!n
Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL PT RU SC 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 8!n 9!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code
5 February 2007
179
SW SW
3..5n 6!n
Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES When the Sender is also the ordering institution, it will be repeated in this field. The coded information contained in field 52a must be meaningful to the Receiver of the message. Option A is the preferred option. Option D should only be used when the ordering financial institution has no BIC.

PRESENCE Optional DEFINITION This field specifies the financial institution from which the Receiver is to receive the funds. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl
180
MT 210
CC ES FW GR HK IE IN IT PL PT SC ZA
9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n 6!n
Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code UK Domestic Sort Code South African National Clearing Code
CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC)
5 February 2007
181
IT PL PT RU SC SW SW ZA
10!n 8!n 8!n 9!n 6!n 3..5n 6!n 6!n
Italian Domestic Identification Code Polish National Clearing Code (KNR) Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES This field is used when the intermediary institution is other than the ordering party. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver.
MT 210 Examples
Narrative Value 22 February 1998, Berliner Bank, Berlin, as a result of a foreign exchange deal (Common Reference BEBEBB0023CRESZZ) with Credit Suisse, Zurich, is expecting US Dollars 230,000 to be credited to its account at Chase Manhattan Bank, New York. The funds will be paid through Citibank, New York. Berliner Bank sends an MT 210, using reference 318393.
182
MT 210
Information Flow
SWIFT Message, MT 210 Explanation Sender Message type Receiver Message text Transaction reference number :20:318393 BEBEDEBB 210 CHASUS33 Format
5 February 2007
183
Explanation Value Date Related reference (1) Currency code and amount Ordering institution Intermediary (2) End of message text/trailer :30:980222
Format
:21:BEBEBB0023CRESZZ :32B:USD230000, :52A:CRESCHZZ :56A:CITIUS33
(1) Field 21 of the incoming funds transfer. In this case, the reference contained in field 21 is a common reference from the related foreign exchange transaction. It will also appear in field 21 of the related funds transfer instruction. (2) The financial institution from which the funds will be received.
184
MT 256
MT 256 Advice of Non-Payment of Cheques

MT 256 Scope
This message is sent by the Receiver of one or more MT 206s. It is used to inform the Sender of (a) previously sent MT 206(s) of the non-payment of specified truncated cheques. This message may only be used to specify dishonoured items that result in reversing a previous payment settlement.

The MT 256 consists of three types of sequences: Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individual cheques detailed in sequence B. Sequence B Cheque Details is a repetitive sequence where each occurrence provides details of an individual cheque. Sequence C Settlement Details is a non-repetitive sequence and contains settlement information applicable to all cheques detailed in sequence B. MT 256 Advice of Non-Payment of Cheques Status Tag Field Name Content/Options No.
Mandatory Sequence A Common Elements M O 20 21 Senders Reference Related Message Reference 16x 16x 1 2
----->Mandatory Repetitive Sequence B Cheque Details M O O O M M O O 44A 21 21D 21E 23E 32J 37J 71G Transaction Reference Number Related Message Reference Cheque Number Cheque Reference Number Reason for Non-Payment/Dishonour Cheque Amount Interest Rate Interest Charges 65x 16x 35x 35x 4!c[/30x] 15d 12d 3!a15d 10 3 4 5 6 7 8 9
5 February 2007
185
Status O O -----|
Tag 71F 71H Senders Charges
Field Name 3!a15d
Content/Options
No. 11
Issuers Financial Institution Charges
3!a15d 12
Mandatory Sequence C Settlement Details M O O O O O O O 32A 30 19 71J 71L 71K 57a 58B Value Date, Currency Code and Total Amount Claimed Original Value Date Total Cheque Amount Sum of Interest Charges Sum of Senders Charges Sum of Issuers Financial Institution Charges Account With Institution (for Settlement) Beneficiary Institutions Account (for Settlement) M = Mandatory O = Optional 6!n3!a15d 13 6!n 14 17d 15 3!a15d 16 3!a15d 17 3!a15d 18 A, C or D 19 [/1!a][/34x] [35x] 20

C1 If field 37J is present, then field 71G must also be present (Error code(s): E25). If field 37J in sequence B is... Present Not present then field 71G in sequence B is... Mandatory Optional
186
MT 256
C2 The amount specified in field 71L in sequence C must be equal to the sum of all occurrences of field 71F in sequence B (Error code(s): E26). C3 The amount specified in field 71J in sequence C must be equal to the sum of all occurrences of field 71G in sequence B (Error code(s): E27). C4 The currency code in the amount fields (71F, 71G, 71H, 71J, 71K, 71L, 32A) must be the same for all occurrences of these fields in the message (Error code(s): C02). C5 If no changes are included, field 32A in sequence C contains the sum of the amounts of all fields 32J in sequence B. Field 19 must not be present (Error code(s): D80). C6 If charges are included, field 19 must be present. It must contain the sum of amounts of all fields 32J in sequence B (Error code(s): C01). C7 Field 21 must be present either in sequence A, or in all occurrences of sequence B (Error code(s): E28). If field 21 in sequence A is... Present Not present then field 21 in sequence B is... Not allowed Mandatory in all occurrences
If field 21 in sequence B is... Present Not present
then field 21 in sequence A is... Not allowed Mandatory
C8 If field 71F is present in any occurrence of sequence B, then field 71L must be present in sequence C. Otherwise, field 71L is not allowed (Error code(s): E29). If field 71F in sequence B is... Present in any occurrence Not present in any occurrence then field 71L in sequence C is... Mandatory Not allowed
5 February 2007
187
C9 If field 71G is present in any occurrence of sequence B, then field 71J must be present in sequence C. Otherwise, field 71J is not allowed (Error code(s): E30). If field 71G in sequence B is... Present in any occurrence Not present in any occurrence then field 71J in sequence C is... Mandatory Not allowed
C10 If field 71H is present in any occurrence of sequence B, then field 71K must be present in sequence C. Otherwise, field 71K is not allowed (Error code(s): E31). If field 71H in sequence B is... Present in any occurrence Not present in any occurrence then field 71K in sequence C is... Mandatory Not allowed
C11 The amount specified in field 71K in sequence C must be equal to the sum of all occurrences of field 71H in sequence B (Error code(s): E32).
MT 256 Usage Rules

The MT 256 can only be sent or received by financial institutions which have registered with SWIFT to send or receive the MT 206/MT 256. If a registered user receives an MT 256 without bilateral agreement with the Sender, the Receiver should query the message according to normal banking practice. This message must not be used to specify reasons that at a later stage could lead to a non-payment, eg, a request for a photocopy to check the signature. For this, an MT 295 Queries must be used, for which special codes are provided. For dishonoured cheques in different currencies, different MT 256s must be used. When the Sender does not have authority to debit the Receivers account, the Receiver of the MT 256 must credit the account according to the specified value date. Field 30 may only be used if the original value date differs from the value date provided in this field. Absence of field 30 implies that the value date in field 32A is taken from the original MT 206.

FORMAT 16x
188
MT 256
PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the instruction. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :20:oref1000
2. Field 21: Related Message Reference

FORMAT 16x
PRESENCE Conditional (C7) DEFINITION This field contains the Senders reference of the previously received MT 206 Cheque Truncation Message, ie, field 20 of the original MT 206. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :21:ref1234
3. Field 44A: Transaction Reference Number

FORMAT Option A 65x
PRESENCE Mandatory DEFINITION This field contains the TRN, field 20 of the previously received MT 206, generated by the beneficiarys financial institution, which identifies the transaction that this dishonoured cheque represents.
5 February 2007
189
EXAMPLE :44A:abc12354
4. Field 21: Related Message Reference

FORMAT 16x
PRESENCE Conditional (C7) DEFINITION This field contains the Senders reference of the previously received MT 206 Cheque Truncation Message in case this MT 256 is informing of the non-payment of cheques in the same currency that were included in different MTs 256. NETWORK VALIDATED RULES This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26). EXAMPLE :21:ref1234
5. Field 21D: Cheque Number

FORMAT Option D 35x
PRESENCE Optional DEFINITION This field contains the number of the cheque that has been dishonoured, normally inserted on the cheque by the issuers financial institution. USAGE RULES This field must be the same as the cheque number specified in the original MT 206. EXAMPLE :21D:9987434
190
MT 256
6. Field 21E: Cheque Reference Number

FORMAT Option E 35x
PRESENCE Optional DEFINITION This field contains the reference of the cheque, as generated by the beneficiarys financial institution. USAGE RULES This reference is usually the archive reference (microfilm) and is as such used as a link to the physical item. This field must be quoted if it is present in the original MT 206. EXAMPLE :21E:888014612
7. Field 23E: Reason for Non-Payment/Dishonour

FORMAT Option E 4!c[/30x] (Code) (Narrative)
PRESENCE Mandatory DEFINITION This field indicates why a cheque was dishonoured. CODES Code must contain one of the following codes (Error code(s): T47): AMAM AMTL CLOS COLN DRAW DUPL Amount exceeds the amount limit allowed for this account. Amount exceeds the truncation limit as defined in the bilateral agreement (min. or max. amount). Closed account. Error in code line. Refer to drawer. Duplicate cheque information.
5 February 2007
191
FRAU FROZ FRWD INCH INSF INSI INVA NELI NMAT OTHR REVO STLD STOP
Fraudulent cheque. (Legally) Frozen account. Forward dated cheque. Cheque number invalid. Insufficient funds. Insufficient information. Account number invalid. Cheques not eligible for truncation. Currency and account do not match. Other followed by a bilaterally agreed code to specify a reason which is not covered by the above. Revocation. Stale cheque, ie, deposited too late relative to the issue date. Stop payment of a cheque.
NETWORK VALIDATED RULES Narrative may only be used in combination with the code OTHR (Error code(s): D81). USAGE RULES The code OTHR may only be used when bilaterally agreed. When used, Narrative must also be present. EXAMPLE :23E:INSI
8. Field 32J: Cheque Amount

FORMAT Option J 15d (Amount)
PRESENCE Mandatory
192
MT 256
DEFINITION This field contains the amount specified on the dishonoured cheque. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32A (Error code(s): C03,T40,T43). USAGE RULES This field must be the same as the cheque amount specified in the original MT 206. EXAMPLE :32J:100000,
9. Field 37J: Interest Rate

FORMAT Option J 12d (Rate)
PRESENCE Optional DEFINITION This field specifies the interest rate to be collected from the Sender of the MT 206. NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).
10. Field 71G: Interest Charges

FORMAT Option G 3!a15d (Currency) (Amount)
PRESENCE Conditional (C1) DEFINITION This field specifies the currency and the interest charges due to the Sender of the MT 256.
5 February 2007
193
NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). USAGE RULES These interest charges are computed at a prevailing interest rate (field 37J) from the original value date (field 30) up to the date when recovery of funds is expected to take place (field 32A). EXAMPLE :71G:USD3,
11. Field 71F: Senders Charges

FORMAT Option F 3!a15d (Currency) (Amount)
PRESENCE Optional DEFINITION This field specifies the currency and the charges due to the Sender of the MT 256, if different from the issuers financial institution, for the above specified reason. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :71F:USD3,
12. Field 71H: Issuers Financial Institution Charges

FORMAT Option H 3!a15d (Currency) (Amount)
194
MT 256
PRESENCE Optional DEFINITION This field specifies the currency and the charges due to the issuers financial institution, for the above specified reason. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :71H:USD8,
13. Field 32A: Value Date, Currency Code and Total Amount Claimed
PRESENCE Mandatory DEFINITION This field specifies the date when the recovery of funds is expected to take place, followed by the currency and the total amount to be claimed. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :32A:961201USD1350,
14. Field 30: Original Value Date

FORMAT 6!n (Date)
5 February 2007
195
PRESENCE Optional DEFINITION This field specifies the value date that appeared on the related MT 206. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). USAGE RULES As this message is sent after provisional credit has been given to the beneficiary, any consequential interests can also be taken into account, by specifying that date. In this case, ie, when back-valuing is applied, no separate fields must be used to indicate the interest charges. EXAMPLE :30:980108
15. Field 19: Total Cheque Amount

FORMAT 17d (Amount)
PRESENCE Conditional (C5, C6) DEFINITION This field specifies the sum of all occurrences of field 32J in sequence B. NETWORK VALIDATED RULES The integer part of the Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of decimal digits in field 19 must not exceed the maximum for its corresponding currency in field 32A in sequence C (Error code(s): C03,T40,T43). EXAMPLE :19:1350,
16. Field 71J: Sum of Interest Charges

FORMAT Option J 3!a15d (Currency) (Amount)
196
MT 256
PRESENCE Conditional (C9) DEFINITION This field specifies the currency and the sum of all occurrences of field 71G in sequence B. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :71J:USD50,
17. Field 71L: Sum of Senders Charges

FORMAT Option L 3!a15d (Currency) (Amount)
PRESENCE Conditional (C8) DEFINITION This field specifies the currency and the sum of all occurrences of field 71F in sequence B. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :71L:USD234,
18. Field 71K: Sum of Issuers Financial Institution Charges

FORMAT Option K 3!a15d (Currency) (Amount)
5 February 2007
197
PRESENCE Conditional (C10) DEFINITION This field specifies the currency and the sum of all occurrences of field 71H in sequence B. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43). EXAMPLE :71K:USD343,
19. Field 57a: Account With Institution (for Settlement)

PRESENCE Optional DEFINITION This field identifies the account with institution at which the Sender wants to have the funds (re)credited . CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used, preceded by a double slash //: with option A: AT AU BL CC ES 5!n 6!n 8!n 9!n 8..9n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code
198
MT 256
FW GR HK IE IN IT PL PT SC ZA
without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 8!n 6!n 6!n
Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR) Portugese National Clearing Code UK Domestic Sort Code South African National Clearing Code
CODES with options C or D: AT AU BL CC CH CP ES FW GR HK IE IN IT PL 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Polish National Clearing Code (KNR)
5 February 2007
199
PT RU SC SW SW ZA
8!n 9!n 6!n 3..5n 6!n 6!n
Portugese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code
NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45). The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05). USAGE RULES This field may only be used where the settlement does not follow the same route as the MT 256 (this message). When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that the code //FW appears in the optional Party Identifier. Option A must be used whenever possible. Option D must only be used in exceptional circumstances: ie, when the party cannot be identified by a BIC, when there is a need to be able to specify a name and address, for example, due to regulatory considerations or when there is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver. When qualified by a clearing system code or an account number, the use of option D will enable the automated processing of the instruction(s) by the Receiver. EXAMPLE :57A:MIDLGB2L
20. Field 58B: Beneficiary Institutions Account (for Settlement)

PRESENCE Optional
200
MT 256
DEFINITION This field specifies the account number of the financial institution which is the ultimate recipient of the funds being (re)transferred (i.e. the Receiver of the MT 206) . USAGE RULES Party Identifier is to be used to specify the account to be credited, where there are multiple direct account relationships in the currency of the transaction between the Sender and account with institution one of these accounts is to be used for reimbursement there is no bilaterally agreed account. EXAMPLE :58B:/123-45678
MT 256 Mapping
Mapping of an MT 206 into a subsequent MT 256 (Receiver of the MT 206 becomes Sender of the MT 256).
5 February 2007
201
MT 256 Examples
Narrative On December 10, 1998, Thomas Cook, London informs Standard Bank of South Africa, Johannesburg that the following travellers cheques are dishonoured in the MT 206 it received from Standard Bank of South Africa (message reference 981201123456AA).
202
MT 256
TRN Cheque 1 Cheque 2 9812010IJKL235693 981201ZZZZ123456AA
Cheque Number EB33333333 GB66666666
Amount GBP10, GBP20,
Reason for dishonour Stopped cheque Invalid cheque number
Since Thomas Cook, London has already reimbursed Standard Bank of South Africa, it wants to have the funds recredited to its account held at Midland Bank, London (account number 123456), back-valuing the amount with the value date used on the original MT 206 (original value date 981207). Information Flow
SWIFT Message, MT 256 Explanation Sender Message Type Receiver Message Text COOKGB22 256 SBZAZAJJ Format
5 February 2007
203
Explanation Senders Reference Related Message Reference Transaction Reference Number Cheque Number Reason for Non-Payment/Dishonour Cheque Amount Transaction Reference Number Cheque Number Reason for Non-Payment/Dishonour Cheque Amount Value Date, Currency Code and Total Amount Claimed Account With Institution Beneficiary Institutions Account End of Message Text/Trailer
Format :20:IPD/S0001/PAIDS :21:981201123456AA :44A:981201IJKL235693 :21D:EB33333333 :23E:STOP :32J:10, :44A:981201ZZZZ123456AA :21D:GB66666666 :23E:INCH :32J:20, :32A:981207GBP30, :57A:MIDLGB22 :58B:/123456
MT 256 Checklist
For a checklist of topics that should be included in bilateral or multilateral agreements for processing truncated cheques, see MT 206 Checklist.
204
MT 290
MT 290 Advice of Charges, Interest and Other Adjustments

Please refer to Category n - Common Group Messages, Chapter n90 Advice of Charges, Interest and Other Adjustments for details concerning this message type.
5 February 2007
205
MT 291 Request for Payment of Charges, Interest and Other Expenses

Please refer to Category n - Common Group Messages, Chapter n91 Request for Payment of Charges, Interest and other Expenses for details concerning this message type.
206
MT 292
MT 292 Request for Cancellation

Please refer to Category n - Common Group Messages, Chapter n92 Request for Cancellation for details concerning this message type.
5 February 2007
207
MT 295 Queries
Please refer to Category n - Common Group Messages, Chapter n95 Queries for details concerning this message type.
208
MT 296
MT 296 Answers
Please refer to Category n - Common Group Messages, Chapter n96 Answers for details concerning this message type.
5 February 2007
209
MT 298 Proprietary Message

Please refer to Category n - Common Group Messages, Chapter n98 Proprietary Message for details concerning this message type.
210
MT 299
MT 299 Free Format Message

Please refer to Category n - Common Group Messages, Chapter n99 Free Format Message for details concerning this message type.
5 February 2007
211
Glossary of Terms
In addition to the definitions which appear in Standards General Information, Glossary of Terms, the following terms apply to category 2 message types: Available Funds Funds available for transfer or withdrawal in cash. Bankleitzahl An eight digit numeric code used to identify banks in Germany. It may only be assigned, changed or cancelled by Deutsche Bundesbank, in Germany. CHIPS (Clearing House Interbank Payments System) A private telecommunications payment service operated by the New York Clearing House Association for banks in the New York area, which handles US dollar payments only. CHIPS Participant A bank authorised to send and receive payments on the CHIPS system. CHIPS Participant ID (ABA Number) A unique number identifying a CHIPS participant. The first four digits are the participants number, followed by a one digit group identifier. For S.W.I.F.T. purposes, only the first four digits of the CHIPS Participant ID will be used. CHIPS Settling Participant A CHIPS Participant responsible for the settlement of its own CHIPS net debit or credit position at the end of the CHIPS business day. CHIPS Universal Identifier A unique six digit number assigned by CHIPS to identify an account. Cover Payment The reimbursement of a correspondent bank for a payment. Federal Funds US dollars on deposit at a Federal Reserve Bank in the United States. Fedwire A payment service operated by the US Federal Reserve System as a private wire network for transfers between financial institutions having accounts at the Federal Reserve Bank. Fedwire Routing Number A nine digit numeric code used to identify banks in the United States. Funds Transfer Complete movement of funds between the originator and the beneficiary. A funds transfer may consist of one or more funds transfer transactions. Funds Transfer Transaction The movement of funds directly between two parties, involving no intermediaries other than a payment or communications service. Immediate Funds Same day funds in which the settlement is simultaneous with execution of the transaction. Instructing Party The party instructing the Sender to execute a transaction.
212
Glossary of Terms
Originator Initiator of the transfer instructions. Equivalent to the ordering institution (field 52a) in the MT 202. Originators Institution Identifies the financial institution which is acting for the originator of the transfer. Remitter The party which is the source of funds in a payment order. Same Day Funds The funds available for transfer today, or for withdrawal in cash, subject to the settlement of the transaction through the payment mechanism used. Settlement A transfer of funds to complete one or more prior transactions made, subject to final accounting.
5 February 2007
213
Table Of Contents
Table of Contents
Copyright . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . Summary of Changes . . . . . . . . . . . . . . . . . Added Message Types . . . . . . . . . . . . . . . . Removed Message Types . . . . . . . . . . . . . . . . Modified Message Types . . . . . . . . . . . . . . . . Category 2 Message Types . . . . . . . . . . . . . . . . . Euro - Impact on Category Message Standards . . . . . . . . . . . . MT 200 Financial Institution Transfer for its Own Account . . . . . . . . . . MT 200 Scope . . . . . . . . . . . . . . . . . . . MT 200 Format Specifications . . . . . . . . . . . . . . . MT 200 Network Validated Rules . . . . . . . . . . . . . . . MT 200 Usage Rules . . . . . . . . . . . . . . . . . MT 200 Field Specifications (updated) . . . . . . . . . . . . . 1. Field 20: Transaction Reference Number . . . . . . . . . . . . 2. Field 32A: Value Date, Currency Code, Amount . . . . . . . . . . 3. Field 53B: Senders Correspondent . . . . . . . . . . . . . 4. Field 56a: Intermediary (updated) . . . . . . . . . . . . . 5. Field 57a: Account With Institution (updated) . . . . . . . . . . . 6. Field 72: Sender to Receiver Information . . . . . . . . . . . . MT 200 Examples . . . . . . . . . . . . . . . . . . Example 1 Financial Institution Transfer for its Own Account with an Account With Institution Example 2 Financial Institution Transfer for its Own Account with an Intermediary . . . MT 201 Multiple Financial Institution Transfer for its Own Account . . . . . . . MT 201 Scope . . . . . . . . . . . . . . . . . . . MT 201 Format Specifications . . . . . . . . . . . . . . . MT 201 Network Validated Rules . . . . . . . . . . . . . . . MT 201 Usage Rules . . . . . . . . . . . . . . . . . MT 201 Field Specifications (updated) . . . . . . . . . . . . . 1. Field 19: Sum of Amounts . . . . . . . . . . . . . . . 2. Field 30: Value Date . . . . . . . . . . . . . . . . 3. Field 53B: Senders Correspondent . . . . . . . . . . . . . 4. Field 72: Sender to Receiver Information . . . . . . . . . . . . 5. Field 20: Transaction Reference Number . . . . . . . . . . . . 6. Field 32B: Currency Code, Amount . . . . . . . . . . . . . 7. Field 56a: Intermediary (updated) . . . . . . . . . . . . . 8. Field 57a: Account With Institution (updated) . . . . . . . . . . . 9. Field 72: Sender to Receiver Information . . . . . . . . . . . . MT 201 Examples . . . . . . . . . . . . . . . . . . MT 202 General Financial Institution Transfer . . . . . . . . . . . . MT 202 Scope . . . . . . . . . . . . . . . . . . . MT 202 Format Specifications . . . . . . . . . . . . . . . MT 202 Network Validated Rules . . . . . . . . . . . . . . . MT 202 Usage Rules . . . . . . . . . . . . . . . . . MT 202 Field Specifications (updated) . . . . . . . . . . . . . 1. Field 20: Transaction Reference Number . . . . . . . . . . . . 2. Field 21: Related Reference . . . . . . . . . . . . . . . 3. Field 13C: Time Indication . . . . . . . . . . . . . . . 4. Field 32A: Value Date, Currency Code, Amount . . . . . . . . . . 5. Field 52a: Ordering Institution . . . . . . . . . . . . . . 6. Field 53a: Senders Correspondent . . . . . . . . . . . . . 7. Field 54a: Receivers Correspondent . . . . . . . . . . . . . 8. Field 56a: Intermediary (updated) . . . . . . . . . . . . . 9. Field 57a: Account With Institution (updated) . . . . . . . . . . . 10. Field 58a: Beneficiary Institution (updated) . . . . . . . . . . . 11. Field 72: Sender to Receiver Information . . . . . . . . . . . . MT 202 Examples . . . . . . . . . . . . . . . . . . Example 1 MT 202 as a Cover Payment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 3 3 3 3 4 6 7 7 7 7 7 7 8 8 8 9 11 14 15 15 17 19 19 19 20 20 20 20 20 21 21 23 23 23 26 29 30 33 33 33 34 34 34 34 34 35 36 37 39 40 41 43 46 49 50 50
5 February 2007
Table Of Contents
Message A SWIFT MT 103 Single Customer CreditTransfer . . . . . . . . . . . 51 . Message B SWIFT MT 202 Cover Message . . . . . . . . . . . . . . . 52 . Example 2 MT 202 with Time Indication . . . . . . . . . . . . . . . . 53 . MT 203 Multiple General Financial Institution Transfer . . . . . . . . . . . . . . 55 . MT 203 Scope . . . . . . . . . . . . . . . . . . . . . . 55 . MT 203 Format Specifications . . . . . . . . . . . . . . . . . . . 55 . MT 203 Network Validated Rules . . . . . . . . . . . . . . . . . . 56 . MT 203 Usage Rules . . . . . . . . . . . . . . . . . . . . . 56 . MT 203 Field Specifications (updated) . . . . . . . . . . . . . . . . . 56 . 1. Field 19: Sum of Amounts . . . . . . . . . . . . . . . . . . 57 . 2. Field 30: Value Date . . . . . . . . . . . . . . . . . . . . 57 . 3. Field 52a: Ordering Institution . . . . . . . . . . . . . . . . . . 57 . 4. Field 53a: Senders Correspondent . . . . . . . . . . . . . . . . . 59 . 5. Field 54a: Receivers Correspondent . . . . . . . . . . . . . . . . 60 . 6. Field 72: Sender to Receiver Information . . . . . . . . . . . . . . . 61 . 7. Field 20: Transaction Reference Number . . . . . . . . . . . . . . . 63 . 8. Field 21: Related Reference . . . . . . . . . . . . . . . . . . 63 . 9. Field 32B: Currency Code, Amount . . . . . . . . . . . . . . . . 64 . 10. Field 56a: Intermediary (updated) . . . . . . . . . . . . . . . . . 64 . 11. Field 57a: Account With Institution (updated) . . . . . . . . . . . . . . 67 . 12. Field 58a: Beneficiary Institution (updated) . . . . . . . . . . . . . . 70 . 13. Field 72: Sender to Receiver Information . . . . . . . . . . . . . . . 72 . MT 203 Examples . . . . . . . . . . . . . . . . . . . . . 74 . MT 204 Financial Markets Direct Debit Message . . . . . . . . . . . . . . . 78 . MT 204 Scope . . . . . . . . . . . . . . . . . . . . . . 78 . MT 204 Format Specifications . . . . . . . . . . . . . . . . . . . 78 . MT 204 Network Validated Rules . . . . . . . . . . . . . . . . . . 79 . MT 204 Usage Rules . . . . . . . . . . . . . . . . . . . . . 79 . MT 204 Field Specifications . . . . . . . . . . . . . . . . . . . 79 . 1. Field 20: Transaction Reference Number . . . . . . . . . . . . . . . 79 . 2. Field 19: Sum of Amounts . . . . . . . . . . . . . . . . . . 80 . 3. Field 30: Value Date . . . . . . . . . . . . . . . . . . . . 80 . 4. Field 57a: Account With Institution . . . . . . . . . . . . . . . . 80 . 5. Field 58a: Beneficiary Institution . . . . . . . . . . . . . . . . . 83 . 6. Field 72: Sender to Receiver Information . . . . . . . . . . . . . . . 85 . 7. Field 20: Transaction Reference Number . . . . . . . . . . . . . . . 87 . 8. Field 21: Related Reference . . . . . . . . . . . . . . . . . . 88 . 9. Field 32B: Transaction Amount . . . . . . . . . . . . . . . . . 88 . 10. Field 53a: Debit Institution . . . . . . . . . . . . . . . . . . 88 . 11. Field 72: Sender to Receiver Information . . . . . . . . . . . . . . . 89 . MT 204 Examples . . . . . . . . . . . . . . . . . . . . . 91 . Example 1 The Exchange and the Member have a Common Correspondent Bank . . . . . . . 91 . Example 2 The Exchange does not want to use the account relationship with the common correspondent and wants the funds to be transferred to another institution . . . . . . . . . . . . . . 94 . MT 205 Financial Institution Transfer Execution . . . . . . . . . . . . . . . 96 . MT 205 Scope . . . . . . . . . . . . . . . . . . . . . . 96 . MT 205 Format Specifications . . . . . . . . . . . . . . . . . . . 96 . MT 205 Network Validated Rules . . . . . . . . . . . . . . . . . . 96 . MT 205 Field Specifications (updated) . . . . . . . . . . . . . . . . . 97 . 1. Field 20: Transaction Reference Number . . . . . . . . . . . . . . . 97 . 2. Field 21: Related Reference . . . . . . . . . . . . . . . . . . 97 . 3. Field 13C: Time Indication . . . . . . . . . . . . . . . . . . 97 . 4. Field 32A: Value Date, Currency Code, Amount . . . . . . . . . . . . . . 99 . 5. Field 52a: Ordering Institution . . . . . . . . . . . . . . . . . . 99 . 6. Field 53a: Senders Correspondent . . . . . . . . . . . . . . . . . 101 . 7. Field 56a: Intermediary (updated) . . . . . . . . . . . . . . . . . 102 . 8. Field 57a: Account With Institution (updated) . . . . . . . . . . . . . . 105 . 9. Field 58a: Beneficiary Institution (updated) . . . . . . . . . . . . . . . 107 . 10. Field 72: Sender to Receiver Information . . . . . . . . . . . . . . . 110 . MT 205 Examples . . . . . . . . . . . . . . . . . . . . . 111 . MT 206 Cheque Truncation Message . . . . . . . . . . . . . . . . . . 115 . MT 206 Scope . . . . . . . . . . . . . . . . . . . . . . 115 .
ii
Table Of Contents
MT 206 Format Specifications . . . . . . . . . . . . . MT 206 Network Validated Rules . . . . . . . . . . . . MT 206 Usage Rules . . . . . . . . . . . . . . . MT 206 Field Specifications (updated) . . . . . . . . . . . 1. Field 20: Senders Reference . . . . . . . . . . . . 2. Field 28E: Message Index/Total . . . . . . . . . . . 3. Field 23E: Cheque Type . . . . . . . . . . . . . 4. Field 17A: Cheque Truncation Indicator . . . . . . . . . 5. Field 52a: Safekeeper . . . . . . . . . . . . . . 6. Field 44A: Transaction Reference Number . . . . . . . . . 7. Field 21D: Cheque Number . . . . . . . . . . . . 8. Field 21E: Cheque Reference Number . . . . . . . . . . 9. Field 29a: Code Line (updated) . . . . . . . . . . . 10. Field 32J: Cheque Amount . . . . . . . . . . . . 11. Field 58a: Issuers Financial Institution . . . . . . . . . 12. Field 25: Issuers Account Number/Code . . . . . . . . . 13. Field 26E: Represented Cheque Entry . . . . . . . . . . 14. Field 30: Date of Issue/Encashment . . . . . . . . . . 15. Field 39C: Place of Issue/Encashment . . . . . . . . . . 16. Field 52a: Safekeeper . . . . . . . . . . . . . 17. Field 72: Sender to Receiver Information . . . . . . . . . 18. Field 32A: Value Date, Currency Code and Sum of Settlement Amounts . . 19. Field 57a: Account With Institution (for Settlement) . . . . . . . 20. Field 58B: Beneficiary Institutions Account (for Settlement) . . . . . 21. Field 19: Settlement Amount . . . . . . . . . . . . MT 206 Mapping . . . . . . . . . . . . . . . . MT 206 Examples . . . . . . . . . . . . . . . Example 1 Travellers Cheques sent via an MT 206 with an Account With Institution Example 2 General Cheques sent via an MT 206 . . . . . . . . MT 206 Checklist . . . . . . . . . . . . . . . Currency & amount . . . . . . . . . . . . . . . Rules & regulations covering cheque truncation . . . . . . . . Responsibility . . . . . . . . . . . . . . . . Paper cheque . . . . . . . . . . . . . . . . Supported types of truncated cheques . . . . . . . . . . . Charges . . . . . . . . . . . . . . . . . Settlement . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . Dates and Time frames . . . . . . . . . . . . . . Remittance Information . . . . . . . . . . . . . . MT 207 Request For Financial Institution Transfer . . . . . . . . . MT 207 Scope . . . . . . . . . . . . . . . . MT 207 Format Specifications . . . . . . . . . . . . . MT 207 Network Validated Rules . . . . . . . . . . . . MT 207 Usage Rules . . . . . . . . . . . . . . . MT 207 Field Specifications (updated) . . . . . . . . . . . 1. Field 20: Senders Reference . . . . . . . . . . . . 2. Field 21R: Specified Reference of the Ordering Institution . . . . . 3. Field 28D: Message Index / Total . . . . . . . . . . . 4. Field 30: Requested Execution Date . . . . . . . . . . 5. Field 51A: Initiating Institution . . . . . . . . . . . 6. Field 52G: Ordering Institution . . . . . . . . . . . 7. Field 52a: Account Servicing Institution . . . . . . . . . 8. Field 72: Sender to Receiver Information . . . . . . . . . 9. Field 21: Transaction Reference . . . . . . . . . . . 10. Field 23E: Instruction Code . . . . . . . . . . . . 11. Field 32B: Currency/Transaction Amount . . . . . . . . . 12. Field 56a: Intermediary (updated) . . . . . . . . . . . 13. Field 57a: Account With Institution (updated) . . . . . . . . 14. Field 58a: Beneficiary Institution (updated) . . . . . . . . MT 207 Examples . . . . . . . . . . . . . . . MT 210 Notice to Receive . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115 . 116 . 118 . 119 . 119 . 119 . 120 . 121 . 121 . 124 . 124 . 124 . 125 . 126 . 126 . 129 . 129 . 129 . 130 . 130 . 133 . 134 . 135 . 137 . 138 . 138 . 140 . 140 . 145 . 147 . 147 . 148 . 148 . 148 . 148 . 148 . 148 . 149 . 149 . 149 . 150 . 150 . 152 . 153 . 153 . 153 . 153 . 154 . 154 . 155 . 155 . 156 . 156 . 159 . 159 . 160 . 161 . 162 . 164 . 166 . 169 . 172 .
5 February 2007
iii
Table Of Contents
MT 210 Scope . . . . . . . . . . . . . MT 210 Format Specifications (updated) . . . . . . . MT 210 Network Validated Rules . . . . . . . . . MT 210 Field Specifications (updated) . . . . . . . . 1. Field 20: Transaction Reference Number . . . . . . 2. Field 25: Account Identification . . . . . . . . 3. Field 30: Value Date . . . . . . . . . . . 4. Field 21: Related Reference . . . . . . . . . 5. Field 32B: Currency Code, Amount . . . . . . . 6. Field 50a: Ordering Customer (updated) . . . . . . 7. Field 52a: Ordering Institution . . . . . . . . . 8. Field 56a: Intermediary (updated) . . . . . . . . MT 210 Examples . . . . . . . . . . . . MT 256 Advice of Non-Payment of Cheques . . . . . . . MT 256 Scope . . . . . . . . . . . . . MT 256 Format Specifications . . . . . . . . . . MT 256 Network Validated Rules . . . . . . . . . MT 256 Usage Rules . . . . . . . . . . . . MT 256 Field Specifications (updated) . . . . . . . . 1. Field 20: Senders Reference . . . . . . . . . 2. Field 21: Related Message Reference . . . . . . . 3. Field 44A: Transaction Reference Number . . . . . . 4. Field 21: Related Message Reference . . . . . . . 5. Field 21D: Cheque Number . . . . . . . . . 6. Field 21E: Cheque Reference Number . . . . . . . 7. Field 23E: Reason for Non-Payment/Dishonour . . . . . 8. Field 32J: Cheque Amount . . . . . . . . . 9. Field 37J: Interest Rate . . . . . . . . . . 10. Field 71G: Interest Charges . . . . . . . . . 11. Field 71F: Senders Charges . . . . . . . . . 12. Field 71H: Issuers Financial Institution Charges . . . . 13. Field 32A: Value Date, Currency Code and Total Amount Claimed 14. Field 30: Original Value Date . . . . . . . . 15. Field 19: Total Cheque Amount . . . . . . . . 16. Field 71J: Sum of Interest Charges . . . . . . . 17. Field 71L: Sum of Senders Charges . . . . . . . 18. Field 71K: Sum of Issuers Financial Institution Charges . . . 19. Field 57a: Account With Institution (for Settlement) (updated) . 20. Field 58B: Beneficiary Institutions Account (for Settlement) . . MT 256 Mapping . . . . . . . . . . . . . MT 256 Examples . . . . . . . . . . . . MT 256 Checklist . . . . . . . . . . . . MT 290 Advice of Charges, Interest and Other Adjustments . . . . MT 291 Request for Payment of Charges, Interest and Other Expenses . MT 292 Request for Cancellation . . . . . . . . . . MT 295 Queries . . . . . . . . . . . . . MT 296 Answers . . . . . . . . . . . . . MT 298 Proprietary Message . . . . . . . . . . . MT 299 Free Format Message . . . . . . . . . . Glossary of Terms . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172 . 172 . 172 . 173 . 173 . 173 . 174 . 174 . 174 . 175 . 178 . 180 . 182 . 185 . 185 . 185 . 186 . 188 . 188 . 188 . 189 . 189 . 190 . 190 . 191 . 191 . 192 . 193 . 193 . 194 . 194 . 195 . 195 . 196 . 196 . 197 . 197 . 198 . 200 . 201 . 202 . 204 . 205 . 206 . 207 . 208 . 209 . 210 . 211 . 212 .
iv

Swiftstandard

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Swiftstandard

Uploaded by

Copyright:

Available Formats

SWIFTStandards

Category 2 Financial Institution Transfers

Message Reference Guide

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

Message Reference Guide - Standards Release Guide - February 2007

Removed Message Types

Modified Message Types

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

Category 2 Message Types

Max. Length 2,000

204 205 206

2,000 2,000 10,000

Notice to Receive Advice of Non-Payment of Cheques

Advice of Charges, Interest and Other Adjustments

Message Reference Guide - Standards Release Guide - February 2007

Category 2 Message Types

Max. Length 2,000

292 295 296

2,000 2,000 2,000

Proprietary Message Free Format Message

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

Euro - Impact on Category Message Standards

Message Reference Guide - Standards Release Guide - February 2007

MT 200 Financial Institution Transfer for its Own Account

MT 200 Format Specifications

MT 200 Network Validated Rules

MT 200 Usage Rules

MT 200 Field Specifications

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

1. Field 20: Transaction Reference Number

2. Field 32A: Value Date, Currency Code, Amount

3. Field 53B: Senders Correspondent

Message Reference Guide - Standards Release Guide - February 2007

4. Field 56a: Intermediary

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

3!n 6!n 11!c 10!n 8!n 8!n

UK Domestic Sort Code South African National Clearing Code

Message Reference Guide - Standards Release Guide - February 2007

RT RU SC SW SW ZA 9!n 6!n 3..5n 6!n 6!n

5. Field 57a: Account With Institution

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

Message Reference Guide - Standards Release Guide - February 2007

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

6. Field 72: Sender to Receiver Information

Message Reference Guide - Standards Release Guide - February 2007

PHONIBK REC TELE TELEIBK

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

Message Reference Guide - Standards Release Guide - February 2007

SWIFT Message Explanation Sender BKAUATWW Format

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

:32A:020524USD1000000, :53B:/34554-3049 :56A:CITIUS33 :57A:CITIUS33MIA

Message Reference Guide - Standards Release Guide - February 2007

MT 201 Multiple Financial Institution Transfer for its Own Account

MT 201 Format Specifications

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

MT 201 Network Validated Rules

MT 201 Usage Rules

MT 201 Field Specifications

2. Field 30: Value Date

Message Reference Guide - Standards Release Guide - February 2007

3. Field 53B: Senders Correspondent

4. Field 72: Sender to Receiver Information

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007