General Mt SWIFT

Standards

Standards MT November 2010

General Information This document provides information about all Standards MT (Message Type) categories, and explains the general rules, conventions, and principles for the Standards MTs. The document explains the organisation of the Standards documentation and the benefits of message standards. This document also provides a description of the ISO Business Identifier Code. This document is for all SWIFT customers (this includes operators and application developers), vendors, and service bureaux.

23 July 2010


Table of Contents Preface .Preface .............................................................................................................................................................................4 1

2

3

4

5

Standards MT Volumes Description ....................................................................................................... 5 1.1

Volume/Chapter Explanation ................................................................................................................... 5

1.2

Standards MT Volumes ............................................................................................................................ 6

1.3

Formatting Explanation .......................................................................................................................... 10

Introduction to Standards MT ................................................................................................................. 15 2.1

Reason for Standards MT ...................................................................................................................... 15

2.2

Standards Development and Implementation Process ..................................................................... 15

2.3

Standards Maintenance Process .......................................................................................................... 15

2.4

Message Envelope Structure ................................................................................................................ 16

2.5

Message Validation Description ........................................................................................................... 17

Business Identifier Code (BIC) ................................................................................................................ 18 3.1

Introduction ............................................................................................................................................... ............................................................................................................................................... 18

3.2

Business Identifier Code Structure ....................................................................................................... 18

3.3

Using BICs in SWIFT Messages .......................................................................................................... 19

3.4

Standards for SWIFT BICs and non-SWIFT BICs ............................................................................. 19

Message Structure and Message Types ............................................................................................. 23 4.1

SWIFT Message Structure .................................................................................................................... 23

4.2

SWIFT Message Types .......................................................................................................................... 23

4.3

Message Length and Structure ............................................................................................................. 44

4.4

Message Structure Example ................................................................................................................. 45

Field Structure ................................................................................................................................................ 46 5.1

6

7

2

Overview ................................................................................................................................................... 46

Characters ........................................................................................................................................................ 49 6.1

SWIFT Character Set (X Character Set) ............................................................................................. 49

6.2

EDIFACT Level A Character Set (Y Character Set) .......................................................................... 49

6.3

Information Service Character Set (Z Character Set) ....................................................................... 49

Field Formatting Rules ............................................................................................................................... 50 7.1

General Rules .......................................................................................................................................... 50

7.2

Dates ......................................................................................................................................................... 50

7.3

Numbers ................................................................................................................................................... 51

7.4

Currency Codes ....................................................................................................................................... ....................................................................................................................................... 52

7.5

................................................................................................................................... 52 Party Identification ...................................................................................................................................

7.6

Times ......................................................................................................................................................... ......................................................................................................................................................... 67

7.7

Value Date Ordering ............................................................................................................................... 67

General Information


Table of Contents Preface .Preface .............................................................................................................................................................................4 1

2

3

4

5

Standards MT Volumes Description ....................................................................................................... 5 1.1

Volume/Chapter Explanation ................................................................................................................... 5

1.2

Standards MT Volumes ............................................................................................................................ 6

1.3

Formatting Explanation .......................................................................................................................... 10

Introduction to Standards MT ................................................................................................................. 15 2.1

Reason for Standards MT ...................................................................................................................... 15

2.2

Standards Development and Implementation Process ..................................................................... 15

2.3

Standards Maintenance Process .......................................................................................................... 15

2.4

Message Envelope Structure ................................................................................................................ 16

2.5

Message Validation Description ........................................................................................................... 17

Business Identifier Code (BIC) ................................................................................................................ 18 3.1

Introduction ............................................................................................................................................... ............................................................................................................................................... 18

3.2

Business Identifier Code Structure ....................................................................................................... 18

3.3

Using BICs in SWIFT Messages .......................................................................................................... 19

3.4

Standards for SWIFT BICs and non-SWIFT BICs ............................................................................. 19

Message Structure and Message Types ............................................................................................. 23 4.1

SWIFT Message Structure .................................................................................................................... 23

4.2

SWIFT Message Types .......................................................................................................................... 23

4.3

Message Length and Structure ............................................................................................................. 44

4.4

Message Structure Example ................................................................................................................. 45

Field Structure ................................................................................................................................................ 46 5.1

6

7

2

Overview ................................................................................................................................................... 46

Characters ........................................................................................................................................................ 49 6.1

SWIFT Character Set (X Character Set) ............................................................................................. 49

6.2

EDIFACT Level A Character Set (Y Character Set) .......................................................................... 49

6.3

Information Service Character Set (Z Character Set) ....................................................................... 49

Field Formatting Rules ............................................................................................................................... 50 7.1

General Rules .......................................................................................................................................... 50

7.2

Dates ......................................................................................................................................................... 50

7.3

Numbers ................................................................................................................................................... 51

7.4

Currency Codes ....................................................................................................................................... ....................................................................................................................................... 52

7.5

................................................................................................................................... 52 Party Identification ...................................................................................................................................

7.6

Times ......................................................................................................................................................... ......................................................................................................................................................... 67

7.7

Value Date Ordering ............................................................................................................................... 67

General Information

Table of Contents

8

Euro-Related Information (ERI) .............................................................................................................. 69 8.1

Deletion of National Currency Denomination (NCD) Currency Codes ........................................... 69

8.2

Euro-Related Information (ERI) ............................................................................................................ 69

8.3

Message Specific Guidelines on the Use of ERI ............................................................................... 72

8.4

ERI Validation and Examples ................................................................................................................ 79

Legal .Legal Notices ...............................................................................................................................................................91

23 July 2010

3


Preface Significant changes The following tables list all significant changes to the content of the MT General Information since the 24 July 2009 edition. These tables do not include editorial changes that SWIFT makes to improve the usability and comprehension of the document. New information

Location

Addition of field 70G of MT 564

6.3, "Information Service Character Set (Z Character Set)" on page 49

Addition of a new section for option no letter

7.5.2, "Option No Letter: Name and Address" on page 54

Addition of a new rule section for option D

7.5.6, "Option D: Name and Address" on page 56

Addition of a new section for option F

7.5.7, "Option F: Party Identifier / Name and Address" on page 60

Addition of a new section for option G

7.5.8, "Option G: Identifier Code" on page 63

Addition of a new rule section for option K

7.5.11, "Option K: Name and Address" on page 65

Introduction of the Euro in Estonia

8.1, "Deletion of National Currency Denomination (NCD) Currency Codes" on page 69 8.3.3, "Messages with Value Date Validation" on page 75

Updated information

Location

BIC/BEI change. BIC now stands for business Changes apply throughout the document identifier code. The concept of BEI (business entity identifier) has been removed. Financial institution BIC replaces the former BIC concept. Non-financial institution BIC replaces the former BEI concept. Allow the "metals messages" to be used for nonmetals, that is change the names and scopes of the suite of messages to "commodities" rather than "metals". This also means changing the names of fields that contain "metal" to "commodity" and revising the definitions accordingly.

1.1, "Volume/Chapter Explanation" on page 5

Update format of code /NAME/ for option J Party identification with no Party Identifier

7.5.10, "Option J: Party Identification with no Party Identifier " on page 64

Deleted information

Location

Deletion of references to BEI

Changes apply throughout the document

Deletion of references to MTs that have been deleted in SRG 2011 (308, 645, 810, 812, 813, 820, 821, 822, 823)

4.2, "SWIFT Message Types " on page 23

Warning

4

1.2.3, "Category Volumes: Message Text Standards" on page 8 4.2, "SWIFT Message Types " on page 23

8.3.3, "Messages with Value Date Validation" on page 75

This volume contains information effective as of the November 2010 Standards Release. Therefore the 24 July 2009 edition of the User Handbook Standards MT volumes remains effective until November 2010.

General Information

Standards MT Volumes Description

1


1.1

Volume/Chapter Explanation Standards MT volumes All SWIFT messages exchanged between users must accord with the message text standards described in the Standards MT volumes. To achieve this, it may be necessary for some users to make changes to their policies and procedures to bring their communications in line with those of the SWIFT community. The Standards MT volumes describe the message text standards which have been developed by representatives from the user community, and which are currently in effect. They consist of: • Standards MT General Information • Standards MT General Field Definitions plus Ten Category volumes containing the respective message text standards: • Category 1 - Customer Payments and Cheques • Category 2 - Financial Institution Transfers • Category 3 - Treasury Markets - Foreign Exchange, Money Markets and Derivatives • Category 4 - Collections and Cash Letters • Category 5 - Securities Markets • Category 6 This volume consists of 2 books: – Commodities – Syndications • Category 7 - Documentary Credits and Guarantees • Category 8 - Travellers Cheques • Category 9 - Cash Management and Customer Status • Category n - Common Group Messages

Additional Standards MT volumes To assist users, usage guidelines have been published in three additional Standards MT volumes for specific categories of messages. These volumes contain guidelines for using message standards. The three volumes are: • Standards MT Usage Guidelines • Category 1 - Customer Payments and Cheques - Message Usage Guidelines • Category 5 - Securities Markets - Message Usage Guidelines 23 July 2010

5


Additional volumes are issued separately for: • advance information, published as the Standards Release Guide • supplementary information, as appropriate

1.2

Standards MT Volumes

1.2.1

Standards MT General Information Volume

Overview The Standards MT General Information volume contains information which is pertinent to all categories of messages. It includes, for example, an explanation of how the information is organised, the benefits of using message standards and the description of the Business Identifier Code.

Chapters description Chapter

Description

1 - "Standards MT Volumes Description"

This chapter contains: • a description of the information which is contained in each volume of the Standards MT volume set • an explanation of the presentation of field definitions, category information and message type formats

2 - "Introduction to Standards MT"

This chapter contains: • a description of the reasons message standards are needed, including the benefits realised through their proper use • information about the method used by SWIFT to update current standards, and to develop new ones, in order to ensure compatibility with current financial practices • a list of the standard development organisations SWIFT consults with when developing message text formats and definitions • a brief description of the format checking performed by the SWIFT system on outgoing SWIFT messages

3 - "Business Identifier Code (BIC)"

This chapter contains: • a description of the purpose and development of the Business Identifier Code • information regarding the nature and format of the components of the Business Identifier Code (BIC) • an explanation on the use of non-SWIFT (not connected) BICs and SWIFT (connected) BICs

6

General Information


Chapter

Description

4 - "Message Structure and Message Types"

This chapter contains: • definitions and illustrations of the structure of a message • a description of the purpose of the category designation within the Message Type (MT) number and how the category may be used to aid the internal routing of messages • a list of all SWIFT message types

5 - "Field Structure"

This chapter contains: • a definition and illustration of the structure and general format restrictions on a field within a message • an explanation of the rules for the formatting of dates, currency codes and parties (that is, the account number line and format options)

6 "Characters"

This chapter lists the allowable characters in the X-, Y-, and Z-character sets.

7"Field Formatting Rules" In addition to General Rules for field formatting, this chapter also covers field formatting rules for the following elements: • Dates • Numbers • Currency Codes • Party Identification • Times • Value Date Ordering 8 - "Euro-Related Information (ERI) "

1.2.2

This chapter contains guidelines for using existing SWIFT message standards for transactions involving the euro.

Standards MT General Field Definitions Plus Volume

Overview This online publication is available only on the User Handbook Online. It allows you to search for specific pieces of information, easily and quickly as information is sorted by MT or by field tag. The Standards MT General Field Definitions plus provides a general description of all messagetext fields. It also provides information about the FIN error codes. Information which applies to fields in a specific message, for example, field usage and codes, is found in the description of the message type within the Standards category message reference guides.

23 July 2010

7


Description The Standards MT General Field Definitions plus contains a description of each field tag, including: • format options • definition • network validated rules • usage rules • relevant message types • codes

1.2.3

Category Volumes: Message Text Standards

Overview Message text standards for individual messages within each category are contained in the category volumes: • Category 1 - Customer Payments and Cheques • Category 2 - Financial Institution Transfers • Category 3 - Treasury Markets - Foreign Exchange, Money Markets and Derivatives • Category 4 - Collection and Cash Letters • Category 5 - Securities Markets • Category 6 - Treasury Markets - Commodities • Category 6 - Treasury Markets - Syndications • Category 7 - Documentary Credits and Guarantees • Category 8 - Travellers Cheques • Category 9 - Cash Management and Customer Status • Category n - Common Group Messages Each volume provides the information as described in the following table. Section

Description

Introduction

This section contains a description of the function and use of the message category. It also indicates what has changed in the book since its previous publication, and explains how the book, and each message type, is structured.

Category Message Types

This section lists and briefly describes the message types defined within the category. It also indicates: • whether the message type requires authentication • the maximum length allowed

8

General Information


Section

Description • whether the use of the message type requires registration with SWIFT in a Message User Group • information about how to register for a Message User Group

Message Type Description

This section contains detailed descriptions of each message type within the category. Including: • MT Scope • MT Format Specifications • MT Network Validated Rules • MT Usage Rules • MT Guidelines • MT Field Specifications • MT Mapping • MT Examples • additional information about the MT as required

Glossary of Terms

1.2.4

Terms and definitions that are used throughout the category.

Additional Volumes

Overview Three additional volumes contain recommendations for using messages in specific business situations. They also provide special information about more than one message type, or across more than one category of message type. These usage guidelines are recommendations and are provided for information. They do not form part of the SWIFT message text standards. Volume

Description

Standards MT Usage Guidelines

This volume recommends the use of messages for specific business situations.

Standards - Category 1 Customer - This volume contains information for using Category Payments and Cheques - Message 1 message types. Currently this volume contains the Usage Guidelines MT 104 Country Section. Standards - Category 5 - Securities This volume contains additional information for using the Category 5 message types. It explains how the Markets - Message Usage Guidelines ISO 15022 messages relate to each other, and the parties involved. It also includes a general outline of the structure of each new message.

23 July 2010

9


1.3

Formatting Explanation

1.3.1

Field Definition Format

Overview The Standards MT General Field Definitions plus contains the following information per field. Name

Description

Definition

A description of the field. Additional information which applies to a specific category, or message type, will appear in the field specifications for that message type.

Format Options

The specification of available options, or alternative formatting possibilities, for the field. The format options include restrictions on length and types of characters allowed.

1.3.2

Usage Rules

Additional information pertaining to use of the field.

Network Validated Rules

Any restrictions on use, for example, a double slash '//' is not permitted within field 20.

Message Type Use

A matrix showing the message types which use the specified field.

Codes

A matrix showing the message types which use the specified code.

Message Type Descriptions

Introduction The ten category volumes contain general information for the category and the detailed description of each message type. For each message type, the following information is provided.

Note

For the ISO 15022 securities messages in Category 5, the format specification and field specifications are presented in a slightly different way. For further explanations see Category 5 - Securities Markets - Message Usage Guidelines .

Example of an information flow The following symbols are used to identify the parties involved in the message flow:

10

General Information


Legend

Originator of the transaction Financial institution

Bank

Corporate Customer Sender or Receiver

Other parties involved in the transaction

MT

The actual SWIFT Message

MT nnn

MT nnn

Another SWIFT message involved in the transaction

Financial institution or customer relationship

Final recipient Financial institution

Bank

Corporate Customer

1 0 0 0 0 2 0 D

In the diagrams, each customer, or financial institution, is identified by the tag number of the corresponding field, for example, 50a, Ordering Customer .

Message type scope The scope specifies the sender and receiver of the message and provides an explanation on how the message is used. In some messages, an example of the message flow is also provided.

