swiftstandards - category 9 - cash management & customer ... · pdf fileswiftstandards...

SWIFTStandards

Category 9Cash Management & Customer Status

November 2003 Standards Release

Standards Release Guide 2003 - Final edition - February 2003

1

Legal Notices

IMPORTANT NOTE: You may install and use this publication only if you have entered into the relevant licence agreementwith SWIFT. Please refer to such licence agreement to determine what you may or may not do with it. Note however that inthe case of a ’Single User Licence’, this publication must be installed on a standalone machine for access by one person atany one time, and references to "organisation" in these notices are to the ordering customer (BIC 8). In the case of a ’ServerLicence’, this publication can also be installed on a server for access within the organisation of the ordering customer (BIC8), and references to "organisation" are then to all those SWIFT Users belonging to the same group as the ordering customer(BIC8) for traffic aggregation purposes.

Copyright

Copyright © S.W.I.F.T. SCRL ("SWIFT"), avenue Adèle 1, B-1310 La Hulpe, Belgium, 2002. All rights reserved. No partof this publication may be copied or reproduced, stored in a retrieval system, sold or transferred to any person, in whole orin part, in any manner or form or on any media, without the prior written permission of SWIFT. The recipient is, however, authorised to copy or reproduce this publication within its own organisation as may be reasonably necessary for the purposefor which it is supplied. Any such copy or reproduction will include the following: acknowledgement of the source, refer-ence and date of publication, and all notices set out on this page.

Confidentiality

This publication may contain proprietary and/or confidential information of SWIFT and/or its suppliers. The recipientshould not disclose this publication outside its organisation without the prior written permission of SWIFT.

Disclaimer

Although SWIFT has used reasonable efforts to ensure accuracy of its contents, SWIFT assumes no liability for any inad-vertent error or omission that may appear in this publication. The information in this publication is the latest available at thedate of its production, and may change from time to time.

Trademarks and Patents

SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, Accord and SWIFT-derived product and service names - such as but notlimited to SWIFTNet and SWIFTAlliance - are trademarks of S.W.I.F.T. SCRL. SWIFT is the trading name of S.W.I.F.T.SCRL. All other product or company names that may be mentioned in this publication are trademarks or registered trade-marks of their respective owners. Patent pending: SWIFTNet - TrustAct - e-paymentsPlus.

February 2003 edition


SWIFTStandards - Category 9Legal Notices

Overview

Added Message TypesRemoved Message TypesModified Message Types

Added Message TypesNone

Removed Message TypesNone

Modified Message TypesMT900

MT910

MT985

3Standards Release Guide 2003 - Final edition - February 2003

OverviewSWIFTStandards - Category 9

MT 900 Confirmation of Debit

MT 900 ScopeThis message type is sent by an account servicing institution to an account owner.

It is used to notify the account owner of an entry which has been debited to its account. The entry will be further confirmedby statement.

MT 900 Format Specifications

MT 900 Confirmation of Debit

Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

M 21 Related Reference 16x 2

M 25 Account Identification 35x 3

M 32A Value Date, Currency Code, Amount 6!n3!a15d 4

O 52a Ordering Institution A or D 5

O 72 Sender to Receiver Information 6*35x 6

M = Mandatory O = Optional

MT 900 Network Validated RulesThere are no network validated rules for this message type.

MT 900 Usage RulesThis message type is not normally sent if statements for the account are frequently transmitted.This message type does not normally result in any bookings. It is a confirmation to the Receiver (account owner) of adebit to its account.

MT 900 Field Specifications

1. Field 20: Transaction Reference Number

FORMAT

16x


SWIFTStandards - Category 9MT 900

PRESENCE

Mandatory

DEFINITION

This field specifies the reference assigned by the Sender to unambiguously identify the message.

NETWORK VALIDATED RULES

This field must not start or end with a slash ’/’ and must not contain two consecutive slashes ’//’ (Error code(s): T26).

2. Field 21: Related Reference

FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field contains the reference number of the transaction which resulted in this message, eg, the field 20 Transaction Reference Number of the SWIFT payment instruction.



3. Field 25: Account Identification

FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the account which has been debited.

4. Field 32A: Value Date, Currency Code, Amount

FORMAT

Option A 6!n3!a15d (Date) (Currency) (Amount)


MT 900SWIFTStandards - Category 9

PRESENCE

Mandatory

DEFINITION

This field specifies the value date, currency code and amount of the debit.


Date must be a valid date expressed as YYMMDD (Error code(s): T50).

Currency must be a valid ISO 4217 currency code (Error code(s): T52).

The integer part of Amount must contain at least one digit. The decimal comma ’,’ is mandatory and is included in themaximum length. The number of digits following the comma must not exceed the maximum number allowed for thatspecific currency as specified in ISO 4217 (Error code(s): C03, T40, T43).

5. Field 52a: Ordering Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]

(Party Identifier)(BIC)

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

(Party Identifier)(Name & Address)

PRESENCE

Optional

DEFINITION

This field identifies the institution which instructed the Sender to execute the transaction resulting in this debit, when otherthan the Receiver.

CODES

Party Identifier may be used to indicate a national clearing system code.

The following codes may be used preceded by a double slash (’//’):

with option A:

AT 5!n Austrian Bankleitzahl

AU 6!n Australian Bank State Branch (BSB) Code

BL 8!n German Bankleitzahl

CC 9!n Canadian Payments Association Payment Routing Number

ES 8..9n Spanish Domestic Interbanking Code

FW without 9 digit code Pay by Fedwire



GR 7!n HEBIC (Hellenic Bank Identification Code)

HK 3!n Bank Code of Hong Kong

IE 6!n Irish National Clearing Code (NSC)

IN 11!c Indian Financial System Code (IFSC)

IT 10!n Italian Domestic Identification Code

PT 8!n Portuguese National Clearing Code

SC 6!n UK Domestic Sort Code

CODES

with option D:





CH 6!n CHIPS Universal Identifier

CP 4!n CHIPS Participant Identifier


FW 9!n Fedwire Routing Number







RU 9!n Russian Central Bank Identification Code


SW 3..5n Swiss Clearing Code (BC code)



SW 6!n Swiss Clearing Code (SIC code)


The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45).

The BIC must not be a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

USAGE RULES

The coded information contained in field 52a must be meaningful to the Receiver of the message.

Option A is the preferred option.

Option D should only be used when the ordering financial institution has no BIC.

6. Field 72: Sender to Receiver Information

FORMAT

6*35x (Narrative)

In addition to narrative text, structured text with the following line formats may be used:

