SWIFT REQUEST FOR TRANSFER SERVICE. Description

Transcription

1 SWIFT REQUEST FOR TRANSFER SERVICE Description

2 Contents 1 Message MT101 Scope MT101 Message Structure Basic Header Block (1) Application Header Block (2) Text Block (4) The MT 101 consists of two sequences: MT 101 Format Specifications MT 101 Network (SWIFT) Validated Rules MT101 Field Specifications Field 20: Sender s Reference Field 21R Customer Specified Reference Field 50L: Instructing Party Field 50H: Ordering Customer Field 52a: Account Servicing Institution Field 51A: Sending Institution Field 30: Requested Execution Date Field 25: Authorisation Field 21: Transaction Reference... 17

3 10. Field 21F: F/X Deal Reference Field 23E: Instruction Code Field 32B: Currency/Transaction Amount Field 50L: Instructing Party Field 50H: Ordering Customer Field 52a: Account Servicing Institution Field 56a: Intermediary Field 57a: Account With Institution Field 59: Beneficiary Field 70: Remittance Information Field 77B: Regulatory Reporting Field 33B: Currency/Original Ordered Amount Field 71A: Details of Charges Field 25A: Charges Account Field 36: Exchange Rate... 31

4 1 M e s s a g e M T S c o p e This message is sent by a financial institution (Danske Bank, sender) on behalf of a nonfinancial institution account owner, i.e., the ordering customer/instructing party (customer of Danske Bank), and is subsequently received by the receiving financial institution and processed by the receiving financial institution or the account servicing financial institution. 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, or from an account(s) owned by the ordering customer which the instructing customer has explicit authority to debit, e.g., a subsidiary account. The MT101 can be used to order the movement of funds: between ordering customer accounts, or in favour of a third party, either domestically or internationally. The parties mentioned in the chain are not necessarily different entities. The first column of the table below shows the parties that can be omitted in an MT 101. The second column specifies the party which assumes the role of the party in the first column, when it is not present: If the following party is missing.. Its function is assumed by... Instructing party Ordering customer Account servicing institution Receiver (or the institution determined from the account number of the ordering customer) Intermediary Account with institution Account with institution Receiver (or the institution determined from the account number of the Beneficiary)

5 2 M T M e s s a g e S t r u c t u r e MT101 message has the following structure: {1: BASIC HEADER BLOCK } {2: APPLICATION HEADER BLOCK } {4: TEXT BLOCK } Blocks 1 and 2 relate to header information, block 4 contains the text of the message. Block 4 contain sub-blocks (i.e., blocks within blocks) and fields delimited by field tags. Every block must start with character { and end with character }. All message text within the text block (block 4) begins with Carriage Return and Line Feed <CRLF> and ends with <CRLF> followed by a hyphen -. Therefore the last line of a message is always -}. The maximum length of MT101 message is characters. 2.1 B asi c Heade r B lock (1) The basic header provides the fundamental referencing of a message. The basic header is always as follows: {1:F01DABAFIHHXXXX } The components can be separated as follows: (a) (b) (c) (d) (e) (f) { 1: F 01 DABAFIHHXXXX } (a) Block Identifier: The block identifier for a basic header block is always 1: (b) Application Identifier: The application identifier is always F

6 (c) Service Identifier: The Service Identifier is always 01 (d) LT Address: This 12-character S.W.I.F.T. address, given in the basic header block, is the address of the sending LT (Logical Terminal). Always DABAFIHHXXXX (e) Session Number: Always 4 spaces (f) Sequence Number (ISN): Always 6 spaces 2.2 Appli cation Header Block (2) 2.3 Text Block (4) The application header of a S.W.I.F.T. message provides information about the message itself. The application header describes the type of message, its addressee and how it should be sent. Normal message: (a) (b) (c) (d) (e) {2: I 101 BANKBEBXXXX N} (a) Block Identifier: The block identifier for an application header block is always 2: (b) Input/Output Identifier: Always I. (c) Message Type: The message type consists of three digits which define the MT number of the message being input. Always 101 (d) Receiver s Address: This address is the 12-character S.W.I.F.T. address of the receiver of the message, but with a Logical Terminal Code of X (9 th character). It defines the destination to which the message should be sent. The branch code is mandatory and will be validated. The default of XXX may be used, as in the example above (three last digits). (e) Message Priority: This character defines the priority with which a message is delivered. The possible value is: N = Normal The text of a S.W.I.F.T. message is given in block 4. An example of the text block in a typical S.W.I.F.T. message follows:

7 {4:<CRLF> :20:PAYREF-TB54302<CRLF> :32A:990103EUR ,<CRLF> :50:CUSTOMER NAME<CRLF> AND ADDRESS<CRLF> :59:/ <CRLF> BENEFICIARY NAME<CRLF> AND ADDRESS<CRLF> -} In the text of a S.W.I.F.T. messages, <CRLF> is a mandatory field delimiter. 2.4 The MT 101 co nsi sts o f two sequences: Sequence A General Information is a single occurrence mandatory sequence and contains information to be applied to all individual transactions detailed in sequence B. Sequence B Transaction Details is a repetitive sequence; each occurrence provides details of one individual transaction. Fields which appear in both sequences are mutually exclusive. The general definition of a field format is using the following symbols: x = any character of the permitted character set n = digits a = letters c = Alphabetic letters (upper case) and digits only! = fixed length, for ex. 3!a = always 3 letters

8 4*35x = up to 4 lines of up to 35 characters each [...] = subfield is optional The permitted character set is as follows: a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., + { } Cr Lf Space Although part of the character set, the curly brackets are permitted as delimiters and cannot be used within the text of message. Character - is not permitted as the first character of the line. All non permitted characters will be converted to blanks. Lower case characters are converted to upper case characters. Ä and Å will be converted to A, Ö will be converted to O and Ü will be converted to U. 3 M T F o r m a t S p e c i f i c a t i o n s Status Tag Field Name Content Options NO Mandatory Sequence A Common Elements M 20 Sender s Reference 16x 1 O 21R Customer Specified 16x 2 Reference O 50L Instructing Party 35x 3 O 50H Ordering Customer /34x 4*35x 4 O 52a Account Servicing Institution A or C 5 O 51A Sending Institution A 6 M 30 Requested Execution 6!n 7

9 Date O 25 Authorisation 35x > Mandatory Repetitive Sequence B Transaction Details M 21 Transaction Refer- 16x 9 ence O 21F F/X Deal Reference 16x > O 23E Instruction Code 4!c [/30x] M 32B Currency/Transaction Amount 3!a15d 12 O 50L Instructing Party 35x 13 O 50H Ordering Customer /34x 4*35x 14 O 52a Account Servicing Institution A or C 15 O 56a Intermediary A, C or D 16 O 57a Account With Institution A, C or D 17 M 59 Beneficiary [/34x] 4*35x 18 O 70 Remittance Information 4*35 19 O 77B Regulatory Reporting 3*35 20 O 33B Currency/Original Ordered 3!a15d 21 Amount M 71A Details of Charges 3!a 22 O 25A Charges Account /34x 23 O 36 Exchange Rate 12d M = Mandatory, O = Optional

10 3.1 MT 101 Netwo rk (SWIFT) Vali dated Rul es C 1 If an exchange rate is given in field 36, the corresponding forex deal must be referenced in field 21F. Sequence B if field 36 is... Sequence B then field 21F is... Present Mandatory Not present Optional C 2 If an exchange rate is given in field 36, the original ordered amount in the original currency must be given in field 33B, and vice-versa Sequence B if field 33B is... Sequence B then field 36 is... Present Mandatory Not present Not allowed Sequence B if field 36 is... Sequence B then field 33B is... Present Mandatory Not present Not allowed C 3 If there is only one debit account, the ordering customer must be identified in field 50H of sequence A. Conversely, if multiple debit accounts are used, they must be identified for every transaction in sequence B. Consequently, field 50H must be present in either sequence A or in each occurrence of sequence B, but must never be present in both sequences, nor be absent from both sequences. Sequence A if field 50H is... Sequence B then field 50H is... Present Not present Not allowed Mandatory

11 C 4 Field 50L may be present in either sequence A or in each occurrence of sequence B, but must not be present in both sequences. Sequence A if field 50L is... Sequence B then field 50L is... Present Not allowed Not present Optional C 5 If field 33B is present in sequence B, its currency code must be different from the currency code in field 32B in the same occurrence of sequence B. Examples: Valid :32B:USD1000, :33B:CHF1200, :32B:CHF1200, :33B:USD1000, Invalid :32B:USD1000,00 :33B:USD1000, :32B:CHF1200, :33B:CHF1000,00 C 6 Field 52a may be present in either sequence A or in each occurrence of sequence B, but must not be present in both sequences. Sequence A if field 52a is... Sequence B then field 52a is... Present Not present Not allowed Optional C 7 If field 56a is present, field 57a must also be present. Sequence A if field 56a is... Sequence B then field 57a is... Present Mandatory

