swiftstandard

SWIFTStandards

Category 2Financial Institution Transfers

For SWIFTStandards MT October 2007

Message Reference GuideStandards Release Guide - February 2007

This reference guide contains the category 2 message text standards, including a detailed description of the scope, theformat specifications, the rules, the guidelines, and the field specifications of each message type .

5 February 2007

1

Copyright

Copyright © S.W.I.F.T. SCRL ("SWIFT"), avenue Adèle 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, SWIFT-Watch, 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 20072

Category 2 - Financial Institution Transfers for SWIFTStandards MT October 2007

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

35 February 2007

Introduction

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), themaximum message length on input (2,000 or 10,000 characters), whether the use of the message requires registration withSWIFT 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 Purpose Authen. Max. Length

MUG VDO

200 Financial Institution Transfer for its Own Account

Requests the movement of the Sender’s funds toits account at another financial institution

Y 2,000 N Y

201 Multiple Financial Institution Transferfor its Own Account

Multiple of the MT 200 Y 2,000 N Y

202 General Financial Institution Transfer

Requests the movement of funds between finan-cial institutions

Y 2,000 N Y

203 Multiple General Financial Institution Transfer

Multiple of the MT 202 Y 2,000 N Y

204 Financial MarketsDirect Debit Message

Claims funds from SWIFT member banks Y 2,000 Y Y

205 Financial Institution Transfer Execution

Further transmits a transfer request domestically Y 2,000 N Y

206 Cheque Truncation Message

Conveys information about one or more truncatedcheques in order to debit or obtain credit underusual reserve

Y 10,000 Y Y

207 Request for Financial Institution Transfer

Requests to debit an ordering financial institu-tion’s account held at the receiving financial institution or the account servicing financial insti-tution

Y 10,000 Y Y

210 Notice to Receive Notifies the Receiver that it will receive funds forthe Sender’s account

Y 2,000 N Y

256 Advice ofNon-Payment of Cheques

Informs the Sender of one or more previouslysent 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 previ-ous payment settlement

Y 10,000 Y Y

290 Advice of Charges, Interest and Other Adjustments

Advises an account owner of charges, interest orother adjustments

Y 2,000 N N



MT MT Name Purpose Authen. Max. Length

MUG VDO

291 Request for Paymentof Charges, Interestand Other Expenses

Requests payment of charges, interest or other expenses

Y 2,000 N N

292 Request for Cancella-tion

Requests the Receiver to consider cancellation ofthe message identified in the request

Y 2,000 N N

295 Queries Requests information relating to a previousmessage or amendment to a previous message

Y 2,000 N N

296 Answers Responds to an MT 295 Queries message or anMT 292 Request for Cancellation or othermessage where no specific message type has beenprovided for a response

Y 2,000 N N

298 Proprietary Message Contains formats defined and agreed to betweenusers and for those messages not yet live

Y 10,000 N N

299 Free Format Message Contains information for which no other messagetype has been defined

Y 2,000 N N

Note: A Message User Group (MUG), for the purposes of this book, is a group of users who have volun-tarily agreed to support the specified message type and have registered with SWIFT to send orreceive the specified message type. These messages are indicated in the preceding table in thecolumn MUG.

Registration is free of charge. To register to use one or more message types, submit a registrationrequest (Register to a Message User Group) through www.swift.com. To withdraw from aMUG, 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 Implemen-tation team (SWHQBEBBCOS).

55 February 2007

Category 2 Message Types

Euro - Impact on Category Message Standards

See the SWIFTStandards General Information volume for full details of the Euro-Related Information (ERI) and the impacton SWIFTStandards FIN message types.



MT 200 Financial Institution Transfer for its Own Account

MT 200 ScopeThis 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 theSender has, in the same currency, with another financial institution.

MT 200 Format Specifications

MT 200 Financial Institution Transfer for its Own Account

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

M 32A Value Date, Currency Code, Amount 6!n3!a15d 2

O 53B Sender’s Correspondent [/1!a][/34x][35x]

3

O 56a Intermediary A or D 4

M 57a Account With Institution A, B or D 5

O 72 Sender to Receiver Information 6*35x 6

M = Mandatory O = Optional

MT 200 Network Validated RulesThere are no network validated rules for this message type.

MT 200 Usage RulesThe 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 fundsbetween two accounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its severalaccounts 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 finan-cial institution transfer or the MT 203 Multiple financial institution transfer must be used.

MT 200 Field Specifications

75 February 2007

MT 200

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.


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 maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the specifiedcurrency (Error code(s): C03,T40,T43).

3. Field 53B: Sender’s Correspondent

FORMAT

Option B [/1!a][/34x][35x]

(Party Identifier)(Location)



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 Senderand the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with theParty 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 [/1!a][/34x]4!a2!a2!c[3!c]

(Party Identifier)(BIC)

Option D [/1!a][/34x]4*35x