Line 1 /8c/[additional information] Lines 2-6 [//continuation of additional information]

or[/8c/[additional information]]

PRESENCE

Optional

DEFINITION

This field contains additional information for the Receiver.

USAGE RULES

This field may contain information only (ie, no instructions may be included).

Additional explanatory information, which may be continued on the next lines, is preceded by a double slash ’//’.

Codes to be used may be agreed to bilaterally.

This field may contain ERI to transport dual currencies, as explained in the chapter ’Euro - Impact on Category 9 Message Standards’.

In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate,format 12d, and terminated with another slash.



MT 910 Confirmation of Credit

MT 910 ScopeThis message is sent by an account servicing institution to an account owner.

It is used to notify the account owner of an entry which has been credited to its account. The entry will be further confirmedby statement.


MT 910 Confirmation of Credit





M 32A Value Date, Currency Code, Amount 6!n3!a15d 4

O 50a Ordering Customer A or K 5

O 52a Ordering Institution A or D 6

O 56a Intermediary A or D 7



MT 910 Network Validated RulesC1

Either field 50a or field 52a must be present, but not both (Error code(s): C06):

If field 50a is... then field 52a is...

Present Not allowed

Not present Mandatory



MT 910 Usage RulesThis message type is not normally sent if statements for the account are frequently transmitted.This message type does not normally result in any bookings. It is a confirmation to the Receiver (account owner) of acredit to its account.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION





FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field contains the reference for the account owner (Receiver), eg, field 21, from the SWIFT message which resulted inthis credit.




FORMAT

35x



PRESENCE

Mandatory

DEFINITION

This field identifies the account which has been credited.

4. Field 32A: Value Date, Currency Code, Amount

FORMAT

Option A 6!n3!a15d (Date) (Currency) (Amount)

PRESENCE

Mandatory

DEFINITION

This field specifies the value date, currency code and amount of the credit.





5. Field 50a: Ordering Customer

FORMAT

Option A [/34x]4!a2!a2!c[3!c]

(Account)(BEI)

Option K [/34x]4*35x

(Account)(Name & Address)

PRESENCE

Conditional (C1)

DEFINITION

This field identifies the customer which originated the transaction resulting in this credit.


The BEI, ie, a BIC with subtype BEID, MCCO, TESP or TRCO, must be a SWIFT registered address, either connected ornon-connected (Error code(s): T27, T28, T29, T45, E57).



USAGE RULES

If the account number is present, it must be stated in Account.

6. Field 52a: Ordering Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


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


PRESENCE

Conditional (C1)

DEFINITION

This field identifies the financial institution which originated the transaction resulting in this credit.

CODES

Party Identifier may be used to indicate a national clearing system code.

The following codes may be used preceded by a double slash (’//’):

with option A:






FW without 9 digit code Pay by Fedwire










CODES

with option D:





CH 6!n CHIPS Universal Identifier

CP 4!n CHIPS Participant Identifier


FW 9!n Fedwire Routing Number







RU 9!n Russian Central Bank Identification Code


SW 3..5n Swiss Clearing Code (BC code)

SW 6!n Swiss Clearing Code (SIC code)




USAGE RULES

The coded information contained in field 52a must be meaningful to the Receiver of the message.

Option A is the preferred option.



Option D should only be used when the ordering financial institution has no BIC.

7. Field 56a: Intermediary

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


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


PRESENCE

Optional

DEFINITION

This field identifies the financial institution from which the Sender received the funds, when other than the ordering institu-tion.





FORMAT

6*35x (Narrative)


Line 1 /8c/[additional information] Lines 2-6 [//continuation of additional information]

or[/8c/[additional information]]

PRESENCE

Optional

DEFINITION


USAGE RULES

This field may contain information only, ie, no instructions may be included.






In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate,format 12d, and terminated with another slash.



MT 920 Request Message

Note: As this message may require the implementation of special procedures, its use is governed by bilat-eral agreements between correspondents.

MT 920 ScopeThis multiple message is sent by an account owner, or a financial institution (concentrating institution) acting on behalf ofan account owner, to an account servicing institution.

It is used to request the account servicing institution to transmit one or more MT 940 Customer Statement(s), MT 941Balance Report(s), MT 942 Interim Transaction Report(s), or MT 950 Statement Message(s) containing the latest informa-tion available for the account(s) identified in the message.


MT 920 Request Message



----->

M 12 Message Requested 3!n 2


O 34F Floor Limit Indicator 3!a[1!a]15d 4


-----|



If field 12 contains the value ’942’, at least one field 34F must be present in the same repetitive sequence (Errorcode(s): C22).

C2

Within each repetitive sequence, when only one field 34F is present, the second subfield must not be used. When bothfields 34F are present, subfield 2 of the first 34F must contain the value ’D’, and subfield 2 of the second 34F mustcontain the value ’C’ (Error code(s): C23).



C3

The currency code must be the same for each occurrence of the indicated fields within each repetitive sequence (Errorcode(s): C40).

MT 920 Usage RulesThis message should only be used if the account owner(s) have authorised the financial institutions to transmit such information and according to agreed criteria.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION




2. Field 12: Message Requested

FORMAT

3!n

PRESENCE

Mandatory

DEFINITION

This field identifies the message type which is being requested.

CODES

This field must contain one of the following message type numbers (Error code(s): T88):

940 Customer Statement

941 Balance Report



942 Interim Transaction Report

950 Statement Message


FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the account for which the information is requested.

4. Field 34F: Floor Limit Indicator

FORMAT

Option F 3!a[1!a]15d (Currency) (D/C Mark) (Amount)

PRESENCE

Conditional (C1)

DEFINITION

This field specifies the minimum value (transaction amount) to be reported on the requested message.

CODES

When D/C Mark is present, it must contain the following code (Error code(s): T51):

D Debit floor limit



The integer part of Amount must contain at least one digit. The decimal comma ’,’ is mandatory and is included in themaximum length. The number of digits following the comma must not exceed the maximum number allowed for the speci-fied currency (Error code(s): C03, T40, T43).

When this field appears two times, Currency must be the same for each occurrence (Error code(s): C40).



USAGE RULES

When the field appears once, the floor limit applies to both debit and credit amounts. When different limits apply, bothfields 34F must be present.

5. Field 34F: Floor Limit Indicator

FORMAT


PRESENCE

Conditional (C2)

DEFINITION

This field specifies the minimum value (transaction amount) to be reported on the requested message.

CODES

D/C Mark must contain the following code (Error code(s): T51):

C Credit floor limit




When this field appears two times, Currency must be the same for each occurrence (Error code(s): C40).

USAGE RULES

When different limits apply, this field 34F must be present, with a credit indicator (’C’).



MT 935 Rate Change Advice

MT 935 ScopeThis multiple message is used by the Sender to advise interest rate change(s) to the Receiver.

It is used to advise the details of:

General interest rate change(s).Interest rate change(s) which apply to specific account(s), other than call/notice loan/deposit account(s), serviced bythe Sender of the message for the Receiver.

Interest rate change(s) that can be advised by this message type include: NOTICE, CALL, PRIME, COMMERCIAL,BASE, CURRENT and DEPOSIT.


MT 935 Rate Change Advice



----->

O 23 Further Identification 16x 2

O 25 Account Identification 35x 3

M 30 Effective Date of New Rate 6!n 4

----->

M 37H New Interest Rate 1!a12d 5

-----|-----|




The repetitive sequence must appear at least once (Error code(s): T11), but not more than ten times (Error code(s): T10).

C2



Either field 23 or field 25, but not both, must be present in any repetitive sequence (Error code(s): C83).

MT 935 Usage RulesAn MT 335 is to be used when advising an interest rate change relating to a specific call/notice loan/deposit.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION




2. Field 23: Further Identification

FORMAT

16x The format is structured as:

3!a[2!n]11x (Currency) (Number of Days) (Function)

PRESENCE

Conditional (C2)

DEFINITION

This field specifies the kind of interest rate being advised, in those cases where it is not related to a specific account.

CODES

Function must contain one of the following codes identifying the function of the message:

BASE Used to advise a change in the base rate

CALL Used to advise a change in the call rate

COMMERCIAL Used to advise a change in the commercial rate



CURRENT Used to advise a change in the interest rate applicable to current accounts

DEPOSIT Used to advise a change in the interest rate applicable to deposits

NOTICE Used to advise a change in the notice rate

PRIME Used to advise a change in the prime rate

USAGE RULES

Currency specifies the currency that applies to the rate.

Number of Days specifies the number of days notice (eg, 07). It must only be used when Function is NOTICE.


FORMAT

35x

PRESENCE

Conditional (C2)

DEFINITION

This field identifies the relevant account, where the rate change relates to a specific account serviced by the Sender for the Receiver.

4. Field 30: Effective Date of New Rate

FORMAT

6!n (Date)

PRESENCE

Mandatory

DEFINITION

This field specifies the effective date of the rate being advised.





5. Field 37H: New Interest Rate

FORMAT

Option H 1!a12d (Indicator) (Rate)

PRESENCE

Mandatory

DEFINITION

This field specifies the new interest rate being advised.

CODES

Indicator must contain one of the following codes:

C The new interest rate is a credit rate.

D The new interest rate is a debit rate.


The integer part of Rate must contain at least one digit. The decimal comma ’,’ is mandatory and is included in themaximum length (Error code(s): T40, T43).

USAGE RULES

This field may be repeated, if required.

Rate specifies the rate in decimal comma format.


FORMAT

6*35x (Narrative)


Line 1 /8c/[additional information] Additional explanatory information,which may be continued on the nextlines, is preceded by a double slash ’//’

Lines 2-6 [//continuation of additional information]or[/8c/[additional information]]



PRESENCE

Optional

DEFINITION


CODES


USAGE RULES




MT 940 Customer Statement Message


MT 940 ScopeThis message type is sent by an account servicing institution (reporting institution) to a financial institution (concentrating institution) which has been authorised by the account owner to receive it.

It is used to transmit detailed information about all entries booked to the account.


MT 940 Customer Statement Message



O 21 Related Reference 16x 2


M 28C Statement Number/Sequence Number 5n[/5n] 4

M 60a Opening Balance F or M 5

----->

O 61 Statement Line * 6

O 86 Information to Account Owner 6*65x 7

-----|

M 62a Closing Balance (Booked Funds) F or M 8

O 64 Closing Available Balance (Available Funds) 1!a6!n3!a15d 9

----->

O 65 Forward Available Balance 1!a6!n3!a15d 10

-----|


M = Mandatory O = Optional* See Field Specifications below.




If field 86 is present in any occurrence of the repetitive sequence, it must be preceded by a field 61. In addition, if field86 is present, it must be present on the same page (message) of the statement as the related field 61 (Error code(s): C24).

C2

The first two characters of the three character currency code in fields 60a, 62a, 64 and 65 must be the same for all occurrences of these fields (Error code(s): C27).

MT 940 Usage RulesThis message should only be used if the account owner(s) have authorised the financial institutions to transmit such information. It must be used according to agreed criteria.Financial institutions which receive this message must not use the information for their own purposes.It is important that amounts be identical to those of the original transaction. For identification purposes, deductions, eg,charges above and beyond those previously accounted for, shall appear separately with the appropriate code. They shalluse the same TRN as the original transaction, or other suitable reference if no TRN is available.Since the length of a SWIFT message is restricted to the maximum input message length, several messages may berequired to accommodate all the information for one statement.


1. Field 20: Transaction Reference Number (TRN)

FORMAT

16x

PRESENCE

Mandatory

DEFINITION




USAGE RULES

The TRN may be the same or different for the separate messages of a statement consisting of several messages.




FORMAT

16x

PRESENCE

Optional

DEFINITION

If the MT 940 is sent in response to an MT 920 Request Message, this field must contain the field 20 Transaction ReferenceNumber of the request message.




FORMAT

35x (Account)

PRESENCE

Mandatory

DEFINITION

This field identifies the account for which the statement is sent.

4. Field 28C: Statement Number/Sequence Number

FORMAT

Option C 5n[/5n] (Statement Number) (Sequence Number)

PRESENCE

Mandatory

DEFINITION

This field contains the sequential number of the statement, optionally followed by the sequence number of the messagewithin that statement when more than one message is sent for one statement.

USAGE RULES

The statement number should be reset to 1 on 1 January of each year.

If used, the sequence number always starts with 1. When several messages are sent to convey information about a single statement, the first message must contain ’/1’ in Sequence Number.



The sequence number must be incremented by one for each additional message.

Both the statement number and sequence number enable the Receiver to put the different messages into sequence and thusform the complete statement.

5. Field 60a: Opening Balance

FORMAT

Option F 1!a6!n3!a15d (D/C Mark) (Date) (Currency)(Amount)

Option M 1!a6!n3!a15d (D/C Mark) (Date) (Currency)(Amount)

PRESENCE

Mandatory

DEFINITION

This field specifies, for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the currency andthe amount of the balance.

CODES

D/C Mark must contain one of the following codes (Error code(s): T51):

C The (intermediate) opening balance is a credit balance.

D The (intermediate) opening balance is a debit balance.





USAGE RULES

This field must always be the same as field 62a (closing balance) of the previous customer statement message for this account.

The first customer statement message for a specified period must contain field 60F (first opening balance); additional state-ment messages for the same statement period must contain field 60M (intermediate opening balance).



6. Field 61: Statement Line

FORMAT

6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x]

where:

Subfield Format Name

1 6!n Value Date (YYMMDD)

2 [4!n] Entry Date (MMDD)

3 2a Debit/Credit Mark

4 [1!a] Funds Code (3rd character of the currency code, if needed)

5 15d Amount

6 1!a3!c Transaction Type Identification Code

7 16x Reference for the Account Owner

8 [//16x] Account Servicing Institution’s Reference

9 [34x] Supplementary Details

PRESENCE

Optional

DEFINITION

This field contains the details of each transaction.

CODES

Subfield 3, Debit/Credit Mark, must contain one of the following codes (Error code(s): T51):

D Debit

C Credit

RC Reversal of credit (debit entry)

RD Reversal of debit (credit entry)



CODES

Subfield 6, Transaction Type Identification Code, may be completed in one of three ways (Error code(s): T53):

1. For entries related to SWIFT transfer instructions and subsequent charge messages:

Format: S3!n

The last three characters will indicate the message type of the SWIFT message causing the entry (for debit entries)or the message type of the SWIFT message used to advise the account owner (for credit entries).

2. For entries related to payment and transfer instructions, including related charges messages, not sent throughSWIFT or where an alpha description is preferred.

Format: N3!c

3. For entries being first advised by the statement (items originated by the account servicing institution):

Format: F3!c

CODES

When formats (2) or (3) are used, the last three characters, ie, 3!c, may contain one of the following codes:

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

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 befollowed by the correct entry with the relevant code)


Subfield 1, Value Date, must be a valid date expressed as YYMMDD (Error code(s): T50).

The SWIFT System validates subfield 2, Entry Date (Date in reduced ISO form), using current System Year (Error code(s): T50).

The integer part of Amount must contain at least one digit. The decimal comma ’,’ is mandatory and is included in themaximum length (Error code(s): T40, T43).

When the first character of subfield 6, Transaction Type Identification Code, is an ’S’, the remaining characters must bein the range 100-999 (Error code(s): T18).

USAGE RULES

This field may be repeated within the constraints of the maximum input message length.

’Original’ advices for charges, ie, the first time the account owner is informed of a charge, must be identified in subfield 6, Transaction Type Identification Code, with the transaction type code ’FCHG’.

The following rules apply to subfield 7, Reference for the Account Owner:

At least one valid character other than a blank must be present.For debit entries, the purpose of this subfield is to identify, to the account owner, the instruction which caused thedebit. Therefore, the content of this subfield is the field 20 Sender’s Transaction Reference Number (or its equivalent)of the original instruction.Credit entries may be the result of one of the following situations:



1. The account servicing institution is identifying, to the account owner the receipt of funds for its account as a resultof a related transaction. In this case, the content of subfield 7, Reference for the Account Owner is the referencefor the beneficiary (eg, field 21 Related Reference) of the related transaction.

2. The account servicing institution has issued a payment instruction to the account owner and the credit identified inthis subfield is for that payment. The content of subfield 7, Reference for the Account Owner is the field 20 Trans-action Reference Number (or its equivalent) of the payment instruction issued by the account servicing institution.

If no reference is available for subfield 7, Reference for the Account Owner, the code NONREF shall be used. The account servicing institution must then supply, in subfield 9, Supplementary Details, what it considers to be the best alternative information.This reference must be quoted in all cases when available. In cases where a transaction passes through several financial institutions, the original reference must always be forwarded.This reference must always be quoted against any charges or fees debited by the account servicing institution.Debits against standing instructions must show the reference of the standing instruction.In cases where a mutually agreed alternative reference exists (eg, in foreign exchange or money market transactions), this reference should then be used.If the statement entry concerns a cheque, the cheque number should be indicated in this subfield.

The following rules apply to subfield 8, Account Servicing Institution’s Reference:

The content of this subfield is the account servicing institution’s own reference for the transaction.When the transaction has been initiated by the account servicing institution, this reference may be identical to subfield7, Reference for the Account Owner. If this is the case, Account Servicing Institution’s Reference, subfield 8 may be omitted.

The following rules apply to subfield 9, Supplementary Details:

When no reference for the account owner is available, ie, subfield 7, Reference for the Account Owner containsNONREF, the account servicing institution should provide the best available alternative information in this subfield.Supplementary details may be provided when an advice has not been sent for a transaction, or to provide additional information to facilitate reconciliation.This field may contain ERI to transport dual currencies, as explained in the chapter ’Euro - Impact on Category 9Message Standards’.In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be usedto transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by theexchange rate, format 12d, and terminated with another slash.

7. Field 86: Information to Account Owner

FORMAT

6*65x (Narrative)

PRESENCE

Conditional (C1)

DEFINITION

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



USAGE RULES


Since the charges field in the customer transfers is repetitive, it may be necessary to report more than one charges amount inthe resulting statement. In this case, it is allowed to repeat the code word CHGS before the code word OCMT. The order inwhich the charges are specified is the same as in the customer transfers, ie, the order in which the charges have been takenduring the transaction. So, the last appearance of the code word CHGS always specifies the charges (if any) of the account servicing institution.

In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate,format 12d, and terminated with another slash. The code may be repeated if the account servicing institution wants to reportan exchange rate that it applied, in addition to the exchange rate received in the instruction. The order in which the exchangerates are specified is the same as the order in which the rates have been applied during the transaction. So, the last appear-ance of the code word EXCH always specifies the rate applied by the account servicing institution.

An ordering party is identified with the preceding code /ORDP/. The information following this code is copied from field50a of the customer payment order, or field 52a (sender if field 52a is not present) of the financial institution transfer. Thecode should be used at the beginning of a line.

In case of a debit item, a beneficiary party may be identified with the preceding code /BENM/. The information followingthis code is copied from field 59a of the customer payment order, or field 58a of the financial institution transfer. The codeshould be used at the beginning of a line.

In case remittance information from field 70 of the payment instruction is to be included in this field, it should be precededby the code /REMI/.

In case the information in field 72 of the payment instruction is intended for the account owner, it should be copied intofield 86 as it is. Codes used in field 72 of the payment instruction have therefore the same meaning in field 86 of the state-ment. If only free text is used in field 72, it is to be copied as it is since a code in field 86 will not add any value.

8. Field 62a: Closing Balance (Booked Funds)

FORMAT



PRESENCE

Mandatory

DEFINITION

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

CODES


C The (intermediate) closing balance is a credit balance.



D The (intermediate) closing balance is a debit balance.





USAGE RULES

The content of this field will be repeated in field 60a of the subsequent customer statement message for this account.

If there is only one customer statement message transmitted for the period, this field must use tag option F, ie, 62F (finalclosing balance). When several messages are transmitted for the same statement period, all messages except the lastmessage must contain field 62M (intermediate closing balance); the last message of the statement must contain field 62F.

9. Field 64: Closing Available Balance (Available Funds)

FORMAT

1!a6!n3!a15d (D/C Mark) (Date) (Currency) (Amount)

PRESENCE

Optional

DEFINITION

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).

CODES


C The closing available balance is a credit balance.

D The closing available balance is a debit balance.







10. Field 65: Forward Available Balance

FORMAT


PRESENCE

Optional

DEFINITION

This field indicates the funds which are available to the account owner (if a credit or debit balance) for the specified forwardvalue date.

CODES


C The forward available balance is a credit balance.

D The forward available balance is a debit balance.





USAGE RULES

When there is more than one value date for the items booked to the account (in this or previous statement periods), this fieldwill indicate the balance which will be available to the account owner on the date(s) indicated.


FORMAT

6*65x (Narrative)

PRESENCE

Optional



DEFINITION

This field contains additional information on the statement as a whole. It is to be passed on to the account owner.



MT 941 Balance Report



It is used to transmit balance information, reflecting the situation at the identified time in field 13D.


MT 941 Balance Report





M 28 Statement Number/Sequence Number 5n[/2n] 4

O 13D Date/Time Indication 6!n4!n1!x4!n 5

O 60F Opening Balance 1!a6!n3!a15d 6

O 90D Number and Sum of Entries 5n3!a15d 7

O 90C Number and Sum of Entries 5n3!a15d 8

M 62F Closing Balance (Booked Funds) 1!a6!n3!a15d 9


----->

O 65 Forward Available Balance 1!a6!n3!a15d 11

-----|






The first two characters of the three character currency code in fields 60F, 90D, 90C, 62F, 64 and 65 must be the samefor all occurrences of these fields (Error code(s): C27).

MT 941 Usage RulesThis message should only be used if the account owner(s) has (have) authorised the financial institutions to transmitsuch information. It must be used according to agreed criteria.Financial institutions which receive this message must not use the information for their own purposes.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION





FORMAT

16x

PRESENCE

Optional

DEFINITION







FORMAT

35x (Account)

PRESENCE

Mandatory

DEFINITION

This field identifies the account for which the balance information is sent.

4. Field 28: Statement Number/Sequence Number

FORMAT

5n[/2n] (Statement Number) (Sequence Number)

PRESENCE

Mandatory

DEFINITION

This field contains the sequential number of the report.

USAGE RULES

The sequence number is not required.

5. Field 13D: Date/Time Indication

FORMAT

Option D 6!n4!n1!x4!n (Date) (Time) (Sign) (Offset)

PRESENCE

Optional

DEFINITION

This field indicates the date, time and time zone at which the report was created.





Time must be a valid time expressed as HHMM (Error code(s): T38).

Sign is either "+" or "-" (Error code(s): T15).

Time offset is expressed as ’HHMM’, where the hour component, ie, ’HH’, must be in the range of 00 through 13, and theminute component, ie, ’MM’ must be in the range of 00 through 59. Any ’HH’ or ’MM’ component outside of these rangechecks will be disallowed (Error code(s): T16).

USAGE RULES

The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated UniversalTime - ISO 8601).

6. Field 60F: Opening Balance

FORMAT


PRESENCE

Optional

DEFINITION

This field specifies, for the opening balance, whether it is a debit or credit balance, the date, the currency and the amount ofthe balance.

CODES


C The opening balance is a credit balance.

D The opening balance is a debit balance.







USAGE RULES

This field must always be the same as field 62F of the previous statement or balance report.

7. Field 90D: Number and Sum of Entries

FORMAT

Option D 5n3!a15d (Number) (Currency) (Amount)

PRESENCE

Optional

DEFINITION

This field indicates the total number and amount of debit entries since the last statement or balance report.




8. Field 90C: Number and Sum of Entries

FORMAT

Option C 5n3!a15d (Number) (Currency) (Amount)

PRESENCE

Optional

DEFINITION

This field indicates the total number and amount of credit entries since the last statement or balance report.




9. Field 62F: Closing Balance (Booked Funds)



FORMAT


PRESENCE

Mandatory

DEFINITION

This field contains the closing book balance for the account as of the end of the business day indicated.

CODES


C The closing balance is a credit balance.

D The closing balance is a debit balance.






FORMAT


PRESENCE

Optional

DEFINITION


CODES










11. Field 65: Forward Available Balance

FORMAT


PRESENCE

Optional

DEFINITION

This field indicates the funds which are available to the account owner (if a credit or debit balance) for the specified forwardvalue date.

CODES


C The forward available balance is a credit balance.

D The forward available balance is a debit balance.





USAGE RULES

When there is more than one value date for the items booked to the account (in this or previous statement periods), this fieldwill indicate the balance which will be available to the account owner on the date(s) indicated.




FORMAT

6*65x (Narrative)

PRESENCE

Optional

DEFINITION

This field contains additional information for the account owner.



MT 942 Interim Transaction Report



It is used to transmit detailed and/or summary information about entries debited or credited to the account since:

the last statement or balance report, orthe last interim transaction report (sent in the period since the last statement or balance report).


MT 942 Interim Transaction Report






M 34F Floor Limit Indicator 3!a[1!a]15d 5


M 13D Date/Time Indication 6!n4!n1!x4!n 7

----->



-----|

O 90D Number and Sum of Entries 5n3!a15d 10

O 90C Number and Sum of Entries 5n3!a15d 11





M = Mandatory O = Optional* See Field Specifications


The first two characters of the three character currency code in fields 34F, 90D, and 90C must be the same (Errorcode(s): C27).

C2

When only one field 34F is present, the second subfield must not be used. When both fields 34F are present, subfield 2of the first 34F must contain the value ’D’, and subfield 2 of the second 34F must contain the value ’C’ (Error code(s): C23).

MT 942 Usage RulesThis message should only be used if the account owner(s) has (have) authorised the financial institutions to transmitsuch information. It must be used according to agreed criteria.Financial institutions which receive this message must not use the information for their own purposes.It is important that amounts be identical to those of the original transaction. For identification purposes, deductions, eg,charges above and beyond those previously accounted for, shall appear separately with the appropriate code. They shalluse the same TRN as the original transaction, or other suitable reference if no TRN is available.Since the length of a SWIFT message is restricted to the maximum input message length, several messages may berequired to accommodate all the information for one statement.Depending on financial practice and the agreement(s) between the account servicing institution and the account owner,the items reported in this message may or may not be considered as booked or available funds.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION






USAGE RULES

The TRN may be the same or different for the separate messages of an interim report consisting of several messages.


FORMAT

16x

PRESENCE

Optional

DEFINITION





FORMAT

35x (Account)

PRESENCE

Mandatory

DEFINITION

This field identifies the account for which the interim transaction report is sent.


FORMAT


PRESENCE

Mandatory

DEFINITION

This field contains the sequential number of the statement, optionally followed by the sequence number of the messagewithin that statement when more than one message is sent for the statement.



USAGE RULES

The statement number should be reset to 1 on 1 January of each year.

If used, the sequence number always starts with 1. When several messages are sent to convey information about a single statement, the first message must contain ’/1’ in Sequence Number.

The sequence number must be incremented by one for each additional message.

Both the statement number and sequence number enable the Receiver to put the different messages into sequence and thusform the complete statement.

5. Field 34F: Floor Limit Indicator (First Occurrence)

FORMAT


PRESENCE

Mandatory

DEFINITION

This field specifies the minimum value (transaction amount) reported in the message.

CODES

When D/C Mark is present, it must contain the following code (Error code(s): T51):

D Debit floor limit




USAGE RULES

When the field appears once, the floor limit applies to both debit and credit amounts. When different limits apply, bothfields 34F must be present.

6. Field 34F: Floor Limit Indicator (Second Occurrence)

FORMAT




PRESENCE

Conditional (C2)

DEFINITION

This field specifies the minimum credit value (transaction amount) reported in the message.

CODES

D/C Mark must contain the following code (Error code(s): T51):

C Credit floor limit




USAGE RULES

When different limits apply, this field 34F must be present, with a credit indicator (’C’).

7. Field 13D: Date/Time Indication

FORMAT

Option D 6!n4!n1!x4!n (Date) (Time) (Sign) (Offset)

PRESENCE

Mandatory

DEFINITION

This field indicates the date, time and time zone at which the report was created.



Time must be a valid time expressed as HHMM (Error code(s): T38).

Sign is either "+" or "-" (Error code(s): T15).

Time offset is expressed as ’HHMM’, where the hour component, ie, ’HH’, must be in the range of 00 through 13, and theminute component, ie, ’MM’ must be in the range of 00 through 59. Any ’HH’ or ’MM’ component outside of these rangechecks will be disallowed (Error code(s): T16).



USAGE RULES

The time zone in which Time is expressed is to be identified by means of the offset against the UTC (Coordinated UniversalTime - ISO 8601).


FORMAT

6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x]

