SWIFTStandards

Category 1 Customer Payments & Cheques
November 2003 Standards Release Standards Release Guide 2003 - Final edition - February 2003

1

Legal Notices

SWIFTStandards - Category 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 Adèle 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, reference 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 inadvertent 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 trademarks of their respective owners. Patent pending: SWIFTNet - TrustAct - e-paymentsPlus. February 2003 edition

2

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

Overview

Overview
Added Message Types Removed Message Types Modified Message Types

Added Message Types
None

Removed Message Types
MT100

Modified Message Types
MT101 MT102 MT102+ MT103 MT103+ MT104 MT107 MT110 MT111 MT112

Standards Release Guide 2003 - Final edition - February 2003

3

MT 100

SWIFTStandards - Category 1

MT 100 Customer Transfer
Note:

the MT 100 Customer Transfer will be removed from the SWIFT network with Standards Release 2003. All users should migrate to the MT 103 Single Customer Credit Transfer before the removal of the MT 100.

MT 100 Scope
This message type is sent by or on behalf of the financial institution of the ordering customer, directly or through (a) correspondent(s), to the financial institution of the beneficiary customer. It is used to convey a funds transfer instruction in which the ordering customer or the beneficiary customer, or both, are non-financial institutions from the perspective of the Sender. This message may only be used for clean payment instructions. It must not be used to advise the remitting bank of a payment for a clean, eg, cheque, collection.

MT 100 Format Specifications
MT 100 Customer Transfer Status M M M O O O O O M O O O Tag 20 32A 50 52a 53a 54a 56a 57a 59 70 71A 72 Field Name Transaction Reference Number Value Date, Currency Code, Amount Ordering Customer Ordering Institution Sender’s Correspondent Receiver’s Correspondent Intermediary Account With Institution Beneficiary Customer Details of Payment Details of Charges Sender to Receiver Information M = Mandatory O = Optional 16x 6!n3!a15d 4*35x A or D A, B or D A, B or D A or D A, B or D [/34x] 4*35x 4*35x 3!a 6*35x Content/Options No. 1 2 3 4 5 6 7 8 9 10 11 12

4

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 100

MT 100 Network Validated Rules
C1 If field 56a is present, then field 57a must also be present (Error code(s): C81). C2 The code /RCB/ may only be used in field 72 if both field 53a and field 54a are present in the message (Error code(s): C74).

MT 100 Usage Rules
At a minimum, either field 50 Ordering Customer or field 59 Beneficiary Customer must be a non-financial institution. If the Sender and the Receiver have a single direct account relationship, in the currency of the transfer, and this account is to be used for reimbursement, fields 53a and/or 54a must not appear in the message. In all other cases, the relevant reimbursement details will be specified in fields 53a and/or 54a in line with the field specifications. Where the Receiver does not service an account for the beneficiary customer and there is no field 57a Account With Institution or alternative instructions in field 72, the Receiver shall effect payment in an appropriate manner of its choice.

MT 100 Field Specifications
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

Standards Release Guide 2003 - Final edition - February 2003

5

Field 50: Ordering Customer FORMAT 4*35x (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the originator of the transfer. either connected or non-connected (Error code(s): T27. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). this field must contain the name of the Sender. Field 52a: Ordering Institution FORMAT Option A Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies the financial institution of the ordering customer. USAGE RULES Where the originator is also the Sender of the message. T28. T40. T43).Category 1 DEFINITION This field specifies the value date.MT 100 SWIFTStandards . when different from the Sender. Currency must be a valid ISO 4217 currency code (Error code(s): T52). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 6 Standards Release Guide 2003 . The integer part of Amount must contain at least one digit. currency and amount to be transferred.February 2003 .Final edition . A decimal comma is mandatory and is included in the maximum length. T45). 4. 3. T29.

using option B with the party identifier only. When field 53B is used to specify a branch city name. the account to be credited or debited must be indicated in field 53a. will be used. when field 53a is present. and the Sender intends to send a cover message to the branch of the Receiver. In this case. The use and interpretation of fields 53a and 54a is. in all cases. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. either connected or non-connected (Error code(s): T27. USAGE RULES The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and Receiver. Field 53a: Sender’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. and one of these accounts is to be used for reimbursement.Category 1 MT 100 USAGE RULES The optional Party Identifier must not be present.February 2003 7 . In those cases where there are multiple direct account relationships. If there is no direct account relationship. the relationship between the Sender and the Receiver and the contents of field 54a. ie. in the currency of the transfer. a cover message. Option A is the preferred option. T28. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver. in the currency of the transaction. T29. it must always be a branch of the Sender. 5. When field 53a is present and contains a branch of the Sender. then field 53a must be present. Standards Release Guide 2003 . T45). dictated by the currency of the transaction and the correspondent relationship between the Sender and the Receiver relative to that currency.SWIFTStandards . the need for a cover message is dependent on the currency of the transaction. if present. In all other cases. in the currency of the transaction.Final edition . the Receiver will be paid by its branch in field 53a. between the Sender and the Receiver (or branch of the Receiver when specified in field 54a). must be sent to the financial institution identified in field 53a. MT 202/203 or equivalent non-SWIFT. between the Sender and the Receiver.

and is not preceded by field 53a. the Receiver will be paid by its branch in field 54a. ie. T28. 8 Standards Release Guide 2003 . shall be specified in field 54a and field 72 shall contain the ISO Bank Identifier Code of the Receiver’s branch. this financial institution. In those cases where field 54a contains a branch of the Receiver. T29. preceded by /RCB/. or field 53a contains an account of the Sender serviced by the Receiver’s branch. The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and the Receiver. In all other cases where field 54a contains a branch of the Receiver. Field 54a: Receiver’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) 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. intermediary reimbursement institution. The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. in the currency of the transfer.Final edition . Field 54a containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53a. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver. A branch of the Sender must not appear in field 54a. depending on the currency of the transfer and the relationship between the Sender and the Receiver. T45).Category 1 6. USAGE RULES Where funds will be made available to the Receiver at its branch through a financial institution other than that indicated in field 53a. will be used. If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender.MT 100 SWIFTStandards . the Receiver will be paid by the financial institution in field 54a.February 2003 . the Receiver will claim reimbursement from its branch. field 54a must not be present. either connected or non-connected (Error code(s): T27. the Receiver will claim reimbursement from its branch or will be paid by its branch.

February 2003 9 ..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement Standards Release Guide 2003 . CODES Party Identifier may be used to indicate a national clearing system code. Field 56a: Intermediary FORMAT Option A Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies a party between the Receiver and the account with institution through which the transaction must pass. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT NZ PT RT 5!n 6!n 8!n 9!n 8.Final edition .SWIFTStandards .Category 1 MT 100 7.

Category 1 SC 6!n UK Domestic Sort Code CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN IT NZ PT RT RU SC SW SW 9!n 6!n 3.9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) 10 Standards Release Guide 2003 .5n 6!n 5!n 6!n 8!n 9!n 6!n 4!n 8.February 2003 .Final edition ...MT 100 SWIFTStandards .

February 2003 11 . When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS). eg. it may be followed by another domestic clearing code.SWIFTStandards . If it is used with option D. 8. CODES Party Identifier may be used to indicate a national clearing system code. either connected or non-connected (Error code(s): T27. T28. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. //AU. This is applicable even if field 59 contains an IBAN. Option A is the preferred option. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a. USAGE RULES When one of the codes //FW (with or without the 9-digit number). due to regulatory considerations.Category 1 MT 100 NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. If it is used with option A. the code //RT should appear in the optional Party Identifier of field 56a or 57a. it should appear only once and in the first of the fields 56a and 57a of the payment instruction. it must not be followed by any other information. T29. Field 57a: Account With Institution FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Conditional (C1) DEFINITION This field specifies the financial institution . Option D must only be used when there is a need to be able to specify a name and address. //CP. T45). The code //RT is binding for the Receiver. //IN or //RT is used.when other than the Receiver . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Standards Release Guide 2003 .which services the account for the beneficiary customer.Final edition .

.9n 9!n 7!n 3!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) 12 Standards Release Guide 2003 .MT 100 SWIFTStandards .Final edition .February 2003 .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 6!n 6!n UK Domestic Sort Code South African National Clearing Code CODES with option D: AT AU BL CC CH CP ES FW GR HK IE 5!n 6!n 8!n 9!n 6!n 4!n 8..Category 1 CC ES FW GR HK IE IN IT NZ PT RT SC ZA 9!n 8.

The code //RT is binding for the Receiver.5n 6!n 6!n Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. either connected or non-connected (Error code(s): T27. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS). eg. due to regulatory considerations. //IN or //RT is used. Field 59: Beneficiary Customer FORMAT [/34x] 4*35x (Account) (Name & Address) Standards Release Guide 2003 . 9. If it is used with option A. //AU.. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a.Final edition . //CP. T29. Option A is the preferred option.Category 1 MT 100 IN IT NZ PT RT RU SC SW SW ZA 11!c 10!n 6!n 8!n Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 9!n 6!n 3. USAGE RULES When one of the codes //FW (with or without the 9-digit number). If it is used with option D. Option B is to be used to identify a branch of the Receiver when that branch has neither a BIC or a clearing code or when its clearing code is meaningless for the Receiver.SWIFTStandards . Option D must only be used when there is a need to be able to specify a name and address. the code //RT should appear in the optional Party Identifier of field 56a or 57a. it may be followed by another domestic clearing code. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. T28. T45).February 2003 13 . it must not be followed by any other information. it should appear only once and in the first of the fields 56a and 57a of the payment instruction.

The information specified in this field is intended only for the beneficiary customer. placed between slashes (’/’): INV RFB ROC Invoice (followed by the date.Final edition .MT 100 SWIFTStandards .Category 1 PRESENCE Mandatory DEFINITION This field specifies the beneficiary customer. ie. 10. this information only needs to be conveyed by the Receiver. CODES The following code may be used in Account preceded by a double slash (’//’): CH 6!n CHIPS Universal Identifier USAGE RULES An account number in this field must always designate the account number of the beneficiary customer with its account servicing institution. the Receiver or the party in field 57a.February 2003 . CODES One of the following codes may be used. Reference for the beneficiary customer (followed by up to 16 characters). Field 70: Details of Payment FORMAT 4*35x (Narrative) PRESENCE Optional DEFINITION This field contains transaction details for the beneficiary customer. 14 Standards Release Guide 2003 . Ordering customer’s reference. USAGE RULES For national clearing purposes. reference and details of the invoice). ie. the Sender must check with the Receiver regarding length restrictions of field 70.

11. It must be followed by a reference for the beneficiary of 16 characters maximum. 12. ’//’.Structured Format) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] Standards Release Guide 2003 .February 2003 15 .SWIFTStandards . it must be placed at the beginning of a line. if any. When /RFB/ is used. CODES One of the following codes must be used (Error code(s): T08): BEN OUR Charges are to be borne by the beneficiary customer. Code must not be repeated between two references of the same kind. Charges are to be borne by the Sender. are to be borne by the beneficiary customer. if separated with a double slash. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Optional DEFINITION This field specifies by which party charges are to be borne. This must be the only information on the first line of the field.Category 1 MT 100 Multiple references can be used. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative . USAGE RULES The absence of this field implies that charges.Final edition .

eg. this financial institution. pension payments. Method of Payment BENONLY CHEQUE CORPTRAD HOLD INTRACOM Payment to be made to the beneficiary customer only. CODES 3. The use of an ISO Bank Identifier Code is strongly recommended.Category 1 PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or another party specified. The payment is made in settlement of a trade. pay upon identification. preceded by /RCB/. ie. CODES Codes must be placed between slashes (’/’): 1. Pay only by cheque. a payment between two companies belonging in the same group. Identification instructions may follow. 16 Standards Release Guide 2003 .February 2003 . shall be specified in field 54a and field 72 shall contain the ISO Bank Identifier Code of the Receiver’s branch. Please advise the intermediary by phone. eg. beneficiary customer will call. Please advise/contact beneficiary/claimant by phone. intermediary reimbursement institution. Receiver’s correspondent. Parties: Where it is necessary to identify parties involved in the transaction which have not been identified in other fields: ACC INS Instructions following are for the account with institution.Final edition . securities transaction. RCB CODES 2. ie. The payment is an intra-company payment. Where funds will be made available to the Receiver at its branch through a financial institution other than that indicated in field 53a. foreign exchange deal. A maximum of two lines may be used. The instructing institution (if other than the ordering institution) which instructed the Sender to execute the transaction.MT 100 SWIFTStandards . Method of Advice PHON PHONBEN PHONIBK Please advise account with institution by phone.

in automated systems. Each item for which a code exists must start with that code and may be completed with additional information. must start with a double slash ’//’. it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.Category 1 MT 100 TELE TELEBEN TELEIBK Please advise the account with institution by the most efficient means of telecommunication.February 2003 17 . The codes REJT/RETN may be used in this field. USAGE RULES Field 72 must never be used for information for which another field is intended. because. as specified in the chapter entitled "Euro-Impact on Category 1 Message Standards". This field may include ERI to transport dual currencies. Please advise the intermediary by the most efficient means of telecommunication. Narrative text should preferably be the last information in this field. where bilateral agreements covering the use of codes in this field are in effect. may cause delay. placed between slashes (’/’). the code word EXCH is placed between slashes. and terminated with another slash. In order to comply with the EC-directive on cross border credit transfers. if used. It is strongly recommended to use the standard codes proposed above. which is continued on the next line(s). However. Use of field 72. Please advise the beneficiary/claimant by the most efficient means of telecommunication.Final edition . It may be followed by additional narrative text. If either of the codes is used in the first position of the first line. Standards Release Guide 2003 . Narrative text relating to a preceding code. followed by the exchange rate.SWIFTStandards . and. the code must conform to the structure of this field. In line with ERI. the presence of this field will normally require manual intervention. particularly with uncoded instructions. format 12d. the optional code word EXCH may be used to transport an exchange rate. must begin on a new line. Each code used must be between slashes and appear at the beginning of a line.

ie.Category 1 MT 101 Request for Transfer Note: The use of this message type requires Message User Group (MUG) registration. MT 101 Request for Transfer Status Tag Field Name Content/Options No. Fields which appear in both sequences are mutually exclusive. eg. or in favour of a third party. and is subsequently received by the receiving financial institution and processed by the receiving financial institution or the account servicing financial institution. or from an account(s) owned by the ordering customer which the instructing customer has explicit authority to debit. a subsidiary account. either domestically or internationally. the ordering customer/instructing party.February 2003 .MT 101 SWIFTStandards .Final edition . It is used to move funds from the ordering customer’s account(s) serviced at the receiving financial institution or at the account servicing institution. Mandatory Sequence A General Information M O M O O O O M O 20 21R 28D 50a 50a 52a 51A 30 25 Sender’s Reference Customer Specified Reference Message Index/Total Instructing Party Ordering Customer Account Servicing Institution Sending Institution Requested Execution Date Authorisation 16x 16x 5n/5n C or L G or H A or C [/1!a][/34x] 4!a2!a2!c[3!c] 6!n 35x 1 2 3 4 5 6 7 8 9 18 Standards Release Guide 2003 . The MT 101 can be used to order the movement of funds: between ordering customer accounts. MT 101 Scope This message is sent by a financial institution on behalf of a non-financial institution account owner. each occurrence provides details of one individual transaction. MT 101 Format Specifications The MT 101 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.

C or D A or no option letter 4*35x 3*35x 3!a15d 3!a /34x 12d 13 14 15 16 17 18 19 20 21 22 23 24 25 23E Instruction Code 4!c[/30x] 12 21 21F Transaction Reference F/X Deal Reference 16x 16x 10 11 MT 101 Network Validated Rules C1 Standards Release Guide 2003 .Category 1 MT 101 Status Tag Field Name Content/Options No. -----> Mandatory Repetitive Sequence B Transaction Details M O ----> O ----| M O O O O O M O O O M O O -----| M = Mandatory O = Optional 32B 50a 50a 52a 56a 57a 59a 70 77B 33B 71A 25A 36 Currency/Transaction Amount Instructing Party Ordering Customer Account Servicing Institution Intermediary Account With Institution Beneficiary Remittance Information Regulatory Reporting Currency/Original Ordered Amount Details of Charges Charges Account Exchange Rate 3!a15d C or L G or H A or C A. C or D A.SWIFTStandards .Final edition .February 2003 19 .

February 2003 ... Sequence B if field 36 is. must be present in either sequence A (index 5) or in each occurrence of sequence B (index 15). and vice-versa (Error code(s): D60).. they must be identified for every transaction in field 50a (option G or H) of sequence B.. Sequence A if field 50a (option G or H) is. C2 If an exchange rate is given in field 36.. Present Not present Mandatory Not allowed Sequence B then field 36 is.. Not allowed Mandatory 20 Standards Release Guide 2003 . Sequence B if field 36 is.Final edition .. the original ordered amount in the original currency must be given in field 33B. Present Not present Mandatory Not allowed Sequence B then field 33B is.MT 101 SWIFTStandards . Present Not present Mandatory Optional Sequence B then field 21F is. if multiple debit accounts are used. Consequently. Conversely. Present Not present In every occurrence of sequence B then field 50a (option G or H) is. the corresponding forex deal must be referenced in field 21F (Error code(s): D54)... nor be absent from both sequences (Error code(s): D61). Sequence B if field 33B is... the ordering customer must be identified in field 50a (option G or H) in sequence A.Category 1 If an exchange rate is given in field 36.. but must never be present in both sequences. C3 If there is only one debit account.... field 50a (option G or H)..

:32B:CHF1200.. :32B:CHF1200. may be present in either sequence A (index 4). C7 If field 56a is present..Category 1 MT 101 C4 Field 50a (option C or L).SWIFTStandards .. Sequence A if field 50a (option C or L) is.. :33B:CHF1200. Standards Release Guide 2003 . :33B:USD1000... Sequence A if field 52a is. Not allowed Optional in any occurrence C5 If field 33B is present in sequence B. Invalid :32B:USD1000. If field 56a is...Final edition .00 :33B:USD1000.. but must not be present in both sequences A and B (Error code(s): D62). field 57a must also be present (Error code(s): D65). Present Not present Sequence B then field 50a (option C or L) is..February 2003 21 . :33B:CHF1000. Examples: Valid :32B:USD1000. Present Not present Not allowed Optional Sequence B then field 52a is.. or in one or more occurrences of sequence B (index 14).00 C6 Field 52a may be present in either sequence A or in one or more occurrences of sequence B. Present Mandatory then field 57a is. but must not be present in both sequences (Error code(s): D64). its currency code must be different from the currency code in field 32B in the same occurrence of sequence B (Error code(s): D68)..

Final edition . then fields 21F. the NCD amount. field 36 (due to network validated rule 2) contains the fixed conversion rate between the euro and the National Denomination Currency amounts. Not allowed Optional MT 101 Usage Rules If field 21R is present in sequence A. the transaction amount in field 32B can equal zero. field 21F (due to network validated rule 1) contains the value "NONREF".. C8 If field 21R is present in sequence A. 33B and 36 are. 33B and 36 are not allowed (Error code(s): D99). When the currency of the settlement amount is in euro and it is necessary to indicate the equivalent in National Currency Denomination.MT 101 SWIFTStandards ... topping or zero balancing operations. all messages belonging to the same chain must have exactly the same sender’s reference in field 20. In case of sweeping.. the following guideline applies: field 32B contains the euro amount. the currency code in fields 32B must be the same (Error code(s): D98). equals 0 not equals 0 In the same occurrence of sequence B then fields 21F.. the currency code must be the same for all occurrences of field 32B in sequence B of all chained messages.e. Not present Optional then field 57a is.. to be executed by the receiver. C9 In each occurrence of sequence B. if ’amount’ in field 32B is equal to zero. sequence A must be repeated and be identical for all messages belonging to the same chain. In each occurrence of sequence B if amount in field 32B is . In case field 28D indicates that messages are chained. identified with a code in field 23E.February 2003 .. equivalent to field 32B. and field 28D indicates that more than one message is chained for this request for transfer instruction. In case field 28D indicates that messages are chained.. The complete chain of parties and the transaction flow is illustrated by the following figure: 22 Standards Release Guide 2003 . field 33B contains the currency and value of the instructed amount i.Category 1 If field 56a is. then in each occurrence of sequence B.

The second column specifies the party which assumes the role of the party in the first column.Category 1 MT 101 The parties mentioned in the chain are not necessarily different entities.February 2003 23 .SWIFTStandards . when it is not present: Standards Release Guide 2003 .Final edition . The first column of the table below shows the parties that can be omitted in an MT 101.

Category 1 If the following party is missing. Ordering customer Receiver Account with institution Receiver MT 101 Field Specifications 1. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. etc.Final edition . 2.MT 101 SWIFTStandards .February 2003 . USAGE RULES The reference must be unique for each message (or chain of messages) and is part of the message identification and transaction identification which is to be used in related queries.... Field 21R: Customer Specified Reference FORMAT Option R 16x PRESENCE Optional DEFINITION This field specifies the reference to the entire message assigned by either the: 24 Standards Release Guide 2003 .. cancellations. Instructing party Account servicing institution Intermediary Account with institution Its function is assumed by .

all debit items are posted individually. 3. TESP or TRCO. T28.SWIFTStandards . MCCO. must be a SWIFT registered address. T45. when present or ordering customer. ie. either connected or non-connected (Error code(s): T27. 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. Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BEI) (Party Identifier) PRESENCE Conditional (C4) DEFINITION This field identifies the customer which is authorised by the account owner/account servicing institution to order all the transactions in the message. NETWORK VALIDATED RULES The BEI. USAGE RULES When this field is present.Category 1 MT 101 instructing party. Standards Release Guide 2003 . the ordering customer 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.February 2003 25 . 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. 4. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). when the instructing party is not present. T29. a BIC with subtype BEID. If the field is not used. E57).Final edition .

Field 50a: Ordering Customer FORMAT Option G Option H /34x 4!a2!a2!c[3!c] /34x 4*35x (Account) (BEI) (Account) (Name & Address) PRESENCE Conditional (C3) DEFINITION This field identifies the account owner whose account is to be debited with all transactions in sequence B. T28. This is applicable even if field 50a Ordering Customer contains an IBAN. MCCO. a BIC with subtype BEID. 26 Standards Release Guide 2003 .when other than the Receiver . TESP or TRCO.February 2003 . Field 52a: Account Servicing Institution FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Party Identifier) PRESENCE Conditional (C6) DEFINITION This field specifies the account servicing institution .MT 101 SWIFTStandards . CODES Party Identifier may be used to indicate a national clearing system code. 5. T29. E57).Category 1 USAGE RULES This field must only be used when the instructing customer is not also the account owner. USAGE RULES Both the account number of the ordering customer at the Receiver or at the account servicing institution and the name and address or the BEI of the ordering customer must be present. 6.which services the account of the account owner to be debited. ie. either connected or non-connected (Error code(s): T27. NETWORK VALIDATED RULES The BEI. must be a SWIFT registered address. T45.Final edition .

.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with option C: AT AU BL CC CH CP ES FW GR 5!n 6!n 8!n 9!n 6!n 4!n 8.9n 9!n 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Standards Release Guide 2003 ..February 2003 27 .Final edition .SWIFTStandards .Category 1 MT 101 The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.

. 28 Standards Release Guide 2003 . MCCO. The BIC must not be a BEI. If the account servicing institution cannot be identified by a BIC. Field 51A: Sending Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field identifies the Sender of the message.5n 6!n Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.Final edition . 7. Option A is the preferred option. TESP or TRCO (Error code(s): C05). option C should be used containing a 2!a clearing system code preceded by a double slash ’//’. T29. T45).Category 1 HK IE IN IT PT RU SC SW SW 3!n 6!n 11!n 10!n 8!n 9!n 6!n 3.February 2003 . ie must not be of subtype BEID. USAGE RULES The coded information contained in field 52a should be meaningful to the Receiver of the message. T28.MT 101 SWIFTStandards . either connected or non-connected (Error code(s): T27.

Final edition . NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). cancellations.Category 1 MT 101 NETWORK VALIDATED RULES Field 51A is only valid in IFT (Error code(s): D63). eg. between the ordering customer/instructing party and the account servicing financial institution. a digital signature. 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. etc. USAGE RULES At least the first eight characters of the BIC in this field must be identical to the originator of this IFT message. Field 21: Transaction Reference Standards Release Guide 2003 . The content of field 20 Sender’s Reference together with the content of this field provides the message identification which is to be used in the case of queries. 10. USAGE RULES This is the date on which the ordering customer’s account(s) is (are) to be debited. 8. Field 25: Authorisation FORMAT 35x PRESENCE Optional DEFINITION This field specifies additional security provisions.February 2003 29 .SWIFTStandards . 9.

NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). USAGE RULES In transaction specific queries. Field 21F: F/X Deal Reference FORMAT Option F 16x PRESENCE Conditional (C1.MT 101 SWIFTStandards . the Sender’s reference together with the content of this field provides the transaction identification. C9) DEFINITION This field specifies the foreign exchange contract reference between the ordering customer and the account servicing financial institution. 30 Standards Release Guide 2003 .Final edition .Category 1 FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the unambiguous reference for the individual transaction contained in a particular occurrence of sequence B. CODES The following code may be used: NONREF There is no underlying foreign exchange deal to this transaction NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).February 2003 . cancellations. etc.. 11.

The floor amount. CHQB CMSW CMTO This transaction contains a request that the beneficiary be paid via issuance of a cheque.February 2003 31 . This transaction contains a cash management instruction. requesting to top the account of the ordering customer above a certain floor amount. CMZB CORT INTC NETS PHON REPA RTGS URGP OTHR Standards Release Guide 2003 . eg. This transaction requires the beneficiary to be contacted by telephone and should be followed by the appropriate telephone number. if available. Payment has a related e-Payments reference. securities transaction.Final edition . if available.Category 1 MT 101 12. This transaction contains a cash management instruction. may be specified after the code. CODES One of the following codes must be used (Error code(s): T47). ie. This transaction contains a payment that should be settled via a real time gross settlement system. Used for bilaterally agreed codes/information. requesting to zero balance the account of the ordering customer. requesting to sweep the account of the ordering customer.SWIFTStandards . This transaction contains a cash management instruction. a payment between two companies belonging to the same group. This code is meant for the last financial institution in the chain. foreign exchange deal. This transaction contains a payment that is made in settlement of a trade. if not pre-agreed by the parties involved. This transaction contains an intra-company payment. This transaction contains a time sensitive payment which should be executed in an expeditious manner. Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Instruction Code) (Additional Information) PRESENCE Optional DEFINITION This field specifies instructions for the account servicer of the ordering customer. This transaction contains a payment that should be settled via a net settlement system. The actual bilateral code/information needs to be specified in Additional Information.

February 2003 . PHON.Final edition . In each occurrence of Sequence B: when this field is repeated. CHQB CHQB CHQB CHQB CHQB CHQB CHQB CHQB CHQB CMSW CMSW CMTO CORT CORT CORT CORT NETS with with with with with with with with with with with with with with with with with CMSW CMTO CMZB CORT NETS PHON REPA RTGS URGP CMTO CMZB CMZB CMSW CMTO CMZB REPA RTGS For example: Valid :23E:URGP :23E:CORT Invalid :23E:CHQB :23E:URGP 32 Standards Release Guide 2003 . OTHR and REPA (Error code(s): D66). the following combinations are not allowed (Error code(s): D67). 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).Category 1 NETWORK VALIDATED RULES Additional Information is only allowed when Instruction Code consists of one of the following codes: CMTO.MT 101 SWIFTStandards . In each occurrence of sequence B: when this field is used more than once.

SWIFTStandards . REPA. The integer part of Amount must contain at least one digit. RTGS) codes containing instructions for one of the following parties in the transaction chain (CHQB. This code is intended for the beneficiary’s bank who should act according to the specifications of the e-payments product. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. A decimal comma is mandatory and is included in the maximum length. the codes must appear in the following order: instructions for the receiver of the message (CMSW.February 2003 33 . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). Field 32B: Currency/Transaction Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and the amount of the subsequent transfer to be executed by the Receiver. T40.Final edition . USAGE RULES The amount is subject to deduction of the Receiver’s/beneficiary bank’s charges if field 71A is BEN or SHA. CMZB. PHON) information codes (OTHR) 13. To facilitate the receiving bank’s processing when multiple codes are used. INTC. URGP) codes impacting the routing or composition of the resulting payment message (NETS. Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BEI) (Party Identifier) Standards Release Guide 2003 .Category 1 MT 101 :23E:NETS :23E:RTGS USAGE RULES Code REPA indicates that the payment is the result of an initiation performed via an e-payments product between the customers. CORT. CMTO. T43). 14.

E57). ie. NETWORK VALIDATED RULES The BEI. T28. T28. T29.MT 101 SWIFTStandards . Field 52a: Account Servicing Institution FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Party Identifier) 34 Standards Release Guide 2003 . ie. T45. Field 50a: Ordering Customer FORMAT Option G Option H /34x 4!a2!a2!c[3!c] /34x 4*35x (Account) (BEI) (Account) (Name & Address) PRESENCE Conditional (C3) DEFINITION This field specifies the ordering customer which is the account owner ordering the transaction in the same occurrence of the sequence.February 2003 .Category 1 PRESENCE Conditional (C4) DEFINITION This field identifies the customer which is authorised by the account owner/account servicing institution to order the transactions in this particular occurrence of sequence B. T45. either connected or non-connected (Error code(s): T27. must be a SWIFT registered address. USAGE RULES This field must only be used when the instructing customer is not also the account owner. either connected or non-connected (Error code(s): T27. TESP or TRCO. MCCO. USAGE RULES Both the account number of the ordering customer at the Receiver or at the account servicing institution and the name and address or BEI of the ordering customer must be present. NETWORK VALIDATED RULES The BEI. TESP or TRCO. T29. a BIC with subtype BEID. must be a SWIFT registered address. 16. a BIC with subtype BEID. E57). MCCO. 15.Final edition .

This is applicable even if field 50a Ordering Customer contains an IBAN..SWIFTStandards .Final edition .Category 1 MT 101 PRESENCE Conditional (C6) DEFINITION This field specifies the account servicing institution . CODES Party Identifier may be used to indicate a national clearing system code.when other than the Receiver .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with option C: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Standards Release Guide 2003 .February 2003 35 . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.which services the account of the account owner to be debited.

9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3.5n 6!n Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. Option A is the preferred option.Final edition .February 2003 . T29. ie. TESP or TRCO (Error code(s): C05). If the account servicing institution cannot be identified by a BIC. T28. MCCO. option C should be used containing a 2!a clearing system code preceded by a double slash ’//’.. either connected or non-connected (Error code(s): T27. must not be of subtype BEID.Category 1 CC CH CP ES FW GR HK IE IN IT PT RU SC SW SW 9!n 6!n 4!n 8.. The BIC must not be a BEI. Field 56a: Intermediary FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) 36 Standards Release Guide 2003 . USAGE RULES The coded information contained in field 52a should be meaningful to the Receiver of the message. 17. T45).MT 101 SWIFTStandards .

through which the transaction must pass. CODES Party Identifier may be used to indicate a national clearing system code.February 2003 37 .SWIFTStandards .Final edition .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code Standards Release Guide 2003 . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT NZ PT SC 5!n 6!n 8!n 9!n 8.Category 1 MT 101 PRESENCE Optional DEFINITION This field specifies the financial institution between the Receiver and the account with institution..

Option A is the preferred option. must not be of subtype BEID. T29. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. 38 Standards Release Guide 2003 . T45). it should appear only once and in the first of the fields 56a and 57a of the payment instruction.5n 6!n German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. T28.. MCCO.Final edition . //CP or //IN is used.. TESP or TRCO (Error code(s): C05). ie. USAGE RULES The intermediary may be a branch or affiliate of the Receiver or the account with institution. either connected or non-connected (Error code(s): T27. The BIC must not be a BEI. //AU. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a.9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n 9!n 6!n 3. When one of the codes //FW (with or without the 9-digit number).MT 101 SWIFTStandards .February 2003 .Category 1 BL CC CH CP ES FW GR HK IE IN IT NZ PT RU SC SW SW 8!n 9!n 6!n 4!n 8. or an entirely different financial institution.

DEFINITION This field specifies the financial institution .Final edition . option C should be used containing a 2!a clearing system code preceded by a double slash ’//’.when other than the Receiver .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Standards Release Guide 2003 . due to regulatory considerations. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT 5!n 6!n 8!n 9!n 8. Field 57a: Account With Institution FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) PRESENCE Conditional (C7).. eg. This is applicable even if field 59 contains an IBAN.Category 1 MT 101 If the intermediary cannot be identified by a BIC. Option D must only be used when there is a need to be able to specify a name and address. 18.February 2003 39 .which services the account for the beneficiary customer.SWIFTStandards . CODES Party Identifier may be used to indicate a national clearing system code.

Category 1 NZ PT SC 6!n 8!n 6!n New Zealand National Clearing Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU BL CC CH CP ES FW GR HK IE IN IT NZ PT RU SC SW SW 5!n 6!n 8!n 9!n 6!n 4!n 8.February 2003 .9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n 9!n 6!n 3.5n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) 40 Standards Release Guide 2003 .Final edition ..MT 101 SWIFTStandards ..

must not be of subtype BEID. USAGE RULES At least the name or BIC/BEI of the beneficiary customer is mandatory.Final edition . T28. due to regulatory considerations. it should appear only once and in the first of the fields 56a and 57a of the payment instruction. USAGE RULES When one of the codes //FW (with or without the 9-digit number). 20. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a. T45). T28. //AU.February 2003 41 . option C should be used containing a 2!a clearing system code preceded by a double slash ’//’.SWIFTStandards . Option D must only be used when there is a need to be able to specify a name and address. T45). When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. eg. MCCO. ie. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. //CP or //IN is used. 19. either connected or non-connected (Error code(s): T27. TESP or TRCO (Error code(s): C05). The BIC must not be a BEI. If the account with institution cannot be identified by a BIC.Category 1 MT 101 NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. Option A is the preferred option. T29. Field 59a: Beneficiary FORMAT Option A No option letter [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field identifies the beneficiary of the subsequent operation from the particular occurrence of sequence B. either connected or non-connected (Error code(s): T27. Field 70: Remittance Information FORMAT 4*35x (Narrative) Standards Release Guide 2003 . T29.

MT 101 SWIFTStandards .Category 1 PRESENCE Optional DEFINITION This field specifies details of the individual transactions which are to be transmitted to the beneficiary customer. the Sender must check with the Receiver regarding length restrictions of field 70. this information only needs to be conveyed by the Receiver. Multiple references can be used. USAGE RULES For national clearing purposes. 42 Standards Release Guide 2003 . Unique reference identifying a related International Payment Instruction (followed by up to 20 characters). placed between slashes: INV IPI RFB ROC Invoice (followed by the date. 21. ie. The information specified in this field is intended only for the beneficiary customer. Ordering customer’s reference. reference and details of the invoice). Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Optional DEFINITION This field specifies code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver or the Sender/originating customer.Final edition . CODES One of the following codes may be used. if separated with a double slash. ’//’. Reference for the beneficiary customer (followed by up to 16 characters). Code must not be repeated between two references of the same kind.February 2003 .

A decimal comma is mandatory and is included in the maximum length. placed between slashes (’/’): ORDERRES BENEFRES Residence of ordering customer Residence of beneficiary customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer.February 2003 43 .SWIFTStandards .Final edition . The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). Field 33B: Currency/Original Ordered Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Conditional (C2. 22. Field 71A: Details of Charges FORMAT Option A 3!a (Code) Standards Release Guide 2003 . 23. C9) DEFINITION This field specifies the original currency and amount as specified by the ordering customer. USAGE RULES This field is used when the currency and amount are different from those specified in field 32B. the following codes may be used. The information specified must not have been explicitly conveyed in another field. T43). T40. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.Category 1 MT 101 CODES When the residence of either the ordering customer or beneficiary customer is to be identified.

103. USAGE RULES When used. Field 25A: Charges Account FORMAT Option A /34x (Account) PRESENCE Optional DEFINITION This field specifies the ordering customer’s account number to which applicable transaction charges should be separately applied. 24. 25. MTs 100.Category 1 PRESENCE Mandatory DEFINITION This field specifies which party will bear the applicable charges for the subsequent transfer of funds. Field 36: Exchange Rate FORMAT 12d (Rate) 44 Standards Release Guide 2003 . for the subsequent credit transfer(s) are to be borne by the beneficiary customer. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges. the account number must be different from the account number specified in field 50a Ordering Customer.Final edition . All transaction charges other than the charges of the financial institution servicing the ordering customer account are borne by the beneficiary customer.February 2003 . including the charges of the financial institution servicing the ordering customer’s account. 102. USAGE RULES These charge codes cover potential charges associated with the sending of subsequent MTs 102.MT 101 SWIFTStandards . Charges for sending the MT 101 should be handled outside of this message type. All transaction charges for the subsequent credit transfer are to be borne by the ordering customer.

February 2003 45 . T43). NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit.Category 1 MT 101 PRESENCE Conditional (C2. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. C9) DEFINITION This field specifies the exchange rate applied by the ordering customer/instructing party when converting the original ordered amount to the transaction amount. Standards Release Guide 2003 .Final edition .SWIFTStandards .