(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 5!n Austrian Bankleitzahl

AU 6!n Australian Bank State Branch (BSB) Code

BL 8!n German Bankleitzahl

CC 9!n Canadian Payments Association Payment Routing Number

ES 8..9n Spanish Domestic Interbanking Code

FW without 9 digit code Pay by Fedwire

GR 7!n HEBIC (Hellenic Bank Identification Code)

95 February 2007

MT 200

HK 3!n Bank Code of Hong Kong

IE 6!n Irish National Clearing Code (NSC)

IN 11!c Indian Financial System Code (IFSC)

IT 10!n Italian Domestic Identification Code

PL 8!n Polish National Clearing Code (KNR)

PT 8!n Portuguese National Clearing Code

RT Pay by Real Time Gross Settlement

SC 6!n UK Domestic Sort Code

ZA 6!n South African National Clearing Code

CODES

with option D:





CH 6!n CHIPS Universal Identifier

CP 4!n CHIPS Participant Identifier


FW 9!n Fedwire Routing Number











RU 9!n Russian Central Bank Identification Code


SW 3..5n Swiss Clearing Code (BC code)

SW 6!n Swiss Clearing Code (SIC code)



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 informationabout BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFTBICs, 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 onlyonce 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 thatthe 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 itis 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 aneed 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 accountnumber, 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 processingof the instruction(s) by the Receiver.

5. Field 57a: Account With Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x

(Party Identifier)(Name & Address)

115 February 2007

MT 200

PRESENCE

Mandatory

DEFINITION

This field identifies the financial institution to which the funds (owned by the Sender and originally placed with theReceiver) are to be transferred.

CODES


The following codes may be used preceded by a double slash ’//’:

with option A:



















CODES

with option D:

























135 February 2007

MT 200

USAGE RULES








6. Field 72: Sender to Receiver Information

FORMAT

6*35x (Narrative - Structured Format)

The following line formats must be used:

Line 1 /8c/[additional information] Lines 2-6 [//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 Instructions following are for the account with institution

INT Instructions following are for the intermediary

PHON Please advise account with institution by phone



PHONIBK Please advise intermediary by phone

REC Instructions following are for the Receiver

TELE Please advise the account with institution by the most efficient means of telecommunication

TELEIBK 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, itis 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 whichit 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 thelast information in this field.

It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in thisfield 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 thisfield 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 AccountWith Institution

Narrative

Value 24 May 2002 UBS, Zürich requests ABN Amro Bank, Amsterdam, to transfer euro 1,000,000 to its account at INGBank, Amsterdam.

The reference for this transaction is 23/200516DEV.

Information Flow

155 February 2007

MT 200

SWIFT Message

Explanation Format

Sender UBSWCHZH80A

Message type 200

Receiver ABNANL2A

Message text

Transaction reference number 20:23/200516DEV

Value date/currency code/amount 32A:020524EUR1000000,

Account with institution (1) 57A:INGBNL2A

End of message text/trailer



(1) The Sender’s 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 toits 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 Format

Sender BKAUATWW

175 February 2007

MT 200

Explanation Format

Message type 200

Receiver CHASUS33

Message text

Transaction reference number :20:39857579

Value date/currency code/amount :32A:020524USD1000000,

Sender’s correspondent (1) :53B:/34554-3049

Intermediary :56A:CITIUS33

Account with institution (2) :57A:CITIUS33MIA


(1) The Sender’s account which is to be debited at Chase Manhattan Bank, New York.

(2) The Sender’s account at the account with institution which is to be credited with the funds in the transfer.



MT 201 Multiple Financial Institution Transfer for its Own Account

MT 201 ScopeThis 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 accountsthat the Sender has, in the same currency, with other financial institutions.

MT 201 Format SpecificationsThe 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 totalamount to be transferred, the Sender’s 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. Itprovides details of each transaction between the Receiver and a financial institution to which the funds will be trans-ferred. Each sequence includes a TRN, the amount and currency code to be transferred, the identification of the finan-cial 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


M 19 Sum of Amounts 17d 1

M 30 Value Date 6!n 2

O 53B Sender’s Correspondent [/1!a][/34x][35x]

3


----->


M 32B Currency Code, Amount 3!a15d 6


M 57a Account With Institution A, B or D 8


-----|


195 February 2007

MT 201

MT 201 Network Validated RulesC1

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 (Errorcode(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 RulesWhere the account owner wishes to instruct its account servicing institution either to transfer funds between twoaccounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its several accounts atan account with institution, the MT 202 General Financial Institution Transfer or the MT 203 Multiple General Finan-cial 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 finan-cial 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.


The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the currency speci-fied in field 32B (Error code(s): C03,T40,T43).

2. Field 30: Value Date

FORMAT

6!n (Date)



PRESENCE

Mandatory

DEFINITION

This field specifies the value date for all transactions in the message.



3. Field 53B: Sender’s Correspondent

FORMAT

Option B [/1!a][/34x][35x]


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 transac-tions.

In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Senderand the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with theParty 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.


FORMAT





215 February 2007

MT 201

PRESENCE

Optional

DEFINITION

This field specifies additional information which applies to every transaction in the message.

CODES








TELEIBK Please advise the intermediary by the most efficient means of telecommunication


USAGE RULES




Narrative text that is not qualified by a code, must start with a double slash ’//’ on a new line, and should preferably be thelast information in this field.








FORMAT

16x

PRESENCE

Mandatory

DEFINITION

The Transaction Reference Number (TRN) specifies the reference assigned by the Sender to unambiguously identify the message.



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.





FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


235 February 2007

MT 201

PRESENCE

Optional

DEFINITION

This field specifies the party between the financial Receiver and the account with institution through which the transactionmust pass to reach the account with institution.

CODES



with option A:



















CODES

with option D:
























The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more informationabout BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFTBICs, Masters, Synonyms, Live destinations and Test & Training destinations.(Error code(s): C05).

255 February 2007

MT 201

USAGE RULES









FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the financial institution to which the funds (owned by the Sender and originally placed with theReceiver) are to be transferred.

CODES



with option A:



















CODES

with option D:











275 February 2007

MT 201















USAGE RULES











FORMAT





PRESENCE

Optional

DEFINITION

This field contains additional information which applies to the transaction specified.

CODES










USAGE RULES



295 February 2007

MT 201


Narrative text that is not qualified by a code, must start with a double slash ’//’ on a new line, and, should preferably be thelast information in this field.





MT 201 Examples

Narrative

Value 28 May 2002, UBS, Zürich requests ABN Amro Bank, Amsterdam, to transfer euro 61,000 to its accounts at the following financial institutions:

ING Bank, Amsterdam EUR 5000,

SNS Bank Nederland NV, Amsterdam EUR 7500,

ABN Amro Bank, Rotterdam EUR 12500,

Crédit Lyonnais, Paris EUR 6000,

Deutsche Bank AG, Frankfurt by telex throughING Bank, Amsterdam

EUR 30000,

Information Flow



SWIFT Message

Explanation Format

Sender UBSWCHZH80A

Message type 201

Receiver ABNANL2A

315 February 2007

MT 201

Explanation Format

Message text

Sum of amounts in the message :19:61000,

Value date :30:020528

Transaction reference number (1) (1) :20:1234/22

Currency code and amount :32B:EUR5000,

Account with institution :57A:INGBNL2A



Account with institution :57A:BBSPNL2A



Account with institution :57B:ROTTERDAM



Account with institution :57A:CRLYFRPP



Intermediary :56A:INGBNL2A

Account with institution :57A:DEUTDEFF

Sender to Receiver information :72:/TELE/


(1) There are 5 requests for transfer within the message



MT 202 General Financial Institution Transfer

MT 202 ScopeThis message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the financial institu-tion 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 betweenthese accounts. In addition it can be sent to a financial institution to debit an account of the Sender serviced by the Receiverand to credit an account, owned by the Sender at an institution specified in field 57a.


MT 202 General Financial Institution Transfer

Status Tag Field Name Content/Options No


M 21 Related Reference 16x 2

----->

O 13C Time Indication /8c/4!n1!x4!n 3

-----|


O 52a Ordering Institution A or D 5

O 53a Sender’s Correspondent A, B or D 6

O 54a Receiver’s Correspondent A, B or D 7


O 57a Account With Institution A, B or D 9

M 58a Beneficiary Institution A or D 10



335 February 2007

MT 202


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

MT 202 Usage RulesAll 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 trans-action. 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 itsseveral accounts at an institution specified in field 57a, field 58A must contain the number of the account to be creditedand 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 Senderand serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A the numberof the account to be credited and the name of the Sender.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION




2. Field 21: Related Reference

FORMAT

16x

PRESENCE

Mandatory



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 inthis field.



USAGE RULES

If the related message is an MT 103 Single Customer Credit Transfer, this field will contain the field 20 Sender’s Referenceof that MT 103.

In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary institu-tion, 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 The time by which the funding payment must be credited, with confirmation, to the CLS Bank’saccount at the central bank, expressed in Central European Time (CET).

RNCTIME The time at which a TARGET payment has been credited at the receiving central bank, expressed inCentral European Time (CET).

SNDTIME The time at which a TARGET payment has been debited at the sending central bank, expressed inCentral European Time (CET).

355 February 2007

MT 202


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 theminute component, ie, ’MM’, must be in the range of 00 through 59. Any ’HH’ or ’MM’ component outside of these rangechecks 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 UniversalTime - ISO 8601).

EXAMPLE

Assume a financial institution in London is sending a payment instruction on 5 January related to CLS in which it indicatesthat 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 inCET (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 completedas follows:

:13C:/CLSTIME/0915+0200

Offsets of local time zones against UTC are published in the green section of the BIC Directory.


FORMAT


PRESENCE

Mandatory

DEFINITION








5. Field 52a: Ordering Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the ordering institution when other than the Sender of the message.

CODES



with option A:













375 February 2007

MT 202



CODES

with option D:

























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 identifiedin 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: Sender’s Correspondent

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the account or branch of the Sender or another financial institution through which the Sender will reim-burse the Receiver.




USAGE RULES

When the Sender instructs the Receiver to transfer funds between two accounts owned by the Sender and serviced by theReceiver, 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 branchof the Receiver when specified in field 54a), then field 53a must be present.

395 February 2007

MT 202

When field 53a is present and contains a branch of the Sender, the need for a cover message is dependent on the currency ofthe 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 Sender’s 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 thecurrency 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 corre-spondent relationship between the Sender and the Receiver relative to that currency.

7. Field 54a: Receiver’s Correspondent

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the branch of the Receiver or another financial institution at which the funds will be made available tothe Receiver.




USAGE RULES

The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender and Receiver, inthe 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 anaccount of the Sender serviced by the Receiver’s 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 reim-bursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationshipbetween 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 Receiver’s branch must be preceded by field 53a; theReceiver 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 correspon-dent relationship between the Sender and the Receiver relative to that currency.


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the financial party between the Receiver and the account with institution through which the transactionmust pass to reach the account with institution.

CODES



with option A:









415 February 2007

MT 202









CODES

with option D:



























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 onlyonce and in the first of the fields 56a, 57a and 58a of the payment instruction.








FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


435 February 2007

MT 202

PRESENCE

Conditional (C1)

DEFINITION

This field identifies the financial institution, when other than the Receiver, which will pay or credit the beneficiary institu-tion.

CODES



with option A:



















CODES

with option D:

























455 February 2007

MT 202

USAGE RULES

When field 57a is not present, it means that the Receiver is also the account with institution.








10. Field 58a: Beneficiary Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient ofthe funds being transferred.

CODES



with option A:



















CODES

with option D:











475 February 2007

MT 202















USAGE RULES

When the Sender instructs the Receiver to either credit one of several accounts owned by the Sender at an institution speci-fied in field 57a, or transfer funds between two accounts owned by the Sender and serviced by the Receiver, option A mustbe 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.











FORMAT





PRESENCE

Optional

DEFINITION

This field specifies additional information for the Receiver.

CODES



BNF Information following is for the beneficiary

INS The instructing institution which instructed the Sender to execute the transaction



PHONBEN Please advise/contact beneficiary/claimant by phone




TELEBEN Please advise the beneficiary/claimant by the most efficient means of telecommunication


495 February 2007

MT 202


USAGE RULES









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.Janssen’s 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 MidlandBank, London.

Information Flow



Message A SWIFT MT 103 Single Customer CreditTransfer

SWIFT Message, MT 103

Explanation Format

Sender BKAUATWW

Message type 103

Receiver ABNANL2A

Message text

Sender’s reference :20:494934/DEV

Bank operation code :23B:CRED

Value date/currency code/amount :32A:980527GBP1285,40

515 February 2007

MT 202

Explanation Format

Currency/Instructed Amount :33B:GBP1285,40

Ordering customer :50K:FRANZ HOLZAPFEL GMBH VIENNA

Sender’s correspondent (1) :53A:MIDLGB22

Beneficiary customer :59:/125-00698 H.F. JANSSEN LEDEBOER-STRAAT 27 AMSTERDAM

Details of charges :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




Explanation Format

Sender BKAUATWW

Message type 202

Receiver MIDLGB22

Message Text

Transaction reference number :20:213804/887

Related reference (1) :21:494934/DEV

Value date/currency code/amount :32A:980527GBP1285,40

Account used for reimbursement :53B:/15158000

Beneficiary institution :58A:ABNANL2A


(1) The related reference is the Sender’s 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 by07.00 AM CET to CLS Bank.

BANKGB2L sends an MT 202 to their JPY nostro correspondent (BANKJPJT), indicating that the funds need to be cred-ited to CLS Bank by 07.00 AM CET.

Information Flow

535 February 2007

MT 202

SWIFT Message

In the MT 202 which BANKGB2L sends to its JPY correspondent BANKJPJT, it can indicate the time by whichBANKJPJT 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 quotedin 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 offsetin 13C to its own offset against UTC. Japan is UTC +0900, therefore BANKJPJT knows it has to process the instructionbefore 15.00 local time in Japan.

Offsets of local delta time zones against UTC are published in the green section of the BIC directory.



MT 203 Multiple General Financial Institution Transfer

MT 203 ScopeThis multiple message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the finan-cial 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 Sender’s own funds in favour of itself. This is the casewhen 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 anaccount owned by the Sender at an institution specified in field 57a.


The first sequence provides details of the transaction between the Sender and Receiver, ie, the value date and totalamount 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. Itprovides details of each transaction between the Receiver and a financial institution to which the funds will be trans-ferred. 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 willpass and any other information about the transaction, as necessary.

MT 203 Multiple General Financial Institution Transfer






O 54a Receiver’s Correspondent A, B or D 5


----->





555 February 2007

MT 203





-----|




C2


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 RulesAll 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 itsseveral accounts at an institution specified in field 57a, field 58A in the related sequence must contain the number ofthe 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 Senderand serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A, in thesequence 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 trans-action. Field 21 must refer to this transaction.





FORMAT

17d (Amount)

PRESENCE

Mandatory

DEFINITION

This field contains the sum of all amounts appearing in each occurrence of field 32B in the message.


The integer part of the Amount must contain at least one digit. A decimal comma is mandatory and is included in themaximum length. The number of digits following the comma must not exceed the maximum number allowed for thecurrency 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.




FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

575 February 2007

MT 203

DEFINITION

This field specifies the ordering institution when other than the Sender of the message.

CODES


The following codes may be used preceded by a double slash (’//’):

with option A:















CODES

with option D:

























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.





595 February 2007

MT 203

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION





USAGE RULES

When the Sender instructs the Receiver to transfer funds between two accounts owned by the Sender and serviced by theReceiver, 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 branchof 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 ofthe 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 Sender’s 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.


The use and interpretation of fields 53a and 54a is, in all cases, dictated by the currency of the transaction and the corre-spondent relationship between the Sender and Receiver relative to that currency.

5. Field 54a: Receiver’s Correspondent



FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the branch of the Receiver or another financial institution at which the funds will be made available tothe Receiver.




USAGE RULES


In those cases where field 54a contains a branch of the Receiver, and is not preceded by field 53a, or field 53a contains anaccount of the Sender serviced by the Receiver’s 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 reim-bursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationshipbetween 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 Receiver’s branch must be preceded by field 53a; theReceiver 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 correspon-dent relationship between the Sender and Receiver relative to that currency.


615 February 2007

MT 203

FORMAT





PRESENCE

Optional

DEFINITION


CODES
















USAGE RULES










FORMAT

16x

PRESENCE

Mandatory

DEFINITION

The Transaction Reference Number (TRN) specifies the reference assigned by the Sender to unambiguously identify the message.



USAGE RULES

A different TRN must be assigned to each transaction in the message.


FORMAT

16x

635 February 2007

MT 203

PRESENCE

Mandatory

DEFINITION

This field contains a reference to the related transaction.



USAGE RULES

If the related message is an MT 103 Single Customer Credit Transfer, this field will contain the field 20 Sender’s Referenceof that MT 103.

In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary institu-tion, 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 inthis field.


FORMAT


PRESENCE

Mandatory

DEFINITION

This field specifies the currency and amount to be transferred for the transaction in the sequence.





FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x




PRESENCE

Optional

DEFINITION

This field specifies the financial party between the Receiver and the account with institution through which the transactionmust pass to reach the account with institution.

CODES



with option A:

















655 February 2007

MT 203

CODES

with option D:



























USAGE RULES









FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Conditional (C4)

DEFINITION

This field specifies the financial institution, when other than the Receiver, which will pay or credit the beneficiary institu-tion.

CODES



with option A:



675 February 2007

MT 203















CODES

with option D:



























USAGE RULES









695 February 2007

MT 203


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient ofthe funds being transferred.

CODES



with option A:



















CODES

with option D:






















715 February 2007

MT 203




USAGE RULES

When the Sender instructs the Receiver to either credit one of several accounts owned by the Sender at an institution speci-fied in field 57a, or transfer funds between two accounts owned by the Sender and serviced by the Receiver, option A mustbe 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 trans-fer is requested, the Party Identifier be used to specify the account number of the beneficiary institution.









FORMAT







PRESENCE

Optional

DEFINITION

This field specifies additional information for the Receiver or other party specified. This information is relevant to thespecific transaction in the sequence.

CODES














USAGE RULES






735 February 2007

MT 203




MT 203 Examples

Narrative

Value 28 May 2002, UBS, Zürich requests ABN Amro Bank, Amsterdam, to transfer euro 5,000,000 as follows:

ING Bank NV, Amsterdamin favour of Morgan Guaranty Trust Co., New York

EUR 500,000

SNS Bank Nederland NV, Amsterdamin favour of Mellon Bank, London

EUR 1,500,000

Citibank, Amsterdamin favour of Citibank, New York

EUR 1,000,000

Dresdner Bank AG, Frankfurt EUR 2,000,000

Information Flow



SWIFT Message

Explanation Format

Sender UBSWCHZH80A

Message type 203

755 February 2007

MT 203

Explanation Format

Receiver ABNANL2A

Message text

Sum of amounts in the message :19:5000000,


Transaction reference number (1) (1) :20:2345

Related reference :21:789022


Account with institution :57A:INGBNL2A

Beneficiary institution :58A:MGTCUS33


Related reference :21:ABX2270


Account with institution :57A:BBSPNL2A

Beneficiary institution :58A:MELNGB2X


Related reference :21:CO 2750/26


Account with institution :57A:CITINL2X

Beneficiary institution :58A:CITIUS33


Related reference :21:DRESFF2344BKAUWW


Beneficiary institution :58A:DRESDEFF




(1) There are 4 transfer orders within the message

775 February 2007

MT 203

MT 204 Financial Markets Direct Debit Message

Note: The use of this message type requires Message User Group (MUG) registration.

MT 204 ScopeThis 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 creditthe corresponding amount in favour of the Sender of the message.


Sequence A Common Elements - Reimbursement Details, is a single occurrence sequence and contains default infor-mation 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


Sequence A Common Elements - Reimbursement Details





O 58a Beneficiary Institution A or D 5


-----> Repetitive Sequence B Transaction Details


O 21 Related Reference 16x 8

M 32B Transaction Amount 3!a15d 9

M 53a Debit Institution A, B or D 10


-----|







C2


C3

The repetitive sequence must not appear more than ten times (Error code(s): T10).

MT 204 Usage RulesThis 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 requestSWIFT to be activated within the FIN subapplication group which controls the use of this message.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION




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.

795 February 2007

MT 204


FORMAT

17d (Amount)

PRESENCE

Mandatory

DEFINITION

This field specifies the sum of the amounts appearing in each occurrence of field 32B.


The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the currency speci-fied 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 theReceiver in favour of the Sender of the message.




FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x




PRESENCE

Optional

DEFINITION

This field identifies the financial institution at which the Sender wishes to receive reimbursement from the Receiver.

CODES



with option A:

















CODES

with option D:


815 February 2007

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 onlyonce and in the first of the fields 57a and 58a of the payment instruction.





Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when thereis a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system codeor an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field identifies the beneficiary institution, which is always the Sender.

CODES



with option A:







835 February 2007

MT 204











CODES

with option D:



























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 onlyonce and in the first of the fields 57a and 58a of the payment instruction.







FORMAT





855 February 2007

MT 204

PRESENCE

Optional

DEFINITION


CODES




CUST The amount to be debited corresponds to a margin call on segregated customer (client) trades/account

CUSTMAR The amount to be debited corresponds to initial/original margin on customer trades (customeraccount margin)

CUSTVAR The amount to be debited corresponds to variation margin on customer trades (customeraccount variation)

HOUSE The amount to be debited corresponds to a margin call on house trades (proprietary funds)

HOUSEMAR The amount to be debited corresponds to initial/original margin on house trades (houseaccount margin)

HOUSEVAR The amount to be debited corresponds to variation margin on house trades (house account vari-ation)

METALS Metals call

MKTMAR The amount to be debited corresponds to initial/original margin on market-maker (specialist)trades/account (market-maker account margin)

MKTMKR The amount to be debited corresponds to a margin call on market-maker (specialist) trades/account

MKTVAR The amount to be debited corresponds to variation margin on market-maker (specialist)trades/account (market-maker account variation)

MMPLDG Market-maker pledge

OPTPREM Options premium


TENDER The amount to be debited corresponds to a payment in respect of a tender (delivery)

VARIATN General variation

XMGN Cross-margin account (covers positions hedged, offset or spread over two exchanges)



XMGNMAR Cross-margin account margin (for initial/original margin)

XMGNVAR Cross-margin account margin (for variation margin)


USAGE RULES







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.



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 individualamount(s), sent to the Sender.

875 February 2007

MT 204


FORMAT

16x

PRESENCE

Optional

DEFINITION

This field contains a reference attributed by the debit institution to the related transaction.



USAGE RULES

This reference would normally be quoted in any related MT 900 Confirmation of Debit or MT 950 Statement Message, sentto the debit institution.

9. Field 32B: Transaction Amount

FORMAT


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.




10. Field 53a: Debit Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]




Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the financial institution which is to be debited with the transaction amount.




USAGE RULES

Optional Party Identifier may be used to specify the account number to be debited.


Option D must only be used in exceptional circumstances, ie, when the debit institution cannot be identified by a BIC, andwhen there is a bilateral agreement between the Sender and Receiver permitting its use. Unless qualified by an accountnumber, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.


FORMAT





PRESENCE

Optional

DEFINITION

This field specifies additional information for the Receiver or another party specified. This information is relevant to thespecific transaction in the sequence.

895 February 2007

MT 204

CODES




CUST The amount to be debited corresponds to a margin call on segregated customer (client) trades/account

CUSTMAR The amount to be debited corresponds to initial/original margin on customer trades (customeraccount margin)

CUSTVAR The amount to be debited corresponds to variation margin on customer trades (customeraccount variation)

HOUSE The amount to be debited corresponds to a margin call on house trades (proprietary funds)

HOUSEMAR The amount to be debited corresponds to initial/original margin on house trades (houseaccount margin)

HOUSEVAR The amount to be debited corresponds to variation margin on house trades (house account vari-ation)

METALS Metals call

MKTMAR The amount to be debited corresponds to initial/original margin on market-maker (specialist)trades/account (market-maker account margin)

MKTMKR The amount to be debited corresponds to a margin call on market-maker (specialist) trades/account

MKTVAR The amount to be debited corresponds to variation margin on market-maker (specialist)trades/account (market-maker account variation)

MMPLDG Market-maker pledge

OPTPREM Options premium


TENDER The amount to be debited corresponds to a payment in respect of a tender (delivery)

VARIATN General variation

XMGN Cross-margin account (covers positions hedged, offset or spread over two exchanges)

XMGNMAR Cross-margin account margin (for initial/original margin)

XMGNVAR Cross-margin account margin (for variation margin)




USAGE RULES








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 andto credit its account 1234-ABC, with value date September 21st 1998.

Information Flow

915 February 2007

MT 204


Explanation Format

Sender XCMEUS4C

Message type 204

Receiver CNORUS44

Message text

Message reference number :20:XCME REF1

Sum of amounts :19:50000,


Beneficiary institution :58A:/1234-ABCXCMEUS4C

Transaction reference number :20:XCME REF2

Related reference :21:MANDATEREF1



Explanation Format

Transaction amount :32B:USD50000,

Debit institution :53A:MLNYUS33


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 Format

Sender CNORUS44

Message type 910

Receiver XCMEUS4C

Message text

Transaction reference number :20:MB REF A

Related reference :21:XCME REF1

Account identification :25:ACCOUNT ID OF XCME


Ordering institution :52A:XCMEUS4C


SWIFT Message, MT 900, Confirmation of Debit

Explanation Format

Sender CNORUS44

Message type 900

Receiver MLNYUS33

Message text

Transaction reference number :20:MB REF B


935 February 2007

MT 204

Explanation Format

Account identification :25:ACCOUNT ID OF MLNY


Ordering institution :52A:XCMEUS4C


Example 2 The Exchange does not want to use the account relationship with thecommon 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 of50,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 andto credit its account serviced by First National Bank of Chicago in Chicago with a value date September 21st, 1998.

Information Flow




Explanation Format

Sender XCMEUS4C

Message type 204

Receiver CNORUS44

Message text

Transaction reference number :20:XCME REF1

Sum of amounts :19:50000,


Account with institution :57A:FNBCUS44

Message reference number :20:XCME REF2


Transaction amount :32B:USD50000,

Debit institution :53A:MLNYUS33


955 February 2007

MT 204

MT 205 Financial Institution Transfer Execution

MT 205 ScopeThis 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




----->

O 13C Time Indication /8c/4!n1!x4!n 3

-----|


M 52a Ordering Institution A or D 5








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





FORMAT

16x

PRESENCE

Mandatory

DEFINITION





FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field contains a reference to the related transaction.



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)

975 February 2007

MT 205

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 The time by which the funding payment must be credited, with confirmation, to the CLS Bank’saccount at the central bank, expressed in Central European Time (CET).

RNCTIME The time at which a TARGET payment has been credited at the receiving central bank, expressed inCentral European Time (CET).

SNDTIME The time at which a TARGET payment has been debited at the sending central bank, expressed inCentral European Time (CET).


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 theminute component, ie, ’MM’, must be in the range of 00 through 59. Any ’HH’ or ’MM’ component outside of these rangechecks 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 UniversalTime - ISO 8601).

EXAMPLE

Assume a financial institution in London is sending a payment instruction on 5 January related to CLS in which it indicatesthat 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 inCET (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 completedas follows:



:13C:/CLSTIME/0915+0200

Offsets of local time zones against UTC are published in the green section of the Bic Directory.


FORMAT


PRESENCE

Mandatory

DEFINITION







FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field identifies the ordering institution from the initial message.

CODES



with option A:


995 February 2007

MT 205














CODES

with option D:

























USAGE RULES

If there was no ordering institution specified in the initial message, the Sender of that message will be the ordering institu-tion in this message.

This field must be forwarded to the beneficiary institution.





FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


1015 February 2007

MT 205

PRESENCE

Optional

DEFINITION





USAGE RULES

In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Senderand 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 field53a must be present.

A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Sender’s 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.


The use and interpretation of field 53a is, in all cases, dictated by the currency of the transaction and the correspondent rela-tionship between the Sender and Receiver relative to that currency.


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the financial party between the Receiver and the account with institution through which the this trans-action must pass to reach the account with institution.



CODES



with option A:

















CODES

with option D:





1035 February 2007

MT 205





















USAGE RULES











FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]


Option D [/1!a][/34x]4*35x


PRESENCE

Conditional (C1)

DEFINITION

This field specifies the financial institution, when other than the Receiver, which is to pay or credit the beneficiary institu-tion.

CODES



with option A:








1055 February 2007

MT 205










CODES

with option D:



























USAGE RULES










FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


1075 February 2007

MT 205

PRESENCE

Mandatory

DEFINITION

This field specifies the ultimate recipient of the funds being transferred.

CODES



with option A:

















CODES

with option D:



























1095 February 2007

MT 205

USAGE RULES





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.





FORMAT





PRESENCE

Optional

DEFINITION


CODES



BNF Information following is for the Beneficiary













USAGE RULES









MT 205 Examples

Narrative

Deutsche Bank, Frankfurt, receives the following MT 202 General Financial Institution Transfer from UBS, Zürich.

1115 February 2007

MT 205

Explanation Format

Sender UBSWCHZH80A

Message Type 202

Receiver DEUTDEFF

Message Text

Transaction Reference Number :20:203998988

Related Reference :21:394882

Value Date/Currency Code/Amount :32A:020528EUR1121,50

Account With Institution :57A:DEUTDEHH

Beneficiary Institution :58A:OSCBDEH1

End of Message Text/Trailer

Information Flow



As a result of this message, Deutsche Bank, Frankfurt, sends an MT 205 to Deutsche Bank, Hamburg:

SWIFT Message

Explanation Format

Sender DEUTDEFF

Message Type 205

Receiver DEUTDEHH

Message Text

Transaction reference number :20:3004GH3882

1135 February 2007

MT 205

Explanation Format

Related reference (1) :21:394882

Value date/currency code/amount :32A:020528EUR1121,50

Ordering institution (2) :52A:UBSWCHZH80A

Beneficiary Institution :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 willbecome the ordering institution.



MT 206 Cheque Truncation Message


MT 206 ScopeThis message is sent from the beneficiary’s financial institution, directly or through one or more other financial institutions,to the issuer’s financial institution to convey information about one or more truncated cheques, in the same currency. It isused 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.

MT 206 Format SpecificationsThe MT 206 consists of three types of sequences:

Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individualcheques 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 allcheques detailed in sequence B.

MT 206 Cheque Truncation Message


Mandatory Sequence A Common Elements

M 20 Sender’s Reference 16x 1

M 28E Message Index/Total 5n/4!c 2

M 23E Cheque Type 4!c[/30x] 3

O 17A Cheque Truncation Indicator 1!a 4

O 52a Safekeeper A, C or D 5

----->Mandatory Repetitive Sequence B Cheque Details

M 44A Transaction Reference Number 65x 6

O 21D Cheque Number 35x 7

O 21E Cheque Reference Number 35x 8

O 29a Code Line F or G 9

1155 February 2007

MT 206


M 32J Cheque Amount 15d 10

O 58a Issuer’s Financial Institution A, C or D 11

O 25 Issuer’s Account Number/Code 35x 12

O 26E Represented Cheque Entry 2n 13

O 30 Date of Issue/Encashment 6!n 14

O 39C Place of Issue/Encashment 4*35x 15

O 52a Safekeeper A, C or D 16


-----|

Mandatory Sequence C Settlement Information

O 32A Value Date, Currency Code and Sum of Settlement Amounts

6!n3!a15d 18

O 57a Account With Institution (for Settlement) A, C or D 19

O 58B Beneficiary Institution’s Account (for Settlement) [/1!a][/34x][35x]

20

O 19 Settlement Amount 17d 21



If field 23E contains TRAV, then either field 21D or field 29a must be present, but not both (Error code(s): E11).

C2



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 Issuer’s Financial Institutionfield 25 Issuer’s Account Number/Codefield 21D Cheque Number

If field 23E insequence A contains

GENC or OTHR, andif field 29a in sequence

B is ...

then field 21D insequence B is ...

then field 25 insequence B is ...

then field 58a insequence B is ...

Not present Mandatory Mandatory Mandatory

If field 29a is present, the following fields must not be present (Error code(s): E20):

field 58a Issuer’s Account Number/Codefield 21D Cheque Number

If field 23E insequence A containsGENC or ’OTHR’and if field 29a insequence B is ...

then field 21D insequence B is ...

then field 25 insequence B is ...

then field 58a insequence B is ...

Present 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 (Errorcode(s): D64).

If field 52a in sequence A is ... then field 52a in any occurrence of sequence Bis ...

Present Not allowed

Not present Optional

If field 52a in any occurrence of sequence B is ... then field 52a in sequence A is ...

Present Not allowed


1175 February 2007

MT 206

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 ... then field 32A in sequence C is ...

LAST Mandatory

MORE Not allowed

ONLY 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 ... then field 19 in Sequence C is ...

LAST Mandatory

MORE Mandatory

ONLY Not allowed

C6

When field 28E contains ONLY, the amount specified in field 32A must be equal to the sum of all occurrences of field32J 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 sequenceB (Error code(s): E24).

MT 206 Usage RulesThe MT 206 can only be sent and/or received by financial institutions which have registered with SWIFT to sendand/or receive the MT 206/MT 256. If a registered user receives an MT 206 without bilateral agreement with theSender, 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/beneficiary’s financial institu-tion and Receiver of the truncation message and where necessary, between the issuer’s financial institution and the issuer.




1. Field 20: Sender’s Reference

FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field specifies the reference assigned by the Sender to unambiguously identify the instruction.



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 This is the last message in a chain of messages.

MORE More messages are following; this is not the last message in the chain of messages.

ONLY This is the one and only message, ie, no chain of messages.

1195 February 2007

MT 206

USAGE RULES

It is recommended that messages be sent in sequence.

All messages belonging to the same sequence must have exactly the same sender’s reference in field 20.

When more than one message is needed to convey all information, this field chains different messages by specifying thesequence 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 General cheques.

OTHR Other type of cheque. This will be followed by a bilaterally agreed code to specify the type of cheque.

TRAV Travellers cheques.




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 The paper cheque is following.

Y 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 [/1!a][/34x]4!a2!a2!c[3!c]


Option C /34x (Party Identifier)Option D [/1!a][/34x]

4*35x(Party Identifier)(Name & Address)

1215 February 2007

MT 206

PRESENCE

Conditional (C3)

DEFINITION

This field identifies the party at which all truncated cheques, ie, the originals, are securely stored.

CODES



with option A:















CODES

with option C or D:

























USAGE RULES



Option D should only be used when the safekeeper has no BIC.

EXAMPLE

:52A:GEBABEBB

1235 February 2007

MT 206

6. Field 44A: Transaction Reference Number

FORMAT

Option A 65x

PRESENCE

Mandatory

DEFINITION

This number is generated by the beneficiary’s 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 issuer’s 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 beneficiary’s financial institution.



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 4*35z (Full Code Line)Option G 9*1!n/33z (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 chequewhich 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 #:

a b c d e f g h i j k l m n o p q r s t u v w x y z

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

0 1 2 3 4 5 6 7 8 9

. , - ( ) / = ’ + : ? ! " % & * < > ; {

{ @ _ #

@ #

Cr Lf Space

It is highly recommended to take great care when using the character string ’CrLf’, since these characters are used by thenetwork to indicate an end of field or subfield. Since option F only has 4 subfields, five ’CrLf’ in the code line would causea 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 thisfield can be used as follows:

1255 February 2007

MT 206

with option G:

:29G:1/xxxxxx2/yyyyyyyyyyy3/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).


The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the currency speci-fied in field 32A (Error code(s): C03,T40,T43).

EXAMPLE

:32J:10000,

11. Field 58a: Issuer’s Financial Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]




PRESENCE

Conditional (C2)

DEFINITION

This field identifies the issuer’s financial institution.



CODES



with option A:













PT 8!n Portugese National Clearing Code



CODES

with options C or D:






1275 February 2007

MT 206



















USAGE RULES



EXAMPLE

:58A:ABNANL2A



12. Field 25: Issuer’s 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

1295 February 2007

MT 206

DEFINITION

This field contains the date written on the cheque when it was prepared by the issuer.



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:MANCHESTERGREAT BRITAIN

16. Field 52a: Safekeeper

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option C /34x (Account)Option D [/1!a][/34x]




PRESENCE

Conditional (C3)

DEFINITION

This field identifies the party at which the truncated cheque, ie, the original, is securely stored.

CODES



with option A:















CODES

with option C or D:




1315 February 2007

MT 206




















USAGE RULES



Option D should only be used when the safekeeper has no BIC.

EXAMPLE

:52A:GEBABEBB




FORMAT





PRESENCE

Optional

DEFINITION


CODES


MANU Manual operation (automated truncation not possible)

OTHR This code is followed by a bilaterally agreed code or other bilaterally agreed structured information

REMI This code is followed by bilaterally agreed remittance information

STAL We think this cheque is stale dated but we still ask for payment

TRAN Transaction Type code (any sub-codes to be agreed upon bilaterally)

USAGE RULES






1335 February 2007

MT 206




EXAMPLE

:72:/STAL/

18. Field 32A: Value Date, Currency Code and Sum of Settlement Amounts

FORMAT


PRESENCE

Conditional (C4)

DEFINITION

This field contains the value date which is to be applied to the funds that must be debited from the Receiver’s account, or credited to the Sender’s account, or the account of another party as specified in the bilateral agreement (see also the check-list on value dates). This is followed by, first the (common) currency for all the truncated cheques, and then the sum of all settlement amounts.





USAGE RULES

If messages are chained, ie, field 28E does not contain ONLY, this field must contain the sum of all occurrences of field 19in the chained messages.

EXAMPLE

message 1: message 2: message 3:

:28E:1/MORE :28E:2/MORE :28E:3/LAST

... ... ...

:19:10000, :19:5000, :32A:990106USD18000,:19:3000,



or

message 1:

:28E:1/ONLY

...

:32A:990106USD12500

19. Field 57a: Account With Institution (for Settlement)

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]




