SCA_TIG_MT940_12

SWIFT Corporate Access

Technical Implementation Guideline

SWIFT MT940

Version: 1.2

SWIFT MT940 2

Contents

1 INTRODUCTION 3

1.1 Table abbreviations............................................................... 3 1.2 Basic assumptions ................................................................ 3 1.3 What has changed since the previous version ..................... 3 1.4 Character set......................................................................... 4

2 USED STRUCTURE OF THE SWIFT MT940 5

3 FORMAT IN DETAIL 6

3.1 Header Block 1...................................................................... 7 3.2 Header Block 2...................................................................... 8 3.3 Header Block 3...................................................................... 9 3.4 Header Block 4.................................................................... 10 3.5 TAG 20................................................................................ 11 3.6 TAG 21................................................................................ 12 3.7 TAG 25................................................................................ 13 3.8 TAG 28(C)........................................................................... 14 3.9 TAG 60a.............................................................................. 15 3.10 TAG 61................................................................................ 16 3.11 TAG 86................................................................................ 18 3.12 TAG 62a.............................................................................. 19 3.13 TAG 64................................................................................ 20 3.14 TAG 65................................................................................ 21 3.15 TAG 86................................................................................ 22 3.16 Trailer Block 5 ..................................................................... 23

SWIFT MT940 3

1 Introduction

The Member Administered – Closed User Group (MA-CUG) provides a complimentary delivery channel for payment instructions via Access Direct FIN and/or Access Direct FileAct. Once enrolled, you can exchange payment instructions with any RBS branch or 3rd party bank where you hold your banking account. You can also exchange payment instructions with banks where authority is retained to request a transfer from the banking account in another location.

This document describes the structure of the SWIFT MT940 message for the SWIFT Corporate Access channel. This document is especially useful during the implementation process.

1.1 Table abbreviations

The following abbreviations are used in tables throughout this document:

Abbreviation Description Usage example

An Alphanumeric An4 indicates that the length is exactly 4 alphanumeric characters. An..4 indicates that the length can be up to 4 alphanumeric characters. Characters are either alphabetical a-z or numeric 1-9.

A Alphabetical A4 indicates that the length is exactly 4 alphabetical characters. A..4 indicates that the length can be up to 4 alphabetic al characters. Characters are a..z.

N Numeric N18 indicates that the length is exactly 18 numeric characters. N..18 indicates that the length can be up to 18 numeric characters.

M Mandatory Field /Segment will always be used.

C Conditional Field/Segment is used but certain rules and restrictions apply to the use.

O Optional Field/Segment can be used.

N/A Not applicable Field/Segment will not be used.

1.2 Basic assumptions

The Technical Implementation Guideline is based on the SWIFT manual version November 2006. The MT940 message is sent by an account servicing institution (reporting institution) to a financial institution which has been authorized by the account owner to receive it. This institution can then forward all statements to the customer.

The MT940 contains an end-of day statement of an account. This statement can just contain balances if no transactions took place or can be more extended containing transactions.

The SWIFT header and footer are present.

1.3 What has changed since the previous version

• Section 1.4: Updated character set;

• Section 3.9, 3.12, 3.13: Included footnote on date in tag 60F, 62F and 64 for the USA and Canada.

• Added new example in Appendix 2

SWIFT MT940 4

Please look at the green blocks to the left of the text. These blocks will contain more info about the changes and will be put in front of the text that has been changed in the document.

1.4 Character set

SWIFT Corporate Access supports the following characters:

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

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

0 1 2 3 4 5 6 7 8 9

/ - ( ) . , { }

CR LF Space

Note: Including other characters may lead to repair or rejection of the transaction.

SWIFT MT940 5

2 Used Structure of The SWIFT MT940

This chapter contains the description of the SWIFT MT940 format and shows which segments are used and which we do not support.