these bilateral agreements cover the transaction amount limits. This message is used to convey multiple payment instructions between financial institutions for clean payments. It requests the Receiver to credit the beneficiary customer(s) directly or through a domestic clearing mechanism via another financial institution in the receiving country. or to issue a cheque to the beneficiary.Final edition . Sequence C Settlement Details is a single occurrence sequence and contains information about the settlement. Its use is subject to bilateral/multilateral agreements between Sender and Receiver. Each occurrence is used to provide details of one individual transaction. Amongst other things. MT 102 Format Specifications The MT 102 consists of three sequences: Sequence A General Information is a single occurrence sequence and contains information which applies to all individual transactions described in sequence B. Sequence B Transaction Details is a repetitive sequence. The MT 102+ is a compatible subset of the core MT 102 and is documented separately after the MT 102. MT 102 Multiple Customer Credit Transfer Status Tag Field Name Content/Options No.MT 102 SWIFTStandards .Category 1 MT 102 Multiple Customer Credit Transfer Note: The use of this message type requires Message User Group (MUG) registration. The multiple payments checklist included below is recommended as a guide for institutions in the setup of their agreements. MT 102 Scope This message is sent by or on behalf of the financial institution of the ordering customer(s) to a financial institution in the country of the beneficiary customer(s). B or C 3!c 3*35x 1 2 3 4 5 6 7 46 Standards Release Guide 2003 . the currencies accepted and their settlement. Mandatory Sequence A General Information M M O O O O O 20 23 51A 50a 52a 26T 77B File Reference Bank Operation Code Sending Institution Ordering Customer Ordering Institution Transaction Type Code Regulatory Reporting 16x 16x [/1!a][/34x] 4!a2!a2!c[3!c] A or K A.February 2003 .

Category 1 MT 102 Status O O Tag 71A 36 Details of Charges Exchange Rate Field Name 3!a 12d Content/Options No.Final edition . B or C A or C A or no option letter 4*35x 3!c 3*35x 3!a15d 3!a 10 11 12 13 14 15 16 17 18 19 20 -----| Mandatory Sequence C Settlement Details M O O -----> O 13C Time Indication /8c/4!n1!x4!n 27 32A 19 71G Value Date. Amount Sum of Amounts Sum of Receiver’s Charges 6!n3!a15d 17d 3!a15d 24 25 26 Standards Release Guide 2003 .February 2003 47 . 8 9 -----> Mandatory Repetitive Sequence B Transaction Details M M O O O M O O O O O -----> O -----| O O 71G 36 Receiver’s Charges Exchange Rate 3!a15d 12d 22 23 71F Sender’s Charges 3!a15d 21 21 32B 50a 52a 57a 59a 70 26T 77B 33B 71A Transaction Reference Transaction Amount Ordering Customer Ordering Institution Account With Institution Beneficiary Customer Remittance Information Transaction Type Code Regulatory Reporting Currency/Instructed Amount Details of Charges 16x 3!a15d A or K A.SWIFTStandards . Currency Code.

If 50a in sequence A is. Sequence A if field 71A is. but it must never be present in both sequences. Not allowed Mandatory 48 Standards Release Guide 2003 .. it must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01) C2 The currency code in the fields 71G. but it must never be present in both sequences. nor be absent from both sequences (Error code(s): D20).. Present Not present In each occurrence of sequence B then field 71A is. 32B and 32A must be the same for all occurrences of these fields in the message (Error code(s): C02).. nor be absent from both sequences (Error code(s): D17).. C3 Field 50a must be present either in sequence A or in each occurrence of sequence B. Present Not present then 50a in each sequence B is ...Category 1 Status -----| O O O Tag Field Name Content/Options No. Not allowed Mandatory C4 Field 71A must be present either in sequence A or in each occurrence of sequence B. 53a 54A 72 Sender’s Correspondent Receiver’s Correspondent Sender to Receiver Information M = Mandatory O = Optional A or C [/1!a][/34x] 4!a2!a2!c[3!c] 6*35x 28 29 30 MT 102 Network Validated Rules C1 If field 19 is present in sequence C.February 2003 .Final edition ...MT 102 SWIFTStandards .

Sequence A if field 52a is ... Not allowed Optional Sequence A if field 26T is . Not allowed Optional Sequence A if field 77B is . When a field 36 (sequence A or sequence B) is required. Present Not present In each occurrence of sequence B then field 26T is .Final edition . 26T or 77B is present in any occurrence of sequence B. 26T or 77B is present in sequence A. Present Not present In each occurrence of sequence B then field 77B is .. that field must not be present in sequence A (Error code(s): D18).SWIFTStandards . Sequence A If field 36 is present Sequence B Then in minimum one occurrence of Seq. in all other cases field 36 is not allowed in the message. Not allowed Optional C6 Field 36 (sequence A or sequence B) must be present in the message if there is any sequence B which contains a field 33B with a currency code different from the currency code in field 32B... When a field 52a. EITHER field 36 must be present in sequence A and not in any sequence B.February 2003 49 ...... B field 33B must be present and currency codes in fields 32B and 33B must be different And field 36 is not allowed in any occurrence of Seq. that field must not be present in any occurrence of sequence B. Present Not present In each occurrence of sequence B then field 52a is .Category 1 MT 102 C5 If a field 52a. OR it must be present in every sequence B which contains fields 32B and 33B with different currency codes and must not be present in sequence A or any other sequence B (Error code(s): D22).. B Standards Release Guide 2003 ..

BV. In all other cases. PT.Final edition ..Category 1 Sequence A If field 36 is . MQ. PM.. Examples: Valid :23:CHQB(CrLf) :59:xxxxx(CrLf) :23:CREDIT(CrLf) :59:/xxxxx(CrLf) xxxxx(CrLf) :23:CRTST(CrLf) :59:/xxxxx(CrLf) xxxxx(CrLf) Invalid :23:CHQB(CrLf) :59:/xxxxx(CrLf) xxxxx(CrLf) :23:CREDIT(CrLf) :59:xxxxx(CrLf) xxxxx(CrLf) :23:CRTST(CrLf) :59:xxxxx(CrLf) xxxxx(CrLf) C8 If the country codes of the Sender’s and the Receiver’s BICs are within the following list: AD. RE. IE. BE. MC.. DK.. SE. 50 Standards Release Guide 2003 . TF and VA. GF. SJ. IT. GB. NL. Not present Present C7 If field 23 contains the code CHQB. the Account Number must not be present in field 59a. FR. CH. otherwise field 33B is optional (Error code(s): D49). In each occurrence of Sequence B And currency codes in fields 32B and 33B are . LI.. GI. Equal Not equal Not present n/a Not allowed Mandatory Not allowed Then field 36 is .February 2003 .MT 102 SWIFTStandards .. LU. FI. If 23 contains. it is mandatory (Error code(s): D93).. CHQB Other Forbidden Mandatory A/N line of 59a.... IS. If field 33B is . GP. NO. GR. then field 33B is mandatory in each occurrence of sequence B.. ES. DE. AT.. SM.

. If field 71A in sequence B contains OUR. then fields 71F are optional and field 71G is not allowed in any occurrence of sequence B (Error code(s): D50)...Final edition . In the same occurrence of sequence B then field(s) 71F is (are)..... Mandatory Optional Optional Optional Note: See Rule C10 C9 If field 71A in sequence A contains OUR.. Note: See rules C4 and C9 (rule C4 takes precedence over rule C9) If field 71A in sequence A contains SHA.February 2003 51 . OUR Not allowed Optional and field 71G is.. In each occurrence of sequence B then field(s) 71F is (are). Standards Release Guide 2003 . In sequence B if field 71A is. In sequence A if field 71A is..Category 1 MT 102 If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No In each occurrence of Seq. then field 71F is not allowed and field 71G is optional in the same occurrence of sequence B (Error code(s): E13).. OUR Not allowed Optional and field 71G is.. B then field 33B is .SWIFTStandards . then field 71F is not allowed and field 71G is optional in any occurrence of sequence B (Error code(s): E13)...

. If field 71A in sequence B contains BEN..Final edition . In sequence A if field 71A is... In the same occurrence of sequence B then field(s) 71F is (are).. BEN Mandatory Not allowed and field 71G is. SHA Optional Not allowed and field 71G is. BEN Mandatory Not allowed and field 71G is... In the same occurrence of sequence B then field(s) 71F is (are). then at least one occurrence of field 71F is mandatory in each occurrence of sequence B and field 71G is not allowed (Error code(s): E15).... In each occurrence of sequence B then field(s) 71F is (are).Category 1 In sequence A if field 71A is. Note: See rules C4 and C9 (rule C4 takes precedence over rule C9) 52 Standards Release Guide 2003 ...MT 102 SWIFTStandards . Not allowed SHA Optional If field 71A in sequence B contains SHA... In each occurrence of sequence B then field(s) 71F is (are).. Note: See rules C4 and C9 (rule C4 takes precedence over rule C9) If field 71A in sequence A contains BEN..... then at least one occurrence of field 71F is mandatory in the same occurrence of sequence B and field 71G is not allowed (Error code(s): E15). In sequence B if field 71A is..February 2003 . then fields 71F are optional and field 71G is not allowed in the same occurrence of sequence B (Error code(s): D50). In sequence B if field 71A is.... and field 71G is..

.. 19 and 32A which may be logically expressed in the following formulas: For each occurrence of sequence B. Present Present Not present Not present and field 71G is. The sum of all Receiver’s charges in fields 71G of sequence B.. When sending the MT 102 via IFT. see rule C9. equals the total Receiver’s charges of field 71G in sequence C. If in any occurrence of sequence B field 71G is. MT 102 Usage Rules If a registered user receives an MT 102 without bilateral agreement with the Sender.. Present Not present Present Not present then field 33B is. then field 71G is mandatory in the sequence C (Error code(s): D79). minus the Sender’s charges in field(s) 71F. adjusted with the exchange rate in field 36..Final edition . 71F... the instructed amount in field 33B. Usage Rules for Amount Related Fields There is a relationship between the amount related fields 33B. In each occurrence of sequence B If field 71F is. 32B.February 2003 53 . 71G.. Standards Release Guide 2003 . equals the transaction amount in field 32B. then field 33B is mandatory in the same occurrence of sequence B (Error code(s): D51). C11 If field 71G is present in an occurrence of sequence B.. Rejected (*) Mandatory Mandatory Optional (*) both fields 71F and 71G present is not a valid combination.SWIFTStandards . Present Mandatory in sequence C then field 71G is.Category 1 MT 102 C10 If either field 71F (at least one occurrence) or field 71G are present in an occurrence of sequence B.. the Receiver should query the message according to normal banking practice. equals the total amount in field 19. The sum of all transaction amounts in fields 32B. 36. institutions must use the payment-related profile.

.1) Beneficiary bank’s (receiving bank’s) transaction charge is GBP 4 (=EUR 6. all occurrences of that field must be taken into account in the formula... plus the total Receiver’s charges in field 71G of sequence C. OUR Sequence B then field 32B is.. Sum of fields 71G of sequences B Not allowed Not allowed Examples Transaction A: Pay the equivalent of EUR1000. Receiver will deduct its own charges. Charges have been prepaid by the ordering customer.February 2003 .00 in GBP to a beneficiary in the United Kingdom The exchange rate is 1 EUR for 0.MT 102 SWIFTStandards . If a field is not present.. SHA Optional Not allowed BEN At least one occurrence mandatory Not allowed Sequence A If field 71A is.... Amount as instructed by the originator... equals the interbank settled amount in field 32A. OUR SHA BEN Sequence C then field 19 is. C6. C10 and C11. If field 71F is present more than once.45) 54 Standards Release Guide 2003 .. Not allowed Optional and field 71G is. C8. that field must not be taken into account in the formula. field 71F is. Receiver will deduct its charges.. Settlement Amount equals field 19 plus field 71G of sequence C Settlement Amount equals Sum of field(s) 32B of sequence B Settlement Amount equals Sum of field(s) 32B of sequence B and field 71G is. Sequence A If field 71A is..Category 1 The total amount in field 19 (or the sum of all transaction amounts in fields 32B). Presence of the fields mentioned above is subject to the conditional field rules C5... Sum of field(s) 32B of sequence B Not used Not used field 32A is. eg.. Net amount to be credited to the Beneficiary. after sending bank has deducted its charges. C9.Final edition .61999 GBP Ordering bank’s (sending bank’s) transaction charge is EUR 5 (=GBP 3. invoice amount. Amount as instructed by the originator.

ie.00 5.99.February 2003 55 .00 Standards Release Guide 2003 . field 32A.99 4.99 1000.99 623.45 1011.00 6.00 OUR 4.00 1005.99 Example A2: Charging option is SHA a) Amount debited from the ordering customer’s account: Original ordered amount + Sender’s charges = Debit amount EUR EUR EUR 1000.Category 1 MT 102 Example A1: Charging option is OUR a) Amount debited from the ordering customer’s account Original ordered amount + Sender’s charges + Receiver’s charges = Debit amount EUR EUR EUR EUR 1000.00 0.Final edition .00 5.SWIFTStandards . sequence C.61999 619. d) Amount credited to the beneficiary: Credit Amount GBP 619.00 c) The subsequent MT 950 shows one debit entry for GBP 623.45 b) MT 102 extract: Field Tag Sequence B 32B 33B 71A 71G 36 Sequence C 19 32A 71G GBP GBP GBP GBP GBP EUR Content 619.

61999 619.99 c) The subsequent MT 950 shows one debit entry for GBP 619.Receiver’s charges = Credit Amount GBP GBP GBP 619.MT 102 SWIFTStandards .Category 1 b) MT 102 extract: Field Tag Sequence B 32B 33B 71A 36 Sequence C 32A GBP GBP EUR Content 619. ie.00 BEN 3.99 Example A3: Charging option is BEN a) Amount debited to the ordering customer’s account: Original ordered amount = Debit amount EUR 1000.00 b) MT 102 extract: Field Tag Sequence B 32B 33B 71A 71F 36 Sequence C 32A GBP GBP GBP EUR Content 616.89 1000. d) Amount credited to the beneficiary: Interbank Settlement Amount . sequence C.99 4.89 56 Standards Release Guide 2003 .February 2003 .99 1000. field 32A.00 615.61999 616.Final edition .00 SHA 0.10 0.99.

SWIFTStandards .10 4. d) Amount credited to the beneficiary: Equivalent of ordered amount .93 5.00 to a beneficiary in the United Kingdom The exchange rate is 1 EUR for 0. ie.Sender’s charges .45 1624.61999 GBP Ordering bank’s (sending bank’s) transaction charge is EUR 5 (=GBP 3.Final edition .00 Standards Release Guide 2003 . field 32A.February 2003 57 .89 Examples Transaction B Pay GBP 1000.89.Category 1 MT 102 c) The subsequent MT 950 shows one debit entry for GBP 616.00 6.00 612.38 b) MT 102 extract Field Tag Sequence B 32B 33B 71A 71G GBP GBP GBP Content 1000.00 1000. sequence C.00 OUR 4.Receiver’s charges = Credit amount GBP GBP GBP GBP 619.1) Beneficiary bank’s (receiving bank’s) transaction charge is GBP 4 (=EUR 6.99 3.45) The ordering customer has an account in euro Sender and Receiver’s BIC are within the EU-country list Example B1: Charging option is OUR a) Amount debited to the ordering customer’s account: Debit on EUR account Equivalent of ordered amount + Sender’s charges + Receiver’s charges = Debit amount EUR EUR EUR EUR 1612.

ie. field 32A.00 1000. field 32A.00 1617.Final edition . sequence C.93 5.00 Note: field 36 does not have to be used since currency in fields 32A and 33B is the same c) The subsequent MT 950 shows one debit entry for GBP1004.MT 102 SWIFTStandards .00 Example B2: Charging option is SHA a) Amount debited to the ordering customer’s account: Debit on EUR-account Equivalent of ordered amount + Sender’s charges = Debit amount EUR EUR EUR 1612.00 SHA 1000.Category 1 Field Tag Sequence C 19 32A 71G GBP GBP GBP Content 1000.00.00 4. sequence C.93 b) MT 102 extract: Field Tag Sequence B 32B 33B 71A Sequence C 32A GBP GBP GBP Content 1000.February 2003 .00 1004.00. 58 Standards Release Guide 2003 . d) Amount credited to the beneficiary: Original ordered amount = Credit amount GBP 1000.00 c) The subsequent MT 950 shows one debit entry for GBP 1000. ie.

c) The subsequent MT 950 shows one debit entry for GBP 996.00 Example B3: Charging option is BEN a) Amount debited to the ordering customer’s account: Debit on: Equivalent of ordered amount = Debit amount EUR account EUR 1612.Category 1 MT 102 d) Amount credited to the beneficiary: Amount in 32A .Receiver’s charges = Credit amount GBP GBP GBP 1000.00 992.February 2003 59 .00 BEN 3.10 996.90 Note: field 36 does not have to be used since currency in fields 32A and 33B is the same. sequence C.Sender’s charges .00 996.90 1000.93 b) MT 102 extract: Field Tag Sequence B 32B 33B 71A 71F Sequence C 32A GBP GBP GBP GBP Content 996.90.SWIFTStandards .90 Standards Release Guide 2003 .Receiver’s charges = Credit amount GBP GBP GBP GBP 1000.10 4.00 4. ie.00 3.Final edition . field 32A. d) Amount credited to the beneficiary: Original ordered amount .

The file reference must be unique for each file and is part of the file identification and transaction identification which is used in case of queries. Field 23: Bank Operation Code FORMAT 16x To be formatted as 6a. USAGE RULES This reference must be quoted in any related confirmation or statement. PRESENCE Mandatory DEFINITION This field identifies the type of operation.MT 102 SWIFTStandards . 2. CODES One of the following codes.10 MT 102 Field Specifications 1. 60 Standards Release Guide 2003 . Field 20: File Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.February 2003 .Final edition . or bilaterally agreed codes may be used: CHQB This message contains transactions requesting that the beneficiary be paid via issuance of a cheque. MT 900 Confirmation of Debit and/or 950 Statement Message. cancellations etc.Category 1 Note: The beneficiary is also advised of the Sender’s charges of GBP 3. eg. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).

This message contains credit transfers for test purpose(s). together with the content of this field provides the message identification which is to be used in case of file related queries. 3. the code CRTST is only valid when sent by a Test & Training destination.Final edition .SWIFTStandards . In IFT.Category 1 MT 102 CREDIT CRTST SPAY This message contains credit transfer(s) to be processed according to the pre-established bilateral agreement between the Sender and the Receiver. USAGE RULES The content of field 20. File Reference. This message contains credit transfer(s) to be processed according to the SWIFTPay Service Level.February 2003 61 . at least the first eight characters of the BIC in this field must be identical to the originator of the IFT message. cancellations etc. NETWORK VALIDATED RULES Field 51A is only valid in IFT (Error code(s): D63). Field 50a: Ordering Customer FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) Standards Release Guide 2003 . Field 51A: Sending Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field identifies the Sender of the message. 4. USAGE RULES As tests in FIN should be done in Test & Training.

USAGE RULES If the account number of the ordering customer is present.. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. T29. when different from the Sender. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW 5!n 6!n 8!n 9!n 8. which instructed the Sender to transmit all transactions described in sequence B. it must be stated in Account. T45). 5.MT 102 SWIFTStandards . T28.9n without 9 digit code Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire 62 Standards Release Guide 2003 . either connected or non-connected (Error code(s): T27.Category 1 PRESENCE Conditional (C3) DEFINITION This field identifies the customer ordering all transactions described in sequence B. Field 52a: Ordering Institution FORMAT Option A Option B Option C [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] /34x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) PRESENCE Conditional (C5) DEFINITION This field specifies the financial institution. CODES Party Identifier may be used to indicate a national clearing system code.Final edition .February 2003 . This is applicable even if field(s) 50a contain(s) an IBAN.

5n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Standards Release Guide 2003 .SWIFTStandards .9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3..Category 1 MT 102 GR HK IE IN IT PT SC 7!n 3!n 6!n 11!c 10!n 8!n 6!n HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with option C: AT AU BL CC CH CP ES FW GR HK IE IN IT PT RU SC SW 5!n 6!n 8!n 9!n 6!n 4!n 8.Final edition ..February 2003 63 .

either connected or non-connected (Error code(s): T27. T29. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. USAGE RULES Option A is the preferred option.Category 1 SW 6!n Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.February 2003 . purpose of and/or reason for all transactions described in sequence B. Option B is to be used to identify a branch of the Sender when that branch has neither a BIC nor a clearing system code or when its clearing system code is meaningless for the Receiver.MT 102 SWIFTStandards . 6. pensions or dividends. 7. Field 26T: Transaction Type Code FORMAT Option T 3!c PRESENCE Conditional (C5) DEFINITION This field identifies the nature of. MCCO. eg. salaries. The BIC must not be a BEI. If the ordering institution cannot be identified by a BIC. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) 64 Standards Release Guide 2003 .Final edition . T28. CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. option C should be used containing a 2!a clearing system code preceded by a double slash (’//’). TESP or TRCO (Error code(s): C05). T45). ie must not be of subtype BEID.

All transaction charges are to be borne by the ordering customer.Final edition . Standards Release Guide 2003 . placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. The information specified must not have been explicitly conveyed in another field and is valid for all transactions described in sequence B. the following codes may be used.SWIFTStandards . 8.Category 1 MT 102 PRESENCE Conditional (C5) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver or Sender. Transaction charges on the Sender’s side are to be borne by the ordering customer and transaction charges on the Receiver’s side are to be borne by the beneficiary customer.February 2003 65 . CODES When the residence of either the ordering customer or the beneficiary customer is to be identified. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the beneficiary customer. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C4) DEFINITION This field specifies which party will bear the charges for all transactions described in sequence B.

USAGE RULES In transaction related queries. 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. Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C6) DEFINITION This field specifies the exchange rate used to convert all instructed amounts specified in field 33B in sequence B. 10. T43). NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). 11. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. cancellations etc.MT 102 SWIFTStandards .Category 1 9. when a currency conversion has been performed on the Sender’s side.Final edition . Field 32B: Transaction Amount 66 Standards Release Guide 2003 . NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit.. USAGE RULES This field must be present.February 2003 . the content of field 20 File Reference together with the content of this field provides the transaction identification.

USAGE RULES This amount will. and from which amount the Receiver will deduct its charges. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 12. If field 71A is SHA. as charges have been prepaid by the ordering customer. T43). Depending on the charging option specified in field 71A. taking into account the charging option. The integer part of Amount must contain at least one digit. Standards Release Guide 2003 .February 2003 67 . eg. the net amount to be credited to the beneficiary. T40. be the basis for the Receiver to calculate the amount to be credited to the beneficiary.Category 1 MT 102 FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the individual transaction amount remitted by the Sender to the Receiver. invoice amount. If field 71A is BEN. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). the content of field 32B is as follows: If field 71A is OUR. the amount as instructed by the originator minus the Senders’ charges.Final edition . the amount as instructed by the originator. A decimal comma is mandatory and is included in the maximum length. of which the Receiver will deduct its own charges. Field 50a: Ordering Customer FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C3) DEFINITION This field specifies the customer ordering the transaction.SWIFTStandards .

T45). which instructed the Sender to transmit the transaction. This is applicable even if field(s) 50a contain(s) an IBAN.. 13.Category 1 NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address.February 2003 . it must be stated in Account.Final edition . T29.9n without 9 digit code 7!n 3!n 6!n 11!c Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) 68 Standards Release Guide 2003 . T28. CODES Party Identifier may be used to indicate a national clearing system code. either connected or non-connected (Error code(s): T27. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN 5!n 6!n 8!n 9!n 8. Field 52a: Ordering Institution FORMAT Option A Option B Option C [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] /34x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) PRESENCE Conditional (C5) DEFINITION This field specifies the financial institution. USAGE RULES If the account number of the ordering customer is present.MT 102 SWIFTStandards . when other than the Sender.

Final edition ..5n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) Standards Release Guide 2003 .Category 1 MT 102 IT PT SC 10!n 8!n 6!n Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with option C: AT AU BL CC CH CP ES FW GR HK IE IN IT PT RU SC SW SW 5!n 6!n 8!n 9!n 6!n 4!n 8.9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3.February 2003 69 .SWIFTStandards ..

either connected or non-connected (Error code(s): T27..which services the account for the beneficiary customer identified in the same sequence. ie must not be of subtype BEID. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR 5!n 6!n 8!n 9!n 8.MT 102 SWIFTStandards . 14.February 2003 . This is applicable even if field 59 or 59A contains an IBAN. T45). The BIC must not be a BEI.Category 1 NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.9n without 9 digit code 7!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) 70 Standards Release Guide 2003 .Final edition . Field 57a: Account With Institution FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Party Identifier) PRESENCE Optional DEFINITION This field specifies the financial institution . T28. option C should be used containing a 2!a clearing system code preceded by a double slash ’//’. USAGE RULES Option A is the preferred option. T29. CODES Party Identifier may be used to indicate a national clearing system code. TESP or TRCO (Error code(s): C05). MCCO.when other than the Receiver . Option B is to be used to identify a branch of the Sender when that branch has neither a BIC nor a clearing system code or when its clearing system code is meaningless for the Receiver. If the ordering institution cannot be identified by a BIC.

SWIFTStandards .9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl CHIPS Universal Identifier Canadian Payments Association Payment Routing Number CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Standards Release Guide 2003 .Final edition ..February 2003 71 .Category 1 MT 102 HK IE IN IT NZ PT RT SC ZA 3!n 6!n 11!c 10!n 6!n 8!n Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 6!n 6!n UK Domestic Sort Code South African National Clearing Code CODES with option C: AT AU BL CH CC CP ES FW GR HK IE IN IT NZ PT 5!n 6!n 8!n 6!n 9!n 4!n 8.

it may be followed by another domestic clearing code. either connected or non-connected (Error code(s): T27. The code //RT is binding for the Receiver. Option A is the preferred option. TESP or TRCO (Error code(s): C05). option C should be used containing a 2!a clearing system code preceded by a double slash ’//’. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS).MT 102 SWIFTStandards . Field 59a: Beneficiary Customer FORMAT Option A No option letter [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the customer to which the transaction amount should be transmitted. ie must not be of subtype BEID. T45). the code //RT should appear in the optional Party Identifier of field 57a. T28.Category 1 RT RU SC SW SW ZA 9!n 6!n 3.Final edition . T29.5n 6!n 6!n Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.February 2003 . it must not be followed by any other information. MCCO. 15. If the account with institution cannot be identified by a BIC. The BIC must not be a BEI. USAGE RULES When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. 72 Standards Release Guide 2003 .. US banks require that the code //FW appears in the optional Party Identifier of field 57a. If it is used with option C. If it is used with option A.

Category 1 MT 102 NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address.Final edition . 16. CODES One of the following codes may be used.February 2003 73 . placed between slashes (’/’): INV IPI RFB ROC Invoice (followed by the date. Field 26T: Transaction Type Code FORMAT Option T 3!c Standards Release Guide 2003 . the Sender must agree to the maximum usable length of this field with the Receiver. Ordering customer’s reference. USAGE RULES This field must not contain information to be acted upon by the Receiver. Reference for the beneficiary customer (followed by up to 16 characters). Due to national clearing restrictions. which vary significantly from country to country. USAGE RULES At least the name or the BIC/BEI of the beneficiary customer is mandatory.SWIFTStandards . Unique reference identifying a related International Payment Instruction (followed by up to 20 characters). 17. T28. If a BEI is specified. either connected or non-connected (Error code(s): T27. it must be meaningful for the financial institution that services the account for the beneficiary customer. Field 70: Remittance Information FORMAT 4*35x (Narrative) PRESENCE Optional DEFINITION This field specifies details of the individual transaction which are to be transmitted to the beneficiary customer. T45). T29. reference and details of the invoice).

February 2003 . USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. purpose of.Final edition . the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C5) DEFINITION This field specifies the codes for the statutory and/or regulatory information required by the authorities in the country of the Receiver or the Sender.Category 1 PRESENCE Conditional (C5) DEFINITION This field identifies the nature of. pension or dividend. 18.MT 102 SWIFTStandards . the following codes may be used. eg. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. 74 Standards Release Guide 2003 . and/or reason for the individual transaction. salary. CODES When the residence of either the ordering customer or the beneficiary customer is to be identified.

As a consequence. it is the amount that the sending bank was instructed to pay. Field 33B: Currency/Instructed Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Conditional (C8. A decimal comma is mandatory and is included in the maximum length. 19. USAGE RULES If field 33B is present in the message received. 20. it has to be forwarded unchanged to the next party. T43). Standards Release Guide 2003 . field 32A equals 33B. Otherwise. this amount is the original ordered amount as instructed by the ordering customer. if present.SWIFTStandards . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). T40. The integer part of Amount must contain at least one digit. C10) DEFINITION This field specifies the currency and amount of the instruction.Final edition . This field must be present when a currency conversion or an exchange has been performed on the Sender’s side. if there are no Sender’s or Receiver’s charges and no currency conversion or exchange took place. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C4) DEFINITION This field specifies which party will bear the charges for the transaction in the same occurrence of sequence B. If the transaction is within the scope of the EC Directive on cross border credit transfers.Category 1 MT 102 The information specified must not have been explicitly conveyed in another field. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.February 2003 75 . This amount is provided for information purposes and has to be transported unchanged through the transaction chain.

T40. A decimal comma is mandatory and is included in the maximum length. the first occurrence of this field specifies the charges of the first bank in the transaction chain that deducted charges. 22. T43). NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).Final edition .MT 102 SWIFTStandards . 21. The net amount after deduction of the Sender’s charges will be quoted as the transaction amount in field 32B. Ie.February 2003 . Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) 76 Standards Release Guide 2003 . The transaction charges on the Sender’s side are to be borne by the ordering customer and the transaction charges on the Receiver’s side are to be borne by the beneficiary customer. Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C9) DEFINITION This repetitive field specifies the currency and amount of the transaction charges deducted by the Sender and by previous banks in the transaction chain. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. This field may be repeated to specify to the Receiver the currency and amount of charges taken by preceding banks in the transaction chain.Category 1 CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA The transaction charges are to be borne by the beneficiary customer. The transaction charges are to be borne by the ordering customer. Charges should be indicated in the order in which they have been deducted from the transaction amount. USAGE RULES These fields are conveyed for transparency reasons. The integer part of Amount must contain at least one digit. the last occurrence always gives the Sender’s charges.

24. A decimal comma is mandatory and is included in the maximum length. ie.Final edition . Field 32A: Value Date. Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C6) DEFINITION This field specifies the exchange rate used to convert the instructed amount specified in field 33B in the same occurrence of sequence B.SWIFTStandards . USAGE RULES The Receiver’s charges are to be conveyed to the Receiver. T40.Category 1 MT 102 PRESENCE Conditional (C9) DEFINITION This field specifies the currency and amount of the transaction charges due to the Receiver. USAGE RULES This field must be present when a currency conversion has been performed on the Sender’s side. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). 23.February 2003 77 . T43). Amount FORMAT Option A 6!n3!a15d (Date) (Currency) (Amount) Standards Release Guide 2003 . Currency Code. T43). The integer part of Amount must contain at least one digit. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. to facilitate bookkeeping and to calculate or verify the total Receiver’s charges amount stipulated in Sequence C. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. not for transparency but for accounting reasons.

The settlement amount is the amount to be booked/reconciled at interbank level. USAGE RULES This field is only to be used where the sum of amounts is different from the settlement amount specified in field 32A. the currency and the settlement amount. T40. A decimal comma is mandatory and is included in the maximum length. A decimal comma is mandatory and is included in the maximum length. 26. USAGE RULES Where field 71A indicates OUR payments. Where field 71A indicates SHA or BEN payments. when one or more transactions in sequence B contains the charging option OUR in field 71A. 25. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).MT 102 SWIFTStandards . T40. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. T43). Field 19: Sum of Amounts FORMAT 17d (Amount) PRESENCE Optional DEFINITION This field specifies the sum of all amounts appearing in field 32B in each occurrence of sequence B. this field contains the sum of the amounts specified in the fields 19 and 71G. this field contains the total of all fields 32B.Category 1 PRESENCE Mandatory DEFINITION This field specifies the value date. Currency must be a valid ISO 4217 currency code (Error code(s): T52).February 2003 . The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The integer part of Amount must contain at least one digit.Final edition . Field 71G: Sum of Receiver’s Charges 78 Standards Release Guide 2003 . The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32A (Error code(s): C03. ie. T43).

Category 1 MT 102 FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C11) DEFINITION This field specifies the currency and accumulated amount of the transaction charges due to the Receiver. 27.Final edition . this field identifies the sum of the charges due. which has been prepaid and included in the interbank settlement amount. The integer part of Amount must contain at least one digit. placed between slashes (’/’): CLSTIME RNCTIME The time by which the funding payment must be credited. The time at which a TARGET payment has been credited at the receiving central bank. expressed in Central European Time (CET). either in sequence A or in all occurrences of sequence B. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. this field is not to be used when field 71A. expressed in Central European Time (CET). A decimal comma is mandatory and is included in the maximum length. T43).SWIFTStandards . 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. T40. If field 71G is present in sequence C.February 2003 79 . to the CLS Bank’s account at the central bank. the amount must not equal ’0’ (Error code(s): D57). with confirmation. or in one or more occurrences of sequence B. Standards Release Guide 2003 . indicates BEN or SHA payments. For transparency or accounting reasons. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). USAGE RULES Where field 71A indicates OUR payments either in sequence A. CODES One of the following codes may be used.

must be in the range of 00 through 13.ISO 8601). Option C must be used where only an account number is to be specified. this field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). The BIC must not be a BEI. Option A is the preferred option.MT 102 SWIFTStandards . 80 Standards Release Guide 2003 . T28. ie must not be of subtype BEID. Field 53a: Sender’s Correspondent FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Account) PRESENCE Optional DEFINITION Where required. the account to be credited or debited must be indicated in field 53a. Any ’HH’ or ’MM’ component outside of these range checks will be disallowed (Error code(s): T16). NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. ’HH’. ie. either connected or non-connected (Error code(s): T27. ie. and one of these accounts is to be used for reimbursement. TESP or TRCO (Error code(s): C05).Final edition . in the currency of the transaction. MCCO.February 2003 . USAGE RULES Absence of this field implies that the bilaterally agreed account is to be used for settlement. 28. Sign is either "+" or "-" (Error code(s): T15).and the minute component. T45). expressed in Central European Time (CET). 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 . where the hour component.Category 1 SNDTIME The time at which a TARGET payment has been debited at the sending central bank. T29. ’MM’ must be in the range of 00 through 59. In those cases where there are multiple direct account relationships. Time offset is expressed as HHMM. between the Sender and the Receiver.

depending on the currency of the transfer and the relationship between the Sender and the Receiver. the relationship between the Sender and the Receiver and the contents of field 54A. T28. If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver. If field 54A contains a branch of the Receiver and field 53a contains a branch of the Sender. the Receiver will claim reimbursement from its branch. the Receiver will claim reimbursement from its branch or will be paid by its branch. A branch of the Sender must not appear in field 54A. will be used. dictated by the currency of the transaction and the correspondent relationship between the Sender and the Receiver relative to that currency. In all other cases where field 54A contains a branch of the Receiver. or field 53a contains an account of the Sender serviced by the Receiver’s branch. in the currency of the transfer. USAGE RULES The absence of fields 53a and 54A implies that the single direct account relationship between the Sender and the Receiver. a cover message. The BIC must not be a BEI. T45). this field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver. the need for a cover message is dependent on the currency of the transaction. MT 202/203 or equivalent non-SWIFT must be sent to the financial institution identified in field 53a.Category 1 MT 102 If there is no direct account relationship. Standards Release Guide 2003 . T29. in the currency of the transaction. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. if present. the Receiver will be paid by its branch in field 53a. and the Sender intends to send a cover message to the branch of the Receiver. between the Sender and the Receiver (or branch of the Receiver when specified in field 54A). the Receiver will be paid by its branch in field 54A. In those cases where field 54A contains a branch of the Receiver. field 54A must not be present. MCCO. ie. and is not preceded by field 53a. The use and interpretation of fields 53a and 54A is. In this case. TESP or TRCO (Error code(s): C05). Field 54A: Receiver’s Correspondent FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION Where required. ie must not be of subtype BEID. then field 53a must be present. In all other cases.Final edition .SWIFTStandards . 29. When field 53a is present and contains a branch of the Sender. either connected or non-connected (Error code(s): T27.February 2003 81 . in all cases. when field 53a is present.

In view of the possible delay of execution and/or rejection of the transaction(s). USAGE RULES This field may be used to provide additional information to the Receiver where no other field is available. 82 Standards Release Guide 2003 . 30. The use and interpretation of fields 53a and 54A is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. field 72 may only be used after bilateral agreement between the Sender and the Receiver and in encoded form. the Receiver will be paid by the financial institution in field 54A. If either of these codes is used in the first position of the first line. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative . it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.Structured Format ) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Optional DEFINITION This field specifies additional information for the Receiver.Final edition .Category 1 Field 54A containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53a.February 2003 . placed between slashes (’/’). The codes REJT/RETN may be used in this field.MT 102 SWIFTStandards .