12 Not present Optional 3.2 MT101 Fi el d Speci fi cations 1. Field 20: Sender s Reference NETWORK RULES USAGE RULES 16x Mandatory This field specifies the reference assigned by the Sender (Danske Bank) to unambiguously identify the message This field must not start or end with a slash / and must not VALIDATED contain two consecutive slashes //. The reference must be unique for each message and is part of the message identification and transaction identification which is to be used in related queries, cancellations, etc. The Ordering Customer (the customer of Danske Bank) may also provide this field with his own unique reference for each message. 2. Field 21R Customer Specified Reference 16x Optional This field specifies the reference to the entire message as signed by eitherthe: instructing party, when present or ordering customer, when the instructing party is not present.

13 NETWORK RULES This field must not start or end with a slash / and must not VALIDATED contain two consecutive slashes // 3. Field 50L: Instructing Party Conditional USAGE RULES 35x (C4) This field identifies the customer which is authorised by the account owner/account servicing institution to order all the transactions in the message. This field must only be used when the instructing customer is not also the account owner. 4. Field 50H: Ordering Customer USAGE RULES /34x (Account) 4*35x (Name & Address) Conditional (C3) This field identifies the account owner whose account is to be debited with all transactions in sequence B. Both the account number of the ordering customer at the Receiver or account servicing institution and the name of the ordering customer (name and address) must be present. 5. Field 52a: Account Servicing Institution Option A [/1!a][/34x] (Party Identifier) 4!a2!a2!c[3!c] (BIC, Bank Identifier Code)

14 CODES With option A Option C Conditional (C6) This field specifies the Account Servicing Institution, when other than the Receiver, which services the account of theaccount Owner to be debited. Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash ( // ): AT 5!n Austrian Bankleitzahl /34x (Party Identifier) AU 6!n Australian Bank State Branch (BSB) BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number ES 8..9n Spanish Domestic Interbanking Code FW without the 9 Pay by Fedwire

15 digit code IT x Italian Domestic Identific ation Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code With option C: AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) Code BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number CH 6!n CHIPS Universal Identifier CP 4!n CHIPS Participant Identifier ES 8..9n Spanish Domestic Interbanking Code FW 9!n Fedwire Routing Number IT x Italian Domestic Ident ification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code SW 3..5n Swiss Clearing Code (BC code) SW 6!n Swiss Clearing Code (SIC code) USAGE RULES The coded information contained in field 52a

16 should be meaningful to the Receiver of the message. Option A is the preferred option. If the account servicing institution cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double slash //. 6. Field 51A: Sending Institution Option A [/1!a][/34x] (Party Identifier) Not used This field identifies the Sender of the message. 4!a2!a2!c[3!c] (BIC) 7. Field 30: Requested Execution Date NETWORK Date must be a valid date expressed as YYMMDD. VALIDATED 6!n (Date) Mandatory This field specifies the date on which all subsequent transactions should be initiated by the executing bank.

17 RULES USAGE RULES This is the date on which the ordering customer s account(s) is (are) to be debited. 8. Field 25: Authorisation 35x Optional This field specifies additional security provisitions, e.g. a digital signature, between the ordering customer/instructing party and the account servicing financial institution. 9. Field 21: Transaction Reference NETWORK VALIDATED RULES USAGE RULES 16x Mandatory This field specifies the unambiguous reference for the individual trans action contained in a particular occurrence of sequence B. This field must not start or end with a slash / and must not contain two consecutive slashes // In transaction specific queries, cancellations, etc., the Sender s reference together with the content of this field provides the transaction identification.

18 10. Field 21F: F/X Deal Reference NETWORK VALIDATED RULES 16x Conditional (C1) This field specifies the foreign exchange contract reference between the ordering customer and the account servicing financial institution. This field must not start or end with a slash / and must not contain two consecutive slashes // 11. Field 23E: Instruction Code CODES CHQB CORT INTC NETS RTGS 4!c[/30x] (Instruction Code)(Additional Information) Optional This field specifies instructions for the account servicer of the ordering customer. One of the following codes must be used. This transaction contains a request that the beneficiary be paid via issuance of a cheque. This transaction contains a payment that is made in settlement of a trade, e.g., foreign exchange deal, securities transaction. This transaction contains an intra-company payment, i.e. a payment between two companies belonging to the same group. This transaction contains a payment that should be settled via a net settlement system, if available. This transaction contains a payment that should be settled via a real time gross set-