Message type format specifications The format specifications are the rules for the layout of the message type. This information is provided in table form as shown below:

23 July 2010

11


MT nnn (Message Type name) Status

Tag

Field Name

Content/Options

No.

M

20

Transaction Reference Number

16x

1

M

21

Related Reference

16x

2

Mandatory Sequence A (Sequence Name) M

25

Account Identification

35x

3

M

32A

Value Date, Currency Code, Amount

6!n3!a15d

4

----> Optional Repetitive Sequence B (Sequence Name) O

52a

Ordering Institution

A or D

5

M

71B

Detail of Charges

6*35x

6

O

72

Sender to Receiver Information

6*35x

7

----| M = Mandatory O = Optional

MT nnn (Message Type name) provides the message type number and name. The table headings have the following meanings: • Status indicates if the field is: – M - Mandatory – O - Optional The status M for fields in optional (sub) sequences means that the field must be present if the (sub)sequence is present, and is otherwise not allowed. • Tag is the field identification. • Field Name is the detailed name of the field tag, for this message type. • Content/Options provides permitted field length and characteristics. • No. identifies the number of the field in the Field Specifications for the message type. It is also called Index. Only fields and field tag options, which are shown in the message format, may be used in that message type. Some of the fields in the format have names different from those in Standards MT General Field Definitions plus . The name in the Message Type Format overrides that given in the Standards MT General Field Definitions plus . Some message formats are separated into sequences of fields, as shown below. An arrow indicates that a sequence of fields may be repeated. Status

Tag

Field Name

Content/Options

No.

First sequence 1 2 ----> 12

General Information


Status

Tag

Field Name

Content/Options

No.

Second Sequence 3 4 ----| Third sequence 5 6 7 M = Mandatory O = Optional

The arrows (----> and ----|) indicate that the second sequence may be repeated.

MT network validated rules Network validated rules are validated on the network, that is, they are identified with an error code. Rules specified in this section affect more than one field in the message, placing a 'condition' on one of the fields specified. They are identified as Cn, or conditional rules. For example, in the MT 202, a rule states that if field 56a (Intermediary) is present, field 57a (Account With Institution) must also be present (Error Code C81).

MT usage rules Usage rules are not validated on the network, that is, no error code is defined for them, but are nevertheless mandatory for the correct usage of the message. Rules specified in this section affect more than one field in the message, or more than one SWIFT message.

MT market practice rules Market practice rules specify the rules published by a recognised Market Practice Group, for example, for category 5, the Securities Market Practice Group (SMPG). It informs the reader of the existence of a global market practice document on the business process in which the concerned field or message type is used. The absence of a market practice rule notation does not mean that no market practices exist for the concerned field or message type. The presence of a market practice rule is merely an indicator of a known market practice. Furthermore, readers should be aware that in addition to global market practices there may also be countryspecific requirements that should be considered when using the field or message type.

MT guidelines Guidelines are not validated on the network and are not mandatory for the correct usage of the message. They concern good practices. Guidelines specified in this section affect more than one field in the message, or more than one SWIFT message.

MT field specifications The rules for the use of each field in the message are specified in this section. Each field is identified by its index number (as shown in the No. column of the MT format specifications), field tag and detailed field name, followed by a description of the field. The description may contain some, or all, of the following: a. FORMAT specifies the field formats which are allowed in the field. b. PRESENCE indicates if the field is mandatory, optional, or conditional in its sequence. 23 July 2010

13


c. DEFINITION specifies the definition of the field in this sequence of the message type. d. CODES lists all codes available for use in the field. If there is more than one subfield for which codes are defined, each separate code list will be identified with a CODES heading. When a list of codes is validated by the network, the error code will be specified. e. NETWORK VALIDATED RULES specifies rules that are validated on the network, that is, rules for which an error code is defined. Generally, rules specified in this section affect only the field in which they appear. In some cases, rules which are validated at the message level, that is, rules which affect more than one field, are repeated in this section. This is the case when the rule does not affect the presence of the field, but information within several fields, for example, a currency which must be the same for more than one field in the message. f. USAGE RULES specifies rules that are not validated on the network, that is, rules for which no error code is defined, but are nevertheless mandatory for the correct usage of the field. Rules specified in this section affect only the field in which they appear. g. EXAMPLES provides one or more examples of the field as it will be formatted/used.

MT mapping MT mapping explains how to map the fields of the message into another SWIFT message, either of the same, or a different, message type.

MT example Examples are provided to illustrate the correct use of a message. Examples always include: • narrative , which provides a brief description of a transaction • information flow, which illustrates the relationships between the parties involved in the message (see below diagram) • SWIFT format, which provides the message using the defined SWIFT format, and providing an explanation, where necessary, of the fields which have been used The sender, receiver and message type are summarily identified. Trailer contents are not shown.

Note

14

For further information about the header and trailer, see the FIN Service Description .

General Information

Introduction to Standards MT

2


2.1

Reason for Standards MT Why Standards MT? The message text standards have been developed to support the business transactions of SWIFT users. To ensure that the multitude of practices and conventions of users are in harmony, financial messages transmitted via the SWIFT network must adhere to the message text standards. Standards enable financial institutions to move from manual to automated initiation and processing of financial transactions.

Key benefits There are important benefits which result from standardisation of messages. These include: • automation • reduced risk of errors and misunderstandings • reduced operating costs • improved productivity • increased efficiency in processing of messages (routing and preparation) • faster and more cost effective account reconciliation • the ability to maintain more comprehensive management information

2.2

Standards Development and Implementation Process Board Paper 828 (R) For details about the standards development and implementation process, please refer to BP828 (R) - Standards development and implementation process, rev.3 , approved by the SWIFT Board of Directors in 2007. This paper is available upon request from National User Group Chairpersons or from the SWIFT Standards Department.

2.3

Standards Maintenance Process Introduction Maintenance projects aim at maintaining the functionality of existing standards. They are carried out to bring existing standards in line with business changes, or to correct technical problems. There are two ways to submit maintenance requests (change requests) to SWIFT, as follows: • through User Group Chairpersons • through representative market practice groups in which there are SWIFT members

23 July 2010

15


Note

Individual users and members may only submit maintenance requests to their User Group Chairperson (requests submitted directly to SWIFT are returned).

Maintenance deliverables The deliverables are the following: 1. Fifteen months prior to implementation (SR-15), SWIFT publishes a high-level document (for budget and resource allocation). It highlights the potential scope and size of the subject maintenance release, based on the change requests received. These changes must still be validated by a Working Group and some of them may be reworded, redefined or even removed. 2. Eleven months prior to implementation (SR-11), SWIFT publishes a revised, high-level document (for budget and resource allocation), which shows only those change requests that were approved by the working groups and accepted by a country vote. 3. Ten months prior to implementation (SR-10), the Standards Release Guide (SRG) provides details of the changes published in the revised, high-level document. 4. Five months prior to implementation (SR-5), the User Handbook is available on www.swift.com. 5. The changes are implemented on the network on the Standards Release (SR-0) date.

Approval Process Sixteen months prior to a planned standards release date (SR-16), the SWIFT Standards department analyses all received change requests. They send the outcome of this analysis to a Maintenance Working Group (MWG) for discussion and approval. MWGs include experts in the business domain and, ideally, in the standards to be maintained. Members are country representatives appointed by their respective User Group Chairperson. The message text formats are developed in line, or in consultation, with various bodies: 1. MWGs review and agree on the validity of the change requests. 2. Country vote takes place on MWG-agreed changes. 3. The Board Standards Committee must approve the country-vote results before the changes are considered final and published in the final-SRG. For more details on any of the processes described in this section, please visit Standards on www.swift.com, or contact the Support team.

2.4

Message Envelope Structure Overview All messages (financial and system) conform to a defined structure, generally including a header, a message text and a trailer.

Note

16

For further details about the message structure, see the FIN Service Description .

General Information


2.5

Message Validation Description Rule The SWIFT system validates the structure of all messages sent via the FIN network. If the SWIFT system finds an error, it will reject the message and inform the sender by a negative acknowledgement (NAK). The NAK will display a text error. Where possible, it will also give the location of the text error by indicating the number of the line on which the error occurred.

Exceptions Exceptions to this rule, which may be based on either system constraints or on the logical layout of the message or field, include: • An error code and line number which relates to a network validated rule violation. In these situations the system may give the line number of the last text line of the message, or if the error occurred within a repetitive sequence, the line number relative to either the beginning or end of the sequence. • An error code and line number which indicate a text error on the previous line.

Note

For additional information about error codes, see the FIN Error Codes .

Some errors, for example, an invalid message type, will prevent any further message validation by the SWIFT system.

Message text validation Validation of message text includes checking the following: • the correct sequence of fields • the presence of mandatory fields, that is, those required in the message type being sent • the presence of only those permitted optional fields for the message type • correct content, for example, numbers or letters and length for each field/subfield; in some cases, codes are validated • the permitted character set • the presence of the decimal comma in numbers and amounts • that in amounts, the correct number of digits appears after the decimal comma for the currency of the message field, for example, not more than 2 for USD • that the sum of individual amounts in the message is equal to the sum of amounts • date validity, for example, day not higher than 31 • conditional relationships, that is, the network validated rules for each message type. Depending on system constraints, not all conditional relationships will be validated by the SWIFT system • codes, where an error code is specified in the Field Specifications of the message description

23 July 2010

17


3

Business Identifier Code (BIC)

3.1

Introduction Overview In the financial environment, a number of telecommunication services have defined coding schemes for identifying financial institutions as well as corporate entities. As a result, many financial institutions and some corporates have more than one code assigned, while others have no codes assigned. To ensure the availability of a unique identifier, an International Standard - ISO 9362 - has been established. This standard specifies a universal method for identifying financial institutions and is intended to facilitate automated processing of telecommunication messages. SWIFT is the designated ISO Registration Authority for these ISO codes, and is responsible for their assignment and subsequent publication.