PRESENCE

Optional

DEFINITION

This field identifies the account with institution at which the Sender wants to have the funds credited.

CODES



with option A:









1355 February 2007

MT 206








CODES



























USAGE RULES

This field may only be used where the settlement is not following the same route as the cheque truncation message.




EXAMPLE

:57A:MIDLGB2L

20. Field 58B: Beneficiary Institution’s Account (for Settlement)

FORMAT

Option B [/1!a][/34x][35x]


PRESENCE

Optional

DEFINITION

This field specifies the account number of the financial institution which is the ultimate recipient of the funds being trans-ferred.

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 institutionone of these accounts is to be used for reimbursementthere is no bilaterally agreed account.

1375 February 2007

MT 206

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.


The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the currency speci-fied in field 32A, if present (Error code(s): C03,T40,T43).

EXAMPLE

:28E:9/MORE...:32J:5300:32J:5000...:19:10300,

MT 206 MappingMapping of an MT 206 into a subsequent MT 206 (Receiver of first MT 206 becomes Sender of the second MT 206)



Mapping of an MT 206 into a subsequent MT 202. (The Receiver of the MT 206 has a direct account relationship with theaccount 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 theaccount with institution of the Sender in field 57a.)

1395 February 2007

MT 206

* If there is no direct account relationship between the party specified in field 57a of the MT 206 and the Receiver of theMT 206, then the Receiver of the related MT 202 becomes the common correspondent between the party specified in field57a 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 therelated 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 followingThomas Cook travellers cheques:

TRN Cheque Number Amount

Cheque 1 981201ABCD123456 GB11111111 GBP20,

Cheque 2 9812010EFGH111123 HB22222222 GBP50,

Cheque 3 9812010IJKL235693 EB33333333 GBP10,

Cheque 4 981201ZZZZ123456AA GB66666666 GBP20,

Cheque 5 981201XXXX258950 HB88888888 GBP50,

Cheque 6 981201YYYY569333 EB99999999 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.



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 Format

Sender SBZAZAJJ

1415 February 2007

MT 206

Explanation Format

Message type 206

Receiver COOKGB22

Message text

Sender’s reference :20:981201123456AA

Message index/total :28E:1/MORE

Cheque type :23E:TRAV

Safekeeper :52A:SBZAZAJJ

Transaction reference number :44A:981201ABCD123456

Cheque number :21D:GB11111111

Cheque amount :32J:20,

Date of issue/encashment :30:981201

Transaction reference number :44A:9812010EFGH111123

Cheque number :21D:HB22222222


Date of encashment :30:981201

Transaction reference number :44A:9812010IJKL235693

Cheque number :21D:EB33333333



Settlement amount :19:80,


SWIFT Message, MT 206 (2)

Explanation Format

Sender SBZAZAJJ

Message type 206



Explanation Format

