(SwiftStandards) Category 2 - Financial Insitution Transfers (MT200 - MT299)

SWIFTStandards
Category 2
Financial Institution Transfers
November 2003 Standards Release
Standards Release Guide 2003 - Final edition - February 2003
1
Legal Notices
IMPORTANT NOTE: You may install and use this publication only if you have entered into the relevant licence agreement
with SWIFT. Please refer to such licence agreement to determine what you may or may not do with it. Note however that in
the case of a Single User Licence, this publication must be installed on a standalone machine for access by one person at
any one time, and references to "organisation" in these notices are to the ordering customer (BIC 8). In the case of a Server
Licence, this publication can also be installed on a server for access within the organisation of the ordering customer (BIC
8), and references to "organisation" are then to all those SWIFT Users belonging to the same group as the ordering customer
(BIC8) for traffic aggregation purposes.
Copyright
Copyright S.W.I.F.T. SCRL ("SWIFT"), avenue Adle 1, B-1310 La Hulpe, Belgium, 2002. All rights reserved. No part
of this publication may be copied or reproduced, stored in a retrieval system, sold or transferred to any person, in whole or
in part, in any manner or form or on any media, without the prior written permission of SWIFT. The recipient is, however,
authorised to copy or reproduce this publication within its own organisation as may be reasonably necessary for the purpose
for which it is supplied. Any such copy or reproduction will include the following: acknowledgement of the source, refer-
ence and date of publication, and all notices set out on this page.
Confidentiality
This publication may contain proprietary and/or confidential information of SWIFT and/or its suppliers. The recipient
should not disclose this publication outside its organisation without the prior written permission of SWIFT.
Disclaimer
Although SWIFT has used reasonable efforts to ensure accuracy of its contents, SWIFT assumes no liability for any inad-
vertent error or omission that may appear in this publication. The information in this publication is the latest available at the
date of its production, and may change from time to time.
Trademarks and Patents
SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, Accord and SWIFT-derived product and service names - such as but not
limited to SWIFTNet and SWIFTAlliance - are trademarks of S.W.I.F.T. SCRL. SWIFT is the trading name of S.W.I.F.T.
SCRL. All other product or company names that may be mentioned in this publication are trademarks or registered trade-
marks of their respective owners. Patent pending: SWIFTNet - TrustAct - e-paymentsPlus.
February 2003 edition
Standards Release Guide 2003 - Final edition - February 2003 2
SWIFTStandards - Category 2 Legal Notices
Overview
Added Message Types
Removed Message Types
Modified Message Types
Added Message Types
None
Removed Message Types
None
Modified Message Types
MT200
MT201
MT202
MT203
MT204
MT205
MT206
MT207
MT210
MT256
3 Standards Release Guide 2003 - Final edition - February 2003
Overview SWIFTStandards - Category 2
MT 200 Financial Institution Transfer for its Own Account
MT 200 Scope
This message type is sent by an account owner to one of its account servicing institutions.
It is used to request the movement of funds from an account that the Receiver services for the Sender to an account that the
Sender has, in the same currency, with another financial institution.
MT 200 Format Specifications
MT 200 Financial Institution Transfer for its Own Account
Status 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 Senders 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 Rules
There are no network validated rules for this message type.
MT 200 Usage Rules
The beneficiary of this transfer is always the Sender.
The Receiver and the account with institution are normally in the same country.
In those cases where the account owner wishes to instruct its account servicing institution either to transfer funds
between two accounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its several
accounts at an account with institution, the MT 202 General Financial Institution Transfer or the MT 203 Multiple
Financial Institution Transfer must be used.
In those cases where the sender wants the account servicing institution to do a book transfer the MT 202 General finan-
cial institution transfer or the MT 203 Multiple financial institution transfer must be used.
MT 200 Field Specifications
SWIFTStandards - Category 2 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 maximum
length. The number of digits following the comma must not exceed the maximum number allowed for the specified
currency (Error code(s): C03, T40, T43).
3. Field 53B: Senders Correspondent
FORMAT
Option B [/1!a][/34x]
[35x]
(Party Identifier)
(Location)
MT 200 SWIFTStandards - Category 2
PRESENCE
Optional
DEFINITION
This field specifies the account of the Sender which is to be debited.
USAGE RULES
In those cases where there are multiple direct account relationships, in the currency of the transaction, between the Sender
and the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with the
Party Identifier only.
When there is a single direct account relationship, in the currency of the transaction, between the Sender and the Receiver,
and this is the account to be used for reimbursement, field 53B must not be present.
4. Field 56a: Intermediary
FORMAT
Option A [/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)
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
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, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).
USAGE RULES
When one of the codes //FW (with or without the 9-digit number), //AU, //CP, //IN or //RT is used, it should appear only
once and in the first of the fields 56a and 57a of the payment instruction.
When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire, US banks require that
the code //FW appears in the optional Party Identifier.
When it is necessary that an incoming SWIFT payment be made to the party in this field via real-time gross settlement
(RTGS), the code //RT should appear in the optional Party Identifier.
The code //RT is binding for the Receiver. If it is used with option A, it must not be followed by any other information. If it
is used with option D, it may be followed by another domestic clearing code.
Option A must be used whenever possible.
Option D must only be used in exceptional circumstances, ie, when the party cannot be identified by a BIC and when there
is a bilateral agreement between the Sender and the Receiver permitting its use. Unless qualified by a clearing system code
or an account number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.
5. Field 57a: Account With Institution
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field identifies the financial institution to which the funds (owned by the Sender and originally placed with the
Receiver) are to be transferred.
CODES
The following codes may be used preceded by a double slash //:
with option A:
CODES
with option D:
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, it
is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.
USAGE RULES
Field 72 must never be used for information for which another field is intended.
Each item of information contained in this field must be preceded by a code which specifically indicates the party for which
it is intended.
Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be
continued on the next lines, is preceded by a double slash //.
Narrative text that is not qualified by a code, must start with a double slash // on a new line, and should preferably be the
last information in this field.
It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this
field are in effect, the code must conform to the structure of this field.
Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this
field will normally require manual intervention.
This field may contain ERI to transport dual currencies, as explained in the chapter Euro - Impact on Category 2 Message
Standards.
In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to
transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate,
format 12d, and terminated with another slash.
MT 201 Multiple Financial Institution Transfer for its Own
Account
MT 201 Scope
This multiple message type is sent by an account owner to one of its account servicing institutions.
It is used to request the movement of funds from an account that the Receiver services for the Sender to several accounts
that the Sender has, in the same currency, with other financial institutions.
The MT 201 consists of two types of sequences:
The first sequence provides details of the transaction between the Sender and Receiver, ie, the value date and total
amount to be transferred, the Senders correspondent and any other information about this transaction, as necessary.
The second sequence, which must appear at least twice and, in order to expedite processing, not more than ten times. It
provides details of each transaction between the Receiver and a financial institution to which the funds will be 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 Senders Correspondent [/1!a][/34x]
[35x]
3
4
----->
5
M 32B Currency Code, Amount 3!a15d
6
7
M 57a Account With Institution A, B or D
8
9
-----|
C1
The amount in field 19 must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01).
C2
The currency code in the amount field 32B must be the same for all occurrences of this field in the message (Error
code(s): C02).
C3
The repetitive sequence must appear at least twice, but not more than ten times (Error code(s): T11, T10).
MT 201 Usage Rules
Where the account owner wishes to instruct its account servicing institution either to transfer funds between two
accounts serviced by the Receiver, or to debit its account with the Receiver and to credit one of its several accounts at
an account with institution, the MT 202 General Financial Institution Transfer or the MT 203 Multiple General 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.
length. 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: Senders Correspondent
FORMAT
[35x]
(Party Identifier)
(Location)
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.
and the Receiver, and one of these accounts is to be used, the account to be debited must be indicated in this field with the
Party Identifier only.
and this is the account to be used for reimbursement, field 53B must not be present.
FORMAT
or

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
it is intended.
Narrative text that is not qualified by a code, must start with a double slash // on a new line, and should preferably be the
Standards.
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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the party between the Receiver and the account with institution through which the transaction must pass.
CODES
with option A:
CODES
with option D:
USAGE RULES
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field specifies the financial institution to which the funds (owned by the Sender and originally placed with the
Receiver) are to be transferred.
CODES
with option A:
CODES
with option D:
USAGE RULES
FORMAT
or

