Sunteți pe pagina 1din 125

SWIFTStandards

Category 6
Treasury Markets - Precious Metals
For SWIFTStandards MT October 2007

Message Reference Guide


Standards Release Guide - February 2007
This reference guide contains the category 6, precious metals, message text standards, including a detailed description of the
scope, the format specifications, the rules, the guidelines, and the field specifications of each message type .
5 February 2007

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Copyright
Copyright S.W.I.F.T. SCRL ("SWIFT"), avenue Adle 1, B-1310 La Hulpe, Belgium, or its licensors, 2007 .
All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal
notices.
Confidentiality
This publication may contain SWIFT or third-party confidential information. Do not disclose this publication outside your
organisation without the prior written consent of SWIFT.
Disclaimer
The information in this publication may change from time to time. You must always refer to the latest available version.
SWIFTStandards Intellectual Property Rights (IPR) Policy - End-User License Agreement
SWIFTStandards are licensed subject to the terms and conditions of the SWIFTStandards IPR Policy - End-User License
Agreement, available at www.swift.com > Standards > More information.
Translations
The English version of SWIFT documentation is the only official version.
Trademarks and Patents
SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady, and Accord are
trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived service and product names, including SWIFTSolutions, SWIFTWatch, and SWIFTSupport are tradenames of S.W.I.F.T. SCRL.
SWIFT is the trading name of S.W.I.F.T. SCRL .
Other product or company names in this publication are tradenames, trademarks, or registered trademarks of their respective
owners.
5 February 2007

Message Reference Guide - Standards Release Guide - February 2007

Introduction

Introduction
Summary of Changes
Added Message Types
n.a.

Removed Message Types


n.a.

Modified Message Types


MT 600
MT 601

5 February 2007

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Category 6 Precious Metals Message Types


The following table lists all message types defined in category 6 Precious Metals.
For each message type, there is a short description, an indicator whether the message type requires authentication (Y or N),
the maximum message length for input (2,000 or 10,000 characters) and whether the use of the message requires registration
with SWIFT for use in a message user group (Y or N).
MT

MT Name

Purpose

Authen.

Max.
Length

MUG

600

Precious Metal Trade


Confirmation

Confirms the details of a precious metal


trade and its settlement

2,000

601

Precious Metal Option


Confirmation

Confirms the details of a precious metal


option contract

2,000

604

Precious Metal Transfer/Delivery Order

Instructs the Receiver to transfer by


book-entry, or physically deliver, a specified type and quantity of precious metal
to a specified party

2,000

605

Precious Metal Notice to


Receive

Notifies the Receiver of an impending


book-entry transfer or physical delivery
of a specified type and quantity of
precious metal

2,000

606

Precious Metal Debit


Advice

Advises the Receiver of a debit entry to a


specified metal account

2,000

607

Precious Metal Credit


Advice

Advises the Receiver of a credit entry to


a specified metal account

2,000

608

Statement of a Metal
Account

Provides the details of all bookings to a


metal account

2,000

609

Statement of Metal
Contracts

Identifies all outstanding metal contracts,


as at a specified date for which confirmations have been exchanged

2,000

690

Advice of Charges, Interest and Other Adjustments

Advises an Account Owner of charges,


interest or other adjustments to its
account

2,000

691

Request for Payment of


Charges, Interest or
Other Expenses

Requests payment of charges, interest


and other expenses

2,000

692

Request for Cancellation

Requests the Receiver to consider


cancellation of the message identified in
the request

2,000

695

Queries

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


message

2,000

Message Reference Guide - Standards Release Guide - February 2007

Category 6 Precious Metals Message Types

MT

MT Name

Purpose

Authen.

Max.
Length

MUG

696

Answers

Responds to a MT 695 Queries message


or MT 692 Request for Cancellation or
other messages where no specific
message type has been provided for the
response

2,000

698

Proprietary Message

Contains formats defined and agreed to


between users and for those messages
not yet live

10,000

699

Free Format Message

Contains information for which no other


message type has been defined

2,000

Note:

A Message User Group (MUG), for the purposes of this book, is a group of users who have voluntarily agreed to support the specified message type and have registered with SWIFT to send or
receive the specified message type. These messages are indicated in the preceding table in the
column MUG.
Registration is free of charge. To register to use one or more message types, submit a registration
request (Register to a Message User Group) through www.swift.com. To withdraw from a
MUG, use the Deregister from a Message User Group request.
These forms are available on www.swift.com > Ordering & Support > Ordering.
To get the list of other members of a particular MUG, send an MT 999 to the Customer Implementation team (SWHQBEBBCOS).

5 February 2007

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Euro - Impact on Category Message Standards


See the SWIFTStandards General Information volume for full details of the Euro-Related Information (ERI) and the impact
on SWIFTStandards FIN message types.

Message Reference Guide - Standards Release Guide - February 2007

MT 600

MT 600 Precious Metal Trade Confirmation


MT 600 Scope
This message type is exchanged by or on behalf of the institutions or corporates, party A and party B, which have agreed to
a precious metal trade. This message is also used when one of the trading parties is a fund manager.
This message type is exchanged between the financial institutions which have agreed to a precious metal trade.
It is used to confirm the details of:
a new contract between the parties
an amendment to a previously agreed contract
the cancellation of a contract
the settlement of a metal option which has been exercised.
This message may also be exchanged to confirm the liquidation of a forward deal.
In some cases, only one of the financial institutions involved in a contract will send a confirmation to the second financial
institution. These cases include:
retransmission due to errors in a previously sent confirmation
additional information about a previously confirmed contract, (eg, to provide the name of the party in field 57a and/or
87a, in those cases where the previous confirmation contained the code UNKNOWN).

MT 600 Format Specifications


The format contains three sequences:
Sequence A provides the details of the precious metal contract.
Sequence B provides the settlement information in those cases where the Sender has bought the metal.
Sequence C provides the settlement information in those cases where the Sender has sold the metal.
MT 600 Precious Metal Trade Confirmation
Status

Tag

Field Name

Content/Options

No.

Mandatory Sequence A Details of the Contract


M

15A

20

New Sequence

(CrLf)

Transaction Reference Number

16x

1
2
1

21

Related Reference

16x

3
2

22

Code/Common Reference

8a/4!a2!c4!n4!a2!c

4
3

94A

Scope of Operation

4!c

82a

Party A

A, D or J

87a

Party B

A, D or J

5 February 2007

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Status

Tag

Field Name

Content/Options

83a

Fund or Beneficiary Customer

A, D or J

30

Date Contract Agreed/Amended

6!n

No.
8
9
4

26C

Identification of the Metal

[3!a]/15x/5!a4!a[4x][//8x]
10 5

26H

Counterpartys Reference

16x
11

33G

Price per Unit

3!a15d[5!c]
12 6

71C

Details of Adjustments

6*35x
13 7

72

Sender to Receiver Information

6*35x
14 8

Optional Sequence B Precious Metal Bought


M

15B

New Sequence

(CrLf)
15

32F

Quantity of the Metal

3!a15d
16 9

86a

Intermediary

A, B or D
17

87a

Receiver of the Metal

A, B or D
18
10

34P

Consideration

6!n3!a15d
19
11

53a

Senders Correspondent

A, B or D
20
12

56a

Intermediary

A, B or D
21

57a

Account With Institution

A, B or D
22
13

Optional Sequence C Precious Metal Sold

Message Reference Guide - Standards Release Guide - February 2007

MT 600

Status

Tag

15C

Field Name
New Sequence

Content/Options

No.

(CrLF)
23

32F

Quantity of the Metal

3!a15d
24
14

86a

Intermediary

A, B or D
25

87a

Deliverer of the Metal

A, B or D
26
15

34R

Consideration

6!n3!a15d
27
16

56a

Intermediary

A, B or D
28

57a

Account With Institution

A, B or D
29
17
M = Mandatory O = Optional

MT 600 Network Validated Rules


C1
Either sequence B or sequence C, but not both, must be present (Error code(s): C93).
C2
In the optional sequences, all fields with status M must be present (Error code(s): C32).
C3
The currency in the amount fields 33G and 34P or 34R must be the same for all occurrences of these fields in the
message (Error code(s): C02).

MT 600 Usage Rules


Changes to the quantity of metal, and/or price per unit, and/or consideration and/or settlement instructions require
another confirmation.
This message handles only the contract part of a precious metal trade.
The actual transfer/delivery of metal is handled through the MT 604 Precious Metal Transfer/Delivery Order and the
confirmation of debits or credits is handled through the MT 606 Precious Metal Debit Advice/MT 607 Precious Metal
Credit Advice/MT 608 Statement of a Metal Account. In all cases, the common reference of the MT 600 must be
quoted in the relevant reference field (ie, field 21 of the MT 604/606/607 or field 61, subfield 7 of the MT 608).

5 February 2007

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

The actual transfer of funds (ie, the consideration) is handled through the financial institution transfer messages
(MT 202/203/205) and the confirmation of debits or credits is handled through the MT 900/910/950. In all cases, the
common reference of the MT 600 must be quoted in the relevant reference field (ie, field 21 of the
MT 202/203/205/910 or field 61, subfield 7 of the MT 950).

MT 600 Field Specifications


1. Field 15A: New Sequence
FORMAT
Option A

Empty field

PRESENCE
Mandatory
DEFINITION
This field specifies the start of mandatory sequence A Details of the Contract.
USAGE RULES
Only the field tag must be present, the field is empty.

2. Field 20: Transaction Reference Number


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal deal.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

3. Field 21: Related Reference


FORMAT
16x

10

Message Reference Guide - Standards Release Guide - February 2007

MT 600

PRESENCE
Mandatory
DEFINITION
This field specifies the related reference to the precious metal deal.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).
USAGE RULES
In a new contract, this field must contain the code NEW.
Where field 22 contains the code EXOPTION, this field must contain the field 20 Transaction Reference Number of the
related MT 601 Precious Metal Option Confirmation.
In all other cases, this field should contain the field 20 Transaction Reference Number of the previous MT 600. The content
of field 21, when other than NEW, will normally be a reference meaningful to the Sender rather than the Receiver. This is
the case because the Sender will normally include the content of field 20 from the MT 600 or MT 601 previously transmitted rather than received.

4. Field 22: Code/Common Reference


FORMAT
8a/4!a2!c4!n4!a2!c

(Code) (Common Reference)

PRESENCE
Mandatory
DEFINITION
This field identifies the function of the message and contains a reference of the contract common to both the Sender and
Receiver.
CODES
In confirmations sent by both financial institutions, Code must contain one of the following codes:
AMEND