where:






5 15d Amount





PRESENCE

Optional

DEFINITION


CODES


D Debit

C Credit

EC Expected credit



ED Expected debit



CODES



Format: S3!n



Format: N3!c


Format: F3!c

CODES



BRF Brokerage fee


CHK Cheques










COM Commission





ECK Eurocheques


INT Interest

LBX Lock box

LDP Loan deposit

MSC Miscellaneous

RTI Returned item


STO Standing order


TRF Transfer









USAGE RULES











When no reference for the account owner is available, ie, subfield 7, Reference for the Account Owner containsNONREF, the account servicing institution should provide the best available alternative information in this subfield.Supplementary details may be provided when an advice has not been sent for a transaction, or to provide additional information to facilitate reconciliation.This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards.This field may contain ERI to transport dual currencies, as explained in the chapter ’Euro - Impact on Category 9Message Standards’.In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be usedto transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by theexchange rate, format 12d, and terminated with another slash.




FORMAT

6*65x (Narrative)

PRESENCE

Optional

DEFINITION

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

USAGE RULES


Since the charges field in the customer transfers is repetitive, it may be necessary to report more than one charges amount inthe resulting statement. In this case, it is allowed to repeat the code word CHGS before the code word OCMT. The order inwhich the charges are specified is the same as in the customer transfers, ie, the order in which the charges have been takenduring the transaction. So, the last appearance of the code word CHGS always specifies the charges (if any) of the account servicing institution.