PRESENCE
Optional
DEFINITION
This field contains additional information which applies to the transaction specified.
CODES
USAGE RULES
it is intended.
Narrative text that is not qualified by a code, must start with a double slash // on a new line, and, should preferably be the
Standards.
MT 202 General Financial Institution Transfer
MT 202 Scope
This message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the financial 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 between
these accounts. In addition it can be sent to a financial institution to debit an account of the Sender serviced by the Receiver
and to credit an account, owned by the Sender at an institution specified in field 57a.
MT 202 General Financial Institution Transfer
Status Tag Field Name Content/Options No
1
M 21 Related Reference 16x
2
----->
O 13C Time Indication /8c/4!n1!x4!n
3
-----|
4
O 52a Ordering Institution A or D
5
O 53a Senders Correspondent A, B or D
6
O 54a Receivers Correspondent A, B or D
7
8
O 57a Account With Institution A, B or D
9
M 58a Beneficiary Institution A or D
10
11
C1
If field 56a is present, then field 57a must also be present (Error code(s): C81).
MT 202 Usage Rules
All parties to the transaction must be financial institutions.
The transfer of funds between the ordering institution and the beneficiary institution is always related to another 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 its
several accounts at an institution specified in field 57a, field 58A must contain the number of the account to be credited
and the name of the Sender.
If the Sender wishes to instruct the Receiver that funds are to be moved between two accounts owned by the Sender
and serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A the number
of the account to be credited and the name of the Sender.
FORMAT
16x
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 in
this field.
USAGE RULES
If the related message is an MT 103 Single Customer Credit Transfer, this field will contain the field 20 Senders Reference
of that MT 103.
In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary 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 Banks
account 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 in
Central European Time (CET).
SNDTIME The time at which a TARGET payment has been debited at the sending central bank, expressed in
Time indication must be a valid time expressed as HHMM (Error code(s): T38).
Sign is either "+" or "-" (Error code(s): T15).
Time offset is expressed as HHMM, where the hour component, ie, HH, must be in the range of 00 through 13, and the
minute component, ie, MM, must be in the range of 00 through 59. Any HH or MM component outside of these range
checks will be disallowed (Error code(s): T16).
USAGE RULES
The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal
Time - ISO 8601).
FORMAT
PRESENCE
Mandatory
DEFINITION
5. Field 52a: Ordering Institution
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the ordering institution when other than the Sender of the message.
CODES
with option A:
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 identified
in this field in any subsequent messages as the ordering institution.
This field must be forwarded to the beneficiary institution.
The coded information contained in field 52a must be meaningful to the Receiver of the message.
Option A is the preferred option.
Option D should only be used when the ordering financial institution has no BIC.
6. Field 53a: Senders Correspondent
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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 the
Receiver, this field must be used with option B to identify the account to be debited.
If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver (or branch
of the Receiver when specified in field 54a), then field 53a must be present.
When field 53a is present and contains a branch of the Sender, the need for a cover message is dependent on the currency of
the transaction, the relationship between the Sender and the Receiver and the contents of field 54a, if present.
A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Senders
correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of the Receiver.
In this case, the Receiver will be paid by its branch in field 53a.
In all other cases, when field 53a is present, a cover message, ie, MT 202/203 or equivalent non-SWIFT, must be sent to the
financial institution identified in field 53a.
When field 53B is used to specify a branch city name, it must always be a branch of the Sender.
The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and Receiver, in the
currency of the transfer, will be used.
The use and interpretation of fields 53a and 54a is, in all cases, dictated by the currency of the transaction and the corre-
spondent relationship between the Sender and the Receiver relative to that currency.
7. Field 54a: Receivers Correspondent
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to
the Receiver.
USAGE RULES
The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender and Receiver, in
the currency of the transfer, will be used.
In those cases where field 54a contains a branch of the Receiver, and is not preceded by field 53a, or field 53a contains an
account of the Sender serviced by the Receivers branch, the Receiver will claim reimbursement from its branch.
If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender, the Receiver will claim reim-
bursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationship
between the Sender and the Receiver.
In all other cases where field 54a contains a branch of the Receiver, the Receiver will be paid by its branch in field 54a.
A branch of the Sender must not appear in field 54a.
If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver,
field 54a must not be present.
Field 54a containing the name of a financial institution other than the Receivers branch must be preceded by field 53a; the
Receiver will be paid by the financial institution in field 54a.
The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspon-
dent relationship between the Sender and the Receiver relative to that currency.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
CODES
with option A:
CODES
with option D:
USAGE RULES
once and in the first of the fields 56a, 57a and 58a of the payment instruction.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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:
USAGE RULES
10. Field 58a: Beneficiary Institution
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient of
the funds being transferred.
CODES
with option A:
CODES
with option D:
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 must
be used to specify the account to be credited and the name of the Sender.
It is strongly recommended that when clearing payments take precedence over book transfer and book transfer is requested,
Party Identifier be used to specify the account of the beneficiary.
FORMAT
or

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
USAGE RULES
it is intended.
Standards.
MT 203 Multiple General Financial Institution Transfer
MT 203 Scope
This multiple message is sent by or on behalf of the ordering institution directly, or through correspondent(s), to the 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 Senders own funds in favour of itself. This is the case
when the Receiver services multiple accounts for the Sender and the funds are to be transferred between these accounts. In
addition, it can be sent to a financial institution to debit an account of the Sender serviced by the Receiver and to credit an
account owned by the Sender at an institution specified in field 57a.
The first sequence provides details of the transaction between the Sender and Receiver, ie, the value date and total
amount to be transferred, as well as any other information about this transaction, as necessary.
The second sequence must appear at least twice and, in order to expedite processing, not more than ten times. It
provides details of each transaction between the Receiver and a financial institution to which the funds will be 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 will
pass and any other information about the transaction, as necessary.
MT 203 Multiple General Financial Institution Transfer
1
M 30 Value Date 6!n
2
3
4
O 54a Receivers Correspondent A, B or D
5
6
----->
7
8
9
10
11
12
13
-----|
C1
C2
code(s): C02).
C3
The repetitive sequence must appear at least twice, but not more than ten times (Error code(s): T11, T10).
C4
If field 56a is present in a transaction, then field 57a must also be present (Error code(s): C81).
MT 203 Usage Rules
All parties to the transactions must be financial institutions.
If the Sender wishes to instruct the Receiver to debit its account serviced by the Receiver and to credit one of its
several accounts at an institution specified in field 57a, field 58A in the related sequence must contain the number of
the account to be credited and the name of the Sender.
If the Sender wishes to instruct the Receiver that funds are to be moved between two accounts owned by the Sender
and serviced by the Receiver, field 53B must specify the number of the account to be debited and field 58A, in the
sequence relating to this order, must specify the number of the account to be credited and the name of the Sender.
Each transfer of funds between the ordering institution and a beneficiary institution is always related to another 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 the
maximum length. The number of digits following the comma must not exceed the maximum number allowed for the
currency specified in field 32B (Error code(s): C03, T40, T43).
FORMAT
6!n (Date)
PRESENCE
Mandatory
DEFINITION
This field specifies the value date for all transactions in the message.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
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.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
burse the Receiver.
The BIC must not be a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05)
USAGE RULES
When the Sender instructs the Receiver to transfer funds between two accounts owned by the Sender and serviced by the
Receiver, this field must be used with option B to identify the account to be debited.
If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver (or branch
of the Receiver when specified in field 54a), then field 53a must be present.
When field 53a is present and contains a branch of the Sender, the need for a cover message is dependent on the currency of
the transaction, the relationship between the Sender and the Receiver and the contents of field 54a, if present.
Correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of the Receiver.
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: Receivers Correspondent
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to
the Receiver.
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 an
account of the Sender serviced by the Receivers branch, the Receiver will claim reimbursement from its branch.
If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender, the Receiver will claim reim-
bursement from its branch or will be paid by its branch, depending on the currency of the transfer and the relationship
between the Sender and the Receiver.
In all other cases where field 54a contains a branch of the Receiver, the Receiver will be paid by its branch in field 54a.
A branch of the Sender must not appear in field 54a.
If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver,
field 54a must not be present.
Field 54a containing the name of a financial institution other than the Receivers branch must be preceded by field 53a; the
Receiver will be paid by the financial institution in field 54a.
The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspon-
dent relationship between the Sender and Receiver relative to that currency.
FORMAT
or