Confirmation of mutually agreed changes to the quantity of metal, and/or price per unit, and/or
consideration and/or settlement instructions of a contract for which a confirmation has been
previously sent.

CANCEL

Confirmation of the mutually agreed cancellation of a contract.

EXOPTION

Confirmation of the mutually agreed settlement of a precious metal option which has been
exercised.

NEW

Confirmation of a new contract.

NOTICE

Liquidation notice for a forward deal. A notice is optional; its use is dependent on internal
practices.

5 February 2007

11

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

CODES
In confirmations sent by one financial institution, Code must contain one of the following codes:
COMPLETE

Complementary Information - used to advise for the first time the name of the financial institution in fields 53a, 57a and/or 87a (eg, in those cases where the previous confirmation
contained the code word UNKNOWN in field 57a).

CORRECT

Retransmission due to error - sent to correct error(s) in a previously sent MT 600.

NETWORK VALIDATED RULES


Common Reference must contain the bank and location codes of the Sender and Receiver, ie, their BIC without the country
code (Error code(s): T95). These codes must appear in alphabetical order, with letters taking precedence over numbers
(Error code(s): T96).
The codes are separated by four digits, which must consist of the rightmost non-zero digits of the price per unit (ie, Price Per
Unit of field 33G) (Error code(s): T22), preceded by the three digits to the left of it. If there are no digits to the left of it, the
space must be zero-filled.

5. Field 94A: Scope of Operation


FORMAT
Option A

4!c

(Scope)

PRESENCE
Optional
DEFINITION
This field specifies the role of the Sender and the Receiver of the message in the execution of the confirmed trade.
CODES
One of the following codes must be used(Error code(s): T36)
AGNT

Sender/Receiver is sending/receiving the message on behalf of a third party.

BILA

Bilateral confirmation, ie, the Sender and the Receiver are the principals.

BROK

The confirmation is sent by a money broker.

USAGE RULES
The absence of this field means that the Sender and the Receiver are principals, ie, Scope is BILA.
AGNT is used when the confirmation has been sent or received on behalf of a separate legal party and that party has done
the deal.

12

Message Reference Guide - Standards Release Guide - February 2007

MT 600

6. Field 82a: Party A


FORMAT
Option A

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

Option D
Option J

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

PRESENCE
Mandatory
DEFINITION
This field identifies party A.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

M = Mandatory O = Optional

NETWORK VALIDATED RULES


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

5 February 2007

13

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

USAGE RULES
For matching purposes, option A must be used when available.
Party A is either the sender :94A:BILA, or, the institution or corporate on whose behalf the message is sent :94A:AGNT,
except when the Sender is a money broker :94A:BROK.
When the Sender is a fund manager, the fund manager is specified in this field.
Please refer to the chapter Scope for this MT.

7. Field 87a: Party B


FORMAT
Option A

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

Option D
Option J

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

PRESENCE
Mandatory
DEFINITION
This field identifies party B.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

14

Message Reference Guide - Standards Release Guide - February 2007

MT 600

M = Mandatory O = Optional

NETWORK VALIDATED RULES


The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
USAGE RULES
For matching purposes, option A must be used when available.
Party B is either the Receiver :94A:BILA, or, the institution or corporate on whose behalf the message is received
:94A:AGNT, except when the Sender is a money broker :94A:BROK.
When the Receiver is a fund manager, the fund manager is specified in this field.
Please refer to the chapter Scope for this MT.

8. Field 83a: Fund or Beneficiary Customer


FORMAT
Option A

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

Option D
Option J

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

PRESENCE
Optional
DEFINITION
This field specifies the fund or beneficiary customer.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

5 February 2007

15

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

M = Mandatory O = Optional

NETWORK VALIDATED RULES


The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
USAGE RULES
For matching purposes, option A must be used when available.
When the message is sent or received by a fund manager, this field specifies the fund. The fund manager is specified respectively in either field 82a or field 87a.

9. Field 30: Date Contract Agreed/Amended


FORMAT
6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field contains the date when the contract or amendment to it (eg, code AMEND in field 22) was agreed between the
dealers.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
When CORRECT or COMPLETE is present in field 22, this field specifies the date of the contract or amendment to which
this message refers.

10. Field 26C: Identification of the Metal


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

Where

16

Message Reference Guide - Standards Release Guide - February 2007

MT 600

Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the precious metal bought or sold.
CODES
When Delivery Details is present, it must contain the code CIF (Error code(s): T35).
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04):
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

5 February 2007

17

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

18

1/10

Message Reference Guide - Standards Release Guide - February 2007

MT 600

Code

Coin Name

Denomination

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

USAGE RULES
Delivery Details is used only if CIF (ie, Cost, Insurance, Freight) applies. If this subfield is not present, then LOCO applies.
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

11. Field 26H: Counterpartys Reference


FORMAT
Option H

16x

PRESENCE
Optional
DEFINITION
This field specifies the counterpartys reference, if known.

12. Field 33G: Price Per Unit


FORMAT
Option G

3!a15d[5!c]

(Currency) (Price) (Code)

PRESENCE
Mandatory
DEFINITION
This field specifies the currency and amount of the price per unit of the agreement and optionally a code indicating a unit of
metal different from that specified in field 32F.
CODES
Code must contain the following code (Error code(s): T07):
SEE72

5 February 2007

Indicates that more information can be found in field 72

19

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Price must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).
USAGE RULES
When the price per unit of the agreement is based on a unit different from the unit specified in field 32F Quantity of the
Metal, Price must be converted based on the unit used in field 32F, and the code SEE72 must appear in Code (ie, [5!c]) with
the conversion explained in field 72.
The number of digits following the decimal comma will not be validated.

13. Field 71C: Details of Adjustments


FORMAT
Option C

6*35x

(Narrative)

which may be structured as:


Line 1
Lines 2-6

/4c/29x
35x

(Code) (Narrative)
(Narrative)

PRESENCE
Optional
DEFINITION
This field specifies details of adjustments, eg, commission to the price stated in field 33G, if applicable.
CODES
Code may contain one or more of the following codes:
BROK

Brokerage.

CHGS

Charges.

COMM

Commission.

FEES

Fees.

MISC

Miscellaneous.

POST

Postage.

SHIN

Shipping including insurance.

STMP

Stamp Duty.

20

Message Reference Guide - Standards Release Guide - February 2007

MT 600

TTAX

Transaction tax.

VTAX

Value added tax.

WITX

Withholding tax.

USAGE RULES
All adjustments must be expressed in the same currency as the amounts stated in fields 33G and 34P or 34R.

14. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code word can be
followed by an indication of the specific electronic means used for arranging the deal.

INTERMDY

Specifies the intermediary institution for the settlement of the metal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

5 February 2007

21

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

15. Field 15B: New Sequence


FORMAT
Option B

Empty field

PRESENCE
Mandatory in a Conditional Sequence (C1).
DEFINITION
This field specifies the start of optional sequence B Precious Metal Bought.
USAGE RULES
This field may only be used when at least one other field in the optional sequence B is present and is otherwise not allowed.
Only the field tag must be present, the field is empty.

16. Field 32F: Quantity of the Metal


FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field specifies the type of unit and the quantity of the precious metal bought by the Sender.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

22

Message Reference Guide - Standards Release Guide - February 2007

MT 600

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

17. Field 86a: Intermediary


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the intermediary institution for the delivery of the metal bought.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
For matching purposes, option A must be used when available.

18. Field 87a: Receiver of the Metal


FORMAT
Option A
Option B

5 February 2007

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

(Party Identifier)
(BIC)
(Party Identifier)
(Location)

23

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Option D

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

(Party Identifier)
(Name & Address)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field identifies the party at which the Sender will receive the metal bought.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
When the Receiver services a metal account (ie, an account for the metal specified in field 26C) for the Sender, and this
account is to be credited, option A should be used and the field must contain the Receivers BIC.
When the Sender services a metal account (ie, an account for the metal specified in field 26C) for the Receiver and this
account is to be debited, option A should be used and the field must contain the Senders BIC.
In forward contracts, if the receiver of the metal is not known, the code UNKNOWN must appear in this field, using option
D.

19. Field 34P: Consideration


FORMAT
Option P

6!n3!a15d

(Date) (Currency) (Amount)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field specifies the value date, currency code and the consideration paid by the Sender.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length. The number of digits following the comma must not exceed the maximum allowed for that specified
currency (Error code(s): C03,T40,T43).

24

Message Reference Guide - Standards Release Guide - February 2007

MT 600

USAGE RULES
The consideration is calculated by multiplying the quantity of metal (ie, the amount stated in field 32F) by the price per unit
(ie, the amount stated in field 33G), and, if applicable, adjusted for any amounts stated in field 71C.

20. Field 53a: Senders Correspondent


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the financial institution from which the Sender will transfer the funds specified in field 34P.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

21. Field 56a: Intermediary


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field specifies the intermediary institution for the transfer of the funds specified in field 34P.

5 February 2007

25

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
For matching purposes, option A must be used when available.

22. Field 57a: Account With Institution


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field identifies the financial institution and account where the Receiver wants to receive the funds specified in field
34P.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
When the optional Party Identifier is present, it identifies the account which is to be debited or credited on the books of the
account with institution which is specified.
When the Sender services an account for the Receiver in the relevant currency, and this account is to be credited, option A
should be used and the field must contain the Senders BIC.
When the Receiver services an account for the Sender in the relevant currency, and this account is to be debited, option A
should be used and the field must contain the Receivers BIC.
In forward contracts, if the account with institution is not known, the code UNKNOWN must appear in this field, using
option D.

26

Message Reference Guide - Standards Release Guide - February 2007

MT 600

23. Field 15C: New Sequence


FORMAT
Option C

Empty field

PRESENCE
Mandatory in a Conditional Sequence (C1).
DEFINITION
This field specifies the start of optional sequence C Precious metal Sold
USAGE RULES
This field may only be used when at least one other field in the optional sequence C is present and is otherwise not allowed.
Only the field tag must be present, the field is empty.

24. Field 32F: Quantity of the Metal


FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field specifies the type of unit and the quantity of the precious metal sold by the Sender.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

5 February 2007

27

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

25. Field 86a: Intermediary


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field specifies the intermediary institution for the transfer of the metal sold.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
For matching purposes, option A must be used when available.

26. Field 87a: Deliverer of the Metal


FORMAT
Option A
Option B
Option D

28

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

Message Reference Guide - Standards Release Guide - February 2007