Business Identifier Codes (BICs) ISO 9362 Business Identifier Codes (BICs) are used in certain fields of messages (for example, field 53a, Sender's Correspondent, or field 59A, Beneficiary Customer) to identify a party in the transaction. When a BIC is available (for example, the party to be specified has been assigned a BIC), it should be used whenever possible, as it is standardised and can therefore be automatically processed by the receiver. Both financial institutions and non-financial institutions can be identified with a BIC.

3.2

Business Identifier Code Structure

3.2.1

Components of a Business Identifier Code

Description The Business Identifier Code (BIC) consists of eight or eleven characters, comprised of the first three, or all four of the following components:

3.2.2

INSTITUTION CODE

4!a

COUNTRY CODE

2!a

LOCATION CODE

2!c

BRANCH CODE

[3!c]

SWIFT and non-SWIFT BICs

Description Business Identifier Codes (BICs) must be registered codes, either connected (referred to as a SWIFT BIC) or not connected (referred to as a non-SWIFT BIC). For financial institutions, corporate institutions, or funds, which are not SWIFT users (that is which are not connected), the eighth character of the BIC must be the digit '1'. 18

General Information


The following illustrates a BIC of a non-connected institution, with and without a branch code: :53A:CHBAHKH1 :54A:CHBLGB21BBB

3.3

Using BICs in SWIFT Messages Identifying the message sender and receiver SWIFT financial and system messages may only be sent from and received by SWIFT users. Therefore, non-SWIFT Business Identifier Codes (BICs) (that is, those which contain the digit '1' in the eighth position) cannot be included in the header of a SWIFT message.

BICs in the message text Several of the party fields in the text of financial message types (see "Party Identifier" on page 53) provide options to identify an institution or corporation by its Identifier Code. Published BICs may be used as Identifier Code in these party field options when selected. The SWIFT system validates the accuracy of the Identifier Code used. There are restrictions on the use of BIC in some of the party fields. "BIC" is used when either a financial institution or a non-financial institution is allowed in the party field. "Financial institution BIC" is used if only financial institution details are allowed in the party field and "non-financial institution BIC" is used if only non-financial institution details are allowed in the party field. Customers can find more information about party formats and validation rules in the Standards MT documentation.

BIC Directory ISO Business Identifier Codes are listed in the International Business Identifier Code Directory (BIC Directory), published by SWIFT as the ISO Registration Authority for ISO 9362. The directory is published on a monthly basis. All registered ISO 9362 BICs including branch codes, are published in the BIC Directory by default. A user can request that a BIC be registered but not published. Unpublished BICs may only be used where there is a bilateral agreement between the sender and the receiver. Unpublished 8-character SWIFT BICs may only be used in the header of a message and not as Identifier Code in fields, for example, 53a, 58a..., of a message.

Note

3.4

For further information, contact End-to-End Ordering, S.W.I.F.T. SCRL, Avenue Adèle 1, B-1310 La Hulpe, Belgium (SWIFT BIC: SWHQBEBBCOS).

Standards for SWIFT BICs and non-SWIFT BICs Introduction This section describes the standards for registered SWIFT BICs and non-SWIFT BICs used in SWIFT messages. Details regarding SWIFT's policy concerning the use of SWIFT BICs can also be found in the FIN Service Description .

23 July 2010

19


3.4.1

Components of a BIC

Introduction All SWIFT BICs and non-SWIFT BICs have the same basic structure except that non-SWIFT BICS must specify the digit '1' in the eighth position. For addressing purposes, the BIC is used with an additional character in the ninth position, shown as the logical terminal code: Institution code Country code Location code Logical terminal code Branch code

a

a

a

a

a

a

c

c

c

c

c

c

1

2

3

4

5

6

7

8

9

10

11

12

SWIFT Destination Logical Terminal Identifier Note: a = Letters only c = Letters and digits only

2 0 0 0 0 2 0 D

Institution code The four-digit institution code is unique to each institution, and identifies the institution worldwide. The institution code may be selected by the customer institution, subject to the following rules: • An institution code is only valid when approved by SWIFT. • A proposed code which is misleading will be rejected by SWIFT, for example, BANK, or GIRO. • SWIFT will allow an institution to use the institution code of another, if agreed by the institution code owner.

Country code The country code identifies the country or geographical territory in which the user is located. It consists of the ISO two-alphabetic character country code, for example, CL = Chile. The country code must reflect the geographical location of the business unit. A current list of ISO country codes may be found in the information section of the BIC Directory. The country code must reflect the geographical location of the business unit.

Location code The location code consists of two alphanumeric characters, and identifies, within a country or geographical territory, the region and/or city in which the user is located.

20

General Information


The first component of the location code is the region code. It consists of one alphanumeric character (the digits '0' '1' are not permitted). A region code is used to: • split a country into geographical parts • identify major commercial locations within a country • represent a time zone in a country The second component of the location code is the suffix code. It consists of one alphanumeric character (excluding the digit '0' and the letter 'O' - the digit '0' is dedicated to test and training destinations). Where required, the suffix code enables a subdivision within a region or city, or distinguishes destinations with the same institution code, country code and region code. For non-SWIFT BICs, this suffix code must be '1'.

Logical terminal code The terminal code identifies a specific terminal connection within a destination. It consists of one alphanumeric character (the digits '0' and '1' are not permitted). This code is not included in the BICs published in the BIC Directory .

Branch code The branch code is an optional component for all BICs. However, once registered, and published in the directory as part of a SWIFT user's BIC, its use is highly recommended. The branch code consists of three alphanumeric characters. A branch code can be registered to identify: • a 100 %-owned branch of the requestor's institution • a department within the requestor's institution The following restrictions exist for branch code registration: • 'X' is not permitted as the first character of a branch code. • The branch code 'BIC' may not be used. • The default branch code for SWIFT BICs which do not include a registered branch code is 'XXX'. • Registration of a branch code denoting a geographical location in a country other than that indicated by the country code within the 8-character BIC, is prohibited. • All registered and published branch codes must be able to receive and act upon all message types in accordance with the receiver's responsibility and liability as defined in the FIN Service Description . • An institution may request that a branch code not be published. All unpublished branch codes must be covered by a bilateral agreement between sender and receiver.

3.4.2

SWIFT BIC

Description A SWIFT BIC is formed from the combination of an institution code, a country code and a location code.

23 July 2010

21


Each user must register and publish at least one 8-character SWIFT BIC of a geographical nature per country. These codes are sufficient for the SWIFT system to determine where to deliver a message. In addition to the 8-character SWIFT BIC registered in the country, the user may request additional SWIFT BICs. These additional SWIFT BICs in the same country may only define a geographical location. The first six characters (institution code, country code) must be identical to the first six characters of the existing SWIFT BIC. Functional references are prohibited for 8character SWIFT BICs. Additional 8-character SWIFT BICs may be registered un-published. These un-published BICs may only be used on a bilateral basis between sender and receiver. Changes to SWIFT BICs may only be done at the time of the monthly BIC Directory publications. To be binding, these changes must be reflected in the BIC Directory. If the deadline for publication is passed, the change in SWIFT BIC may only be made in the next publication. Non-financial institutions can be further identified with one of the following subtypes: • BEID (Business Entity Identifier) • TRCO (Treasury Counterparty) • MCCO (Non-financial Institution in an MA-CUG) • SMDP (Securities Market Data Provider) • CORP (Corporate) The list of subtypes is published in the Corporations section of the BIC Directory .

22

General Information

Message Structure and Message Types

4


4.1

SWIFT Message Structure Overview All financial messages must conform to the rules of one of the message types described in the Standards MT volumes.

Message Type (MT) The message type is composed of three digits, generally defined as: Message Structure

Category Group Type

MT nnn

3 0 0 0 0 2 0 D

Where: Category

Usually describes, at a general level, the underlying business function of the message. For example: Category 1 = Customer Payments and Cheques.

Group

Describes the function of the message within the specified category. For example: 11n = Category 1 Cheque Payment Messages.

Type

Describes the specific function. For example: 112 = Status of a Request for Stop Payment of a Cheque.

From the message type (which is located in the header of a message), the receiver of a message can help to determine the message's business and function, as well as the details of its composition. This section provides the general rules for message types. Detailed specifications pertaining to individual messages can be found in the related Category volumes. More information concerning the FIN message structure can be found in Part C of the FIN Operations Guide .

4.2

SWIFT Message Types Overview The following table lists all message types defined in the Standards MT volumes, effective in the November 2010 Standards Release. For each message type, there is a short description, an indicator that the message type requires authentication (Y or N), the maximum message length (either 2,000 or 10,000) and whether the use of the message requires registration within a Message User Group (Y or N).

23 July 2010

23


Note

A Message User Group, for the purposes of this book, is a group of users who have voluntarily agreed to support the specified message type and have registered with SWIFT to send or receive the specified message type. These messages are indicated in the following table, in the column 'MUG'. (More information about Message User Groups follows this table.)

List of Message Types MT

MT Name

Purpose

Authen

Max Length

MUG

101

Request For Transfer

Requests to debit a customer's account held at another institution.

Y

10,000

Y

102

Multiple Customer Credit Transfer

Conveys multiple payment instructions between financial institutions.

Y

10,000

Y

Single Customer Credit Transfer

Instructs a funds transfer.

Y

10,000

N

103 REMIT


Instructs a fund transfer.

Y

10,000

Y

104

Direct Debit and Request for Debit Transfer Message

Conveys direct debit instructions and requests for direct debits between financial institutions.

Y

10,000

Y

105

EDIFACT Envelope

An envelope which conveys a 2k EDIFACT message.

Y

2,000

Y

107

General Direct Debit Message

Conveys direct debit instructions between financial institutions.

Y

10,000

Y

110

Advice of Cheque(s)

Advises or confirms the issuance of a cheque to the drawee bank.

Y

2,000

N

111

Request for Stop Payment of a Cheque

Requests the drawee bank to stop payment of a cheque.

Y

2,000

N

112

Status of a Request Indicates action(s) taken in for Stop Payment of attempting to stop a Cheque payment of a cheque.

Y

2,000

N

190

Advice of Charges, Interest and Other Adjustments

Advises an account owner of charges, interest and other adjustments.

Y

2,000

N

191

Request for Payment of Charges, Interest and Other Expenses

Requests payment of charges, interest or other expenses.

Y

2,000

N

192

Request for Cancellation

Requests the receiver to consider cancellation of the message identified in the request.

Y

2,000

N

102+ 103 103+

24

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

195

Queries

Requests information relating to a previous message or amendment to a previous message.

Y

2,000

N

196

Answers

Responds to an MT 195 Query or MT 192 Request for Cancellation or other message where no specific message type has been provided for a response.

Y

2,000

N

198

Proprietary Message

Contains formats defined and agreed to between users and for those messages not yet live.

Y

10,000

N

199

Free Format Message

Contains information for which no other message type has been defined.

Y

2,000

N

200

Financial Institution Transfer for its Own Account

Requests the movement of the sender's funds to its account at another financial institution.

Y

2,000

N

201

Multiple Financial Institution Transfer for its Own Account

Multiple of the MT 200.

Y

2,000

N

202

General Financial Institution Transfer

Requests the movement of funds between financial institutions except if the transfer is related to an underlying customer credit transfer that was sent with the cover method, in which case the MT 202 COV must be used.

Y

10,000

N

202 COV


Requests the movement of funds between financial institutions, related to an underlying customer credit transfer that was sent with the cover method.

Y

10,000

N

203

Multiple General Financial Institution Transfer

Multiple of the MT 202.

Y

2,000

N

204

Financial Markets Direct Debit Message

Claims funds from SWIFT member banks.

Y

2,000

Y

205

Financial Institution Transfer Execution

Further transmits a transfer request domestically except if the transfer is related to an underlying customer credit transfer that was sent with the cover method, in which case the MT 205 COV must be used.

Y

10,000

N

25


26

MT

MT Name

Purpose

Authen

Max Length

MUG

205 COV


Further transmits a transfer request domestically, related to an underlying customer credit transfer that was sent with the cover method.

Y

10,000

N

207

Request for Financial Institution Transfer

Requests to debit an Y ordering financial institution's account held at the receiving financial institution or the account servicing financial institution.

10,000

Y

210

Notice to Receive

Notifies the receiver that it will receive funds for the sender's account.

Y

2,000

N

256

Advice of NonPayment of Cheques

Informs the sender of one or more previously sent cheque truncation messages of non-payment of one or more truncated cheques. It may also be used to specify dishonoured items that result in reversing a previous payment settlement.

Y

10,000

Y

290


Advises an account owner of charges, interest or other adjustments.

Y

2,000

N

291



Y

2,000

N

292



Y

2,000

N

295

Queries


Y

2,000

N

296

Answers

Responds to an MT 295 Queries message or an MT 292 Request for Cancellation or other message where no specific message type has been provided for a response.

Y

2,000

N

298

Proprietary Message


Y

10,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

299

Free Format Message


Y

2,000

N

300

Foreign Exchange Confirmation

Confirms information agreed to in the buying/ selling of two currencies.

N

10,000

N

303

Forex/Currency Option Allocation Instruction

Instructs the allocation of a block trade (forex or currency option).

N

10,000

Y

304

Advice/Instruction of a Third Party Deal

Advises of or instructs settlement of a third party foreign exchange deal.

Y

10,000

Y

305

Foreign Currency Option Confirmation

Confirms information agreed to in the buying and selling of vanilla options on currencies.

N

2,000

N

306

Foreign Currency Option Confirmation

Confirms information agreed to in the buying and selling of exotic options on currencies.

N

10,000

N

307

Advice/Instruction of a Third Party FX Deal

Advises of or instructs settlement of a third party foreign exchange deal.

Y

10,000

Y

320

Fixed Loan/Deposit Confirmation

Confirms the terms of a contract relative to a fixed loan/deposit transaction.

N

10,000

N

321

Instruction to Settle a Third Party Loan/ Deposit

Advises the trade details and instructs the settlement of a fixed term loan/deposit done with a third party financial institution.

Y

10,000

Y

330

Call/Notice Loan/ Deposit Confirmation

Confirms the terms of a contract relative to a call/ notice loan/deposit transaction.

N

10,000

N

340

Forward Rate Agreement Confirmation

Confirms the details of a forward rate agreement.

N

10,000

N

341

Forward Rate Agreement Settlement Confirmation

Confirms the settlement details of a forward rate agreement.

N

10,000

N

350

Advice of Loan/ Deposit Interest Payment

Advises of a loan/deposit interest payment.

N

10,000

N

360

Single Currency Interest Rate Derivative Confirmation

Confirms the details of a single currency interest rate derivative swap, cap, collar or floor.

N

10,000

N

27


28

MT

MT Name

Purpose

Authen

Max Length

MUG

361

Cross Currency Interest Rate Swap Confirmation

Confirms the details of a cross currency interest rate swap transaction.

N

10,000

N

362

Interest Rate Reset/ Advice of Payment

Confirms or advises the reset rates of the floating interest rate(s) in a single or cross-currency interest rate derivative transaction and/or the payment of interest at the end of an interest period.

N

2,000

N

364

Single Currency Interest Rate Derivative Termination/ Recouponing Confirmation

Confirms the details of the partial or full termination or recouponing of a single currency interest rate swap, cap, collar, or floor.

N

10,000

N

365

Cross Currency Interest Rate Swap Termination/ Recouponing Confirmation

Confirms the details of the partial or full termination or recouponing of a cross currency interest rate swap.

N

10,000

N

380

Foreign Exchange Order

Orders to purchase or sell a specific amount of a certain currency.

Y

10,000

Y

381

Foreign Exchange Order Confirmation

Confirms the execution of an FX order previously sent.

Y

10,000

Y

390


Advises an account owner of charges, interest or other adjustments.

N

2,000

N

391



N

2,000

N

392



N

2,000

N

395

Queries


N

2,000

N

396

Answers

Responds to an MT 395 Queries or an MT 392 Request for Cancellation or other message where no specific message type has been provided for a response.

N

2,000

N

398

Proprietary Message

Contains formats defined and agreed to between

N

10,000

N

General Information


MT

MT Name

Purpose

Authen

Max Length

MUG

users and for those messages not yet live.

23 July 2010

399

Free Format Message


N

2,000

N

400

Advice of Payment

Advises of a payment under a collection or part thereof. It also handles the settlement of proceeds.

Y

2,000

N

405

Clean Collection

Conveys instructions to obtain payment or acceptance against specified conditions. The message is used for clean collections only and supports financial documents such as accepted and nonaccepted bills of exchange and promissory notes.

Y

10,000

Y

410

Acknowledgement

Acknowledges receipt of a collection. It also specifies if the collecting bank does not intend to act in accordance with the collection instruction.

Y

2,000

N

412

Advice of Acceptance

Informs the remitting bank of the acceptance of one or more drafts under one collection instruction.

Y

2,000

N

416

Advice of NonPayment/ NonAcceptance

Advises of the nonpayment or nonacceptance under a previously received collection.

Y

10,000

Y

420

Tracer

Enquires about documents sent for collection.

Y

2,000

N

422

Advice of Fate and Request for Instructions

Advises the remitting bank of the fate of one or more collection documents; usually accompanied by one or more questions or requests.

Y

2,000

N

430

Amendment of Instructions

Amends collection instructions.

Y

2,000

N

450

Cash Letter Credit Advice

Confirms that the face Y amount of cash letter(s) received has been credited under usual reserve (subject to final payment).

2,000

N

455

Cash Letter Credit Adjustment Advice

Advises the account owner of adjustments made to its account (related to a previous credit for a cash letter).

2,000

N

Y

29


30

MT

MT Name

Purpose

Authen

Max Length

MUG

456

Advice of Dishonour

Advises the account owner that financial document(s) included in the cash letter have been dishonoured for reasons specified in the advice.

Y

2,000

N

490


Advises an account owner of charges, interest or other adjustments to its account.

Y

2,000

N

491



Y

2,000

N

492



Y

2,000

N

495

Queries


Y

2,000

N

496

Answers

Responds to an MT 495 Queries message or MT 492 Request for Cancellation or other messages where no specific message type has been provided for the response.

Y

2,000

N

498

Proprietary Message


Y

10,000

N

499

Free Format Message


Y

10,000

N

500

Instruction to Register

Instructs the registration, deregistration or reregistration of a financial instrument at the registration provider.

Y

10,000

N

501

Confirmation of Registration or Modification

Confirms the registration, deregistration or reregistration of a beneficial owner or shareholder with the registration provider.

Y

10,000

N

502

Order to Buy or Sell

Instructs the purchase or sale of a given quantity of a specified financial instrument under specified conditions.

Y

10,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

503

Collateral Claim

Requests new or additional collateral, or the return or recall of collateral.

Y

10,000

Y

504

Collateral Proposal

Proposes new or additional collateral.

Y

10,000

Y

505

Collateral Substitution

Proposes or requests the substitution of collateral held.

Y

10,000

Y

506

Collateral and Exposure Statement

Provides the details of the valuation of both the collateral and the exposure.

Y

10,000

Y

507

Collateral Status and Processing Advice

Advises the status of a Y collateral claim, a collateral proposal, or a proposal/ request for collateral substitution.

10,000

Y

508

Intra-Position Advice

Reports on the movement of securities within the holding.

Y

10,000

N

509

Trade Status Message

Provides information about the status of a previously executed trade.

Y

10,000

N

510

Registration Status and Processing Advice

Advises the status of a registration instruction or modification.

Y

10,000

N

513

Client Advice of Execution

Provides brief and early Y information about a securities deal, for example, a block trade that is to be allocated before final confirmation.

10,000

N

514

Trade Allocation Instruction

Instructs the allocation of a block trade.

Y

10,000

N

515

Client Confirmation of Purchase or Sale

Provides a detailed accounting of financial instruments purchased or sold by the sender on behalf of the receiver or its client. It may also convey the payment details of the purchase or sale. It may also be sent by, or via an ETC service provider.

Y

10,000

N

516

Securities Loan Confirmation

Confirms the details of a securities loan, including collateral arrangements. It may also confirm the details of a partial recall or return of securities previously out on loan.

Y

2,000

N

31


32

MT

MT Name

Purpose

Authen

Max Length

MUG

517

Trade Confirmation Affirmation

Positively affirms the details of a previously received confirmation/ contract note.

Y

10,000

N

518

Market-Side Securities Trade Confirmation

Confirms the details of a trade and, where necessary, its settlement to a trading counterparty.

Y

10,000

N

519

Modification of Client Details

Instructs the modification of client details at the registration provider.

Y

10,000

N

524

Intra-Position Instruction

Instructs the movement of securities within the holding.

Y

10,000

N

526

General Securities Lending/Borrowing Message

Requests the borrowing of securities or notifies the return or recall of securities previously out on loan. It may also be used to list securities available for lending.

Y

2,000

N

527

Triparty Collateral Instruction

Performs a specific action on a collateral management transaction.

Y

10,000

Y

528

ETC Client-Side Settlement Instruction

Sent by an ETC service provider, it communicates early settlement information to a custodian or clearing agent about a client-side trade.

Y

10,000

N

529

ETC Market-Side Settlement Instruction

Sent by an ETC service provider, it communicates early settlement information to a custodian or clearing agent about a market-side trade.

Y

10,000

N

530

Transaction Processing Command

Requests the modification Y of a processing indicator or other non-matching information.

10,000

N

535

Statement of Holdings

Reports at a specified time, the quantity and identification of securities and other holdings which the account servicer holds for the account owner.

Y

10,000

N

536

Statement of Transactions

Provides details of increases and decreases of holdings which occurred during a specified period.

Y

10,000

N

537

Statement of Pending Transactions

Provides details of pending Y increases and decreases of holdings at a specified time.

10,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

538

Statement of IntraPosition Advices

Provides details of increases and decreases in securities within the holding during a specified period.

Y

10,000

N

540

Receive Free

Instructs a receipt of financial instruments free of payment. It may also be used to request a cancellation or pre-advise an instruction.

Y

10,000

N

541

Receive Against Payment

Instructs a receipt of financial instruments against payment. It may also be used to request a cancellation or pre-advise an instruction.

Y

10,000

N

542

Deliver Free

Instructs a delivery of financial instruments free of payment. It may also be used to request a cancellation or pre-advise an instruction.

Y

10,000

N

543

Deliver Against Payment

Instructs a delivery of financial instruments against payment. It may also be used to request a cancellation or pre-advise an instruction.

Y

10,000

N

544

Receive Free Confirmation

Confirms a receipt of financial instruments free of payment. It may also be used to cancel or reverse a confirmation.

Y

10,000

N

545

Receive Against Payment Confirmation

Confirms a receipt of financial instruments against payment. It may also be used to cancel or reverse a confirmation.

Y

10,000

N

546

Deliver Free Confirmation

Confirms a delivery of financial instruments free of payment. It may also be used to cancel or reverse a confirmation.

Y

10,000

N

547

Deliver Against Payment Confirmation

Confirms a delivery of financial instruments against payment. It may also be used to cancel or reverse a confirmation.

Y

10,000

N

548

Settlement Status and Processing Advice

Advises the status of a settlement instruction or replies to a cancellation request.

Y

10,000

N

33


34

MT

MT Name

Purpose

Authen

Max Length

MUG

549

Request for Statement/ Status Advice

Requests a statement or a status message.

Y

10,000

N

558

Triparty Collateral Status and Processing Advice

Provides validation results and status advice re collateral instructions and proposed collateral movements.

Y

10,000

Y

559

Paying Agent's Claim

Claims reimbursement of income or redemption proceeds, or a combination of both.

Y

2,000

N

564

Corporate Action Notification

Provides an account owner with details of a corporate action event and the choices available to the account owner. It also provides the account owner with details on the impact a corporate action event will have on a safekeeping or cash account, for example, entitlement calculation.

Y

10,000

N

565

Corporate Action Instruction

Instructs the custodian on Y the investment decision made by an account owner relative to a corporate action event.

10,000

N

566

Corporate Action Confirmation

Confirms to the account owner that securities and/ or cash have been credited/debited to an account as a result of a corporate action event.

Y

10,000

N

567

Corporate Action Status and Processing Advice

Indicates the status, or a change in status, of a corporate action-related transaction previously instructed by, or executed on behalf of, the account owner.

Y

10,000

N

568

Corporate Action Narrative

Provides complex instructions or narrative details relating to a corporate action event.

Y

10,000

N

569

Triparty Collateral and Exposure Statement

Provides the details of the valuation of both the collateral and the exposure.

Y

10,000

Y

574(1)

IRS 1441 NRA-IRS Beneficial Owners' List

Provides owner or pooled income information for a period of time arranged between the intermediary and the withholding agent.

Y

10,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

574(2)

IRS 1441 NRAForm W8-BEN

Certifies the foreign status of a beneficial owner for United States tax withholding.

Y

10,000

N

575

Report of Combined Activity

Reports on all securities and cash activity for a given combination of safekeeping and cash accounts.

Y

10,000

Y

576

Statement of Open Orders

Provides details of orders to buy or to sell financial instruments, as at a specified date, which have been accepted by the sender, but which have not yet been executed.

Y

10,000

N

577

Statement of Numbers

Provides certificate numbers of securities.

Y

10,000

N

578

Settlement Allegement

Advises the account owner that a counterparty has alleged a settlement instruction on the account owner's account.

Y

10,000

N

579

Certificate Numbers Replaces or supplements the 'certificate numbers' field in a primary message, for example, MT 577.

Y

2,000

N

581

Collateral Adjustment Message

Claims or notifies a change in the amount of collateral held against securities out on loan or for other reasons.

Y

2,000

N

582

Reimbursement Claim or Advice

Claims reimbursement of funds paid on behalf of the receiver or of securities received which are due to the sender. It may also advise that funds and/or securities have or will be remitted by the sender in favour of the receiver.

Y

2,000

N

584

Statement of ETC Pending Trades

Provides statuses and details of executed trades which are not yet matched nor affirmed.

Y

10,000

N

586

Statement of Settlement Allegements

Provides details of pending Y settlement allegements.

10,000

N

587

Depositary Receipt Instruction

Instructs the issuance or release of a depositary receipt from/to ordinary shares, or the conversion from one type of depositary receipt to another.

10,000

N

Y

35


36

MT

MT Name

Purpose

Authen

Max Length

MUG

588

Depositary Receipt Confirmation

Confirms the issuance or release of a depositary receipt from/to ordinary shares, or the conversion from one type of depositary receipt to another.

Y

10,000

N

589

Depositary Receipt Status and Processing Advice

Advises the status, or change in status, of a depositary receipt.

Y

10,000

N

590



Y

2,000

N

591



Y

2,000

N

592



Y

2,000

N

595

Queries


Y

2,000

N

596

Answers

Responds to an MT 595 Queries or MT 592 Request for Cancellation or other message where no specific message type has been provided for the response.

Y

2,000

N

598

Proprietary Message


Y

10,000

N

599

Free Format Message


Y

2,000

N

600

Commodity Trade Confirmation

Confirms the details of a commodity trade and its settlement.

N

2,000

N

601

Commodity Option Confirmation

Confirms the details of a commodity option contract.

N

2,000

N

604

Commodity Transfer/Delivery Order

Instructs the receiver to transfer by book-entry, or physically deliver, a specified type and quantity of commodity to a specified party.

Y

2,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

605

Commodity Notice to Receive

Notifies the receiver of an impending book-entry transfer or physical delivery of a specified type and quantity of commodity.

N

2,000

N

606

Commodity Debit Advice

Advises the receiver of a debit entry to a specified commodity account.

N

2,000

N

607

Commodity Credit Advice

Advises the receiver of a credit entry to a specified commodity account.

N

2,000

N

608

Statement of a Commodity Account

Provides the details of all bookings to a commodity account.

N

2,000

N

609

Statement of Commodity Contracts

Identifies all outstanding commodity contracts, as at a specified date for which confirmations have been exchanged.

N

2,000

N

620

Commodity Fixed Loan/Deposit Confirmation

Confirms a commodity fixed term loan/deposit contract.

N

10,000

Y

643

Notice of Drawdown/ Renewal

Provides notice of the borrower(s) request for drawdown(s)/renewal(s) on a given date.

Y

2,000

N

644

Advice of Rate and Amount Fixing

Specifies the interest rate and, if applicable, the exchange rate, for the next interest period.

Y

2,000

N

646

Payment of Principal and/or of Interest

Advises of payments and/ or prepayments of principal and/or of interest with the same value date, but not related to any subsequent drawing or renewal.

Y

2,000

N

649

General Syndicated Provides for Facility Message communications related to syndicated facilities for which no specific message has been defined.

Y

2,000

N

690



Y

2,000

N

691



Y

2,000

N

692


Requests the receiver to consider cancellation of

Y

2,000

N

37


MT

MT Name

Purpose

Authen

Max Length

MUG

the message identified in the request.

38

695

Queries


Y

2,000

N

696

Answers

Responds to an MT 695 Queries message or MT 692 Request for Cancellation or other messages where no specific message type has been provided for the response.

Y

2000

N

698

Proprietary Message


Y

10,000

N

699

Free Format Message


Y

2,000

N

700

Issue of a Documentary Credit

Indicates the terms and conditions of a documentary credit.

Y

10,000

N

701

Issue of a Documentary Credit

Continuation of an MT 700 for fields 45a, 46a and 47a.

Y

10,000

N

705

Pre-Advice of a Documentary Credit

Provides brief advice of a documentary credit for which full details will follow.

Y

2,000

N

707

Amendment to a Documentary Credit

Informs the receiver of amendments to the terms and conditions of a documentary credit.

Y

10,000

N

710

Advice of a Third Bank's or a NonBank's Documentary Credit

Advises the receiver of the terms and conditions of a documentary credit.

Y

10,000

N

711

Advice of a Third Bank's Documentary Credit


Y

10,000

N

720

Transfer of a Documentary Credit

Advises the transfer of a documentary credit, or part thereof, to the bank advising the second beneficiary.

Y

10,000

N

721

Transfer of a Documentary Credit


Y

10,000

N

General Information


23 July 2010

MT

MT Name

Purpose

Authen

Max Length

MUG

730

Acknowledgement

Acknowledges the receipt of a documentary credit message and may indicate that the message has been forwarded according to instructions. It may also be used to account for bank charges or to advise of acceptance or rejection of an amendment of a documentary credit.

Y

2,000

N

732

Advice of Discharge

Advises that documents received with discrepancies have been taken up.

Y

2,000

N

734

Advice of Refusal

Advises the refusal of documents that are not in accordance with the terms and conditions of a documentary credit.

Y

10,000

N

740

Authorisation to Reimburse

Requests the receiver to honour claims for reimbursement of payment(s) or negotiation(s) under a documentary credit.

Y

2,000

N

742

Re-imbursement Claim

Provides a reimbursement claim to the bank authorised to reimburse the sender or its branch for its payments/ negotiations.

Y

2,000

N

747

Amendment to an Authorisation to Reimburse

Informs the reimbursing Y bank of amendments to the terms and conditions of a documentary credit, relative to the authorisation to reimburse.

2,000

N

750

Advice of Discrepancy

Advises of discrepancies and requests authorisation to honour documents presented that are not in accordance with the terms and conditions of the documentary credit.

Y

10,000

N

752

Authorisation to Pay, Accept or Negotiate

Advises a bank which has requested authorisation to pay, accept, negotiate or incur a deferred payment undertaking that the presentation of the documents may be honoured, notwithstanding the discrepancies, provided they are otherwise in order.

Y

2,000

N

39


40

MT

MT Name

Purpose

Authen

Max Length

MUG

754

Advice of Payment/ Advises that documents Acceptance/ have been presented in Negotiation accordance with the terms of a documentary credit and are being forwarded as instructed. This message type also handles the payment/ negotiation.

Y

2,000

N

756

Advice of Reimbursement or Payment

Advises of the Y reimbursement or payment for a drawing under a documentary credit in which no specific reimbursement instructions or payment provisions were given.

2,000

N

760

Guarantee

Issues or requests the issue of a guarantee.

Y

10,000

N

767

Guarantee Amendment

Amends a guarantee Y which has been previously issued or requests the amendment of a guarantee which the sender has previously requested to be issued.

10,000

N

768

Acknowledgement of a Guarantee Message

Acknowledges the receipt of a guarantee message and may indicate that action has been taken according to instructions.

Y

2,000

N

769

Advice of Reduction or Release

Advises that a bank has Y been released of its liability for a specified amount under its guarantee.

2,000

N

790



Y

2,000

N

791



Y

2,000

N

792



Y

2,000

N

795

Queries


Y

2,000

N

796

Answers

Responds to an MT 795 Queries message or MT 792 Request for

Y

2,000

N

General Information


MT

MT Name

Purpose

Authen

Max Length

MUG

Cancellation or other messages where no specific message type has been provided for the response.

23 July 2010

798

Proprietary Message


Y

10,000

N

799

Free Format Message


Y

10,000

N

800

T/C Sales and Settlement Advice [Single]

Provides the sale and settlement details for the sale of travellers cheques by a single selling agent.

Y

2,000

N

801

T/C Multiple Sales Advice

Provides the details (excluding the settlement details) of the sales of travellers cheques in cases where the data is lengthy or includes data from several selling agents.

Y

2,000

N

802

T/C Settlement Advice

Provides the settlement details of multiple sales of travellers cheques.

Y

2,000

N

824

T/C Inventory Destruction/ Cancellation Notice

Notifies the issuer of the destruction/cancellation of travellers cheque inventory held by the selling agent. It may also request a selling agent to destroy/cancel travellers cheque inventory.

Y

2,000

N

890



Y

2,000

N

891



Y

2,000

N

892



Y

2,000

N

895

Queries


Y

2,000

N

896

Answers

Responds to an MT 895 Queries message or MT 892 Request for

Y

2,000

N

41


MT

MT Name

Purpose

Authen

Max Length

MUG

Cancellation or other messages where no specific message type has been provided for the response.

42

898

Proprietary Message


Y

10,000

N

899

Free Format Message


Y

2,000

N

900

Confirmation of Debit

Advises an account owner of a debit to its account.

N

2,000

N

910

Confirmation of Credit

Advises an account owner of a credit to its account.

N

2,000

N

920

Request Message

Requests the account N servicing institution to send an MT 940, 941, 942 or 950.

2,000

N

935

Rate Change Advice

Advises the receiver of general rate change(s) and/or rate change(s) which applies to a specific account other than a call/ notice loan/deposit account.

N

2,000

N

940

Customer Statement Message

Provides balance and transaction details of an account to a financial institution on behalf of the account owner.

N

2,000

N

941

Balance Report

Provides balance information of an account to a financial institution on behalf of the account owner.

N

2,000

N

942

Interim Transaction Report

Provides balance and transaction details of an account, for a specified period of time, to a financial institution on behalf of the account owner.

N

2,000

N

950

Statement Message

Provides balance and transaction details of an account to the account owner.

N

2,000

N

970

Netting Statement

Provides balance and transaction details of a netting position as recorded by a netting system.

N

2,000

N

General Information


MT

MT Name

Purpose

Authen

Max Length

MUG

971

Netting Balance Report

Provides balance information for specified netting position(s).

N

2,000

N

972

Netting Interim Statement

Advises interim balance and transaction details of a netting position as recorded by a netting system.

N

2,000

N

973

Netting Request Message

Requests an MT 971 or 972 containing the latest available information.

N

2,000

N

985

Status Enquiry

Requests an MT 986.

N

2,000

N

986

Status Report

Provides business-related information about a customer or institution.

N

2,000

N

990



N

2,000

N

991



N

2,000

N

992



N

2,000

N

995

Queries


N

2,000

N

996

Answers

Responds to an MT 995 Queries or MT 992 Request for Cancellation or other messages where no specific message type has been provided for the response.

N

2,000

N

998

Proprietary Message


N

10,000

N

999

Free Format Message


N

2,000

N

(1) The appropriate format validation of the IRS Beneficial Owners' List of the MT 574 IRS 1441 NRA is triggered by the code IRSLST in field 119 ({3:{119:IRSLST}}) of the user header of the message (block 3). (2) The appropriate format validation of the IRS Form W8-BEN of the MT 574 IRS 1441 NRA is triggered by the code W8BENO in field 119 ({3:{119:W8BENO}}) of the user header of the message (block 3).

23 July 2010

43


Message User Group registration procedure Registration is free of charge. To register to use one or more Message Types (MTs), submit a registration request (Register to a Message User Group) through www.swift.com. To withdraw from a Message User Group, use the Deregister from a Message User Group request To get the list of other members of a particular Message User Group, send an MT 999 to the Customer Implementation team (SWHQBEBBCOS).

4.3

Message Length and Structure Rules There are several rules which must be followed when structuring financial messages: • There are two alternative message length limitations for financial messages, as explained below. For both alternatives, there is a difference between the message length calculation on input and on output. The total number of characters always includes headers and trailers. (See "SWIFT Message Types " on page 23 for information about the maximum length per message type.) Alternatives: – The number of characters allowed by the SWIFT system on input from a computer-based terminal is 2,000. On output to a computer-based terminal the system will limit the number of characters to 2,600. – The number of characters allowed by the SWIFT System on input from a computer-based terminal is 10,000. On output to a computer-based terminal the system will limit the number of characters to 10,600. The number of characters permitted on output for retrieved messages, including headers and trailers, is 11,325. • The format of each message type specifies a number of fixed and variable length fields. The presence of these fields may be mandatory or optional. • A field which is not specified in the format specifications for a particular message type must never appear. • A field may appear only once in a sequence, unless repetition is specifically allowed. • Fields are separated by a unique field separator.

44

General Information


4.4

Message Structure Example Example: structure of an MT 103 The following example illustrates the structure of a financial message (MT 103) as input by the sender. {1:F01OELBATWWAXXX0975000073}

Basic header block

{2:I103ABNANL2AXXXXU3003}

Application header block

{3:{113:URGT}{108:INTLPMTS}}

User header block

{4: (CrLf) :20:494932/DEV (CrLf) :23B:CRED (CrLf) :32A:030731EUR1958,47 (CrLf) :33B:EUR1958,47 (CrLf) :50K:FRANZ HOLZAPFEL GMBH (CrLf)

Text block

VIENNA (CrLf) :59:H.F. JANSSEN (CrLf) LEDEBOERSTRAAT 27 (CrLf) AMSTERDAM (CrLf) :70:/INV/ 18042 910412 (CrLf) :71A:SHA (CrLf)

-} {5:{CHK:123456789ABC}}

Note

23 July 2010

Trailer block

4 0 0 0 0 2 0 D

Basic Header, Application Header, User Header, Text and Trailers Blocks are not separated by CrLf. In the above example, the blocks have been shown on separate lines for purposes of clarity.

45


5

Field Structure

5.1

Overview Field structure Delimiter Field tag number Letter option Delimiter

: nn [a] :

5 0 0 0 0 2 0 D

Rules There are several rules which must be followed when structuring fields: • Each field is identified by a tag which consists of two digits, or two digits followed by a letter option. • Field structure consists of a colon ':', followed by a tag, followed by a colon ':' and the field content. • The following character restrictions are applied to field content: – it must not start with a Carriage Return, Line Feed (CrLf) – it must not be entirely composed of blank characters – within field content, apart from the first character of the field, a colon ':' or hyphen '-' must never be used as the first character of a line – except for fields 15a and 77E, a field must consist of at least one meaningful character (See the Standards MT General Field Definitions plus for formatting requirements) • Fields are separated by a 'Field Separator within Text' (CrLf:). • The first field in a message is preceded by a 'Start of Text' (CrLf:) and the last field in a message is followed by an 'End of Text' (CrLf-). • The Carriage Return, Line Feed character must always appear as a sequence. This sequence shall only be used to indicate start of text, as a field separation within text, to indicate a new line, and to indicate the end of text. • Field content may be composed of one or several subfields. When subfields appear on separate lines, the Carriage Return, Line Feed (CrLf), which is not included in the number of characters for the length of the subfield, serves as the subfield separator. Subfields: – subfields may themselves be of fixed or variable length – the order of subfields is fixed 46

General Information

Field Structure

– when necessary, subfields are separated by special symbols, for example, '/' or '//' – subfields must not be entirely composed of blank characters – subfields and/or components must consist of at least one meaningful character • Whenever a field content contains mandatory and optional subfields, at least all of the mandatory subfields must appear when that field is used. • The specification of field or subfield content may consist of: – restrictions on the length of field or subfield content, using the descriptions listed in the following table: Restrictions on Length

Types of Characters Allowed

nn

maximum length (minimum is 1)

n

numeric digits (0 through 9) only

nn-nn

minimum and maximum length

a

alphabetic letters (A through Z), upper case only

c

alphabetic letters (upper case) and digits only

h

hexadecimal letters A through F (upper case) and digits only

x

any character of the X permitted set (General FIN application set) upper and lower case allowed ("SWIFT Character Set (X Character Set)" on page 49)

y

any character of the EDIFACT level A character set as defined in ISO 9735 upper case only ("Information Service Character Set (Z Character Set)" on page 49)

z

any character as defined by the Information Service ("SWIFT Character Set (X Character Set)" on page 49)

e

blank space

d

decimals

nn!

nn*nn

fixed length

maximum number of lines times maximum line length

Examples 2n

up to 2 digits

3!a

always 3 letters

4*35x

up to 4 lines of up to 35 characters each

16-64h

at least 16 and up to 64 hexadecimal digits

– special formats, for example, for numbers and dates – codes, for example, currency codes (see the BIC Directory ) • In some messages, the field specifications may indicate specific characters, or sets of characters, for inclusion in the text of the field. These take the following forms: – codes, for example, AMEND, TRF or 08 23 July 2010

47


– slash '/' or double slash '//' – slash or double slash followed by a code, for example, //CH or /FIXED – slash followed by a code and another slash, for example, /REC/

Note

48

All codes must be in upper-case alphabetic characters. When codes contain a mix of alpha and numeric characters, the alpha character must also be in uppercase.

General Information

Characters

6

Characters

6.1

SWIFT Character Set (X Character Set) Description Computer-based terminals communicating with SWIFT use EBCDIC code. The character set is as follows: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 / - ? : ( ) . , ' + { } CR LF Space Although part of the character set, the curly brackets are permitted as delimiters and cannot be used within the text of user-to-user messages (Error Code M60).

6.2

EDIFACT Level A Character Set (Y Character Set) Description In field 77F of MT 105, the EDIFACT level A character set, as defined in ISO 9735, is used. This character set is as follows: ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 .,-()/='+:?!"%&*<>; Space Other characters are not allowed (Error Code M60).

6.3

Information Service Character Set (Z Character Set) Description In fields 70F of MT 568, field 70G of the MT 564, and 77T of MT 103, the allowed character set is as follows: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789 .,-()/='+:?!"%&*<>;{ @ # _ CrLf Space Other characters are not allowed, including the curly bracket '}' (Error Code M60).