The first column of this table contains how a tag or tag-group is used within RBS bank. As can be seen this can be M (Mandatory), O (Optional), C (Conditional) or N/A (Not applicable). The second column shows the TAG concerned and the third column contains a short description of the TAG. The last column shows the maximum occurrences of a TAG within one statement.

Use TAG Description of TAG Maximum use per TAG or TAG Group

C - Header Block 1 1



M - Header Block 4 1

General Group

M 20 Transaction Reference number 1

O 21 Related Reference 1

M 25 Account Identification 1

M 28(C) Statement Number / Sequence Number 1

M 60a Opening Balance 1

Transaction Group

O 61 Statement Line Unlimited

O 86 Information to Account Owner (statement line level) Unlimited*

Balance Group

M 62a Closing Balance 1

O 64 Closing Available Balance 1

Balance Group

O 65 Forward Available Balance 5

Free text

O 86 Information to Account Owner (Account level) 1

C - Trailer Block 5 1

* TAG 86 of the Transaction Group can only be present if TAG61 is present since TAG61 and 86 belong together. TAG86 is free text related to the transaction details mentioned in TAG61.

SWIFT MT940 6

3 Format in Detail

The segments mentioned in Chapter 2 are covered in detail in this chapter.

The build up for each segment is as follows:

Use: Mandatory/Conditional/Optional/Not applicable

Purpose: The purpose of the TAG

Example: An example of what the field may look like

Where needed, a table will be added to describe the exact build up of the segment. The table contains the following columns:

Use: To indicate whether the specific segment is Mandatory, Conditional, Optional or Not applicable.

Segment To indicate the underlying segment

Description: Description of the use of the segment

Purpose: Explanation of what the segment is needed / used for

Restriction: To indicate whether the segment needs to contain a certain value or if there are restrictions regarding the length of the field etc. If a value is mentioned in between ' ' it means that this is the only value allowed. If the restriction is not a specific value, a restriction can either be: numeric, alphanumeric or alphabetic.

SWIFT MT940 7

3.1 Header Block 1

Use: C

Purpose: To indicate the sender of the message

Example:

{1:F01RBOSNL2AXXXX0000000000}

The components can be separated as follows:

{1: F 01 RBOSNL2AXXXX 0000 000000}

(1) (2) (3) (4) (5) (6)

Use Segment Description Purpose Restriction

M 1 Block Identifier This is needed to indicate which block it is.

‘1:’

M 2 Application Identifier This is used to indicate it is a Financial message.

‘F’

M 3 Service Identifier Indicates the type of data that is being sent. 01 is used for all Financial messages.

‘01’

M 4 Sender ID This segment is used to indicate the Sender. The field is for 12 characters, so it is outlined to 12 with X’s on the right.

‘RBOSNL2AXXXX’

M 5 Session number Identifies the session in which this message is transmitted.

'0000'

M 6 Sequence number This segment is used to indicate the file reference number.

'000000'

SWIFT MT940 8

3.2 Header Block 2

Use: C

Purpose: To indicate the receiver of the message and to indicate which message it is.

Example:

{2:O9400000000000TESTCLIENT 00000000000000000000N}

The components can be separated as follows:

{2: O 940 0000 000000 TESTCLIENT 0000 000000 000000 0000 N}

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)


M 1 Block Identifier This is needed to indicate which block it is.

‘2:’

M 2 Input/ Output Identifier To indicate whether this is an Input message or an Output message.

‘O’

M 3 Message Type The number that defines the message (e.g. which payment file etc.).

‘940’

M 4 Input time The local time of the sender. '0000'

M 5 Input date The local date of the sender. ‘000000’

M 6 Receiver ID This segment is used to indicate the receiver. The field is followed by one space.

An..12

M 7 Session number Identifies the session in which this message is transmitted.

'0000'

M 8 Sequence number This segment is used to indicate the file reference number.

'000000'

M 9 Output date The local date of the receiver. '000000'

M 10 Output time Output time of the receiver. '0000'