MT 600

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field identifies the party to which the Sender will deliver the metal sold.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
When the Sender services a metal account (ie, an account for the metal specified in field 26C) for the Receiver, and this
account is to be credited, option A should be used and the field must contain the Senders BIC.
When the Receiver services a metal account (ie, an account for the metal specified in field 26C) for the Sender and this
account is to be debited, option A should be used and the field must contain the Receivers SWIFT BIC.
In forward contracts, if the deliverer of the metal is not known, the code UNKNOWN must appear in this field, using option
D.

27. Field 34R: Consideration


FORMAT
Option R

6!n3!a15d

(Date) (Currency) (Amount)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field specifies the value date, currency code and the consideration received by the Sender.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length. The number of digits following the comma must not exceed the maximum allowed for that specified
currency (Error code(s): C03,T40,T43).
USAGE RULES
The consideration is calculated by multiplying the quantity of metal (ie, the amount stated in field 32F) by the price per unit
(ie, the amount stated in field 33G), and, if applicable, adjusted for any amounts stated in field 71C.

5 February 2007

29

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

28. Field 56a: Intermediary


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field specifies the intermediary institution for the transfer of the funds specified in field 34R.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
For matching purposes, option A must be used when available.

29. Field 57a: Account With Institution


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Mandatory in an optional sequence
DEFINITION
This field identifies the financial institution and account at which the Sender wishes to receive the funds specified in field
34R.

30

Message Reference Guide - Standards Release Guide - February 2007

MT 600

NETWORK VALIDATED RULES


The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
When the optional Party Identifier is present, it identifies the account which is to be debited or credited on the books of the
account with institution which is specified.
When the Receiver services an account for the Sender in the relevant currency, and this account is to be credited, option A
should be used and the field must contain the Receivers BIC.
When the Sender services an account for the Receiver in the relevant currency, and this account is to be debited, option A
should be used and the field must contain the Senders BIC.
In forward contracts, if the account with institution is not known, the code UNKNOWN must appear in this field, using
option D.

5 February 2007

31

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 601 Precious Metal Option Confirmation


MT 601 Scope
This message type is exchanged by or on behalf of the institutions or corporates, party A and party B, which have agreed to
a precious metal option contract. This message is also used when one of the parties is a fund manager.
This message type is exchanged between the financial institutions which have agreed to a precious metal option contract.
It is used to confirm the details of
a new contract between the parties
an amendment to a previously agreed contract
the cancellation of a contract
the surrender of an option by the buyer (holder) to the seller (grantor) for compensation.
In some cases, only one of the financial institutions involved in a contract will send a confirmation to the second financial
institution. These cases include:
retransmission due to errors in a previously sent confirmation
additional information about a previously confirmed contract.

MT 601 Format Specifications


MT 601 Precious Metal Option Confirmation
Status

Tag

Field Name

Content/Options

No.

20

Transaction Reference Number

16x

21

Related Reference

16x

22

Code/Common Reference

8a/4!a2!c4!n4!a2!c

94A

Scope of Operation

4!c

82a

Party A

A, D or J

87a

Party B

A, D or J

83a

Fund or Beneficiary Customer

A, D or J

23

Further Identification

16x

8
4

30

Date Contract Agreed/Amended

6!n

9
5

26C

Identification of the Metal

[3!a]/15x/5!a4!a[4x][//8x]
10 6

31C

Earliest Exercise Date

6!n
11 7

32

Message Reference Guide - Standards Release Guide - February 2007

MT 601

Status

Tag

31G

Field Name
Expiry Details

Content/Options

No.

6!n/4!n/12a
12 8

32F

Unit and Amount of the Metal

3!a15d
13 9

32B

Strike Price

3!a15d
14
10

33B

Premium Price

3!a15d
15
11

34a

Premium Payment

P or R
16
12

53a

Senders Correspondent

A, B or D
17
13

56a

Intermediary

A, B or D
18

57a

Account With Institution

A, B or D
19
14

72

Sender to Receiver Information

6*35x
20
15

M = Mandatory O = Optional

MT 601 Network Validated Rules


C1
Field 53a may only be present if field 34P is used (Error code(s): C20).
C2
Field 31C may only be present in the case of an American style option (ie, subfield 3 of field 23 contains A) (Error
code(s): C79).
C3
The currency in the amount fields 32B and 34a must be the same (Error code(s): C02).

5 February 2007

33

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 601 Usage Rules


Changes to the quantity of the metal, and/or strike price, and/or premium price, and/or exercise date, and/or settlement
instructions require another confirmation .
This message type handles only the contract part of the precious metal option .
In those cases where the message is exchanged to confirm a new contract, or an amendment, cancellation or close out
of a previously agreed contract, the content of the confirmations should be identical, and is used to confirm information
already known to the two parties. Careful verification of the exchanged messages is, of course, required.
A precious metal option may be exercised by the buyer. To confirm the settlement of the exercise of a precious metal
option, an MT 600 Precious Metal Trade Confirmation may be used, with the function code EXOPTION in field 22
and field 21 containing the TRN of the related MT 601.

MT 601 Field Specifications


1. Field 20: Transaction Reference Number
FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal deal.
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 specifies the related reference to the precious metal deal.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

34

Message Reference Guide - Standards Release Guide - February 2007

MT 601

USAGE RULES
When this message is a confirmation of a new contract, the code NEW must be used.
In all other cases, this field must contain the field 20 TRN of the previous MT 601.
The content of field 21, when other than NEW, will normally be a reference meaningful to the Sender rather than the
Receiver. This is because the Sender will normally include the content of field 20 from the MT 601 previously transmitted
rather than received.

3. Field 22: Code/Common Reference


FORMAT
8a/4!a2!c4!n4!a2!c

(Code) (Common Reference)

PRESENCE
Mandatory
DEFINITION
This field identifies the function of the message and contains the reference of the contract common to both the Sender and
Receiver.
CODES
In confirmations sent by both financial institutions, Code must contain one of the following codes:
AMEND

Confirmation of mutually agreed changes to the quantity of the metal, and/or strike price,
and/or premium price and/or exercise date and/or settlement information of the contract for
which a confirmation message has been previously sent.

CANCEL

Confirmation of the mutually agreed cancellation of a contract.

CLOSEOUT

Confirmation of the mutually agreed surrender of the option by the buyer (holder) to the seller
(grantor) for compensation.

NEW

Confirmation of a new precious metal option.

CODES
In confirmations sent by one financial institution, Code must contain one of the following codes:
COMPLETE

Complementary information - used to advise for the first time the name of the financial institution in field 53a and/or 57a (eg, in those cases where the previous confirmation contained the
code UNKNOWN in field 57a).

CORRECT

Retransmission due to error - to correct error(s) in a previously sent MT 601.

5 February 2007

35

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


Common Reference must contain the bank and location codes of the Sender and Receiver, ie, their BIC without the country
code (Error code(s): T95). These codes must appear in alphabetical order, with letters taking precedence over numbers
(Error code(s): T96).
The codes are separated by four digits, which must consist of the rightmost non-zero digits of the strike price specified in
field 32B (Error code(s): T22), preceded by the three digits to the left of it. If there are no digits to the left of it, the space
must be zero-filled.

4. Field 94A: Scope of Operation


FORMAT
Option A

4!c

(Scope)

PRESENCE
Optional
DEFINITION
This field specifies the role of the Sender and the Receiver of the message in the execution of the confirmed trade.
CODES
One of the following codes must be used(Error code(s): T36)
AGNT

Sender/Receiver is sending/receiving the message on behalf of a third party.

BILA

Bilateral confirmation, ie, the Sender and the Receiver are the principals.

BROK

The confirmation is sent by a money broker.

USAGE RULES
The absence of this field means that the Sender and the Receiver are principals, ie, Scope is BILA.
AGNT is used when the confirmation has been sent or received on behalf of a separate legal party and that party has done
the deal.

5. Field 82a: Party A


FORMAT
Option A
Option D
Option J

36

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

Message Reference Guide - Standards Release Guide - February 2007

MT 601

PRESENCE
Mandatory
DEFINITION
This field identifies party A.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

M = Mandatory O = Optional

NETWORK VALIDATED RULES


The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
USAGE RULES
For matching purposes, option A must be used when available.
Party A is either the sender :94A:BILA, or, the institution or corporate on whose behalf the message is sent :94A:AGNT,
except when the Sender is a money broker :94A:BROK.
When the Sender is a fund manager, the fund manager is specified in this field.
Please refer to the chapter Scope for this MT.

5 February 2007

37

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

6. Field 87a: Party B


FORMAT
Option A

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

Option D
Option J

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

PRESENCE
Mandatory
DEFINITION
This field identifies party B.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

M = Mandatory O = Optional

NETWORK VALIDATED RULES


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

38

Message Reference Guide - Standards Release Guide - February 2007

MT 601

USAGE RULES
For matching purposes, option A must be used when available.
Party B is either the Receiver :94A:BILA, or, the institution or corporate on whose behalf the message is received
:94A:AGNT, except when the Sender is a money broker :94A:BROK.
When the Receiver is a fund manager, the fund manager is specified in this field.
Please refer to the chapter Scope for this MT.

7. Field 83a: Fund or Beneficiary Customer


FORMAT
Option A

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x
5*40x

Option D
Option J

(Party Identifier)
(BIC/BEI)
(Party Identifier)
(Name & Address)
(Party Identification)

PRESENCE
Optional
DEFINITION
This field specifies the fund or beneficiary customer.
CODES
With option J, the following codes must be used (Error code(s): T78):
/ABIC/

followed by the BIC/BEI or UKWN if


BIC/BEI not known

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

/ACCT/

followed by the account number

34x

/ADD1/

followed by the first line of the address

35x

/ADD2/

followed by the second line of the address

35x

/CITY/

followed by the city (and state, country)

35x

/CLRC/

followed by a clearing code

35x

/GBSC/

followed by UK domestic sort code

6!n

/NAME/

followed by the name

34x

/USCH/

followed by CHIPS UID

6!n

/USFW/

followed by FedWire Routing Number

9!n

5 February 2007

39

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

M = Mandatory O = Optional

NETWORK VALIDATED RULES


The BIC/BEI must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
USAGE RULES
For matching purposes, option A must be used when available.
When the message is sent or received by a fund manager, this field specifies the fund. The fund manager is specified respectively in either field 82a or field 87a.

8. Field 23: Further Identification


FORMAT
16x

to be formatted as 4a/4a/1!a, where:


4a
/4a
/1!a

Buy/Sell Indicator
Call/Put Indicator
Style Indicator

PRESENCE
Mandatory
DEFINITION
This field specifies whether, from the Senders point of view, the option is sold or bought, is a put or a call, and indicates the
style.
CODES
Buy/Sell Indicator must contain one of the following codes:
BUY

The Sender is confirming an option bought

SELL

The Sender is confirming an option sold

CODES
Call/Put Indicator must contain one of the following codes:
CALL

The Sender is confirming a call option

PUT

The Sender is confirming a put option

40

Message Reference Guide - Standards Release Guide - February 2007

MT 601

CODES
Style Indicator must contain one of the following codes (Error code(s): T09):
A

This is an American style option

This is a European style option

9. Field 30: Date Contract Agreed/Amended


FORMAT
6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field contains the date when the contract or amendment to it (eg, code AMEND in field 22) was agreed between the
dealers.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
When CORRECT or COMPLETE is present in field 22, this field specifies the date of the contract or amendment to which
this message refers.

10. Field 26C: Identification of the Metal


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

Where
Subfield

Format

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

5 February 2007

Name

41

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Subfield

Format

Name

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field specifies the underlying precious metal of the option contract.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:

42

Message Reference Guide - Standards Release Guide - February 2007

MT 601

Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

5 February 2007

1/10

43

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

11. Field 31C: Earliest Exercise Date


FORMAT
Option C

6!n

(Date)

PRESENCE
Conditional (C2)
DEFINITION
This field is used in an American style option to specify the earliest date the exercise of the option may be requested.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

12. Field 31G: Expiry Details


FORMAT
Option G

6!n/4!n/12a

(Date) (Time) (Location)

PRESENCE
Mandatory
DEFINITION
This field specifies the date, time and location at which the option expires.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Time must be a valid time expressed as HHMM (Error code(s): T38).

13. Field 32F: Unit and Amount of the Metal

44

Message Reference Guide - Standards Release Guide - February 2007

MT 601

FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory
DEFINITION
This field specifies the type of unit and the quantity of the underlying metal.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

14. Field 32B: Strike Price


FORMAT
Option B

3!a15d

(Currency) (Price)

PRESENCE
Mandatory

5 February 2007

45

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

DEFINITION
This field specifies the currency code and the strike price per unit of the underlying metal.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Price must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).
USAGE RULES
The number of digits in Price following the decimal comma will not be validated.