Receiver COOKGB22

Message text

Sender’s reference :20:981201123456AA

Message index/total :28E:2/LAST

Cheque type :23E:TRAV

Safekeeper :52A:SBZAZAJJ

Transaction reference number :44A:981201ZZZZ123456AA

Cheque number :21D:GB66666666



Transaction reference number :44A:981201XXXX258950

Cheque number :21D:HB88888888



Transaction reference number :44A:981201YYYY569333

Cheque number :21D:EB99999999



Value date, currency code and sum of settlement amounts :32A:981207GBP160,

Account with institution :57A:NWBKGB2L

Beneficiary institution’s account :58B:/555-888-9

Settlement amount :19:80,


1435 February 2007

MT 206

Message B SWIFT MT 202 General Financial Institution Transfer

Information Flow


Explanation Format

Sender COOKGB22

Message type 202

Receiver MIDLGB22

Message text



Explanation Format

Transaction reference number :20:IPD/00001/PAIDS

Related reference :21:981201123456AA

Value date, currency code and amount :32A:981207GBP160,

Sender’s correspondent :53B:/123456

Account with institution :57A:NWBKGB2L

Beneficiary institution :58A:/555-888-9SBZAZAJJ


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 issuedon 011212 in Oostende in favour of CMB, reference 3855026.

Cheque 2: Stadtsparkasse in Dusseldorf (DUSSDEDD), EUR 500, cheque number 000721111 account 45678912 issued on011214 in Namur in favour of Sofitel Wepion, reference 3855027.

TRN Cheque Number Amount Issuer’s A/C

Cheque 1 3855026 0007206657588 EUR1000, 3869999

Cheque 2 3855027 0000721111 EUR500, 45678912

Handling of the cheques is centralised in Fortis Bank, Brussels which truncates these cheques and sends them that same dayto 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 Westdeutsche’s euro account held with Fortis Bank, Brussels will be debitedwith value date D+4.

Information Flow

1455 February 2007

MT 206


Explanation Format

Sender GEBABEBB

Message type 206

Receiver WELADEDD

Message text

Sender’s reference :20:291342/0071115

Message index/total :28E:1/ONLY



Explanation Format

Cheque type :23E:GENC

Cheque truncation indicator :17A:Y

Safekeeper :52A:GEBABEBB

Transaction reference number :44A:3855026

Cheque number :21D:0007206657588


Issuer’s financial institution :58A:WELADED1

Issuer’s Account Number/Code :25:3869999

Transaction reference number :44A:3855027

Cheque number :21D:000721111


Issuer’s financial institution :58A:DUSSDEDD

Issuer’s account number/code :25:45678912

Value date, currency code and total settlement amount :32A:020114EUR1500,


MT 206 ChecklistIt 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 thesetting 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. Topicsmay include:

Currency & amount

Specify minimum and maximum amounts per type of chequeSpecify currencies accepted per type of chequeSet out the procedure to follow when there is a discrepancy between the code line and another field, eg, the amountUnless otherwise agreed, cheque truncation messages are expressed in either the currency of the sending or the receiv-ing country. If financial institutions wish to accept third currencies this should be bilaterally agreed.

1475 February 2007

MT 206

Rules & regulations covering cheque truncation

Enumerate (inter)national laws and regulationsSpecify regulatory reporting requirementsSpecify 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 requirementsDefine stale dateList the criteria for cheque truncationAn 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 beneficiary’s financial institution must endorsethat the party that cashes the cheque is the legitimate beneficial partyBack of cheque - Since it is very difficult to automatically truncate this information, the truncation agreement shouldmake it the truncating party’s responsibility to ensure that the truncated cheques contain all legally required endorse-ments.Define the responsible parties at each stage of the whole process, eg, whether or not the beneficiary’s financial institu-tion can determine stale dated cheques. Also the agreement should establish the party responsible for verifying certainparts, 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, establishways of avoiding bad code lines such as:

using a specific control key to help manual keying when the code line is unreadableavoiding double truncation of a cheque through automatic checking at the point of capture.

Paper cheque

Specify which party must safekeep the originalAgree the period the original must be keptAgree whether or not the cheque (or a copy) must be sent to the drawee bank and if so whenAgree 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 amountDefine the charging period, eg, once a monthUnless 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 notpresent, the MT 206 can be used as a financial message to request to credit the account of the Sender automatically. Iffield 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.



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.

1495 February 2007

MT 206

MT 207 Request For Financial Institution Transfer


MT 207 ScopeThis message is used to move funds from the ordering financial institution’s 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 initi-ating institution has explicit authority to debit, eg, a subsidiary account.

It can be used to order the movement of funds:

between the ordering institution’s accounts, orin 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 andprocessed 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:



The parties mentioned in the chain are not necessarily different entities. The first column of the table below shows theparties that can be omitted in an MT 207. The second column specifies the party which assumes the role of the party in thefirst column, when it is not present:

1515 February 2007

MT 207

If the following party is missing... Its function is assumed by ...

Initiating institution Ordering institution

Account servicing institution Receiver

Intermediary Account with institution

Account with institution Receiver

MT 207 Format SpecificationsThe MT 207 consists of two sequences:

Sequence A General Information is a single occurrence mandatory sequence and contains information to be applied toall 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


Mandatory Sequence A General Information


O 21R Specified Reference of the Ordering Institution 16x 2