23 July 2010

49


7

Field Formatting Rules

7 .1

General Rules Overview The following general rules apply to all fields: • The field length length and type of character( character(s), s), for example, example, letters, letters, numbers, are are specified specified in the Standards MT General Field Definitions plus and in the field specifications for individual message types. • Unless Unless oth otherw erwise ise stated stated in in the the Standards MT General Field Definitions plus or message field specifications, all specified subfields must be present: – in the order (that is, sequence sequence)) specified specified – with no separator separator symbols symbols (except (except a slash '/' or double slash slash '//' when specifie specified). d). • Brackets, Brackets, [ ], around the format format of a particular particular subfield subfield (in a field containin containing g more than one subfield), indicate that the subfield is optional within that field. For example, if the format for a field is '16x[/4x]', up to 16 characters must be present (when the field is used). The following 4 characters, preceded by a slash '/', are optional, and therefore need not be present in the field. • A field field format format may be shown shown on ttwo wo or more lines: lines: 3!n 6!n When this is the case, the information must be formatted with the CrLf character separating each line.

Note

7 .2

In the ISO 15022 securities messages, generic fields are used to specify Party, Amount, Date, Reference and Other types of data. For further explanation of this approach see Category 5 Securities Markets - Message Usage Guidelines .

Dates Formats Format: 4!n Format: 6!n Format: 8!n