15. Field 33B: Premium Price


FORMAT
Option B

3!a15d

(Currency) (Price)

PRESENCE
Mandatory
DEFINITION
This field specifies the currency code and amount of the premium price per unit of the underlying metal .
NETWORK VALIDATED RULES
If not PCT, Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Price must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).
USAGE RULES
The number of digits following the decimal comma in the Price will not be validated .

16. Field 34a: Premium Payment


FORMAT
Option P
Option R

6!n3!a15d
6!n3!a15d

(Date) (Currency) (Amount)


(Date) (Currency) (Amount)

PRESENCE
Mandatory

46

Message Reference Guide - Standards Release Guide - February 2007

MT 601

DEFINITION
This field specifies the value date, currency code and premium amount which the buyer pays to the seller for the option.
The letter option indicates, from the Senders point of view, the direction of the payment of the premium.
P = Paid, ie, the Sender pays the premium.
R = Received, ie, the Sender receives the premium.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length. The number of digits following the comma must not exceed the maximum number allowed for the specified currency (Error code(s): C03,T40,T43).

17. Field 53a: Senders Correspondent


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Conditional (C1)
DEFINITION
This field identifies the financial institution from which the Sender will transfer the premium amount specified in field 34P
to the financial institution specified in field 57a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

18. Field 56a: Intermediary


FORMAT
Option A
Option B

5 February 2007

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

(Party Identifier)
(BIC)
(Party Identifier)
(Location)

47

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Option D

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

(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field specifies the intermediary institution for the transfer of the premium.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
USAGE RULES
For matching purposes, option A must be used when available.

19. Field 57a: Account With Institution


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Mandatory
DEFINITION
This field identifies the financial institution and account where the receiver of the premium wishes to receive the amount
specified in field 34a .
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

48

Message Reference Guide - Standards Release Guide - February 2007

MT 601

USAGE RULES
When the optional Party Identifier is present, it identifies the account which is to be debited or credited on the books of the
account with institution which is specified.
When the receiver of the premium services an account in the relevant currency for the payer of the premium, and this
account is to be debited, option A should be used and the field must contain the BIC of the receiver of the premium.
When the payer of the premium services an account in the relevant currency for the receiver of the premium, and this
account is to be credited, option A should be used and the field must contain the BIC of the payer of the premium.
If the account with institution is not known, the code UNKNOWN must appear in this field, using option D.

20. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code word can be followed by an
indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

5 February 2007

49

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

50

Message Reference Guide - Standards Release Guide - February 2007

MT 604

MT 604 Precious Metal Transfer/Delivery Order


MT 604 Scope
This message is sent by the owner of a metal account or its authorised agent to the metal account servicing institution.
It is used to instruct the Receiver to transfer by book entry, or physically deliver, specified quantities of allocated or unallocated precious metal to a specified party.

MT 604 Format Specifications


MT 604 Precious Metal Transfer/Delivery Order
Status

Tag

26C

Field Name

Content/Options

No.

Identification of the Metal and the Metal Account

[3!a]/15x/5!a4!a[4x][//8x]

25

Further Account Identification

35x

30

Value Date

6!n

72

Sender to Receiver Information

6*35x

20

Transaction Reference Number

16x

21

Related Reference

16x

23

Further Identification

16x

26D

Certificate Number(s) and/or Bar Number(s)

30*65x

32F

Quantity of the Metal

3!a15d

82a

Instructing Party

A, B or D

----->

10
O

86a

Intermediary

A, B or D
11

87a

Receiver of the Metal

A, B or D
12

88a

Beneficiary of the Metal

A, B or D
13

72

Sender to Receiver Information

6*35x
14

-----|

5 February 2007

51

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Status

Tag

Field Name

Content/Options

No.

M = Mandatory O = Optional

MT 604 Network Validated Rules


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

MT 604 Usage Rules


Each transfer/delivery order must be for the same type of metal, metal account and value date.

MT 604 Field Specifications


1. Field 26C: Identification of the Metal and the Metal Account
FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

Where
Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the metal to be transferred/delivered, as well as the metal account to be debited which is serviced by the
Receiver for the Sender, or the party for which the Sender is an authorised agent.

52

Message Reference Guide - Standards Release Guide - February 2007

MT 604

CODES
When Delivery Details is present, it must contain the code CIF (Error code(s): T35).
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

5 February 2007

53

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Code

Coin Name

Denomination

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

1/10

USAGE RULES
Delivery Details is used only if CIF (ie, Cost, Insurance, Freight) applies. If this subfield is not present, then LOCO applies.
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

2. Field 25: Further Account Identification

54

Message Reference Guide - Standards Release Guide - February 2007

MT 604

FORMAT
35x

PRESENCE
Optional
DEFINITION
This field provides further identification information about the metal account to be debited.

3. Field 30: Value Date


FORMAT
6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the metal is to be transferred/delivered.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

4. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional

5 February 2007

55

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

DEFINITION
This field specifies additional information for the Receiver concerning the entire message.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code word can be followed by an
indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

5. Field 20: Transaction Reference Number


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

6. Field 21: Related Reference


FORMAT
16x

56

Message Reference Guide - Standards Release Guide - February 2007

MT 604

PRESENCE
Mandatory
DEFINITION
This field contains a reference to the related transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).
USAGE RULES
If the related message is an MT 600 Precious Metal Trade Confirmation, this field must contain the common reference of
that MT 600.
If the related message is an MT 604, this field must contain the contents of field 21 of that MT 604.
If the Sender is not the originator of the transaction and no related reference is available, the code NONREF must be used in
this field.
In all other cases, this field must contain a reference to the related transaction which is meaningful to the beneficiary of the
metal.

7. Field 23: Further Identification


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field indicates whether the metal is to be delivered (ie, physical movement is involved) or transferred (ie, by book
entry).
CODES
One of the following codes must be used:
DELIVERY

Delivery

TRANSFER

Transfer

8. Field 26D: Certificate Number(s) and/or Bar Number(s)

5 February 2007

57

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

FORMAT
Option D

30*65x

(Narrative)

PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal to be transferred/delivered.

9. Field 32F: Quantity of the Metal


FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory
DEFINITION
This field specifies the type of unit and the quantity of the precious metal to be transferred/delivered.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

58

Message Reference Guide - Standards Release Guide - February 2007

MT 604

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

10. Field 82a: Instructing Party


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the initiator of the transaction, when other than the Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

11. Field 86a: Intermediary


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional

5 February 2007

59

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

DEFINITION
This field identifies the intermediary institution for the transfer of the metal.
NETWORK VALIDATED RULES
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).

12. Field 87a: Receiver of the Metal


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the party, if different from the Receiver of the message, to which the precious metal is to be delivered/
transferred in favour of the party specified in field 88a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations.(Error code(s): C05).

13. Field 88a: Beneficiary of the Metal


FORMAT
Option A
Option B
Option D

60

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

Message Reference Guide - Standards Release Guide - February 2007

MT 604

PRESENCE
Mandatory
DEFINITION
This field identifies the beneficiary of the precious metal.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

14. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver concerning the transfer/delivery order in this occurrence of the
repetitive sequence.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code word can be followed by an
indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

5 February 2007

61

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

62

Message Reference Guide - Standards Release Guide - February 2007

MT 605

MT 605 Precious Metal Notice to Receive


MT 605 Scope
This message is sent by the owner of a metal account or its authorised agent to the metal account servicing institution.
It notifies the Receiver of the impending delivery/transfer of specified quantities of precious metal, physically or by book
entry, to be held for, or credited to, the account serviced for the Sender or the party specified in field 88a for which the
Sender is an authorised agent.

MT 605 Format Specifications


MT 605 Precious Metal Notice to Receive
Status

Tag

20

26C

Field Name

Content/Options

No.

Transaction Reference Number

16x

Identification of the Metal and the Metal Account