M 11 Message Priority Defines the priority of the message. 'N'

SWIFT MT940 9

3.3 Header Block 3

Use: C

Purpose: To indicate user to user messages

Example:

{3:}

No information of this header will be used. This header will be empty.

SWIFT MT940 10

3.4 Header Block 4

Use: M

Purpose: To hold the text of the SWIFT message

Example:

{4:<CRLF>

:20:8800946/00000010<CRLF>

:25:6099848002<CRLF>

:28C:117/1<CRLF>

:60F:C020821EUR3319155,58<CRLF>

:61:0208220822D340395,06NTRFNONREF//EZ/AZE2082203290<CLRF>

GTC000206<CLRF>

:86:EZ/AZE2082203290 //REF 12046371 INV.NO. 20020014 200 20032 3702 4<CLRF>

138 4140 SUHLING TECHNIK GMBH ZUR AUMUNDSWEISE 10 BREMEN DE 28279<CLRF>

AMOUNT EUR 340.395,06<CLRF>

:62F:C020822EUR4836397,76<CRLF>

:64:C020822EUR4836397,76<CRLF>

-}

The <CRLF> is a mandatory field delimiter.

SWIFT MT940 11

3.5 TAG 20

Use: M

Purpose: This tag specifies the reference assigned by the Sender to unambiguously identify the message. Filled with Sequence number.

Example:

:20:[1]

Example:

:20:8800946/00000010


M 1 The original reference number of the MT940.

To ensure uniqueness of the file. An..16

SWIFT MT940 12

3.6 TAG 21

Use: O

Purpose: To identify the account holding bank.

Example:

:21:[1]

Example:

:21:RBOSNL2AXXX

If an RBS branch is the account servicing institution, the BIC11 or BIC8 followed by "XXX" will be included within this field. No codeword will accompany the BIC identification. For other branches tag 21 will remain the same.


O 1 Additional Reference number.

To identify the account holding branch An..16

SWIFT MT940 13

3.7 TAG 25

Use: M

Purpose: This tag identifies the account (number) for which the statement is sent.

Example:

:25:[1]

Example:

:25:6099848002


M 1 Account number Identifies the account for which the statement is sent.

An..35

SWIFT MT940 14

3.8 TAG 28(C)

Use: M

Purpose: This tag contains the sequential number of the statement, optionally followed by the sequence number of the message within that statement when more than one message is sent for one statement.

Example:

:28(C):[1][/2]

Example:

:28:43577/11 or :28C:117/1


M 1 Statement number To indicate the statement number. N..5

O 2 Sequence number To indicate the message. /N..5

SWIFT MT940 15

3.9 TAG 60a

Use: M

Purpose: This tag specifies, for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance.

Example:

:60F:[1][2][3][4]

Example:

:60F:C020821EUR3319155,58

The amount will always contain two digits behind the comma. So for a zero balance the amount will be 0,00.

TAG60a can be an F or an M (:60F: or :60M:): The first customer statement message for a specified period must contain field 60F (first opening balance); additional statement messages for the same statement period must contain field 60M (intermediate opening balance).


M 1 Debit/Credit indicator To indicate whether the balance is positive (‘C’) or negative (‘D’).

For a zero balance the ‘C’ is used.

A1

M 2 Book date Indicates the date of the last statement for most RBS branches. For RBS branches in the US and Canada, the opening balance "book date" is equal to the date of the statement (not the date of the last statement).

'YYMMDD'

M 3 ISO Currency code To show the currency of the account. A3

M 4 Amount The actual amount of the opening balance of the account.

N..15

SWIFT MT940 16

3.10 TAG 61

Use: O

Purpose: This field contains the details of each transaction.

Example:

:61:[1][2][3][4][5][6][7][8]

[9]

Examples:

:61:0208220822D340395,06NTRFNONREF//EZ/AZE2082203290<CRLF>