the currencies accepted and their settlement. The MT 102+ is a compatible subset of the core MT 102 that is documented separately in this section. This message may only be used on the FIN SWIFT network since it requires special validation field 23 may only contain codes CREDIT and SPAY subfield 1 (Account) of either field 59 or 59A is always mandatory field 72. Sequence B Transaction Details is a repetitive sequence.February 2003 83 .SWIFTStandards . MT 102+ Scope This message is sent by or on behalf of the financial institution of the ordering customer(s) to a financial institution in the country of the beneficiary customer(s). The MT 102+ allows the exchange of multiple customer credit transfers using a restricted set of fields and format options of the core MT 102 to make it straight through processable. The differences with the core MT 102 are: appropriate MT 102+ format validation is triggered by the code STP in the validation flag field 119 ({3:{119:STP}}) of the user header of the message (block 3) fields 52 and 57 may only be used with letter option A field 51A is not used in MT 102+. the user header of the message (block 3) is mandatory and must contain the code STP in the validation flag field 119 ({3:{119:STP}}). This message is used to convey multiple payment instructions between financial institutions for clean payments. code INS must be followed by a valid BIC field 72. these bilateral agreements cover the transaction amount limits. The multiple payments checklist included below is recommended as a guide for institutions in the setup of their agreements. Sequence C Settlement Details is a single occurrence sequence and contains information about the settlement. or to issue a cheque to the beneficiary. It requests the Receiver to credit the beneficiary customer(s) directly or through a domestic clearing mechanism via another financial institution in the receiving country. Each occurrence is used to provide details of one individual transaction.Final edition .Category 1 MT 102+ MT 102+ Multiple Customer Credit Transfer Note: The use of this message type requires Message User Group (MUG) registration. MT 102+ Format Specifications To trigger the MT 102+ format validation. Mandatory Sequence A General Information Standards Release Guide 2003 . Its use is subject to bilateral/multilateral agreements between Sender and Receiver. Amongst other things. MT 102+ Multiple Customer Credit Transfer Status Tag Field Name Content/Options No. codes REJT/RETN must not be used field 72 must not include ERI information. The MT 102+ consists of three sequences: Sequence A General Information is a single occurrence sequence and contains information which applies to all individual transactions described in sequence B.

Final edition .MT 102+ SWIFTStandards . 1 2 3 4 5 6 7 8 A or K [/1!a][/34x] 4!a2!a2!c[3!c] 3!c 3*35x 3!a 12d Transaction Type Code Regulatory Reporting Details of Charges Exchange Rate -----> Mandatory Repetitive Sequence B Transaction Details M M O O O M O O O O O -----> O -----| O 71G Receiver’s Charges 3!a15d 21 71F Sender’s Charges 3!a15d 20 21 32B 50a 52A 57A 59a 70 26T 77B 33B 71A Transaction Reference Transaction Amount Ordering Customer Ordering Institution Account With Institution Beneficiary Customer Remittance Information Transaction Type Code Regulatory Reporting Currency/Instructed Amount Details of Charges 16x 3!a15d A or K [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4!a2!a2!c[3!c] A or no option letter 4*35x 3!c 3*35x 3!a15d 3!a 9 10 11 12 13 14 15 16 17 18 19 84 Standards Release Guide 2003 .February 2003 .Category 1 Status M M O O O O O O Tag 20 23 50a 52A 26T 77B 71A 36 File Reference Bank Operation Code Ordering Customer Ordering Institution Field Name 16x 16x Content/Options No.

nor be absent from both sequences (Error code(s): D17). but it must never be present in both sequences..February 2003 85 .. Present Not present then 50a in each sequence B is . 32B and 32A must be the same for all occurrences of these fields in the message (Error code(s): C02). Not allowed Mandatory Standards Release Guide 2003 .Final edition . Currency Code. 22 -----| Mandatory Sequence C Settlement Details M O O -----> O -----| O O O 53a 54A 72 Sender’s Correspondent Receiver’s Correspondent Sender to Receiver Information M = Mandatory O = Optional A or C [/1!a][/34x] 4!a2!a2!c[3!c] 6*35x 27 28 29 13C Time Indication /8c/4!n1!x4!n 26 32A 19 71G Value Date.. Amount Sum of Amounts Sum of Receiver’s Charges 6!n3!a15d 17d 3!a15d 23 24 25 MT 102+ Network Validated Rules C1 If field 19 is present in sequence C. C2 The currency code in the fields 71G. If 50a in sequence A is. C3 Field 50a must be present either in sequence A or in each occurrence of sequence B.Category 1 MT 102+ Status O Tag 36 Exchange Rate Field Name 12d Content/Options No.SWIFTStandards .. it must equal the sum of the amounts in all occurrences of field 32B (Error code(s): C01).

. that field must not be present in any occurrence of sequence B..MT 102+ SWIFTStandards . EITHER field 36 must be present in sequence A and not in any sequence B. Not allowed Mandatory C5 If a field 52A. Present Not present In each occurrence of sequence B then field 52A is .. nor be absent from both sequences (Error code(s): D20).. When a field 36 (sequence A or sequence B) is required...Final edition . in all other cases field 36 is not allowed in the message.. Present Not present In each occurrence of sequence B then field 71A is. Not allowed Optional Sequence A if field 26T is .February 2003 . Sequence A if field 71A is. Sequence A if field 52A is . that field must not be present in sequence A (Error code(s): D18).. 26T or 77B is present in sequence A. 86 Standards Release Guide 2003 ..... OR it must be present in every sequence B which contains fields 32B and 33B with different currency codes and must not be present in sequence A or any other sequence B (Error code(s): D22). Not allowed Optional Sequence A if field 77B is .. When a field 52A.. Present Not present In each occurrence of sequence B then field 26T is .. Present Not present In each occurrence of sequence B then field 77B is .. Not allowed Optional C6 Field 36 (sequence A or sequence B) must be present in the message if there is any sequence B which contains a field 33B with a currency code different from the currency code in field 32B. 26T or 77B is present in any occurrence of sequence B. but it must never be present in both sequences.Category 1 C4 Field 71A must be present either in sequence A or in each occurrence of sequence B.

PT... IS. GF. otherwise field 33B is optional (Error code(s): D49). GB. TF and VA.. SM.Final edition .Category 1 MT 102+ Sequence A If field 36 is present Sequence B Then in minimum one occurrence of Seq. IT. MC. Mandatory Optional Optional Optional Note: See Rule C9 C8 If field 71A in sequence A contains OUR.. NL. PM. Equal Not equal Not present n/a Not allowed Mandatory Not allowed Then field 36 is . In each occurrence of Sequence B And currency codes in fields 32B and 33B are . GP. LI.. GR. Not present Present C7 If the country codes of the Sender’s and the Receiver’s BICs are within the following list: AD. NO. FI. CH.SWIFTStandards . SE. SJ. ES. DK.. then field 71F is not allowed and field 71G is optional in any occurrence of sequence B (Error code(s): E13). RE. then field 33B is mandatory in each occurrence of sequence B. BV. If field 33B is .. Standards Release Guide 2003 . GI. MQ. LU. If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No In each occurrence of sequence B then field 33B is . AT. DE. IE. B field 33B must be present and currency codes in fields 32B and 33B must be different And field 36 is not allowed in any occurrence of Seq. B Sequence A If field 36 is ... FR.February 2003 87 .. BE.

In sequence B if field 71A is. then fields 71F are optional and field 71G is not allowed in the same occurrence of sequence B (Error code(s): D50).February 2003 . SHA Optional Not allowed and field 71G is.. In each occurrence of sequence B then field(s) 71F is (are).. In the same occurrence of sequence B then field(s) 71F is (are)............. In sequence A if field 71A is. In each occurrence of sequence B then field(s) 71F is (are).. OUR Not allowed Optional and field 71G is..Final edition . Note: See rules C4 and C8 (rule C4 takes precedence over rule C8) If field 71A in sequence A contains SHA. Note: See rules C4 and C8 (rule C4 takes precedence over rule C8) 88 Standards Release Guide 2003 ... and field 71G is..Category 1 In sequence A if field 71A is. In sequence B if field 71A is.MT 102+ SWIFTStandards . In the same occurrence of sequence B then field(s) 71F is (are).. Optional OUR Not allowed If field 71A in sequence B contains OUR... SHA Optional Not allowed and field 71G is... If field 71A in sequence B contains SHA. then field 71F is not allowed and field 71G is optional in the same occurrence of sequence B (Error code(s): E13). then fields 71F are optional and field 71G is not allowed in any occurrence of sequence B (Error code(s): D50).

Present Present Not present Not present and field 71G is. BEN Mandatory Not allowed and field 71G is. In each occurrence of sequence B If field 71F is.Final edition ....... then at least one occurrence of field 71F is mandatory in each occurrence of sequence B and field 71G is not allowed (Error code(s): E15). In sequence A if field 71A is. C10 If field 71G is present in an occurrence of sequence B.. BEN Mandatory Not allowed and field 71G is. then at least one occurrence of field 71F is mandatory in the same occurrence of sequence B and field 71G is not allowed (Error code(s): E15)....SWIFTStandards ... Present Not present Present Not present then field 33B is. then field 71G is mandatory in the sequence C (Error code(s): D79)....Category 1 MT 102+ If field 71A in sequence A contains BEN. If field 71A in sequence B contains BEN.. In the same occurrence of sequence B then field(s) 71F is (are). then field 33B is mandatory in the same occurrence of sequence B (Error code(s): D51). In sequence B if field 71A is. see rule C8.February 2003 89 . In each occurrence of sequence B then field(s) 71F is (are)... Rejected (*) Mandatory Mandatory Optional (*) both fields 71F and 71G present is not a valid combination. Standards Release Guide 2003 . Note: See rules C4 and C8 (rule C4 takes precedence over rule C8) C9 If either field 71F (at least one occurrence) or field 71G are present in an occurrence of sequence B.

RE. If field 57A is present and the country code of the BIC in 57A is within the above list of country codes. BE.Final edition . In header of MT If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No Yes Yes No No Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No Yes No Yes No Yes No Yes No In each occurrence of sequence B and field 57A is present and country code of field 57A equals one of the listed country codes n/a n/a n/a n/a Yes Yes Yes Yes No No No No Then an IBAN in subfield Account of field 59a in this occurrence of Seq. GP. DE. IS. IE. SE. MC. TF and VA. CH. BV. B (Error code(s): D19). C11 If the country codes of the Sender’s and the Receiver’s BIC are within the following list: AD. B is . the IBAN (ISO-13616) is mandatory in subfield Account of field 59a in that occurrence of Seq. the IBAN (ISO-13616) is mandatory in subfield Account of field 59a in that occurrence of Seq. the presence of the IBAN (ISO-13616) is optional and its format is not validated in subfield Account of field 59a. NL.MT 102+ SWIFTStandards . GB.February 2003 . In all other cases.Category 1 If in any occurrence of sequence B field 71G is. PM. Present Mandatory in sequence C then field 71G is. DK. LU.. PT. GR. SM. AT.. NO. FI.. FR. GF. then in each occurrence of sequence B the following apply: If field 57A is not present. Mandatory Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Optional Optional No No No No Yes Yes Yes Yes Yes Yes Yes Yes 90 Standards Release Guide 2003 . IT. B (Error code(s): D19).. GI. SJ. LI... ES. MQ.

. Usage Rules for Amount Related Fields There is a relationship between the amount related fields 33B. Receiver will deduct its charges. adjusted with the exchange rate in field 36. invoice amount. equals the total amount in field 19. The sum of all transaction amounts in fields 32B. 19 and 32A which may be logically expressed in the following formulas: For each occurrence of sequence B. Sequence B field 71F is..February 2003 91 . Amount instructed by the originator. the instructed amount in field 33B. Receiver will deduct its own charges. after sending bank has deducted its charges..Final edition . equals the transaction amount in field 32B. C7.. 32B. C8. OUR Sum of field(s) 32B of sequence B Sequence C field 32A is. Sum of fields 71G of sequences B Standards Release Guide 2003 .Category 1 MT 102+ MT 102+ Usage Rules If a registered user receives an MT 102+ without bilateral agreement with the Sender. 71F. C9 and C10. The total amount in field 19 (or the sum of all transaction amounts in fields 32B). C6. then field 32B is. The sum of all Receiver’s charges in fields 71G of sequence B.. minus the Sender’s charges in field(s) 71F. equals the total Receiver’s charges of field 71G in sequence C.. all occurrences of that field must be taken into account in the formula.. equals the interbank settled amount in field 32A. the Receiver should query the message according to normal banking practice. SHA Optional Not allowed BEN At least one occurrence mandatory Not allowed Sequence A if field 71A is.. 36. Not allowed Optional and field 71G is.. 71G..... If field 71F is present more than once.. that field must not be taken into account in the formula. Amount as instructed by the originator. OUR Net amount to be credited to the Beneficiary. Settlement Amount equals field 19 plus field 71G of sequence C and field 71G is... If a field is not present. plus the total Receiver’s charges in field 71G of sequence C. Charges have been prepaid by the ordering customer.SWIFTStandards . Sequence A if field 71A is. Presence of the fields mentioned above is subject to the conditional field rules C5. eg. then field 19 is.

2. then field 19 is. SHA BEN Not used Not used Sequence C field 32A is....Category 1 Sequence A if field 71A is. MT 900 Confirmation of Debit and/or 950 Statement Message. eg..February 2003 . cancellations etc. Settlement Amount equals Sum of field(s) 32B of sequence B Settlement Amount equals Sum of field(s) 32B of sequence B and field 71G is.MT 102+ SWIFTStandards . USAGE RULES This reference must be quoted in any related confirmation or statement..Final edition . PRESENCE Mandatory 92 Standards Release Guide 2003 . Field 23: Bank Operation Code FORMAT 16x To be formatted as 6a. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). The file reference must be unique for each file and is part of the file identification and transaction identification which is used in case of queries. Field 20: File Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.. Not allowed Not allowed MT 102+ Field Specifications 1...

Field 52A: Ordering Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) Standards Release Guide 2003 .Category 1 MT 102+ DEFINITION This field identifies the type of operation. it must be stated in Account. T28. the code CRTST is only valid when sent by a Test & Training destination. CODES One of the following codes must be used (Error code(s): T08): CREDIT CRTST SPAY This message contains credit transfer(s) to be processed according to the pre-established bilateral agreement between the Sender and the Receiver.SWIFTStandards . either connected or non-connected (Error code(s): T27. 3. This message contains credit transfer(s) to be processed according to the SWIFTPay Service Level. This message contains credit transfers for test purpose(s). T29. 4. Field 50a: Ordering Customer FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C3) DEFINITION This field identifies the customer ordering all transactions described in sequence B. USAGE RULES If the account number of the ordering customer is present. USAGE RULES As tests in FIN should be done in Test & Training.February 2003 93 . NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. T45).Final edition .

9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. when different from the Sender. T28. The BIC must not be a BEI.. T45). 94 Standards Release Guide 2003 . ie must not be of subtype BEID.Final edition . This is applicable even if field(s) 50a contain(s) an IBAN. The following codes may be used preceded by a double slash (’//’): AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8. which instructed the Sender to transmit all transactions described in sequence B.Category 1 PRESENCE Conditional (C5) DEFINITION This field specifies the financial institution. CODES Party Identifier may be used to indicate a national clearing system code. either connected or non-connected (Error code(s): T27. TESP or TRCO (Error code(s): C05).February 2003 . T29. MCCO. USAGE RULES The coded information contained in field 52A must be meaningful to the Receiver of the message.MT 102+ SWIFTStandards .

eg. In case the Receiver of the message is not legally obliged to forward the information to a regulatory body. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. salaries. CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. pensions or dividends. the following codes must be used. placed between slashes (’/’): Standards Release Guide 2003 .Category 1 MT 102+ 5. 6.February 2003 95 .Final edition . Field 26T: Transaction Type Code FORMAT Option T 3!c PRESENCE Conditional (C5) DEFINITION This field identifies the nature of. USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. CODES When the residence of either ordering customer or beneficiary customer is to be identified. he is allowed to ignore the content of this field. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C5) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver or Sender.SWIFTStandards . purpose of and/or reason for all transactions described in sequence B.

Transaction charges on the Sender’s side are to be borne by the ordering customer and transaction charges on the Receiver’s side are to be borne by the beneficiary customer. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C4) DEFINITION This field specifies which party will bear the charges for all transactions described in sequence B. In case the Receiver of the message is not legally obliged to forward the information to a regulatory body. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the beneficiary customer. 8. 7.Category 1 BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. he is allowed to ignore the content of this field. All transaction charges are to be borne by the ordering customer.MT 102+ SWIFTStandards .Final edition . Field 36: Exchange Rate FORMAT 12d (Rate) 96 Standards Release Guide 2003 . The information specified must not have been explicitly conveyed in another field and is valid for all transactions described in sequence B.February 2003 .

Final edition .. 10.SWIFTStandards . Field 32B: Transaction Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory Standards Release Guide 2003 . NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). the content of field 20 File Reference together with the content of this field provides the transaction identification.February 2003 97 . USAGE RULES This field must be present.Category 1 MT 102+ PRESENCE Conditional (C6) DEFINITION This field specifies the exchange rate used to convert all instructed amounts specified in field 33B in sequence B. 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 related queries. T43). cancellations etc. 9. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. when a currency conversion has been performed on the Sender’s side.

of which the Receiver will deduct its own charges. Depending on the charging option specified in field 71A. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. it must be stated in Account.Category 1 DEFINITION This field specifies the individual transaction amount remitted by the Sender to the Receiver. A decimal comma is mandatory and is included in the maximum length. If field 71A is BEN. be the basis for the Receiver to calculate the amount to be credited to the beneficiary. eg. Field 52A: Ordering Institution 98 Standards Release Guide 2003 . T40. USAGE RULES If the account number of the ordering customer is present. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). Field 50a: Ordering Customer FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C3) DEFINITION This field specifies the customer ordering the transaction. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. either connected or non-connected (Error code(s): T27. T45). 11. the amount as instructed by the originator. and from which amount the Receiver will deduct its charges. The integer part of Amount must contain at least one digit. If field 71A is SHA. invoice amount. taking into account the charging option. the content of field 32B is as follows: If field 71A is OUR.Final edition . T28.February 2003 . the amount as instructed by the originator minus the Senders’ charges. as charges have been prepaid by the ordering customer. T43). USAGE RULES This amount will.MT 102+ SWIFTStandards . the net amount to be credited to the beneficiary. 12. T29.

T29. T45). when other than the Sender.Final edition . T28.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.February 2003 99 .SWIFTStandards .. either connected or non-connected (Error code(s): T27. Standards Release Guide 2003 .Category 1 MT 102+ FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Conditional (C5) DEFINITION This field specifies the financial institution. This is applicable even if field 50a contains an IBAN. which instructed the Sender to transmit the transaction. The following codes may be used preceded by a double slash (’//’): AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8. CODES Party Identifier may be used to indicate a national clearing system code.

ie must not be of subtype BEID.February 2003 .which services the account for the beneficiary customer identified in the same sequence. TESP or TRCO (Error code(s): C05).9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code 100 Standards Release Guide 2003 . 13.Final edition . CODES Party Identifier may be used to indicate a national clearing system code. This is applicable even if field 59 or 59A contains an IBAN.when other than the Receiver . USAGE RULES The coded information contained in field 52A must be meaningful to the Receiver of the message. MCCO.MT 102+ SWIFTStandards ..Category 1 The BIC must not be a BEI. The following codes may be used preceded by a double slash (’//’): AT AU BL CC ES FW GR HK IE IN IT NZ PT 5!n 6!n 8!n 9!n 8. Field 57A: Account With Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field specifies the financial institution .

The BIC must not be a BEI. either connected or non-connected (Error code(s): T27. ie must not be of subtype BEID. NETWORK VALIDATED RULES Account must be present (Error code(s): E10).SWIFTStandards . T73). T29. US banks require that the code //FW appears in the optional Party Identifier of field 57A. The code //RT is binding for the Receiver. If a BEI is specified. TESP or TRCO (Error code(s): C05). T29. Standards Release Guide 2003 .February 2003 101 . If an IBAN must be present in Account (C11). either connected or non-connected (Error code(s): T27. MCCO.Category 1 MT 102+ RT SC 6!n Pay by Real Time Gross Settlement UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. Field 59a: Beneficiary Customer FORMAT Option A No option letter [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the customer to which the transaction amount should be transmitted. USAGE RULES At least the name or the BEI of the beneficiary customer is mandatory. the code //RT should appear in the optional Party Identifier of field 57A. it must be meaningful for the financial institution that services the account for the beneficiary customer. T45). T28. The BIC/BEI must be a SWIFT registered address. USAGE RULES When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire.Final edition . the IBAN must be a valid IBAN (ISO-13616) (Error code(s): D19. It must not be followed by any other information. T28. 14. T45). When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS).

CODES One of the following codes may be used.MT 102+ SWIFTStandards . 16. 102 Standards Release Guide 2003 . Ordering customer’s reference. Field 26T: Transaction Type Code FORMAT Option T 3!c PRESENCE Conditional (C5) DEFINITION This field identifies the nature of. which vary significantly from country to country. Reference for the beneficiary customer (followed by up to 16 characters). and/or reason for the individual transaction. Unique reference identifying a related International Payment Instruction (followed by up to 20 characters).Final edition . USAGE RULES This field must not contain information to be acted upon by the Receiver. Field 70: Remittance Information FORMAT 4*35x (Narrative) PRESENCE Optional DEFINITION This field specifies details of the individual transaction which are to be transmitted to the beneficiary customer. pension or dividend. salary. Due to national clearing restrictions.Category 1 15. eg. purpose of. the Sender must agree to the maximum usable length of this field with the Receiver.February 2003 . reference and details of the invoice). placed between slashes (’/’): INV IPI RFB ROC Invoice (followed by the date.

he is allowed to ignore the content of this field. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C5) DEFINITION This field specifies the codes for the statutory and/or regulatory information required by the authorities in the country of the Receiver or the Sender.Category 1 MT 102+ CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. 17. CODES When the residence of either the ordering customer or the beneficiary customer is to be identified.February 2003 103 . The information specified must not have been explicitly conveyed in another field.Final edition . Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. Standards Release Guide 2003 . In case the Receiver of the message is not legally obliged to forward the information to a regulatory body. placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer.SWIFTStandards . USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. the following codes may be used.

T40.Final edition . The integer part of Amount must contain at least one digit.February 2003 . 104 Standards Release Guide 2003 . C9) DEFINITION This field specifies the currency and amount of the instruction. This amount is provided for information purposes and has to be transported unchanged through the transaction chain.Category 1 18. this amount is the original ordered amount as instructed by the ordering customer. Field 33B: Currency/Instructed Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Conditional (C7. If the transaction is within the scope of the EC Directive on cross border credit transfers. field 32A equals 33B. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Otherwise. As a consequence. it is the amount that the sending bank was instructed to pay. This field must be present when a currency conversion or an exchange has been performed on the Sender’s side. USAGE RULES If field 33B is present in the message received. it has to be forwarded unchanged to the next party. 19. CODES One of the following codes must be used (Error code(s): T08): BEN The transaction charges are to be borne by the beneficiary customer. T43). A decimal comma is mandatory and is included in the maximum length. if there are no Sender’s or Receiver’s charges and no currency conversion or exchange took place. if present. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C4) DEFINITION This field specifies which party will bear the charges for the transaction in the same occurrence of sequence B.MT 102+ SWIFTStandards . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).

the first occurrence of this field specifies the charges of the first bank in the transaction chain that deducted charges. A decimal comma is mandatory and is included in the maximum length. 21. The integer part of Amount must contain at least one digit. 20. This field may be repeated to specify to the Receiver the currency and amount of charges taken by preceding banks in the transaction chain. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.Category 1 MT 102+ OUR SHA The transaction charges are to be borne by the ordering customer. Charges should be indicated in the order in which they have been deducted from the transaction amount. The net amount after deduction of the Sender’s charges will be quoted as the transaction amount in field 32B. USAGE RULES These fields are conveyed for transparency reasons. Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C9) DEFINITION This repetitive field specifies the currency and amount of the transaction charges deducted by the Sender and by previous banks in the transaction chain.Final edition . T43).February 2003 105 . the last occurrence always gives the Sender’s charges. T40. The transaction charges on the Sender’s side are to be borne by the ordering customer and the transaction charges on the Receiver’s side are to be borne by the beneficiary customer. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).SWIFTStandards . Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C9) Standards Release Guide 2003 . Ie.

The integer part of Amount must contain at least one digit.Final edition . 22. ie. Currency Code.MT 102+ SWIFTStandards .Category 1 DEFINITION This field specifies the currency and amount of the transaction charges due to the Receiver. Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C6) DEFINITION This field specifies the exchange rate used to convert the instructed amount specified in field 33B in the same occurrence of sequence B. Amount FORMAT Option A 6!n3!a15d (Date) (Currency) (Amount) PRESENCE Mandatory 106 Standards Release Guide 2003 .February 2003 . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. T43). T40. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. 23. T43). Field 32A: Value Date. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. USAGE RULES This field must be present when a currency conversion has been performed on the Sender’s side. USAGE RULES The Receiver’s charges are to be conveyed to the Receiver. to facilitate bookkeeping and to calculate or verify the total Receiver’s charges amount stipulated in Sequence C. A decimal comma is mandatory and is included in the maximum length. not for transparency but for accounting reasons.

The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). T43).Final edition . USAGE RULES Where field 71A indicates OUR payments. Field 71G: Sum of Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) Standards Release Guide 2003 . ie.SWIFTStandards . T40. this field contains the sum of the amounts specified in the fields 19 and 71G. USAGE RULES This field is only to be used where the sum of amounts is different from the settlement amount specified in field 32A. The number of digits following the comma must not exceed the maximum number allowed for the currency specified in field 32A (Error code(s): C03. Currency must be a valid ISO 4217 currency code (Error code(s): T52). 25. the currency and the settlement amount. A decimal comma is mandatory and is included in the maximum length. Field 19: Sum of Amounts FORMAT 17d (Amount) PRESENCE Optional DEFINITION This field specifies the sum of all amounts appearing in field 32B in each occurrence of sequence B. when one or more transactions in sequence B contains the charging option OUR in field 71A. The settlement amount is the amount to be booked/reconciled at interbank level. Where field 71A indicates SHA or BEN payments. 24. T40.February 2003 107 . this field contains the total of all fields 32B. T43). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. A decimal comma is mandatory and is included in the maximum length.Category 1 MT 102+ DEFINITION This field specifies the value date.

which has been prepaid and included in the interbank settlement amount. T40. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). to the CLS Bank’s account at the central bank. 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. with confirmation. expressed in Central European Time (CET). the amount in field 71G must not equal ’0’ (Error code(s): D57). this field identifies the sum of the charges due.MT 102+ SWIFTStandards . expressed in Central European Time (CET). indicates BEN or SHA payments. CODES One of the following codes may be used. 26.Final edition . either in sequence A or in all occurrences of sequence B.February 2003 . placed between slashes (’/’): CLSTIME RNCTIME SNDTIME The time by which the funding payment must be credited. The time at which a TARGET payment has been credited at the receiving central bank. The integer part of Amount must contain at least one digit. For transparency or accounting reasons. USAGE RULES Where field 71A indicates OUR payments either in sequence A. The time at which a TARGET payment has been debited at the sending central bank. T43). If field 71G is present in sequence C. A decimal comma is mandatory and is included in the maximum length. or in one or more occurrences of sequence B.Category 1 PRESENCE Conditional (C10) DEFINITION This field specifies the currency and accumulated amount of the transaction charges due to the Receiver. expressed in Central European Time (CET). this field is not to be used when field 71A. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 108 Standards Release Guide 2003 .

SWIFTStandards . in the currency of the transaction. between the Sender and the Receiver. USAGE RULES The time zone in which date and Time are expressed is to be identified by means of the offset against the UTC (Coordinated Universal Time .February 2003 109 . the account to be credited or debited must be indicated in field 53a. and one of these accounts is to be used for reimbursement. Standards Release Guide 2003 . Sign is either "+" or "-" (Error code(s): T15). When field 53A is present and contains a branch of the Sender. ’HH’. If there is no direct account relationship. the relationship between the Sender and the Receiver and the contents of field 54A. ie. either connected or non-connected (Error code(s): T27. In those cases where there are multiple direct account relationships. Option C must be used where only an account number is to be specified. T45).Final edition . Option A is the preferred option. Time offset is expressed as ’HHMM’. MCCO. this field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. must be in the range of 00 through 13.ISO 8601). ie. Field 53a: Sender’s Correspondent FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Account) PRESENCE Optional DEFINITION Where required. between the Sender and the Receiver (or branch of the Receiver when specified in field 54A). TESP or TRCO (Error code(s): C05). and the minute component. T28. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. the need for a cover message is dependent on the currency of the transaction. Any ’HH’ or ’MM’ component outside of these range checks will be disallowed (Error code(s): T16).Category 1 MT 102+ NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). T29. then field 53A must be present. if present. The BIC must not be a BEI. ie must not be of subtype BEID. USAGE RULES Absence of this field implies that the bilaterally agreed account is to be used for settlement. where the hour component. in the currency of the transaction. ’MM’ must be in the range of 00 through 59. 27.

dictated by the currency of the transaction and the correspondent relationship between the Sender and the Receiver relative to that currency. Field 54A: Receiver’s Correspondent FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION Where required. T29. when field 53A is present. MCCO. field 54A must not be present. and is not preceded by field 53a.Final edition . either connected or non-connected (Error code(s): T27. ie must not be of subtype BEID. the Receiver will be paid by its branch in field 54A. or field 53a contains an account of the Sender serviced by the Receiver’s branch. ie. USAGE RULES The absence of fields 53a and 54A implies that the single direct account relationship between the Sender and the Receiver. In all other cases. a cover message. The use and interpretation of fields 53a and 54a is.February 2003 . the Receiver will claim reimbursement from its branch. In those cases where field 54A contains a branch of the Receiver. In this case. in the currency of the transfer. MT 202/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 correspondent relationship between the Sender and Receiver relative to that currency. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.MT 102+ SWIFTStandards . the Receiver will claim reimbursement from its branch or will be paid by its branch. the Receiver will be paid by its branch in field 53A. the Receiver will be paid by the financial institution in field 54A. and the Sender intends to send a cover message to the branch of the Receiver. In all other cases where field 54A contains a branch of the Receiver. If the branch of the Sender or other financial institution specified in field 53A is also the account servicer for the Receiver. in all cases. this field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. will be used. Field 54A containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53A. 110 Standards Release Guide 2003 . T45). depending on the currency of the transfer and the relationship between the Sender and the Receiver. T28. TESP or TRCO (Error code(s): C05). The BIC must not be a BEI. 28. If field 54A contains a branch of the Receiver and field 53A contains a branch of the Sender. A branch of the Sender must not appear in field 54A.Category 1 A branch of the Receiver may appear in field 53A if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver.