M 28D Message Index/Total 5n/5n 3

M 30 Requested Execution Date 6!n 4

O 51A Initiating Institution [/1!a][/34x]4!a2!a2!c[3!c]

5

M 52G Ordering Institution /34x4!a2!a2!c[3!c]

6

O 52a Account Servicing Institution A or C 7


----->Mandatory Repetitive Sequence B Transaction Details

M 21 Transaction Reference 16x 9

----->

O 23E Instruction Code 4!c[/30x] 10

-----|




M 32B Currency/Transaction Amount 3!a15d 11


O 57a Account With Institution A, C or D 13


-----|



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 ... then field 57a is ...

Present Mandatory


MT 207 Usage RulesIf 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 thesame sender’s 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.



1535 February 2007

MT 207

FORMAT

16x

PRESENCE

Mandatory

DEFINITION




USAGE RULES

The reference must be unique for each message (or chain of messages) and is part of the message identification and transac-tion 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 orordering institution, when the initiating institution is not present.



USAGE RULES

When this field is present, the ordering institution requests a single debit entry for the sum of the amounts of all transactionsin 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



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 executedhave 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.



USAGE RULES

This is the date on which the ordering institution’s account is to be debited.

5. Field 51A: Initiating Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


PRESENCE

Optional

1555 February 2007

MT 207

DEFINITION

This field identifies the institution which is authorised by the ordering institution/account servicing institution to order allthe transactions in the message.




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 /34x4!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 insequence(s) B.




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 [/1!a][/34x]4!a2!a2!c[3!c]


Option C /34x (Party Identifier)



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



with option A:






FW Without 9 digit code Pay by Fedwire









CODES

with option C:



1575 February 2007

MT 207





















USAGE RULES

The coded information contained in field 52a should be meaningful to the Receiver of the message.


If the account servicing institution cannot be identified by a BIC, option C should be used containing a 2!a clearing systemcode preceded by a double slash ’//’.




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 areturn, 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.


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 StandardsUsage 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 ofsequence B.

1595 February 2007

MT 207



USAGE RULES

In transaction specific queries, cancellations, etc., the Sender’s 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 This transaction contains a cash management instruction, requesting to sweep the account of the order-ing institution.

CMTO 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.

CMZB This transaction contains a cash management instruction, requesting to zero balance the account of the ordering institution.

CORT This transaction contains a payment that is made in settlement of a trade, eg, foreign exchange deal, securities transaction.

NETS This transaction contains a payment that should be settled via a net settlement system, if available.

OTHR Used for bilaterally agreed codes/information. The actual bilateral code/information needs to be speci-fied in Additional Information.

PHON 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

RTGS This transaction contains a payment that should be settled via a real time gross settlement system, if available.

URGP This transaction contains a time sensitive payment which should be executed in an expeditious manner.




Additional Information is only allowed when Instruction Code consists of one of the following codes: CMTO, PHON orOTHR (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 with CMTO

CMSW with CMZB

CMTO with CMZB

CORT with CMSW

CORT with CMTO

CORT with CMZB

NETS with RTGS

In each occurrence of Sequence B: when this field is repeated, the same code word must not be present more than once withthe exception of OTHR. The code word OTHR may be repeated (Error code(s): E46).

USAGE RULES

To facilitate the receiving bank’s 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

FORMAT


PRESENCE

Mandatory

DEFINITION

This field specifies the currency and amount of the subsequent transfer to be executed by the Receiver.

1615 February 2007

MT 207


Currency must be the same for all occurrences of this field (Error code(s): C02).




FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the financial institution between the Receiver and the account with institution, through which the trans-action must pass to reach the account with institution.

CODES



with option A:

















CODES

with option D:




















1635 February 2007

MT 207




USAGE RULES

The intermediary may be a branch or affiliate of the Receiver or the account with institution, or an entirely different finan-cial 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 andin 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 thatthe code //FW appears in the optional Party Identifier of field 56a, 57a or 58a.


Option D must only be used in exceptional circumstances: when the party cannot be identified by a BIC, when there is aneed 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.


Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considera-tions.


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]




PRESENCE

Conditional (C1)

DEFINITION

This field specifies the financial institution - when other than the Receiver - which services the account for the beneficiary institution.

CODES





with option A:















CODES

with options C and D:










1655 February 2007

MT 207














USAGE RULES











FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the beneficiary financial institution of the subsequent operation from the particular occurrence ofsequence B.

CODES



with option A:















1675 February 2007

MT 207

CODES

with option D:

























USAGE RULES



Party Identifier may contain the beneficiary financial institution’s account number.

If the message is used to request the transfer of funds between the ordering financial institution’s accounts, this field mustcontain the BIC of this institution.





MT 207 Examples

Narrative

The Canadian Imperial Bank of Commerce, Canada (CIBCCATT) owns a euro account (account number 123456) atDeutsche Bank, Frankfurt (DEUTDEFF).

The Canadian Imperial Bank of Commerce is a customer of Deutsche Bank, Toronto (DEUTCATT) and instructs this bankvia a proprietary link to ask Deutsche Bank, Frankfurt to make a euro payment to Banco Bilbao Vizcaya Argentaria,Madrid, via an RTGS system, using CIBCCATT’s EUR account at DEUTDEFF .

Information Flow

1695 February 2007

MT 207

SWIFT Message

Explanation Format

Sender DEUTCATT

Message type 207

Receiver DEUTDEFF

Message text - General Information

Sender’s Reference :20:ABCDEF

Message Index/Total :28D:1/1

Requested Execution Date :30:020110

Ordering Institution :52G:/123456CIBCCATT

Message text - Transaction Details 1

Transaction Reference :21:REFBOF123



Explanation Format

Instruction Code :23E:RTGS

Currency/Transaction Amount :32B:EUR500000,

Beneficiary Institution :58A:BBVAESMM


1715 February 2007

MT 207

MT 210 Notice to Receive

MT 210 ScopeThis 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 Sender’s account.


MT 210 Notice to Receive



O 25 Account Identification 35x 2


----->



O 50a Ordering Customer C, No letter option or F C or noletter option

6



-----|



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... then field 52a is ...

Present Not allowed



If field 50a is... then field 52a is ...

Not present Mandatory

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




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.

1735 February 2007

MT 210

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.




FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field contains the content of field 20 Transaction Reference Number, or other reference, eg, Common Reference, of therelated transaction.



EXAMPLE

:21:ref1234


FORMAT




PRESENCE

Mandatory

DEFINITION

This field specifies the currency and amount to be received.




6. Field 50a: Ordering Customer

FORMAT

Option C 4!a2!a2!c[3!c] (BEI)No letter option 4*35x (Name & Address)Option F 35x


With Option F, for Subfield 1 (Party Identifier) Line Format 1 or Line Format 2 must be used:

/34x (Account)or 4!a/30x (Code) (Identifier)

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 Alien RegistrationNumber

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’ and the Alien Registration Number .

CCPT Passport Number The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’ and the Passport Number.

1755 February 2007

MT 210

CUST Customer Identifica-tion Number

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’, the issuer of the number, a slash, ’/’ and the Customer Identification Number.

DRLC Driver’s License Number

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’, the issuing authority, a slash, ’/’ and the Driver’s License Number.

EMPL Employer Number The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’, the registration authority, a slash, ’/’ and the Employer Number .

IBEI International Busi-ness Entity Identifier

The code followed by a slash, ’/’ must be followed by the International Busi-ness Entity Identifier.

NIDN National IdentityNumber

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’ and the National Identity Number.

SOSE Social Security Number

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’ and the Social Security Number.

TXID Tax IdentificationNumber

The code followed by a slash, ’/’ must be followed by the ISO country code, aslash, ’/’ and the Tax Identification Number.

CODES

With option F - Subfield 2 ( Name & Address): each line when present must contain one of the following codes (Errorcode(s): T56).

1 Name of the ordering customer

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)).

2 Address Line 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).