19 URGP PHON OTHR NETWORK VALIDATED RULES tlement system, if available This transaction contains a time sensitive payment which should be executed in an expeditious manner. This transaction requires the beneficiary to be contacted by telephone and should be followed by the appropriate telephone number. This code is meant for the last financial Institution in the chain. Used for bilaterally agreed codes/information. The actual bilateral code/information needs to be specified in the Additiona Information. Additional Information must be used only in combination with PHON and OTHR When field 23E is used more than once, the following combinations are not allowed : CHQB with URGP CHQB with RTGS CHQB with NETS CHQB with PHON NETS with RTGS. 12. Field 32B: Currency/Transaction Amount 3!a15d (Currency) (Amount) Mandatory This field specifies the currency and the amount of the subsequent transfer to be executed by the Receiver.

20 NETWORK VALIDATED RULES USAGE RULES Currency must be a valid ISO 4217 currency code. 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 that specific currency. The amount is subject to deduction of the Receiver s/beneficiary bank s charges if field 71A is BEN or SHA. 13. Field 50L: Instructing Party USAGE RULES 35x Conditional (C4) This field identifies the customer which is authorised by the account owner/account servicing institution to order all the transactions in this particular occurrence of sequence B. This field must only be used when the instructing customer is not also the account owner. 14. Field 50H: Ordering Customer USAGE RULES /34x (Account) 4*35x (Name & Address) Conditional (C3) This field specifies the ordering customer which is the account owner ordering the transaction in the same occurrence of the sequence. Both the account number of the ordering customer at the Receiver or account servicing institution and the name of the ordering customer (name and address) must be present.