placed between slashes (’/’): INS The instructing institution which instructed the Sender to execute the transaction. T28. there is no validation of the following BIC either.Category 1 MT 102+ 29. USAGE RULES Field 72 must never be used for information for which another field is intended. It may be followed by additional narrative text.Structured Format ) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Optional DEFINITION This field specifies additional information for the Receiver. If the code /INS/ is used anywhere else than at the beginning of a line. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative .SWIFTStandards . it must not be used again at the beginning of any other line (Error code(s): T47). Each item for which a code exists must start with that code and may be completed with additional information.February 2003 111 . In this case. T29. NETWORK VALIDATED RULES If the code /INS/ is used at the beginning of a line. Each code used must be between slashes and appear at the beginning of a line. it is treated as free text and is ignored as far as validation is concerned. T46). T44. T45. This field must not include ERI (Error code(s): T82). it must be followed by a valid BIC and be the only information on that line (Error code(s): T27. Standards Release Guide 2003 .Final edition . the following code may be used. The codes /REJT/ or /RETN/ must not be used in this field (Error code(s): T81). If the code /INS/ is present at the beginning of a line. CODES Unless bilaterally agreed otherwise between the Sender and the Receiver.

MT 102+ SWIFTStandards . In any case.Final edition .February 2003 . and. Narrative text should preferably be the last information in this field.Category 1 Narrative text relating to a preceding code. Use of field 72 with uncoded instructions is not allowed. the code must conform to the structured format of this field. if used. where bilateral agreements covering the use of codes in this field are in effect. which is continued on the next line(s). must begin on a new line. 112 Standards Release Guide 2003 . must start with a double slash ’//’. It is strongly recommended to use the standard code proposed above.

1. are non-financial institutions from the perspective of the Sender. ie. via an MT 400.000 characters) will have to register for the Extended Remittance Information MUG. such as EDIFACT or ANSI-X12. depending on the business scenario in which the message is used. It is used to convey a funds transfer instruction in which the ordering customer or the beneficiary customer. This remittance information may optionally be exchanged in a non-SWIFT format. The core MT 103 is a General Use message. eg. This message may only be used for clean payment instructions. eg. no registration in a Message User Group is necessary to send and receive this message. The MT 103 + is a General Use message. or both.February 2003 113 . The MT 103 Extended Remittance Information MUG allows its subscribers to exchange MT 103 messages with field 77T containing an extended amount of remittance information. ie. 1 Standards Release Guide 2003 . It allows the exchange of single customer credit transfers using a restricted set of fields and format options of the MT 103 to make it straight through processable. Senders and Receivers who wish to use the MT 103 for the exchange of extended remittance data (up to 9. MT 103 Scope This message type is sent by or on behalf of the financial institution of the ordering customer. MT 103 Format Specifications MT 103 Single Customer Credit Transfer Status M -----> O -----| M -----> O -----| 23E Instruction Code 4!c[/30x] 4 23B Bank Operation Code 4!c 3 13C Time Indication /8c/4!n1!x4!n 2 Tag 20 Sender’s Reference Field Name 16x Content/Options No. 2. no registration in a Message User Group (MUG) is necessary to send and receive this message. directly or through (a) correspondent(s). It allows the exchange of single customer credit transfers using all MT 103 fields. collection.SWIFTStandards . to the financial institution of the beneficiary customer.Final edition . The MT 103 + is a compatible subset of the core MT 103 and is documented separately after the MT103.Category 1 MT 103 MT 103 Single Customer Credit Transfer The MT 103 message can be exchanged in three different ways. It must not be used to advise the remitting bank of a payment for a clean. 3. cheque. nor to provide the cover for a transaction whose completion was advised separately. except field 77T (Envelope Contents).

C or D A or no letter option 4*35x 3!a 71F Sender’s Charges 3!a15d 20 71G 72 77B 77T Receiver’s Charges Sender to Receiver Information Regulatory Reporting Envelope Contents M = Mandatory O = Optional 3!a15d 6*35x 3*35x 9000z 21 22 23 24 114 Standards Release Guide 2003 . B or D A.MT 103 SWIFTStandards .Category 1 Status O M O O M O O O O O O O M O M -----> O -----| O O O O Tag 26T 32A 33B 36 50a 51A 52a 53a 54a 55a 56a 57a 59a 70 71A Field Name Transaction Type Code Value Date/Currency/Interbank Settled Amount Currency/Instructed Amount Exchange Rate Ordering Customer Sending Institution Ordering Institution Sender’s Correspondent Receiver’s Correspondent Third Reimbursement Institution Intermediary Institution Account With Institution Beneficiary Customer Remittance Information Details of Charges 3!c Content/Options No. B or D A. C or D A.Final edition . 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 6!n3!a15d 3!a15d 12d A or K [/1!a][/34x] 4!a2!a2!c[3!c] A or D A.February 2003 . B. B or D A.

GP. If field 23B is . LU. Optional.. field 23E may contain only the codes SDVA. ES. PT.. AT. SM.. It can contain only SDVA. NL. CH. DE.SWIFTStandards . TELB. If field 33B is. NO. TELB. TF and VA.. FI.. GB. SE.Final edition . LI. GI. FR. IE. Present and currency code in field 33B . PM. SJ. PHOB or INTC Not allowed Standards Release Guide 2003 . otherwise field 33B is optional (Error code(s): D49).Category 1 MT 103 MT 103 Network Validated Rules C1 If field 33B is present and the currency code is different from the currency code in field 32A. PHOB.February 2003 115 . field 36 must be present. DK. then field 33B is mandatory.. C2 If the country codes of the Sender’s and the Receiver’s BICs are within the following list: AD. field 23E must not be used (Error code(s): E02). GR... GF. Mandatory Optional Optional Optional Note: See also Network Validated Rule C16 (Error code(s): D51) C3 If field 23B contains the code SPRI. BV.. BE. otherwise field 36 is not allowed (Error code(s): D75). INTC (Error code(s): E01).. If field 23B contains one of the codes SSTD or SPAY. NOT equals currency code in field 32A equals currency code in field 32A Not present NA Mandatory Not allowed Not allowed then field 36 is. IT. If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No then field 33B is ... IS. RE. MC. MQ. SPRI SSTD then field 23E is .

..Final edition . Present Not present then field 53a is . SPRI... Mandatory Optional C8 If field 23B contains one of the codes SPRI.. If field 23B is . May be used with option A only 116 Standards Release Guide 2003 . SSTD or SPAY then field 55a .MT 103 SWIFTStandards . SSTD or SPAY. If field 23B is . If field 55a is .. SSTD or SPAY then field 54a .February 2003 . SSTD or SPAY and field 53a is present with option B.. field 54a may be used with option A only (Error code(s): E05). Party Identifier must be present in field 53B (Error code(s): E04).. then both fields 53a and 54a must also be present (Error code(s): E06)...... field 53a must not be used with option D (Error code(s): E03).. Must not be used with option D C5 If field 23B contains one of the codes SPRI. SSTD and SPAY Not allowed Optional then field 23E is .... SPRI.. SPAY Not equals SPRI. May be used with option A only C7 If field 55a is present.Category 1 If field 23B is . C4 If field 23B contains one of the codes SPRI. SPRI.. SSTD or SPAY then field 53a . SSTD or SPAY. C6 If field 23B contains one of the codes SPRI. field 55a may be used with option A only (Error code(s): E07)... SSTD or SPAY.. If field 23B is . Mandatory Optional and field 54a is .

Allowed only with options A. If field 23B is .. If field 56a is .....February 2003 117 . C14 Fields 70 and 77T are mutually exclusive (Error code(s): E12). SPRI SSTD or SPAY Not allowed Allowed with option A or C only (if option C: clearing code must be used) then field 56a is . SPRI.SWIFTStandards .. subfield 1 (Account) in field 59a Beneficiary Customer is not allowed (Error code(s): E18). C11 If field 23B contains one of the codes SPRI. Present Not present Mandatory Optional then field 57a is . C or D (In option D: Party Identifier is mandatory) C12 If field 23B contains one of the codes SPRI. C10 If field 23B contains the code SPRI. C13 If any field 23E contains the code CHQB.. the following combinations are allowed: Standards Release Guide 2003 .. Subfield 1 (Party Identifier) in option D must be present (Error code(s): E09). If field 23B contains one of the codes SSTD or SPAY. subfield 1 (Account) in field 59a Beneficiary Customer is mandatory (Error code(s): E10).. field 56a may be used with either option A or option C. Thus. field 56a must not be present (Error code(s): E16).Category 1 MT 103 C9 If field 56a is present.. If field 23B is . it must contain a clearing code (Error code(s): E17).. option C or option D.. SSTD or SPAY. SSTD or SPAY. SSTD or SPAY then field 57a is . If option C is used. field 57a may be used with option A. field 57a must also be present (Error code(s): C81).Final edition .

.. If field 71A is . Not allowed and field 71G is .. then field 71F is not allowed and field 71G is optional (Error code(s): E13). then at least one occurrence of field 71F is mandatory and field 71G is not allowed (Error code(s): E15).. no field 23E may contain TELI or PHOI (Error code(s): E44).Final edition .. Mandatory (at least one occurrence) and field 71G is .. SHA then field(s) 71F is(are) . Not allowed C16 If either field 71F (at least one occurrence) or field 71G is present. Not allowed If field 71A contains BEN.MT 103 SWIFTStandards .... E15).. Optional If field 71A contains SHA. BEN then field 71F is ... Optional and field 71G is ...Category 1 Field 70 is .. If field 71A is . D50.February 2003 . Note 1: The presence of both fields 71F and 71G is also regulated by the network validated rule C15 (Error code(s): E13. Note 2: The presence of field 33B is also regulated by the Network Validated Rule C2 (Error code(s): D49). Present Not present Not present Not present Present Not present Field 77T is ... If field 71A is . OUR then field 71F is . 118 Standards Release Guide 2003 . C17 If field 56a is not present. C15 If field 71A contains OUR. then field(s) 71F is(are) optional and field 71G is not allowed (Error code(s): D50)... otherwise field 33B is optional (Error code(s): D51).. then field 33B is mandatory...

.. Both the Sender and the Receiver must have agreed to the exchange of MT 103 messages using field 77T. plus the Receiver’s charges in field 71G.45) Standards Release Guide 2003 .. TELI or PHOI C18 If field 57a is not present. If field 71F is present more than once.00 in GBP to a beneficiary in the United Kingdom Exchange rate is 1 EUR for 0. only contains coded information. Presence of the fields mentioned above is subject to the conditional field rules C1.. 71G. ie. When sending the message via IFT. If field 57a is . 71F and 32A which may be logically expressed in the following formula: The instructed amount in field 33B.Final edition .. that field must not be taken into account in the formula. Examples: Transaction A Pay the equivalent of EUR 1000..00 (=GBP 3. Field 72 may only be present when it is structured.1) Transaction charges on the Receiver’s side are GBP 4 (=EUR 6. If the field is used.. C15 and C16. Usage Rules for Amount Related Fields There is a relationship between the amount related fields 33B. no field 23E may contain TELE or PHON (Error code(s): E45).61999 GBP Transaction charges on the Sender’s side are EUR 5.Category 1 MT 103 If field 56a is .SWIFTStandards . the Sender must set the validation flag to REMIT in field 119 of the user header of the message. institutions must use the ’payments related’ content type 1020 (see IFT User Handbook) which requires authentication and acknowledgement that the message will be processed and submitted for execution. Not present then no occurrence of field 23E subfield 1 may contain . Institutions should bilaterally agree on the maximum size of the message.. If a field is not present. all occurrences of that field must be taken into account in the formula. the code of the validation flag must not be REMIT. C2. adjusted with the exchange rate in field 36. TELE or PHON C19 The currency code in the fields 71G and 32A must be the same (Error code(s): C02). If field 77T is not present. minus the Sender’s charges in field(s) 71F. equals the interbank settled amount in field 32A. MT 103 Usage Rules Field 77T can only be used if both Sender and Receiver of the message have subscribed to the Extended Remittance Information MUG.February 2003 119 . Not present then no occurrence of field 23E subfield 1 may contain . 36.

00 0.Category 1 Example A1: Charging option is OUR a) Amount debited from the ordering customer’s account: Instructed Amount + Sender’s charges + Receiver’s charges = Debit Amount EUR EUR EUR EUR 1000.99 Example A2: Charging option is SHA a) Amount debited from the ordering customer’s account: Instructed amount + Sender’s charges = Debit amount EUR EUR EUR 1000.99 4.Receiver’s charges = Credit amount GBP GBP GBP 623.00 6.99.00 120 Standards Release Guide 2003 . ie.00 5.00 OUR 4.00 619.45 1011. d) Amount credited to the beneficiary: Interbank settlement amount .MT 103 SWIFTStandards .99 c) The subsequent MT 950 shows one debit entry for GBP 623.Final edition .February 2003 .00 1005. field 32A.45 b) MT 103 extract: Field Tag 33B 71A 71G 36 32A GBP GBP EUR Content 1000.61999 623.00 5.

SWIFTStandards .99 c) The subsequent MT 950 shows one debit entry for GBP 619.99 Example A3: Charging option is BEN a) Amount debited from the ordering customer’s account: Instructed amount = Debit amount EUR 1000.99.1 0.00 b) MT 103 extract: Field Tag 33B 71A 71F 36 32A GBP GBP EUR Content 1000.89.00 SHA 0. ie.61999 619.89 c) The subsequent MT 950 shows one debit entry for GBP 616. Standards Release Guide 2003 . ie.99 4.00 BEN 3.00 615. d) Amount credited to the beneficiary: Interbank settlement amount .February 2003 121 .Receiver’s charges = Credit amount GBP GBP GBP 619.Final edition . field 32A. field 32A.61999 616.Category 1 MT 103 b) MT 103 extract: Field Tag 33B 71A 36 32A GBP EUR Content 1000.

MT 103 SWIFTStandards .93 5.1 Examples: Transaction B Pay GBP 1000.Final edition .Category 1 d) Amount credited to the beneficiary: Equivalent of Instructed amount .00 122 Standards Release Guide 2003 .38 b) MT 103 extract Field Tag 33B 71A 71G 32A GBP GBP GBP Content 1000.1) Transaction charges on the Receiver’s side are GBP 4.00 to a beneficiary in the United Kingdom Exchange rate is 1 EUR for 0.00 612.99 3.00 (=EUR 6.89 Note: The beneficiary is also advised of the Sender’s charges of GBP 3.Sender’s charges .00 1004.00 OUR 4.00 (=GBP 3.45) The ordering customer has an account in euro Sender and Receiver’s BIC are within the EU-country list Example B1: Charging option is OUR a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount + Sender’s charges + Receiver’s charges = Debit amount EUR EUR EUR EUR 1612.1 4.00 6.Receiver’s charges = Credit amount GBP GBP GBP GBP 619.45 1624.61999 GBP Transaction charges on the Sender’s side are EUR 5.February 2003 .

d) Amount credited to the beneficiary: Instructed amount = Credit amount GBP 1000.00 4. field 32A. ie.SWIFTStandards .Final edition .February 2003 123 .00 e) Note: field 36 does not have to be used since currency in fields 32A and 33B is the same Standards Release Guide 2003 .Receiver’s charges = Credit amount GBP GBP GBP 1000. field 32A.00 SHA 1000.00 c) The subsequent MT 950 shows one debit entry for GBP 1000.00 1617.93 b) MT 103 extract: Field Tag 33B 71A 32A GBP GBP Content 1000.00 Example B2: Charging option is SHA a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount + Sender’s charges = Debit amount EUR EUR EUR 1612.Category 1 MT 103 Note: field 36 does not have to be used since currency in fields 32A and 33B is the same c) The subsequent MT 950 shows one debit entry for GBP 1004.93 5. d) Amount credited to the beneficiary: Amount in 32A .00 996. ie.

9 ie.00 992. then third banks will be involved to cover the transaction. then the MT 103 message will contain the cover for the customer transfer as well as the payment details.93 b) MT 103 extract: Field Tag 33B 71A 71F 32A GBP GBP GBP Content 1000.10 996.00 3. and if the MT 103 is sent from one financial institution to the next financial institution in this chain. field 32A.90 c) The subsequent MT 950 shows one debit entry for GBP 996.10 4.Receiver’s charges = Credit amount GBP GBP GBP GBP 1000. 124 Standards Release Guide 2003 . d) Amount credited to the beneficiary: Instructed amount . and no account servicing institution is indicated.00 BEN 3. If the Receiver does not service an account for the beneficiary customer. then the Receiver will act upon the customer credit transfer instruction in an appropriate manner of its choice. nor any alternative instructions given.Sender’s charges . then the payment method is called ’serial’. Where more than two financial institutions are involved in the payment chain.MT 103 SWIFTStandards .1 MT 103 Guidelines If the Sender and the Receiver wish to use their direct account relationship in the currency of the transfer. The MT 103 contains only the payment details and the Sender must cover the customer transfer by sending an MT 202 General Financial Institution Transfer to a third bank. This payment method is called ’cover’.Category 1 Example B3: Charging option is BEN a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount = Debit amount EUR 1612.February 2003 . If the Sender and the Receiver have no direct account relationship in the currency of the transfer or do not wish to use their account relationship.Final edition .90 Note: The beneficiary is also advised of the Sender’s charges of GBP 3.

SWIFTPay. 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. MT 103 Field Specifications 1. The MT 103 gives the Sender the ability to identify in the message the level of service requested. the MT 103 supports full charges transparency and structured remittance information. what service is expected from the Receiver for a particular payment. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).SWIFTStandards .February 2003 125 . Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference to the entire message. In order to allow better reconciliation by the Receiver. MT 900.Final edition . Standard or Priority or any other bilaterally agreed service. The message also allows for the inclusion of regulatory information in countries where regulatory reporting is requested.Category 1 MT 103 In order to allow better reconciliation by the beneficiary customer. Standards Release Guide 2003 . eg. 910 and/or 950. 2. the MT 103 gives an unambiguous indication of the interbank amount booked by the Sender/to be booked by the Receiver. USAGE RULES This reference must be quoted in any related confirmation or statement. ie. eg.

ISO 8601).Final edition . where the hour component. placed between slashes (’/’): CLSTIME RNCTIME SNDTIME The time by which the funding payment must be credited. This message contains a credit transfer to be processed according to the SWIFTPay Service Level. This message contains a credit transfer to be processed according to the Priority Service Level. The time at which a TARGET payment has been debited at the sending central bank. expressed in Central European Time (CET). This message contains a credit transfer for test purposes. Time offset is expressed as ’HHMM’. ie. with confirmation.MT 103 SWIFTStandards . must be in the range of 00 through 13.Category 1 CODES One of the following codes may be used. ’HH’. and the minute component. expressed in Central European Time (CET). Any ’HH’ or ’MM’ component outside of these range checks will be disallowed (Error code(s): T16). 3. ’MM’ must be in the range of 00 through 59. 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 . ie. Field 23B: Bank Operation Code FORMAT Option B 4!c (Type) PRESENCE Mandatory DEFINITION This field identifies the type of operation. to the CLS Bank’s account at the central bank. NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). 126 Standards Release Guide 2003 . Sign is either "+" or "-" (Error code(s): T15). CODES One of the following codes must be used (Error code(s): T36): CRED CRTS SPAY SPRI This message contains a credit transfer where there is no SWIFT Service Level involved.February 2003 . The time at which a TARGET payment has been credited at the receiving central bank. expressed in Central European Time (CET).

SWIFTStandards .Final edition . securities transaction. The optional account number line in field 59 must not be used. USAGE RULES The code CRTS should not be used on the FIN network. Standards Release Guide 2003 . ie. Please advise account with institution by the most efficient means of telecommunication. Please advise/contact beneficiary/claimant by the most efficient means of telecommunication.Category 1 MT 103 SSTD This message contains a credit transfer to be processed according to the Standard Service Level. Payment is made in settlement of a trade. Payment is to be made to the beneficiary customer only. pay upon identification. a payment between two companies belonging to the same group. Please advise/contact beneficiary/claimant by phone. foreign exchange deal.February 2003 127 . Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Instruction) (Additional Information) PRESENCE Conditional (C3) DEFINITION This field specifies an instruction. Payment has a related e-Payments reference. Beneficiary customer/claimant will call. The payment is an intra-company payment. Please advise account with institution by phone. Please advise the intermediary institution by the most efficient means of telecommunication. CODES Instruction must contain one of the following codes (Error code(s): T47): SDVA INTC REPA CORT BONL HOLD CHQB PHOB TELB PHON TELE PHOI TELI Payment must be executed with same day value to the beneficiary. Pay beneficiary customer only by cheque. 4. Please advise the intermediary institution by phone. eg.

PHOI. TELE. the codes must appear in the following order (Error code(s): D98): SDVA INTC REPA CORT BONL HOLD CHQB PHOB TELB PHON TELE PHOI TELI When this field is used more than once.Final edition .Category 1 NETWORK VALIDATED RULES Additional Information is only allowed when Instruction Code consists of one of the following codes: PHON. PHOB. HOLD or REPA (Error code(s): D97). TELI. If this field is repeated. the following combinations are not allowed (Error code(s): D67): SDVA SDVA INTC INTC INTC REPA REPA REPA REPA with with with with with with with with with HOLD CHQB BONL HOLD CHQB HOLD CHQB BONL CORT 128 Standards Release Guide 2003 .MT 103 SWIFTStandards .February 2003 . TELB.

pensions. 5. Field 26T: Transaction Type Code FORMAT Option T 3!c (Type) PRESENCE Optional DEFINITION This field identifies the nature of.February 2003 129 . CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. This code is intended for the beneficiary’s bank who should act according to the specifications of the e-payments product. purpose of.SWIFTStandards .Final edition . dividends. Field 32A: Value Date/Currency/Interbank Settled Amount Standards Release Guide 2003 . 6. and/or reason for the individual transaction. USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. eg. salaries.Category 1 MT 103 CORT CORT CORT HOLD PHOB PHON PHOI with with with with with with with BONL HOLD CHQB CHQB TELB TELE TELI If this field is repeated. Code REPA indicates that the payment is the result of an initiation performed via an e-payments product between the customers. the same code word must not be present more than once (Error code(s): E46). USAGE RULES This field may be repeated to give several coded instructions to one or more parties.

it is the amount that the sending bank was instructed to pay. 7. 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. The settlement amount is the amount to be booked/reconciled at interbank level. this amount is the original ordered amount as instructed by the ordering customer. This amount is provided for information purposes and has to be transported unchanged through the transaction chain. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.February 2003 .Category 1 FORMAT Option A 6!n3!a15d (Date) (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the value date. This field must be present when a currency conversion or an exchange has been performed on the Sender’s side. 130 Standards Release Guide 2003 . T43). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. If the transaction is within the scope of the EC Directive on cross border credit transfers. C16) DEFINITION This field specifies the currency and amount of the instruction. T40.Final edition . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. it has to be forwarded unchanged to the next party.MT 103 SWIFTStandards . Field 33B: Currency/Instructed Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Conditional (C2. USAGE RULES If field 33B is present in the message received. T40. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). the currency and the settlement amount. T43). Currency must be a valid ISO 4217 currency code (Error code(s): T52). Otherwise.

either connected or non-connected (Error code(s): T27. T28. 9. NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. field 32A equals 33B.Category 1 MT 103 As a consequence. Field 50a: Ordering Customer FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the customer ordering the transaction. Standards Release Guide 2003 . T43).February 2003 131 . NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. T29. T45). A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. if there are no Sender’s or Receiver’s charges and no currency conversion or exchange took place. USAGE RULES If the account number of the ordering customer is present. if present. USAGE RULES This field must be present when a currency conversion or an exchange has been performed on the Sender’s side. Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C1) DEFINITION This field specifies the exchange rate used to convert the instructed amount specified in field 33B.Final edition .SWIFTStandards . 8. it must be stated in Account.

The content of field 20. cancellations etc. Sender’s reference together with the content of this field provides the message identification which is to be used in case of queries. CODES Party Identifier may be used to indicate a national clearing system code. NETWORK VALIDATED RULES Field 51A is only valid in IFT (Error code(s): D63). Field 52a: Ordering Institution FORMAT Option A Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies the financial institution of the ordering customer. even if field 50a contains an IBAN.Category 1 10. Field 51A: Sending Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field identifies the Sender of the message.MT 103 SWIFTStandards . 11. USAGE RULES At least the first 8 characters of the BIC in this field must be identical to the originator of this IFT message. The following codes may be used preceded by a double slash (’//’): with option A: AT 5!n Austrian Bankleitzahl 132 Standards Release Guide 2003 .Final edition .February 2003 . when different from the Sender.

9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with option D: AT AU BL CC CH CP ES FW GR HK IE IN 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Standards Release Guide 2003 ..Final edition .SWIFTStandards .Category 1 MT 103 AU BL CC ES FW GR HK IE IN IT PT SC 6!n 8!n 9!n 8.February 2003 133 .

T45). T28. T29. The BIC must not be a BEI. MCCO. C7) DEFINITION Where required.Category 1 IT PT RU SC SW SW 10!n 8!n 9!n 6!n 3.5n 6!n Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. MCCO. USAGE RULES The coded information contained in field 52a must be meaningful to the Receiver of the message. T28. ie must not be of subtype BEID. Field 53a: Sender’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Conditional (C4.Final edition . NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. C5. Option D should only be used when the ordering financial institution has no BIC. either connected or non-connected (Error code(s): T27. T29. either connected or non-connected (Error code(s): T27. TESP or TRCO (Error code(s): C05). ie must not be of subtype BEID.. T45).MT 103 SWIFTStandards . 12. TESP or TRCO (Error code(s): C05). this field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. The BIC must not be a BEI. 134 Standards Release Guide 2003 .February 2003 . Option A is the preferred option.

NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.February 2003 135 . In this case. If there is no direct account relationship. and one of these accounts is to be used for reimbursement. in all cases. ie. MT 202/203 or equivalent non-SWIFT must be sent to the financial institution identified in field 53a. the account to be credited or debited must be indicated in field 53a. Field 54a: Receiver’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Conditional (C6 and C7) DEFINITION This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. the Receiver will be paid by its branch in field 53a. Option A is the preferred option.Final edition .SWIFTStandards . T45). between the Sender and the Receiver (or branch of the Receiver when specified in field 54a). when field 53a is present. In those cases where there are multiple direct account relationships. MCCO. between the Sender and the Receiver. Standards Release Guide 2003 . The BIC must not be a BEI. either connected or non-connected (Error code(s): T27. In all other cases. T28. a cover message. then field 53a must be present. using option B with the party identifier only. it must always be a branch of the Sender. TESP or TRCO (Error code(s): C05).Category 1 MT 103 USAGE RULES Absence of this field implies that there is a unique account relationship between the Sender and the Receiver or that the bilaterally agreed account is to be used for settlement. T29. When field 53a is present and contains a branch of the Sender. the relationship between the Sender and the Receiver and the contents of field 54a. in the currency of the transaction. the need for a cover message is dependent on the currency of the transaction. When field 53B is used to specify a branch city name. 13. ie must not be of subtype BEID. The use and interpretation of fields 53a and 54a is. if present. and the Sender intends to send a cover message to the branch of the Receiver. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver. dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. in the currency of the transaction.

14. In those cases where field 54a contains a branch of the Receiver. either connected or non-connected (Error code(s): T27. the Receiver will be paid by the financial institution in field 54a. when the funds are made available to this branch through a financial institution other than that indicated 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 correspondent relationship between the Sender and Receiver relative to that currency. Field 54a containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53a. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. the Receiver will claim reimbursement from its branch. and is not preceded by field 53a. ie must not be of subtype BEID. Field 55a: Third Reimbursement Institution FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Conditional (C8) DEFINITION This field specifies the Receiver’s branch.Final edition . TESP or TRCO (Error code(s): C05). 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. T28. this financial institution. MCCO.MT 103 SWIFTStandards . Option B must only be used with a location. 136 Standards Release Guide 2003 . or field 53a contains an account of the Sender serviced by the Receiver’s branch. T45). the Receiver will claim reimbursement from its branch or will be paid by its branch. In all other cases where field 54a contains a branch of the Receiver. depending on the currency of the transfer and the relationship between the Sender and the Receiver. T29. A branch of the Sender must not appear in field 54a. If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender. The BIC must not be a BEI. the Receiver will be paid by its branch in field 54a. Option A is the preferred option. intermediary reimbursement institution shall be specified in field 54a and field 55a shall contain the Receiver’s branch.February 2003 . ie.Category 1 USAGE RULES When the funds are made available to the Receiver’s branch through a financial institution other than that indicated in field 53a.

The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT NZ 5!n 6!n 8!n 9!n 8. through which the transaction must pass..Category 1 MT 103 USAGE RULES Option A is the preferred option.February 2003 137 . CODES Party Identifier may be used to indicate a national clearing system code.Final edition . Field 56a: Intermediary Institution FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) PRESENCE Conditional (C10) DEFINITION This field specifies the financial institution.SWIFTStandards . between the Receiver and the account with institution. 15.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Standards Release Guide 2003 .

9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) 138 Standards Release Guide 2003 .Category 1 PT RT SC 8!n Portuguese National Clearing Code Pay by Real Time Gross Settlement 6!n UK Domestic Sort Code CODES with options C or D: AT AU BL CC CH CP ES FW GR HK IE IN IT NZ PT RT RU SC SW SW 9!n 6!n 3..MT 103 SWIFTStandards .5n 6!n 5!n 6!n 8!n 9!n 6!n 4!n 8.Final edition ..February 2003 .

Option D must only be used when there is a need to be able to specify a name and address.February 2003 139 . //CP. due to regulatory considerations. If it is used with option A.SWIFTStandards . it should appear only once and in the first of the fields 56a and 57a of the payment instruction. 16.Category 1 MT 103 NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.Final edition . This is applicable even if field 59 or 59A contains an IBAN. T45). T28. If it is used with option C or D. the code //RT should appear in the optional Party Identifier of field 56a or 57a. //IN or //RT is used. TESP or TRCO (Error code(s): C05). Option A is always the preferred option. it may be followed by another domestic clearing code. either connected or non-connected (Error code(s): T27. The following codes may be used preceded by a double slash (’//’): with option A: Standards Release Guide 2003 . When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire.when other than the Receiver . it must not be followed by any other information. T29. The code //RT is binding for the Receiver. ie must not be of subtype BEID. Option C must be used containing a 2!a clearing system code preceded by a double slash ’//’. CODES Party Identifier may be used to indicate a national clearing system code. MCCO. //AU. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS). eg. The BIC must not be a BEI. Field 57a: Account With Institution FORMAT Option A Option B Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Party Identifier) (Name & Address) PRESENCE Conditional (C9 and C11) DEFINITION This field specifies the financial institution .which services the account for the beneficiary customer. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a. USAGE RULES When one of the codes //FW (with or without the 9-digit number).

MT 103 SWIFTStandards .Final edition .February 2003 .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 6!n 6!n UK Domestic Sort Code South African National Clearing Code CODES with options C and D: AT AU BL CC CH CP ES FW 5!n 6!n 8!n 9!n 6!n 4!n 8.9n 9!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number 140 Standards Release Guide 2003 .Category 1 AT AU BL CC ES FW GR HK IE IN IT NZ PT RT SC ZA 5!n 6!n 8!n 9!n 8...

The BIC must not be a BEI.Final edition . Standards Release Guide 2003 . either connected or non-connected (Error code(s): T27.. it should appear only once and in the first of the fields 56a and 57a of the payment instruction. T29. Option D must only be used when there is a need to be able to specify a name and address. T45). eg. The code //RT is binding for the Receiver. Option A is the preferred option. due to regulatory considerations.February 2003 141 . T28. //AU. USAGE RULES When one of the codes //FW (with or without the 9-digit number). it must not be followed by any other information.SWIFTStandards . If it is used with option C or D. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire.Category 1 MT 103 GR HK IE IN IT NZ PT RT RU SC SW SW ZA 7!n 3!n 6!n 11!c 10!n 6!n 8!n HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 9!n 6!n 3. Option C must be used containing a 2!a clearing system code preceded by a double slash ’//’. //CP. MCCO. it may be followed by another domestic clearing code. ie must not be of subtype BEID. US banks require that the code //FW appears in the optional Party Identifier of field 56a or 57a. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS). //IN or //RT is used. the code //RT should appear in the optional Party Identifier of field 56a or 57a. TESP or TRCO (Error code(s): C05). If it is used with option A.5n 6!n 6!n Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) South African National Clearing Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.

If a BEI is specified. CODES The following codes may be used in Account preceded by a double slash (’//’): CH 6!n CHIPS Universal Identifier NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. 142 Standards Release Guide 2003 . Field 59a: Beneficiary Customer FORMAT Option A No letter option [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the customer which will be paid.February 2003 . T45).Category 1 17. 18. USAGE RULES At least the name or the BIC/BEI of the beneficiary customer is mandatory. it must be meaningful for the financial institution that services the account for the beneficiary customer. T29.Final edition .MT 103 SWIFTStandards . T28. Field 70: Remittance Information FORMAT 4*35x (Narrative) PRESENCE Conditional (C14) DEFINITION This field specifies either the details of the individual transaction or a reference to another message containing the details which are to be transmitted to the beneficiary customer. either connected or non-connected (Error code(s): T27.

ie. Transaction charges on the Sender’s side are to be borne by the ordering customer. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Mandatory DEFINITION This field specifies which party will bear the charges for the transaction. if separated with a double slash. transaction charges on the Receiver’s side are to be borne by the beneficiary customer. placed between slashes (’/’): INV IPI RFB ROC Invoice (followed by the date. the Sender must check with the Receiver regarding length restrictions of field 70.Category 1 MT 103 CODES One of the following codes may be used. reference and details of the invoice). this information only needs to be conveyed by the Receiver.Final edition . All transaction charges are to be borne by the ordering customer. Standards Release Guide 2003 . The information specified in this field is intended only for the beneficiary customer. Ordering customer’s reference. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the beneficiary customer. USAGE RULES For national clearing purposes.February 2003 143 . 19. Multiple references can be used. Reference for the beneficiary customer (followed by up to 16 characters).SWIFTStandards . Unique reference identifying a related International Payment Instruction (followed by up to 20 characters). Code must not be repeated between two references of the same kind. ’//’.

21. A decimal comma is mandatory and is included in the maximum length. The integer part of Amount must contain at least one digit. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C15) DEFINITION This field specifies the currency and amount of the transaction charges due to the Receiver. T43). T40. Ie. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). This field may be repeated to specify to the Receiver the currency and amount of charges taken by preceding banks in the transaction chain.Category 1 20. T43). USAGE RULES These fields are conveyed for transparency reasons. the last occurrence always gives the Sender’s charges. T40. the first occurrence of this field specifies the charges of the first bank in the transaction chain that deducted charges. 144 Standards Release Guide 2003 . Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C15) DEFINITION This repetitive field specifies the currency and amount of the transaction charges deducted by the Sender and by previous banks in the transaction chain.Final edition . The net amount after deduction of the Sender’s charges will be quoted as the inter-bank settled amount in field 32A. Charges should be indicated in the order in which they have been deducted from the transaction amount. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The integer part of Amount must contain at least one digit.February 2003 .MT 103 SWIFTStandards . A decimal comma is mandatory and is included in the maximum length. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).

one of the following codes must be used. Instructions following are for the intermediary institution. Each item for which a code exists must start with that code and may be completed with additional information. placed between slashes (’/’): ACC INS INT REC Instructions following are for the account with institution. ie. USAGE RULES This field is conveyed for accounting reasons. Where field 71A indicates OUR payments. which have been prepaid and included in the interbank settlement amount.February 2003 145 . the amount must not equal ’0’ (Error code(s): D57). this field identifies the charges due. The instructing institution which instructed the Sender to execute the transaction. Each code used must be between slashes and appear at the beginning of a line. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative .SWIFTStandards . to facilitate bookkeeping. USAGE RULES Field 72 must never be used for information for which another field is intended. Standards Release Guide 2003 . 22. Instructions following are for the Receiver of the message.Category 1 MT 103 If field 71G is present.Structured Format) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or other party specified. CODES Unless bilaterally agreed otherwise between the Sender and the Receiver.Final edition . It may be followed by additional narrative text.

must start with a double slash ’//’.February 2003 . Narrative text should preferably be the last information in this field. particularly with uncoded instructions.Final edition . it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. The codes REJT/RETN may be used in this field. If either of these codes is used in the first position of the first line. and. must begin on a new line. where bilateral agreements covering the use of codes in this field are in effect. Use of field 72. It is strongly recommended to use the standard codes proposed above. placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. 146 Standards Release Guide 2003 . 23. placed between slashes (’/’).Category 1 Narrative text relating to a preceding code. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. which is continued on the next line(s). In any case. in automated systems. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Optional DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of Receiver or Sender. The information specified must not have been explicitly conveyed in another field.MT 103 SWIFTStandards . the code must conform to the structured format of this field. CODES Where the residence of either ordering customer or beneficiary customer is to be identified. the following codes may be used. the presence of this field will normally require manual intervention. because. may cause delay. if used.

which contains all necessary information to process the rest of the field. Field 77T: Envelope Contents FORMAT Option T 9000z PRESENCE Conditional (C14) DEFINITION This field can contain extended remittance information in different formats. CODES One of the following codes may be used.SWIFTStandards . ie.Category 1 MT 103 24. the code of the validation flag must not be REMIT (Error code(s): G06). It can only be included in messages that are sent and/or received by those customers who have registered for the Extended Remittance Information MUG. The content of the field matches the structure proposed in field 70 of this message.February 2003 147 . If field 77T is not present. The information will start with the UNH-segment. Standards Release Guide 2003 . The content of the field is narrative text. USAGE RULES The presence of this field is subject to a special validation. ’//’. placed between slashes (’/’): ANSI NARR SWIF The content of the field is in the ANSI/X12 format. UEDI NETWORK VALIDATED RULES If the field is used.Final edition . The content of the field is in the UN-EDIFACT format. the Sender must set the validation flag to REMIT in field 119 of the User Header of the message. The content of the field is subject to bilateral agreements between the ordering customer and the Beneficiary. Codes must not be repeated between two references of the same kind. multiple references can be used. if separated with a double slash.

The MT 103+ is a compatible subset of the core MT 103 that is documented separately. are non-financial institutions from the perspective of the Sender. 56 and 57 may only be used with letter option A field 53 may only be used with letter options A and B field 51A is not used in MT 103+. It allows the exchange of single customer credit transfers using a restricted set of fields and format options of the core MT 103 to make it straight through processable. MT 103+ Scope This message type is sent by. codes REJT/RETN must not be used field 72 must not include ERI information.MT 103+ SWIFTStandards . the financial institution of the ordering customer. Party Identifier must be used subfield 1 (Account) of either field 59 or 59A is always mandatory field 72. 54. via an MT 400. no registration in a Message User Group is necessary to send and receive this message. eg. eg. code INS must be followed by a valid BIC field 72. INTC. The differences with the core MT 103 are: appropriate MT 103+ format validation is triggered by the code STP in the validation flag field 119 ({3:{119: STP}}) of the user header of the message (block 3) fields 52. directly or through (a) correspondent(s). M -----> O -----| M 20 Sender’s Reference 16x 1 13C Time Indication /8c/4!n1!x4!n 2 23B Bank Operation Code 4!c 3 148 Standards Release Guide 2003 . cheque.February 2003 . or both.Category 1 MT 103+ Single Customer Credit Transfer The MT 103+ is a General Use message. SDVA and REPA if field 53a is used with option B. MT 103+ Format Specifications To trigger the MT 103+ format validation. ie. the user header of the message (block 3) is mandatory and must contain the code STP in the validation flag field 119 ({3:{119:STP}}). nor to provide the cover for a transaction whose completion was advised separately. This message may only be used for clean payment instructions. or on behalf of. It must not be used to advise the remitting bank of a payment for a clean. This message may only be used on the FIN SWIFT network since it requires special validation field 23E may only contain codes CORT. It is used to convey a funds transfer instruction in which the ordering customer or the beneficiary customer. collection. 55. to the financial institution of the beneficiary customer.Final edition . MT 103+ Single Customer Credit Transfer Status Tag Field Name Content/Options No.

SWIFTStandards .Category 1 MT 103+ Status -----> O -----| O M O O M O O O O O O M O M -----> O -----| O O O Tag Field Name Content/Options No.Final edition .February 2003 149 . 23E Instruction Code 4!c[/30x] 4 26T 32A 33B 36 50a 52A 53a 54A 55A 56A 57A 59a 70 71A Transaction Type Code Value Date/Currency/Interbank Settled Amount Currency/Instructed Amount Exchange Rate Ordering Customer Ordering Institution Sender’s Correspondent Receiver’s Correspondent Third Reimbursement Institution Intermediary Institution Account With Institution Beneficiary Customer Remittance Information Details of Charges 3!c 6!n3!a15d 3!a15d 12d A or K [/1!a][/34x] 4!a2!a2!c[3!c] A or B [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] 4!a2!a2!c[3!c] A or no letter option 4*35x 3!a 5 6 7 8 9 10 11 12 13 14 15 16 17 18 71F Sender’s Charges 3!a15d 19 71G 72 77B Receiver’s Charges Sender to Receiver Information Regulatory Reporting 3!a15d 6*35x 3*35x 20 21 22 Standards Release Guide 2003 .

DE. LI. AT. IT. DK. C2 If the country codes of the Sender’s and the Receiver’s BICs are within the following list: AD. SJ. RE. GI. IE... If field 23B contains one of the codes SSTD or SPAY. SE. CH.Category 1 Status Tag Field Name M = Mandatory O = Optional Content/Options No.MT 103+ SWIFTStandards . 150 Standards Release Guide 2003 . NL. LU.. BE. PM. ES. field 23E may contain only the codes SDVA or INTC (Error code(s): E01). GP. GB. then field 33B is mandatory. GF.. SM. Mandatory Optional Optional Optional Note: See also Network Validated Rule C8 (Error code(s): D51) C3 If field 23B contains the code SPRI. NO..Final edition .. MT 103+ Network Validated Rules C1 If field 33B is present and the currency code is different from the currency code in field 32A. MQ. NOT equal currency code in field 32A Equals currency code in field 32A Not present Not applicable Mandatory Not allowed Not allowed then field 36 is. If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No then field 33B is . PT. BV. IS. GR... Present and currency code in field 33B . FI. field 23E must not be used (Error code(s): E02). otherwise field 33B is optional (Error code(s): D49). field 36 must be present. TF and VA. MC. otherwise field 36 is not allowed (Error code(s): D75). FR.February 2003 . If field 33B is.

.. C7 If field 71A contains OUR.. field 57A must also be present (Error code(s): C81).. SPRI SSTD SPAY Not equal SPRI.Category 1 MT 103+ If field 23B is ....SWIFTStandards . Optional. Mandatory Optional C5 If field 56A is present. If field 23B is . If field 56A is . field 56A must not be present (Error code(s): E16)..February 2003 151 . Standards Release Guide 2003 . both fields 53A and 54A must also be present (Error code(s): E06).....Final edition .. Present Not present Mandatory Optional then field 57A is . SPRI SSTD or SPAY Not allowed Optional then field 56A is . Mandatory Optional and field 54A is .. then field 71F is not allowed and field 71G is optional (Error code(s): E13). SSTD and SPAY then field 23E is .... It may contain only SDVA or INTC Not allowed Not allowed Optional C4 If field 55A is present.. C6 If field 23B contains the code SPRI. Present Not present then field 53A is . If field 55A is .