In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate,format 12d, and terminated with another slash. The code may be repeated if the account servicing institution wants to reportan exchange rate that it applied, in addition to the exchange rate received in the instruction. The order in which the exchangerates are specified is the same as the order in which the rates have been applied during the transaction. So, the last appear-ance of the code word EXCH always specifies the rate applied by the account servicing institution.

An ordering party is identified with the preceding code /ORDP/. The information following this code is copied from field50a of the customer payment order, or field 52a (sender if field 52a is not present) of the financial institution transfer. Thecode should be used at the beginning of a line.

In case of a debit item, a beneficiary party may be identified with the preceding code /BENM/. The information followingthis code is copied from field 59a of the customer payment order, or field 58a of the financial institution transfer. The codeshould be used at the beginning of a line.

In case remittance information from field 70 of the payment instruction is to be included in this field, it should be precededby the code /REMI/.

In case the information in field 72 of the payment instruction is intended for the account owner, it should be copied intofield 86 as it is. Codes used in field 72 of the payment instruction have therefore the same meaning in field 86 of the state-ment. If only free text is used in field 72, it is to be copied as it is since a code in field 86 will not add any value.

10. Field 90D: Number and Sum of Entries

FORMAT

Option D 5n3!a15d (Number) (Currency) (Amount)