21 15. Field 52a: Account Servicing Institution Option A [/1!a][/34x] (Party Identifier) 4!a2!a2!c[3!c] (BIC) CODES with option A Option C /34x (Party Identifier) Conditional (C6) This field specifies the Account Servicing Institution, when other than the Receiver, which services the account of the account owner to be debited. Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash ( // ): AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number ES 8..9n Spanish Domestic Interbanking Code FW without the 9 digit code Pay by Fedwire IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code with option C: AT 5!n Austrian Bankleitzahl

22 AU 6!n Australian Bank State Branch (BSB) Code BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number CH 6!n CHIPS Universal Identifier CP 4!n CHIPS Participant Identifier ES 8..9n Spanish Domestic Interbanking Code FW 9!n Fedwire Routing Number IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code SW 3..5n Swiss Clearing Code (BC code) SW 6!n Swiss Clearing Code (SIC code) USAGE RULES The coded information contained in field 52a should be meaningful to the Receiver of the message. Option A is the preferred option. If the account servicing institution cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double slash //. 16. Field 56a: Intermediary Option A [/1!a][/34x] (Party Identifier)

23 4!a2!a2!c[3!c] (BIC) Option C /34x (Party Identifier) Option D [/1!a][/34x] (Party Identifier) With option A 4*35x (Name & Address) Optional This field specifies the financial Institution between the Receiver and the account with institution, through which the transaction must pass. CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash ( // ): AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number ES 8..9n Spanish Domestic Interbanking Code FW without the 9 Pay by Fedwire

24 digit code IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code With option C: AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) Code BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number CH 6!n CHIPS Universal Identifier CP 4!n CHIPS Participant Identifier ES 8..9n Spanish Domestic Interbanking Code FW 9!n Fedwire Routing Number IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code SW 3..5n Swiss Clearing Code (BC code) SW 6!n Swiss Clearing Code (SIC code) USAGE RULES The intermediary may be a branch or affiliate of the Receiver or the account with institu-

25 tion, or an entirely different financial institution. When one of the codes //FW (with or without the 9-digit number),//au, //SC, //CP or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming S.W.I.F.T. payment be made to the party in this field via Fedwire, US banks require that the code FW appears in the optional Party Identifier of field 56a or 57a. When it is necessary that an incoming S.W.I.F.T. payment be made to the intermediary or the account with institution via a real-time gross settlement system (RTGS), the code //RT should appear in the optional Party Identifier of field 56a or 57a. Option A is the preferred option. If the intermediary cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by a double slash //. Option D must only be used when there is a need to be able to specify a name and address, e.g., due to regulatory considerations. 17. Field 57a: Account With Institution Option A [/1!a][/34x] Party Identifier) 4!a2!a2!c[3!c] (BIC) Option C /34x (Party Identifier) Option D [/1!a][/34x] 4*35x Conditional Party Identifier) This field specifies the financial institution, when other than the Receiver, which services the account for the beneficiary customer.

26 CODES Party Identifier may be used to indicate a national clearing system code. The following codes may be used preceded by a double slash ( // ): With option A : AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association Payment Routing Number ES 8..9n Spanish Domestic Interbanking Code FW without the 9 Pay by Fedwire digit code IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code With options C and D: AT 5!n Austrian Bankleitzahl AU 6!n Australian Bank State Branch (BSB) Code BL 8!n German Bankleitzahl CC 9!n Canadian Payments Association

27 Payment Routing Number CH 6!n CHIPS Universal Identifier CP 4!n CHIPS Participant Identifier ES 8..9n Spanish Domestic Interbanking Code FW 9!n Fedwire Routing Number IT x Italian Domestic Identification Code RT Real Time Clearing System SC 6!n CHAPS Branch Sort Code SW 3..5n Swiss Clearing Code (BC code) SW 6!n Swiss Clearing Code (SIC code) USAGE RULES When one of the codes //FW (with or without the 9-digit number), //AU, //SC, //CP or //RT is used, it should appear only once and in the first of the fields 56a and 57a of the payment instruction. When it is necessary that an incoming S.W.I.F.T. payment be made to the party in this field via Fedwire, US banks require that the code FW appears in the optional Party Identifier of field 56a or 57a. When it is necessary that an incoming S.W.I.F.T. payment be made to the intermediary or the account with institution via a realtime gross settlement system (RTGS), the code //RT should appear in the optional Party Identifier of field 56a or 57a. Option A is the preferred option.if the account with institution cannot be identified by a BIC, option C should be used containing a 2!a clearing system code preceded by A double slash //. Option D must only be used when there is a need to be able to specify a name and address, e.g., due to regulatory considerations.

28 18. Field 59: Beneficiary [/34x] (Account) 4*35x (Name & Address) Mandatory This field identifies the beneficiary of the subsequent operation from the particular occurrence of sequence B. 19. Field 70: Remittance Information 4*35x (Narrative) Optional This field specifies details of the individual transactions which are to be transmitted to the beneficiary customer. 20. Field 77B: Regulatory Reporting 3*35x (Narrative) In addition to narrative text, the following line formats may be used: Line 1 /8a/2!a[//additional information] (Code)(Country) (Narrative) Line 2-6 [//continuation of additional information (Narrative) Optional This field specifies code(s) for the statutory and/or regulatory information required by the authorities in the country of Receiver or Sender/originating customer.

29 CODES USAGE RULES The information required is covered by a pre-established bilateral agreement between the Receiver and the Ordering Customer, and between the Ordering Customer and the Sender. When the residence of either the ordering customer or beneficiary customer is to be identified, the following codes may be used: ORDERRES Residence of ordering customer BENEFRES Residence of beneficiary customer Country consists of the ISO country code of the country of residence of the ordering customer or beneficiary customer. The information required is covered by a pre-established bilateral agreement between the Receiver and the ordering customer, and between the ordering customer and the Sender. The information specified must not have been explicitly conveyed in another field. 21. Field 33B: Currency/Original Ordered Amount 3!a15D (Currency) (Amount) NETWORK VALIDATED RULES Conditional (C2) This field specifies the original currency and amount as specified by the Ordering Customer. Currency must be a valid ISO 4217 currency code. 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.

30 USAGE RULES This field is used when the currency and amount are different from those specified in field 32B. 22. Field 71A: Details of Charges VALUES USAGE RULES 3!a (Code) Mandatory This field specifies which party will bear the applicable charges for the subsequent transfer of funds. One of the following code words must be used: OUR All transaction charges are to be borne by the ordering customer SHA All transaction charges other than the charges of the fi nancial institution servicing the ordering customer ac count are borne by the beneficiary customer. BEN All transaction charges are to be borne by the beneficiary Customer These charge code words cover potential charges associated with the sending of a subsequent MTs 100, 102,103. Charges for sending the MT101 should be handled outside of this message type. 23. Field 25A: Charges Account USAGE RULES / 34x (Account) Optional This field specifies the ordering customer s account number to which applicable transaction charges should be separately applied. When used, the account number must be different from the account number specified in field 50H.

31 24. Field 36: Exchange Rate NETWORK VALIDATED RULES 12d (Rate) Conditional (C2) This field specifies the exchange rate applied by the ordering customer/ instructing party when converting the original ordered amount to the transaction amount. The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length.