DK. IS.. RE. LU. GP.. IT. PM. CH... If field 57A is present and the country code of the BIC in 57A is within the above list of country codes. PT. Mandatory (at least one occurrence) and field 71G is .. otherwise field 33B is optional (Error code(s): D51). GI.Category 1 If field 71A is .. MQ. GB. then the following apply: If field 57A is not present. then field(s) 71F is(are) optional and field 71G is not allowed (Error code(s): D50). In all other cases. IE. Optional If field 71A contains SHA... OUR then field 71F is . D50. FI. Not allowed If field 71A contains BEN. Optional and field 71G is .. GF. SJ. DE... LI. the presence of the IBAN (ISO-13616) is optional and its format is not validated in subfield Account of field 59a. BEN then field 71F is .. Not allowed and field 71G is .. C9 The currency code in the fields 71G and 32A must be the same (Error code(s): C02). then at least one occurrence of field 71F is mandatory and field 71G is not allowed (Error code(s): E15). Note 1: The presence of both fields 71F and 71G is also regulated by the Network Validated Rule C7 (Error code(s): E13. GR. NL. then field 33B is mandatory.. SE. BV.. SM. the IBAN (ISO-13616) is mandatory in subfield Account of field 59a (Error code(s): D19). NO. MC. If field 71A is . FR. the IBAN (ISO-13616) is mandatory in subfield Account of field 59a (Error code(s): D19). E15). If field 71A is .. BE.February 2003 .MT 103+ SWIFTStandards . TF and VA. AT. 152 Standards Release Guide 2003 . Not allowed C8 If either field 71F (at least one occurrence) or field 71G is present.Final edition . C10 If the country codes of the Sender’s and the Receiver’s BICs are within the following list: AD.. ES.. Note 2: The presence of field 33B is also regulated by the Network Validated Rule C2 (Error code(s): D49). SHA then field 71F is.

00 in GBP to a beneficiary in the United Kingdom Exchange rate is 1 EUR for 0. Presence of the fields mentioned above is subject to the conditional field rules C1. all occurrences of that field must be taken into account in the formula. If a field is not present.00 (=GBP 3. C7 and C8.1) Transaction charges on the Receiver’s side are GBP 4 (=EUR 6. plus the Receiver’s charges in field 71G. equals the interbank settled amount in field 32A. C2..SWIFTStandards . minus the Sender’s charges in field(s) 71F. Examples: Transaction A Pay the equivalent of EUR 1000.Final edition . If field 71F is present more than once. 36. that field must not be taken into account in the formula. adjusted with the exchange rate in field 36. 71G. No No No No Yes Yes Yes Yes Yes Yes Yes Yes n/a n/a n/a n/a Yes Yes Yes Yes No No No No Mandatory Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Optional Optional MT 103+ Usage Rules Usage Rules for Amount Related Fields There is a relationship between the amount related fields 33B.61999 GBP Transaction charges on the Sender’s side are EUR 5.Category 1 MT 103+ If country code of Sender’s BIC equals one of the listed country codes Yes Yes No No Yes Yes No No Yes Yes No No and country code of Receiver’s BIC equals one of the listed country codes Yes No Yes No Yes No Yes No Yes No Yes No and field 57A is present and country code of field 57A equals one of the listed country codes then an IBAN in subfield Account of field 59a is .45) Standards Release Guide 2003 . 71F and 32A which may be logically expressed in the following formula: The instructed amount in field 33B..February 2003 153 .

99 4.Category 1 Example A1: Charging option is OUR a) Amount debited from the ordering customer’s account: Instructed Amount + Sender’s charges + Receiver’s charges = Debit Amount EUR EUR EUR EUR 1000.45 b) MT 103+ extract: Field Tag 33B 71A 71G 36 32A GBP GBP EUR Content 1000.February 2003 .45 1011. ie.00 0.Final edition .00 154 Standards Release Guide 2003 .00 5.00 5.00 6.99 c) The subsequent MT 950 shows one debit entry for GBP 623.99.00 619. field 32A.99 Example A2: Charging option is SHA a) Amount debited from the ordering customer’s account: Instructed amount + Sender’s charges = Debit amount EUR EUR EUR 1000.MT 103+ SWIFTStandards . d) Amount credited to the beneficiary: Interbank settlement amount .00 OUR 4.00 1005.Receiver’s charges = Credit amount GBP GBP GBP 623.61999 623.

Category 1 MT 103+ b) MT 103+ extract: Field Tag 33B 71A 36 32A GBP EUR Content 1000.February 2003 155 . ie.99 c) The subsequent MT 950 shows one debit entry for GBP 619.00 b) MT 103+ extract: Field Tag 33B 71A 71F 36 32A GBP GBP EUR Content 1000.SWIFTStandards .00 BEN 3.99.99 4.89. Standards Release Guide 2003 .00 615.61999 619. field 32A.Receiver’s charges = Credit amount GBP GBP GBP 619.89 c) The subsequent MT 950 shows one debit entry for GBP 616.00 SHA 0.Final edition .1 0. field 32A.61999 616. ie.99 Example A3: Charging option is BEN a) Amount debited from the ordering customer’s account: Instructed amount = Debit amount EUR 1000. d) Amount credited to the beneficiary: Interbank settlement amount .

1 4.00 612.89 Note: The beneficiary is also advised of the Sender’s charges of GBP 3.MT 103+ SWIFTStandards .February 2003 .00 to a beneficiary in the United Kingdom Exchange rate is 1 EUR for 0.Category 1 d) Amount credited to the beneficiary: Equivalent of Instructed amount .99 3.00 6.38 b) MT 103+ extract Field Tag 33B 71A 71G 32A GBP GBP GBP Content 1000 OUR 4.45 1624.45) The ordering customer has an account in euro Sender and Receiver’s BIC are within the EU-country list Example B1: Charging option is OUR a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount + Sender’s charges + Receiver’s charges = Debit amount EUR EUR EUR EUR 1612.00 1004.93 5.1 Examples: Transaction B Pay GBP 1000.61999 GBP Transaction charges on the Sender’s side are EUR 5.Sender’s charges . 156 Standards Release Guide 2003 .Final edition .00 (=GBP 3.Receiver’s charges = Credit amount GBP GBP GBP GBP 619.00 (=EUR 6.1) Transaction charges on the Receiver’s side are GBP 4.

Category 1 MT 103+ Note: field 36 does not have to be used since currency in fields 32A and 33B is the same c) The subsequent MT 950 shows one debit entry for GBP 1004.00 4. field 32A.00 1617. c) The subsequent MT 950 shows one debit entry for GBP 1000.00 Example B2: Charging option is SHA a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount + Sender’s charges = Debit amount EUR EUR EUR 1612.00 996.SWIFTStandards .93 5.Final edition . field 32A. d) Amount credited to the beneficiary: Amount in 32A .93 b) MT 103+ extract: Field Tag 71A 32A GBP Content SHA 1000.Receiver’s charges = Credit amount GBP GBP GBP 1000.00 e) Note: field 36 does not have to be used since currency in fields 32A and 33B is the same Standards Release Guide 2003 .February 2003 157 . d) Amount credited to the beneficiary: Instructed amount = Credit amount GBP 1000. ie. ie.

field 32A.90 Note: The beneficiary is also advised of the Sender’s charges of GBP 3.00 992.Final edition . In order to allow better reconciliation by the beneficiary customer.Sender’s charges . then the payment method is called ’serial’.1 MT 103+ Guidelines If the Sender and the Receiver wish to use their direct account relationship in the currency of the transfer.90 c) The subsequent MT 950 shows one debit entry for GBP 996.00 3. Where more than two financial institutions are involved in the payment chain.MT 103+ SWIFTStandards . This payment method is called ’cover’. then third banks will be involved to cover the transaction. If the Sender and the Receiver have no direct account relationship in the currency of the transfer or do not wish to use their account relationship. then the MT 103+ message will contain the cover for the customer transfer as well as the payment details. the MT 103+ supports full charges transparency and structured remittance information. the MT 103+ gives an unambiguous indication of the interbank 158 Standards Release Guide 2003 . The MT 103+ contains only the payment details and the Sender must cover the customer transfer by sending an MT 202 General Financial Institution Transfer to a third bank.February 2003 .00 BEN 3.10 4.9 ie. d) Amount credited to the beneficiary: Instructed amount . In order to allow better reconciliation by the Receiver. and if the MT 103+ is sent from one financial institution to the next financial institution in this chain.Receiver’s charges = Credit amount GBP GBP GBP GBP 1000.Category 1 Example B3: Charging option is BEN a) Amount debited from the ordering customer’s account: Debit on EUR-account Equivalent of Instructed amount = Debit amount EUR 1612.10 996.93 b) MT 103+ extract: Field Tag 33B 71A 71F 32A GBP GBP GBP Content 1000.

ie.February 2003 159 . MT 103+ Field Specifications 1. Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference to the entire message. with confirmation. 910 and/or 950. Standards Release Guide 2003 .Final edition . SWIFTPay. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). USAGE RULES This reference must be quoted in any related confirmation or statement.SWIFTStandards . The message also allows for the inclusion of regulatory information in countries where regulatory reporting is requested. 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. MT 900. to the CLS Bank’s account at the central bank. The MT 103+ gives the Sender the ability to identify in the message the level of service requested. what service is expected from the Receiver for a particular payment. Standard or Priority or any other bilaterally agreed service. 2.Category 1 MT 103+ amount booked by the Sender/to be booked by the Receiver. CODES One of the following codes may be used. placed between slashes (’/’): CLSTIME The time by which the funding payment must be credited. eg. eg. expressed in Central European Time (CET).

MT 103+

SWIFTStandards - Category 1

RNCTIME SNDTIME

The time at which a TARGET payment has been credited at the receiving central bank, expressed in Central European Time (CET). The time at which a TARGET payment has been debited at the sending central bank, expressed in Central European Time (CET).

NETWORK VALIDATED RULES Time indication must be a valid time expressed as HHMM (Error code(s): T38). Sign is either "+" or "-" (Error code(s): T15). Time offset is expressed as ’HHMM’, where the hour component, ie, ’HH’, must be in the range of 00 through 13, and the minute component, ie, ’MM’ must be in the range of 00 through 59. Any ’HH’ or ’MM’ component outside of these range checks will be disallowed (Error code(s): T16). USAGE RULES The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated Universal Time - ISO 8601).

3. Field 23B: Bank Operation Code
FORMAT Option B 4!c (Type)

PRESENCE Mandatory DEFINITION This field identifies the type of operation. CODES One of the following codes must be used (Error code(s): T36): CRED CRTS SPAY SPRI SSTD This message contains a credit transfer where there is no SWIFT Service Level involved. This message contains a credit transfer for test purposes. This message contains a credit transfer to be processed according to the SWIFTPay Service Level. This message contains a credit transfer to be processed according to the Priority Service Level. This message contains a credit transfer to be processed according to the Standard Service Level.

160

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 103+

USAGE RULES The code CRTS should not be used on the FIN network.

4. Field 23E: Instruction Code
FORMAT Option E 4!c[/30x] (Instruction)

PRESENCE Conditional (C3) DEFINITION This field specifies an instruction. CODES Instruction must contain one of the following codes (Error code(s): T48): SDVA INTC REPA CORT Payment must be executed with same day value to the beneficiary. The payment is an intra-company payment, ie, a payment between two companies belonging to the same group. Payment has a related e-Payments reference. Payment is made in settlement of a trade, eg, foreign exchange deal, securities transaction.

NETWORK VALIDATED RULES Additional Information is only allowed when Instruction Code consists of the following code: REPA (Error code(s): D97). If this field is repeated, the codes must appear in the following order (Error code(s): D98): SDVA INTC REPA CORT

When this field is used more than once, the following combinations are not allowed (Error code(s): D67). REPA with CORT

Standards Release Guide 2003 - Final edition - February 2003

161

MT 103+

SWIFTStandards - Category 1

If this field is repeated, the same code word must not be present more than once (Error code(s): E46). USAGE RULES This field may be repeated to give several coded instructions to one or more parties. Code REPA indicates that the payment is the result of an initiation performed via an e-payments product between the customers. This code is intended for the beneficiary’s bank who should act according to the specifications of the e-payments product.

5. Field 26T: Transaction Type Code
FORMAT Option T 3!c (Type)

PRESENCE Optional DEFINITION This field identifies the nature of, purpose of, and/or reason for the individual transaction, eg, salaries, pensions, dividends. CODES Codes from the EUROSTAT list "Code List for Balance of Payments Collection Systems" may be used in this field. USAGE RULES The information given is intended both for regulatory and statutory requirements and/or to provide information to the beneficiary customer on the nature of the transaction. In case the Receiver of the message is not legally obliged to forward the information to a regulatory body, he is allowed to ignore the content of this field.

6. Field 32A: Value Date/Currency/Interbank Settled Amount
FORMAT Option A 6!n3!a15d (Date) (Currency) (Amount)

PRESENCE Mandatory DEFINITION This field specifies the value date, the currency and the settlement amount. The settlement amount is the amount to be booked/reconciled at interbank level.

162

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 103+

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

7. Field 33B: Currency/Instructed Amount
FORMAT Option B 3!a15d (Currency) (Amount)

PRESENCE Conditional (C2, C8) DEFINITION This field specifies the currency and amount of the instruction. This amount is provided for information purposes and has to be transported unchanged through the transaction chain. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03, T40, T43). USAGE RULES If field 33B is present in the message received, it has to be forwarded unchanged to the next party. This field must be present when a currency conversion or an exchange has been performed on the Sender ’s side. If the transaction is within the scope of the EC Directive on cross border credit transfers, this amount is the original ordered amount as instructed by the ordering customer. Otherwise, it is the amount that the sending bank was instructed to pay. As a consequence, if there are no Sender’s or Receiver’s charges and no currency conversion or exchange took place, field 32A equals 33B, if present.

8. Field 36: Exchange Rate
FORMAT 12d (Rate)

Standards Release Guide 2003 - Final edition - February 2003

163

MT 103+

SWIFTStandards - Category 1

PRESENCE Conditional (C1) DEFINITION This field specifies the exchange rate used to convert the instructed amount specified in field 33B. NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40, T43). USAGE RULES This field must be present when a currency conversion or an exchange has been performed on the Sender’s side.

9. Field 50a: Ordering Customer
FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address)

PRESENCE Mandatory DEFINITION This field specifies the customer ordering the transaction. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45). USAGE RULES If the account number of the ordering customer is present, it must be stated in Account.

10. Field 52A: Ordering Institution
FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC)

PRESENCE Optional

164

Standards Release Guide 2003 - Final edition - February 2003

11.SWIFTStandards . T28. USAGE RULES The coded information contained in field 52A must be meaningful to the Receiver of the message. when different from the Sender. CODES Party Identifier may be used to indicate a national clearing system code..February 2003 165 .Category 1 MT 103+ DEFINITION This field specifies the financial institution of the ordering customer.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. TESP or TRCO (Error code(s): C05). ie must not be of subtype BEID. T29. T45). The BIC must not be a BEI. The following codes may be used preceded by a double slash (’//’): AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8. either connected or non-connected (Error code(s): T27.Final edition . MCCO. even if field 50a contains an IBAN. Field 53a: Sender’s Correspondent Standards Release Guide 2003 .

the account to be credited or debited must be indicated in field 53B with the party identifier only. a cover message. If there is no direct account relationship. ie. Field 54A: Receiver’s Correspondent FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) 166 Standards Release Guide 2003 .MT 103+ SWIFTStandards . The BIC must not be a BEI.February 2003 . A branch of the Receiver may appear in field 53A if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver. Party Identifier must be present in field 53B (Error code(s): E04). NETWORK VALIDATED RULES If field 53a is present with option B. and the Sender intends to send a cover message to the branch of the Receiver. When field 53A is present and contains a branch of the Sender. if present. T28. In this case. TESP or TRCO (Error code(s): C05). 12. USAGE RULES Absence of this field implies that there is a unique account relationship between the Sender and the Receiver or that the bilaterally agreed account is to be used for settlement. the Receiver will be paid by its branch in field 53A. dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. MT 202/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. ie must not be of subtype BEID. then field 53a must be present with option A. in the currency of the transaction. either connected or non-connected (Error code(s): T27. when field 53A is present. T45). The BIC must be a SWIFT registered address.Category 1 FORMAT Option A Option B [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] (Party Identifier) (BIC) (Party Identifier) (Location) PRESENCE Conditional (C4) DEFINITION Where required. this field specifies the account or branch of the Sender or another financial institution through which the Sender will reimburse the Receiver. between the Sender and the Receiver (or branch of the Receiver when specified in field 54A).Final edition . MCCO. In those cases where there are multiple direct account relationships. and one of these accounts is to be used for reimbursement. in all cases. T29. between the Sender and the Receiver. In all other cases. in the currency of the transaction. the relationship between the Sender and the Receiver and the contents of field 54A. the need for a cover message is dependent on the currency of the transaction.

ie. TESP or TRCO (Error code(s): C05). In those cases where field 54A contains a branch of the Receiver. and is not preceded by field 53A.Final edition . this financial institution. If the branch of the Sender or other financial institution specified in field 53A is also the account servicer for the Receiver. T29. the Receiver will be paid by its branch in field 54A. A branch of the Sender must not appear in field 54A. MCCO. The use and interpretation of fields 53a and 54A is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. Standards Release Guide 2003 . The BIC must not be a BEI.SWIFTStandards . Field 54A containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53A. the Receiver will be paid by the financial institution in field 54A. T45). either connected or non-connected (Error code(s): T27. the Receiver will claim reimbursement from its branch.February 2003 167 . when the funds are made available to this branch through a financial institution other than that indicated in field 53A. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. In all other cases where field 54A contains a branch of the Receiver. intermediary reimbursement institution shall be specified in field 54A and field 55A shall contain the Receiver’s branch. T28.Category 1 MT 103+ PRESENCE Conditional (C4) DEFINITION This field specifies the branch of the Receiver or another financial institution at which the funds will be made available to the Receiver. depending on the currency of the transfer and the relationship between the Sender and the Receiver. or field 53B contains an account of the Sender serviced by the Receiver’s branch. the Receiver will claim reimbursement from its branch or will be paid by its branch. If field 54A contains a branch of the Receiver and field 53A contains a branch of the Sender. field 54A must not be present. 13. Field 55A: Third Reimbursement Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field specifies the Receiver’s branch. ie must not be of subtype BEID. USAGE RULES When the funds are made available to the Receiver’s branch through a financial institution other than that indicated in field 53A.

The BIC must not be a BEI. Field 56A: Intermediary Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Conditional (C6) DEFINITION This field specifies the financial institution. The following codes may be used preceded by a double slash (’//’): AT AU BL CC ES FW GR HK IE IN IT NZ PT 5!n 6!n 8!n 9!n 8. T29.MT 103+ SWIFTStandards . through which the transaction must pass.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code 168 Standards Release Guide 2003 . 14. between the Receiver and the account with institution.Final edition . TESP or TRCO (Error code(s): C05). either connected or non-connected (Error code(s): T27. T28. CODES Party Identifier may be used to indicate a national clearing system code. T45).. MCCO.February 2003 . ie must not be of subtype BEID.Category 1 NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.

It must not be followed by any other information.SWIFTStandards . T28. This is applicable even if field 59 or 59A contains an IBAN. TESP or TRCO (Error code(s): C05). The code //RT is binding for the Receiver.February 2003 169 . US banks require that the code //FW appears in the optional Party Identifier of field 56A or 57A.Final edition . 15. T29. The following codes may be used preceded by a double slash (’//’): AT AU BL CC 5!n 6!n 8!n 9!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Standards Release Guide 2003 . ie must not be of subtype BEID. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS). it should appear only once and in the first of the fields 56A and 57A of the payment instruction. T45). //AU.which services the account for the beneficiary customer. Field 57A: Account With Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) PRESENCE Conditional (C5) DEFINITION This field specifies the financial institution . MCCO.when other than the Receiver . either connected or non-connected (Error code(s): T27. CODES Party Identifier may be used to indicate a national clearing system code.Category 1 MT 103+ RT SC 6!n Pay by Real Time Gross Settlement UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. The BIC must not be a BEI. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. USAGE RULES When one of the codes //FW. //IN or //RT is used. the code //RT should appear in the optional Party Identifier of field 56A or 57A.

//IN or //RT is used. TESP or TRCO (Error code(s): C05). T28.Final edition .Category 1 ES FW GR HK IE IN IT NZ PT RT SC 8. //AU. It must not be followed by any other information.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Pay by Real Time Gross Settlement 6!n UK Domestic Sort Code NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. T29. it should appear only once and in the first of the fields 56A and 57A of the payment instruction. Field 59a: Beneficiary Customer FORMAT Option A No letter option [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) 170 Standards Release Guide 2003 . 16.. T45). US banks require that the code //FW appears in the optional Party Identifier of field 56A or 57A. MCCO. When it is necessary that an incoming SWIFT payment be made to the party in this field via Fedwire. The code //RT is binding for the Receiver. USAGE RULES When one of the codes //FW. ie must not be of subtype BEID. the code //RT should appear in the optional Party Identifier of field 56A or 57A. either connected or non-connected (Error code(s): T27. When it is necessary that an incoming SWIFT payment be made to the intermediary or the account with institution via real-time gross settlement (RTGS).MT 103+ SWIFTStandards .February 2003 . The BIC must not be a BEI.

Unique reference identifying a related International Payment Instruction (followed by up to 20 characters).Category 1 MT 103+ PRESENCE Mandatory DEFINITION This field specifies the customer which will be paid.February 2003 171 . T28. The BIC/BEI must be a SWIFT registered address. T29. T45). USAGE RULES At least the name or the BEI of the beneficiary customer is mandatory. T73). either connected or non-connected (Error code(s): T27. CODES The following codes may be used in Account preceded by a double slash (’//’): CH 6!n CHIPS Universal Identifier NETWORK VALIDATED RULES Account must be present. CODES One of the following codes may be used.Final edition . the IBAN must be a valid IBAN (ISO-13616) (Error code(s): D19. (Error code(s): E10). Standards Release Guide 2003 . it must be meaningful for the financial institution that services the account for the beneficiary customer. placed between slashes (’/’): INV IPI Invoice (followed by the date. Field 70: Remittance Information FORMAT 4*35x (Narrative) PRESENCE Optional DEFINITION This field specifies either the details of the individual transaction or a reference to another message containing the details which are to be transmitted to the beneficiary customer.SWIFTStandards . If a BEI is specified. If an IBAN must be present in Account (C10). reference and details of the invoice). 17.

18. All transaction charges are to be borne by the ordering customer.Category 1 RFB ROC Reference for the beneficiary customer (followed by up to 16 characters). Transaction charges on the Sender’s side are to be borne by the ordering customer. Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) 172 Standards Release Guide 2003 . The information specified in this field is intended only for the beneficiary customer. this information only needs to be conveyed by the Receiver. transaction charges on the Receiver’s side are to be borne by the beneficiary customer. Ordering customer’s reference. the Sender must check with the Receiver regarding length restrictions of field 70. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Mandatory DEFINITION This field specifies which party will bear the charges for the transaction. Code must not be repeated between two references of the same kind. ie. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the beneficiary customer. USAGE RULES For national clearing purposes.Final edition . 19.February 2003 . if separated with a double slash.MT 103+ SWIFTStandards . ’//’. Multiple references can be used.

The integer part of Amount must contain at least one digit.SWIFTStandards . USAGE RULES These fields are conveyed for transparency reasons. T40.February 2003 173 . T43). the amount must not equal ’0’ (Error code(s): D57). T43). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The integer part of Amount must contain at least one digit.Category 1 MT 103+ PRESENCE Conditional (C7) DEFINITION This repetitive field specifies the currency and amount of the transaction charges deducted by the Sender and by previous banks in the transaction chain. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). T40. Standards Release Guide 2003 . If field 71G is present. Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C7) DEFINITION This field specifies the currency and amount of the transaction charges due to the Receiver. 20. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). A decimal comma is mandatory and is included in the maximum length. Charges should be indicated in the order in which they have been deducted from the transaction amount. the first occurrence of this field specifies the charges of the first bank in the transaction chain that deducted charges. the last occurrence always gives the Sender’s charges.Final edition . The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Ie. This field may be repeated to specify to the Receiver the currency and amount of charges taken by preceding banks in the transaction chain. The net amount after deduction of the Sender’s charges will be quoted as the inter-bank settled amount in field 32A. A decimal comma is mandatory and is included in the maximum length.

ie. to facilitate bookkeeping. T28.Structured Format) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or other party specified.Category 1 USAGE RULES This field is conveyed for accounting reasons. it must be followed by a valid BIC and be the only information on that line (Error code(s): T27.MT 103+ SWIFTStandards . T45.February 2003 . If the code /INS/ is used anywhere else than at the beginning of a line. In this case. If the code /INS/ is present at the beginning of a line. this field identifies the charges due. 21.Final edition . T46). NETWORK VALIDATED RULES If the code /INS/ is used at the beginning of a line. which have been prepaid and included in the interbank settlement amount. the following code may be used. it must not be used again at the beginning of any other line (Error code(s): T47). T44. placed between slashes (’/’): INS The instructing institution which instructed the Sender to execute the transaction. CODES Unless bilaterally agreed otherwise between the Sender and the Receiver. The codes /REJT/ or /RETN/ must not be used in this field (Error code(s): T81). there is no validation of the following BIC either. This field must not include ERI (Error code(s): T82). it is treated as free text and is ignored as far as validation is concerned. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative . Where field 71A indicates OUR payments. T29. 174 Standards Release Guide 2003 .

In any case.February 2003 175 . Each code used must be between slashes and appear at the beginning of a line. which is continued on the next line(s).Category 1 MT 103+ USAGE RULES Field 72 must never be used for information for which another field is intended. CODES When the residence of either ordering customer or beneficiary customer is to be identified. placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. Each item for which a code exists must start with that code and may be completed with additional information.Final edition . the following codes may be used. 22.SWIFTStandards . The information specified must not have been explicitly conveyed in another field. Standards Release Guide 2003 . the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Optional DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of Receiver or Sender. and. Use of field 72 with uncoded instructions is not allowed. must start with a double slash ’//’. where bilateral agreements covering the use of codes in this field are in effect. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. the code must conform to the structured format of this field. It is strongly recommended to use the standard code proposed above. Narrative text relating to a preceding code. must begin on a new line. if used. Narrative text should preferably be the last information in this field. It may be followed by additional narrative text.

Category 1 In case the Receiver of the message is not legally obliged to forward the information to a regulatory body. he is allowed to ignore the content of this field.Final edition . 176 Standards Release Guide 2003 .February 2003 .MT 103+ SWIFTStandards .

SWIFTStandards - Category 1

MT 104

MT 104 Direct Debit and Request for Debit Transfer Message
Note: The use of this message type requires Message User Group (MUG) registration(s).

MT 104 Scope
The MT 104 is used to convey customer direct debit instructions between financial institutions. The MT 104 can be: sent by the creditor’s bank, or another financial institution, to the debtor’s bank, or another financial institution, on behalf of the creditor/instructing party to order the debit of the debtor’s account and to collect payment from this account. or sent between two financial institutions on behalf of a creditor/instructing party to request the direct debit of the debtor’s account in the Receiver’s country and subsequently to credit the creditor’s account maintained by the Receiver or one of its branches.

MT 104 Format Specifications
The MT 104 consists of three 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 mandatory sequence; each occurrence provides details of one individual transaction. Sequence C Settlement Details is a single occurrence optional sequence. When the message is used as a Request for Direct Debit message, this sequence is not used. When the message is used as a Direct Debit message, this sequence is mandatory and provides further settlement information for all transactions mentioned in sequence B. MT 104 Direct Debit and Request for Debit Transfer Message Status Tag Field Name Content/Options No.

Mandatory Sequence A General Information M O O O M O O O 20 21R 23E 21E 30 51A 50a 50a Sender’s Reference Customer Specified Reference Instruction Code Registration Reference Requested Execution Date Sending Institution Instructing Party Creditor 16x 16x 4!c[/30x] 35x 6!n [/1!a][/34x] 4!a2!a2!c[3!c] C or L A or K 1 2 3 4 5 6 7 8

Standards Release Guide 2003 - Final edition - February 2003

177

MT 104

SWIFTStandards - Category 1

Status O O O O O

Tag 52a 26T 77B 71A 72 Creditor’s Bank

Field Name

Content/Options A, C or D 3!c

No. 9 10

Transaction Type Code Regulatory Reporting Details of Charges Sender to Receiver Information

3*35x 11 3!a 12 6*35x 13

-----> Mandatory Repetitive Sequence B Transaction Details M O O O O M O O O O M O 21 23E 21C 21D 21E 32B 50a 50a 52a 57a 59a 70 Transaction Reference Instruction Code Mandate Reference Direct Debit Reference Registration Reference Currency and Transaction Amount Instructing Party Creditor Creditor’s Bank Debtor’s Bank Debtor Remittance Information 16x 14 4!c[/30x] 15 35x 16 35x 17 35x 18 3!a15d 19 C or L 20 A or K 21 A, C or D 22 A, C or D 23 A or no option letter 24 4*35x 25

178

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 104

Status O O O O O O O -----|

Tag 26T 77B 33B 71A 71F 71G 36

Field Name Transaction Type Code Regulatory Reporting Currency/Original Ordered Amount Details of Charges Sender’s Charges Receiver’s Charges Exchange Rate 3!c

Content/Options

No. 26

3*35x 27 3!a15d 28 3!a 29 3!a15d 30 3!a15d 31 12d 32

Optional Sequence C Settlement Details M O O O O 32B 19 71F 71G 53a Currency and Settlement Amount Sum of Amounts Sum of Sender’s Charges Sum of Receiver’s Charges Sender’s Correspondent M = Mandatory O = Optional 3!a15d 33 17d 34 3!a15d 35 3!a15d 36 A or B 37

MT 104 Network Validated Rules
C1 If field 23E is present in sequence A and contains RFDD then field 23E must be present in all occurrences of sequence B. If field 23E is present in sequence A and does not contain RFDD then field 23E must not be present in any occurrence of sequence B. If field 23E is not present in sequence A then field 23E must be present in all occurrences of sequence B (Error code(s): C75):

Standards Release Guide 2003 - Final edition - February 2003

179

MT 104

SWIFTStandards - Category 1

Sequence A if field 23E is... Present and equals RFDD Present and not equals RFDD Not present

Sequence B then field 23E is... Mandatory in all occurrences Not allowed Mandatory in all occurrences

C2 Field 50a (option A or K), must be present in either sequence A (index 8) or in each occurrence of sequence B (index 21), but must never be present in both sequences, nor be absent from both sequences (Error code(s): C76). Sequence A if field 50a (option A or K) is... Present Not present In every occurrence of Sequence B then field 50a (option A or K) is... Not allowed Mandatory in all occurrences

C3 When present in sequence A, fields 21E, 26T, 52a, 71A, 77B and 50a (option C or L) must, independently of each other, not be present in any occurrence of sequence B. When present in one or more occurrences of sequence B, fields 21E, 26T, 52a, 71A, 77B and 50a (option C or L) must not be present in sequence A (Error code(s): D73). Sequence A if field 26T is... Present Not present Not allowed Optional Sequence B then field 26T is...

Sequence A if field 77B is... Present Not present Not allowed Optional

Sequence B then field 77B is...

Sequence A if field 71A is... Present Not present Not allowed Optional

Sequence B then field 71A is...

180

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 104

Sequence A if field 52a is... Present Not present Not allowed Optional

Sequence B then field 52a is...

Sequence A if field 21E is... Present Not present Not allowed Optional

Sequence B then field 21E is...

Sequence A if field 50a (option C or L) is... Present Not present

Sequence B then field 50a (option C or L) is... Not allowed Optional

C4 If field 21E is present in sequence A, then the second occurrence of field 50a (option A or K), must also be present in sequence A. In each occurrence of sequence B, if field 21E is present, then the second occurrence of field 50a (option A or K), must also be present in the same occurrence (Error code(s): D77): Sequence A if field 21E is... Present Not present Sequence A then field 50a (option A or K) is... Mandatory Optional (See C2)

Sequence B if field 21E is... Present Not present

Sequence B then field 50a (option A or K) is... Mandatory Optional (See C2, C12)

C5

Standards Release Guide 2003 - Final edition - February 2003

181

Category 1 In sequence A. :33B:USD2. then it must also be present in sequence C.Final edition . C6 If field 71F is present in one or more occurrence of sequence B..ie field 23E not present. :33B:USD0001... Sequence B if field 71G is. or both. :33B:USD1. if field 23E is present and contains RTND then field 72 must be present.. Sequence B if field 71F is.. then it must also be present in Sequence C.00 182 Standards Release Guide 2003 .. and vice-versa (Error code(s): D79).. and vice-versa (Error code(s): D79). must be different between fields 33B and 32B (Error code(s): D21).February 2003 .field 72 is not allowed (Error code(s): C82): Sequence A if field 23E is. Invalid :32B:USD1. Examples: Valid :32B:USD1. or field 23E does not contain RTND . if field 33B is present then the currency code or the amount. If field 71G is present in one or more occurrence of sequence B. C7 In each occurrence of sequence B.. :32B:USD1..... Present and equals RTND Present and not equals RTND Not present Mandatory Not allowed Not allowed Sequence A then field 72 is. Present Not present Mandatory Not allowed Sequence C then field 71F is. :33B:BEF1. in all other cases . Present Not present Mandatory Not allowed Sequence C then field 71G is.MT 104 SWIFTStandards . :32B:USD1.

. 71G must not be present and sequence C must not be present.. 52a. 71F. 71F and 71G are. if field 23E is present and contains RFDD. C11 The currency code in fields 32B and 71G in sequences B and C must be the same for all occurrences of these fields in the message (Error code(s): C02). then field 36 must be present. C10 If field 19 is present in sequence C then it must be equal to the sum of the amounts in all occurrences of field 32B in sequence B (Error code(s): C01).. Otherwise. then: in sequence A field 21R is optional and in sequence B the fields 21E. C8 In any occurrence of sequence B. Optional Not allowed Not allowed Sequence B and fields 21E.Final edition .. if field 33B is present and the currency codes in fields 32B and 33B are different. Present and equals RFDD Present and not equals RFDD Not present Sequence A then field 21R is. 50a (option A or K). 50a (option A or K).Category 1 MT 104 Valid :32B:USD1. :33B:BEF2. then field 19 must not be present.February 2003 183 . (Error code(s): C96) Sequence A if field 23E is. Invalid :32B:USD1. 71G are optional and sequence C must be present. 50a (option A or K). 52a. Otherwise field 19 must be present (Error code(s): D80). ie.00 :33B:USD0001.. 71F.. Not allowed Optional Optional and sequence C is. The currency code in the charges fields 71F (in sequences B and C) must be the same for all occurrences of these fields in the message (Error code(s): C02) C12 In sequence A. 52a... in sequence A field 23E does not contain RFDD or field 23E is not present: in sequence A field 21R must not be present and in sequence B the fields 21E. C9 If sequence C is present and if the amount in field 32B of sequence C is equal to the sum of the amounts of the fields 32B of sequence B. Not allowed Mandatory Mandatory Standards Release Guide 2003 .SWIFTStandards . field 36 must not be present (Error code(s): D75). Otherwise.

depending on the business scenario for which the message is used. then field 119 of User Header must not be present (Error code(s): C94). he must not use the validation flag -field 119 of the User Header.. The Direct Debit MUG. allows its subscribers to exchange Direct Debit instructions via an MT 104. The MT 104 under the "Direct Debit Order" MUG 184 Standards Release Guide 2003 . then field 119 of User Header must be present and contain RFDD.. Depending on the MUG that is used.February 2003 . proceeds of these Direct Debits being directly credited to a customer’s account maintained at the Receiver. If field 23E in sequence A is not present or does not contain RFDD. Sequence A if field 23E is. The Request for Direct Debit MUG allows its subscribers to exchange request for Direct Debit instructions via an MT 104.of the message..Category 1 C13 If field 23E in sequence A is present and contains RFDD.MT 104 SWIFTStandards . If the Sender has registered in the Request for Direct Debit MUG and wants to send a Request for Direct Debit message. Present and equals RFDD Present and not equals RFDD Not present User Header then field 119 is.. certain fields are subject to special validation (see network validated rules and field specifications). Mandatory and must contain RFDD Not allowed Not allowed MT 104 Guidelines The MT 104 message can be exchanged in two different Message Users Groups (MUGs).of the message to "RFDD" which indicates that the message is a Request for Direct Debit. If the Sender has registered in the Direct Debit MUG and wants to send a Direct Debit message. he must set the validation flag -field 119 of the User Header. They can only be used by the institutions who have registered in the corresponding MUG. proceeds of the Direct Debits being credited to the Sender’s account at the Receiver and ultimately to the Ordering Customer/Instructing Party.Final edition .