PRESENCE

Optional

DEFINITION

This field indicates the total number and amount of debit entries.




11. Field 90C: Number and Sum of Entries

FORMAT

Option C 5n3!a15d (Number) (Currency) (Amount)

PRESENCE

Optional

DEFINITION

This field indicates the total number and amount of credit entries.





FORMAT

6*65x (Narrative)

PRESENCE

Optional

DEFINITION

This field contains additional information on the message as a whole which is to be passed to the account owner.



MT 950 Statement Message

MT 950 ScopeThis message type is sent by an account servicing institution to an account owner.

It is used to transmit detailed information about all entries, whether or not caused by a SWIFT message, booked to the account.


MT 950 Statement Message






----->


-----|

M 62a Closing Balance (Booked Funds) F or M 6


M = Mandatory O = Optional* See the Field Specifications below.


The first two characters of the three character currency code in fields 60a, 62a and 64 must be the same (Error code(s): C27).

MT 950 Usage RulesCharges, interest and other adjustments may be referenced as follows:

By reference to a previous MT n90 Advice of Charges, Interest and Other Adjustments message (for information regarding the formatting of the MTn90, see Category n - Common Group Messages).By original advice via this statement, under the following conditions:

The charges must be unambiguously identified with a single associated underlying transaction, eg, theaccount owner’s reference of the original transaction.The principal amount must be separately identified on the statement.



The required references must fit the constraints of the statement line.It is important that amounts should be identical to those of related messages. Charges which are clearly indicated inanother message concerning the same entry, or which form an integral part of another message, eg, proceeds of a collection, do not need to be specifically indicated in the statement. Deductions, eg, charges, above and beyond those previously accounted for in a related message shall appear separately with the appropriate code. They shall use thesame reference for the account owner or other suitable reference if no reference for the account owner is available.The account servicing institution must not ’bulk’ separate transactions, charges, or charges with transactions. Whenbooking multiple messages, individual transactions, eg, one entry per TRN (field 20), must be booked.It is recommended that statements be sent daily, ie, at the end of each business day, when movement in the account hasoccurred. If no movement has occurred, ie, no entries have been posted, it is recommended that the statementfrequency should be monthly, and that the maximum interval between statements should not exceed one year.To facilitate manual reconciliation, it is recommended that statement entries be sorted by debits and credits and theseby value date in ascending amounts.Since the length of a SWIFT message is restricted to the maximum input message length, several messages may berequired to accommodate all the information for one statement.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION




USAGE RULES

The TRN may be the same or different for the separate messages of a statement consisting of several messages.


FORMAT

35x (Account)

PRESENCE

Mandatory



DEFINITION

This field identifies the account for which the statement is sent.


FORMAT


PRESENCE

Mandatory

DEFINITION

This field contains the sequential number of the statement, optionally followed by the sequence number of the messagewithin that statement when more than one message is sent for the statement.


FORMAT



PRESENCE

Mandatory

DEFINITION


CODES










USAGE RULES

This field must always be the same as field 62a (closing balance) of the previous statement message for this account.

The first statement message for a specified period must contain field 60F (first opening balance); additional statementmessages for the same statement period must contain field 60M (intermediate opening balance).


FORMAT

6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x]

where:






5 15d Amount





PRESENCE

Optional

DEFINITION




CODES


D Debit

C Credit



CODES



Format: S3!n



Format: N3!c


Format: F3!c

CODES



BRF Brokerage fee


CHK Cheques










COM Commission




ECK Eurocheques



INT Interest

LBX Lock box

LDP Loan deposit

MSC Miscellaneous

RTI Returned item


STO Standing order


TRF Transfer









USAGE RULES











When no reference for the account owner is available, ie, subfield 7, Reference for the Account Owner containsNONREF, the account servicing institution should provide the best available alternative information in this subfield.Supplementary details may be provided when an advice has not been sent for a transaction, or to provide additional information to facilitate reconciliation.

6. Field 62a: Closing Balance (Booked Funds)

FORMAT

Option F 1!a6!n3!a15d (D/C Mark) (Date)(Currency) (Amount)

Option M 1!a6!n3!a15d (D/C Mark) (Date)(Currency) (Amount)



PRESENCE

Mandatory

DEFINITION


CODES








USAGE RULES

The contents of this field will be repeated in field 60a of the subsequent statement message for this account.

If there is only one statement message transmitted for the period, this field must use tag option F, ie, 62F (final closingbalance). When several messages are transmitted for the same statement period, all messages except the last message mustcontain field 62M (intermediate closing balance); the last message of the statement must contain field 62F.