[3!a]/15x/5!a4!a[4x][//8x]

25

Further Account Identification

35x

30

Value Date

6!n

72

Sender to Receiver Information

6*35x

21

Related Reference

16x

23

Further Identification

16x

26D

Certificate Number(s) and/or Bar Number(s)

30*65x

32F

Quantity of the Metal

3!a15d

82a

Instructing Party

A, B or D

----->

10
M

87a

Deliverer of the Metal

A, B or D
11

88a

Beneficiary of the Metal

A, B or D
12

72

Sender to Receiver Information

6*35x
13

-----|
M = Mandatory O = Optional

5 February 2007

63

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 605 Network Validated Rules


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

MT 605 Usage Rules


Each notice must relate to the same type of metal, metal account and value date.

MT 605 Field Specifications


1. Field 20: Transaction Reference Number
FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

2. Field 26C: Identification of the Metal and the Metal Account


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

Where

64

Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

Message Reference Guide - Standards Release Guide - February 2007

MT 605

PRESENCE
Mandatory
DEFINITION
This field identifies the metal to be received by the Receiver in favour of the Sender or the party for which the Sender is an
authorised agent (ie, the party specified in field 88a). It also identifies the metal account serviced by the Receiver for the
Sender or the party for which the Sender is an authorised agent.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

5 February 2007

65

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Code

Coin Name

BRIT

BRITANNIA

COIN

OTHER COINS

CORO

Denomination
1/1

1/2

1/4

1/10

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

1/10

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).

66

Message Reference Guide - Standards Release Guide - February 2007

MT 605

USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

3. Field 25: Further Account Identification


FORMAT
35x

PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account to be credited.

4. Field 30: Value Date


FORMAT
6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the specified metal is to be received.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

5. 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
Lines 2-6

5 February 2007

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

67

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver concerning the entire message.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code can be followed by an indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

6. Field 21: Related Reference


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field contains a reference to the related transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).
USAGE RULES
If the related message is an MT 604 Precious Metal Transfer/ Delivery Order, this field must contain the contents of field 21
of that MT 604.
If the related message is an MT 600 Precious Metal Trade Confirmation, this field must contain the common reference of
that MT 600.

68

Message Reference Guide - Standards Release Guide - February 2007

MT 605

If no related reference is available, the code NONREF must be used in this field.

7. Field 23: Further Identification


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field indicates whether the metal will be delivered (ie, physical movement is involved) or transferred (ie, by book
entry) to the Receiver of the message.
CODES
One of the following codes must be used:
DELIVERY

Delivery

TRANSFER

Transfer

8. Field 26D: Certificate Number(s) and/or Bar Number(s)


FORMAT
Option D

30*65x

(Narrative)

PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal to be received.

9. Field 32F: Quantity of the Metal


FORMAT
Option F

5 February 2007

3!a15d

(Unit) (Amount)

69

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

PRESENCE
Mandatory
DEFINITION
This field specifies the type of unit and the quantity of metal to be received.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

10. Field 82a: Instructing Party


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Optional

70

Message Reference Guide - Standards Release Guide - February 2007

MT 605

DEFINITION
This field identifies the party by order of which the metal is to be transferred/delivered to the Receiver of the message, if
different from the Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

11. Field 87a: Deliverer of the Metal


FORMAT
Option A
Option B
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

PRESENCE
Mandatory
DEFINITION
This field identifies the party from which the precious metal will be delivered/transferred to the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

12. Field 88a: Beneficiary of the Metal


FORMAT
Option A
Option B
Option D

5 February 2007

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Location)
(Party Identifier)
(Name & Address)

71

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

PRESENCE
Optional
DEFINITION
Where applicable, this field identifies the party for which the Sender is the authorised agent.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

13. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver concerning the notice in this occurrence of the repetitive
sequence.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code can be followed by an indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

72

Message Reference Guide - Standards Release Guide - February 2007

MT 605

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

5 February 2007

73

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 606 Precious Metal Debit Advice


MT 606 Scope
This message is sent by the metal account servicing institution to the account owner or its authorised agent.
It is used to advise the Receiver of an entry which has been debited to its account or an account for which the Receiver is an
authorised agent.

MT 606 Format Specifications


MT 606 Precious Metal Debit Advice
Status

Tag

Field Name

Content/Options

No.

20

Transaction Reference Number

16x

21

Related Reference

16x

26C

Identification of the Metal and the Metal Account

[3!a]/15x/5!a4!a[4x][//8x]

25

Further Account Identification

35x

26D

Certificate Number(s) and/or Bar Number(s)

30*65x

30

Value Date

6!n

32F

Quantity of the Metal

3!a15d

82a

Instructing Party

A or D

87a

Receiver of the Metal

A or D

88a

Beneficiary of the Metal

A or D
10

72

Sender to Receiver Information

6*35x
11

M = Mandatory O = Optional

MT 606 Network Validated Rules


There are no network validated rules for this message type.

MT 606 Field Specifications

74

Message Reference Guide - Standards Release Guide - February 2007

MT 606

1. Field 20: Transaction Reference Number


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

2. Field 21: Related Reference


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field contains the reference of the transaction which resulted in this 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).
USAGE RULES
If the related message is an MT 600 Precious Metal Trade Confirmation, this field must contain the common reference of
that MT 600.
If the related message is an MT 604 Precious Metal Transfer/Delivery Order, this field must contain the contents of field 20
of that MT 604.
If no related reference is available, the code NONREF must be used in this field.

3. Field 26C: Identification of the Metal and the Metal Account


FORMAT
Option C

5 February 2007

[3!a]/15x/5!a4!a[4x][//8x]

75

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Where
Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the metal to which this message relates, and the metal account serviced by the Sender for the Receiver
or the party for which the Receiver is an authorised agent, which is debited for the amount of metal advised by this message.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

76

Message Reference Guide - Standards Release Guide - February 2007

MT 606

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

5 February 2007

1/10

77

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Code

Coin Name

Denomination

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

4. Field 25: Further Account Identification


FORMAT
35x

PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account which has been debited.

5. Field 26D: Certificate Number(s) and/or Bar Number(s)


FORMAT
Option D

30*65x

(Narrative)

PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal which has been debited.

6. Field 30: Value Date

78

Message Reference Guide - Standards Release Guide - February 2007

MT 606

FORMAT
6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the specified metal was debited.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

7. Field 32F: Quantity of the Metal


FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory
DEFINITION
This field specifies the type of unit and the quantity of metal which has been debited from the metal account.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

5 February 2007

79

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

8. Field 82a: Instructing Party


FORMAT
Option A
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the party which instructed the Sender to execute the transaction, when different from the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

9. Field 87a: Receiver of the Metal


FORMAT
Option A
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the party to which the precious metal has been delivered/transferred.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).

80

Message Reference Guide - Standards Release Guide - February 2007

MT 606

The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

10. Field 88a: Beneficiary of the Metal


FORMAT
Option A
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the final beneficiary of the metal.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

11. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.

5 February 2007

81

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code can be followed by an indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

82

Message Reference Guide - Standards Release Guide - February 2007

MT 607

MT 607 Precious Metal Credit Advice


MT 607 Scope
This message is sent by the metal account servicing institution to the account owner or its authorised agent.
It is used to advise the Receiver of an entry which has been credited to its account or an account for which the Receiver is
an authorised agent.

MT 607 Format Specifications


MT 607 Precious Metal Credit Advice
Status

Tag

Field Name

Content/Options

No.

20

Transaction Reference Number

16x

21

Related Reference

16x

26C

Identification of the Metal and the Metal Account

[3!a]/15x/5!a4!a[4x][//8x]

25

Further Account Identification

35x

26D

Certificate Number(s) and/or Bar Number(s)

30*65x

30

Value Date

6!n

32F

Quantity of the Metal

3!a15d

82a

Instructing Party

A or D

87a

Deliverer of the Metal

A or D

72

Sender to Receiver Information

6*35x
10

M = Mandatory O = Optional

MT 607 Network Validated Rules


There are no network validated rules for this message type.

MT 607 Field Specifications


1. Field 20: Transaction Reference Number

5 February 2007

83

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

2. Field 21: Related Reference


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field contains the reference to the related message or transaction.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).
USAGE RULES
If the related message is an MT 600 Precious Metal Trade Confirmation, this field must contain the common reference of
that MT 600.
If the related message is an MT 604 Precious Metal Transfer/ Delivery Order, this field must contain the contents of field 21
of that MT 604.
If no related reference is available, the code NONREF must be used in this field.

3. Field 26C: Identification of the Metal and the Metal Account


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

Where

84

Message Reference Guide - Standards Release Guide - February 2007

MT 607

Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the metal to which this message relates and the metal account serviced by the Sender for the Receiver or
the party for which the Receiver is an authorised agent, which is credited with the amount of metal advised by this message.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

5 February 2007

85

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

86

10

1/10

Message Reference Guide - Standards Release Guide - February 2007

MT 607

Code
VREN

Coin Name
VRENELI

Denomination
20

10

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

4. Field 25: Further Account Identification


FORMAT
35x

PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account which has been credited.

5. Field 26D: Certificate Number(s) and/or Bar Number(s)


FORMAT
Option D

30*65x

(Narrative)

PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal which has been credited.

6. Field 30: Value Date


FORMAT
6!n

5 February 2007

(Date)

87

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the specified metal was credited.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

7. Field 32F: Quantity of the Metal


FORMAT
Option F

3!a15d

(Unit) (Amount)

PRESENCE
Mandatory
DEFINITION
This field specifies the type of unit and the quantity of metal which has been credited to the metal account.
CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).

88

Message Reference Guide - Standards Release Guide - February 2007

MT 607

8. Field 82a: Instructing Party


FORMAT
Option A
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the instructing party which originated the transaction, if different from the Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

9. Field 87a: Deliverer of the Metal


FORMAT
Option A
Option D