Category 1 MT 104 In this scenario there can be one or several instructing parties and one or several ordering customers ordering direct debits to be processed in the receiving country with a repatriation of funds on sending bank’s account and then on the creditor’s account.SWIFTStandards . The MT 104 under the "Request for Direct Debit" MUG Standards Release Guide 2003 .February 2003 185 .Final edition .

... when it is not present: If the following party is missing. Sender (S) in the Direct Debit scenario Receiver (R) in the Request for Direct Debit Creditor (field 50A or 50K) Receiver (R) 186 Standards Release Guide 2003 . The first column of the table below shows the parties that can be omitted in an MT 104.Category 1 The parties mentioned in the chain are not necessarily different entities.MT 104 SWIFTStandards .February 2003 .Final edition . The second column specifies the party which assumes the role of the party in the first column. Creditor’s bank (field 52a) Instructing Party (field 50C or 50L) Debtor’s bank (field 57a) Their function is assumed by..

MT 104 Field Specifications 1. 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. The MT 104 Checklist at the end of this chapter is recommended as a guide for institutions in the setup of their agreements. Standards Release Guide 2003 . when the instructing party is not present. cancellations. USAGE RULES This field must be unique for each message and is part of the file identification and transaction identification which is used in case of queries. Amongst other things.SWIFTStandards . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.February 2003 187 . etc.Category 1 MT 104 The use of the MT 104 is subject to bilateral/multilateral agreements between the Sender and the Receiver. Field 21R : Customer Specified Reference FORMAT Option R 16x PRESENCE Conditional (C12) DEFINITION This field specifies the reference to the entire message assigned by either the: instructing party.Final edition . these bilateral agreements cover information about transaction amount limits and definitions of direct debit schemes. when present or ordering customer.

This message contains request for direct debit instructions.Final edition . Field 21E: Registration Reference FORMAT Option E 35x PRESENCE Conditional (C3) DEFINITION This field contains the registration reference authorising a creditor to take part in a direct debit scheme.February 2003 . The actual bilateral code/information will be specified in the second subfield. This message contains non pre-authorised direct debit instructions. rejected. CODES Type must contain one of the following codes (Error code(s): T47): AUTH NAUT RFDD RTND OTHR This message contains pre-authorised direct debit instructions to be processed according to the terms and conditions of the direct debit contract and/or mandate. NETWORK VALIDATED RULES The narrative second subfield can only be used in combination with OTHR (Error code(s): D81). ie. 4. 188 Standards Release Guide 2003 .Category 1 3. Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Type) (Additional Information) PRESENCE Optional DEFINITION This field identifies the type of the direct debit instructions contained in the message. A previously sent MT 104 is being returned.MT 104 SWIFTStandards . reversed or revoked. Used for bilaterally agreed codes/information.

February 2003 189 . etc. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). 7. 6. Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BIC/BEI) (Party Identifier) Standards Release Guide 2003 . NETWORK VALIDATED RULES Field 51A is only valid in IFT (Error code(s): D63). Field 51A: Sending Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field identifies the Sender of the message. The requested execution date is the date on which the Sender requests the Receiver to execute all transactions contained in sequence B. cancellations. USAGE RULES At least the first eight characters of the BIC in this field must be identical to the originator of this IFT message.Final edition .Category 1 MT 104 5. Field 30: Requested Execution Date FORMAT 6!n (Date) PRESENCE Mandatory DEFINITION This field specifies the requested execution date valid for all transactions contained in the MT 104. The content of field 20 Sender’s reference together with the content of this field provides the file identification which is to be used in the case of queries.SWIFTStandards .

MT 104 SWIFTStandards . 8. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address.Category 1 PRESENCE Conditional (C3) DEFINITION This field specifies the customer which is authorised by the creditor/account servicing institution to order all the transactions in the message. either connected or non-connected (Error code(s): T27. the account is maintained at the Sender or the account servicing institution specified in field 52a. the name or BIC/BEI of the creditor must be present. T28. T28. T45). either connected or non-connected (Error code(s): T27. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. In all other cases. Under the Request for Direct Debit scenario. Account is mandatory. 9. this account is held at the Receiver. In case the MT 104 is used under the request for Direct Debit scenario. Field 52a: Creditor’s Bank FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) 190 Standards Release Guide 2003 . T45).February 2003 . USAGE RULES This field must only be used when the instructing party is not also the creditor. T29.Final edition . USAGE RULES At a minimum. Field 50a: Creditor FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C2 and C4) DEFINITION This field specifies the creditor whose account is to be credited with all transactions in sequence B. T29.

. which orders all transactions in the message.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Standards Release Guide 2003 .SWIFTStandards . even if field 50A or 50K contain an IBAN.Final edition . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.February 2003 191 . CODES Party Identifier may be used to indicate a national clearing system code.Category 1 MT 104 PRESENCE Conditional (C3) DEFINITION This field specifies the creditor’s bank.

option C should be used containing a 2!a clearing system code preceded by a double ’//’.MT 104 SWIFTStandards . Option D must only be used when there is a need to be able to specify a name and address.February 2003 . ie must not be of subtype BEID..Final edition . due to regulatory considerations. The BIC must not be a BEI.5n 6!n Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. T28. either connected or non-connected (Error code(s): T27. MCCO..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3. 10. If the creditor’s bank cannot be identified by a BIC. TESP or TRCO (Error code(s): C05). Field 26T: Transaction Type Code FORMAT Option T 3!c (Type) 192 Standards Release Guide 2003 . eg. T29.Category 1 CC CH CP ES FW GR HK IE IN IT PT RU SC SW SW 9!n 6!n 4!n 8. USAGE RULES Option A is the preferred option. T45).

placed between slashes (’/’): BENEFRES ORDERRES Residence of debtor Residence of creditor USAGE RULES Country consists of the ISO country code of the country of residence of the creditor or the debtor. invoices. and/or reason for all transactions in the message. structured text with the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C3) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver and/or the Sender. instalment payments. eg. the following codes may be used. Standards Release Guide 2003 . 11. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. The information required is covered in the pre-established bilateral agreement between the Sender and the Receiver. Codes must be agreed upon bilaterally. purpose of. USAGE RULES The information given is intended both for regulatory and statutory requirements and to provide information to the debtor on the nature of the transaction.SWIFTStandards .February 2003 193 .Final edition . subscriptions.Category 1 MT 104 PRESENCE Conditional (C3) DEFINITION This field identifies the nature of. CODES When the residence of either creditor or debtor is to be identified.

the following definition applies: All transaction charges other than the charges of the Receiver servicing the creditor’s account are borne by the debtor. Under the Direct Debit scenario. CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the debtor. Receiver should be understood as Receiver of the MT 104 (RFDD). the following definition applies: Transaction charges on the Sender’s side are to be borne by the creditor. 12.MT 104 SWIFTStandards . Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C3) DEFINITION Under the Direct Debit scenario. 13.Category 1 The information specified must not have been explicitly conveyed in another field. The Sender and the Receiver should be understood as the Sender and the Receiver of the MT 104.Final edition . Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative-Structured Format) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] 194 Standards Release Guide 2003 . the following definition applies: This field specifies which party will bear the charges for all subsequent direct debits contained in the message. Under the Request for Direct Debit scenario. transaction charges on the Receiver’s side are to be borne by the debtor. the following definition applies: This field specifies which party will bear the charges for all transactions in the message.February 2003 . Under the Request for Direct Debit scenario. All transaction charges are to be borne by the creditor.

the MT 195 should be used as per the Standards Usage Guidelines. reversal. This reference must be unique within one single message. rejection or revocal. NETWORK VALIDATED RULES The first element in line 1 must contain either code /RETN/ or /REJT/ (Error code(s): D82). ie.g. placed between slashes (’/’). For returns or rejections of a single transaction within the MT 104 (ie. 14.Final edition . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). It is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. Field 21: Transaction Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the unique reference for the individual transaction. USAGE RULES The Reject/Return mechanism is used to reject or return all the transactions within the MT 104 message due to e. Sender of the original message regarding the reason for a return. 15.Category 1 MT 104 PRESENCE Conditional (C5) DEFINITION This field specifies additional information for the Receiver. CODES The codes REJT or RETN must be used in this field in the first position of the first line. non-compliance with the domestic scheme requirements.SWIFTStandards .February 2003 195 . USAGE RULES In related transactions the Sender’s reference together with the content of this field provides the transaction identification. Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Type) (Additional Information) Standards Release Guide 2003 . ie. sequence B).

16.Final edition . Field 21C: Mandate Reference FORMAT Option C 35x PRESENCE Optional DEFINITION This field contains the reference of the direct debit mandate which has been agreed upon between the creditor and the debtor. This occurrence of sequence B contains a non pre-authorised direct debit instruction. Used for bilaterally agreed codes/information. 17. AUTH NAUT OTHR This occurrence of sequence B contains a pre-authorised direct debit instruction to be processed according to the terms and conditions of the direct debit contract and/or mandate. The actual bilateral code/information will be specified in the second subfield. CODES One of the following codes must be used (Error code(s): T47). NETWORK VALIDATED RULES The narrative second subfield can only be used in combination with OTHR (Error code(s): D81).Category 1 PRESENCE Conditional (C1) DEFINITION This field identifies or further specifies the type of direct debit instruction in the same occurrence of sequence B.February 2003 .MT 104 SWIFTStandards . Field 21D: Direct Debit Reference FORMAT Option D 35x PRESENCE Optional 196 Standards Release Guide 2003 .

Final edition .Category 1 MT 104 DEFINITION This field further identifies the direct debit transaction. Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BIC/BEI) (Party Identifier) Standards Release Guide 2003 . 19. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The debtor’s account is identified in field 59a of the same occurrence of sequence B. 18. 20.February 2003 197 . T43). Field 32B: Currency and Transaction Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and the amount to be debited from the debtor’s account. subject to addition of charges if field 71A equals BEN or SHA. A decimal comma is mandatory and is included in the maximum length.SWIFTStandards . Field 21E: Registration Reference FORMAT Option E 35x PRESENCE Conditional (C3 and C12) DEFINITION This field contains the registration reference authorising a creditor to take part in a direct debit scheme. The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). T40.

T29. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. C4 and C12) DEFINITION This field specifies the creditor whose account is to be credited with the direct debit transaction in this particular occurrence of sequence B. either connected or non-connected (Error code(s): T27. T45). 21.February 2003 .Final edition . T45).MT 104 SWIFTStandards . the name or BIC/BEI of the creditor must be specified. 22.Category 1 PRESENCE Conditional (C3) DEFINITION This field specifies the customer which is authorised by the creditor/account servicing institution to order the direct debit transaction in this particular occurrence of sequence B. either connected or non-connected (Error code(s): T27. T28. Field 52a: Creditor’s Bank FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) 198 Standards Release Guide 2003 . T28. T29. USAGE RULES At a minimum. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. USAGE RULES This field must only be used when the instructing party is not also the ordering customer. Field 50a: Creditor FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Party Identifier) (Name & Address) PRESENCE Conditional (C2.

SWIFTStandards . CODES Party Identifier may be used to indicate a national clearing system code.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU BL 5!n 6!n 8!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Standards Release Guide 2003 .. which orders the transaction in the particular occurrence of sequence B.Category 1 MT 104 PRESENCE Conditional (C3 and C12) DEFINITION This field specifies the creditor’s bank. even if field 50A or 50K contain an IBAN. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.February 2003 199 .Final edition .

MT 104

SWIFTStandards - Category 1

CC CH CP ES FW GR HK IE IN IT PT RU SC SW SW

9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3..5n 6!n

Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)

NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45). The BIC must not be a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05). USAGE RULES Option A is the preferred option. If the creditor’s bank cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double ’//’. Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considerations.

23. Field 57a: Debtor’s Bank
FORMAT Option A Option C [/1!a][/34x] 4!a2!a2!c[3!c] /34x (Party Identifier) (BIC) (Party Identifier)

200

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 104

Option D

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

(Party Identifier) (Name & Address)

PRESENCE Optional DEFINITION This field specifies the bank - when other than the Receiver - which holds the account(s) of the debtor and which will execute the associated transaction in this occurrence of sequence B. This is applicable even if field 59a contains an IBAN. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT NZ PT SC 5!n 6!n 8!n 9!n 8..9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code UK Domestic Sort Code

Standards Release Guide 2003 - Final edition - February 2003

201

MT 104

SWIFTStandards - Category 1

CODES with options C and D: AT AU BL CC CH CP ES FW GR HK IE IN IT NZ PT RU SC SW SW 5!n 6!n 8!n 9!n 6!n 4!n 8..9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n 9!n 6!n 3..5n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code)

NETWORK VALIDATED RULES The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45). The BIC must not be a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

202

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 104

USAGE RULES Option A is the preferred option. If the debtor’s bank cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double ’//’. Option D must only be used when there is a need to be able to specify a name and address, eg, due to regulatory considerations.

24. Field 59a: Debtor
FORMAT Option A No option letter [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address)

PRESENCE Mandatory DEFINITION This field specifies the debtor whose account will be debited according to the direct debit instruction specified in this occurrence of sequence B. NETWORK VALIDATED RULES Although the presence of Account is optional in the field format, for the purpose of this message the Account of the debtor must be present (Error code(s): E10). The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45).

25. Field 70: Remittance Information
FORMAT 4*35x (Narrative)

PRESENCE Optional DEFINITION This field specifies details of the individual direct debit which are to be transmitted to the debtor. CODES One of the following codes may be used, placed between slashes (’/’): INV Invoice (followed by the date, reference and details of the invoice).

Standards Release Guide 2003 - Final edition - February 2003

203

MT 104

SWIFTStandards - Category 1

IPI RFB ROC

Unique reference identifying a related International Payment Instruction (followed by up to 20 characters). Reference for the debtor (followed by up to 16 characters). Ordering customer’s reference.

USAGE RULES For national clearing purposes, the Sender must check with the Receiver regarding length restrictions of field 70. The information specified in this field is intended only for the debtor, ie, this information only needs to be conveyed by the Receiver. Multiple references can be used, if separated with a double slash, ’//’. Code must not be repeated between two references of the same kind.

26. Field 26T: Transaction Type Code
FORMAT Option T 3!c (Type)

PRESENCE Conditional (C3) DEFINITION This field identifies the nature of, purpose of, and/or reason for the transaction in the particular occurrence of sequence B, eg, invoices, subscriptions, instalment payments. USAGE RULES The information given is intended both for regulatory and statutory requirements and to provide information to the debtor on the nature of the transaction. Codes must be agreed upon bilaterally.

27. Field 77B: Regulatory Reporting
FORMAT Option B 3*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative)

204

Standards Release Guide 2003 - Final edition - February 2003

Field 33B: Currency/Original Ordered Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Optional DEFINITION This field specifies the original currency and amount as ordered by the creditor when different from the transaction currency and amount specified in field 32B of the same occurrence of sequence B. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The integer part of Amount must contain at least one digit. The information specified must not have been explicitly conveyed in another field. 28. T40. T43).Category 1 MT 104 PRESENCE Conditional (C3) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver and/or the Sender.Final edition . The information required is covered in the pre-established bilateral agreement between the Sender and the Receiver. the following codes may be used placed between slashes (’/’): BENEFRES ORDERRES Residence of debtor Residence of creditor USAGE RULES Country consists of the ISO country code of the country of residence of the creditor or the debtor. CODES When the residence of either creditor or debtor is to be identified. Standards Release Guide 2003 .February 2003 205 . A decimal comma is mandatory and is included in the maximum length.SWIFTStandards . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).

MT 104 SWIFTStandards . CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the debtor. Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C6 and C12) 206 Standards Release Guide 2003 . The Sender and the Receiver should be understood as the Sender and the Receiver of the MT 104. Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C3) DEFINITION Under the Direct Debit scenario. the following definition applies: This field specifies which party will bear the charges for the direct debit transaction in this particular occurrence of sequence B. 30. Receiver should be understood as Receiver of the MT 104 (RFDD). Under the Request for Direct Debit scenario. Under the Direct Debit scenario.Final edition .February 2003 .Category 1 29. the following definition applies: Transaction charges on the Sender’s side are to be borne by the creditor. the following definition applies: All transaction charges other than the charges of the Receiver servicing the creditor’s account are borne by the debtor. Under the Request for Direct Debit scenario. the following definition applies: This field specifies which party will bear the charges for the subsequent direct debit transaction in this particular occurrence of sequence B. transaction charges on the Receiver’s side are to be borne by the debtor. All transaction charges are to be borne by the creditor.

T43). Standards Release Guide 2003 . A decimal comma is mandatory and is included in the maximum length.Category 1 MT 104 DEFINITION This field specifies the currency and amount of the charges due to the Sender for the individual transaction. NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C6 and C12) DEFINITION This field specifies the currency and amount of the charges due to the Receiver for the individual transaction.SWIFTStandards . The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. T40. The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). A decimal comma is mandatory and is included in the maximum length. 31. Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C8) DEFINITION This field specifies the exchange rate used to convert the original ordered amount specified in field 33B into the currency of the transaction amount (field 32B) in this occurrence of sequence B. T43). T43). The integer part of Amount must contain at least one digit. T40.Final edition . A decimal comma is mandatory and is included in the maximum length (Error code(s): T40.February 2003 207 . 32. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).

USAGE RULES If charges are settled immediately. 34. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Field 32B: Currency and Settlement Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory in a conditional (C12) sequence DEFINITION This field specifies the currency and the total settlement amount. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. if appropriate. T43). 35. Field 71F: Sum of Sender’s Charges 208 Standards Release Guide 2003 .Final edition . Field 19: Sum of Amounts FORMAT 17d (Amount) PRESENCE Conditional (C9) in a conditional (C12) sequence DEFINITION This field specifies the sum of all transaction amounts appearing in field 32B in each occurrence of sequence B. T40.Category 1 33. The integer part of Amount must contain at least one digit. T40.February 2003 .MT 104 SWIFTStandards . care must be taken that transactions are only combined in a single MT 104 which do not lead to a total amount that exceeds the 15d limit. Because the field can only contain a 15d amount. A decimal comma is mandatory and is included in the maximum length. 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. T43). the settlement amount may also include the total charges.

The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. T43). 37. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). T40.Final edition . A decimal comma is mandatory and is included in the maximum length. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). the amount must not equal ’0’ (Error code(s): D57).Category 1 MT 104 FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C6) in a conditional (C12) sequence DEFINITION This field specifies the total amount of the charges due to the Sender. 36. A decimal comma is mandatory and is included in the maximum length. T43).SWIFTStandards . The integer part of Amount must contain at least one digit. The integer part of Amount must contain at least one digit. Field 71G: Sum of Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C6) in a conditional (C12) sequence DEFINITION This field specifies the total amount of the charges due to the Receiver. T40. Field 53a: Sender’s Correspondent FORMAT Option A Option B [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] (Party Identifier) (BIC) (Party Identifier) (Location) Standards Release Guide 2003 . The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.February 2003 209 . If field 71G is present in sequence C.

February 2003 . in the currency of the transaction. then field 53a must be present (with a party identifier and bank identifier). in the currency of the transaction. TESP or TRCO (Error code(s): C05). USAGE RULES When there is a single direct account relationship. the account or branch of the Sender through which the Sender wants to be reimbursed by the Receiver. the account to be credited must be indicated in field 53a. in all cases. dictated by the currency of the transaction and the correspondent relationship between the Receiver and the Sender relative to that currency. either connected or non-connected (Error code(s): T27. a cover message (ie. and one of these accounts is to be used for reimbursement. T28. the need for a cover message is dependent on the currency of the transaction and the relationship between the Receiver and the branch of the Sender. between the Receiver and the Sender. between the Receiver and the Sender. where required. The use and interpretation of field 53a is.Final edition . field 53a must not be present. T45). MT202/203 or equivalent non-SWIFT) must be sent by the Receiver to the financial institution identified in field 53a. When field 53a is present and contains a branch of the Sender. MCCO. and this is the account to be used for crediting the Sender. The BIC must not be a BEI. A branch of the Receiver may appear in field 53a if the financial institution where the funds must be credited is both the Sender’s correspondent and a branch of the Receiver. between the Receiver and the Sender. the Sender will be paid at the Receiver’s branch identified in field 53a. When field 53B is used to specify a branch city name.MT 104 SWIFTStandards . NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. In all other cases. ie must not be of subtype BEID. when field 53a is present. using option B (with the account number only). If there is no direct account relationship. In those cases where there are multiple direct account relationships. 210 Standards Release Guide 2003 . T29. in the currency of the transaction(s).Category 1 PRESENCE Optional DEFINITION This field specifies. it must always be a branch of the Sender. In this case.

the last field in the message (77F) must be followed by a ’CrLf-’. MT 105 Format Specifications MT 105 EDIFACT Envelope Status M M M M M Tag 27 20 21 12 77F Sequence of Total Transaction Reference Number Related Reference Sub-message Type EDIFACT Message Field Name Content/Options 1!n/1!n 16x 16x 3!n 1800y No. The SWIFT character set ’x’ ONLY must be used in fields 27. An additional MT 105(s) should then be sent until the entire EDIFACT message has been conveyed.Category 1 MT 105 MT 105 EDIFACT Envelope Note: The use of this message type requires Message User Group (MUG) registration. 1 2 3 4 5 MT 105 Network Validated Rules There are no network validated rules for this message type. as is the case for all SWIFT messages. that two or more messages are not put in a single MT 105).SWIFTStandards . MT 105 Scope This message is sent by a financial institution to another financial institution. When more than one message is required to convey the details of the EDIFACT message embedded in field 77F the content of field 21 Related Reference of the MT 105 must be the same for all the messages in the series. must be used in field 77F. The use and content of this message is governed by an established bilateral agreement between the Sender and Receiver. Standards Release Guide 2003 . However. An alternative is to utilise the greater capacity of the MT 106. MT 105 Usage Rules When using this message you are requested to refer to the official Message Implementation Guidelines (MIGs) which contain full details on the format specifications and field specifications. It is used as an envelope to convey an EDIFACT message. as defined in the EDIFACT syntax rules (ISO 9735). this is subject to a bilateral agreement between the Sender and Receiver.February 2003 211 . 21 and 12. 20. The EDIFACT syntax and level A character set (the ’y’ character set on the SWIFT Network).Final edition . It should be noted that. When this is the case the EDIFACT message may be divided at any point within the text up to the maximum field capacity for 77F of 1800 characters. It is recommended that EDIFACT messages be transported one at a time (ie. to indicate ’End of Text’. It may not be possible to fit the entire EDIFACT message to be embedded in field 77F into one MT 105.

Field 20: Transaction Reference Number FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the Sender’s unambiguous identification of the transaction.Final edition . 3.February 2003 . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).Category 1 MT 105 Field Specifications 1. 2.MT 105 SWIFTStandards . Field 21: Related Reference FORMAT 16x 212 Standards Release Guide 2003 . Field 27: Sequence of Total FORMAT 1!n/1!n (Message Number) (Sequence Number) PRESENCE Mandatory DEFINITION The sequence of total specifies the rank of this message in the series and the total number of messages in the series. USAGE RULES The detailed form and content of this field are at the discretion of the Sender. in the instance below the content of field 27 in the last message of the series will be ’9/9’. USAGE RULES When only one MT 105 is necessary the content of field 27 will be ’1/1’. A maximum number of 9 messages may be sent in a series.

eg. When more than one MT 105 is sent to convey the EDIFACT message.Final edition . This requirement is to facilitate the unambiguous re-association of the separate ’pages’ of the transaction. CODES The following list of codes is currently available for use in field 12 of the MT 105: FINPAY REMADV Customer payment (Numeric code: to be allocated) Remittance Advice (Numeric code: 381) 5.SWIFTStandards .February 2003 213 . 4.Category 1 MT 105 PRESENCE Mandatory DEFINITION This field contains the reference to the associated (enveloped) EDIFACT message. the significant characters of the Document/Message Number (Data Element 1004) in the Beginning of the Message (BGM) segment of the EDIFACT message embedded in field 77F. Field 12: Sub-Message Type FORMAT 3!n PRESENCE Mandatory DEFINITION This field contains the identification of the EDIFACT message contained within field 77F by its recognized numeric code. up to a maximum of 16. Field 77F: EDIFACT Message FORMAT Option F 1800y Standards Release Guide 2003 . must be the same for each MT 105 in the series. USAGE RULES The content of this field should reflect. the content of field 21. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). and also to provide a direct link to the EDIFACT message in case of further processing. cancellation.

must be used in this field.Category 1 PRESENCE Mandatory DEFINITION This field contains the EDIFACT message being sent by the Sender to the Receiver. the EDIFACT message may be divided at any point up to the maximum field capacity of 1800 characters. 214 Standards Release Guide 2003 .February 2003 . more than one MT 105 is required to convey the contents of the EDIFACT message. USAGE RULES For the purposes of this message. the EDIFACT syntax.Final edition . When the content of field 27: Sequence of Total is other than 1/1.MT 105 SWIFTStandards . as defined in the EDIFACT syntax rules (ISO 9735). Please refer to the appropriate volume of the EDIFACT Message Implementation Guidelines (MIGs) for guidance on how to complete the EDIFACT message that will be contained in this field. ie.

that two or more messages are not put in a single MT 106). 20. 1 2 3 4 5 MT 106 Network Validated Rules There are no network validated rules for this message type. The S. as is the case for all S. Standards Release Guide 2003 . When this is the case the EDIFACT message may be divided at any point within the text up to the maximum field capacity for 77G of 9800 characters.Final edition .T.. must be used in field 77G. character set ’x’ ONLY must be used in fields 27. Network).Category 1 MT 106 MT 106 EDIFACT Envelope Note: The use of this message type requires Message User Group (MUG) registration. MT 106 Scope This message is sent by a financial institution to another financial institution.T.e. It is used as an envelope to convey an EDIFACT message. MT 106 Format Specifications MT 106 EDIFACT Envelope Status M M M M M Tag 27 20 21 12 77G Sequence of Total Transaction Reference Number Related Reference Sub-message Type EDIFACT Message Field Name Content/Options 1!n/1!n 16x 16x 3!n 9800y No. It may not be possible to fit the entire EDIFACT message to be embedded in field 77G into one MT 106.W. It should be noted that. MT 106 Usage Rules When using this message you are requested to refer to the official Message Implementation Guidelines (MIGs) which contain full details on the format specifications and field specifications.W.T. When more than one message is required to convey the details of the EDIFACT message embedded in field 77G the content of field 21 Related Reference of the MT 106 must be the same for all the messages in the series.F. to indicate ’End of Text’.I. 21 and 12. An additional MT 106(s) should then be sent until the entire EDIFACT message has been conveyed. as defined in the EDIFACT syntax rules (ISO 9735). messages.SWIFTStandards .February 2003 215 .I.F.I. It is recommended that EDIFACT messages be transported one at a time (i. the last field in the message (77G) must be followed by a ’CrLf-’. The use and content of this message is governed by an established bilateral agreement between the Sender and Receiver.W. The EDIFACT syntax and level A character set (the ’y’ character set on the S.F.

Category 1 MT 106 Field Specifications 1. USAGE RULES Its detailed form and content are at the discretion of the Sender. 3.Final edition . USAGE RULES When only one MT 106 is necessary the content of field 27 will be ’1/1’. Field 20: Transaction Reference Number FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the Sender’s unambiguous identification of the transaction. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).MT 106 SWIFTStandards . Field 21: Related Reference FORMAT 16x 216 Standards Release Guide 2003 .February 2003 . Field 27: Sequence of Total FORMAT 1!n/1!n (Message Number) (Sequence Number) PRESENCE Mandatory DEFINITION The sequence of total specifies the rank of this message in the series and the total number of messages in the series. in the instance below the content of field 27 in the last message of the series will be ’9/9’. 2. A maximum number of 9 messages may be sent in a series.

SWIFTStandards - Category 1

MT 106

PRESENCE Mandatory DEFINITION This field contains the reference to the associated (enveloped) EDIFACT message. USAGE RULES The content of this field should reflect, up to a maximum of 16, the significant characters of the Document/Message Number (Data Element 1004) in the Beginning of Message (BGM) segment of the EDIFACT message embedded in field 77G. When more than one MT 106 is sent to convey the EDIFACT message the content of field 21 must be the same for each MT 106 in the series. This requirement is to facilitate the unambiguous re-association of the separate ’pages’ of the transaction, and also to provide a direct link to the EDIFACT message in case of further processing.

4. Field 12: Sub-Message Type
FORMAT 3!n

PRESENCE Mandatory DEFINITION This field contains the identification of the EDIFACT message contained within field 77G by its recognized numeric code. CODES The following list of codes is currently available for use in field 12 of the MT 106: FINPAY REMADV Customer payment (Numeric code: to be allocated) Remittance Advice (Numeric code: 381)

5. Field 77G: EDIFACT Message
FORMAT Option G 9800y

PRESENCE Mandatory

Standards Release Guide 2003 - Final edition - February 2003

217

MT 106

SWIFTStandards - Category 1

DEFINITION This field contains the EDIFACT message being sent by the Sender to the Receiver. USAGE RULES For the purposes of this message, the EDIFACT syntax, as defined in the EDIFACT syntax rules (ISO 9735), must be used in this field. Please refer to the appropriate volume of the EDIFACT Message Implementation Guidelines (MIGs) for guidance on how to complete the EDIFACT message that will be contained in this field. When the content of field 27: Sequence of Total is other than 1/1, ie, more than one MT 106 is required to convey the contents of the EDIFACT message, the EDIFACT message may be divided at any point up to the maximum field capacity of 9800 characters.

218

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 107

MT 107 General Direct Debit Message
Note: The use of this message type requires Message User Group (MUG) registration.

MT 107 Scope
This message is sent by the creditor’s financial institution or another financial institution, to the debtor’s financial Institution or another financial institution, on behalf of the creditor, to order the debit of the debtor’s account and to collect payment from this account.

MT 107 Format Specifications
The MT 107 consists of three 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 mandatory sequence; each occurrence provides details of one individual transaction. Fields which appear in both sequences A and B are mutually exclusive. Sequence C Settlement Details is a single occurrence mandatory sequence and provides further settlement information for all transactions mentioned in sequence B. MT 107 General Direct Debit Message Status Tag Field Name Content/Options No.

Mandatory Sequence A General Information M O O M O O O O O O O 20 23E 21E 30 51A 50a 50a 52a 26T 77B 71A Sender’s Reference Instruction Code Registration Reference Requested Execution Date Sending Institution Instructing Party Creditor Creditor’s Bank Transaction Type Code Regulatory Reporting Details of Charges 16x 4!c[/30x] 35x 6!n [/1!a][/34x] 4!a2!a2!c[3!c] C or L A or K A, C or D 3!c 3*35x 10 3!a 11 1 2 3 4 5 6 7 8 9

Standards Release Guide 2003 - Final edition - February 2003

219

MT 107

SWIFTStandards - Category 1

Status O

Tag 72

Field Name Sender to Receiver Information

Content/Options 6*35x

No. 12

-----> Mandatory Repetitive Sequence B Transaction Details M O O O O M O O O O M O O O O O 21 23E 21C 21D 21E 32B 50a 50a 52a 57a 59a 70 26T 77B 33B 71A Transaction Reference Instruction Code Mandate Reference Direct Debit Reference Registration Reference Currency and Transaction Amount Instructing Party Creditor Creditor’s Bank Debtor’s Bank Debtor Remittance Information Transaction Type Code Regulatory Reporting Currency/Original Ordered Amount Details of Charges 16x 13 4!c[/30x] 14 35x 15 35x 16 35x 17 3!a15d 18 C or L 19 A or K 20 A, C or D 21 A, C or D 22 A or no option letter 23 4*35x 24 3!c 25 3*35x 26 3!a15d 27 3!a 28

220

Standards Release Guide 2003 - Final edition - February 2003

SWIFTStandards - Category 1

MT 107

Status O O O -----|

Tag 71F 71G 36 Sender’s Charges Receiver’s Charges Exchange Rate

Field Name

Content/Options 3!a15d

No. 29

3!a15d 30 12d 31

Mandatory Sequence C Settlement Details M O O O O 32B 19 71F 71G 53a Currency and Settlement Amount Sum of Amounts Sum of Sender’s Charges Sum of Receiver’s Charges Sender’s Correspondent M = Mandatory O = Optional 3!a15d 32 17d 33 3!a15d 34 3!a15d 35 A or B 36

MT 107 Network Validated Rules
C1 Fields 23E and the second occurrence field 50a (option A or K) must, independently of each other, be present either in sequence A or in each occurrence of sequence B, but not in both (Error code(s): D86): Sequence A if field 23E is... Present Not present In each occurrence of Sequence B then field 23E is... Not allowed Mandatory

Sequence A if field 50a (option A or K) is... Present

In each occurrence of Sequence B then field 50a (option A or K) is... Not allowed

Standards Release Guide 2003 - Final edition - February 2003

221

71A... Present Not present Not allowed Optional Sequence B then field 71A is. not be present in any occurrence of sequence B.Category 1 Sequence A if field 50a (option A or K) is.... 26T. independently of each other. Present Not present Not allowed Optional Sequence B then field 21E is. When present in one or more occurrences of sequence B.. 52a and 50a (option C or L) must.. 222 Standards Release Guide 2003 ...... Present Not present Not allowed Optional Sequence B then field 26T is.. 77B.. Present Not present Not allowed Optional Sequence B then field 52a is. 71A. Mandatory C2 When present in sequence A.Final edition . 26T. Sequence A if field 77B is. Not present In each occurrence of Sequence B then field 50a (option A or K) is.MT 107 SWIFTStandards .. Sequence A if field 71A is... fields 21E. fields 21E.... 77B.. Sequence A if field 21E is.. 52a and 50a (option C or L) must not be present in sequence A (Error code(s): D73): Sequence A if field 26T is..February 2003 . Present Not present Not allowed Optional Sequence B then field 77B is.. Sequence A if field 52a is.

Present Not present Sequence B then field 50a (option A or K) is . Not allowed Optional C3 If field 21E is present in sequence A. equals RTND not equals RTND Not present Mandatory Not allowed Not allowed Sequence A then field 72 is. Present Not present Sequence A then field 50a (option A or K) is. independently of each other.. then field 50a (option A or K). if field 21E is present.February 2003 223 . fields 71F and 71G are present in one or more occurrence of sequence B.ie. field 23E not present..SWIFTStandards . if field 23E is present and contains RTND then field 72 must be present.. C5 If... Mandatory Optional (See C1) Sequence B if field 21E is...Final edition .. in all other cases ... must also be present in sequence A..field 72 is not allowed (Error code(s): C82): Sequence A if field 23E is... In each occurrence of sequence B. then they must also be present in sequence C. and vice versa (Error code(s): D79): Standards Release Guide 2003 ... Mandatory Optional (See C1) C4 In sequence A. or field 23E does not contain RTND . then field 50a (option A or K) must also be present in the same occurrence (Error code(s): D77): Sequence A if field 21E is..Category 1 MT 107 Sequence A if field 50a (option C or L) is. Present Not present Sequence B then field 50a (option C or L) is.

C7 In any occurrence of sequence B. Examples: Valid :32B:USD1. if field 33B is present and the currency codes in fields 32B and 33B are different. Otherwise.00 :32B:USD1. then the currency code or the amount. :32B:USD1. field 19 must not be present (Error code(s): D80). Field 19 must equal the sum of the amounts in all occurrences of field 32B in sequence B (Error code(s): C01). :33B:USD0001. :32B:USD1..Category 1 Sequence B if field 71F is. or be put in field 19 of sequence C. In the former case. :32B:USD1.00 :33B:USD0001. or both.Final edition . Sequence B if field 71G is.. C9 The currency code in fields 32B and 71G in sequences B and C must be the same for all occurrences of these fields in the message (Error code(s): C02)... :33B:USD2. if field 33B is present. Present Not present Mandatory Not allowed Sequence C then field 71G is. :33B:USD1. then field 36 must be present. field 36 must not be present (Error code(s): D75). C6 In each occurrence of sequence B. Invalid :32B:USD1. :33B:BEF2. Present Not present Mandatory Not allowed Sequence C then field 71F is. In the latter case.February 2003 . 224 Standards Release Guide 2003 ..MT 107 SWIFTStandards ... :33B:BEF1. must be different between fields 33B and 32B(Error code(s): D21). C8 The sum of the amounts of fields 32B in sequence B must be put either in field 32B of sequence C when no charges are included..

MT 107 Usage Rules The entire chain of parties and the transaction flow is illustrated by the following figure: Standards Release Guide 2003 .SWIFTStandards .February 2003 225 .Category 1 MT 107 The currency code in the charges fields 71F (in sequences B and C) must be the same for all occurrences of these fields in the message (Error code(s): C02).Final edition .

Category 1 The parties mentioned in the chain are not necessarily different entities... cancellations. The MT 107 Checklist at the end of this chapter is recommended as a guide for institutions in the setup of their agreements. The use of the MT 107 is subject to bilateral/multilateral agreements between the Sender and the Receiver. MT 107 Field Specifications 1. these bilateral agreements cover information about transaction amount limits and definitions of direct debit schemes.. Creditor’s bank (field 52a) Instructing Party (field 50C or 50L) Debtor’s bank (field 57a) Sender Creditor (field 50A or 50K) Receiver Their function is assumed by. Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.MT 107 SWIFTStandards . The first column of the table below shows the parties that can be omitted in an MT 107.. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). when it is not present: If the following party is missing. 2. USAGE RULES This field must be unique for each message and is part of the file identification and transaction identification which is used in case of queries.February 2003 . The second column specifies the party which assumes the role of the party in the first column. Amongst other things. etc.Final edition . Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Type) (Additional Information) 226 Standards Release Guide 2003 .