FORMAT


PRESENCE

Optional

DEFINITION




CODES










MT 960 Request for Service Initiation Message

Note: This message may only be sent between financial institutions in an automated exchange of authen-ticator keys.

MT 960 ScopeThis message is sent from one SWIFT user to another SWIFT user to initiate a Bilateral Key Exchange (BKE) process. Therequest in this message is an RSI class Cryptographic Service Message.


MT 960 Request for Service Initiation Message



O 79 Narrative 35*50x 2

M 91A Request for Service Initiation * 3

M = Mandatory O = Optional*See Field Specifications


MT 960 GuidelinesIf the request is agreed, the Receiver of the MT 960 must return the requested certificate using an MT 961, otherwisethe request is rejected.



FORMAT

16x

PRESENCE

Mandatory



DEFINITION

This field specifies a reference assigned by the Sender to identify the key exchange.



USAGE RULES

It is recommended that the TRN be assigned as a common reference for all messages initiated during a bilateral key exchange.

2. Field 79: Narrative

FORMAT

35*50x (Narrative)

PRESENCE

Optional

DEFINITION

This field contains information in narrative form.

3. Field 91A: Request for Service Initiation

FORMAT

Option A CSM(MCL/RSI1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eSVR/CVO)

PRESENCE

Mandatory

DEFINITION

This field contains a request.



MT 961 Initiation Response Message


MT 961 ScopeThis message is sent by the Receiver of an MT 960 Request for Service Initiation Message to the Sender of the MT 960 to acknowledge receipt of the request and to deliver a certificate in order to continue the Bilateral Key Exchange process. The acknowledgement in this message is an RSM class of Cryptographic Service Message.


MT 961 Initiation Response Message




M 91B Response Service Message * 3





FORMAT

16x

PRESENCE

Mandatory

DEFINITION






USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the content of field 20 Transaction Reference Number of the MT 960 to which it responds.



3. Field 91B: Response Service Message

FORMAT

Option B CSM(MCL/RSM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eCV/160-288h)

PRESENCE

Mandatory

DEFINITION

This field contains a response message.



MT 962 Key Service Message


MT 962 ScopeThis message is sent by the Receiver of an MT 961 Initiation Response Message to the Sender of the MT 961 to send a bilateral authenticator key as part of the bilateral key exchange process. The bilateral key in enciphered form in this messageis contained in a KSM class Cryptographic Service Message.


MT 962 Key Service Message




M 91C Key Service Message * 3





FORMAT

16x

PRESENCE

Mandatory

DEFINITION






USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the content of field 20 Transaction Reference Number of the MT 961 to which it responds.



3. Field 91C: Key Service Message

FORMAT

Option C CSM(MCL/KSM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eCV/160-288h1!eBE/128-256h1!eBES/128-256h1!eND/.1!n.16!c1!eEDK/12!n1!eCTP/14h1!eMAC/4!h1!e4!h)

PRESENCE

Mandatory

DEFINITION

This field contains a key service message.



MT 963 Key Acknowledgement Message


MT 963 ScopeThis message is sent by the Receiver of an MT 962 Key Service Message to acknowledge receipt of the bilateral key. This acknowledgement is an RSM class Cryptographic Service Message.


MT 963 Key Acknowledgement Message




M 91D Response Service Message * 3





FORMAT

16x

PRESENCE

Mandatory

DEFINITION






USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the contents of field 20 Transaction Reference Number of the MT 962 to which it responds.



3. Field 91D: Response Service Message

FORMAT

Option D CSM(MCL/RSM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eMAC/4!h1!e4!h)

PRESENCE

Mandatory

DEFINITION

This field contains a response service message.



MT 964 Error Message


MT 964 ScopeThis message is sent by the Receiver of an MT 960 Request for Service Initiation Message, MT 961 Initiation ResponseMessage, MT 963 Key Acknowledgement Message, MT 966 Discontinue Service Message or MT 967 Discontinuation Acknowledgement Message to the Sender if an error has been detected in that message. The error code is contained in anESM class Cryptographic Service Message.


MT 964 Error Message




M 79 Additional Error Comments 35*50x 3

M 91E Error on RSI, RSM or DSM * 4





FORMAT

16x

PRESENCE

Mandatory



DEFINITION




USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the contents of field 20 Transaction Reference Number of the MT 960, MT 961, MT 963, MT 966or MT 967 to which this message responds.



3. Field 79: Additional Error Comments

FORMAT

35*50x (Narrative)

PRESENCE

Mandatory

DEFINITION

This field must be used to add comments on the error code(s) contained in field 91E.

USAGE RULES

Use of this field may require manual intervention by the Receiver.



4. Field 91E: Error on RSI, RSM or DSM

FORMAT

Option E CSM(MCL/ESM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!e[IDA/16!c1!e]ERF/1!a[15a])

PRESENCE

Mandatory

DEFINITION

This field contains an error message.



MT 965 Error in Key Service Message


MT 965 ScopeThis message is sent by the Receiver of an MT 962 Key Service Message to the Sender if an error has been detected in thatmessage. The error code is contained in an ESM class Cryptographic Service Message.


MT 965 Error in Key Service Message




M 79 Additional Error Comments 35*50x 3

M 91F Error on KSM * 4





FORMAT

16x

PRESENCE

Mandatory



DEFINITION




USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the contents of field 20 Transaction Reference Number of the MT 962 to which this message responds.



3. Field 79: Additional Error Comments

FORMAT

35*50x (Narrative)

PRESENCE

Mandatory

DEFINITION

This field must be used to add comments on the error code(s) contained in field 91F.

USAGE RULES




4. Field 91F: Error on KSM

FORMAT

Option F CSM(MCL/ESM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eIDA/16!c1!eCTP/14h1!e[CTR/14h1!e]ERF/1!a[15a])

PRESENCE

Mandatory

DEFINITION

This field contains an error in key service message.



MT 966 Discontinue Service Message


MT 966 ScopeThis message is sent by a financial institution to another financial institution with which it has exchanged bilateral keys. It isused to discontinue one or several bilateral authenticator keys already in existence between the Sender and Receiver. The identification of the keys to be discontinued are contained in a DSM class Cryptographic Service Message.


MT 966 Discontinue Service Message



O 79 Additional Comments 35*50x 2

M 91G Discontinue Service Message * 3





FORMAT

16x

PRESENCE

Mandatory

DEFINITION






USAGE RULES


2. Field 79: Additional Comments

FORMAT

35*50x (Narrative)

PRESENCE

Optional

DEFINITION

This field should be used to add comments on the discontinuation of keys in field 91G.

USAGE RULES


3. Field 91G: Discontinue Service Message

FORMAT

Option G CSM(MCL/DSM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!e IDD/[16!c]1!e[IDD/[16!c]1!e]0-5IDA/16!c1!eMAC/4!h1!e4!h)

PRESENCE

Mandatory

DEFINITION

This field contains a discontinue service message



MT 967 Discontinuation Acknowledgement Message


MT 967 ScopeThis message is sent by the Receiver of an MT 966 Discontinue Service Message to the Sender. It is used to acknowledgereceipt of the previous MT 966 and confirms discontinuation of the authenticator key(s) specified in the MT 966.


MT 967 Discontinuation Acknowledgement Message




O 79 Additional Comments 35*50x 3

M 91H Response Service Message * 4





FORMAT

16x

PRESENCE

Mandatory



DEFINITION




USAGE RULES



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the contents of field 20 Transaction Reference Number of the MT 966 to which this message responds.



3. Field 79: Additional Comments

FORMAT

35*50x (Narrative)

PRESENCE

Optional

DEFINITION

This field should be used to add comments on the discontinuation of keys in field 91H.

USAGE RULES




4. Field 91H: Response Service Message

FORMAT

Option H CSM(MCL/RSM1!eRCV/4!a[2!a[2!c[8c]]]1!eORG/4!a[2!a[2!c[8c]]]1!eIDD/[16!c]1!eIDD/[16!c]1!e]0-5MAC/4!h1!e4!h)

PRESENCE

Mandatory

DEFINITION

This field contains a response service message.



MT 970 Netting Statement

Note: This message may only be sent and received after prior arrangement between a user and SWIFT

MT 970 ScopeThis message type is sent at pre-arranged times from a netting system to a subscriber to the netting system.

It is used to provide detailed information about all the transactions which have been recorded by the netting system involv-ing the receiving financial institution.

All transactions are reported once only in an MT 970 Netting Statement.


MT 970 Netting Statement






----->


-----|

M 62a Closing Balance F or M 6