GTC000206<CLRF>

In some cases a funds code will be present. This is only the case if it has been provided by the sending institution. (e.g. EUR then the R is present as is shown in the example).

:61:0202150215CR325,44FTRFNONREF


M 1 Value Date The value date of the underlying transaction.

'YYMMDD'

O 2 Entry Date Entry Date. 'MMDD'

M 3 Debit/Credit indicator To indicate whether the transaction was a debit a credit or a reversal in the account.

'C'

'D'

'RC'

'RD'

O 4 Funds code 3rd Character of the currency code. A1

M 5 Amount Amount of transaction. N..15

M 6 Transaction Type Identification Code

This field contains the Transaction Type Identification code. The first character will always be ‘N’, ‘S’ or ‘F’. For more information on the codes please refer to Appendix 1.

An4

M 7 Reference for Account owner1

If the transaction of the statement has been matched, this field will contain the original transaction reference number (or batch Reference number). The number will be present after the three or four characters of subfield 6.

If the transaction has not been matched the original data of the MT940 will be present.

An..16

O 8 Account Servicing institution reference

Original information of the MT940. Account Servicing institution’s own reference number.

An..16

O 9 Supplementary Details Additional information that was present in input. Information provided by

An..34

1 When Customer Reference Number is activated this will be shown in subfield 7.

SWIFT MT940 17


account servicing institution that can be used for reference.

SWIFT MT940 18

3.11 TAG 86

Use: O

Purpose: This field contains additional information on the transaction detailed in the preceding statement line and which is to be passed on to the account owner.

Example:

:86:[1]

[2]

[3]

[4]

[5]

[6]

Example:

:86:EZ/AZE2082203290 //REF 12046371 INV.NO. 20020014 200 20032 3702 4

138 4140 SUHLING TECHNIK GMBH ZUR AUMUNDSWEISE 10 BREMEN DE 28279

AMOUNT EUR 340.395,06

The <CRLF> characters from the original MT940 message are removed which can for certain countries result in one long text string. To prevent this the <CRLF> characters can be replaced by spaces.


O 1 Free text To inform client on the statement line that was preceding this TAG 86.

An..65


An..65


An..65


An..65


An..65


An..65

SWIFT MT940 19

3.12 TAG 62a

Use: M

Purpose: This field specifies, for the (intermediate) closing balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance.

Example:

:62a:[1][2][3][4]

Example: :62F:C020822EUR4836397,76


TAG62a can be an F or an M (:62F: or :62M:): The first customer statement message for a specified period must contain field 62F (first opening balance); additional statement messages for the same statement period must contain field 62M (intermediate opening balance).




A1

M 2 Book date To indicate the statement date 'YYMMDD'


M 4 Amount The actual amount of the closing balance of the account.

N..15

SWIFT MT940 20

3.13 TAG 64

Use: O

Purpose: This field indicates the funds which are available to the account owner (if credit balance) or the balance which is subject to interest charges (if debit balance).

Example:

:64:[1][2][3][4]

Example:

:64:C020822EUR4836397,76





A1

M 2 Book date To indicate the statement date 'YYMMDD'


M 4 Amount The Closing Available Balance. N..15

SWIFT MT940 21

3.14 TAG 65

Use: O

Purpose: This field indicates the funds which are available to the account owner (if credit balance) or the balance which is subject to interest charges (if debit balance) for the specified value date.

Example:

:65:[1][2][3][4]

Example:

:65:C020823EUR4830001,25


When there is more than one value date for the items booked to the account (in this or previous statement periods), this field will indicate the balance which will be available to the Account Owner on the date(s) indicated. This field can be present multiple times. The information is provided by the account servicing institution.




A1

M 2 Book date To indicate the date concerned. 'YYMMDD'


M 4 Amount The forward Available Balance. N..15

SWIFT MT940 22

3.15 TAG 86

Use: O

Purpose: Information to Account Owner (statement level)