PRESENCE
Optional
DEFINITION
CODES
USAGE RULES
it is intended.
Standards.
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
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 Senders Reference
of that MT 103.
In all other cases, this field will contain a reference to the related transaction which is meaningful to the beneficiary 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 in
this field.
FORMAT
PRESENCE
Mandatory
DEFINITION
This field specifies the currency and amount to be transferred for the transaction in the sequence.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
CODES
with option A:
CODES
with option D:
USAGE RULES
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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:
CODES
with option D:
USAGE RULES
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field specifies the financial institution which has been designated by the ordering institution as the ultimate recipient of
the funds being transferred.
CODES
with option A:
CODES
with option D:
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 must
be used in the related sequence to specify the account to be credited and the name of the Sender.
It is strongly recommended that in those cases where clearing payments take precedence over book transfer and book trans-
fer is requested, the Party Identifier be used to specify the account number of the beneficiary institution.
FORMAT
or

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver or other party specified. This information is relevant to the
specific transaction in the sequence.
CODES
USAGE RULES
it is intended.
Standards.
MT 204 Financial Markets Direct Debit Message
Note: The use of this message type requires Message User Group (MUG) registration.
MT 204 Scope
This message is sent by an exchange or clearing house, or another financial institution to a SWIFT member or submember,
to instruct the Receiver of the message to debit the account(s) of a third party specified in the message and to pay or credit
the corresponding amount in favour of the Sender of the message.
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
1
2
M 30 Value Date 6!n
3
4
O 58a Beneficiary Institution A or D
5
6
-----> Repetitive Sequence B Transaction Details
7
O 21 Related Reference 16x
8
M 32B Transaction Amount 3!a15d
9
M 53a Debit Institution A, B or D
10
11
-----|
C1
C2
code(s): C02).
C3
The repetitive sequence must not appear more than ten times (Error code(s): T10).
MT 204 Usage Rules
This message requires the implementation of special procedures, its use is governed by bilateral agreements between
counterparties. In order to be able to send or receive this message, the interested customers need to formally request
SWIFT to be activated within the FIN subapplication group which controls the use of this message.
FORMAT
16x
PRESENCE
Mandatory
DEFINITION
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.
FORMAT
17d (Amount)
PRESENCE
Mandatory
DEFINITION
This field specifies the sum of the amounts appearing in each occurrence of field 32B.
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 the
Receiver in favour of the Sender of the message.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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:
USAGE RULES
When one of the codes //FW (with or without the 9-digit number), //AU, //RT, //IN or //CP is used, it should appear only
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field identifies the beneficiary institution, which is always the Sender.
CODES
with option A:
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 only
FORMAT
or

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 (customer
account margin)
CUSTVAR The amount to be debited corresponds to variation margin on customer trades (customer account
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 (house account
margin)
HOUSEVAR The amount to be debited corresponds to variation margin on house trades (house account varia-
tion)
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
it is intended.
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 individual
amount(s), sent to the Sender.
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, sent
to 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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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, and
when there is a bilateral agreement between the Sender and Receiver permitting its use. Unless qualified by an account
number, the use of option D may prevent the automated processing of the instruction(s) by the Receiver.
FORMAT
or

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver or another party specified. This information is relevant to the
specific transaction in the sequence.
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 (customer
account margin)
CUSTVAR The amount to be debited corresponds to variation margin on customer trades (customer account
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 (house account
margin)
HOUSEVAR The amount to be debited corresponds to variation margin on house trades (house account varia-
tion)
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
it is intended.
Standards.
MT 205 Financial Institution Transfer Execution
MT 205 Scope
This message is sent by the Receiver of a category 2 transfer message, ie, MT 200, 201, 202, 203 or 205, directly or through
correspondent(s), to another financial institution located in the same country as the Sender.
It is used to further transmit a funds transfer instruction domestically.
MT 205 Financial Institution Transfer Execution
1
2
----->
O 13C Time Indication /8c/4!n1!x4!n
3
-----|
4
M 52a Ordering Institution A or D
5
6
7
8
9
10
C1
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)
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 Banks
account 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 in
SNDTIME The time at which a TARGET payment has been debited at the sending central bank, expressed in
Time indication must be a valid time expressed as HHMM (Error code(s): T38).
Sign is either "+" or "-" (Error code(s): T15).
Time offset is expressed as HHMM, where the hour component, ie, HH, must be in the range of 00 through 13, and the
minute component, ie, MM, must be in the range of 00 through 59. Any HH or MM component outside of these range
checks will be disallowed (Error code(s): T16).
USAGE RULES
The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal
Time - ISO 8601).
FORMAT
PRESENCE
Mandatory
DEFINITION
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field identifies the ordering institution from the initial message.
CODES
with option A:
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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
burse the Receiver.
USAGE RULES
and the Receiver, and one of these accounts is to be used for reimbursement, the account to be credited or debited must be
indicated in field 53a, using option B with the account number line only.
If there is no direct account relationship, in the currency of the transaction, between the Sender and the Receiver, then field
53a must be present.
Correspondent and a branch of the Receiver, and the Sender intends to send a cover message to the branch of 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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the party between the Receiver and the account with institution through which this transaction must
pass.
CODES
with option A:
CODES
with option D:
USAGE RULES
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
[35x]
(Party Identifier)
(Location)
4*35x
(Party Identifier)
(Name & Address)
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:
CODES
with option D:
USAGE RULES
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field specifies the ultimate recipient of the funds being transferred.
CODES
with option A:
CODES
with option D:
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
or