Rules Dates are represented as either: 4, 6 or 8 digit integers, that is, in ISO form MMDD, YYMMDD or YYYYMMDD Where: • YY = last 2 digits of the year

50

General Information


• YYYY = all four digits of the year • MM = month • DD = day No blank spaces or other characters are permitted. Examples: • 1129 = November 29 • 941129 = 94 November 29 • 19941129 = 1994 November 29

The date field formatted as 6!n (YYMMDD) distinguishes between the 20th and 21st century as follows: If the year, (YY) is greater than 79, the date refers to the 20th century. If the year is 79 or less, the date refers to the 21st century: If YY > 79

YYMMDD = 19YYMMDD

else

YYMMDD = 20YYMMDD

The six-digit date thus ranges from 1980 to 2079. On the FIN network, there is an additional restriction for the year range where the date is affected by the Value Date Ordering process ("Value ("Value Date Ordering" on page 67) 67) The valid date range of 1980 to 2060 applies to: • field 30, 30, in MTs: MTs: 101, 104, 104, 107, 110, 110, 111, 112, 201, 201, 203, 204, 204, 207, 210, 256 • field 32A, 32A, in MTs: 102, 102, 103, 110, 111, 111, 112, 200, 200, 202, 202 COV, COV, 205, 205 205 COV, 256, 256, 910

7 .3

Numbers Format

nn...nn, nn...n

Fractional part (optional) Integer part

6 0 0 0 0 2 0 D

Usage Rules Wherever they represent a numeric value, numbers always take the same form: • The integer integer part must contain contain at least least one one digit. digit. • Decimal Decimal points are not permitted permitted.. A decimal comma comma ',' shall precede precede the fractional fractional part. • The maximum maximum length includes includes the the decimal decimal comma. • The fractional fractional part part may be missing, missing, but the the decimal decimal comma must must always always be present. present. 23 July 2010

51


• Neither Neither blank spaces, spaces, nor any any symbols symbols other than than the decimal decimal comma comma are permitted. permitted. • The integer integer part is mandatory mandatory in in the number number component, component, and at least least one character character must must appear. Leading zeros are allowed. • Normally, Normally, when a number number represents represents an amount amount of money, money, the number number of places places following following the decimal comma may not exceed the number of decimal digits valid for the specified currency. The specifications for the individual message types will indicate the fields where this is not the case. Details regarding the allowable fractional parts for each currency code may be found in the BIC Directory .

Examples

7 .4

Valid

Invalid

000,00 0, 0,67 0,25 100000, 25768, 99999999, 100, 10500,00 5,25

0000 0 .67 ,25 100.000 25-768 999.999.999 100 10500.00 5 1/4

Currency Codes Format Format: 3!a

Description A currency code normally consists of a two-letter ISO country code followed by a third letter denoting the particular currency or type of funds. For a complete list of ISO currency codes, please refer to the BIC Directory .

7 .5

Party Identification Introduction Parties may be represented in several ways: • Ide Ident ntif ifie ierr Code Code (BI (BIC) C) • branch branch (city (city)) of the send sender er or the the receive receiverr • name name and and add addre ress ss • other identif identificatio ication n codes, codes, for example example,, account account number number When necessary, party identification can be supplemented by an account number line preceding other party information.

52

General Information


7.5.1

Party Identifier

Overview When further identification of a party, for example, specification of an account number to be credited, is necessary, the party identifier should be used.

Format: [/1a][/34x] Where: Subfield 1

Subfield 2

[/1a]

Specifies which account is involved:

/C

The receiver's account serviced by the sender is credited.

/D

The sender's account serviced by the receiver is debited.

[/34x]

The account number information, preceded by a slash '/'.

Rules When the party identifier is present, the following rules apply: • The party specified in the field with the account must be the account owner. The optional party identifier must specify the account known to the account servicing institution. • Extreme care must be taken when formatting the party identifier, for example, when only subfield 2 '[/34x]' is entered, and its first and third characters consist of '/', the system can only presume that both subfields 1 and 2 are present. It will then qualify the second character for either code 'C' or 'D', and NAK the message if one or the other is not present (Error Code T51).

Note

Other fields impacted by this form of validation are: • 42A, 42D. • 50D, 50F*, 51A, 51D, 52A, 52B, 52D, 53A, 53B, 53D, 54A, 54B, 54D, 55A, 55B, 55D, 56A, 56B, 56D, 57A, 57B, 57D, 58A, 58B, 58D. • 82A, 82B, 82D, 83A, 83D, 84A, 84B, 84D, 85A, 85B, 85D, 86A, 86B, 86D, 87A, 87B, 87D, 88A, 88B, 88D. * See additional structure for party identifier in section 7.5.7, "Option F: Party Identifier / Name and Address" on page 60

Additional Rules The following additional rules apply: • An account specified in field 58a or 59a must be owned by that party and must be serviced by the financial institution in field 57a or, if field 57a is absent, by the receiver. • An account specified in field 57a must be owned by that party and must be serviced by the financial institution in field 56a or, if field 56a is absent, by the receiver. • An account specified in field 56a must be owned by that party and must be serviced by the receiver.

23 July 2010

53


• In field 53a, when when an account account is used it normally normally indicates: indicates: – which account account is to be used for reimburse reimbursement, ment, if multiple multiple accounts accounts in the currency currency of the transaction are serviced for the other party. In this case, the account should be specified – whether the sender's sender's account account serviced by the receiver, receiver, or the receiver's receiver's account serviced serviced by the sender, is to be used for reimbursement, if they both service accounts for each other in the currency of the transaction. In this case, the account to be debited or credited shall be indicated in the party identifier by either the code /C or /D, or the account, or both In both cases, this information should be specified in field 53a with the format option B (party identifier only).

Examples Valid

Invalid

:53A:/C/12-12 CITIUS33CHI

:53A:/6/12-12 CITIUS33CHI

: 5 3 B : / D / 2 4 - 24

:53 B: / A /2 4- 2 4

:53D:/52/48-48 John Doe 122 Peyton Place Elyria, OH 22216

:53D:/:/48-48 John Doe 122 Peyton Place Elyria, OH 22216

:87E:FREE /C/12-12 CHASUS33

:87E:APMT /A/12-12 CHASUS33

:87F:APMT /D/12-12 John Doe 122 Peyton Place Elyria, OH 22216

:87F:APMT /:/48-48 John Doe 122 Peyton Place Elyria, OH 22216

Example Bank A in New York services an account a ccount in USD for Bank B in London. Bank B also services, in London, a USD account (number 567-3245-01) for Bank A. Bank A sends a USD transfer to Bank B, using its USD account in London, serviced by Bank B, for reimbursement. Bank A will request that Bank B debit its account in London as follows: 53B:/D/567-3245-01

Note

7.5. 7. 5.2 2

In certain message types there are exceptions to the rules for use of the party identifier detailed in this section, for example, Field 57a in category 3 messages. In those cases, the intended use of the party identifier is described in the relevant field specification for the message type.

Opti Option on No Let Lette ter: r: Name ame a and nd Addre ddress ss

Format [/34x]

(Account)

4*35x

(Name and Address)

Definition Name and address of the party, with an optional account.

54

General Information


Rules If Account is absent, then Name and Address must not start with a slash '/' (Error code: T77).

Field assigned to this option 59

7.5. 5.3 3

Option A: Ident entifier Code

Format [/1a][/34x]

(Party Identifier)

4!a2!a2!c[3!c]

(Identifier Code)

Definition Identifier code such as a BIC. Optionally, the account of the party.

Network validation rules Identifier Code must be a registered BIC (Error codes T27, T28, T29 and T45). For institutions which are not SWIFT users, that is, which are not yet connected, the eighth position must consist of the digit '1'.

Examples The following example shows BICs of non-connected users, without, and with, a branch code: :53A:CHBAKHH1 :54A:CHBLGB21BBB

Fields assigned to this option • 41A*, 42A • 50A**, 51A, 52A, 52A, 53A, 53A, 54A, 54A, 55A, 56A, 57A, 57A, 58A, 58A, 59A • 82A, 82A, 83A, 83A, 84A, 84A, 85A, 85A, 86A, 86A, 87A, 87A, 88A 88A

Note

When this option is used, the SWIFT system will validate the correctness of the Identifier Code, that is, to ensure that it is registered : either connected or nonconnected. (*) Field 41A does not have the optional party identifier, but does have an additional subfield. See "Option D: Name and Address" on page 56 on the use of clearing codes. (**) Field 50A has the format [/34x] for Party Identifier.

7.5. 7. 5.4 4

Opti Option on B: Bra Branc nch h of of Sen Sende der/ r/Re Rece ceiv iver er

Format

23 July 2010

[/1a][/34x]

(Party Identifier)

[35x]

(Location)

55


Usage rules When used, at least one line must be present. An account number only, not followed by any other identification, is allowed (field 53a). For field 52a, the field specifications for individual message types specify whether this option identifies a branch of the sender or the receiver. In field 53a, this option specifies either the account to be debited or credited, or a branch of the sender, that is, of the financial institution specified in the sender's address in the header. In fields 54a and 57a, this option specifies a branch of the receiver, that is, of the financial institution specified in the receiver's address in the header.

Fields assigned this option 52B, 53B, 54B, 55B, 57B, 58B 82B, 84B, 85B, 87B, 88B

7.5. 7. 5.5 5

Opti Option on C: Ac Acco coun untt Num Numbe ber/ r/Pa Part rty y Ide Ident ntif ifie ierr

Format /34x

(Account)

Definition A code uniquely identifying an account and/or party. In the MTs 101, 102, 103 and 104, clearing codes may be used.

Fields assigned this option 51C, 52C, 53C, 56C, 57C, 58C 82C, 83C, 85C, 87C, 88C

Note

7.5. 5.6 6

See "Option D: Name and Address" on page 56 on the use of clearing codes.

Option D: Name and and Addres ess s

Format [/1a][/34x]

(Party Identifier)

4*35x

(Name and Address)

Note

This option is used when no other option is available. This information also applies to fields 50 (when option representing name and address is selected) and 59 (without letter option).

Definition Name and address and, optionally, the account or clearing code of the party.

56

General Information


Rules If a Party Identifier is absent, then Name and Address must not start with a slash '/' (Error code: T77).

Usage rules When the party identification is provided by name and address (whether by full postal address or informal identification), the following rules apply: • at least one line of the name and address must be present, in addition to the party identifier • the street address must be on a new line following the name • when a city is present, it must be on the last line, with the postal code (zip, etc.), state and country identification Although more than one element of an address may appear on each line, care should be taken that, when possible, no element, for example, street address, should be spread over more than one line.

National clearing codes list When the party identifier is used to indicate a national clearing system code preceded by a double slash '//', the following codes may be used: 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

GR

7!n

HEBIC (Hellenic Bank Identification Code)

HK

3!n

Bank Code of Hong-Kong

IE

6!n

Irish National Clearing Code

IN

11!n

Indian Financial System Code (IFSC) is the identification scheme defined by the Reserve Bank of India

IT

10!n

Italian Domestic Identification Code

PL

8!n

Polish National Clearing Code (KNR)

PT

8!n

Portuguese National Clearing Code

RU

9!n

Russian Central Bank Identification Code

SC

6!n

UK Domestic Sort Code

SW

3..5n

Swiss Clearing Code (BC code)

SW

6!n

Swiss Clearing Code (SIC code)

In some messages, some of these clearing codes may also be used with option A, that is, the MTs 101, 102, 103 and 104. This is indicated with the field specifications of each message type.

23 July 2010

57


When one of the codes //FW (with or without the 9-digit number), //AU, //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 SWIFT payment be made to the party in this field via Fedwire, US banks require that the code FW appears in the optional Party Identifier. When it is necessary that an incoming SWIFT payment be made to the party in this field via a real-time gross settlement system (RTGS), the code RT should appear in the optional Party Identifier. Option D must only be used in exceptional circumstances, that is, when the party cannot be identified by a BIC, and when there is a bilateral agreement between the sender and the receiver permitting its use. Unless qualified by a clearing system code or an account number, the use of option D may prevent the automated processing of the instruction(s) by the receiver.

National clearing codes formats List of codes and formats: • The Australian BSB code is the identification scheme defined by APCA (Australian Payments Clearing Association). Its structure is either: for financial institutions with an extensive branch network: – 2!n = Bank Code – 1!n = State Code – 3!n = Branch Code or for institutions with a small network: – 3!n = Bank Code – 3!n = Branch Code • The Bank Code for Hong-Kong is structured as follows: – 3!n = Bank Code • The Hellenic Bank Identification Code (HEBIC) is the identification scheme defined by the Hellenic Bank Association. Its structure is: – 3!n = Bank Code – 4!n = Branch Code • The Indian Financial System Code (IFSC) is the identification scheme defined by the Reserve Bank of India. Its structure is: – 4!a = Bank code (same as institution code in BIC - ISO 9362) – 1!n = Numerical zero - Reserved for future use – 6!c = Branch code • The structure of the Irish NSC code is 2!n4!n, where: – 2!n = Bank code – 4!n = Branch code

58

General Information


• The Italian ITBI code is the identification scheme defined by ABI (Associazione Bancaria Italiana). Its structure is: – 5!n = Bank Code (ABI) – 5!n = Branch Code (CAB) • The New Zealand Bank/Branch code is the identification scheme defined by NZBA (New Zealand Bankers Association). Its structure is: – 2!n = Bank Code – 4!n = Branch Code • The Portuguese National Clearing code is defined by the Banco de Portugal. Its structure is 4!n4!n, where: – 4!n = Bank Code (IFRI), potentially containing leading zeros – 4!n = Branch Code (BLCI) which is unique for each branch and locally assigned by the Financial Institution. • The Russian Central Bank Identification Code is to be considered as one, uniform, indivisible code. Its structure is 2!n2!n2!n3!n, where: – 2!n = Country Code. The first position is always 0 and is not shown in the database of the Central Bank of Russia. – 2!n = Region Code within the country – 2!n = Code of the division of the Central Bank in the region – 3!n = Bank Code • The South African National Clearing code is defined by BankServ, the South African Bankers Services Company Ltd. Its structure is 3!n3!n, where: – 3!n = Bank code, potentially with leading zeros – 3!n = Branch code, potentially with leading zeros • The Spanish Domestic Interbanking Code is the identification scheme defined by CCI (Centro de Cooperacion Interbancaria). Its structure is: – 4!n = Bank Code – 4!n = Branch Code – [1!n] = Check Digit

Fields assigned to this option 42D 50D, 51D, 52D, 53D, 54D, 55D, 56D, 57D, 58D 82D, 83D, 84D, 85D, 86D, 87D, 88D

Note

23 July 2010

Field 41D does not have the optional party identifier but does have an additional subfield.

59


7.5.7

Option F: Party Identifier / Name and Address

Format [35x]

(Party Identifier)

4*35x

(Name and Address)

The following line formats must be used (Error code(s): T54): Line 1 (subfield Party Identifier)

/34x

(Account)

Line 2-5 (subfield Name and Address

1!n/33x

(Number)(Details)

Line 1 (subfield Party Identifier)

4!a/2!a/27x

(Code)(Country Code)(Identifier)

Line 2-5 (subfield Name and Address

1!n/33x

(Number)(Details)

Or

Definition Name and address in a structured format to facilitate straight through processing.

Codes When subfield 1 Party Identifier is used with the (Code)(Country Code)(Identifier) format, one of the following codes must be used:

60

ARNU

Alien Registration Number

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

CCPT

Passport Number

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

CUST

Customer Identification

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

DRLC

Driver's License Number

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

EMPL

Employer Number

The code followed by a slash, '/' must be followed by the ISO country code of the registration authority, a slash, '/', the registration authority, a slash, '/' and the Employer Number.

NIDN

National Identity Number

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

SOSE

Social Security Number

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

TXID

Tax Identification Number

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

General Information


Codes Each line of subfield 2 Name and Address when present must start with one of the following numbers: 1

Name of the ordering customer

The number followed by a slash, '/' must be followed by the name of the ordering customer (where it is recommended that the surname precedes given name(s)).

2

Address Line

The number followed by a slash, '/' must be followed by an Address Line (Address Line can be used to provide for example, street name and number, or building name).

3

Country and Town

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

4

Date of Birth

The number followed by a slash, '/' must be followed by the Date of Birth in the YYYYMMDD format.

5

Place of Birth

The number followed by a slash, '/' must be followed by the ISO country code, a slash '/' and the Place of Birth.

6

Customer Identification Number

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

7

National Identity Number

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

8

Additional Information

The number followed by a slash, '/' is followed by information completing one of the following: • the Identifier provided in subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format. • the Customer Identification Number provided in subfield 2 (Name and Address) with number 6. • the National Identity Number provided in subfield 2 (Name and Address) with number 7.

Network validation rules Subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format: Country Code must be a valid ISO country code (Error code(s): T73). Subfield 2 (Name and Address): • The first line must start with number 1 (Error code(s): T56). • Numbers must appear in numerical order (Error code(s): T56). • Number 2 must not be used without number 3 (Error code(s): T56). • Number 4 must not be used without number 5 and vice versa (Error code(s): T56).

23 July 2010

61


• Number 4 must be followed by a valid date in the format YYYYMMDD and this date, local to the sender, must not be later than the date on which the message is successfully sent to SWIFT (Error code(s): T53). • Numbers 3, 5, 6 and 7 must be followed by a valid ISO country code (Error code(s): T73), a slash '/' and additional Details (Error code(s): T56). • Numbers 3, 4, 5, 6, 7 and 8 must not be repeated (Error code(s): T56). • The use of number 8 is only allowed in the following instances (Error code(s): T56): – to continue information on the Identifier of the ordering customer provided in subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format. – to continue information on the Customer Identification Number provided in subfield 2 (Name and Address) following number 6. – to continue information on the National Identity Number provided in subfield 2 (Name and Address) following number 7.

Usage rules If the account number of the ordering customer is present, it must be stated in Account. Subfield 2 (Name and Address): Numbers 1 and 2 may be repeated. Subfield 1 (Party Identifier) used with the (Code)(Country Code)(Identifier) format: if additional space is required for providing the Identifier of the ordering customer, one of the following options must be used: 1. First option (preferred): Identify the ordering customer with a different identifier where the length is not an issue. 2. Second option: Continue the information in subfield 2 (Name and Address) using number 8. Subfield 2 (Name and Address): if additional space is required for providing the Customer Identification Number (number 6) or the National Identity Number (number 7) of the ordering customer, one of the following options must be used: 1. First option (preferred): Identify the ordering customer with a different identifier where the length is not an issue. 2. Second option: Continue the information in subfield 2 (Name and Address) using number 8.

Examples Example 1 :50F:/12345678 1/SMITH JOHN 2/299, PARK AVENUE 3/US/NEW YORK, NY 10017

Example 2 :50F:/BE30001216371411 1/PHILIPS MARK 4/19720830 5/BE/BRUSSELS

Example 3

62

General Information


:50F:DRLC/BE/BRUSSELS/NB0949042 1/DUPONT JACQUES 2/HIGH STREET 6, APT 6C 3/BE/BRUSSELS

Example 4 :50F:NIDN/DE/121231234342 1/MANN GEORG 6/DE/ABC BANK/1234578293

Example 5 :50F:CUST/DE/ABC BANK/123456789/8-123456 1/MANN GEORG 2/LOW STREET 7 3/DE/FRANKFURT 8/7890

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

Field assigned to this option 50F

7.5.8

Option G: Identifier Code

Format /34x

(Account)

4!a2!a2!c[3!c]

(Identifier Code)

Definition Identifier code of the party with mandatory account number.

Network validation rules Identifier Code must be a registered BIC (Error codes T27, T28, T29, and T45).

Fields assigned to this option 50G, 52G

7.5.9

Option H: Name and Address

Format /34x

(Account)

4*35x

(Name and Address)

Definition Name and address of the party with a mandatory account.

Field assigned to this option 50H

23 July 2010

63


7.5.10 Option J: Party Identification with no Party Identifier Format (Narrative)

5*40x

Definition Identification of the party.

Codes The following codes can be used with this option. Depending on the field tag and message type, some codes may or may not be used, may exclude each other or not, or may be mandatory or not: Code

Format

Description

/ABIC/

4!a2!a2!c[3!c] or 4!a

the BIC or 'UKWN' if BIC not known

/ACCT/

34x

account followed by the account number

/NAME/

34x

name followed by the name

/ADD1/

35x

address followed by the first line of the address

/ADD2/

35x

address followed by the second line of the address

/CITY/

35x

city followed by the name of city (and state, country)

/USFW/

9!n

FedWire followed by FedWire Routing Number

/USCH/

6!n

CHIPS followed by CHIPS UID

/GBSC/

6!n

CHAPS followed by CHAPS sort code

/CLRC/

35x

Clearing Code followed by a clearing code

/NETS/

-

a net settlement is taking place

/SSIS/

-

standard settlement instructions are used

The codes do not need to be put on separate lines. It is the '/' at the beginning of a code, not the end-of-line, that marks the end of the information behind the previous code. As a result, the narrative following the code may not contain a slash '/'. The end-of-line may be part of the narrative text following the code, but it is to be ignored when reading the field. However, the end-of-line may not be part of the code.

Examples /ABIC/BNKAXA11/NAME/BANK A OF XANADU(CrLf) /NAME/BANK A OF XANADU/ABIC/BNKAXA11(CrLf) /ABIC/BNKAXA11(CrLf) /NAME/BANK A OF XANADU(CrLf) /ABIC/BNKAXA11/NAME/BRANCH B OF THE(CrLf) SECOND NATIONAL BANK A OF XANADU(CrLf)

Fields assigned to this option 53J, 56J, 57J, 58J 82J, 83J, 84J, 85J, 86J, 87J, 88J.

64

General Information


7.5.11 Option K: Name and Address Format [/34x]

(Account)

4*35x

(Name and Address)

Definition Name and address of the party, with an optional account.

Rules If Account is absent, then Name and Address must not start with a slash '/' (Error code: T77).

Field assigned to this option 50K

7.5.12 Option L: Party Identification Format 35x

(Narrative)

Definition Identification of the party

Field assigned to this option 50L

7.5.13 Option P: Party Format :4!c//4!a2!a2!c[3!c]

(Qualifier)(Identifier Code)

Definition Identification of the party, with a qualifier and an identifier code such as a BIC.

Field assigned to this option 95P

7.5.14 Option Q: Party Format :4!c//4*35x

23 July 2010

(Qualifier) (Name and Address)

65


Definition Identification of the party, with a qualifier and name and address.

Field assigned to this option 95Q

7.5.15 Option R: Party Format :4!c/8c/34x

(Qualifier) (Data Source Scheme) (Proprietary Code)

Definition Identification of the party, with a qualifier, issuer code and proprietary code.

Field assigned to this option 95R

7.5.16 Option S: Party Format :4!c/[8c]/4!c/2!a/30x

(Qualifier) (Data Source Scheme) (Type of ID) (Country code) (Alternate ID)

Definition Identification of the party, with a qualifier, an optional issuer code, type of ID, country code and alternate ID.

Field assigned to this option 95S

7.5.17 Option T: Party Format :4!c//2*35x

(Qualifier) (Name)

Definition Identification of the party, with a qualifier and name.

Field assigned to this option 95T

7.5.18 Option U: Party Format :4!c//3*35x 66

(Qualifier) (Name) General Information


Definition Identification of the party, with a qualifier and names.

Field assigned to this option 95U

7.6

Times Formats 4!n 6!n Rules Times are represented as either four or six digit integers, that is, in form HHMM or HHMMSS respectively, where (Error Code T38): • H = Hour • M = Minutes • S = Seconds No blank spaces or other characters are permitted.

Examples 0000 1200 235959

7.7

Value Date Ordering Overview The SWIFT system allows the receiver to request value date ordering of its value date sensitive messages. The value date sensitive messages are: • MT 910 • all Category 1 and Category 2 messages containing fields 30 or 32A, or both 30 and 32A, except common group messages 192, 292, 195, 295, 196 and 296 The valid range of value dates implemented on the SWIFT system for these MTs is from 1980 to 2060, and must meet the following requirements: • allowed: a year component, for example, 'YY' in the range of 80 through 60, of an ISO defined six digit integer date 'YYMMDD' • not allowed: any 'YY' component outside of this range, for example, 'YY' in the range of 61 through 79

23 July 2010

67


Example ACKed

NAKed

:32A:601130USD1, :32A:801130USD1,

:30:61130USD1, :30:791130USD1,

For the purpose of value date ordering, if there is more than one value date field in a message, the lesser date will be selected: MTxxx :30:951218 :32A:020103USD123000,00

Value date = 18th December 1995 Value Date = 3rd January 2002

In this example, field 30 Value Date (18 December 1995) is selected for value date ordering of the message. Error code 'T50' is returned after an invalid value date.

68

General Information

Euro-Related Information (ERI)

8


.1

Deletion of National Currency Denomination (NCD) Currency Codes Background On 1 March 2002, ISO announced the deletion of the National Currency Denomination (NCD) currency codes from the official ISO currency code table 4217. The currencies concerned are ATS, BEF, DEM, ESP, FIM, FRF, GRD, IEP, ITL, LUF, NLG, PTE, and XEU. On 1 January 2007, ISO announced a similar deletion for the SIT. For certain message types, when NCDs are used as the currency of settlement, SWIFT validates to ensure that the value date is not after the date on which the currencies ceased to be a legal tender: • When ATS, BEF, DEM, ESP, FIM, FRF, GRD, IEP, ITL, LUF, NLG, PTE or XEU is used, the value date must not be after 31 December 2001. • When the Slovenian currency code SIT is used, the value date must not be after 31 December 2006. • When the Cyprus currency code CYP or the Maltese currency code MTL are used, the value date must not be after 31 December 2007. • When the Slovakian currency code SKK is used, the value date must not be after 31 December 2008. • When the Estonian currency code EEK is used, the value date must not be after 31 December 2010. Until further notice, and where allowed (NCDs cannot be used in settlement amount fields), SWIFT will continue to support NCD currency codes (for example, instructed amounts, ERI) in the relevant fields of its message types.

.2

Euro-Related Information (ERI) Introduction This section discusses what is meant by Euro-Related Information (ERI).

8.2.1

ERI Content

Overview Euro-Related Information (ERI) refers to the following data: • original currency • original amount • transaction charges

23 July 2010

69


The original currency and amount in ERI is the equivalent of the information in the field containing the amount which is used for interbank settlement of the transaction. This field may contain additional information, for example, value date. ERI may be specified in one of several free-text fields preceded by a code. As of Standards Release 2001, the use of ERI was extended to non-European currencies and beyond the transition period of 3 years. In the Corporate Action messages within Category 5, codes are used to indicate the processing of redenominations.

8.2.2

ERI Usage Guidelines and Rules

Introduction The specification of ERI is always optional. If used, however, the rules specified in this section apply. These rules include: • The network validated rules must be complied with, and are validated by the network. • The usage rules must be complied with, although they are not validated by the network. • The usage guidelines are recommendations on how to specify ERI.

Network validated rules If a network validated rule mandates the presence of an exchange rate field where both the transaction amount and the original ordered amount are quoted (for example, field 36 in the MTs 101, 102, 103, 104, 107), this rule remains effective. In the case of euro-related currencies, the exchange rate field must specify the value of the fixed euro conversion rate.

Usage rules The following rules must be adhered to: • ERI may be used only when the message does not have a specific existing field to specify the information. If specific fields have been defined in a message to contain the original currency and amount, these fields, and not ERI, should be used to indicate the original currency and amount. For example, all ISO 15022 compliant Category 5 Trade Initiation and Confirmation (TIC), Settlement and Reconciliation (S&R) and Corporate Action (CA) messages contain specific fields for this purpose, as does the MT 103. • As with all other information occurring in fields 72, 77A or 79, ERI is for information purposes only. In the case of a discrepancy between ERI and the settlement amount (for example, net proceeds), specified in the message, the information in the settlement amount prevails.

Usage guidelines Guidelines when specifying fields are: • If no specific fields are available to specify the original currency and amount, ERI may be used in any message type containing a free text field 72, 77A or 79. The use of ERI is not restricted to specific message types. See "Messages Likely to Contain ERI" on page 72.

70

General Information


• The preferred field for specifying ERI is field 72. If not present, field 77A should be used. If there is no field 72 nor 77A, then field 79 should be used. • If ERI is specified in field 72, 77A, or 79 it should appear on the first line whenever possible. Whatever line is used, the ERI should always appear on the first position of that line. • For message types that do not contain a field 72, 77A nor 79, there are only two that may need to specify a second currency: MTs 940 and 942. For these two cases, subfield 9 of field 61 should be used to specify ERI. If this subfield is used for other purposes, field 86 should be used to specify ERI. It is recommended that the sender of the MT 940/942 advises the receiver whenever field 86 is used to contain ERI. • Where the settlement amount is part of a repetitive sequence which does not contain a free text field, the message should be used as a single transaction message, that is, one message should be used per transaction. • Where transaction charges are specified in ERI, this information must appear after the code / CHGS/. This will not necessarily be processed by the receiver. • ERI is designed to be passed on unchanged in the appropriate message types throughout the entire transaction, that is, throughout the chain of messages relating to the transaction. Therefore it should appear in the appropriate SWIFT messages related to the transaction.

8.2.3

ERI Structure

Format Field 72

6*35x

Field 77A

20*35x

Field 79

35*50x

Definition In addition to previously defined sender to receiver information, or other narrative information, these fields may include Euro-Related Information (ERI) for information purposes. ERI indicates currency conversion details, related to the conversion of the original currency into a settlement currency, found in free text fields. It is recommended that ERI be structured in these free text fields, using codes.

Codes The following codes must be used /OCMT/

3!a15d/

O

Original currency and amount. If no charges are specified then the original currency and amount will be the equivalent of the transaction amount specified in the message.

23 July 2010

71


/CHGS/

3!a15d/

O

Currency and amount of the transaction charges. When the BEN option is used in payments and related messages, that is, all transaction charges are to be paid by the beneficiary customer, the charges amount has been deducted from the original amount to obtain the settlement amount specified in the message.

Usage rules The network will validate the structure of ERI, but not the content.

Example :72:/OCMT/GBP2525,/ /CHGS/EUR2,40/

.3

Message Specific Guidelines on the Use of ERI Introduction This section lists message types which: • are likely to contain ERI • contain a special field for original amount • are to be validated against a specified value date

8.3.1

Messages Likely to Contain ERI

List of message types that can contain ERI in a free text field The following lists message types that are likely to contain Euro-Related Information (ERI) in a free text field. Message types that already contain a field to specify an original currency and amount, are not included here. If there are business requirements to specify ERI in other message types, these should be similarly specified in a free text field 72, 77A or 79, as explained in "ERI Structure" on page 71. This list is therefore not exhaustive.

72

MT

MT Name

Settlement Amount Field

Repetitive / Non Repetitive

ERI Field

Repetitive/ Non Repetitive

202


32A Value Date, Currency Code, Amount

NR

72

NR

202 COV



NR

72

NR

203

Multiple General Financial Institution Transfer

32B Currency Code, Amount

R

72

R

General Information


23 July 2010

MT

MT Name



ERI Field


204



R

72

R

205



NR

72

NR

205 COV



NR

72

NR

207

Request for Financial Institution Transfer


R

72

NR

400

Advice of Payment

33A Proceeds Remitted

NR

72

NR

405

Clean Collection

32a Proceeds to be Remitted in seq C

NR

72, seq A

NR

32a Proceeds to be Remitted in subseq B3

N(1)

72, seq B

NR

450



R

72

NR

455


33a Value Date and Adjustment Amount

R

72

NR

456

Advice of Dishonour

33D Total Amount Debited

R

72

NR

559

Paying Agent's Claim

34A Net Proceeds

NR

72

NR

581

Collateral Adjustment Message

34B Outstanding Collateral Value

NR

72

NR

582

Reimbursement Claim or Advice

34A Net Amount Claimed/Paid

NR

79

NR

752


33a Net Amount

NR

72

NR

754

Advice of Payment/ Acceptance/ Negotiation

34a Total Amount Claimed

NR

72

NR

756


33A Amount Reimbursed or Paid

NR

72

NR

73


MT

MT Name



ERI Field


768

Acknow ledgement of a Guarantee Message

32a Amount of Charges

NR

72

NR

769


32a Amount of Charges

NR

72

NR

900



NR

72

NR

910



NR

72

NR

940

Customer Statement Message

subfield 5 of field 61

R

61/9 or 86

R

942

Interim Transaction Report

subfield 5 of field 61

R

61/9 or 86

R

(1) Subsequence B3 is non-repetitive within the repetitive sequence B.

8.3.2

Messages Containing a Special Field for Original Amount

List of message types containing a special field for original amount The following lists message types that already have a special field for specifying an original amount to be transferred. This list is not exhaustive, as there may be other messages with special fields specifying an original amount. MT

MT Name



ERI Field


101

Request for Transfer

32B

R

33B

R

102

Multiple 32B Customer Credit Transfer

R

33B

R

Single 32A Customer Credit Transfer

NR

33B

NR

104

Direct Debit and Request for Debit Transfer

32B

R

33B

R

107

General Direct 32B Debit Message

R

33B

R

102+ 103 103+ 103 REMIT

74

General Information


8.3.3

MT

MT Name



ERI Field


513


19A::SETT

NR

19A::OCMT

NR

514


19A::SETT

NR

19A::OCMT

NR

515


19A::SETT

NR

19A::OCMT

NR

518


19A::SETT

NR

19A::OCMT

NR

528

ETC ClientSide Settlement Instruction

19A::SETT

NR

19A::OCMT

NR

529

ETC MarketSide Settlement Instruction

19A::SETT

NR

19A::OCMT

NR

541


19A::SETT

NR

19A::OCMT

NR

543


19A::SETT

NR

19A::OCMT

NR

545


19A::ESTT

NR

19A::OCMT

NR

547


19A::ESTT

NR

19A::OCMT

NR

564


19A::ESTT

NR

19A::OCMT

NR

566


19A::ESTT

NR

19A::OCMT

NR

584


19A::ESTT

NR

19A::OCMT

NR

Messages with Value Date Validation

List of message types used to transfer amounts in National Currency Denominations The following table contains messages that can be used to transfer amounts in National Currency Denominations (NCDs). 23 July 2010

75


If ATS, BEF, DEM, ESP, FIM, FRF, GRD, IEP, ITL, LUF, NLG, PTE or XEU is used, the value date has to be equal to, or before 31 December 2001. If SIT is used, the value date has to be equal to, or before 31 December 2006. If CYP or MTL is used, the value date has to be equal to, or before 31 December 2007. If SKK is used, the value date has to be equal to, or before 31 December 2008. If EEK is used, the value date has to be equal to, or before 31 December 2010. If these validations against value date fail, the message will be NAKed (Error Code E76).

Note

Statement messages are not validated against value date, since they are generally the result of earlier validated messages. Furthermore, accounts are no longer held in any of the discontinued National Currency Denominations (NCDs) mentioned above.

Currencies concerned The currencies concerned are ATS, BEF, CYP, DEM, EEK, ESP, FIM, FRF, GRD, IEP, ITL, LUF, MTL, NLG, PTE, SIT, SKK, and XEU. The table gives the message description, the field containing the NCD amount and the field containing the value date. MT

MT Name

NCD Amount Field

Value Date Field

101

Request for Transfer

32B in Seq B (each occurrence)

30 in Seq A

102

Multiple Customer Credit Transfer

32A in Seq C

32A in Seq C

32A in Seq C

32A in Seq C


32A

32A

32A

32A

32A

32A

Direct Debit and Request for Debit Transfer Message

32B (each occurrence)

30 in Seq A


30 in Seq A

107

General Direct Debit Message

32B in Seq C

30 in Seq A

200

FI Transfer for its Own Account

32A

32A

201

Multiple FI Transfer for its Own Account

32B (each occurrence

30

202

General FI Transfer

32A

32A

202 COV

General FI Transfer

32A

32A

203

Multiple General FI Transfer


30

204



30

205

FI Transfer Execution

32A

32A

205 COV

FI Transfer Execution

32A

32A

102+ 103 CORE 103+ 103 REMIT 104 104RFDD

76

General Information


MT

MT Name

NCD Amount Field

Value Date Field

207

Request for FI Transfer Message

32B (each occurrence

30 in Seq A

210

Notice to Receive


30

400

Advice of Payment

33A

33A

405

Clean Collection

32C in Subseq. B3 (each occurrence)

32C

32D in Seq C

32D

450


32A (each occurrence)

32A

455


32A

32A

33C

33C

33D

33D

456

Advice of Dishonour

32D (each occurrence)

33D

513


Seq C Order Details Field 19A Qualifier SETT

Seq C Order Details Field 98a Qualifier SETT (1)

Seq D3 Amounts Field 19A Qualifier SETT

Seq C Order Details Field 98a Qualifier SETT (1)

Seq B Confirmation Details Field 19A Qualifier SETT

Seq B Confirmation Details Field 98a Qualifier SETT (1)

Seq C3 Amounts Field 19A Qualifier SETT

Seq B Confirmation Details Field 98a Qualifier SETT (1)

Seq C Confirmation Details Field 19A Qualifier SETT

Seq C Confirmation Details Field 98a Qualifier SETT

Seq D3 Amounts Field 19A Qualifier SETT

Seq C Confirmation Details Field 98a Qualifier SETT


Seq B Confirmation Details Field 98a Qualifier SETT





Seq B Confirmation Details Field 19A Qualifier SEBL




514

515

518

528

23 July 2010




ETC Client-Side Settlement Instruction

77


78

MT

MT Name

NCD Amount Field

Value Date Field

529

ETC Market-Side Settlement Instruction





541


Seq E3 Amounts Field 19A Qualifier SETT

Seq B Trade Details Field 98a Qualifier SETT

543


Seq E3 Amounts Field 19A Qualifier SETT

Seq B Trade Details Field 98a Qualifier SETT

545


Seq E3 Amounts Field 19A Qualifier ESTT

Seq B Trade Details Field 98a Qualifier SETT (1)

547


Seq E3 Amounts Field 19A Qualifier ESTT

Seq B Trade Details Field 98a Qualifier SETT (1)

564


Seq E2 Cash Movement Field 19B Qualifier ENTL

Seq E2 Cash Movement Field 98a Qualifier PAYD(2)

564


Seq E2 Cash Movements Field 19B Qualifier ENTL (each occurrence)

Seq E2 Cash Movements Field 98a Qualifier VALU(3)

566


Seq D2 Cash Movement Field 19B Qualifier PSTA

Seq D2 Cash Movement Field 98a Qualifier POST

584


Seq B2b Trade Details Field 19A Qualifier SETT (each occurrence)

Seq B2b Trade Details Field 98a Qualifier SETT (1)

Seq B2b2 Amounts Field 19A Qualifier SETT

Seq B2b Trade Details Field 98a Qualifier SETT (1)

Seq C1c Trade Details Field 19A Qualifier SETT

Seq C1c Trade Details Field 98a Qualifier SETT (1)

Seq C1c2 Amounts Field 19A Qualifier

Seq C1c Trade Details Field 98a Qualifier SETT (1)

730

Acknowledgement

32D

32D

734

Advice of Refusal

33A

33A

742

Reimbursement Claim

34A

34A

752


33A

33A

754

Advice of Payment/ Acceptance/ Negotiation

34A

34A

General Information


MT

MT Name

NCD Amount Field

Value Date Field

756


33A

33A

768

Acknowledgement of a Guarantee Message

32D

32D

769


32D

32D

800

T/C Sales and Settlement Advice [Single]

32A in Seq B

32A in Seq B

802

T/C Settlement Advice

32A

32A

900


32A

32A

910


32A

32A

(1) If the settlement date in the optional field is not specified, the message will be accepted. (2) If the Value Date component is not present, then the validation is not performed (for example: MT 564 seq. E2, if : 98B:: is used, the validation is not performed) (3) If the Value Date component is not present, then the validation is not performed (for example: MT 564 seq. E2, if : 98B:: is used, the validation is not performed)

.4

ERI Validation and Examples Introduction This section details the validation of the ERI information and provides examples that give correct and incorrect messages.

8.4.1

General ERI Validation Rules

Rules Codes and format: • /OCMT/3!a15d/ • /CHGS/3!a15d/ Where: • The currency component 3!a must be a valid currency code (Error Code T52). • The amount component 15d following the currency code must be formatted according to the Field Formatting Rules given in section "Numbers" on page 51. If not properly formatted, the system will NAK the message with Error Code T40, T43, T33 or other generic error codes as deemed necessary. • The amount component 15d will not be checked on the maximum number of decimal digits allowed for the relevant currency code.

23 July 2010

79


Examples - currency codes The currency code XYZ is invalid. The messages are NAKed: • :79:/OCMT/XYZ150,/(CrLf) /CHGS/EUR1,(CrLf)

• :77A:xxx/OCMT/EUR5000,/CHGS/XYZ1,/CrLf)

Examples - amount components The amount components are invalid. The messages are NAKed: • :86:/OCMT/EUR,12/(CrLf) • :86:/OCMT/EUR123/(CrLf)

Note

The amount component must be followed by a slash character, '/' (Error Code T31). In the following example the amount component is invalid. The message is NAKed: :86:/OCMT/EUR1,23(CrLf)

8.4.2

Messages and Fields Impacted

Rules The ERI validation will be performed in fields: • 72 Structured Format, 72 ISITC Structured Format, 72 Narrative, 77A and/or 79, of all messages except the MTs 104, n92, n95, n96 and n99 • 61 (subfield 9) and 86, of the MTs 940 and 942

Examples The messages are not NAKed: • OCMT is validated :79:xxxxx/OCMT/EUR10,25/xxxxx(CrLf)

• OCMT and CHGS are validated :79:xxxxx/OCMT/EUR10,25/(CrLf) /CHGS/EUR1,/(CrLf)

8.4.3

No ERI Validation Hierarchy between the Fields

Rules Note that if the same field specification is reused in the message, the ERI validation will be performed. This is usually the case where a field is defined in a loop, that is, a repetitive block of fields or sequence.

Example For example, if fields 72, 77A and 79 are all present in a message, and the ERI validation is defined for that message, the system will apply the ERI validation in the three types of fields.

80

General Information


8.4.4

/CHGS/ is only Validated if /OCMT/ is Present

Rule The ERI validation for the code /CHGS/ (6 characters) will be performed only if it immediately follows /OCMT/3!a15d/ in the same occurrence of that field. Therefore, if /OCMT/ is present in field 72, and /CHGS/ is present in field 79 (but /OCMT/ is not present in 79), the system does not validate the format following /CHGS/ in field 79.

Example In the following example, CHGS is not validated because OCMT is missing. The message is not NAKed: :86:xxxxx/CHGS/EUR1,40/xxxxx(CrLf)

8.4.5

Sequence of Codes is Required

Rule Within a field, the sequence of the codes /OCMT/ and /CHGS/ is relevant. It is only if /OCMT/ appears immediately before /CHGS/ that the ERI validation will be applied to /CHGS/.

Example 1 - structured field 72 CHGS is validated. The message is not NAKed: :72:/INS/BANKCCCY/OCMT/EUR12345,/(CrLf) /CHGS/EUR20,/xxxxx(CrLf)

Example 2 - free format field 79 OCMT is validated. The message is not NAKed: :79:xyz/OCMT/EUR1234,00//CHGS/EUR40,00/xxx(CrLf)

Example 3 - free format field 72 Only OCMT is validated because CHGS does not follow immediately OCMT. The message is not NAKed: :72:xxxxxxxxxx(CrLf) //xxxxxxxxxx(CrLf) /OCMT/EUR1000,/xxxxx(CrLf) //xxxxxxxxxx(CrLf) /CHGS/EUR5,/(CR) //xxxxxxxxxx(CrLf)

Note: if /CHGS/ appears before /OCMT/, /CHGS/ will not be recognised as part of the ERI and will not be subject to the ERI validation.

Example 4 - structured field 72 Only OCMT is validated. The message is not NAKed: :72:/CHGS/EUR12,/xxxxx(CrLf) //xxxxxxxxxx(CrLf) //xxxxxxxxxx(CrLf) /OCMT/EUR12345,/xxxxx(CrLf) //xxxxxxxxxx(CrLf)

23 July 2010

81


Example 5 - free format field 79 Only OCMT is validated. The message is not NAKed: :79:xyz/CHGS/EUR4,00/xxx/OCMT/EUR1234,00/xxx(CrLf)

Example 6 - structured field 72 OCMT and the second occurrence of CHGS are validated. The message is not NAKed: :72:/CHGS/EUR1,/xxxxx(CrLf) //xxxxxxxxxx(CrLf) //xxxxxxxxxx(CrLf) /OCMT/EUR12345,/(CrLf) /CHGS/EUR12,/xxxxx(CrLf)

8.4.6

Double Codes are not Allowed in one Field

Rule In one occurrence of a field where the ERI validation must be performed, the codes /OCMT/ and /CHGS/ must not be used more than once.

Note

Note: Since the presence of /OCMT/ triggers the validation of /CHGS/, a double / CHGS/ will be NAKed only if /OCMT/ is present in the same field.

If the ERI validation fails due to a duplicated code, it will result - whichever field was validated in the existing Error Code T47. The line number of the first field in sequence in the message where the error occurred, will be indicated, together with the error code.

Example 1 - structured field 72 OCMT is found twice. The message is NAKed: :72:/OCMT/EUR12345,/(CrLf) //xxxxxx(CrLf) /OCMT/EUR100,/xxxxx(CrLf)

Example 2 - field 61 OCMT is found twice. The message is NAKed: :61:9809010931C3500,25FCHK304955//4958843(CrLf) /OCMT/EUR1101,//OCMT/EUR1020,25/(CrLf)

Example 3 - free format field 79 OCMT is found twice. The message is NAKed: :79:xyz/OCMT/EUR1234,00//OCMT/EUR40,00/xxx(CrLf)

Example 4 - free format field 72 CHGS is found twice. The message is NAKed: :72:xxxxxxxxxx(CrLf) //xxxxxxxxxx(CrLf) /OCMT/EUR10000,/(CrLf) /CHGS/EUR100,/xxxxxxxxxx(CrLf) /CHGS/EUR50,/(CR) //xxxxxxxxxx(CrLf)

Note

82

Note that if /CHGS/ appears before /OCMT/, /CHGS/ will not be recognised as part of the ERI and thus not be subject to the ERI validation. General Information


Example 5 - structured field 72 OCMT and the second occurrence of CHGS, are validated. The message is not NAKed: :72:/CHGS/EUR12,/xxxxx(CrLf) //xxxxxxxxxx(CrLf) //xxxxxxxxxx(CrLf) /OCMT/EUR12345,/(CrLf) /CHGS/EUR50,/(CR) //xxxxxxxxxx(CrLf)

Example 6 - free format field 79 OCMT and the second occurrence of CHGS, are validated. The message is not NAKed: :79:xyz/CHGS/EUR4,00//OCMT/EUR1234,00//CHGS/EUR4,00/(CrLf)

8.4.7

Consistent with Current Standards

Rule In all fields where the ERI validation is defined, the generic that is, current, validation must still be performed.

Example Field 72 is always checked for maximum 6 lines, with a maximum of 35 characters per line. Field 72, structured format, the first line must begin with a '/', and the second through sixth line (optional), must begin with a '/' or a '//'.

8.4.8

Maximum Use of the Generic Format Definition

Rule In order to maximise the use of all characters allowed in the generic format, the codes /OCMT/, / CHGS/, as well as the data (3!a15d/), may be split across lines.

Examples Narrative format of information that follows ERI-related codes split across lines: :72:xxxxx/OCMT/EUR12345,(CrLf) 12//CHGS/ (CrLf) EUR12,/(CrLf)

Structured format of ERI-related codes split across lines: :72:/INS/BANKCCCY/OCMT/EUR1234,//CH(CrLf) //GS/EUR1,/xxxxxxx(CrLf)

Narrative format of ERI-related codes split across lines: :77A:xxxxx/OC(CrLf) MT/EUR100,/(CrLf)

23 July 2010

83


8.4.9

No ERI Validation

Rules SWIFT does not perform network validation on the Euro-Related Information in: • Fields 72 and 79, if the REJT or RETN codes are present, that is, the special REJT/RETN validation for fields 72 and 79 prevails • MT 104 • Common Group message types (category n) • MTs 96n (only used for bilateral key exchange)

8.4.10 Details of the ERI Validation Implementation 8.4.10.1 Field 61, subfield 9 Format [34x]

Validation The system performs the following validation: 1.

If subfield 9 in field 61 is present, then validate according to the format 34x: • If the check here above is OK, then go to point 2. • Otherwise the message is NAKed with the corresponding error code.

2.

Scan for /OCMT/ If /OCMT/ is: • not present, then perform next field validation • present more than once, then NAK the message with the error code T47 and terminate the validation • present only once, then validate the format <3!a15d/> If format is: – valid, then go to point 3 – invalid, then NAK the message with the corresponding error code and terminate the validation

3.

Check for /CHGS/ immediately after /OCMT/3!a15d/. If /CHGS/ is: • not present, then perform next field validation • present more than once, then NAK the message with the error code T47 and terminate the validation • present only once, then validate the format <3!a15d/>

84

General Information


If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminate the validation

8.4.10.2 Field 72 (Structured Format) Format first line [(CrLf)(INSTR> or '//' 33x)] optionally, 2nd through 6th line

where is defined as: • /<1!a>/[32x] or • /<2!a>/[31x] or • /<3!a>/[30x] or • /<4!a>/[29x] or • /<5!a>/[28x] or • /<6!a>/[27x] or • /<7!a>/[26x] or • /<8!a>/[25x]


maximum 6 lines, maximum 35 characters per line ( character set)

2.

first line as , per the format defined here above

3.

second through sixth line If present, defined as : or <'//' 33x>: • if the 3 checks here above are OK, then go to point 4 • otherwise the message is NAKed, with the corresponding error code

4.

throughout the field content, removes all (CrLf'//'), if any

5.

throughout the field content, removes all (CrLf), if any

6.

scans for /OCMT/ If /OCMT/ is: • not present, then perform next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • present only once, then validates the format <3!a15d/>

23 July 2010

85


If format is: – valid, then go to point 7 – invalid, then NAK the message with the corresponding error code and terminates the validation 7.

checks for /CHGS/ immediately after /OCMT/3!a15d/ If /CHGS/ is: • not present, then performs next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • present only once, then validates the format <3!a15d/> If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminates the validation

8.4.10.3 Field 72 (Narrative) Format 35x[(CrLf)35x] 0-5.



2.

second through sixth line, if present, defined as 35x If present, defined as 35x: • if the 2 checks are OK, then go to point 3 • otherwise the message is NAKed with the corresponding error code

3.


4.

scans for /OCMT/ If /OCMT/ is: • not present, then performs next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • is present only once, then validates the format <3!a15d/>

86

General Information



checks for /CHGS/ immediately after /OCMT/3!a15d/. If /CHGS/ is: • not present, then performs next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • present only once, then validates the format <3!a15d/> If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminates the validation

8.4.10.4 Field 77A (Narrative) Format 35x[(CrLf)35x] 0-19



2.

second through 20th line If present, defined as 35x: • if the 2 checks here above are OK, then go to point 3 • otherwise the message is NAKed with the corresponding error code

3.


4.

scans for /OCMT/ If /OCMT/ is: • not present, then perform next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • present only once, then validate the format <3!a15d/>

23 July 2010

87


If format <3!a15d/> is: – valid, then go to point 5 – invalid, then NAK the message with the corresponding error code and terminates the validation 5.

checks for /CHGS/ immediately after /OCMT/3!a15d/ If /CHGS/ is: • not present, then perform next field validation • present more than once, then NAK the message with the error code T47 and terminate the validation • present only once, then validate the format <3!a15d/> If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminate the validation

8.4.10.5 Field 79 (Narrative) Format 50x [(CrLf)50x] 0-34



2.

second through 35th line If present, defined as 50x: • if the 2 checks (point 1) are OK, then go to point 3 • otherwise the message is NAKed with the corresponding error code

3.


4.


88

General Information



checks for /CHGS/ immediately after /OCMT/3!a15d/ If /CHGS/ is: • not present, then perform next field validation • present more than once (double), then NAK the message with the error code T47 and terminates the validation • present only once, then validates the format <3!a15d/> If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminates the validation

8.4.10.6 Field 86 (Narrative) Format 65x [(CrLf)65x] 0-5



2.

second through sixth line If present, defined as 65x: • if the 2 checks (point 1) are OK, then go to point 3 • otherwise the message is NAKed, with the corresponding error code

3.


4.


23 July 2010

89



checks for /CHGS/ immediately after /OCMT/3!a15d/ If /CHGS/ is: • not present, then perform next field validation • present more than once (double), then NAK the message with the error code T47 and terminate the validation • present only once, then validates the format <3!a15d/> If format is: – valid, then go to next field validation – invalid, then NAK the message with the corresponding error code and terminates the validation

90

General Information

General Mt SWIFT

Recommend Documents