Example:

:86:[1]

[2]

[3]

[4]

[5]

[6]

Example: :86:/ACSI/RBOSNL2AXXX

Both RBS branches and other banks (account servicing institution) will be identified by their BIC11 or BIC8 followed by "xxx" on the first free line in tag 86. BIC’s in field 86 will be preceded by the code word "/ACSI/". Should all 6 lines of field 86 be filled, the identification will not be added, allowing the original text to remain intact.

This TAG can be present only once per statement. The previous TAG 86 can be present for every TAG61, this TAG 86 at the end of the statement is only present once. It can contain generic account level information.


O 1 Free text Account level information. An..65






SWIFT MT940 23

3.16 Trailer Block 5

Use: C

Purpose: User to user message

Example:

{5:}

No information of this footer will be used. The footer will be left empty.

SWIFT MT940 24

Appendix 1

Transaction codes in TAG61 subfield 6.

:61:0210311031C325,44NTRFNONREF

If a customer is not set up to receive Reporting Codes the original value of the received MT940 will be present in the statement sent to the customer.

The length of this field is 4 characters.

The first character will always be an ‘N’, ‘S’, or ‘F’.

N no relation with another SWIFT message

S a relation with another SWIFT message MTnnn

F first advised (there hasn’t been a pre-mentioning)

When the first character is an N or F the last three characters can be one of the following:

BOE Bill of exchange

BRF Brokerage fee

CHG Charges and other expenses

CHK Cheques

CLR Cash letters/ Cheques remittance

CMI Cash management item - No detail

CMN Cash management item - Notional pooling

CMS Cash management item - Sweeping

CMT Cash management item -Topping

CMZ Cash management item - Zero balancing

COL Collections (used when entering a principal amount)

COM Commission

DCR Documentary credit (used when entering a principal amount)

DDT Direct Debit Item

DIV Dividends- Warrants

EQA Equivalent amount

ECK Eurocheques

FEX Foreign exchange

SWIFT MT940 25

INT Interest

LBX Lock Box

LDP Loan Deposit

MSC Miscellaneous

RTI Returned item

SEC Securities (used when entering a principal amount)

STO Standing order

TCK Travellers cheques

TRF Transfer

VDA Value date adjustment (used with an entry made to withdraw an incorrectly dated entry – it will be followed by the correct entry with the relevant code)

SWIFT MT940 26

Appendix 2

{1:F01RBOSNL2AXXXX0000000000}{2:O9400000070801ABNAESMMMAD00000000000708010000N}{3:{108:RR00000000000000}}{4:

:20:20070801

:21:ABNAESMMMAD

:25:100000111

:28C:001/00001

:60F:C070731EUR0,

:61:0708010801C1900000,NTRFNONREF//1011708011 00001

COMPANY NAME ESPANA S./GTC101170

:86:COMPANY NAME ESPANA S.A. STREET 2 10000 PLACE ES S A1

8974976 IMP. TRANSF. EUR 1.900.000,00 IMP.ORIGEN EUR 1.900.000,00

:61:0708010801C2400000,NTRFNONREF//1910708011 00002

COMPANY NAME ESPANA S /GTC101170

:86: COMPANY NAME ESPANA S.A. STREET 2

10000 PLACE IMP. TRANSF. EUR 2.400

.000,00 IMP.ORIGEN EUR 2.400.000,00

:61:0708010801D4300000,NTRFZero balancing s//190-ZB-00101010

000100000011 / 000100012/GTC100206

:86:ZERO BALANCING SWEEP BETWEEN 000100000011 EUR

AND 000100000012 EUR

:62F:C070801EUR0,

:64:C070801EUR0,

:86:/ACSI/ABNAESMMMAD

Date post:	27-Nov-2014
Category:	Documents
Upload:	nitesh-patil
View:	166 times
Download:	5 times

SCA_TIG_MT940_12

Documents