Field 21E: Registration Reference FORMAT Option E 35x PRESENCE Conditional (C2) DEFINITION This field contains the registration reference authorising a creditor to take part in a direct debit scheme. rejected. ie. This message contains non pre-authorised direct debit instructions. 3. The actual bilateral code/information will be specified in the second subfield.February 2003 227 .Category 1 MT 107 PRESENCE Conditional (C1) DEFINITION This field identifies the type of the direct debit instructions contained in the message. CODES Type must contain one of the following codes (Error code(s): T47): AUTH NAUT RTND OTHR This message contains pre-authorised direct debit instructions to be processed according to the terms and conditions of the direct debit contract and/or mandate. A previously sent MT 107 is being returned. NETWORK VALIDATED RULES The narrative second subfield can only be used in combination with OTHR (Error code(s): D81).Final edition . Field 30: Requested Execution Date FORMAT 6!n (Date) PRESENCE Mandatory Standards Release Guide 2003 . 4.SWIFTStandards . reversed or revoked. Used for bilaterally agreed codes/information.

T45). 6. Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BIC/BEI) (Party Identifier) PRESENCE Conditional (C2) DEFINITION This field specifies the instructing party ordering all transactions of the message. T29. NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. (Error code(s): T50). The requested execution date is the date on which the Sender requests the Receiver to execute all transactions contained in sequence B. NETWORK VALIDATED RULES Field 51A is only valid in IFT (Error code(s): D63). 228 Standards Release Guide 2003 . NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD.MT 107 SWIFTStandards .February 2003 . USAGE RULES At least the first eight characters of the BIC in this field must be identical to the originator of this IFT message.Category 1 DEFINITION This field specifies the requested execution date valid for all transactions contained in the MT 107. either connected or non-connected (Error code(s): T27.Final edition . T28. 5. Field 51A: Sending Institution FORMAT Option A [/1!a][/34x] 4!a2!a2!c[3!c] (Party Identifier) (BIC) PRESENCE Optional DEFINITION This field identifies the Sender of the message.

SWIFTStandards . 8. The BIC/BEI must be a SWIFT registered address. T28. T29. T45). If the account of the creditor is present.Category 1 MT 107 USAGE RULES This field must only be used when the instructing party is not also the ordering customer. even if field 50A or 50K contain an IBAN. it must be specified in Account.Final edition . which orders all transactions in the message. Field 52a: Creditor’s Bank FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) PRESENCE Conditional (C2) DEFINITION This field specifies the creditor’s bank. Field 50a: Creditor FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C1 and C3) DEFINITION This field specifies the creditor ordering all transactions in the message. NETWORK VALIDATED RULES At least one line of the Name and Address must be present (Error code(s): T77). USAGE RULES The name of the creditor must be specified.February 2003 229 . either connected or non-connected (Error code(s): T27. 7. Standards Release Guide 2003 .

MT 107 SWIFTStandards ..Category 1 CODES Party Identifier may be used to indicate a national clearing system code.Final edition . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.February 2003 .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU BL CC CH CP ES 5!n 6!n 8!n 9!n 6!n 4!n 8..9n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code 230 Standards Release Guide 2003 .

option C should be used containing a 2!a clearing system code preceded by a double ’//’. Option D must only be used when there is a need to be able to specify a name and address. T29.. either connected or non-connected (Error code(s): T27.Final edition .Category 1 MT 107 FW GR HK IE IN IT PT RU SC SW SW 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3. MCCO. ie must not be of subtype BEID. The BIC must not be a BEI.5n 6!n Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.SWIFTStandards . If the creditor’s bank cannot be identified by a BIC. T28.February 2003 231 . due to regulatory considerations. TESP or TRCO (Error code(s): C05). Field 26T: Transaction Type Code FORMAT Option T 3!c (Type) PRESENCE Conditional (C2) Standards Release Guide 2003 . 9. USAGE RULES Option A is the preferred option. T45). eg.

CODES When the residence of either creditor or debtor is to be identified. invoices.Category 1 DEFINITION This field identifies the nature of. subscriptions. The information required is covered in the pre-established bilateral agreement between the Sender and the Receiver. Codes must be agreed upon bilaterally. the following codes may be used.Final edition . Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. 232 Standards Release Guide 2003 . and/or reason for all transactions in the message. 10. purpose of.February 2003 . installment payments. USAGE RULES The information given is intended both for regulatory and statutory requirements and to provide information to the debtor on the nature of the transaction. The information specified must not have been explicitly conveyed in another field. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C2) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver and/or the Sender. eg.MT 107 SWIFTStandards . placed between slashes (’/’): BENEFRES ORDERRES Residence of debtor Residence of creditor USAGE RULES Country consists of the ISO country code of the country of residence of the creditor or the debtor.

transaction charges on the Receiver’s side are to be borne by the debtor. 12. The Sender and the Receiver should be understood as the Sender and the Receiver of the MT 107.SWIFTStandards .Structured Format) The following line formats must be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Conditional (C4) DEFINITION This field specifies additional information for the Receiver. rejection or revocation of the whole message.February 2003 233 . Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C2) DEFINITION This field specifies which party will bear the charges for all transactions in the message. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative .Final edition . CODES One of the following codes must be used (Error code(s): T08) BEN OUR SHA All transaction charges are to be borne by the debtor. Standards Release Guide 2003 . All transaction charges are to be borne by the creditor. ie. ie. reversal.Category 1 MT 107 11. Transaction charges on the Sender’s side are to be borne by the creditor. Sender of the original message regarding the reason for a return.

non-compliance with the domestic scheme requirements.Final edition . 234 Standards Release Guide 2003 .Category 1 CODES The codes RETN/REJT must be used in this field in the first position of the first line. the MT 195 should be used as per the Standards Usage Guidelines. USAGE RULES The Reject/Return mechanism is used to reject or return all the transactions within the MT 107 message due to e. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).February 2003 . placed between slashes (’/’). It is mandatory to use these codes according to the Generic Payment Reject Mechanism described in the Standards Usage Guidelines. Field 23E: Instruction Code FORMAT Option E 4!c[/30x] (Type) (Additional Information) PRESENCE Conditional (C1) DEFINITION This field identifies the type of direct debit instruction in the occurrence of sequence B. 13. USAGE RULES In related transactions the Sender’s reference together with the content of this field provides the transaction identification.g. 14. NETWORK VALIDATED RULES The first element in line 1 must contain either code /RETN/ or /REJT/ (Error code(s): T82). Field 21: Transaction Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the unique reference for the individual transaction.MT 107 SWIFTStandards . For returns or rejections of a single transaction within the MT 107 (ie. sequence B).

AUTH NAUT OTHR This occurrence of sequence B contains a pre-authorised direct debit instruction to be processed according to the terms and conditions of the direct debit contract and/or mandate. Field 21E: Registration Reference Standards Release Guide 2003 . NETWORK VALIDATED RULES The narrative second subfield can only be used in combination with OTHR (Error code(s): D81). Field 21D: Direct Debit Reference FORMAT Option D 35x PRESENCE Optional DEFINITION This field further identifies the direct debit transaction. This occurrence of sequence B contains a non pre-authorised direct debit instruction. Used for bilaterally agreed codes/information.Final edition . Field 21C: Mandate Reference FORMAT Option C 35x PRESENCE Optional DEFINITION This field contains the reference of the direct debit mandate which has been agreed upon between the creditor and the debtor.Category 1 MT 107 CODES One of the following codes must be used (Error code(s): T47).February 2003 235 . The actual bilateral code/information will be specified in the second subfield.SWIFTStandards . 15. 17. 16.

19. 236 Standards Release Guide 2003 . T43).February 2003 . Field 50a: Instructing Party FORMAT Option C Option L 4!a2!a2!c[3!c] 35x (BIC/BEI) (Party Identifier) PRESENCE Conditional (C2) DEFINITION This field specifies the instructing party ordering the transaction in this particular occurrence of sequence B. T40. subject to addition of charges if field 71A equals BEN or SHA.Category 1 FORMAT Option E 35x PRESENCE Conditional (C2) DEFINITION This field contains the registration reference authorising a creditor to take part in a direct debit scheme. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). The debtor’s account is identified in field 59a of the same occurrence of sequence B. 18. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Field 32B: Currency and Transaction Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and the amount to be debited from the debtor’s account.MT 107 SWIFTStandards . A decimal comma is mandatory and is included in the maximum length. The integer part of Amount must contain at least one digit.Final edition .

T45). 21.Final edition . either connected or non-connected (Error code(s): T27. it must be specified in Account.Category 1 MT 107 NETWORK VALIDATED RULES The BIC/BEI must be a SWIFT registered address. T29.SWIFTStandards . Field 50a: Creditor FORMAT Option A Option K [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Conditional (C1 and C3) DEFINITION This field specifies the creditor ordering the transaction in this particular occurrence of sequence B. The BIC/BEI must be a SWIFT registered address. T28. T29. 20. If the account of the creditor is present. either connected or non-connected (Error code(s): T27. T28. T45).February 2003 237 . Field 52a: Creditor’s Bank FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) PRESENCE Conditional (C2) Standards Release Guide 2003 . USAGE RULES This field must only be used when the instructing party is not also the ordering customer. USAGE RULES At a minimum. NETWORK VALIDATED RULES At least one line of the Name and Address must be present (Error code(s): T77). the name of the creditor must be specified.

Category 1 DEFINITION This field specifies the creditor’s bank.MT 107 SWIFTStandards . which orders the transaction in this particular occurrence of sequence B.Final edition . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8. even if field 50A or 50K contain an IBAN..February 2003 . CODES Party Identifier may be used to indicate a national clearing system code.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU BL CC CH 5!n 6!n 8!n 9!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier 238 Standards Release Guide 2003 .

TESP or TRCO (Error code(s): C05).February 2003 239 .. If the creditor’s bank cannot be identified by a BIC. 22. option C should be used containing a 2!a clearing system code preceded by a double ’//’.9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3. due to regulatory considerations.Final edition . either connected or non-connected (Error code(s): T27. T28.5n 6!n CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. ie must not be of subtype BEID.. MCCO. Option D must only be used when there is a need to be able to specify a name and address. T29. T45).Category 1 MT 107 CP ES FW GR HK IE IN IT PT RU SC SW SW 4!n 8.SWIFTStandards . The BIC must not be a BEI. eg. USAGE RULES Option A is the preferred option. Field 57a: Debtor’s Bank FORMAT Option A Option C Option D [/1!a][/34x] 4!a2!a2!c[3!c] /34x [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Party Identifier) (Name & Address) Standards Release Guide 2003 .

.Final edition . This is applicable even if field 59a contains an IBAN.which holds the account of the debtor and which will execute the associated transaction in this occurrence of sequence B.Category 1 PRESENCE Optional DEFINITION This field specifies the bank .February 2003 . CODES Party Identifier may be used to indicate a national clearing system code.MT 107 SWIFTStandards .when other than the Receiver . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT NZ PT SC 5!n 6!n 8!n 9!n 8.9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 6!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options C and D: AT AU 5!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code 240 Standards Release Guide 2003 .

Category 1 MT 107 BL CC CH CP ES FW GR HK IE IN IT NZ PT RU SC SW SW 8!n 9!n 6!n 4!n 8.February 2003 241 . Option D must only be used when there is a need to be able to specify a name and address. eg. T28. either connected or non-connected (Error code(s): T27. USAGE RULES Option A is the preferred option.SWIFTStandards . option C should be used containing a 2!a clearing system code preceded by a double ’//’. If the debtor’s bank cannot be identified by a BIC. Standards Release Guide 2003 .. TESP or TRCO (Error code(s): C05). ie must not be of subtype BEID. The BIC must not be a BEI.. MCCO. T29.9n 9!n 7!n 3!n 6!n 11!c 10!n 6!n 8!n 9!n 6!n 3.Final edition . T45).5n 6!n German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code New Zealand National Clearing Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. due to regulatory considerations.

24. NETWORK VALIDATED RULES Account of the debtor must be present (Error code(s): E10). Reference for the debtor (followed by up to 16 characters). placed between slashes (’/’): INV IPI RFB ROC Invoice (followed by the date. T28. Ordering customer’s reference. either connected or non-connected (Error code(s): T27. CODES One of the following codes may be used.MT 107 SWIFTStandards . T45). Field 70: Remittance Information FORMAT 4*35x (Narrative) PRESENCE Optional DEFINITION This field specifies details of the individual direct debit which are to be transmitted to the debtor. Unique reference identifying a related International Payment Instruction (followed by up to 20 characters).Category 1 23.Final edition . 242 Standards Release Guide 2003 . reference and details of the invoice).February 2003 . T29. The BIC/BEI must be a SWIFT registered address. Field 59a: Debtor FORMAT Option A No option letter [/34x] 4!a2!a2!c[3!c] [/34x] 4*35x (Account) (BIC/BEI) (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field specifies the debtor whose account will be debited according to the direct debit instruction specified in this occurrence of sequence B.

Field 26T: Transaction Type Code FORMAT Option T 3!c (Type) PRESENCE Conditional (C2) DEFINITION This field identifies the nature of. this information only needs to be conveyed by the Receiver. Codes must be agreed upon bilaterally. subscriptions. Standards Release Guide 2003 . USAGE RULES The information given is intended both for regulatory and statutory requirements and to provide information to the debtor on the nature of the transaction.SWIFTStandards . ie.February 2003 243 . if separated with a double slash. 26. Field 77B: Regulatory Reporting FORMAT Option B 3*35x (Narrative) In addition to narrative text. The information specified in this field is intended only for the debtor. ’//’. Code must not be repeated between two references of the same kind. Multiple references can be used. the following line formats may be used: Line 1 Lines 2-3 /8a/2!a[//additional information] [//continuation of additional information] (Code) (Country) (Narrative) (Narrative) PRESENCE Conditional (C2) DEFINITION This field specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of the Receiver and/or the Sender. invoices. purpose of.Final edition . the Sender must check with the Receiver regarding length restrictions of field 70. 25. and/or reason for the transaction in the particular occurrence of sequence B.Category 1 MT 107 USAGE RULES For national clearing purposes. eg. instalment payments.

A decimal comma is mandatory and is included in the maximum length. The information required is covered in the pre-established bilateral agreement between the Sender and the Receiver. T40. 27. the following codes may be used placed between slashes (’/’): BENEFRES ORDERRES Residence of beneficiary customer Residence of ordering customer USAGE RULES Country consists of the ISO country code of the country of residence of the creditor or the debtor. The information specified must not have been explicitly conveyed in another field.MT 107 SWIFTStandards . The integer part of Amount must contain at least one digit. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).February 2003 . 28. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03.Final edition . T43). Field 71A: Details of Charges FORMAT Option A 3!a (Code) PRESENCE Conditional (C2) 244 Standards Release Guide 2003 . Field 33B: Currency/Original Ordered Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Optional DEFINITION This field specifies the original currency and amount as ordered by the creditor when different from the transaction currency and amount specified in field 32B of the same occurrence of sequence B.Category 1 CODES When the residence of either creditor or debtor is to be identified.

transaction charges on the Receiver’s side are to be borne by the debtor.Final edition . NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). All transaction charges are to be borne by the creditor.Category 1 MT 107 DEFINITION This field specifies which party will bear the charges for the transaction in this particular occurrence of sequence B. Field 71G: Receiver’s Charges FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C5) Standards Release Guide 2003 . A decimal comma is mandatory and is included in the maximum length. The integer part of Amount must contain at least one digit. Field 71F: Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C5) DEFINITION This field specifies the currency and amount of the charges due to the Sender for the individual transaction. Transaction charges on the Sender’s side are to be borne by the creditor.SWIFTStandards . CODES One of the following codes must be used (Error code(s): T08): BEN OUR SHA All transaction charges are to be borne by the debtor. 29. The Sender and the Receiver should be understood as the Sender and the Receiver of the MT 107. T40. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 30. T43).February 2003 245 .

T43). Field 32B: Currency and Settlement Amount FORMAT Option B 3!a15d (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and the total settlement amount. T43). NETWORK VALIDATED RULES The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. The integer part of Amount must contain at least one digit.February 2003 . A decimal comma is mandatory and is included in the maximum length (Error code(s): T40. T40. 32. T43). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 31.Final edition . 246 Standards Release Guide 2003 . The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length.MT 107 SWIFTStandards . Field 36: Exchange Rate FORMAT 12d (Rate) PRESENCE Conditional (C7) DEFINITION This field specifies the exchange rate used to convert the original ordered amount specified in field 33B into the currency of the transaction amount (field 32B) in this occurrence of sequence B. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52). T40.Category 1 DEFINITION This field specifies the currency and amount of the charges due to the Receiver for the individual transaction.

33. 35. Field 71F: Sum of Sender’s Charges FORMAT Option F 3!a15d (Currency) (Amount) PRESENCE Conditional (C5) DEFINITION This field specifies the total amount of the charges due to the Sender. Field 19: Sum of Amounts FORMAT 17d (Amount) PRESENCE Conditional (C8) DEFINITION This field specifies the sum of all transaction amounts appearing in field 32B in each occurrence of sequence B. 34. Field 71G: Sum of Receiver’s Charges Standards Release Guide 2003 . A decimal comma is mandatory and is included in the maximum length. A decimal comma is mandatory and is included in the maximum length. the settlement amount may also include the total charges. The integer part of Amount must contain at least one digit. T40.SWIFTStandards . 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.February 2003 247 . T40. NETWORK VALIDATED RULES The integer part of Amount must contain at least one digit. Because the field can only contain a 15d amount. care must be taken that transactions are only combined in a single MT 107 which do not lead to a total amount that exceeds the 15d limit. if appropriate. T43). T43). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).Category 1 MT 107 USAGE RULES If charges are settled immediately.Final edition .

USAGE RULES When there is a single direct account relationship. Field 53a: Sender’s Correspondent FORMAT Option A Option B [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] (Party Identifier) (BIC) (Party Identifier) (Location) PRESENCE Optional DEFINITION This field specifies. ie must not be of subtype BEID. If field 71G is present in sequence C. in the currency of the transaction. T43). A decimal comma is mandatory and is included in the maximum length. 248 Standards Release Guide 2003 . and one of these accounts is to be used for reimbursement. between the Receiver and the Sender. In those cases where there are multiple direct account relationships. T28. T40.February 2003 .Category 1 FORMAT Option G 3!a15d (Currency) (Amount) PRESENCE Conditional (C5) DEFINITION This field specifies the total amount of the charges due to the Receiver. TESP or TRCO (Error code(s): C05). T29. the account to be credited must be indicated in field 53a. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. MCCO. either connected or non-connected (Error code(s): T27. The integer part of Amount must contain at least one digit. and this is the account to be used for crediting the Sender. between the Receiver and the Sender. field 53a must not be present. the account or branch of the Sender through which the Sender wants to be reimbursed by the Receiver. in the currency of the transaction(s). using option B (with the account number only). the amount must not equal ’0’ (Error code(s): D57). where required. 36.Final edition . The BIC must not be a BEI. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. T45). NETWORK VALIDATED RULES Currency must be a valid ISO 4217 currency code (Error code(s): T52).MT 107 SWIFTStandards .

in the currency of the transaction. it must always be a branch of the Sender. dictated by the currency of the transaction and the correspondent relationship between the Receiver and the Sender relative to that currency.Final edition . When field 53a is present and contains a branch of the Sender. In this case. The use and interpretation of field 53a is. Standards Release Guide 2003 . the need for a cover message is dependent on the currency of the transaction and the relationship between the Receiver and the branch of the Sender.February 2003 249 . a cover message (ie.SWIFTStandards . the Sender will be paid at the Receiver’s branch identified in field 53a. then field 53a must be present (with a party identifier and bank identifier). In all other cases.Category 1 MT 107 If there is no direct account relationship. When field 53B is used to specify a branch city name. MT 202/203 or equivalent non-SWIFT) must be sent by the Receiver to the financial institution identified in field 53a. in all cases. A branch of the Receiver may appear in field 53a if the financial institution where the funds must be credited is both the Sender’s correspondent and a branch of the Receiver. between the Receiver and the Sender. when field 53a is present.

B or D 6*35x Content/Options No. MT 110 Format Specifications MT 110 Advice of Cheque(s) Status M O O O -----> M M M O M -----| M = Mandatory O = Optional 21 30 32a 52a 59 Cheque Number Date of Issue Amount Drawer Bank Payee 16x 6!n A or B A.February 2003 . C2 250 Standards Release Guide 2003 .MT 110 SWIFTStandards . It is used to advise the drawee bank.Final edition . B or D A. 1 2 3 4 MT 110 Network Validated Rules C1 The repetitive sequence must not be present more than ten times (Error code(s): T10).Category 1 MT 110 Advice of Cheque(s) MT 110 Scope This multiple message is sent by a drawer bank. B or D [/34x] 4*35x 5 6 7 8 9 Tag 20 53a 54a 72 Sender’s Reference Sender’s Correspondent Receiver’s Correspondent Sender to Receiver Information Field Name 16x A. or a bank acting on behalf of the drawer bank to the bank on which a/several cheque(s) has been drawn (the drawee bank). or confirm to an enquiring bank. the details concerning the cheque(s) referred to in the message.

Category 1 MT 110 The currency code in the amount field 32a must be the same for all occurrences of this field in the message (Error code(s): C02). 2. ie must not be of subtype BEID. T45). TESP or TRCO (Error code(s): C05). MT 110 Field Specifications 1.Final edition . T29. Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.February 2003 251 . Field 53a: Sender’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies the account or branch of the Sender or another bank through which the Sender will reimburse the Receiver.SWIFTStandards . either connected or non-connected (Error code(s): T27. MCCO. Standards Release Guide 2003 . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. The BIC must not be a BEI. T28.

252 Standards Release Guide 2003 . In all other cases. A branch of the Receiver may appear in field 53a if the financial institution providing reimbursement is both the Sender’s correspondent and a branch of the Receiver.February 2003 . ie MT 202/203 or equivalent non-SWIFT.Final edition . it must always be a branch of the Sender. T29. NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. then field 53a must be present. either connected or non-connected (Error code(s): T27. must be sent to the financial institution identified in field 53a. in the currency of the transaction. T45). TESP or TRCO (Error code(s): C05). and one of these accounts is to be used for reimbursement.Category 1 USAGE RULES The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and the Receiver. In those cases where there are multiple direct account relationships. When field 53B is used to specify a branch city name. between the Sender and the Receiver. using option B with the party identifier only. In this case. in the currency of the cheques. dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. the relationship between the Sender and the Receiver and the contents of field 54a. will be used. a cover message. The BIC must not be a BEI. T28. 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. ie must not be of subtype BEID. in all cases. 3. if present.MT 110 SWIFTStandards . If there is no direct account relationship. MCCO. The use and interpretation of fields 53a and 54a is. in the currency of the transaction. Field 54a: Receiver’s Correspondent FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field specifies the branch of the Receiver or another bank at which the funds will be made available to the Receiver. and the Sender intends to send a cover message to the branch of the Receiver. between the Sender and the Receiver (or branch of the Receiver when specified in field 54a). the account to be credited or debited must be indicated in field 53a. when field 53a is present. the Receiver will be paid by its branch in field 53a.

one of the following codes must be used placed between slashes (’/’): ACC INS Instructions following are for the account with institution. A branch of the Sender must not appear in field 54a.SWIFTStandards . structured text with the following formats may be used: Line 1 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]] PRESENCE Optional DEFINITION This field specifies additional information for the Receiver or other party specified. or field 53a contains an account of the Sender serviced by the Receiver’s branch. the Receiver will be paid by its branch in field 54a.Category 1 MT 110 USAGE RULES The absence of fields 53a and 54a implies that the single direct account relationship between the Sender and the Receiver. Field 54a containing the name of a financial institution other than the Receiver’s branch must be preceded by field 53a. in the currency of the cheques. 4. If the branch of the Sender or other financial institution specified in field 53a is also the account servicer for the Receiver. the Receiver will claim reimbursement from its branch. the Receiver will claim reimbursement from its branch or will be paid by its branch. If field 54a contains a branch of the Receiver and field 53a contains a branch of the Sender. The instructing institution which instructed the Sender to execute the transaction. will be used. The use and interpretation of fields 53a and 54a is in all cases dictated by the currency of the transaction and the correspondent relationship between the Sender and Receiver relative to that currency. Field 72: Sender to Receiver Information FORMAT 6*35x (Narrative) In addition to narrative text. In all other cases where field 54a contains a branch of the Receiver.Final edition .February 2003 253 . depending on the currency of the transfer and the relationship between the Sender and the Receiver. field 54a must not be present. Standards Release Guide 2003 . the Receiver will be paid by the financial institution in field 54a. In those cases where field 54a contains a branch of the Receiver. CODES Unless bilaterally agreed otherwise between the Sender and the Receiver. and is not preceded by field 53a.

Final edition . where bilateral agreements covering the use of codes in this field are in effect. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).February 2003 .MT 110 SWIFTStandards . It may be followed by additional narrative text. must begin on a new line. Narrative text should preferably be the last information in this field. However. it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines. and. Instructions following are for the Receiver of the message. Each code used must be between slashes and appear at the beginning of a line. must start with a double slash ’//’. format 12d. placed between slashes (’/’). if used. which is continued on the next line(s). If either of these codes is used in the first position of the first line. 5. USAGE RULES Field 72 must never be used for information for which another field is intended. The codes REJT/RETN may be used in this field. Use of field 72. because. and terminated with another slash. Each item for which a code exists must start with that code and may be completed with additional information. the presence of this field will normally require manual intervention. Narrative text relating to a preceding code. In line with ERI. as specified in the chapter entitled Euro-Impact on Category 1 Message Standards. particularly with uncoded instructions. may cause delay.Category 1 INT REC Instructions following are for the intermediary institution. the code must conform to the structure of this field. in automated systems. the optional code word EXCH may be used to transport an exchange rate. followed by the exchange rate. 254 Standards Release Guide 2003 . In order to comply with the EC-directive on cross border credit transfers. This field may include ERI to transport dual currencies. It is strongly recommended to use the standard codes proposed above. the code word EXCH is placed between slashes. Field 21: Cheque Number FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the number of the cheque being advised.

Field 30: Date of Issue FORMAT 6!n (Date) PRESENCE Mandatory DEFINITION This field contains the date on which the cheque was drawn. Currency must be the same for all occurrences of this field in the message (Error code(s): C02). T43). T40.February 2003 255 . Field 32a: Amount FORMAT Option A Option B 6!n3!a15d 3!a15d (Date) (Currency) (Amount) (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and amount of the cheque for which the Sender has credited the Receiver with the cheque amount.Category 1 MT 110 6. A decimal comma is mandatory and is included in the maximum length. The integer part of Amount must contain at least one digit.SWIFTStandards .Final edition . USAGE RULES Option A will be used when the Sender has credited the Receiver with the cheque amount. Standards Release Guide 2003 . NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). it may also specify the value date. Currency must be a valid ISO 4217 currency code (Error code(s): T52). The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. 7. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).

9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code 256 Standards Release Guide 2003 .Final edition . Field 52a: Drawer Bank FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field identifies the drawer bank.Category 1 8. CODES Party Identifier may be used to indicate a national clearing system code.February 2003 . The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.MT 110 SWIFTStandards ..

9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3.Category 1 MT 110 CODES with options B or D: AT AU BL CC CH CP ES FW GR HK IE IN IT PT RU SC SW SW 5!n 6!n 8!n 9!n 6!n 4!n 8. TESP or TRCO (Error code(s): C05).Final edition .5n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. T45). Standards Release Guide 2003 . The coded information contained in field 52a must be meaningful to the Receiver of the message.. MCCO.February 2003 257 . T28. USAGE RULES This field is used when the drawer bank is a branch of the Sender or a bank other than the Sender of the message. ie must not be of subtype BEID.SWIFTStandards . either connected or non-connected (Error code(s): T27. The BIC must not be a BEI.. T29.

Option D should only be used when the ordering financial institution has no BIC.Category 1 Option A is the preferred option. 9. 258 Standards Release Guide 2003 .Final edition .MT 110 SWIFTStandards . USAGE RULES Account must not be used. Field 59: Payee FORMAT [/34x] 4*35x (Account) (Name & Address) PRESENCE Mandatory DEFINITION This field identifies the beneficiary of the cheque.February 2003 .

or a bank acting on behalf of the drawer bank. B or D [/34x] 4*35x 6*35x Content/Options No.SWIFTStandards . MT 111 Field Specifications Standards Release Guide 2003 . to the bank on which a cheque has been drawn (the drawee bank). 1 2 3 4 5 6 7 MT 111 Network Validated Rules There are no network validated rules for this message type. MT 111 Usage Rules This message must not be used to request stop payment of a cheque which was issued without a specified payee. MT 111 Format Specifications MT 111 Request for Stop Payment of a Cheque Status M M M M O O O Tag 20 21 30 32a 52a 59 75 Sender’s Reference Cheque Number Date of Issue Amount Drawer Bank Payee Queries M = Mandatory O = Optional Field Name 16x 16x 6!n A or B A. MT 111 Guidelines Information concerning national policies and procedures for stop payments may be found in the General Information Section (green) of the International Bank Identifier Code Directory (BIC Directory). This message always requires a response. It is used to request stop payment of the cheque referred to in the message.February 2003 259 .Final edition .Category 1 MT 111 MT 111 Request for Stop Payment of a Cheque MT 111 Scope This single message type is sent by a drawer bank. preferably by an MT 112 Status of a Request for Stop Payment of a Cheque.

Field 21: Cheque Number FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the number of the cheque for which stop payment is being requested.Category 1 1. 3. 2. NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). Field 20: Sender’s Reference FORMAT 16x PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message.MT 111 SWIFTStandards . Field 30: Date of Issue FORMAT 6!n (Date) PRESENCE Mandatory DEFINITION This field contains the date on which the cheque was drawn.February 2003 .Final edition . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). 260 Standards Release Guide 2003 .

5. T43). option B will be used. T40. 4. Field 32a: Amount FORMAT Option A Option B 6!n3!a15d 3!a15d (Date) (Currency) (Amount) (Currency) (Amount) PRESENCE Mandatory DEFINITION This field specifies the currency and amount of the cheque. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. Option A will be used when the Sender has previously credited the Receiver with the cheque amount.SWIFTStandards . In all other cases.February 2003 261 . When no MT 110 has been sent. Currency must be a valid ISO 4217 currency code (Error code(s): T52). NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). Field 52a: Drawer Bank FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional Standards Release Guide 2003 . A decimal comma is mandatory and is included in the maximum length. it may also specify the value date. the contents of this field must be the same as in the MT 110. The integer part of Amount must contain at least one digit. USAGE RULES When an MT 110 has been sent for the referenced cheque.Final edition .Category 1 MT 111 NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).

. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.Final edition .February 2003 .MT 111 SWIFTStandards .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options B or D: AT AU BL CC CH CP 5!n 6!n 8!n 9!n 6!n 4!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier 262 Standards Release Guide 2003 .Category 1 DEFINITION This field identifies the drawer bank.

SWIFTStandards . T45). Field 59: Payee FORMAT [/34x] 4*35x (Account) (Name & Address) PRESENCE Optional Standards Release Guide 2003 .. T29. MCCO. ie must not be of subtype BEID. The BIC must not be a BEI.Category 1 MT 111 ES FW GR HK IE IN IT PT RU SC SW SW 8. The coded information contained in field 52a must be meaningful to the Receiver of the message.9n 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3.February 2003 263 . either connected or non-connected (Error code(s): T27..Final edition . USAGE RULES This field is used when the drawer bank is a branch of the Sender or a bank other than the Sender of the message. Option A is the preferred option. Option D should only be used when the ordering financial institution has no BIC. TESP or TRCO (Error code(s): C05). T28.5n 6!n Spanish Domestic Interbanking Code Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address. 6.

. 7.Category 1 DEFINITION This field identifies the beneficiary of the cheque.. Please state if and when the transaction was effected. USAGE RULES Where a message contains more than one query. two different pieces of supplementary information are provided. (YYMMDD).(account/place).MT 111 SWIFTStandards . Field 75: Queries FORMAT 6*35x (Narrative) PRESENCE Optional DEFINITION This field may contain either the reason for stopping the payment of the cheque or a request for reimbursement authorisation.Final edition .February 2003 .. 264 Standards Release Guide 2003 .. (1). Please refund cover to credit of (1). When supplement (2) is used. Numbers in brackets. Please authorise us to debit your account.. eg. This supplementary information must be the first information following the code number. (number) dated (2). Cheque has been stolen/lost. the second piece of information should be preceded by a slash ’/’. mean that supplementary information is required. each query must appear on a separate line. ie. Cheque/draft not debited as of closing balance of statement (1). CODES The following code numbers have been defined for this message: Query /3/ /18/ /19/ /20/ /21/ Meaning We have been advised that the beneficiary did not receive payment/cheque.. USAGE RULES Account must not be used.

MT 112 Field Specifications 1.February 2003 265 .Category 1 MT 112 MT 112 Status of a Request for Stop Payment of a Cheque MT 112 Scope This message type is sent by the drawee bank (on which a cheque is drawn) to the drawer bank or the bank acting on behalf of the drawer bank. MT 112 Usage Rules This message may respond to an earlier MT 111 Request for Stop Payment of a Cheque. 1 2 3 4 5 6 7 MT 112 Network Validated Rules There are no network validated rules for this message type. It is used to indicate what actions have been taken in attempting to stop payment of the cheque referred to in the message.Final edition . Field 20: Transaction Reference Number FORMAT 16x Standards Release Guide 2003 .SWIFTStandards . B or D [/34x] 4*35x 6*35x Content/Options No. MT 112 Format Specifications MT 112 Status of a Request for Stop Payment of a Cheque Status M M M M O O M Tag 20 21 30 32a 52a 59 76 Field Name Transaction Reference Number Cheque Number Date of Issue Amount Drawer Bank Payee Answers M = Mandatory O = Optional 16x 16x 6!n A or B A.

MT 112 SWIFTStandards . NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26). NETWORK VALIDATED RULES This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).February 2003 .Final edition . Field 32a: Amount 266 Standards Release Guide 2003 . Field 21: Cheque Number FORMAT 16x PRESENCE Mandatory DEFINITION This field contains the number of the cheque to which this message refers. Field 30: Date of Issue FORMAT 6!n (Date) PRESENCE Mandatory DEFINITION This field contains the date on which the cheque was drawn. 4. 3. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).Category 1 PRESENCE Mandatory DEFINITION This field specifies the reference assigned by the Sender to unambiguously identify the message. 2.

Standards Release Guide 2003 .Final edition . 5. option A will be used when the drawer bank has previously credited the drawee bank with the cheque amount. Currency must be a valid ISO 4217 currency code (Error code(s): T52). In all other cases. If the request for stop payment has not been received via an MT 111. it may also specify the value date. USAGE RULES When the message is in response to an MT 111 Request for Stop Payment of a Cheque. The integer part of Amount must contain at least one digit. the contents of this field must be the same as field 32a of the MT 111. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03. option B must be used. A decimal comma is mandatory and is included in the maximum length. NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50). currency code and amount of the cheque. T43).February 2003 267 . T40. Field 52a: Drawer Bank FORMAT Option A Option B Option D [/1!a][/34x] 4!a2!a2!c[3!c] [/1!a][/34x] [35x] [/1!a][/34x] 4*35x (Party Identifier) (BIC) (Party Identifier) (Location) (Party Identifier) (Name & Address) PRESENCE Optional DEFINITION This field identifies the drawer bank when other than the Sender.Category 1 MT 112 FORMAT Option A Option B 6!n3!a15d 3!a15d (Date) (Currency) (Amount) (Currency) (Amount) PRESENCE Mandatory DEFINITION This field identifies the currency and amount of the cheque.SWIFTStandards . It contains the value date.