O 64 Closing Available Balance 1!a6!n3!a15d 7

M = Mandatory O = Optional*See the Field Specifications below.





MT 970 Usage RulesEntries must be sorted by ascending amount, within debits and credits.Since the length of a SWIFT message is restricted to the maximum input message length, several messages may berequired to accommodate all the information in one statement.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field specifies a reference assigned by the Sender to unambiguously identify the message.



USAGE RULES

The TRN may be the same or different for the separate messages of a netting statement consisting of several messages.


FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the netting position for which the netting statement is sent.


FORMAT




PRESENCE

Mandatory

DEFINITION

This field contains the statement number of the netting statement, optionally followed by the sequence number of themessage within that statement, when more than one message is sent for the statement.


FORMAT



PRESENCE

Mandatory

DEFINITION

This field specifies for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the currency andthe amount of the balance.

CODES








USAGE RULES

This field must always be the same as field 62a (closing balance) of the previous netting statement message (if any) for thisnetting position.

The first netting statement message of a statement must contain field 60F (first opening balance). Subsequent messages ofthe same statement must contain field 60M (intermediate opening balance).




FORMAT

6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x]

where:






5 15d Amount





PRESENCE

Optional

DEFINITION


CODES


D Debit

C Credit





CODES



Format: S3!n



Format: N3!c


Format: F3!c

CODES



BRF Brokerage fee


CHK Cheques








COM Commission






ECK Eurocheques



INT Interest

LBX Lock box

LDP Loan deposit

MSC Miscellaneous

RTI Returned item


STO Standing order


TRF Transfer







USAGE RULES














6. Field 62a: Closing Balance

FORMAT



PRESENCE

Mandatory

DEFINITION


CODES










USAGE RULES

The content of this field will be repeated in field 60a of the subsequent netting statement message for this netting position.

All netting statement messages of a statement, except the last message, must contain field 62M (intermediate closingbalance); the last message of the statement must contain field 62F (final closing balance).

7. Field 64: Closing Available Balance

FORMAT


PRESENCE

Optional

DEFINITION

This field indicates the funds which are available to the Receiver (if credit balance) or the balance which is subject to inter-est charges (if debit balance).

CODES










MT 971 Netting Balance Report


MT 971 ScopeThis message type is sent, on request or at pre-arranged times, from a netting system to a subscriber to the netting systemand to other authorised receivers.

It is used to advise the netting balance(s), at the time of transmission, for one or more financial institutions.


MT 971 Netting Balance Report



----->


M 62F Final Closing Balance 1!a6!n3!a15d 3

-----|





FORMAT

16x

PRESENCE

Mandatory



DEFINITION

This field specifies the reference assigned by the Sender to unambiguously identify this message.




FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the netting position for which the balance is being sent.

3. Field 62F: Final Closing Balance

FORMAT

Option F 1!a6!n3!a15d (D/C Mark) (Date) (Currency) (Amount)

PRESENCE

Mandatory

DEFINITION

This field contains the balance for the netting position identified in field 25.

CODES


C The final closing balance is a credit balance.

D The final closing balance is a debit balance.






MT 972 Netting Interim Statement


MT 972 ScopeThis message type is sent, on request or at pre-arranged times, from a netting system to a subscriber to the netting system.

It is used to provide detailed information about transactions which have been recorded by the netting system involving the receiving financial institution.


MT 972 Netting Interim Statement






----->


-----|

M 62a Closing Balance F or M 6

O 64 Closing Available Balance 1!a6!n3!a15d 7

M = Mandatory O = Optional* See the Field Specifications below.





MT 972 Usage RulesTransactions may appear in more than one netting interim statement if more than one is generated for the same netting position.Entries must be sorted by ascending amount, within debits and credits.Since the length of a SWIFT message is restricted to the maximum input length, several messages may be required to accommodate all the information for one statement.



FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field specifies the reference assigned by the Sender to unambiguously identify this message.



USAGE RULES

The TRN may be the same or different for the separate messages of a netting statement consisting of several messages.


FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the netting position for which the netting interim statement is sent.




FORMAT


PRESENCE

Mandatory

DEFINITION

This field contains the statement number of the netting interim statement, optionally followed by the sequence number ofthe message within the statement, when more than one message is sent for the statement.


FORMAT



PRESENCE

Mandatory

DEFINITION


CODES










USAGE RULES

This field must always be the same as field 62a (closing balance) of the previous netting interim statement message for thisnetting position.

The first netting interim statement message of a statement must contain field 60F (first opening balance); subsequentmessages of the same statement must contain field 60M (intermediate opening balance).


FORMAT

6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x]

where:






5 15d Amount





PRESENCE

Optional

DEFINITION


CODES


D Debit

C Credit





CODES



Format: S3!n



Format: N3!c


Format: F3!c

CODES



BRF Brokerage fee


CHK Cheques










COM Commission

DCR Documentary credit (ussed when entering a principal amount)



ECK Eurocheques



INT Interest

LBX Lock box

LDP Loan deposit

MSC Miscellaneous

RTI Returned item


STO Standing order


TRF Transfer







USAGE RULES











The content of this subfield is the account servicing institution’s own reference for the transaction.When the transaction has been initiated by the account servicing institution, this reference may be identical to subfield7, Reference for the Account Owner. If this is the case, Account Servicing Institution’s Reference, subfield 8, may be omitted.



6. Field 62a: Closing Balance

FORMAT





PRESENCE

Mandatory

DEFINITION


CODES








USAGE RULES

The contents of this field will be repeated in field 60a (opening balance) of the subsequent netting interim statementmessage for this netting position.

All netting interim statement messages of a statement, except the last message, must contain field 62M (intermediate closingbalance); the last message of the statement must contain field 62F (final closing balance).

7. Field 64: Closing Available Balance

FORMAT


PRESENCE

Optional

DEFINITION

This field indicates the funds which are available to the Receiver (if credit balance) or the balance which is subject to inter-est charges (if debit balance).



CODES










MT 973 Netting Request Message


MT 973 ScopeThis message type is sent by a financial institution to a netting system.

It is used to request the netting system to transmit an MT 971 Netting Balance Report, an MT 972 Netting Interim Statementor an MT 998 Proprietary Message containing the latest available information.


MT 973 Netting Request Message



----->

M 12 Message Type 3!n 2


-----|


MT 973 Network Validated RulesThere are no network validated field rules for this message type.



FORMAT

16x

PRESENCE

Mandatory



DEFINITION




2. Field 12: Message Type

FORMAT

3!n

PRESENCE

Mandatory

DEFINITION

This field identifies the message type which is being requested.

CODES

This field must contain one of the following message type numbers (Error code(s): T88):

971 Netting Balance Report

972 Netting Interim Statement

998 Proprietary Message


FORMAT

35x

PRESENCE

Mandatory

DEFINITION

This field identifies the netting position for which balance or transaction detail information is requested.



MT 985 Status Enquiry

MT 985 ScopeThis message type is sent by a financial institution, to another financial institution, to request an MT 986 Status Report.


MT 985 Status Enquiry



O 57a Account With Institution A, B or D 2

M 59 Enquired Party [/34x]4*35x

3

O 75 Queries 6*35x 4





FORMAT

16x

PRESENCE

Mandatory

DEFINITION






2. Field 57a: Account With Institution

FORMAT

Option A [/1!a][/34x]4!a2!a2!c[3!c]


Option B [/1!a][/34x][35x]

(Party Identifier)(Location)

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


PRESENCE

Optional

DEFINITION

This field identifies the financial institution and/or branch of the financial institution of the enquired party.




USAGE RULES

When this information is known, it should be specified, even when it is the Receiver of the message.

3. Field 59: Enquired Party

FORMAT

[/34x]4*35x


PRESENCE

Mandatory

DEFINITION

This field specifies the party about which information is requested.

USAGE RULES

When an account number is provided, it is the account number on the books of the Receiver.

4. Field 75: Queries



FORMAT

6*35x (Narrative)

PRESENCE

Optional

DEFINITION

This field is used when information other than general credit information is requested for the enquired party.

USAGE RULES

This field contains a narrative explanation of the information requested.



MT 986 Status Report

MT 986 ScopeThis message type is sent by a financial institution, to another financial institution, to provide general credit information,without responsibility, about an individual or an institution.


MT 986 Status Report




O 59 Enquired Party [/34x]4*35x

3

M 79 Narrative 35*50x 4





FORMAT

16x

PRESENCE

Mandatory

DEFINITION







FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field must contain the content of field 20 Transaction Reference Number of the MT 985 which requested the informa-tion in this message.