[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
4*35x

(Party Identifier)
(BIC)
(Party Identifier)
(Name & Address)

PRESENCE
Optional
DEFINITION
This field identifies the party from which the precious metal was received.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27,T28,T29,T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more information
about BEIs. This error code applies to all types of BICs referenced in a FIN message including SWIFT BICs, non-SWIFT
BICs, Masters, Synonyms, Live destinations and Test & Training destinations .(Error code(s): C05).

5 February 2007

89

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

10. 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
Lines 2-6

/8c/[additional information]
[//continuation of additional information]
or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code can be followed by an indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

90

Message Reference Guide - Standards Release Guide - February 2007

MT 608

MT 608 Statement of a Metal Account


MT 608 Scope
This message is sent by a metal account servicing institution to the metal account owner or its authorised agent.
It is used to advise the Receiver of transactions booked to a metal account.
This statement message contains all bookings present in the account, whether caused by a message received via SWIFT or
by some other means.

MT 608 Format Specifications


MT 608 Statement of a Metal Account
Status

Tag

20

26C

Field Name

Content/Options

No.

Transaction Reference Number

16x

Identification of the Metal and the Metal Account

[3!a]/15x/5!a4!a[4x][//8x]

25

Further Account Identification

35x

28

Statement Number/Sequence Number

5n[/2n]

60a

Opening Balance

F or M

61

Statement Line

62a

Closing Balance

F or M

64

Closing Available Balance

1!a6!n3!a15d

65

Forward Available Balance

1!a6!n3!a15d

----->
O
-----|

----->
O
-----|
M = Mandatory O = Optional
* See Field Specifications

5 February 2007

91

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 608 Network Validated Rules


C1
The metal code must be the same for all occurrences of fields 60a, 62a, 64 and 65 in the message (Error code(s): C80).

MT 608 Usage Rules


While it may be the ultimate goal to have full identification for all bookings, this is currently not always practicable for
bookings from non-SWIFT transactions. A four character code is provided, however, for classification according to the
nature of such non-SWIFT transactions.
Each statement message carries an opening and a closing balance, as well as its sequence number in field 28 Statement
Number/Page Number. The book entry itself is contained in a field 61 Statement Line. The last message in a multiple
message statement is identified by the closing balance in field 62a Closing Balance showing the tag letter F.
Since a SWIFT message is restricted to the maximum input message length, it is possible that several messages
(pages) may be needed to accommodate all the information. In these instances, each message should be identified as
to its sequence in the total number.
To facilitate manual reconciliation, it is recommended that statement entries be sorted by debits and credits and these
by value date in ascending amounts.

MT 608 Field Specifications


1. Field 20: Transaction Reference Number
FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the precious metal statement.
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 26C: Identification of the Metal and the Metal Account


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

where:

92

Subfield

Format

[3!a]

Name
Delivery Details

Message Reference Guide - Standards Release Guide - February 2007

MT 608

Subfield

Format

Name

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the metal account, serviced by the Sender for the Receiver or the party for which the Receiver is an
authorised agent, to which this statement relates.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

5 February 2007

93

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

94

10

1/10

Message Reference Guide - Standards Release Guide - February 2007

MT 608

Code
VREN

Coin Name
VRENELI

Denomination
20

10

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

3. Field 25: Further Account Identification


FORMAT
35x

PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account to which this statement relates.

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 statement followed by the sequence number of the message within that
statement.

5. Field 60a: Opening Balance


FORMAT
Option F
Option M

5 February 2007

1!a6!n3!a15d
1!a6!n3!a15d

(D/C Mark) (Date) (Unit) (Amount)


(D/C Mark) (Date) (Unit) (Amount)

95

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

PRESENCE
Mandatory
DEFINITION
This field specifies, for the (intermediate) opening balance, whether it is a debit or credit balance, the date, the unit of metal
and 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.

The (intermediate) opening balance is a debit balance.

CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Unit must be the same in the fields 60, 62a, 64 and 65 (Error code(s): C80).
Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length .(Error code(s): T40,T43).

96

Message Reference Guide - Standards Release Guide - February 2007

MT 608

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 statement
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

6!n

[4!n]

2a

[1!a]

Funds Code (3rd character of the currency code, if needed)

15d

Amount

1!a3!c

16x

[//16x]

Account Servicing Institutions Reference

[34x]

Supplementary Details

Date (YYMMDD)
Entry Date (MMDD)
Debit/Credit Mark

Transaction Type Identification Code


Reference for the Account Owner

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):
C

Credit

Debit

5 February 2007

97

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

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
through SWIFT or where an alpha description is preferred.
Format:

3.

N3!c

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:
BRF

Brokerage fee

CHG

Charges and other expenses

COM

Commission

DIV

Dividends-Warrants

EQA

Equivalent amount

INT

Interest

MSC

Miscellaneous

PCH

Purchase

RTI

Returned item

SAL

Sale

STO

Standing order

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)

98

Message Reference Guide - Standards Release Guide - February 2007

MT 608

NETWORK VALIDATED RULES


Subfield 1 ,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).
Subfield 4 ,Funds Code, must not be used in this message (Error code(s): C91).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length (Error code(s): T40,T43).
Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
When the first character of subfield 6 ,Transaction Type Identification Code, is an S, the remaining characters must be
in the range 100-999 (Error code(s): T18).
USAGE RULES
This field may be repeated within the constraints of the maximum input message length.
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 the
debit. Therefore, the content of this subfield is the field 20 Senders 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 result
of a related transaction. In this case, the content of subfield 7, Reference for the Account Owner, is the reference
for 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 in
this subfield is for that payment. The content of Reference for the Account Owner is the field 20 Transaction
Reference Number (or its equivalent) of the payment instruction issued by the account servicing institution.
If no reference is available for this subfield, 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 Institutions Reference:
The content of this subfield is the account servicing institutions own reference for the transaction.
When the transaction has been initiated by the account servicing institution, this reference may be identical to subfield
7, Reference for the Account Owner. If this is the case, Account Servicing Institutions Reference, sub field 8 may be
omitted.
The following rules apply to subfield 9 ,Supplementary Details:
When no reference for the account owner is available, ie, Reference for the Account Owner contains NONREF, 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.

5 February 2007

99

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

7. Field 62a: Closing Balance


FORMAT
Option F
Option M

1!a6!n3!a15d
1!a6!n3!a15d

(D/C Mark) (Date) (Unit) (Amount)


(D/C Mark) (Date) (Unit) (Amount)

PRESENCE
Mandatory
DEFINITION
This field specifies, for the (intermediate) closing balance, whether it is a debit or credit balance, the date, the unit of metal
and amount of the balance.
CODES
D/C Mark must contain one of the following codes (Error code(s): T51):
C

The (intermediate) closing balance is a credit balance.

The (intermediate) closing balance is a debit balance.

CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


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

100

Message Reference Guide - Standards Release Guide - February 2007

MT 608

Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length .(Error code(s): T40,T43).
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. When several
messages are transmitted for the same statement period, all statement messages except the last message must contain field
62M (intermediate closing balance); the last message of the statement period must contain field 62F (final closing balance).

8. Field 64: Closing Available Balance


FORMAT
1!a6!n3!a15d

(D/C Mark) (Date) (Unit) (Amount)

PRESENCE
Optional
DEFINITION
This field specifies, for the available closing balance, whether it is a debit or credit balance, the date, the unit of metal and
amount of the balance.
CODES
D/C Mark must contain one of the following codes (Error code(s): T51):
C

The available closing balance is a credit balance.

The available closing balance is a debit balance.

CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

5 February 2007

101

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length .(Error code(s): T40,T43).

9. Field 65: Forward Available Balance


FORMAT
1!a6!n3!a15d

(D/C Mark) (Date) (Unit) (Amount)

PRESENCE
Optional
DEFINITION
This field specifies, for the forward available balance, whether it is a debit or credit balance, the date, the unit of metal and
amount of the balance.
CODES
D/C Mark must contain one of the following codes (Error code(s): T51):
C

The forward available balance is a credit balance.

The forward available balance is a debit balance.

CODES
Unit must contain one of the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

102

Message Reference Guide - Standards Release Guide - February 2007

MT 608

TAL

Tael

TOL

Tola

UNT

Unit

NETWORK VALIDATED RULES


Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Amount must not contain more than six digits following the decimal comma (Error code(s): C89).
The integer part of Amount must contain at least one digit. The decimal comma , is mandatory and is included in the
maximum length .(Error code(s): T40,T43).
USAGE RULES
Unit specifies the code for the unit of metal associated with this metal account.

5 February 2007

103

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 609 Statement of Metal Contracts


MT 609 Scope
This message is sent by a metal trader to its counterparty.
It is a listing of all undelivered spots and/or outstanding forward contracts, and/or unexercised options, as at a specified date.

MT 609 Format Specifications


MT 609 Statement of Metal Contracts
Status

Tag

Field Name

Content/Options

No.

27

Sequence of Total

1!n/1!n

20

Transaction Reference Number

16x

31C

Statement Date

6!n

30

Date Prepared

6!n

23

Further Identification

16x

26C

Identification of the Metal

[3!a]/15x/5!a4!a[4x][//8x]

68a

Transaction Details

B or C

72

Sender to Receiver Information

6*35x

----->
M
----->
M
----->
M
-----|
-----|
O
-----|
M = Mandatory O = Optional

MT 609 Network Validated Rules


C1
Field 68B must be used when the immediately preceding field 23 contains either SPOTS or FORWARDS (Error
code(s): C85).

104

Message Reference Guide - Standards Release Guide - February 2007

MT 609

C2
Field 68C must be used when the immediately preceding field 23 contains the code word OPTIONS (Error code(s):
C86).
C3
The currency in subfield 7 and 10 of field 68B and subfields 7, 9 and 11 of field 68C must be the same (Error code(s):
T74).

MT 609 Usage Rules


All the entries must be related to contracts outstanding as at the same date (ie, the date specified in field 31C).
All the entries should correspond to the details of previously exchanged confirmations for these metal contracts.
Since a SWIFT message, as sent, is restricted to the maximum input message length, it is possible that several
messages are needed to accommodate all the information.

MT 609 Field Specifications


1. Field 27: Sequence of Total
FORMAT
1!n/1!n

(Number) (Total)

PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the total sequence of messages sent to the Receiver to convey the information about the metal contracts outstanding at the date specified in field 31C.

2. Field 20: Transaction Reference Number


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field specifies the Senders reference to the statement.
NETWORK VALIDATED RULES
This field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

5 February 2007

105

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

3. Field 31C: Statement Date


FORMAT
Option C

6!n

(Date)

PRESENCE
Mandatory
DEFINITION
This field specifies the date at which the contracts listed in this statement message remain outstanding.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

4. Field 30: Date Prepared


FORMAT
6!n

(Date)

PRESENCE
Optional
DEFINITION
This field specifies the date the statement was prepared, if different from the date the message was sent.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).

5. Field 23: Further Identification


FORMAT
16x

PRESENCE
Mandatory
DEFINITION
This field identifies the type of contract listed in the sequence of fields 26C and 68a immediately following it.

106

Message Reference Guide - Standards Release Guide - February 2007

MT 609

CODES
This field must contain one of the following codes to indicate the type of contracts to be listed (Error code(s): T08):
FORWARDS

The following is a list of all outstanding forward contracts as at a specified date.

OPTIONS

The following is a list of all unexercised options as at a specified date .

SPOTS

The following is a list of all undelivered spots as at a specified date.

6. Field 26C: Identification of the Metal


FORMAT
Option C

[3!a]/15x/5!a4!a[4x][//8x]

where:
Subfield

Format

Name

[3!a]

Delivery Details

/15x

Availability

/5!a

Allocation

4!a

Type

[4x]

Denomination

[//8x]

Form

PRESENCE
Mandatory
DEFINITION
This field identifies the metal to which this statement relates.
CODES
Allocation must contain one of the following codes (Error code(s): T03):
ALLOC

Specifies the metal is allocated

UNALL

Specifies the metal is unallocated

5 February 2007

107

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

CODES
Type identifies the metal or coin. When identifying a metal, one of the following codes must be used (Error code(s): T04) :
GOLD

Gold

IRID

Iridium

OSMI

Osmium

PALL

Palladium

PLAT

Platinum

RHOD

Rhodium

RUTH

Ruthenium

SILV

Silver

CODES
When Type is used to identify a coin, one of the following codes must be used (Error code(s): T04). When this is the case,
the denomination must be specified in Denomination:
Code

Coin Name

Denomination

AMEG

AMERICAN
EAGLE

50

25

10

ANUG

AUSTRALIAN
NUGGET

1/1

1/2

1/4

1/10

BRIT

BRITANNIA

1/1

1/2

1/4

1/10

COIN

OTHER COINS

CORO

AUSTRIAN
CORONA

100

20

10

DUCA

DUCAT FOURFOLD SINGLE

FRFR

FRENCH
FRANCS

20

GECU

GOLDEN ECU

50

KRUG

KRUGER
RAND

1/1

1/2

1/4

LBTY

LIBERTY
DOLLAR

20

10

108

1/10

Message Reference Guide - Standards Release Guide - February 2007

MT 609

Code

Coin Name

Denomination

MAPL

MAPLE

1/1

1/2

1/4

1/10

MEXP

MEXICAN
PESO

50

20

10

NOBL

NOBLE

1/1

NSOV

NEW
SOVEREIGN

1/1

1/2

OSOV

OLD
SOVEREIGN

1/1

1/2

SAEG

SILVER
AMERICAN
EAGLE

1/1

SECU

SILVER ECU

STAT

STATUE

20

10

VREN

VRENELI

20

10

NETWORK VALIDATED RULES


Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.

7. Field 68a: Transaction Details


FORMAT
Option B
Option C

6!n6!n16x/1!a3!a15d
3!a15d/6!n3!a15d
4a/4a/1!a[6!n]3!a15d
3!a15d3!a15d3!a15d

where Option B is:


Subfield

Format

6!n

Trade Date

6!n

Maturity Date

5 February 2007

Name

109

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

Subfield

Format

Name

16x

Contract Number

/1!a

Indicator

3!a15d

Unit and Quantity of Metal

3!a15d

Currency and Price Per Unit

/6!n

3!a15d

Value Date (of the Consideration)


Currency and Consideration

and where Option C is:


Subfield

Format

Name

4a

Buy/Sell Indicator

/4a

Call/Put indicator

/1!a

Style Indicator

[6!n]

Date Contract Agreed

3!a15d

Unit and Amount of the Underlying Metal

3!a15d

Currency and Strike Price of the metal option per unit of the underlying metal

3!a15d

Currency and Premium Price per unit of the underlying metal

3!a15d

Currency and Premium Payment of the metal option.

PRESENCE
Mandatory
DEFINITION
This field provides transaction details on undelivered SPOTS or outstanding FORWARDS (option B) or pending OPTIONS
(option C) as specified in the immediately preceding field 23.
CODES
In option B, subfield 4, Indicator, one of the following codes must be used (Error code(s): T05):
B

110

The Sender bought the metal

Message Reference Guide - Standards Release Guide - February 2007

MT 609

The Sender sold the metal

CODES
In both options B and C, Unit specifies the unit on which the amount of metal bought or sold is based. It must contain one of
the following codes (Error code(s): T06):
FOZ

Fine ounce

GOZ

Gross ounce

GRM

Gramme

KLO

Kilo

LOT

Lot

TAL

Tael

TOL

Tola

UNT

Unit

CODES
In option C, subfield 1, Buy/Sell Indicator, must contain one of the following codes:
BUY

The Sender has bought the option

SELL

The Sender has sold the option

CODES
In option C, subfield 2, Call/Put Indicator, must contain one of the following codes:
CALL

The option is a call

PUT

The option is a put

CODES
In option C, subfield 3, Style Indicator, must contain one of the following codes (Error code(s): T09):
A

This is an American style option

This is a European style option

5 February 2007

111

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

NETWORK VALIDATED RULES


In option B:
When field 23 contains SPOTS or FORWARDS, option B must be used (Error Code C1).
Subfield 1, Trade Date, subfield 2, Maturity Date and subfield 7, Value Date, must be valid dates expressed as YYMMDD
(Error code(s): T50).
In subfields 5, 6 and 8, the integer part of Quantity of Metal, Price Per Unit and Consideration must contain at least one
digit. The decimal comma , is mandatory and is included in the maximum length .(Error code(s): T40,T43).
In subfield 5, Quantity of Metal, must not contain more than six digits following the decimal comma (Error code(s): C89).
In subfields 6 and 8, Currency must be a valid ISO 4217 currency code (Error code(s): T52).
In subfields 6 and 8, Currency must be the same in Price Per Unit and Consideration (Error code(s): T74).
In subfield 8, the number of decimal digits in Consideration will be validated against the maximum number allowed for the
corresponding currency specified in Currency (Error code(s): C03).
In option C:
When field 23 contains OPTIONS, option C must be used (Error Code C2).
Subfield 4, Date Contract Agreed, must be a valid date expressed as YYMMDD (Error code(s): T50).
The integer part of Amount in subfields 5,6,7 and 8, the Underlying Metal, Strike Price, Premium Price Per Unit and
Premium Payment must contain at least one digit. The decimal comma , is mandatory and is included in the maximum
length .(Error code(s): T40,T43).
In subfield 5, Amount of the Underlying Metal must not contain more than six digits following the decimal comma (Error
code(s): C89).
In subfields 6, 7 and 8, Currency must be a valid ISO 4217 currency code (Error code(s): T52).
In subfields 6, 7 and 8, Currency must be the same in Strike Price, Premium Price Per Unit and Premium Payment (Error
code(s): T74).
In Premium Payment, the number of decimal digits will be validated against the maximum number allowed for the corresponding currency specified in Currency (Error code(s): C03).
USAGE RULES
Contract Number specifies the reference of the contract, eg, the field 20 Transaction Reference Number of the MT 600
Precious Metal Trade Confirmation.

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

112

/8c/[additional information]

Message Reference Guide - Standards Release Guide - February 2007

MT 609

Lines 2-6

[//continuation of additional information]


or
[/8c/[additional information]]

PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
BROKER

Identification of the broker negotiating the contract on behalf of one of the parties.

ELEC

Indicates that the deal has been arranged via an electronic means. The code can be followed by an indication of the specific electronic means used for arranging the deal.

PHON

The deal was arranged by telephone.

TELEX

The deal was arranged by telex.

USAGE RULES
Each code must be between slashes and must appear at the beginning of a line. All alphabetic characters must be in upper
case.
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".

5 February 2007

113

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 690 Advice of Charges, Interest and Other Adjustments


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

114

Message Reference Guide - Standards Release Guide - February 2007

MT 691

MT 691 Request for Payment of Charges, Interest and Other


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

5 February 2007

115

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 692 Request for Cancellation


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

116

Message Reference Guide - Standards Release Guide - February 2007

MT 695

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

5 February 2007

117

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

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

118

Message Reference Guide - Standards Release Guide - February 2007

MT 698

MT 698 Proprietary Message


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

5 February 2007

119

Category 6 - Treasury Markets - Precious Metals for SWIFTStandards MT October 2007

MT 699 Free Format Message


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

120

Message Reference Guide - Standards Release Guide - February 2007

Glossary of Terms

Glossary of Terms
In addition to the definitions which appear in the Glossary of Terms, Standards General Information, the following terms
apply to category 6 Precious Metals messages:
Consideration
Funds paid by the Buyer of the precious metal to the Seller of the precious metal. This is calculated by multiplying the
quantity of the metal bought/sold by the price per unit and if applicable, adjusted for amounts such as commissions.
Metal Account
An account, also referred to as an Exchange or Holding Account, and related to one specific type and fineness of metal.

5 February 2007

121

Table Of Contents

Table of Contents
Copyright
.
.
.
.
.
.
.
.
.
.
Introduction .
.
.
.
.
.
.
.
.
.
Summary of Changes
.
.
.
.
.
.
.
Added Message Types
.
.
.
.
.
.
Removed Message Types .
.
.
.
.
.
Modified Message Types .
.
.
.
.
.
Category 6 Precious Metals Message Types .
.
.
Euro - Impact on Category Message Standards
.
.
MT 600 Precious Metal Trade Confirmation .
.
.
MT 600 Scope (updated) .
.
.
.
.
.
.
MT 600 Format Specifications (updated) .
.
.
MT 600 Network Validated Rules .
.
.
.
.
MT 600 Usage Rules
.
.
.
.
.
.
.
MT 600 Field Specifications (updated)
.
.
.
1. Field 15A: New Sequence (inserted) .
.
.
2. Field 20: Transaction Reference Number .
.
3. Field 21: Related Reference .
.
.
.
.
4. Field 22: Code/Common Reference .
.
.
5. Field 94A: Scope of Operation (inserted) .
.
6. Field 82a: Party A (inserted) .
.
.
.
.
7. Field 87a: Party B (inserted) .
.
.
.
.
8. Field 83a: Fund or Beneficiary Customer (inserted)
9. Field 30: Date Contract Agreed/Amended .
.
10. Field 26C: Identification of the Metal
.
.
11. Field 26H: Counterpartys Reference (inserted)
12. Field 33G: Price Per Unit .
.
.
.
.
13. Field 71C: Details of Adjustments .
.
.
14. Field 72: Sender to Receiver Information .
.
15. Field 15B: New Sequence (inserted) .
.
.
16. Field 32F: Quantity of the Metal
.
.
.
17. Field 86a: Intermediary (inserted) .
.
.
18. Field 87a: Receiver of the Metal .
.
.
.
19. Field 34P: Consideration .
.
.
.
.
20. Field 53a: Senders Correspondent .
.
.
21. Field 56a: Intermediary (inserted) .
.
.
22. Field 57a: Account With Institution .
.
.
23. Field 15C: New Sequence (inserted) .
.
.
24. Field 32F: Quantity of the Metal
.
.
.
25. Field 86a: Intermediary (inserted) .
.
.
26. Field 87a: Deliverer of the Metal
.
.
.
27. Field 34R: Consideration .
.
.
.
.
28. Field 56a: Intermediary (inserted) .
.
.
29. Field 57a: Account With Institution .
.
.
MT 601 Precious Metal Option Confirmation .
.
.
MT 601 Scope (updated) .
.
.
.
.
.
.
MT 601 Format Specifications (updated) .
.
.
MT 601 Network Validated Rules .
.
.
.
.
MT 601 Usage Rules
.
.
.
.
.
.
.
MT 601 Field Specifications (updated)
.
.
.
1. Field 20: Transaction Reference Number .
.
2. Field 21: Related Reference .
.
.
.
.
3. Field 22: Code/Common Reference .
.
.
4. Field 94A: Scope of Operation (inserted) .
.
5. Field 82a: Party A (inserted) .
.
.
.
.
6. Field 87a: Party B (inserted) .
.
.
.
.
7. Field 83a: Fund or Beneficiary Customer (inserted)
8. Field 23: Further Identification .
.
.
.
9. Field 30: Date Contract Agreed/Amended .
.

5 February 2007

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2
3
3
3
3
3
4
6
7
7
7
9
9
10
10
10
10
11
12
13
14
15
16
16
19
19
20
21
22
22
23
23
24
25
25
26
27
27
28
28
29
30
30
32
32
32
33
34
34
34
34
35
36
36
38
39
40
41

Table Of Contents

10. Field 26C: Identification of the Metal .


.
.
.
.
11. Field 31C: Earliest Exercise Date .
.
.
.
.
.
12. Field 31G: Expiry Details
.
.
.
.
.
.
.
13. Field 32F: Unit and Amount of the Metal .
.
.
.
14. Field 32B: Strike Price .
.
.
.
.
.
.
.
15. Field 33B: Premium Price
.
.
.
.
.
.
.
16. Field 34a: Premium Payment .
.
.
.
.
.
.
17. Field 53a: Senders Correspondent
.
.
.
.
.
18. Field 56a: Intermediary (inserted) .
.
.
.
.
.
19. Field 57a: Account With Institution .
.
.
.
.
20. Field 72: Sender to Receiver Information .
.
.
.
MT 604 Precious Metal Transfer/Delivery Order .
.
.
.
MT 604 Scope .
.
.
.
.
.
.
.
.
.
.
MT 604 Format Specifications .
.
.
.
.
.
.
.
MT 604 Network Validated Rules .
.
.
.
.
.
.
MT 604 Usage Rules .
.
.
.
.
.
.
.
.
.
MT 604 Field Specifications .
.
.
.
.
.
.
.
1. Field 26C: Identification of the Metal and the Metal Account
2. Field 25: Further Account Identification
.
.
.
.
3. Field 30: Value Date .
.
.
.
.
.
.
.
.
4. Field 72: Sender to Receiver Information
.
.
.
.
5. Field 20: Transaction Reference Number
.
.
.
.
6. Field 21: Related Reference .
.
.
.
.
.
.
7. Field 23: Further Identification
.
.
.
.
.
.
8. Field 26D: Certificate Number(s) and/or Bar Number(s) .
9. Field 32F: Quantity of the Metal .
.
.
.
.
.
10. Field 82a: Instructing Party .
.
.
.
.
.
.
11. Field 86a: Intermediary .
.
.
.
.
.
.
.
12. Field 87a: Receiver of the Metal .
.
.
.
.
.
13. Field 88a: Beneficiary of the Metal
.
.
.
.
.
14. Field 72: Sender to Receiver Information .
.
.
.
MT 605 Precious Metal Notice to Receive .
.
.
.
.
.
MT 605 Scope .
.
.
.
.
.
.
.
.
.
.
MT 605 Format Specifications .
.
.
.
.
.
.
.
MT 605 Network Validated Rules .
.
.
.
.
.
.
MT 605 Usage Rules .
.
.
.
.
.
.
.
.
.
MT 605 Field Specifications .
.
.
.
.
.
.
.
1. Field 20: Transaction Reference Number
.
.
.
.
2. Field 26C: Identification of the Metal and the Metal Account
3. Field 25: Further Account Identification
.
.
.
.
4. Field 30: Value Date .
.
.
.
.
.
.
.
.
5. Field 72: Sender to Receiver Information
.
.
.
.
6. Field 21: Related Reference .
.
.
.
.
.
.
7. Field 23: Further Identification
.
.
.
.
.
.
8. Field 26D: Certificate Number(s) and/or Bar Number(s) .
9. Field 32F: Quantity of the Metal .
.
.
.
.
.
10. Field 82a: Instructing Party .
.
.
.
.
.
.
11. Field 87a: Deliverer of the Metal .
.
.
.
.
.
12. Field 88a: Beneficiary of the Metal
.
.
.
.
.
13. Field 72: Sender to Receiver Information .
.
.
.
MT 606 Precious Metal Debit Advice .
.
.
.
.
.
.
MT 606 Scope .
.
.
.
.
.
.
.
.
.
.
MT 606 Format Specifications .
.
.
.
.
.
.
.
MT 606 Network Validated Rules .
.
.
.
.
.
.
MT 606 Field Specifications .
.
.
.
.
.
.
.
1. Field 20: Transaction Reference Number
.
.
.
.
2. Field 21: Related Reference .
.
.
.
.
.
.
3. Field 26C: Identification of the Metal and the Metal Account
4. Field 25: Further Account Identification
.
.
.
.
5. Field 26D: Certificate Number(s) and/or Bar Number(s) .
6. Field 30: Value Date .
.
.
.
.
.
.
.
.
7. Field 32F: Quantity of the Metal .
.
.
.
.
.

ii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

41
.
44
.
44
.
44
.
45
.
46
.
46
.
47
.
47
.
48
.
49
.
51
.
51
.
51
.
52
.
52
.
52
.
52
.
54
.
55
.
55
.
56
.
56
.
57
.
57
.
58
.
59
.
59
.
60
.
60
.
61
.
63
.
63
.
63
.
64
.
64
.
64
.
64
.
64
.
67
.
67
.
67
.
68
.
69
.
69
.
69
.
70
.
71
.
71
.
72
.
74
.
74
.
74
.
74
.
74
.
75
.
75
.
75
.
78
.
78
.
78
.
79
.

Message Reference Guide - Standards Release Guide - February 2007

Table Of Contents

8. Field 82a: Instructing Party


.
.
.
.
.
.
.
.
9. Field 87a: Receiver of the Metal .
.
.
.
.
.
.
10. Field 88a: Beneficiary of the Metal
.
.
.
.
.
.
11. Field 72: Sender to Receiver Information .
.
.
.
.
MT 607 Precious Metal Credit Advice
.
.
.
.
.
.
.
MT 607 Scope .
.
.
.
.
.
.
.
.
.
.
.
MT 607 Format Specifications .
.
.
.
.
.
.
.
.
MT 607 Network Validated Rules .
.
.
.
.
.
.
.
MT 607 Field Specifications .
.
.
.
.
.
.
.
.
1. Field 20: Transaction Reference Number
.
.
.
.
.
2. Field 21: Related Reference .
.
.
.
.
.
.
.
3. Field 26C: Identification of the Metal and the Metal Account .
4. Field 25: Further Account Identification
.
.
.
.
.
5. Field 26D: Certificate Number(s) and/or Bar Number(s) .
.
6. Field 30: Value Date .
.
.
.
.
.
.
.
.
.
7. Field 32F: Quantity of the Metal .
.
.
.
.
.
.
8. Field 82a: Instructing Party
.
.
.
.
.
.
.
.
9. Field 87a: Deliverer of the Metal .
.
.
.
.
.
.
10. Field 72: Sender to Receiver Information .
.
.
.
.
MT 608 Statement of a Metal Account
.
.
.
.
.
.
.
MT 608 Scope .
.
.
.
.
.
.
.
.
.
.
.
MT 608 Format Specifications .
.
.
.
.
.
.
.
.
MT 608 Network Validated Rules .
.
.
.
.
.
.
.
MT 608 Usage Rules .
.
.
.
.
.
.
.
.
.
.
MT 608 Field Specifications .
.
.
.
.
.
.
.
.
1. Field 20: Transaction Reference Number
.
.
.
.
.
2. Field 26C: Identification of the Metal and the Metal Account .
3. Field 25: Further Account Identification
.
.
.
.
.
4. Field 28: Statement Number/Sequence Number .
.
.
.
5. Field 60a: Opening Balance .
.
.
.
.
.
.
.
6. Field 61: Statement Line .
.
.
.
.
.
.
.
.
7. Field 62a: Closing Balance
.
.
.
.
.
.
.
.
8. Field 64: Closing Available Balance
.
.
.
.
.
.
9. Field 65: Forward Available Balance .
.
.
.
.
.
MT 609 Statement of Metal Contracts .
.
.
.
.
.
.
.
MT 609 Scope .
.
.
.
.
.
.
.
.
.
.
.
MT 609 Format Specifications .
.
.
.
.
.
.
.
.
MT 609 Network Validated Rules .
.
.
.
.
.
.
.
MT 609 Usage Rules .
.
.
.
.
.
.
.
.
.
.
MT 609 Field Specifications .
.
.
.
.
.
.
.
.
1. Field 27: Sequence of Total .
.
.
.
.
.
.
.
2. Field 20: Transaction Reference Number
.
.
.
.
.
3. Field 31C: Statement Date
.
.
.
.
.
.
.
.
4. Field 30: Date Prepared .
.
.
.
.
.
.
.
.
5. Field 23: Further Identification
.
.
.
.
.
.
.
6. Field 26C: Identification of the Metal .
.
.
.
.
.
7. Field 68a: Transaction Details .
.
.
.
.
.
.
.
8. Field 72: Sender to Receiver Information
.
.
.
.
.
MT 690 Advice of Charges, Interest and Other Adjustments .
.
.
MT 691 Request for Payment of Charges, Interest and Other Expenses
MT 692 Request for Cancellation .
.
.
.
.
.
.
.
.
MT 695 Queries
.
.
.
.
.
.
.
.
.
.
.
.
MT 696 Answers .
.
.
.
.
.
.
.
.
.
.
.
MT 698 Proprietary Message .
.
.
.
.
.
.
.
.
.
MT 699 Free Format Message
.
.
.
.
.
.
.
.
.
Glossary of Terms .
.
.
.
.
.
.
.
.
.
.
.

5 February 2007

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

80
.
80
.
81
.
81
.
83
.
83
.
83
.
83
.
83
.
83
.
84
.
84
.
87
.
87
.
87
.
88
.
89
.
89
.
90
.
91
.
91
.
91
.
92
.
92
.
92
.
92
.
92
.
95
.
95
.
95
.
97
.
100
.
101
.
102
.
104
.
104
.
104
.
104
.
105
.
105
.
105
.
105
.
106
.
106
.
106
.
107
.
109
.
112
.
114
.
115
.
116
.
117
.
118
.
119
.
120
.
121
.

iii

S-ar putea să vă placă și