Category 1 CODES Party Identifier may be used to indicate a national clearing system code.. The following codes may be used preceded by a double slash (’//’): with option A: AT AU BL CC ES FW GR HK IE IN IT PT SC 5!n 6!n 8!n 9!n 8.February 2003 .9n without 9 digit code 7!n 3!n 6!n 11!c 10!n 8!n 6!n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number Spanish Domestic Interbanking Code Pay by Fedwire HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code UK Domestic Sort Code CODES with options B or D: AT AU BL CC CH CP ES 5!n 6!n 8!n 9!n 6!n 4!n 8.Final edition ..MT 112 SWIFTStandards .9n Austrian Bankleitzahl Australian Bank State Branch (BSB) Code German Bankleitzahl Canadian Payments Association Payment Routing Number CHIPS Universal Identifier CHIPS Participant Identifier Spanish Domestic Interbanking Code 268 Standards Release Guide 2003 .

February 2003 269 .Category 1 MT 112 FW GR HK IE IN IT PT RU SC SW SW 9!n 7!n 3!n 6!n 11!c 10!n 8!n 9!n 6!n 3. The coded information contained in field 52a must be meaningful to the Receiver of the message. Option D should only be used when the ordering financial institution has no BIC. Option A is the preferred option. TESP or TRCO (Error code(s): C05). Field 59: Payee FORMAT [/34x] 4*35x (Account) (Name & Address) PRESENCE Optional Standards Release Guide 2003 . T28. USAGE RULES This field will be used when the drawer bank is a branch of the Receiver or a bank other than the Receiver of the message.. 6. T29. The BIC must not be a BEI. MCCO.5n 6!n Fedwire Routing Number HEBIC (Hellenic Bank Identification Code) Bank Code of Hong Kong Irish National Clearing Code (NSC) Indian Financial System Code (IFSC) Italian Domestic Identification Code Portuguese National Clearing Code Russian Central Bank Identification Code UK Domestic Sort Code Swiss Clearing Code (BC code) Swiss Clearing Code (SIC code) NETWORK VALIDATED RULES The BIC must be a SWIFT registered address.Final edition . T45). either connected or non-connected (Error code(s): T27.SWIFTStandards . ie must not be of subtype BEID.

Stop instructions valid until (1). each answer must appear on a separate line. The answers may be in response to these query numbers. Stop instructions duly recorded.MT 112 SWIFTStandards . Field 76: Answers FORMAT 6*35x (Narrative) PRESENCE Mandatory DEFINITION This field must include information as to whether or not the stop payment has been effected. Numbers in brackets.Category 1 DEFINITION This field identifies the beneficiary of the cheque. We authorise you to debit our account.. In addition. /2/ /10/ /11/ /12/ /13/ /14/ Meaning We hereby confirm that the transaction has been effected and advised on (1). 270 Standards Release Guide 2003 . 7. (1).. (account/place). 21 Query No 3 20 18 19 USAGE RULES Where a message contains more than one answer... mean that supplementary information is required. (YYMMDD). This supplementary information must be the first information following the code number.Final edition . USAGE RULES Account must not be used. eg. Stop instructions are not acceptable.February 2003 . a response should be given to any request for reimbursement authorisation. (Reason).. CODES The following answer code numbers have been defined.. (Further details. Answer No. (YYMMDD). Cover refunded to the credit of (1). where applicable).

Final edition . it is recommended to use the text ’EDIFACT FINPAY’ because the MT 121 does not contain a field 20 Transaction Reference Number and the common group messages do not support the ’y’ character set. MT 121 Multiple Interbank Funds Transfer Status M Tag (none) Field Name EDIFACT FINPAY Message Contents Content/Options 9900y No. the MT 121 can only be described using a narrative description because this message contains no tagged mandatory field and the common group messages do not support the ’y’ character set.yyy’ represents the EDIFACT FINPAY message and ’CrLf-}’ is the text block trailer. Wherever. Longer EDIFACT FINPAY messages can. MT 121 Format Specifications This message has no predefined SWIFT format. field 21 Related Reference is mandatory in the common group message. MT 121 Guidelines It is recommended to implement the EDIFACT FINPAY message with the segments of the currently accepted EDIFACT directory.Category 1 MT 121 MT 121 Multiple Interbank Funds Transfer (EDIFACT FINPAY Message) Note: The use of this message type requires Message User Group (MUG) registration. Any deviation should be governed by a bilateral agreement between the Sender and the Receiver. The resulting text block will appear as ’{4:yyy..up to the defined maximum number of characters .February 2003 271 . MT 121 Field Specifications 1..is available for the contents of the EDIFACT FINPAY message.. The complete text block . MT 121 Scope This message is used by a financial institution to send an EDIFACT FINPAY message to another financial institution.SWIFTStandards . Control of delivery of this message will be possible according to all normal criteria. however. 1 MT 121 Network Validated Rules There are no network validated rules for this message type. When control of delivery is based on the message category. ’yyy. be sent using multiple MT 106s. In common group messages. Retrieval of this message will be possible according to all normal criteria except field 20 Transaction Reference Number.. this message will be grouped with the other Category 1 messages.yyyCrLf-}’ where ’{4:’ is the text block header. No SWIFT specific field tags are used. EDIFACT FINPAY message contents Standards Release Guide 2003 . This message cannot be used for EDIFACT FINPAY messages exceeding the maximum length specified above.

The field length will not be validated separately but only via the implementation rule defining the maximum length of the complete message.February 2003 . ie.MT 121 SWIFTStandards . USAGE RULES The contents of this field will not be validated except for the use of the ’y’ character set. EDIFACT level A/ISO 9735. 272 Standards Release Guide 2003 . The effective maximum length of this field in a real message depends on the length of the added SWIFT headers and trailers.Category 1 FORMAT 9900y (no field tag) PRESENCE Mandatory DEFINITION This field contains the EDIFACT FINPAY message.Final edition .

Standards Release Guide 2003 . Interest and Other Adjustments for details concerning this message type. Interest and Other Adjustments Please refer to Category n . Chapter n90 Advice of Charges.February 2003 273 .Common Group Messages.Final edition .Category 1 MT 190 MT 190 Advice of Charges.SWIFTStandards .

MT 191 SWIFTStandards .February 2003 . Interest and Other Expenses Please refer to Category n .Common Group Messages.Final edition . 274 Standards Release Guide 2003 . Chapter n91 Request for Payment of Charges. Interest and Other Expenses for details concerning this message type.Category 1 MT 191 Request for Payment of Charges.

Final edition .Common Group Messages.SWIFTStandards .February 2003 275 . Chapter n92 Request for Cancellation for details concerning this message type.Category 1 MT 192 MT 192 Request for Cancellation Please refer to Category n . Standards Release Guide 2003 .

February 2003 . 276 Standards Release Guide 2003 .Category 1 MT 195 Queries Please refer to Category n .Final edition .MT 195 SWIFTStandards . Chapter n95 Queries for details concerning this message type.Common Group Messages.

February 2003 277 . Standards Release Guide 2003 .Final edition .Category 1 MT 196 MT 196 Answers Please refer to Category n . Chapter n96 Answers for details concerning this message type.SWIFTStandards .Common Group Messages.

Chapter n98 Proprietary Message for details concerning this message type.MT 198 SWIFTStandards .Common Group Messages. 278 Standards Release Guide 2003 .February 2003 .Final edition .Category 1 MT 198 Proprietary Message Please refer to Category n .

Standards Release Guide 2003 . Chapter n99 Free Format Message for details concerning this message type.SWIFTStandards .Category 1 MT 199 MT 199 Free Format Message Please refer to Category n .Final edition .February 2003 279 .Common Group Messages.

.

. . . Field 20: Sender’s Reference . . . . . . . . . . . . . . . . . Field 59: Beneficiary Customer (deleted) . . . . . . . . . . . . . . Removed Message Types . . . MT 102 Format Specifications . Overview . . . . . 15. . . . . . . . Field 52a: Account Servicing Institution (updated) . . . . . . . . . . . 17. . . . . . . . . . . . . . 18. . . . Field 59a: Beneficiary . . . . . . . . . . . . . . . . Field 25A: Charges Account . . . . . . . . . . . . . . . . . . . . 9. . . . . . . . . . . . MT 100 Network Validated Rules (deleted) . . . Field 51A: Sending Institution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21. . . . . . . 10. . . . . . .Final edition . . . 22. MT 101 Format Specifications . Field 72: Sender to Receiver Information (deleted) . . . . . 25. . . . . . . . . . . 9. . Field 28D: Message Index / Total . 1. . 16. . Field 56a: Intermediary (deleted) . . . . . . . . . . . . . . . . . 3. . . Field 36: Exchange Rate . . . . . . . . . . Field 54a: Receiver’s Correspondent (deleted) . . . . . . . . . . . . . . . . . . . . . 10. . . . . 23. . . . . . . . . . . . . 11. . . . . . . Field 32B: Currency/Transaction Amount . Field 50a: Instructing Party (updated) . . . 5. . 11. . . MT 101 Usage Rules . . . . . . . . . . . . . . . . . . . . . . . . . . MT 100 Usage Rules (deleted) . . . . 12. . . . . . . . . 1. MT 100 Field Specifications (deleted) . . . . . . . . . . . . . . . . . . . . . . . Field 21: Transaction Reference . . . . . Field 33B: Currency/Original Ordered Amount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 77B: Regulatory Reporting . Modified Message Types . Field 71A: Details of Charges (deleted) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Added Message Types . . . . . . . . . . . . . Field 70: Details of Payment (deleted) . . . Field 32A: Value Date. . . . . . . . . Field 57a: Account With Institution (updated) . . . . . . . . . . . . . . . . . . MT 102 Multiple Customer Credit Transfer . . . . . . . . . . . . . . . . Field 20: Transaction Reference Number (deleted) . . . . . . . . . . . . . . 7. . . MT 102 Scope . . Field 30: Requested Execution Date . 2 3 3 3 3 4 4 4 5 5 5 5 5 6 6 7 8 9 11 13 14 15 15 18 18 18 19 22 24 24 24 25 25 26 26 28 29 29 29 30 31 33 33 34 34 36 39 41 41 42 43 43 44 44 46 46 46 48 Standards Release Guide 2003 . . . . . . . . . . . . . . . . . 4. . . . . . .Category 1 Table Of Contents Table of Contents Legal Notices . . . 24. . . . . . . . Currency Code. . . Field 52a: Account Servicing Institution (updated) . . . 4. . . . . . . . . MT 101 Field Specifications (updated) . . . . . . . . MT 101 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 50a: Ordering Customer (updated) . . . . . 7. . . . . . . . . . . . . . . . . . . . MT 102 Network Validated Rules . . . . . . . . . . . . . . . . . . . . . . Field 21R: Customer Specified Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5. . . 12. . . . . . . . . . . . . . . 8. . . 8. . . . . . . . 6. . . . . . . . . . . . . . . . . . . . . . 2. . . . . . . . . . . Field 50a: Ordering Customer (updated) . . . . . . . . . . . . . . . . . . Field 23E: Instruction Code . . . . . . . . . . . . . Field 21F: F/X Deal Reference . . . . . . . . Field 70: Remittance Information . . MT 100 Scope (deleted) . . . . MT 101 Network Validated Rules . 2. . 6. . . . . . . MT 100 Customer Transfer (deleted) . . . . . . Field 71A: Details of Charges (updated) . . . . . Field 25: Authorisation . . . . . . . . . . . Amount (deleted) 3. . . . . . . Field 53a: Sender’s Correspondent (deleted) . MT 101 Request for Transfer . . . . . . . . . . . . . 19. . . . . . . . Field 50a: Instructing Party (updated) . . . . . . Field 52a: Ordering Institution (deleted) . . . . . . Field 50: Ordering Customer (deleted) . . . . . . . . . . . . . . . . . . . . . . . . . . 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .SWIFTStandards . . . . . . .February 2003 i . . . . . . . . . . Field 56a: Intermediary (updated) . . . . 14. MT 100 Format Specifications (deleted) . . 20. . . . . . . . . Field 57a: Account With Institution (deleted) . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . Field 20: File Reference . . . . . . . . . . Field 32A: Value Date. . 17. . 3. . 93 . . . . . . . . . . . 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 . . . . . . . . . . . . . . . . . . . Example A2: Charging option is SHA . Field 23: Bank Operation Code . 18. . . . . Field 71A: Details of Charges . . . . . 73 . . . . . . 16. . . . 12. . . 95 . Field 53a: Sender’s Correspondent (updated) . . . . 11. . . . . . . . . 82 . . . 64 . 62 . . Field 26T: Transaction Type Code . Amount 25. . . . . . .February 2003 . . . . . . . . . . . . . . . . . . 20. . . . . . 5. . . . . . . . . . . . . . . Field 59a: Beneficiary Customer . . . . . . . . Field 77B: Regulatory Reporting . 98 . . 2. . . 81 . . . 76 . . . . . . . . 67 . . . . . . . . . . Field 36: Exchange Rate . . . . . Field 52a: Ordering Institution (updated) . . . . . . . . . . . . . . . . . . . . . . 96 . . . . . . . . . . . . . . . . 78 . . . . . . . 56 . . 64 . . . . . . . . . . . . . . . . . . . . . . . MT 102+ Multiple Customer Credit Transfer . . . . . . . . . . . . . . . . 77 . . . . . . . . 1. Field 71G: Sum of Receiver’s Charges . . . . Field 52a: Ordering Institution (updated) . . . 21. . 76 . . . . . . 59 . . . . . . . . Field 71A: Details of Charges . . . . . . 28. . 77 . . . . . . . 12. . . . . . . . 10. . . . 7. . . . . . . . . . . . . Field 71G: Receiver’s Charges . . . . . . . . . . . MT 102+ Network Validated Rules . . . Example B3: Charging option is BEN . . Field 70: Remittance Information . . . . . . . . . . . . . . MT 102+ Format Specifications . . . . 29. . . . . 83 . . . . . . Field 77B: Regulatory Reporting . . . . 14. . . . . 16. Field 26T: Transaction Type Code . . Field 32B: Transaction Amount . . 2. . . . . . . . . Field 23: Bank Operation Code . . . . . . . . . . 15. . . . . 1. 75 . . . . Example B2: Charging option is SHA . . . . . . . . . . . . . . . 27. . 14. . . . . . . 22. . . . 80 . . . . . . . Example A3: Charging option is BEN . . . . 7. . . 95 . . . . . . . . . . . 101 . . . 60 . Field 36: Exchange Rate . . . . . . . 60 . . . . . . . . . 23. . . . . . . . . . . . . . 61 . . . . . 8. . . . . . . . . . . Field 72: Sender to Receiver Information . . . . Field 52A: Ordering Institution (updated) . . . .Category 1 MT 102 Usage Rules . . Field 51A: Sending Institution . . . . . . . . . . . . . . . . . 65 . . . . . . . . . . . . . Field 57A: Account With Institution (updated) . . . Field 71F: Sender’s Charges . . . . . 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 26T: Transaction Type Code . 72 . . . . . . . MT 102+ Usage Rules . . . 60 . 104 . . . . . . . . . 6. . Field 19: Sum of Amounts . . . . . . . . 83 . . . 55 . . . . . . . . Currency Code. . . . . . . . . . . . . . 92 . . Field 32B: Transaction Amount . . . . . . . . . . . . . . . . 4. . . . . 103 . . Field 50a: Ordering Customer . . . . . . . 19. . . . Field 71A: Details of Charges . 97 . . Field 21: Transaction Reference . . . . 61 . 73 . 66 . Field 57a: Account With Institution (updated) . . . . . 66 . . . . . . Field 59a: Beneficiary Customer . . . . . . . . ii Standards Release Guide 2003 . . . Field 36: Exchange Rate . 98 . . . . . . . . . . . . . . . . . . . . . . . 13. . . 13. . . 17. . Field 77B: Regulatory Reporting .Final edition . Field 54A: Receiver’s Correspondent (updated) . 74 . . . . . . . . . . Field 21: Transaction Reference . . . . . . . . . . Field 52A: Ordering Institution (updated) . . . . . . . . . . . . 91 . . . . 70 . . . . . 5. . Example A1: Charging option is OUR . . . . . 4. . . . . . . . . . . . . . 30. . . . . . . MT 102 Field Specifications (updated) . . . . . . . . 18. 102 . . . . . . . . . MT 102+ Scope . . . . . . . . 102 . Field 26T: Transaction Type Code . . . . . . . . 92 . . . . . . . . . . . . 57 . 66 . 97 . . . . . . . Field 70: Remittance Information . . . . . 83 . . . . . 8. . . . . . . . . . 100 . . . .Table Of Contents SWIFTStandards . . . . . . . . 26. . 78 . . . . . . . . . . . . . Field 20: File Reference . . Example B1: Charging option is OUR . . . . . . Field 33B: Currency/Instructed Amount . . . . Field 50a: Ordering Customer . . . . . 9. . . 9. . . . . . . . . . . . . . . . 68 . 55 . . . . . . . . . . . Field 13C: Time Indication . 53 . . 10. . . . 58 . . . . 6. Field 50a: Ordering Customer . . . . . . . 24. . . . . . . . . 15. . . . 92 . . . . . . . . . . . . . . . MT 102+ Field Specifications (updated) . . . . . . . . Field 77B: Regulatory Reporting . . . 11. . . . . . . . . . . 3. . . . . . . . . . . . . . . Field 33B: Currency/Instructed Amount . . . . . . . . . . . . . . 79 . . . . . . . . . . . Field 50a: Ordering Customer . . . . . . . . . . . . . . . . . . . 96 . .

. . 146 . Field 19: Sum of Amounts . . . . . . . . . . . . . . . 137 . . 160 . . . . . . . . . . . . . . . Field 54A: Receiver’s Correspondent (updated) . . . . . . . . . . . . . . Example A1: Charging option is OUR . . . . . . 159 . . . . . . . . . 126 . . . . . . 24. . . 4. . . . . . . . . . . . . . . . . . . . . . . . . . 14. 161 . . 15. . . . . . . 123 . . . . 120 . . . . . . . . . . 10. . . . . . . . . . . . . . . . . 148 . . . . . . . . . . . . . . Example B2: Charging option is SHA . Field 71G: Receiver’s Charges . . . . . . . . . . . . . . . . . . . 2. . . . . . 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MT 103 Format Specifications . . . . . . . . . MT 103+ Field Specifications (updated) . . . 1. . . . . 107 . . . . . . 106 . 18. . . . 113 . . MT 103 Scope . . . . . . . . . . . . . . . . Field 71A: Details of Charges . . . . . . . . . Example B1: Charging option is OUR . . Field 71F: Sender’s Charges . . . 150 . 108 . . . . . . . . . . 127 . . . . . 119 . . . Field 72: Sender to Receiver Information . . . . . . . . . . . 25.February 2003 iii . . . . . . . 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 54a: Receiver’s Correspondent (updated) . . . . 135 . . . . . . . . . . . . 21. . . . Field 71F: Sender’s Charges . . . . 142 . . . . . .Category 1 Table Of Contents 19. . . . . . . . . . . . 111 . . . 27. . . . . . . . . . . . . . . . . . 110 . 23. Field 51A: Sending Institution . . 148 . 106 . . . . . . . . MT 103+ Scope . . . . . . . . Example B3: Charging option is BEN . . . . . . . . . . . . . . . . . . . . . . 132 . . . . . . . . . . MT 103+ Format Specifications . . . . . Field 53a: Sender’s Correspondent (updated) . . . 107 . . . . 12. . . . . . 113 . . . . . . . 142 . . . . . . . . . . 122 . . . . . . . . . . . . . . . Field 20: Sender’s Reference . . . . . . . . . . . . 22. . 132 . . . . . . . . . . . 125 . . . . Example A3: Charging option is BEN . 144 . . . . . 131 . . . . . MT 103+ Network Validated Rules . Field 23E: Instruction Code . . . . . . Currency Code. . . MT 103 Guidelines . . . . . . . . . . . . . . . . 159 . . . . . . . . . . . . . . Field 55a: Third Reimbursement Institution (updated) . . . . . . . . . . 147 . . . Field 77T: Envelope Contents . . . . . . . 143 . . . Field 33B: Currency/Instructed Amount . . . 156 . . . . . . . . . . . . 13. 11. . . . . . . 24. . 125 . . . . . . . MT 103 Network Validated Rules . . . . . . . . . . . . . . 131 . 21. . . . 5. . . . . . . . Field 13C: Time Indication . 104 . . . . . Field 36: Exchange Rate . . 136 . 16. . Field 23E: Instruction Code . . . . . . . . . . . . . . . 144 . . . . . 6. . Field 77B: Regulatory Reporting . . . . Field 71G: Receiver’s Charges . . . Field 71A: Details of Charges . . . . 23. . 158 . Field 13C: Time Indication . . 3. . 109 . . . . . . . . Amount . . . . . . . . 105 . . . . . . . 125 . . . Field 50a: Ordering Customer . . . . . . . . . . . . . . 8. . . . . . . . . . . . . MT 103 Single Customer Credit Transfer . . 9. . . . . Field 52a: Ordering Institution (updated) . . . . . . . . . . . . . . Field 70: Remittance Information . . . . . . . . . . 124 . . . . . . . . . . . . Field 26T: Transaction Type Code . . 5. . . . . . Field 57a: Account With Institution (updated) . 153 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 . . . 148 . . . MT 103 Usage Rules . . . . . . . . . . . . . . . . . 129 . . . . . . . . . . . . . . . Field 56a: Intermediary Institution (updated) . . Standards Release Guide 2003 . . . . . . . . .Final edition . MT 103+ Usage Rules . . . . . . . . . . . . . . . 121 . . . . Field 32A: Value Date. . . Field 23B: Bank Operation Code . . 115 . . . . . . . MT 103 Field Specifications (updated) . . . . 19. . Field 59a: Beneficiary Customer . . . . . . . . . . . 105 . . 4. . . . . 3. . . . . . . . . . . 28. . . . . 20. . . 139 . . . . . . MT 103+ Single Customer Credit Transfer . . . . . . . . . . . . . . 129 . . . Examples: Transaction A . . Field 71G: Sum of Receiver’s Charges . . 17. 1. . . . .SWIFTStandards . 124 . . . . . . . . . Field 36: Exchange Rate . . . MT 103+ Guidelines . . . . . . . Field 72: Sender to Receiver Information . . . Example A2: Charging option is SHA . . . . 113 . 22. . . . . . . . . . Field 13C: Time Indication . . . . . . 159 . . . . . . . . 145 . . Field 32A: Value Date/Currency/Interbank Settled Amount 7. . . 2. . . 162 . . . . . . 120 . . . . . . . Examples: Transaction B . . . . . . . . . Field 26T: Transaction Type Code . . . . . . . 134 . Field 53a: Sender’s Correspondent (updated) . . . . . . Field 20: Sender’s Reference . . . . . . . . . 130 . . 20. . . . . . . . Field 23B: Bank Operation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . 188 . . . . . . 20. . . . . . . . 21. . . . . . . 9. 15. . . . 2. . . . . . . 190 . . . . . . . . . . . . . . Field 70: Remittance Information . 13. . . Field 36: Exchange Rate . . . . Field 21C: Mandate Reference . Field 21D: Direct Debit Reference . . . . . . . . . . . . . . . . . . . . . . . 206 . . . . . . . . . . . . 11. . 29. . . . . . . . Field 50a: Creditor . . . . . 22. Field 71A: Details of Charges . . . 13. . . 10. . . . . . . . . . . . 184 . . . . . . . . . 15. . . Field 71A: Details of Charges . . 20. . . . . . . . . . Field 59a: Debtor . . . Field 59a: Beneficiary Customer . . . . . . Field 77B: Regulatory Reporting . Field 19: Sum of Amounts . . . . . . . . . . . . . . . 197 . 168 . . . . . . . . . . . . . . . . . 28. . Field 51A: Sending Institution . . Field 33B: Currency/Original Ordered Amount . . . . . 197 . . . . . . Field 71F: Sender’s Charges . . . . . . . . . . . . . . 189 . . . . . . .Category 1 6. . . . . . Field 50a: Creditor . . . . . . . . Field 21E: Registration Reference . . . . . . .Final edition . . . . . . . . . . . MT 104 Network Validated Rules . . . . . 194 . . 22. . . . . . . . . MT 104 Direct Debit and Request for Debit Transfer Message . . . . 14. . . . . iv Standards Release Guide 2003 . . . . . .Table Of Contents SWIFTStandards . . . . . . . . . . . . . . 33. . . . . 166 . . . . . . . . . Field 71F: Sender’s Charges . Field 52a: Creditor’s Bank (updated) . Field 33B: Currency/Instructed Amount . . 18. . . . . 177 . . . . . . . . . . . . 174 . . . . . . . 187 . Field 32B: Currency and Settlement Amount . . . Field 32A: Value Date/Currency/Interbank Settled Amount 7. . . 205 . . . . . . . 211 . . 1. . 8. . . . . . . . Field 20: Sender’s Reference . . Field 71F: Sum of Sender’s Charges . . 193 . 5. Field 56A: Intermediary Institution (updated) . Field 23E: Instruction Code . . 165 . . 164 . MT 105 EDIFACT Envelope . 206 . . . . . . . . . . 171 . . . . 170 . . . . . . . . 36. . . . . . . . . . . . . 211 . . 6. . . . . . . . Field 77B: Regulatory Reporting . . . . . . . . . . . . . . . . . . . . . . 173 . Field 53a: Sender’s Correspondent (updated) . . . . . . . . 26. . . . . . . . . . 34. . .February 2003 . . . . . . . . . . . . . . . 14. . . . . . Field 52a: Creditor’s Bank (updated) . . . 18. . 162 . . . . . . . 4. . . . . . . . . . . . . . . Field 72: Sender to Receiver Information . . . . . MT 104 Format Specifications . . . 19. . 208 . . Field 71G: Receiver’s Charges . Field 23E: Instruction Code . . . . . . . 17. 31. . Field 57a: Debtor’s Bank (updated) . . . . . . . . . 163 . . Field 21R : Customer Specified Reference . 203 . 11. . 192 . . . . . . . . . . . . . . . . . . . . . Field 72: Sender to Receiver Information . . . Field 71G: Receiver’s Charges . . . . . . . . . . . . . . . . . . 196 . . . . . . 197 . . . . . . . 169 . . . . . . . . . . . . . 163 . . 32. . MT 104 Scope . 21. . 209 . . Field 30: Requested Execution Date . . . . . . . . . . . . . . . . . . . . . Field 50a: Instructing Party . . . . 3. . . . . . . 203 . . . . . . . . . . . . . . . . Field 52A: Ordering Institution (updated) . . . . . . . 19. 167 . . Field 70: Remittance Information . 177 . . . 30. 16. . . . . . . . . . . . . 27. 204 . Field 36: Exchange Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 . . . . Field 32B: Currency and Transaction Amount . . . . . . . . 207 . . . . . . . . 207 . Field 26T: Transaction Type Code . . 198 . . . MT 104 Field Specifications (updated) . . 35. Field 50a: Instructing Party . . . . . . . . . . . 172 . . . . 8. . . 172 . . . . Field 57A: Account With Institution (updated) . . . . . . Field 53a: Sender’s Correspondent (updated) . . . . . . . . 25. . . . . . . . . . . . . . . . . . . . . MT 105 Scope . . . . . . 208 . . . 7. . . . . . 175 . . . . 16. . 164 . . . . . 195 . . . . . . . . . . . . 195 . . . . . . . 189 . . . . . . . . . Field 26T: Transaction Type Code . . 187 . 204 . . 196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 . . . . . . . . . . . . . Field 71G: Sum of Receiver’s Charges . Field 21: Transaction Reference . Field 50a: Ordering Customer . . 10. . . . . Field 71A: Details of Charges . . . . . . . . 194 . . . . . . . . . Field 21E: Registration Reference . . . . . . 9. . . Field 54A: Receiver’s Correspondent (updated) . 198 . . . . . . . MT 104 Guidelines . . . . . . . 17. . . . . . . . . . . . . . . . . . . . . 23. . . . . . . . . . . . Field 77B: Regulatory Reporting . 12. . . . . . . . . . . . . . . . 208 . . . 177 . . . . . 209 . . . . . 188 . 179 . . . . . . . . . . . . 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37. . . 187 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 55A: Third Reimbursement Institution (updated) . . 189 . . . 12. . . . . . . . .

. . MT 107 Scope . Standards Release Guide 2003 . Field 12: Sub-Message Type . . 235 . 5. . . . . . . 219 . MT 106 EDIFACT Envelope . . . . . . . . . . . Field 36: Exchange Rate . 3. . . . . . . 232 . . MT 107 Network Validated Rules . . Field 71A: Details of Charges . . . . . . Field 21: Related Reference . . . . . Field 21: Transaction Reference . . . . . 216 . . . 248 . . . . . . . . . . . . . . . MT 106 Field Specifications . . . 228 . . . MT 106 Format Specifications . . . . . . . . . . . . . . . . . . . . . . . 8. . . . . . . . . . . . . . Field 20: Sender’s Reference . . . . . . . 1. . . 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. . . . . . . 242 . . . . . . . . MT 107 Field Specifications (updated) . . 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 . . . . . . .Category 1 Table Of Contents MT 105 Format Specifications . . . . . . Field 32B: Currency and Transaction Amount 19. 3. 228 . . 225 . . Field 23E: Instruction Code . . . . . . Field 27: Sequence of Total . . . . . . . . . . . . . .February 2003 v . . . . . . . . . . . . . . . . . . . Field 19: Sum of Amounts . . . . . . . 212 . 247 . . . . . . . . . . . . Field 20: Transaction Reference Number . . . . . . . 226 . . . 9. . . 34. . . . . . . . . . . . 221 . . . Field 71F: Sender’s Charges . . . 247 . Field 72: Sender to Receiver Information . . . . . . . . . . 17. . 1. . . . . . . . 215 . . . . . . . . 14. . . . . 233 . . . . . . . . 229 . . . . . . . . Field 21E: Registration Reference . . . . . . . . 215 . . . . 35. . . . . . . . . 31. 20. . . Field 20: Transaction Reference Number . . 22. . . . . . . . . . . . . . 24. . . 245 . Field 59a: Debtor . . . . . . . . 229 . Field 26T: Transaction Type Code . 244 . . . . . . . Field 70: Remittance Information . . . 11. Field 71G: Receiver’s Charges . . Field 71G: Sum of Receiver’s Charges . . . . . . . . . . . . . . . . . . . . . . . 216 . . Field 50a: Instructing Party . . 212 . . . . . . 18. . 216 . . . . . . . . . . Field 33B: Currency/Original Ordered Amount 28. . 242 . . 26. . . . . . . . . . . . . . . 226 . 2. . 25. . . . . . . . . . . . . . . . . . . . 7. 233 . . . . . . . . . . 237 . . 213 . . 29. . . . . . . . . . MT 105 Network Validated Rules . . . MT 105 Usage Rules . . . . 243 . . . . . . . . Field 12: Sub-Message Type . . . . 16. . . . 6. 211 . . . . . Field 26T: Transaction Type Code . . . . . . . 236 . . Field 50a: Creditor . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 . . . 239 . . . . 15. . . . . . MT 107 Usage Rules . 231 . . . . . . . . 247 . Field 77B: Regulatory Reporting . . . . . . . . Field 77G: EDIFACT Message . . 13. . . . . . . Field 52a: Creditor’s Bank (updated) . . . . MT 105 Field Specifications . . . . . Field 77F: EDIFACT Message . . . 227 . . . . . . . . . . . . 244 . . . . . . . . . 235 . . . . . . . . . . . . . . . . . . . 2. . . . . . 211 . . . . . . . . . . . . 219 . . . . . . . . . . . 36. . . . . . . 1. . . . . . . . . . . . . 12. . 23. . 243 . . . . . . . . MT 106 Usage Rules . . . . 246 . . . 217 . 5. . . . . 215 . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 71F: Sum of Sender’s Charges . 215 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field 30: Requested Execution Date . . . . . . . . 217 .SWIFTStandards . . . MT 106 Scope . . . . . . . . . . Field 71A: Details of Charges . . . . MT 107 General Direct Debit Message . . . . . . . . . . . . 226 . . . . . 235 . . . . . . . . . . . . . . . . . . . . MT 107 Format Specifications . . . . . . 27. . 227 . . . . . . . . . . . . . . . . MT 106 Network Validated Rules . . 213 . . Field 57a: Debtor’s Bank (updated) . . 4. . . . . . . Field 53a: Sender’s Correspondent (updated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10. . . Field 27: Sequence of Total . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 . . 237 . . Field 50a: Creditor . . . . . 234 . . . . . . .Final edition . . Field 21E: Registration Reference . 212 . . . . . Field 51A: Sending Institution . . . . . . 246 . . . . . . . . . . . . . 219 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3. . . . . . 4. . . . . . Field 52a: Creditor’s Bank (updated) . Field 21D: Direct Debit Reference . . . . . . 236 . . . . . . . . . . . . . . . . . . . . . . . . . Field 21: Related Reference . . 21. . . . . . . . . . . 4. . . . . . . . 234 . . . . . . Field 77B: Regulatory Reporting . . . . . . . . . . . . . . . . . . . . . Field 23E: Instruction Code . . Field 32B: Currency and Settlement Amount 33. . . . . . 30. . . . . . . . . . 216 . . . . Field 21C: Mandate Reference . . 215 . . . . . . Field 50a: Instructing Party . .

. . 273 . . . . . . . . 279 . Field 20: Transaction Reference Number . . . 265 . . . . . . . . . . Field 21: Cheque Number . . . . MT 111 Guidelines . . . . . MT 121 Guidelines . . . . . Field 21: Cheque Number . . MT 121 Field Specifications . . . . 263 . . . . MT 110 Format Specifications . . . . . . . . . . . . . . . . . . . 250 . . . . . 259 . . . . . . . . . MT 190 Advice of Charges. . 267 . . . . . 6. . . . 259 . . . . . . . . . . . . . . vi Standards Release Guide 2003 . . . . . . Field 30: Date of Issue . . . . Field 30: Date of Issue . . . . . . . MT 112 Format Specifications . . . MT 112 Scope . . . . . . 261 . . . . . . MT 191 Request for Payment of Charges. 265 . . . 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 . . . . . . . . . . . . . . . . . . . 271 . . . MT 121 Multiple Interbank Funds Transfer (EDIFACT FINPAY Message) MT 121 Scope . . . . . . . . . . . . . . . . . 256 . . . . . . . . . . . 259 . . . . . . . . . . . . . . . . . . . . MT 121 Format Specifications . . . . . . . . . . . . . Field 20: Sender’s Reference . . . . . . . . . . 253 . . . . . . MT 199 Free Format Message . . . . . . 271 . . . . . . . . . . 254 . . . MT 110 Field Specifications (updated) . . . . . . . . . . . . . . . 9. . . 269 . . . . . . . . . . . . . . . . . . . . . . 250 . . . . . . . . . . . . MT 112 Status of a Request for Stop Payment of a Cheque . . . . . . . MT 111 Network Validated Rules . . . . . . . . . . .Final edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5. 259 . 260 . . . . . . 1. . . . . . . . . . . . . . . . . . . Field 21: Cheque Number . . 259 . . . . . . Interest and Other Expenses . 2. . . . . . . 266 . . . . . . . . . . . . . . . . . . . . MT 110 Network Validated Rules . . . . . . 6. . MT 112 Field Specifications (updated) . 8. . Field 53a: Sender’s Correspondent (updated) . . . . . . . . . . . 4. . . . . Field 32a: Amount . . . . 252 . . . . .February 2003 . . . . . . . . MT 192 Request for Cancellation . . . . . . . . . . . . . . . . . . 7. . . . . . . Field 76: Answers . . . . . . 264 . . 278 . . . . . . . . . . . . MT 121 Network Validated Rules . 3. . . . Field 32a: Amount . . . . . . . . Field 59: Payee . . . . . . . . . . . . . . . 251 . . MT 111 Usage Rules . . . . . . . . . . . . . . . Field 59: Payee . . 265 . . . . . . . . . . . . . . . . . . . . . 5. . . . . . 3. . . . . . MT 112 Usage Rules . . . . . . . . . . . . 255 . . 259 . . . . . . . . . . Field 52a: Drawer Bank (updated) . . . . .Category 1 MT 110 Advice of Cheque(s) . . . 4. . . . 265 . . . . . . . . . . . . . . . 266 . . . . . . . . . 259 . . . . . 251 . 266 . . . . . . . . 7. 6. . 271 . . . 265 . . . . . . . . . . . . . 7. . . . . . . . 275 . . . . . . . . . 250 . . . . . . . . . . . . . . . . . . Field 54a: Receiver’s Correspondent (updated) . . . . Interest and Other Adjustments . . . . . . . Field 75: Queries . . . . 258 . . . . 265 . . . . . Field 59: Payee . MT 110 Scope . . . . . . . . . . . . . Field 20: Sender’s Reference . . . . . . . 4. . . 261 . . . 1. . . . . . . . . . . . . MT 198 Proprietary Message . .Table Of Contents SWIFTStandards . . . . . Field 30: Date of Issue . . . . . . Field 72: Sender to Receiver Information . . . . . . . . . . . 5. . . . MT 196 Answers . . . . . 271 . . . . . . . . . . . . . . . . . . . 271 . . . . . . . . . . . 2. . . . Field 52a: Drawer Bank (updated) . . . . . . . . . 260 . . . . . . . . . . 271 . . 260 . . . . . . . . . . . . . MT 112 Network Validated Rules . . . 271 . . . . . . Field 32a: Amount . . Field 52a: Drawer Bank (updated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 . . . . . . EDIFACT FINPAY message contents . . . . . . MT 195 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. . . . . . . . 251 . . . . . . . . . . . . . 277 . MT 111 Request for Stop Payment of a Cheque . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. . . . . 274 . MT 111 Scope . . 3. . . . MT 111 Format Specifications . . . . . . . . . . . . 250 . . . . . . . 265 . . . . 276 . . . . . MT 111 Field Specifications (updated) .

Sign up to vote on this title
UsefulNot useful