3. Field 59: Enquired Party

FORMAT

[/34x]4*35x


PRESENCE

Optional

DEFINITION

This field specifies the party about which information is provided.

USAGE RULES

When an account number is provided, it is the account on the books of the Sender.

4. Field 79: Narrative

FORMAT

35*50x (Narrative)

PRESENCE

Mandatory



DEFINITION

This field contains the information requested.



MT 990 Advice of Charges, Interest and Other Adjustments

Please refer to Category n - Common Group Messages , Chapter MT n90 Advice of Charges, Interest and Other Adjust-ments for details concerning this message type.



MT 991 Request for Payment of Charges, Interest and Other Expenses

Please refer to Category n - Common Group Messages , Chapter MT n91 Request for Payment of Charges, Interest andOther Expenses for details concerning this message type.



MT 992 Request for Cancellation

Please refer to Category n - Common Group Messages , Chapter MT n92 Request for Cancellation for details concerningthis message type.



MT 995 Queries

Please refer to Category n - Common Group Messages , Chapter MT n95 Queries for details concerning this message type.



MT 996 Answers

Please refer to Category n - Common Group Messages , Chapter MT n96 Answers for details concerning this message type.



MT 998 Proprietary Message

Please refer to Category n - Common Group Messages, Chapter MT n98 Proprietary Message for details concerning thismessage type.



MT 999 Free Format Message

Please refer to Category n - Common Group Messages , Chapter MT n99 Free Format Message for details concerning thismessage type.



Table of Contents

....................... 2Legal Notices

....................... 3Overview

.................... 3Added Message Types

................... 3Removed Message Types

................... 3Modified Message Types

................... 4MT 900 Confirmation of Debit

...................... 4MT 900 Scope

.................. 4MT 900 Format Specifications

.................. 4MT 900 Network Validated Rules

.................... 4MT 900 Usage Rules

................ 4MT 900 Field Specifications (updated)

............... 41. Field 20: Transaction Reference Number

.................. 52. Field 21: Related Reference

................. 53. Field 25: Account Identification

............. 54. Field 32A: Value Date, Currency Code, Amount

............... 65. Field 52a: Ordering Institution (updated)

............... 86. Field 72: Sender to Receiver Information

................... 9MT 910 Confirmation of Credit

...................... 9MT 910 Scope



.................... 10MT 910 Usage Rules

................ 10MT 910 Field Specifications (updated)


.................. 102. Field 21: Related Reference


............. 114. Field 32A: Value Date, Currency Code, Amount

............... 115. Field 50a: Ordering Customer (updated)

............... 126. Field 52a: Ordering Institution (updated)

................ 147. Field 56a: Intermediary (updated)


.................... 16MT 920 Request Message

...................... 16MT 920 Scope



.................... 17MT 920 Usage Rules

................... 17MT 920 Field Specifications


................. 172. Field 12: Message Requested


................. 184. Field 34F: Floor Limit Indicator

................. 195. Field 34F: Floor Limit Indicator

................... 20MT 935 Rate Change Advice

...................... 20MT 935 Scope



.................... 21MT 935 Usage Rules

................... 21MT 935 Field Specifications


................. 212. Field 23: Further Identification


................ 224. Field 30: Effective Date of New Rate

................. 235. Field 37H: New Interest Rate


................. 25MT 940 Customer Statement Message

...................... 25MT 940 Scope



iStandards Release Guide 2003 - Final edition - February 2003

Table Of ContentsSWIFTStandards - Category 9

...................... 26MT 940 Usage Rules

.................... 26MT 940 Field Specifications

............... 261. Field 20: Transaction Reference Number (TRN)

................... 262. Field 21: Related Reference

.................. 273. Field 25: Account Identification

.............. 274. Field 28C: Statement Number/Sequence Number

................... 285. Field 60a: Opening Balance

.................... 296. Field 61: Statement Line

................ 327. Field 86: Information to Account Owner

................ 338. Field 62a: Closing Balance (Booked Funds)

............. 349. Field 64: Closing Available Balance (Available Funds)

................. 3510. Field 65: Forward Available Balance


...................... 37MT 941 Balance Report

....................... 37MT 941 Scope

.................... 37MT 941 Format Specifications

................... 38MT 941 Network Validated Rules

...................... 38MT 941 Usage Rules





............... 394. Field 28: Statement Number/Sequence Number

.................. 395. Field 13D: Date/Time Indication

................... 406. Field 60F: Opening Balance

................. 417. Field 90D: Number and Sum of Entries

................. 418. Field 90C: Number and Sum of Entries

................ 419. Field 62F: Closing Balance (Booked Funds)


................. 4311. Field 65: Forward Available Balance


................... 45MT 942 Interim Transaction Report

....................... 45MT 942 Scope



...................... 46MT 942 Usage Rules






.............. 485. Field 34F: Floor Limit Indicator (First Occurrence)

............. 486. Field 34F: Floor Limit Indicator (Second Occurrence)

.................. 497. Field 13D: Date/Time Indication



................ 5410. Field 90D: Number and Sum of Entries

................ 5511. Field 90C: Number and Sum of Entries


..................... 56MT 950 Statement Message

....................... 56MT 950 Scope



...................... 56MT 950 Usage Rules







................ 626. Field 62a: Closing Balance (Booked Funds)


Standards Release Guide 2003 - Final edition - February 2003ii

SWIFTStandards - Category 9Table Of Contents

................ 65MT 960 Request for Service Initiation Message

....................... 65MT 960 Scope



...................... 65MT 960 Guidelines


................ 651. Field 20: Transaction Reference Number

..................... 662. Field 79: Narrative

................ 663. Field 91A: Request for Service Initiation

................... 67MT 961 Initiation Response Message

....................... 67MT 961 Scope






................. 683. Field 91B: Response Service Message

.................... 69MT 962 Key Service Message

....................... 69MT 962 Scope






.................. 703. Field 91C: Key Service Message

.................. 71MT 963 Key Acknowledgement Message

....................... 71MT 963 Scope






................. 723. Field 91D: Response Service Message

...................... 73MT 964 Error Message

....................... 73MT 964 Scope






................. 743. Field 79: Additional Error Comments

................. 754. Field 91E: Error on RSI, RSM or DSM

.................. 76MT 965 Error in Key Service Message

....................... 76MT 965 Scope






................. 773. Field 79: Additional Error Comments

.................... 784. Field 91F: Error on KSM

................... 79MT 966 Discontinue Service Message

....................... 79MT 966 Scope





.................. 802. Field 79: Additional Comments

................ 803. Field 91G: Discontinue Service Message

............... 81MT 967 Discontinuation Acknowledgement Message

....................... 81MT 967 Scope


iiiStandards Release Guide 2003 - Final edition - February 2003






.................. 823. Field 79: Additional Comments

................. 834. Field 91H: Response Service Message

..................... 84MT 970 Netting Statement

....................... 84MT 970 Scope



...................... 85MT 970 Usage Rules







................... 906. Field 62a: Closing Balance

................. 917. Field 64: Closing Available Balance

.................... 92MT 971 Netting Balance Report

....................... 92MT 971 Scope






.................. 933. Field 62F: Final Closing Balance

................... 95MT 972 Netting Interim Statement

....................... 95MT 972 Scope



...................... 96MT 972 Usage Rules







................... 1016. Field 62a: Closing Balance

................. 1027. Field 64: Closing Available Balance

................... 104MT 973 Netting Request Message

....................... 104MT 973 Scope





.................... 1052. Field 12: Message Type


...................... 106MT 985 Status Enquiry

....................... 106MT 985 Scope



.................. 106MT 985 Field Specifications (updated)


............... 1072. Field 57a: Account With Institution (updated)

.................... 1073. Field 59: Enquired Party

...................... 1074. Field 75: Queries

...................... 109MT 986 Status Report

....................... 109MT 986 Scope




Standards Release Guide 2003 - Final edition - February 2003iv

SWIFTStandards - Category 9Table Of Contents



.................... 1103. Field 59: Enquired Party

..................... 1104. Field 79: Narrative

.............. 112MT 990 Advice of Charges, Interest and Other Adjustments

........... 113MT 991 Request for Payment of Charges, Interest and Other Expenses

.................... 114MT 992 Request for Cancellation

....................... 115MT 995 Queries

....................... 116MT 996 Answers

..................... 117MT 998 Proprietary Message

.................... 118MT 999 Free Format Message

vStandards Release Guide 2003 - Final edition - February 2003


swiftstandards - category 9 - cash management & customer ... · pdf fileswiftstandards...

Documents