3 Country and Town The number followed by a slash, ’/’ must be followed by the ISO countrycode, a slash ’/’ and Town (Town can be complemented by postal code (forexample zip), country subdivision (for example state, province, or county).

4 Date of Birth The number followed by a slash, ’/’ must be followed by the Date of Birth inthe YYYYMMDD format.

5 Place of Birth The number followed by a slash, ’/’ must be followed by the ISO countrycode, a slash ’/’ and the Place of Birth.

6 Customer Identifica-tion Number

The number followed by a slash, ’/’ must be followed by the ISO countrycode, a slash, ’/’, the issuer of the number, a slash, ’/’ and the Customer Identi-fication Number .

7 National IdentityNumber

The number followed by a slash, ’/’ must be followed by the ISO countrycode, a slash, ’/’ and the National Identity Number .

8 Additional Informa-tion

The number followed by a slash, ’/’ is followed by information completing the Identifier provided in field 50F, subfield 1 - line format 2




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 ofthe 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 2lines 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 providedunder Subfield 1 - Line Format 2.

EXAMPLE

Option F - Example 1

:50F:/123456781/SMITH JOHN2/299, PARK AVENUE3/US/NEW YORK, NY 10017


:50F:/BE300012163714111/PHILIPS MARK4/197208305/BE/BRUSSELS


:50F:DRLC/BE/BRUSSELS/NB09490421/DUPONT JACQUES2/HIGH STREET 6, APT 6C3/BE/BRUSSELS

1775 February 2007

MT 210


:50F:NIDN/DE/1212312343421/MANN GEORG6/DE/ABC BANK/1234578293


:50F:CUST/DE/ABC BANK/123456789/8-1234561/MANN GEORG2/LOW STREET 73/DE/FRANKFURT8/7890

This means that the customer identification number of Mann Georg assigned by ABC Bank is123456789/8-1234567890.


FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Conditional (C2)

DEFINITION

This field specifies the ordering party when it is a financial institution.

CODES



with option A:

















CODES

with option D:


















1795 February 2007

MT 210






USAGE RULES

When the Sender is also the ordering institution, it will be repeated in this field.





FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option D [/1!a][/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the financial institution from which the Receiver is to receive the funds.

CODES



with option A:


















CODES

with option D:













1815 February 2007

MT 210












USAGE RULES

This field is used when the intermediary institution is other than the ordering party.




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.



Information Flow


Explanation Format

Sender BEBEDEBB

Message type 210

Receiver CHASUS33

Message text

Transaction reference number :20:318393

1835 February 2007

MT 210

Explanation Format

Value Date :30:980222

Related reference (1) :21:BEBEBB0023CRESZZ

Currency code and amount :32B:USD230000,

Ordering institution :52A:CRESCHZZ

Intermediary (2) :56A:CITIUS33


(1) Field 21 of the incoming funds transfer. In this case, the reference contained in field 21 is a common reference from therelated 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.



MT 256 Advice of Non-Payment of Cheques


MT 256 ScopeThis message is sent by the Receiver of one or more MT 206s. It is used to inform the Sender of (a) previously sentMT 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.

MT 256 Format SpecificationsThe MT 256 consists of three types of sequences:

Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individualcheques 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 allcheques detailed in sequence B.

MT 256 Advice of Non-Payment of Cheques


Mandatory Sequence A Common Elements


O 21 Related Message Reference 16x 2

----->Mandatory Repetitive Sequence B Cheque Details

M 44A Transaction Reference Number 65x 3

O 21 Related Message Reference 16x 4

O 21D Cheque Number 35x 5

O 21E Cheque Reference Number 35x 6

M 23E Reason for Non-Payment/Dishonour 4!c[/30x] 7

M 32J Cheque Amount 15d 8

O 37J Interest Rate 12d 9

O 71G Interest Charges 3!a15d 10

1855 February 2007

MT 256


O 71F Sender’s Charges 3!a15d 11

O 71H Issuer’s Financial Institution Charges 3!a15d 12

-----|

Mandatory Sequence C Settlement Details

M 32A Value Date, Currency Code and Total Amount Claimed 6!n3!a15d 13

O 30 Original Value Date 6!n 14

O 19 Total Cheque Amount 17d 15

O 71J Sum of Interest Charges 3!a15d 16

O 71L Sum of Sender’s Charges 3!a15d 17

O 71K Sum of Issuer’s Financial Institution Charges 3!a15d 18

O 57a Account With Institution (for Settlement) A, C or D 19

O 58B Beneficiary Institution’s Account (for Settlement) [/1!a][/34x][35x]

20



If field 37J is present, then field 71G must also be present (Error code(s): E25).

If field 37J in sequence B is... then field 71G in sequence B is...

Present Mandatory




C2

The amount specified in field 71L in sequence C must be equal to the sum of all occurrences of field 71F in sequenceB (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 ofthese 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... then field 21 in sequence B is...

Present Not allowed

Not present Mandatory in all occurrences

If field 21 in sequence B is... then field 21 in sequence A is...

Present Not allowed

Not present Mandatory

C8

If field 71F is present in any occurrence of sequence B, then field 71L must be present in sequence C. Otherwise, field71L is not allowed (Error code(s): E29).

If field 71F in sequence B is... then field 71L in sequence C is...

Present in any occurrence Mandatory

Not present in any occurrence Not allowed

1875 February 2007

MT 256

C9

If field 71G is present in any occurrence of sequence B, then field 71J must be present in sequence C. Otherwise, field71J is not allowed (Error code(s): E30).

If field 71G in sequence B is... then field 71J in sequence C is...



C10

If field 71H is present in any occurrence of sequence B, then field 71K must be present in sequence C. Otherwise, field71K is not allowed (Error code(s): E31).

If field 71H in sequence B is... then field 71K in sequence C is...



C11

The amount specified in field 71K in sequence C must be equal to the sum of all occurrences of field 71H in sequenceB (Error code(s): E32).

MT 256 Usage RulesThe MT 256 can only be sent or received by financial institutions which have registered with SWIFT to send or receivethe MT 206/MT 256. If a registered user receives an MT 256 without bilateral agreement with the Sender, the Receivershould 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 Receiver’s account, the Receiver of the MT 256 must credit theaccount 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 field30 implies that the value date in field 32A is taken from the original MT 206.



FORMAT

16x



PRESENCE

Mandatory

DEFINITION




EXAMPLE

:20:oref1000

2. Field 21: Related Message Reference

FORMAT

16x

PRESENCE

Conditional (C7)

DEFINITION

This field contains the Sender’s reference of the previously received MT 206 Cheque Truncation Message, ie, field 20 of the original MT 206.



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 beneficiary’s financial institution,which identifies the transaction that this dishonoured cheque represents.

1895 February 2007

MT 256

EXAMPLE

:44A:abc12354

4. Field 21: Related Message Reference

FORMAT

16x

PRESENCE

Conditional (C7)

DEFINITION

This field contains the Sender’s reference of the previously received MT 206 Cheque Truncation Message in case thisMT 256 is informing of the non-payment of cheques in the same currency that were included in different MTs 256.



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 issuer’s financial institution.

USAGE RULES

This field must be the same as the cheque number specified in the original MT 206.

EXAMPLE

:21D:9987434



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 beneficiary’s 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 Amount exceeds the amount limit allowed for this account.

AMTL Amount exceeds the truncation limit as defined in the bilateral agreement (min. or max. amount).

CLOS Closed account.

COLN Error in code line.

DRAW Refer to drawer.

DUPL Duplicate cheque information.

1915 February 2007

MT 256

FRAU Fraudulent cheque.

FROZ (Legally) Frozen account.

FRWD Forward dated cheque.

INCH Cheque number invalid.

INSF Insufficient funds.

INSI Insufficient information.

INVA Account number invalid.

NELI Cheques not eligible for truncation.

NMAT Currency and account do not match.

OTHR Other followed by a bilaterally agreed code to specify a reason which is not covered by the above.

REVO Revocation.

STLD Stale cheque, ie, deposited too late relative to the issue date.

STOP Stop payment of a cheque.


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



DEFINITION

This field contains the amount specified on the dishonoured cheque.


The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength. The number of digits following the comma must not exceed the maximum number allowed for the currency speci-fied 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.


The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength (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.

1935 February 2007

MT 256




USAGE RULES

These interest charges are computed at a prevailing interest rate (field 37J) from the original value date (field 30) up to thedate when recovery of funds is expected to take place (field 32A).

EXAMPLE

:71G:USD3,

11. Field 71F: Sender’s 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 issuer’s financial institution, for the above specified reason.




EXAMPLE

:71F:USD3,

12. Field 71H: Issuer’s Financial Institution Charges

FORMAT

Option H 3!a15d (Currency) (Amount)



PRESENCE

Optional

DEFINITION

This field specifies the currency and the charges due to the issuer’s financial institution, for the above specified reason.




EXAMPLE

:71H:USD8,

13. Field 32A: Value Date, Currency Code and Total Amount Claimed

FORMAT


PRESENCE

Mandatory

DEFINITION

This field specifies the date when the recovery of funds is expected to take place, followed by the currency and the totalamount to be claimed.





EXAMPLE

:32A:961201USD1350,

14. Field 30: Original Value Date

FORMAT

6!n (Date)

1955 February 2007

MT 256

PRESENCE

Optional

DEFINITION

This field specifies the value date that appeared on the related MT 206.



USAGE RULES

As this message is sent after provisional credit has been given to the beneficiary, any consequential interests can also betaken 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.


The integer part of the Amount must contain at least one digit. A decimal comma is mandatory and is included in themaximum length. The number of decimal digits in field 19 must not exceed the maximum for its corresponding currency infield 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)



PRESENCE

Conditional (C9)

DEFINITION

This field specifies the currency and the sum of all occurrences of field 71G in sequence B.




EXAMPLE

:71J:USD50,

17. Field 71L: Sum of Sender’s 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.




EXAMPLE

:71L:USD234,

18. Field 71K: Sum of Issuer’s Financial Institution Charges

FORMAT

Option K 3!a15d (Currency) (Amount)

1975 February 2007

MT 256

PRESENCE

Conditional (C10)

DEFINITION

This field specifies the currency and the sum of all occurrences of field 71H in sequence B.




EXAMPLE

:71K:USD343,

19. Field 57a: Account With Institution (for Settlement)

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]




PRESENCE

Optional

DEFINITION

This field identifies the account with institution at which the Sender wants to have the funds (re)credited .

CODES



with option A:


















CODES
















1995 February 2007

MT 256










USAGE RULES

This field may only be used where the settlement does not follow the same route as the MT 256 (this message).





EXAMPLE

:57A:MIDLGB2L

20. Field 58B: Beneficiary Institution’s Account (for Settlement)

FORMAT

Option B [/1!a][/34x][35x]


PRESENCE

Optional



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 institutionone of these accounts is to be used for reimbursementthere is no bilaterally agreed account.

EXAMPLE

:58B:/123-45678

MT 256 MappingMapping of an MT 206 into a subsequent MT 256 (Receiver of the MT 206 becomes Sender of the MT 256).

2015 February 2007

MT 256

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).



TRN Cheque Number Amount Reason for dishonour

Cheque 1 9812010IJKL235693 EB33333333 GBP10, Stopped cheque

Cheque 2 981201ZZZZ123456AA GB66666666 GBP20, Invalid cheque number

Since Thomas Cook, London has already reimbursed Standard Bank of South Africa, it wants to have the funds recreditedto its account held at Midland Bank, London (account number 123456), back-valuing the amount with the value date usedon the original MT 206 (original value date 981207).

Information Flow


Explanation Format

Sender COOKGB22

Message Type 256

Receiver SBZAZAJJ

Message Text

2035 February 2007

MT 256

Explanation Format

Sender’s Reference :20:IPD/S0001/PAIDS

Related Message Reference :21:981201123456AA

Transaction Reference Number :44A:981201IJKL235693

Cheque Number :21D:EB33333333

Reason for Non-Payment/Dishonour :23E:STOP

Cheque Amount :32J:10,

Transaction Reference Number :44A:981201ZZZZ123456AA

Cheque Number :21D:GB66666666

Reason for Non-Payment/Dishonour :23E:INCH

Cheque Amount :32J:20,

Value Date, Currency Code and Total Amount Claimed :32A:981207GBP30,

Account With Institution :57A:MIDLGB22

Beneficiary Institution’s Account :58B:/123456


MT 256 ChecklistFor a checklist of topics that should be included in bilateral or multilateral agreements for processing truncated cheques, seeMT 206 Checklist.



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 fordetails concerning this message type.

2055 February 2007

MT 290

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.



MT 292 Request for Cancellation

Please refer to Category n - Common Group Messages, Chapter n92 Request for Cancellation for details concerning thismessage type.

2075 February 2007

MT 292

MT 295 Queries

Please refer to Category n - Common Group Messages, Chapter n95 Queries for details concerning this message type.



MT 296 Answers

Please refer to Category n - Common Group Messages, Chapter n96 Answers for details concerning this message type.

2095 February 2007

MT 296

MT 298 Proprietary Message

Please refer to Category n - Common Group Messages, Chapter n98 Proprietary Message for details concerning thismessage type.



MT 299 Free Format Message

Please refer to Category n - Common Group Messages, Chapter n99 Free Format Message for details concerning thismessage type.

2115 February 2007

MT 299

Glossary of Terms

In addition to the definitions which appear in Standards General Information, Glossary of Terms, the following terms applyto 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 byDeutsche 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 theNew 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 participant’s number, followed by a onedigit 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 theCHIPS 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 finan-cial 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 morefunds transfer transactions.

Funds Transfer Transaction The movement of funds directly between two parties, involving no intermediaries other than a payment or communica-tions 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.



Originator Initiator of the transfer instructions. Equivalent to the ordering institution (field 52a) in the MT 202.

Originator’s 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 thepayment mechanism used.

Settlement A transfer of funds to complete one or more prior transactions made, subject to final accounting.

2135 February 2007

Glossary of Terms

Table of Contents

....................... 2Copyright

....................... 3Introduction

.................... 3Summary of Changes

................... 3Added Message Types

................... 3Removed Message Types

................... 3Modified Message Types

.................... 4Category 2 Message Types

............... 6Euro - Impact on Category Message Standards

............. 7MT 200 Financial Institution Transfer for its Own Account

...................... 7MT 200 Scope

.................. 7MT 200 Format Specifications

.................. 7MT 200 Network Validated Rules

.................... 7MT 200 Usage Rules

................ 7MT 200 Field Specifications (updated)

............... 81. Field 20: Transaction Reference Number

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

................ 83. Field 53B: Sender’s Correspondent

................ 94. Field 56a: Intermediary (updated)

.............. 115. Field 57a: Account With Institution (updated)

............... 146. Field 72: Sender to Receiver Information

..................... 15MT 200 Examples

... 15Example 1 Financial Institution Transfer for its Own Account with an Account With Institution

...... 17Example 2 Financial Institution Transfer for its Own Account with an Intermediary

.......... 19MT 201 Multiple Financial Institution Transfer for its Own Account

...................... 19MT 201 Scope



.................... 20MT 201 Usage Rules


.................. 201. Field 19: Sum of Amounts

................... 202. Field 30: Value Date

................ 213. Field 53B: Sender’s Correspondent



................ 236. Field 32B: Currency Code, Amount




..................... 30MT 201 Examples

............... 33MT 202 General Financial Institution Transfer

...................... 33MT 202 Scope



.................... 34MT 202 Usage Rules



.................. 342. Field 21: Related Reference

.................. 353. Field 13C: Time Indication

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

................. 375. Field 52a: Ordering Institution

................ 396. Field 53a: Sender’s Correspondent

................ 407. Field 54a: Receiver’s Correspondent



.............. 4610. Field 58a: Beneficiary Institution (updated)


..................... 50MT 202 Examples

................ 50Example 1 MT 202 as a Cover Payment

i5 February 2007

Table Of Contents

............ 51Message A SWIFT MT 103 Single Customer CreditTransfer

................ 52Message B SWIFT MT 202 Cover Message

................. 53Example 2 MT 202 with Time Indication

............... 55MT 203 Multiple General Financial Institution Transfer

....................... 55MT 203 Scope

.................... 55MT 203 Format Specifications

................... 56MT 203 Network Validated Rules

...................... 56MT 203 Usage Rules

.................. 56MT 203 Field Specifications (updated)

................... 571. Field 19: Sum of Amounts

..................... 572. Field 30: Value Date

................... 573. Field 52a: Ordering Institution

.................. 594. Field 53a: Sender’s Correspondent

................. 605. Field 54a: Receiver’s Correspondent

................ 616. Field 72: Sender to Receiver Information

................ 637. Field 20: Transaction Reference Number

................... 638. Field 21: Related Reference

................. 649. Field 32B: Currency Code, Amount

.................. 6410. Field 56a: Intermediary (updated)

............... 6711. Field 57a: Account With Institution (updated)

............... 7012. Field 58a: Beneficiary Institution (updated)


...................... 74MT 203 Examples

................ 78MT 204 Financial Markets Direct Debit Message

....................... 78MT 204 Scope



...................... 79MT 204 Usage Rules

.................... 79MT 204 Field Specifications


................... 802. Field 19: Sum of Amounts

..................... 803. Field 30: Value Date

................. 804. Field 57a: Account With Institution

.................. 835. Field 58a: Beneficiary Institution




.................. 889. Field 32B: Transaction Amount

................... 8810. Field 53a: Debit Institution


...................... 91MT 204 Examples

........ 91Example 1 The Exchange and the Member have a Common Correspondent BankExample 2 The Exchange does not want to use the account relationship with the common correspondent and wants

............... 94the funds to be transferred to another institution

................ 96MT 205 Financial Institution Transfer Execution

....................... 96MT 205 Scope






................... 973. Field 13C: Time Indication

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


.................. 1016. Field 53a: Sender’s Correspondent



................ 1079. Field 58a: Beneficiary Institution (updated)


...................... 111MT 205 Examples

................... 115MT 206 Cheque Truncation Message

....................... 115MT 206 Scope

Message Reference Guide - Standards Release Guide - February 2007ii

Table Of Contents



...................... 118MT 206 Usage Rules


................... 1191. Field 20: Sender’s Reference

.................. 1192. Field 28E: Message Index/Total

.................... 1203. Field 23E: Cheque Type

................ 1214. Field 17A: Cheque Truncation Indicator

..................... 1215. Field 52a: Safekeeper

................ 1246. Field 44A: Transaction Reference Number

................... 1247. Field 21D: Cheque Number

................. 1248. Field 21E: Cheque Reference Number

.................. 1259. Field 29a: Code Line (updated)

................... 12610. Field 32J: Cheque Amount

................ 12611. Field 58a: Issuer’s Financial Institution

................ 12912. Field 25: Issuer’s Account Number/Code

................. 12913. Field 26E: Represented Cheque Entry

................. 12914. Field 30: Date of Issue/Encashment

................. 13015. Field 39C: Place of Issue/Encashment

.................... 13016. Field 52a: Safekeeper


......... 13418. Field 32A: Value Date, Currency Code and Sum of Settlement Amounts

.............. 13519. Field 57a: Account With Institution (for Settlement)

............ 13720. Field 58B: Beneficiary Institution’s Account (for Settlement)

................... 13821. Field 19: Settlement Amount

....................... 138MT 206 Mapping

...................... 140MT 206 Examples

....... 140Example 1 Travellers Cheques sent via an MT 206 with an Account With Institution

............... 145Example 2 General Cheques sent via an MT 206

...................... 147MT 206 Checklist

...................... 147Currency & amount

............... 148Rules & regulations covering cheque truncation

....................... 148Responsibility

....................... 148Paper cheque

.................. 148Supported types of truncated cheques

........................ 148Charges

........................ 148Settlement

....................... 149Administration

..................... 149Dates and Time frames

..................... 149Remittance Information

................ 150MT 207 Request For Financial Institution Transfer

....................... 150MT 207 Scope



...................... 153MT 207 Usage Rules



............ 1542. Field 21R: Specified Reference of the Ordering Institution

.................. 1543. Field 28D: Message Index / Total

................. 1554. Field 30: Requested Execution Date

.................. 1555. Field 51A: Initiating Institution

.................. 1566. Field 52G: Ordering Institution

................ 1567. Field 52a: Account Servicing Institution


.................. 1599. Field 21: Transaction Reference

................... 16010. Field 23E: Instruction Code

................ 16111. Field 32B: Currency/Transaction Amount



............... 16614. Field 58a: Beneficiary Institution (updated)

...................... 169MT 207 Examples

..................... 172MT 210 Notice to Receive

iii5 February 2007

Table Of Contents

....................... 172MT 210 Scope

................. 172MT 210 Format Specifications (updated)




.................. 1732. Field 25: Account Identification

..................... 1743. Field 30: Value Date


................. 1745. Field 32B: Currency Code, Amount

................ 1756. Field 50a: Ordering Customer (updated)



...................... 182MT 210 Examples

................. 185MT 256 Advice of Non-Payment of Cheques

....................... 185MT 256 Scope



...................... 188MT 256 Usage Rules



................. 1892. Field 21: Related Message Reference

................ 1893. Field 44A: Transaction Reference Number

................. 1904. Field 21: Related Message Reference

................... 1905. Field 21D: Cheque Number

................. 1916. Field 21E: Cheque Reference Number

............... 1917. Field 23E: Reason for Non-Payment/Dishonour

................... 1928. Field 32J: Cheque Amount

.................... 1939. Field 37J: Interest Rate

................... 19310. Field 71G: Interest Charges

................... 19411. Field 71F: Sender’s Charges

.............. 19412. Field 71H: Issuer’s Financial Institution Charges

.......... 19513. Field 32A: Value Date, Currency Code and Total Amount Claimed

.................. 19514. Field 30: Original Value Date

.................. 19615. Field 19: Total Cheque Amount

................. 19616. Field 71J: Sum of Interest Charges

................. 19717. Field 71L: Sum of Sender’s Charges

............. 19718. Field 71K: Sum of Issuer’s Financial Institution Charges

........... 19819. Field 57a: Account With Institution (for Settlement) (updated)

............ 20020. Field 58B: Beneficiary Institution’s Account (for Settlement)

....................... 201MT 256 Mapping

...................... 202MT 256 Examples

...................... 204MT 256 Checklist

.............. 205MT 290 Advice of Charges, Interest and Other Adjustments

........... 206MT 291 Request for Payment of Charges, Interest and Other Expenses

.................... 207MT 292 Request for Cancellation

....................... 208MT 295 Queries

....................... 209MT 296 Answers

..................... 210MT 298 Proprietary Message

.................... 211MT 299 Free Format Message

....................... 212Glossary of Terms

Message Reference Guide - Standards Release Guide - February 2007iv

Table Of Contents

swiftstandard

Documents