Beruflich Dokumente
Kultur Dokumente
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
Introduction
Introduction
Summary of Changes
Added Message Types
n.a.
5 February 2007
MT Name
Purpose
Authen.
Max.
Length
MUG
600
2,000
601
2,000
604
2,000
605
2,000
606
2,000
607
2,000
608
Statement of a Metal
Account
2,000
609
Statement of Metal
Contracts
2,000
690
2,000
691
2,000
692
2,000
695
Queries
2,000
MT
MT Name
Purpose
Authen.
Max.
Length
MUG
696
Answers
2,000
698
Proprietary Message
10,000
699
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
MT 600
Tag
Field Name
Content/Options
No.
15A
20
New Sequence
(CrLf)
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
Status
Tag
Field Name
Content/Options
83a
A, D or J
30
6!n
No.
8
9
4
26C
[3!a]/15x/5!a4!a[4x][//8x]
10 5
26H
Counterpartys Reference
16x
11
33G
3!a15d[5!c]
12 6
71C
Details of Adjustments
6*35x
13 7
72
6*35x
14 8
15B
New Sequence
(CrLf)
15
32F
3!a15d
16 9
86a
Intermediary
A, B or D
17
87a
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
A, B or D
22
13
MT 600
Status
Tag
15C
Field Name
New Sequence
Content/Options
No.
(CrLF)
23
32F
3!a15d
24
14
86a
Intermediary
A, B or D
25
87a
A, B or D
26
15
34R
Consideration
6!n3!a15d
27
16
56a
Intermediary
A, B or D
28
57a
A, B or D
29
17
M = Mandatory O = Optional
5 February 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).
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.
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).
10
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.
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
EXOPTION
Confirmation of the mutually agreed settlement of a precious metal option which has been
exercised.
NEW
NOTICE
Liquidation notice for a forward deal. A notice is optional; its use is dependent on internal
practices.
5 February 2007
11
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
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
BILA
Bilateral confirmation, ie, the Sender and the Receiver are the principals.
BROK
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
MT 600
[/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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
M = Mandatory O = Optional
5 February 2007
13
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.
[/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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
14
MT 600
M = Mandatory O = Optional
[/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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
5 February 2007
15
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
M = Mandatory O = Optional
(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.
[3!a]/15x/5!a4!a[4x][//8x]
Where
16
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
UNALL
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
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
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
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.
16x
PRESENCE
Optional
DEFINITION
This field specifies the counterpartys reference, if known.
3!a15d[5!c]
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
19
6*35x
(Narrative)
/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
STMP
Stamp Duty.
20
MT 600
TTAX
Transaction tax.
VTAX
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.
(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
PHON
TELEX
5 February 2007
21
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 "//".
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.
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
MT 600
LOT
Lot
TAL
Tael
TOL
Tola
UNT
Unit
[/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.
5 February 2007
[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
(Party Identifier)
(BIC)
(Party Identifier)
(Location)
23
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.
6!n3!a15d
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
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.
[/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).
[/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
[/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
MT 600
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.
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
[/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.
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)
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.
6!n3!a15d
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
[/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.
[/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
MT 600
5 February 2007
31
Tag
Field Name
Content/Options
No.
20
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
A, D or J
23
Further Identification
16x
8
4
30
6!n
9
5
26C
[3!a]/15x/5!a4!a[4x][//8x]
10 6
31C
6!n
11 7
32
MT 601
Status
Tag
31G
Field Name
Expiry Details
Content/Options
No.
6!n/4!n/12a
12 8
32F
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
A, B or D
19
14
72
6*35x
20
15
M = Mandatory O = Optional
5 February 2007
33
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).
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
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.
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
CLOSEOUT
Confirmation of the mutually agreed surrender of the option by the buyer (holder) to the seller
(grantor) for compensation.
NEW
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
5 February 2007
35
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
BILA
Bilateral confirmation, ie, the Sender and the Receiver are the principals.
BROK
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.
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)
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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
M = Mandatory O = Optional
5 February 2007
37
[/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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
M = Mandatory O = Optional
38
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.
[/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/
4!a2!a2!c[3!c] or 4!a
/ACCT/
34x
/ADD1/
35x
/ADD2/
35x
/CITY/
35x
/CLRC/
35x
/GBSC/
6!n
/NAME/
34x
/USCH/
6!n
/USFW/
9!n
5 February 2007
39
M = Mandatory O = Optional
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
SELL
CODES
Call/Put Indicator must contain one of the following codes:
CALL
PUT
40
MT 601
CODES
Style Indicator must contain one of the following codes (Error code(s): T09):
A
(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.
[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
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
UNALL
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
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
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
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).
6!n/4!n/12a
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).
44
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
3!a15d
(Currency) (Price)
PRESENCE
Mandatory
5 February 2007
45
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.
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 .
6!n3!a15d
6!n3!a15d
PRESENCE
Mandatory
46
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).
[/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).
5 February 2007
[/1!a][/34x]
4!a2!a2!c[3!c]
[/1!a][/34x]
[35x]
(Party Identifier)
(BIC)
(Party Identifier)
(Location)
47
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.
[/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
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.
(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
TELEX
5 February 2007
49
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
MT 604
Tag
26C
Field Name
Content/Options
No.
[3!a]/15x/5!a4!a[4x][//8x]
25
35x
30
Value Date
6!n
72
6*35x
20
16x
21
Related Reference
16x
23
Further Identification
16x
26D
30*65x
32F
3!a15d
82a
Instructing Party
A, B or D
----->
10
O
86a
Intermediary
A, B or D
11
87a
A, B or D
12
88a
A, B or D
13
72
6*35x
14
-----|
5 February 2007
51
Status
Tag
Field Name
Content/Options
No.
M = Mandatory O = Optional
[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
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
UNALL
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
Code
Coin Name
Denomination
DUCA
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.
54
MT 604
FORMAT
35x
PRESENCE
Optional
DEFINITION
This field provides further identification information about the metal account to be debited.
(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).
(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
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
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 "//".
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).
56
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.
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
5 February 2007
57
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.
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
MT 604
[/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).
[/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
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).
[/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).
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)
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).
(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
TELEX
5 February 2007
61
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
MT 605
Tag
20
26C
Field Name
Content/Options
No.
16x
[3!a]/15x/5!a4!a[4x][//8x]
25
35x
30
Value Date
6!n
72
6*35x
21
Related Reference
16x
23
Further Identification
16x
26D
30*65x
32F
3!a15d
82a
Instructing Party
A, B or D
----->
10
M
87a
A, B or D
11
88a
A, B or D
12
72
6*35x
13
-----|
M = Mandatory O = Optional
5 February 2007
63
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).
[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
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
UNALL
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
Code
Coin Name
BRIT
BRITANNIA
COIN
OTHER COINS
CORO
Denomination
1/1
1/2
1/4
1/10
AUSTRIAN
CORONA
100
20
10
DUCA
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
66
MT 605
USAGE RULES
Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK).
Form specifies the physical form of the metal.
PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account to be credited.
(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).
(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
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
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 "//".
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
MT 605
If no related reference is available, the code NONREF must be used in this field.
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
30*65x
(Narrative)
PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal to be received.
5 February 2007
3!a15d
(Unit) (Amount)
69
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
[/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
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).
[/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).
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
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).
(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
TELEX
72
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
Tag
Field Name
Content/Options
No.
20
16x
21
Related Reference
16x
26C
[3!a]/15x/5!a4!a[4x][//8x]
25
35x
26D
30*65x
30
Value Date
6!n
32F
3!a15d
82a
Instructing Party
A or D
87a
A or D
88a
A or D
10
72
6*35x
11
M = Mandatory O = Optional
74
MT 606
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).
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.
5 February 2007
[3!a]/15x/5!a4!a[4x][//8x]
75
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
UNALL
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
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
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
Code
Coin Name
Denomination
SECU
SILVER ECU
STAT
STATUE
20
10
VREN
VRENELI
20
10
PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account which has been debited.
30*65x
(Narrative)
PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal which has been debited.
78
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).
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
[/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).
[/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
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).
[/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).
(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
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
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
MT 607
Tag
Field Name
Content/Options
No.
20
16x
21
Related Reference
16x
26C
[3!a]/15x/5!a4!a[4x][//8x]
25
35x
26D
30*65x
30
Value Date
6!n
32F
3!a15d
82a
Instructing Party
A or D
87a
A or D
72
6*35x
10
M = Mandatory O = Optional
5 February 2007
83
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).
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!a]/15x/5!a4!a[4x][//8x]
Where
84
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
UNALL
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
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
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
MT 607
Code
VREN
Coin Name
VRENELI
Denomination
20
10
PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account which has been credited.
30*65x
(Narrative)
PRESENCE
Optional
DEFINITION
This field lists the certificate and/or bar number(s) of the metal which has been credited.
5 February 2007
(Date)
87
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).
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
88
MT 607
[/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).
[/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
(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
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
MT 608
Tag
20
26C
Field Name
Content/Options
No.
16x
[3!a]/15x/5!a4!a[4x][//8x]
25
35x
28
5n[/2n]
60a
Opening Balance
F or M
61
Statement Line
62a
Closing Balance
F or M
64
1!a6!n3!a15d
65
1!a6!n3!a15d
----->
O
-----|
----->
O
-----|
M = Mandatory O = Optional
* See Field Specifications
5 February 2007
91
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).
[3!a]/15x/5!a4!a[4x][//8x]
where:
92
Subfield
Format
[3!a]
Name
Delivery Details
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
UNALL
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
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
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
MT 608
Code
VREN
Coin Name
VRENELI
Denomination
20
10
PRESENCE
Optional
DEFINITION
This field contains further identification information about the metal account to which this statement relates.
PRESENCE
Mandatory
DEFINITION
This field contains the sequential number of the statement followed by the sequence number of the message within that
statement.
5 February 2007
1!a6!n3!a15d
1!a6!n3!a15d
95
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
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
96
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).
where:
Subfield
Format
Name
6!n
[4!n]
2a
[1!a]
15d
Amount
1!a3!c
16x
[//16x]
[34x]
Supplementary Details
Date (YYMMDD)
Entry Date (MMDD)
Debit/Credit Mark
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
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
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
MT 608
5 February 2007
99
1!a6!n3!a15d
1!a6!n3!a15d
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
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
100
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).
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
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
TOL
Tola
UNT
Unit
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
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
MT 608
TAL
Tael
TOL
Tola
UNT
Unit
5 February 2007
103
Tag
Field Name
Content/Options
No.
27
Sequence of Total
1!n/1!n
20
16x
31C
Statement Date
6!n
30
Date Prepared
6!n
23
Further Identification
16x
26C
[3!a]/15x/5!a4!a[4x][//8x]
68a
Transaction Details
B or C
72
6*35x
----->
M
----->
M
----->
M
-----|
-----|
O
-----|
M = Mandatory O = Optional
104
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).
(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.
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
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).
(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).
PRESENCE
Mandatory
DEFINITION
This field identifies the type of contract listed in the sequence of fields 26C and 68a immediately following it.
106
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
OPTIONS
SPOTS
[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
UNALL
5 February 2007
107
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
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
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
6!n6!n16x/1!a3!a15d
3!a15d/6!n3!a15d
4a/4a/1!a[6!n]3!a15d
3!a15d3!a15d3!a15d
Format
6!n
Trade Date
6!n
Maturity Date
5 February 2007
Name
109
Subfield
Format
Name
16x
Contract Number
/1!a
Indicator
3!a15d
3!a15d
/6!n
3!a15d
Format
Name
4a
Buy/Sell Indicator
/4a
Call/Put indicator
/1!a
Style Indicator
[6!n]
3!a15d
3!a15d
Currency and Strike Price of the metal option per unit of the underlying metal
3!a15d
3!a15d
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
MT 609
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
SELL
CODES
In option C, subfield 2, Call/Put Indicator, must contain one of the following codes:
CALL
PUT
CODES
In option C, subfield 3, Style Indicator, must contain one of the following codes (Error code(s): T09):
A
5 February 2007
111
(Narrative)
In addition to narrative text, structured text with the following line formats may be used:
Line 1
112
/8c/[additional information]
MT 609
Lines 2-6
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
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
114
MT 691
5 February 2007
115
116
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
MT 696 Answers
Please refer to Category n - Common Group Messages, Chapter n96 Answers for details concerning this message type.
118
MT 698
5 February 2007
119
120
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
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
.
Table Of Contents
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