PRESENCE
Optional
DEFINITION
CODES
BNF Information following is for the Beneficiary
USAGE RULES
it is intended.
Standards.
MT 206 Cheque Truncation Message
MT 206 Scope
This message is sent from the beneficiarys financial institution, directly or through one or more other financial institutions,
to the issuers financial institution to convey information about one or more truncated cheques, in the same currency. It is
used to debit or obtain credit under usual reserve.
In case of travellers cheques, this message may also be sent to a travellers cheque issuer.
This message may not be used to convey information about truncated cheques sent on a collection basis.
The MT 206 consists of three types of sequences:
Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individual
cheques detailed in sequence B.
Sequence B Cheque Details is a repetitive sequence where each occurrence provides details of an individual cheque.
Sequence C Settlement Information is a non-repetitive sequence and contains settlement information applicable to all
MT 206 Cheque Truncation Message
Mandatory Sequence A Common Elements
M 20 Senders 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
M 32J Cheque Amount 15d
10
O 58a Issuers Financial Institution A, C or D
11
O 25 Issuers 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
17
-----|
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 Institutions Account (for Settlement) [/1!a][/34x]
[35x]
20
O 19 Settlement Amount 17d
21
C1
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 Issuers Financial Institution
field 25 Issuers Account Number/Code
field 21D Cheque Number
If field 23E in sequence A contains
GENC or OTHR, and if field 29a in
sequence B is ...
then field 21D in
sequence B is ...
then field 25 in
sequence B is ...
then field 58a in
sequence 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 Issuers Account Number/Code
field 21D Cheque Number
If field 23E in sequence A contains
GENC or OTHR and if field 29a in
sequence B is ...
then field 21D in
sequence B is ...
then field 25 in
sequence B is ...
then field 58a in
sequence 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 (Error
code(s): D64).
If field 52a in sequence A is ... then field 52a in any occurrence of sequence B is
...
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
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
If field 28E in sequence A contains ... then field 32A in sequence C is ...
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 field
32J in sequence B (Error code(s): E23).
When field 28E contains MORE or LAST, field 19 must be equal to the sum of all occurrences of field 32J in sequence
B (Error code(s): E24).
MT 206 Usage Rules
The MT 206 can only be sent and/or received by financial institutions which have registered with SWIFT to send
and/or receive the MT 206/MT 256. If a registered user receives an MT 206 without bilateral agreement with the
Sender, the Receiver should query the message according to normal banking practice.
When sending a large number of truncated cheques, it may not be possible to fit them all into one MT 206. In that case:
Additional MTs 206 must be sent, and they are chained using field 28E.
All fields present in sequence A except field 28E must be repeated and contain exactly the same content.
Field 32A of the last message must contain the sum of all fields 19 of all chained messages.
Field 23E must contain the same value in all messages.
The currency code in fields 32A of all messages must be the same.
The use of this message is subject to bilateral/multilateral agreements between Sender/beneficiarys financial institu-
tion and Receiver of the truncation message and where necessary, between the issuers financial institution and the
issuer.
1. Field 20: Senders Reference
FORMAT
16x
PRESENCE
Mandatory
DEFINITION
This field specifies the reference assigned by the Sender to unambiguously identify the instruction.
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.
USAGE RULES
It is recommended that messages be sent in sequence.
All messages belonging to the same sequence must have exactly the same senders reference in field 20.
When more than one message is needed to convey all information, this field chains different messages by specifying the
sequence number in the total number of messages.
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.
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.
5. Field 52a: Safekeeper
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
Option C /34x (Party Identifier)
4*35x
(Party Identifier)
(Name & Address)
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.
6. Field 44A: Transaction Reference Number
FORMAT
Option A 65x
PRESENCE
Mandatory
DEFINITION
This number is generated by the beneficiarys financial institution to identify the transaction that this truncated cheque
represents.
7. Field 21D: Cheque Number
FORMAT
Option D 35x
PRESENCE
Conditional (C1 and C2)
DEFINITION
This field contains the number of the cheque, which is normally inserted on the cheque by the issuers financial institution.
8. Field 21E: Cheque Reference Number
FORMAT
Option E 35x
PRESENCE
Optional
DEFINITION
This field contains the reference of the cheque generated by the beneficiarys financial institution.
USAGE RULES
The cheque reference number is usually the archive reference (microfilm) and is as such used as a link to the physical item.
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 cheque
which in most cases can be read optically or magnetically, of the original cheque.
USAGE RULES
This field can be subdivided into its different parts with option G using an index to separate them, or it can be completely
unstructured, untreated and unaltered using option F.
It may contain any character defined in the z character set. The z character set contains the characters of both the x and
y character set extended with the characters @ and #:
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 the
network to indicate an end of field or subfield. Since option F only has 4 subfields, five CrLf in the code line would cause
a NAK by the network. Also, within option G, after a CrLf, a number and a slash are expected.
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).
fied in field 32A (Error code(s): C03, T40, T43).
11. Field 58a: Issuers Financial Institution
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Conditional (C2)
DEFINITION
This field identifies the issuers financial institution.
CODES
with option A:
PT 8!n Portugese National Clearing Code
CODES
with options C or D:
USAGE RULES
12. Field 25: Issuers Account Number/Code
FORMAT
35x (Account)
PRESENCE
Conditional (C2)
DEFINITION
This field identifies the issuer based on the account number appearing on the cheque.
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.
14. Field 30: Date of Issue/Encashment
FORMAT
6!n (Date)
PRESENCE
Optional
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.
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.
16. Field 52a: Safekeeper
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
Option C /34x (Account)
4*35x
(Party Identifier)
(Name & Address)
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:
USAGE RULES
Option D should only be used when the safekeeper has no BIC.
FORMAT
or

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
it is intended.
Standards.
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 Receivers account, or
credited to the Senders 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 19
in the chained messages.
19. Field 57a: Account With Institution (for Settlement)
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field identifies the account with institution at which the Sender wants to have the funds credited.
CODES
with option A:
CODES
USAGE RULES
This field may only be used where the settlement is not following the same route as the cheque truncation message. message
(see the example shown below).
20. Field 58B: Beneficiary Institutions Account (for Settlement)
FORMAT
[35x]
(Party Identifier)
(Location)
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
institution
one of these accounts is to be used for reimbursement
there is no bilaterally agreed account.
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.
fied in field 32A, if present (Error code(s): C03, T40, T43).
MT 207 Request For Financial Institution Transfer
MT 207 Scope
This message is used to move funds from the ordering financial institutions account, serviced at the receiving financial
institution or at the account servicing institution, or from an account(s) owned by the ordering institution for which the 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 institutions accounts, or
in favour of a third party, either domestically or internationally.
The message is sent by a financial institution on behalf of the ordering financial institution, ie, the account owning financial
institution, or on behalf of the initiating financial institution. It is subsequently received by a financial institution and
processed by this receiving financial institution or another account servicing financial institution.
The complete chain of parties and the transaction flow is illustrated by the following figure:
The parties mentioned in the chain are not necessarily different entities. The first column of the table below shows the
parties that can be omitted in an MT 207. The second column specifies the party which assumes the role of the party in the
first column, when it is not present:
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
The MT 207 consists of two sequences:
Sequence A General Information is a single occurrence mandatory sequence and contains information to be applied to
all individual transactions detailed in sequence B.
Sequence B Transaction Details is a repetitive sequence; each occurrence provides details of one individual transaction.
MT 207 Request for Financial Institution Transfer
Mandatory Sequence A General Information
1
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 /34x
4!a2!a2!c[3!c]
6
O 52a Account Servicing Institution A or C
7
8
----->
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
12
O 57a Account With Institution A, C or D
13
14
-----|
C1
In each occurrence of Sequence B: If field 56a is present then field 57a must also be present (Error code(s): D65).
If field 56a is ... then field 57a is ...
Present Mandatory
MT 207 Usage Rules
If field 21R is present in sequence A, and field 28D indicates that more than one message is chained for this request for
transfer instruction, the currency code must be the same for all occurrences of field 32B in sequence B of all chained
messages.
In case field 23E identifies with a code a sweeping (CMSW), topping (CMTO) or zero balancing (CMZB) operation,
the transaction amount in field 32B can equal zero.
In case field 28D indicates that messages are chained, all messages belonging to the same chain must have exactly the
same senders reference in field 20.
In case field 28D indicates that messages are chained, sequence A must be repeated and be identical for all messages
belonging to the same chain.
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 or
ordering 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 transactions
in the instruction, even if this instruction is chained in several messages. If the field is not used, all debit items are posted
individually.
3. Field 28D: Message Index / Total
FORMAT
Option D 5n/5n (Message Index)/(Total)
PRESENCE
Mandatory
DEFINITION
This field chains different messages by specifying the sequence number in the total number of messages.
USAGE RULES
Both the message index and the total number of messages allow the receiver to check that all transactions to be executed
have been received.
4. Field 30: Requested Execution Date
FORMAT
6!n (Date)
PRESENCE
Mandatory
DEFINITION
This field specifies the date on which all subsequent transactions should be initiated by the executing bank.
USAGE RULES
This is the date on which the ordering institutions account is to be debited.
5. Field 51A: Initiating Institution
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
PRESENCE
Optional
DEFINITION
This field identifies the institution which is authorised by the ordering institution/account servicing institution to order all
the 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 /34x
4!a2!a2!c[3!c]
(Account)
(BIC)
PRESENCE
Mandatory
DEFINITION
This field identifies the account owning financial institution whose account is to be debited with all transactions in
sequence(s) B.
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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
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:
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 system
code preceded by a double slash //.
FORMAT
6*35x (Narrative - Structured Format )
or

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver, ie, Sender of the original message regarding the reason for a
return, ie, reversal, rejection or revocal.
CODES
The codes REJT or RETN must be used in this field in the first position of the first line, placed between slashes (/). It is
mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.
The first element in line 1 must contain either code /RETN/ or /REJT/ (Error code(s): D82).
USAGE RULES
The Reject/Return mechanism is used to reject or return all the transactions within the MT 207 message. For returns or
rejections of a single transaction within the MT 207 (ie, sequence B), the MT 295 should be used as per the Standards
Usage Guidelines.
9. Field 21: Transaction Reference
FORMAT
16x
PRESENCE
Mandatory
DEFINITION
This field specifies the unambiguous reference for the individual transaction contained in a particular occurrence of
sequence B.
USAGE RULES
In transaction specific queries, cancellations, etc., the Senders reference together with the content of this field provides the
transaction identification.
10. Field 23E: Instruction Code
FORMAT
Option E 4!c[/30x] (Instruction Code) (Additional Information)
PRESENCE
Optional
DEFINITION
This field specifies instructions for the subsequent parties in the transaction chain.
CODES
One of the following codes must be used (Error code(s): T47).
CMSW This transaction contains a cash management instruction, requesting to sweep the account of the
ordering 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 or
OTHR (Error code(s): D66).
In each occurrence of Sequence B: when this field is used more than once, the following combinations are not allowed
(Error code(s): D67).
CMSW 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 with
the exception of OTHR. The code word OTHR may be repeated (Error code(s): E46).
USAGE RULES
To facilitate the receiving banks processing when multiple codes are used, the codes must appear in the following order:
instructions for the receiver of the message (CMSW, CMTO, CMZB, CORT, URGP)
codes impacting the routing or composition of the resulting payment message (NETS, RTGS)
codes containing instructions for one of the following parties in the transaction chain (PHON)
information codes ( OTHR)
11. Field 32B: Currency/Transaction Amount
FORMAT
PRESENCE
Mandatory
DEFINITION
This field specifies the currency and amount of the subsequent transfer to be executed by the Receiver.
Currency must be the same for all occurrences of this field (Error code(s): C02).
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Optional
DEFINITION
This field specifies the financial institution between the Receiver and the account with institution, through which the trans-
action must pass.
CODES
with option A:
CODES
with option D:
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 and
in the first of the fields 56a, 57a and 58a of the payment instruction.
the code //FW appears in the optional Party Identifier of field 56a, 57a or 58a.
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
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
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:
USAGE RULES
tions.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Mandatory
DEFINITION
This field specifies the beneficiary financial institution of the subsequent operation from the particular occurrence of
sequence B.
CODES
with option A:
CODES
with option D:
USAGE RULES
Party Identifier may contain the beneficiary financial institutions account number.
If the message is used to request the transfer of funds between the ordering financial institutions accounts, this field must
contain the BIC of this institution.
tions.
MT 210 Notice to Receive
MT 210 Scope
This message type is sent by an account owner to one of its account servicing institutions.
It is an advance notice to the account servicing institution that it will receive funds to be credited to the Senders account.
MT 210 Notice to Receive
1
O 25 Account Identification 35x
2
M 30 Value Date 6!n
3
----->
4
5
O 50a Ordering Customer C or no option letter
6
7
8
-----|
C1
The repetitive sequence must not appear more than ten times (Error code(s): T10).
C2
Either field 50a or field 52a, but not both, must be present in a repetitive sequence (Error code(s): C06).
If field 50a is... 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
2. Field 25: Account Identification
FORMAT
35x (Account)
PRESENCE
Optional
DEFINITION
This field identifies the account to be credited with the incoming funds.
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 the
related transaction.
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 option letter 4*35x (Name & Address)
PRESENCE
Conditional (C2)
DEFINITION
This field specifies the ordering party when it is not a financial institution.
The BEI, ie, a BIC with subtype BEID, MCCO, TESP or TRCO, must be a SWIFT registered address, either connected or
non-connected (Error code(s): T27, T28, T29, T45, E57).
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
PRESENCE
Conditional (C2)
DEFINITION
This field specifies the ordering party when it is a financial institution.
CODES
with option A:
CODES
with option D:
USAGE RULES
When the Sender is also the ordering institution, it will be repeated in this field.
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
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:
USAGE RULES
This field is used when the intermediary institution is other than the ordering party.
MT 256 Advice of Non-Payment of Cheques
MT 256 Scope
This message is sent by the Receiver of one or more MT 206s. It is used to inform the Sender of (a) previously sent
MT 206(s) of the non-payment of specified truncated cheques.
This message may only be used to specify dishonoured items that result in reversing a previous payment settlement.
The MT 256 consists of three types of sequences:
Sequence A Common Elements is a non-repetitive sequence and contains information applicable to all individual
Sequence B Cheque Details is a repetitive sequence where each occurrence provides details of an individual cheque.
Sequence C Settlement Details is a non-repetitive sequence and contains settlement information applicable to all
MT 256 Advice of Non-Payment of Cheques
Mandatory Sequence A Common Elements
1
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
O 71F Senders Charges 3!a15d
11
O 71H Issuers 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 Senders Charges 3!a15d
17
O 71K Sum of Issuers Financial Institution Charges 3!a15d
18
O 57a Account With Institution (for Settlement) A, C or D
19
O 58B Beneficiary Institutions Account (for Settlement) [/1!a][/34x]
[35x]
20
C1
If field 37J is present, then field 71G must also be present (Error code(s): E25).
If field 37J in sequence B is... 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 sequence
C3
The amount specified in field 71J in sequence C must be equal to the sum of all occurrences of field 71G in sequence B
(Error code(s): E27).
C4
The currency code in the amount fields (71F, 71G, 71H, 71J, 71K, 71L, 32A) must be the same for all occurrences of
these fields in the message (Error code(s): C02).
C5
If no changes are included, field 32A in sequence C contains the sum of the amounts of all fields 32J in sequence B.
Field 19 must not be present (Error code(s): D80).
C6
If charges are included, field 19 must be present. It must contain the sum of amounts of all fields 32J in sequence B
(Error code(s): C01).
C7
Field 21 must be present either in sequence A, or in all occurrences of sequence B (Error code(s): E28).
If field 21 in sequence A is... 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, field
71L 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
C9
If field 71G is present in any occurrence of sequence B, then field 71J must be present in sequence C. Otherwise, field
71J is not allowed (Error code(s): E30).
If field 71G in sequence B is... 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, field
71K 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 sequence
MT 256 Usage Rules
The MT 256 can only be sent or received by financial institutions which have registered with SWIFT to send or receive
the MT 206/MT 256. If a registered user receives an MT 256 without bilateral agreement with the Sender, the Receiver
should query the message according to normal banking practice.
This message must not be used to specify reasons that at a later stage could lead to a non-payment, eg, a request for a
photocopy to check the signature. For this, an MT 295 Queries must be used, for which special codes are provided.
For dishonoured cheques in different currencies, different MT 256s must be used.
When the Sender does not have authority to debit the Receivers account, the Receiver of the MT 256 must credit the
account according to the specified value date.
Field 30 may only be used if the original value date differs from the value date provided in this field. Absence of field
30 implies that the value date in field 32A is taken from the original MT 206.
FORMAT
16x
PRESENCE
Mandatory
DEFINITION
2. Field 21: Related Message Reference
FORMAT
16x
PRESENCE
Conditional (C7)
DEFINITION
This field contains the Senders reference of the previously received MT 206 Cheque Truncation Message, ie, field 20 of the
original MT 206.
3. Field 44A: Transaction Reference Number
FORMAT
Option A 65x
PRESENCE
Mandatory
DEFINITION
This field contains the TRN, field 20 of the previously received MT 206, generated by the beneficiarys financial institution,
which identifies the transaction that this dishonoured cheque represents.
4. Field 21: Related Message Reference
FORMAT
16x
PRESENCE
Conditional (C7)
DEFINITION
This field contains the Senders reference of the previously received MT 206 Cheque Truncation Message in case this
MT 256 is informing of the non-payment of cheques in the same currency that were included in different MTs 256.
5. Field 21D: Cheque Number
FORMAT
Option D 35x
PRESENCE
Optional
DEFINITION
This field contains the number of the cheque that has been dishonoured, normally inserted on the cheque by the issuers
financial institution.
USAGE RULES
This field must be the same as the cheque number specified in the original MT 206.
6. Field 21E: Cheque Reference Number
FORMAT
Option E 35x
PRESENCE
Optional
DEFINITION
This field contains the reference of the cheque, as generated by the beneficiarys financial institution.
USAGE RULES
This reference is usually the archive reference (microfilm) and is as such used as a link to the physical item.
This field must be quoted if it is present in the original MT 206.
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.
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.
8. Field 32J: Cheque Amount
FORMAT
Option J 15d (Amount)
PRESENCE
Mandatory
DEFINITION
This field contains the amount specified on the dishonoured cheque.
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.
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 maximum
length (Error code(s): T40, T43).
10. Field 71G: Interest Charges
FORMAT
Option G 3!a15d (Currency) (Amount)
PRESENCE
Conditional (C1)
DEFINITION
This field specifies the currency and the interest charges due to the Sender of the MT 256.
USAGE RULES
These interest charges are computed at a prevailing interest rate (field 37J) from the original value date (field 30) up to the
date when recovery of funds is expected to take place (field 32A).
11. Field 71F: Senders Charges
FORMAT
Option F 3!a15d (Currency) (Amount)
PRESENCE
Optional
DEFINITION
This field specifies the currency and the charges due to the Sender of the MT 256, if different from the issuers financial
institution, for the above specified reason.
12. Field 71H: Issuers Financial Institution Charges
FORMAT
Option H 3!a15d (Currency) (Amount)
PRESENCE
Optional
DEFINITION
This field specifies the currency and the charges due to the issuers financial institution, for the above specified reason.
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 total
amount to be claimed.
14. Field 30: Original Value Date
FORMAT
6!n (Date)
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 be
taken into account, by specifying that date. In this case, ie, when back-valuing is applied, no separate fields must be used to
indicate the interest charges.
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 the
maximum length. The number of decimal digits in field 19 must not exceed the maximum for its corresponding currency in
field 32A in sequence C (Error code(s): C03, T40, T43).
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.
17. Field 71L: Sum of Senders Charges
FORMAT
Option L 3!a15d (Currency) (Amount)
PRESENCE
Conditional (C8)
DEFINITION
This field specifies the currency and the sum of all occurrences of field 71F in sequence B.
18. Field 71K: Sum of Issuers Financial Institution Charges
FORMAT
Option K 3!a15d (Currency) (Amount)
PRESENCE
Conditional (C10)
DEFINITION
This field specifies the currency and the sum of all occurrences of field 71H in sequence B.
19. Field 57a: Account With Institution (for Settlement)
FORMAT
4!a2!a2!c[3!c]
(Party Identifier)
(BIC)
4*35x
(Party Identifier)
(Name & Address)
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
USAGE RULES
This field may only be used where the settlement does not follow the same route as the MT 256 (this message).
20. Field 58B: Beneficiary Institutions Account (for Settlement)
FORMAT
[35x]
(Party Identifier)
(Location)
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
institution
one of these accounts is to be used for reimbursement
there is no bilaterally agreed account.
MT 290 Advice of Charges, Interest and Other Adjustments
Please refer to Category n - Common Group Messages, Chapter n90 Advice of Charges, Interest and Other Adjustments for
details concerning this message type.
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 this
message type.
MT 293 Information Service Message
MT 293 Scope
This message is an envelope exchanged between a financial institution and an information service.
This message is intended for computer-to-computer communication to send updates and to receive updates from databases.
The message is an envelope of which the contents is not intended for direct human entry or processing, and is thus not
designed to be printed unprocessed.
The contents of the envelope is service dependent and is not part of the MT 293 standard. For details on the contents, refer
to the appropriate standard defined with the service. The envelope itself consists of fields to uniquely identify the message
into a sequence of messages, and to allow routing to the appropriate organisation, database or workstation.
The message is available as an authenticated message. The messages can contain updates concerning all categories and all
markets. The markets in a particular update are detailed in a repetitive field.
MT 293 Information Service Message
Mandatory Sequence A Envelope Information
1
M 28D Message Index/Total 5n/5n
2
----->
M 14T Type of Service, Market and Data 4!c[/4!c[/4!c]]
3
-----|
M 22A Type of Operation 4!c
4
O 21 Related Reference 16x
5
M 12 Sub-Message Type 3!n
6
Mandatory Sequence B Envelope Contents
M 77S Envelope Contents 9800z
7
There are no network validated rules that apply to this message type.
FORMAT
16x
PRESENCE
Mandatory
DEFINITION
This field must not start or end with a slash / and not contain two consecutive slashes // (Error code(s): T26).
2. Field 28D: Message Index/Total
FORMAT
Option D 5n/5n (Number) (Total)
PRESENCE
Mandatory
DEFINITION
When more than one message is needed to convey all information, this field links different messages by specifying the
sequence number in the total number of messages.
USAGE RULES
It is recommended that messages be sent in sequence.
All messages belonging to the same sequence must have the same content as field 20.
No part of the envelope contents should be duplicated in subsequent messages. A straight concatenation of all fields 77S
should then result in one large field 77S.
3. Field 14T: Type of Service, Market and Data
FORMAT
Option T 4!c[/4!c[/4!c]] (Type) (Market) (Data)
PRESENCE
Mandatory
DEFINITION
This field is meant for routing and duplication of the message to the appropriate organisation, database or workstation. It is
then left up to the receiving application to filter out data not relevant for it.
Type identifies the information service the message is intended for or is coming from.
Market identifies the financial market for which the message is applicable.
Data identifies the data element or group of data elements the envelope provides an update for.
CODES
The following code is defined for Type. The list of codes will expand as more services use this message type:
INFS This message contains an update to or from an information service.
CODES
The following codes are currently defined for the Market, but the list is not exhaustive:
ALLM All Markets.
PAYM Payments.
COLL Collections.
DOCC Documentary credits.
FXMM Forex, money markets and derivatives.
SECS Securities.
TRAD Other Trade Services.
PMET Precious metals.
4. Field 22A: Type of Operation
FORMAT
Option A 4!c
PRESENCE
Mandatory
DEFINITION
This field specifies whether the message contains an update, query or answer to a query.
CODES
One of the following codes must be used (Error code(s): T36):
R001 Instruction. The Receiver is expected to update its records and to act accordingly, or to notify other-
wise.
R002 Query. The Receiver is expected to provide a response / report.
A001 Solicited information, ie, an answer to a query, eg, a report or an acknowledgement.
A002 Unsolicited information, eg, a report or warning.
FORMAT
16x
PRESENCE
Optional
DEFINITION
This field contains the contents of field 20 Senders Reference of a related message, eg, a query message.
This field must not start or end with a slash / and not contain two consecutive slashes // (Error code(s): T26).
USAGE RULES
If an answer relates to a previously sent query, field 21 must contain a copy of the Senders reference, field 20, of the query.
If a query relates to a previously sent update or response, field 21 must contain a copy of the Senders reference, field 20, of
the previous message.
If an update is forwarded by the information service, field 21 contains the reference of the original sender.
6. Field 12: Sub-Message Type
FORMAT
3!n
PRESENCE
Mandatory
DEFINITION
This field specifies the message type number, as defined by the information service, for the contents of field 77S.
USAGE RULES
An information service may also use this field to imply a particular release version.
7. Field 77S: Envelope Contents
FORMAT
Option S 9800z (Narrative)
PRESENCE
Mandatory
DEFINITION
This field conveys the actual message contents in a format defined by the information service.
The actual format of this field is defined by the information service.
USAGE RULES
The meaning and the conditions of the data in field 77S is service dependent and is not part of the standard.
The field 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
Note that the } must not be used inside the field.
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.
MT 298 Proprietary Message
Please refer to Category n - Common Group Messages, Chapter n98 Proprietary Message for details concerning this
message type.
MT 299 Free Format Message
Please refer to Category n - Common Group Messages, Chapter n99 Free Format Message for details concerning this
message type.
Table of Contents
. . . . . . . . . . . . . . . . . . . . . . . 2 Legal Notices
. . . . . . . . . . . . . . . . . . . . . . . 3 Overview
. . . . . . . . . . . . . . . . . . . . 3 Added Message Types
. . . . . . . . . . . . . . . . . . . 3 Removed Message Types
. . . . . . . . . . . . . . . . . . . 3 Modified Message Types
. . . . . . . . . . . . . 4 MT 200 Financial Institution Transfer for its Own Account
. . . . . . . . . . . . . . . . . . . . . . 4 MT 200 Scope
. . . . . . . . . . . . . . . . . . 4 MT 200 Format Specifications
. . . . . . . . . . . . . . . . . . 4 MT 200 Network Validated Rules
. . . . . . . . . . . . . . . . . . . . 4 MT 200 Usage Rules
. . . . . . . . . . . . . . . . 4 MT 200 Field Specifications (updated)
. . . . . . . . . . . . . . . 5 1. Field 20: Transaction Reference Number
. . . . . . . . . . . . . 5 2. Field 32A: Value Date, Currency Code, Amount
. . . . . . . . . . . . . . . . 5 3. Field 53B: Senders Correspondent
. . . . . . . . . . . . . . . . 6 4. Field 56a: Intermediary (updated)
. . . . . . . . . . . . . . 8 5. Field 57a: Account With Institution (updated)
. . . . . . . . . . . . . . . 11 6. Field 72: Sender to Receiver Information
. . . . . . . . . . 13 MT 201 Multiple Financial Institution Transfer for its Own Account
. . . . . . . . . . . . . . . . . . . . . . 13 MT 201 Scope
. . . . . . . . . . . . . . . . . . . . 14 MT 201 Usage Rules
. . . . . . . . . . . . . . . . . . 14 1. Field 19: Sum of Amounts
. . . . . . . . . . . . . . . . . . . 14 2. Field 30: Value Date
. . . . . . . . . . . . . . . . 15 3. Field 53B: Senders Correspondent
. . . . . . . . . . . . . . . . 17 6. Field 32B: Currency Code, Amount
. . . . . . . . . . . . . . . 24 MT 202 General Financial Institution Transfer
. . . . . . . . . . . . . . . . . . . . . . 24 MT 202 Scope
. . . . . . . . . . . . . . . . . . . . 25 MT 202 Usage Rules
. . . . . . . . . . . . . . . . . . 25 2. Field 21: Related Reference
. . . . . . . . . . . . . . . . . . 26 3. Field 13C: Time Indication
. . . . . . . . . . . . . 27 4. Field 32A: Value Date, Currency Code, Amount
. . . . . . . . . . . . . . . 27 5. Field 52a: Ordering Institution (updated)
. . . . . . . . . . . . . . 29 6. Field 53a: Senders Correspondent (updated)
. . . . . . . . . . . . . . 30 7. Field 54a: Receivers Correspondent (updated)
. . . . . . . . . . . . . . 36 10. Field 58a: Beneficiary Institution (updated)
. . . . . . . . . . . . . 41 MT 203 Multiple General Financial Institution Transfer
. . . . . . . . . . . . . . . . . . . . . . 41 MT 203 Scope
. . . . . . . . . . . . . . . . . . . . 42 MT 203 Usage Rules
. . . . . . . . . . . . . . . . . . 42 1. Field 19: Sum of Amounts
. . . . . . . . . . . . . . . . . . . 43 2. Field 30: Value Date
. . . . . . . . . . . . . . . 43 3. Field 52a: Ordering Institution (updated)
i Standards Release Guide 2003 - Final edition - February 2003
Table Of Contents SWIFTStandards - Category 2
. . . . . . . . . . . . . . . 45 4. Field 53a: Senders Correspondent (updated)
. . . . . . . . . . . . . . . 46 5. Field 54a: Receivers Correspondent (updated)
. . . . . . . . . . . . . . . . 47 6. Field 72: Sender to Receiver Information
. . . . . . . . . . . . . . . . 49 7. Field 20: Transaction Reference Number
. . . . . . . . . . . . . . . . . . . 49 8. Field 21: Related Reference
. . . . . . . . . . . . . . . . . 50 9. Field 32B: Currency Code, Amount
. . . . . . . . . . . . . . . . . . 50 10. Field 56a: Intermediary (updated)
. . . . . . . . . . . . . . . 53 11. Field 57a: Account With Institution (updated)
. . . . . . . . . . . . . . . 55 12. Field 58a: Beneficiary Institution (updated)
. . . . . . . . . . . . . . . . 60 MT 204 Financial Markets Direct Debit Message
. . . . . . . . . . . . . . . . . . . . . . . 60 MT 204 Scope
. . . . . . . . . . . . . . . . . . . . 60 MT 204 Format Specifications
. . . . . . . . . . . . . . . . . . . 61 MT 204 Network Validated Rules
. . . . . . . . . . . . . . . . . . . . . . 61 MT 204 Usage Rules
. . . . . . . . . . . . . . . . . . 61 MT 204 Field Specifications (updated)
. . . . . . . . . . . . . . . . . . . 61 2. Field 19: Sum of Amounts
. . . . . . . . . . . . . . . . . . . . . 62 3. Field 30: Value Date
. . . . . . . . . . . . . . . . 65 5. Field 58a: Beneficiary Institution (updated)
. . . . . . . . . . . . . . . . . . 70 9. Field 32B: Transaction Amount
. . . . . . . . . . . . . . . . . 70 10. Field 53a: Debit Institution (updated)
. . . . . . . . . . . . . . . . 74 MT 205 Financial Institution Transfer Execution
. . . . . . . . . . . . . . . . . . . . . . . 74 MT 205 Scope
. . . . . . . . . . . . . . . . . . . 75 3. Field 13C: Time Indication
. . . . . . . . . . . . . . . 76 4. Field 32A: Value Date, Currency Code, Amount
. . . . . . . . . . . . . . . . 77 5. Field 52a: Ordering Institution (updated)
. . . . . . . . . . . . . . . 79 6. Field 53a: Senders Correspondent (updated)
. . . . . . . . . . . . . . . . 85 9. Field 58a: Beneficiary Institution (updated)
. . . . . . . . . . . . . . . . . . . 89 MT 206 Cheque Truncation Message
. . . . . . . . . . . . . . . . . . . . . . . 89 MT 206 Scope
. . . . . . . . . . . . . . . . . . . . . . 92 MT 206 Usage Rules
. . . . . . . . . . . . . . . . . . . 92 1. Field 20: Senders Reference
. . . . . . . . . . . . . . . . . . 93 2. Field 28E: Message Index/Total
. . . . . . . . . . . . . . . . . . . . 93 3. Field 23E: Cheque Type
. . . . . . . . . . . . . . . . 94 4. Field 17A: Cheque Truncation Indicator
. . . . . . . . . . . . . . . . . . 95 5. Field 52a: Safekeeper (updated)
. . . . . . . . . . . . . . . . 97 6. Field 44A: Transaction Reference Number
. . . . . . . . . . . . . . . . . . . 97 7. Field 21D: Cheque Number
. . . . . . . . . . . . . . . . . 97 8. Field 21E: Cheque Reference Number
. . . . . . . . . . . . . . . . . . . . . 98 9. Field 29a: Code Line
. . . . . . . . . . . . . . . . . . . 98 10. Field 32J: Cheque Amount
. . . . . . . . . . . . . . 99 11. Field 58a: Issuers Financial Institution (updated)
. . . . . . . . . . . . . . . . 101 12. Field 25: Issuers Account Number/Code
. . . . . . . . . . . . . . . . . 101 13. Field 26E: Represented Cheque Entry
. . . . . . . . . . . . . . . . . 101 14. Field 30: Date of Issue/Encashment
Standards Release Guide 2003 - Final edition - February 2003 ii
SWIFTStandards - Category 2 Table Of Contents
. . . . . . . . . . . . . . . . . 102 15. Field 39C: Place of Issue/Encashment
. . . . . . . . . . . . . . . . . . 102 16. Field 52a: Safekeeper (updated)
. . . . . . . . . 105 18. Field 32A: Value Date, Currency Code and Sum of Settlement Amounts
. . . . . . . . . . . 106 19. Field 57a: Account With Institution (for Settlement) (updated)
. . . . . . . . . . . . 108 20. Field 58B: Beneficiary Institutions Account (for Settlement)
. . . . . . . . . . . . . . . . . . . 109 21. Field 19: Settlement Amount
. . . . . . . . . . . . . . . . 110 MT 207 Request For Financial Institution Transfer
. . . . . . . . . . . . . . . . . . . . . . . 110 MT 207 Scope
. . . . . . . . . . . . . . . . . . . . . . 113 MT 207 Usage Rules
. . . . . . . . . . . . 114 2. Field 21R: Specified Reference of the Ordering Institution
. . . . . . . . . . . . . . . . . . 114 3. Field 28D: Message Index / Total
. . . . . . . . . . . . . . . . . 115 4. Field 30: Requested Execution Date
. . . . . . . . . . . . . . . . 115 5. Field 51A: Initiating Institution (updated)
. . . . . . . . . . . . . . . . 116 6. Field 52G: Ordering Institution (updated)
. . . . . . . . . . . . . . 116 7. Field 52a: Account Servicing Institution (updated)
. . . . . . . . . . . . . . . . . . 119 9. Field 21: Transaction Reference
. . . . . . . . . . . . . . . . . . . 119 10. Field 23E: Instruction Code
. . . . . . . . . . . . . . . . 121 11. Field 32B: Currency/Transaction Amount
. . . . . . . . . . . . . . . 126 14. Field 58a: Beneficiary Institution (updated)
. . . . . . . . . . . . . . . . . . . . . 129 MT 210 Notice to Receive
. . . . . . . . . . . . . . . . . . . . . . . 129 MT 210 Scope
. . . . . . . . . . . . . . . . . . 130 2. Field 25: Account Identification
. . . . . . . . . . . . . . . . . . . . . 131 3. Field 30: Value Date
. . . . . . . . . . . . . . . . . 131 5. Field 32B: Currency Code, Amount
. . . . . . . . . . . . . . . . 132 6. Field 50a: Ordering Customer (updated)
. . . . . . . . . . . . . . . . 132 7. Field 52a: Ordering Institution (updated)
. . . . . . . . . . . . . . . . . 137 MT 256 Advice of Non-Payment of Cheques
. . . . . . . . . . . . . . . . . . . . . . . 137 MT 256 Scope
. . . . . . . . . . . . . . . . . . . . . . 140 MT 256 Usage Rules
. . . . . . . . . . . . . . . . . 141 2. Field 21: Related Message Reference
. . . . . . . . . . . . . . . . 141 3. Field 44A: Transaction Reference Number
. . . . . . . . . . . . . . . . . 141 4. Field 21: Related Message Reference
. . . . . . . . . . . . . . . . . . . 142 5. Field 21D: Cheque Number
. . . . . . . . . . . . . . . . . 142 6. Field 21E: Cheque Reference Number
. . . . . . . . . . . . . . . 142 7. Field 23E: Reason for Non-Payment/Dishonour
. . . . . . . . . . . . . . . . . . . 144 8. Field 32J: Cheque Amount
. . . . . . . . . . . . . . . . . . . . 144 9. Field 37J: Interest Rate
. . . . . . . . . . . . . . . . . . . 145 10. Field 71G: Interest Charges
. . . . . . . . . . . . . . . . . . . 145 11. Field 71F: Senders Charges
. . . . . . . . . . . . . . 146 12. Field 71H: Issuers Financial Institution Charges
. . . . . . . . . . 146 13. Field 32A: Value Date, Currency Code and Total Amount Claimed
. . . . . . . . . . . . . . . . . . 146 14. Field 30: Original Value Date
. . . . . . . . . . . . . . . . . . 147 15. Field 19: Total Cheque Amount
. . . . . . . . . . . . . . . . . 147 16. Field 71J: Sum of Interest Charges
iii Standards Release Guide 2003 - Final edition - February 2003
Table Of Contents SWIFTStandards - Category 2
. . . . . . . . . . . . . . . . . 148 17. Field 71L: Sum of Senders Charges
. . . . . . . . . . . . . 148 18. Field 71K: Sum of Issuers Financial Institution Charges
. . . . . . . . . . . 149 19. Field 57a: Account With Institution (for Settlement) (updated)
. . . . . . . . . . . . 151 20. Field 58B: Beneficiary Institutions Account (for Settlement)
. . . . . . . . . . . . . . 152 MT 290 Advice of Charges, Interest and Other Adjustments
. . . . . . . . . . . 153 MT 291 Request for Payment of Charges, Interest and Other Expenses
. . . . . . . . . . . . . . . . . . . . 154 MT 292 Request for Cancellation
. . . . . . . . . . . . . . . . . . . 155 MT 293 Information Service Message
. . . . . . . . . . . . . . . . . . . . . . . 155 MT 293 Scope
. . . . . . . . . . . . . . . . . . . . 156 MT 293 Field Specifications
. . . . . . . . . . . . . . . . . . 156 2. Field 28D: Message Index/Total
. . . . . . . . . . . . . . . 157 3. Field 14T: Type of Service, Market and Data
. . . . . . . . . . . . . . . . . . . 158 4. Field 22A: Type of Operation
. . . . . . . . . . . . . . . . . . . 159 6. Field 12: Sub-Message Type
. . . . . . . . . . . . . . . . . . . 159 7. Field 77S: Envelope Contents
. . . . . . . . . . . . . . . . . . . . . . . 161 MT 295 Queries
. . . . . . . . . . . . . . . . . . . . . . . 162 MT 296 Answers
. . . . . . . . . . . . . . . . . . . . . 163 MT 298 Proprietary Message
. . . . . . . . . . . . . . . . . . . . 164 MT 299 Free Format Message
Standards Release Guide 2003 - Final edition - February 2003 iv
SWIFTStandards - Category 2 Table Of Contents

(SwiftStandards) Category 2 - Financial Insitution Transfers (MT200 - MT299)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

(SwiftStandards) Category 2 - Financial Insitution Transfers (MT200 - MT299)

Diunggah oleh

Hak Cipta:

Format Tersedia

SWIFTStandards

Anda mungkin juga menyukai