Swift Standards Category 6 Treasury Markets Precious Metals MT600 MT699

SWIFTStandards
Category 6 Treasury Markets Precious Metals

November 2003 Standards Release Standards Release Guide 2003 - Final edition - February 2003
Legal Notices
SWIFTStandards - Category 6
Legal Notices
IMPORTANT NOTE: You may install and use this publication only if you have entered into the relevant licence agreement with SWIFT. Please refer to such licence agreement to determine what you may or may not do with it. Note however that in the case of a Single User Licence, this publication must be installed on a standalone machine for access by one person at any one time, and references to "organisation" in these notices are to the ordering customer (BIC 8). In the case of a Server Licence, this publication can also be installed on a server for access within the organisation of the ordering customer (BIC 8), and references to "organisation" are then to all those SWIFT Users belonging to the same group as the ordering customer (BIC8) for traffic aggregation purposes. Copyright Copyright S.W.I.F.T. SCRL ("SWIFT"), avenue Adle 1, B-1310 La Hulpe, Belgium, 2002. All rights reserved. No part of this publication may be copied or reproduced, stored in a retrieval system, sold or transferred to any person, in whole or in part, in any manner or form or on any media, without the prior written permission of SWIFT. The recipient is, however, authorised to copy or reproduce this publication within its own organisation as may be reasonably necessary for the purpose for which it is supplied. Any such copy or reproduction will include the following: acknowledgement of the source, reference and date of publication, and all notices set out on this page. Confidentiality This publication may contain proprietary and/or confidential information of SWIFT and/or its suppliers. The recipient should not disclose this publication outside its organisation without the prior written permission of SWIFT. Disclaimer Although SWIFT has used reasonable efforts to ensure accuracy of its contents, SWIFT assumes no liability for any inadvertent error or omission that may appear in this publication. The information in this publication is the latest available at the date of its production, and may change from time to time. Trademarks and Patents SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, Accord and SWIFT-derived product and service names - such as but not limited to SWIFTNet and SWIFTAlliance - are trademarks of S.W.I.F.T. SCRL. SWIFT is the trading name of S.W.I.F.T. SCRL. All other product or company names that may be mentioned in this publication are trademarks or registered trademarks of their respective owners. Patent pending: SWIFTNet - TrustAct - e-paymentsPlus. February 2003 edition
Standards Release Guide 2003 - Final edition - February 2003
Overview
Overview
Added Message Types Removed Message Types Modified Message Types
Added Message Types

None
Removed Message Types

None
Modified Message Types

MT600 MT601 MT604 MT605 MT606 MT607
MT 600
MT 600 Precious Metal Trade Confirmation

MT 600 Scope
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 M M M M M O O 20 21 22 30 26C 33G 71C 72 Transaction Reference Number Related Reference Code/Common Reference Date Contract Agreed/Amended Identification of the Metal Price per Unit Details of Adjustments Sender to Receiver Information 16x 16x 8a/4!a2!c4!n4!a2!c 6!n [3!a]/15x/5!a4!a[4x][//8x] 3!a15d[5!c] 6*35x 6*35x 1 2 3 4 5 6 7 8
Optional Sequence B Precious Metal Bought
MT 600
Status M M M O M
Tag 32F 87a 34P 53a 57a
Field Name Quantity of the Metal Receiver of the Metal Consideration Senders Correspondent Account With Institution 3!a15d A, B or D 6!n3!a15d A, B or D A, B or D
Content/Options
No. 9 10 11 12 13
Optional Sequence C Precious Metal Sold M M M M 32F 87a 34R 57a Quantity of the Metal Deliverer of the Metal Consideration Account With Institution 3!a15d A, B or D 6!n3!a15d A, B or D 14 15 16 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). 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
MT 600 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). 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.
MT 600
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 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: NEW AMEND Confirmation of a new contract. 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. Confirmation of the mutually agreed cancellation of a contract. Confirmation of the mutually agreed settlement of a precious metal option which has been exercised. Liquidation notice for a forward deal. A notice is optional; its use is dependent on internal practices.
CANCEL EXOPTION NOTICE
CODES In confirmations sent by one financial institution, Code must contain one of the following codes: CORRECT COMPLETE Retransmission due to error - sent to correct error(s) in a previously sent MT 600. 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).
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.
MT 600
4. 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.
5. Field 26C: Identification of the Metal

FORMAT Option C [3!a]/15x/5!a4!a[4x][//8x]
Where Subfield 1 2 3 4 5 6 Format [3!a] /15x /5!a 4!a [4x] [//8x] Delivery Details Availability Allocation Type Denomination Form Name
MT 600
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 Specifies the metal is allocated 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 SILV PLAT PALL RHOD RUTH OSMI IRID Gold Silver Platinum Palladium Rhodium Ruthenium Osmium Iridium
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 AMEG ANUG Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET 50 1/1 25 1/2 Denomination 10 1/4 5 1/10
MT 600
Code CORO BRIT DUCA FRFR GECU KRUG LBTY MAPL MEXP NSOV NOBL OSOV SAEG SECU STAT VREN COIN
Coin Name AUSTRIAN CORONA BRITANNIA DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU STATUE VRENELI OTHER COINS 100 1/1 4 20 50 1/1 20 1/1 50 1/1 1/1 1/1 1/1 5 20 20 10 10 1/2 1/2 10 1/2 20 1/2 20 1/2 1
Denomination 10 1/4 1/10
1/4 5 1/4 10
1/10
1/10 5
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.
6. Field 33G: Price Per Unit

FORMAT Option G 3!a15d[5!c] (Currency) (Price) (Code)
10
MT 600
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 Indicates that more information can be found in field 72
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.
7. 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.
11
MT 600
CODES Code may contain one or more of the following codes: BROK CHGS COMM MISC FEES POST SHIN STAMP TTAX VTAX WITX Brokerage. Charges. Commission. Miscellaneous. Fees. Postage. Shipping including insurance. Stamp Duty. Transaction tax. Value added tax. Withholding tax.
USAGE RULES All adjustments must be expressed in the same currency as the amounts stated in fields 33G and 34P or 34R.
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 Lines 2-6 /8c/[additional information] [//continuation of additional information] or [/8c/[additional information]]
PRESENCE Optional
12
MT 600
DEFINITION This field specifies additional information for the Receiver. CODES One or more of the following codes may be used: BROKER PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
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 "//".
9. 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 GOZ GRM KLO LOT Fine ounce Gross ounce Gramme Kilo Lot
13
MT 600
TAL TOL UNT
Tael Tola 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 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 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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (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.
14
MT 600
11. 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). 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.
12. Field 53a: Senders Correspondent

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).
15
MT 600
The BIC must not be a BEI, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).
13. Field 57a: Account With Institution

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (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.

PRESENCE Mandatory in an optional sequence
16
MT 600
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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit
15. Field 87a: Deliverer of the Metal

PRESENCE Mandatory in an optional sequence DEFINITION This field identifies the party to which the Sender will deliver the metal sold.
17
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (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.
16. 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.

18
MT 600
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. 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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (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.
19
MT 601
MT 601 Precious Metal Option Confirmation

MT 601 Scope
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 Precious Metal Option Confirmation Status M M M M M M O M M M M M O M Tag 20 21 22 23 30 26C 31C 31G 32F 32B 33B 34a 53a 57a Field Name Transaction Reference Number Related Reference Code/Common Reference Further Identification Date Contract Agreed/Amended Identification of the Metal Earliest Exercise Date Expiry Details Unit and Amount of the Metal Strike Price Premium Price Premium Payment Senders Correspondent Account With Institution 16x 16x 8a/4!a2!c4!n4!a2!c 16x 6!n [3!a]/15x/5!a4!a[4x][//8x] 6!n 6!n/4!n/12a 3!a15d 3!a15d 3!a15d P or R A, B or D A, B or D Content/Options No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14
20
MT 601
Status O
Tag 72
Field Name Sender to Receiver Information 6*35x
Content/Options
No. 15
M = Mandatory O = Optional

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

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

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). 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: NEW Confirmation of a new precious metal option.
22
MT 601
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. Confirmation of the mutually agreed cancellation of a contract. Confirmation of the mutually agreed surrender of the option by the buyer (holder) to the seller (grantor) for compensation.
CANCEL CLOSEOUT
CODES In confirmations sent by one financial institution, Code must contain one of the following codes: CORRECT COMPLETE Retransmission due to error - to correct error(s) in a previously sent MT 601. 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).
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 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.
23
MT 601
CODES Buy/Sell Indicator must contain one of the following codes: BUY SELL The Sender is confirming an option bought The Sender is confirming an option sold
CODES Call/Put Indicator must contain one of the following codes: CALL PUT The Sender is confirming a call option The Sender is confirming a put option
CODES Style Indicator must contain one of the following codes (Error code(s): T09): A E This is an American style option This is a European style option
5. 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).
24
MT 601
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.

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 Specifies the metal is allocated 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
25
MT 601
SILV PLAT PALL RHOD RUTH OSMI IRID
Silver Platinum Palladium Rhodium Ruthenium Osmium Iridium
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 AMEG ANUG CORO BRIT DUCA FRFR GECU KRUG LBTY MAPL MEXP NSOV NOBL OSOV SAEG SECU Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET AUSTRIAN CORONA BRITANNIA DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU 50 1/1 100 1/1 4 20 50 1/1 20 1/1 50 1/1 1/1 1/1 1/1 5 1/2 1/2 10 1/2 20 1/2 1/4 5 1/4 10 1/10 5 1/10 25 1/2 20 1/2 1 Denomination 10 1/4 10 1/4 1/10 5 1/10
26
MT 601
Code STAT VREN COIN STATUE VRENELI OTHER COINS
Coin Name 20 20 10 10
Denomination 5
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 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).
8. 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.
27
MT 601
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).
9. Field 32F: Unit and Amount of the Metal

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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit
10. Field 32B: Strike Price
28
MT 601
FORMAT Option B 3!a15d (Currency) (Price)
PRESENCE Mandatory 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.
11. 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.
12. Field 34a: Premium Payment
29
MT 601
FORMAT Option P Option R 6!n3!a15d 6!n3!a15d (Date) (Currency) (Amount) (Date) (Currency) (Amount)
PRESENCE Mandatory 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).
13. Field 53a: Senders Correspondent

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).
30
MT 601
The BIC must not be a BEI, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (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 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.

31
MT 601
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver. CODES One or more of the following codes may be used: BROKER PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
32
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 Precious Metal Transfer/Delivery Order Status M O M O -----> M M M O M O O M O -----| M = Mandatory O = Optional 20 21 23 26D 32F 82a 87a 88a 72 Transaction Reference Number Related Reference Further Identification Certificate Number(s) and/or Bar Number(s) Quantity of the Metal Instructing Party Receiver of the Metal Beneficiary of the Metal Sender to Receiver Information 16x 16x 16x 30*65x 3!a15d A, B or D A, B or D A, B or D 6*35x 5 6 7 8 9 10 11 12 13 Tag 26C 25 30 72 Field Name Identification of the Metal and the Metal Account Further Account Identification Value Date Sender to Receiver Information Content/Options [3!a]/15x/5!a4!a[4x][//8x] 35x 6!n 6*35x No. 1 2 3 4
33
MT 604

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.

1. Field 26C: Identification of the Metal and the Metal Account
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. CODES When Delivery Details is present, it must contain the code CIF (Error code(s): T35).
34
MT 604
CODES Allocation must contain one of the following codes (Error code(s): T03): ALLOC UNALL Specifies the metal is allocated 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 SILV PLAT PALL RHOD RUTH OSMI IRID Gold Silver Platinum Palladium Rhodium Ruthenium Osmium Iridium
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 AMEG ANUG CORO BRIT DUCA FRFR GECU KRUG Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET AUSTRIAN CORONA BRITANNIA DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND 50 1/1 100 1/1 4 20 50 1/1 1/2 1/4 1/10 25 1/2 20 1/2 1 Denomination 10 1/4 10 1/4 1/10 5 1/10
35
MT 604
Code LBTY MAPL MEXP NSOV NOBL OSOV SAEG SECU STAT VREN COIN
Coin Name LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU STATUE VRENELI OTHER COINS 20 1/1 50 1/1 1/1 1/1 1/1 5 20 20 10 10 1/2 10 1/2 20 1/2
Denomination 5 1/4 10 1/10 5
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

FORMAT 35x
PRESENCE Optional DEFINITION This field provides further identification information on the metal account to be debited.
3. Field 30: Value Date
36
MT 604
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).

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 PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
37
MT 604

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

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 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.
38
MT 604
In all other cases, this field must contain a reference to the related transaction which is meaningful to the beneficiary of the metal.

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 TRANSFER Delivery 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 transferred/delivered.

39
MT 604
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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit
10. Field 82a: Instructing Party

PRESENCE Optional
40
MT 604
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).
12. Field 88a: Beneficiary of the Metal

PRESENCE Mandatory
41
MT 604
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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 PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
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.
42
MT 604
Additional explanatory information, which may continue on the next line, must be preceded by double slashes "//".
43
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 Precious Metal Notice to Receive Status M M O M O -----> M M O M O M O O -----| M = Mandatory O = Optional 21 23 26D 32F 82a 87a 88a 72 Related Reference Further Identification Certificate Number(s) and/or Bar Number(s) Quantity of the Metal Instructing Party Deliverer of the Metal Beneficiary of the Metal Sender to Receiver Information 16x 16x 30*65x 3!a15d A, B or D A, B or D A, B or D 6*35x 6 7 8 9 10 11 12 13 Tag 20 26C 25 30 72 Field Name Transaction Reference Number Identification of the Metal and the Metal Account Further Account Identification Value Date Sender to Receiver Information 16x [3!a]/15x/5!a4!a[4x][//8x] 35x 6!n 6*35x Content/Options No. 1 2 3 4 5
44
MT 605

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.

FORMAT 16x

45
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 Specifies the metal is allocated Specifies the metal is unallocated
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 AMEG ANUG CORO Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET AUSTRIAN CORONA 50 1/1 100 25 1/2 20 Denomination 10 1/4 10 5 1/10
46
MT 605
Code BRIT DUCA FRFR GECU KRUG LBTY MAPL MEXP NSOV NOBL OSOV SAEG SECU STAT VREN COIN BRITANNIA
Coin Name 1/1 4 20 50 1/1 20 1/1 50 1/1 1/1 1/1 1/1 5 20 20 10 10 1/2 1/2 10 1/2 20 1/2 1/2 1
Denomination 1/4 1/10
DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU STATUE VRENELI OTHER COINS
1/4 5 1/4 10
1/10
1/10 5

FORMAT 35x
47
MT 605
PRESENCE Optional DEFINITION This field contains further identification information on the metal account to be credited.

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

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.
48
MT 605
PHON TELEX ELEC
The deal was arranged by telephone. The deal was arranged by telex. 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.

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. If no related reference is available, the code NONREF must be used in this field.

FORMAT 16x
49
MT 605
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 TRANSFER Delivery Transfer

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

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
50
MT 605
GOZ GRM KLO LOT TAL TOL UNT
Gross ounce Gramme Kilo Lot Tael Tola Unit

PRESENCE Optional 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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).
51
MT 605
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).
52
MT 605
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 PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
53
MT 606
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 Precious Metal Debit Advice Status M M M O O M M O O O O Tag 20 21 26C 25 26D 30 32F 82a 87a 88a 72 Field Name Transaction Reference Number Related Reference Identification of the Metal and the Metal Account Further Account Identification Certificate Number(s) and/or Bar Number(s) Value Date Quantity of the Metal Instructing Party Receiver of the Metal Beneficiary of the Metal Sender to Receiver Information M = Mandatory O = Optional 16x 16x [3!a]/15x/5!a4!a[4x][//8x] 35x 30*65x 6!n 3!a15d A or D A or D A or D 6*35x Content/Options No. 1 2 3 4 5 6 7 8 9 10 11

There are no network validated rules for this message type.
54
MT 606

FORMAT 16x

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.

55
MT 606
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 Specifies the metal is allocated 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 SILV PLAT PALL RHOD RUTH OSMI Gold Silver Platinum Palladium Rhodium Ruthenium Osmium
56
MT 606
IRID
Iridium
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 AMEG ANUG CORO BRIT DUCA FRFR GECU KRUG LBTY MAPL MEXP NSOV NOBL OSOV SAEG SECU STAT VREN COIN Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET AUSTRIAN CORONA BRITANNIA DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU STATUE VRENELI OTHER COINS 50 1/1 100 1/1 4 20 50 1/1 20 1/1 50 1/1 1/1 1/1 1/1 5 20 20 10 10 5 1/2 1/2 10 1/2 20 1/2 1/4 5 1/4 10 1/10 5 1/10 25 1/2 20 1/2 1 Denomination 10 1/4 10 1/4 1/10 5 1/10
57
MT 606

FORMAT 35x
PRESENCE Optional DEFINITION This field contains further identification information on the metal account which has been debited.

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

FORMAT 6!n (Date)
PRESENCE Mandatory
58
MT 606
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).

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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit
59
MT 606

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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). The BIC must not be a BEI, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

60
MT 606
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver. CODES One or more of the following codes may be used: BROKER PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
61
MT 606
62
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 Precious Metal Credit Advice Status M M M O O M M O O O Tag 20 21 26C 25 26D 30 32F 82a 87a 72 Field Name Transaction Reference Number Related Reference Identification of the Metal and the Metal Account Further Account Identification Certificate Number(s) and/or Bar Number(s) Value Date Quantity of the Metal Instructing Party Deliverer of the Metal Sender to Receiver Information M = Mandatory O = Optional 16x 16x [3!a]/15x/5!a4!a[4x][//8x] 35x 30*65x 6!n 3!a15d A or D A or D 6*35x Content/Options No. 1 2 3 4 5 6 7 8 9 10

There are no network validated rules for this message type.

63
MT 607
FORMAT 16x

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.

Where
64
MT 607
Subfield 1 2 3 4 5 6
Format [3!a] /15x /5!a 4!a [4x] [//8x] Delivery Details Availability Allocation Type Denomination Form
Name
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 Specifies the metal is allocated Specifies the metal is unallocated
65
MT 607
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
MT 607
USAGE RULES Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK). Form specifies the physical form of the metal.

FORMAT 35x
PRESENCE Optional DEFINITION This field contains further identification information on the metal account which has been credited.

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

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

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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit

68
MT 607
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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

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, ie, must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

69
MT 607
PRESENCE Optional DEFINITION This field specifies additional information for the Receiver. CODES One or more of the following codes may be used: BROKER PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
70
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 Statement of a Metal Account Status M M O M M -----> O -----| M O -----> O -----| M = Mandatory O = Optional * See Field Specifications 65 Forward Available Balance 1!a6!n3!a15d 9 62a 64 Closing Balance Closing Available Balance F or M 1!a6!n3!a15d 7 8 61 Statement Line * 6 Tag 20 26C 25 28 60a Field Name Transaction Reference Number Identification of the Metal and the Metal Account Further Account Identification Statement Number/Sequence Number Opening Balance 16x [3!a]/15x/5!a4!a[4x][//8x] 35x 5n[/2n] F or M Content/Options No. 1 2 3 4 5
71
MT 608

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.

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

where: Subfield 1 Format [3!a] Delivery Details Name
72
MT 608
Subfield 2 3 4 5 6
Format /15x /5!a 4!a [4x] [//8x] Availability Allocation Type Denomination Form
Name
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 Specifies the metal is allocated Specifies the metal is unallocated
73
MT 608
NETWORK VALIDATED RULES Delivery Details must not be present, as CIF does not apply. In this message, LOCO always applies (Error code(s): C87).
74
MT 608
USAGE RULES Availability specifies the availability of the metal (eg, LONDON, ZURICH, NEW YORK). Form specifies the physical form of the metal.

FORMAT 35x
PRESENCE Optional DEFINITION This field contains further identification information on 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 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) opening balance, whether it is a debit or credit balance, the date, the unit of metal and amount of the balance.
75
MT 608
CODES D/C Mark must contain one of the following codes (Error code(s): T51): C D 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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola 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). 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
76
MT 608
FORMAT 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x] [34x]
where: Subfield 1 2 3 4 5 6 7 8 9 Format 6!n [4!n] 2a [1!a] 15d 1!a3!c 16x [//16x] [34x] Date (YYMMDD) Entry Date (MMDD) Debit/Credit Mark Funds Code (3rd character of the currency code, if needed) Amount Transaction Type Identification Code Reference for the Account Owner Account Servicing Institutions Reference Supplementary Details Name
PRESENCE Optional DEFINITION This field contains the details of each transaction. CODES Subfield 3, Debit/Credit Mark, must contain one of the following codes (Error code(s): T51): D C Debit Credit
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:
77
MT 608
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 CHG COM DIV EQA INT MSC PCH RTI SAL STO TRF VDA Brokerage fee Charges and other expenses Commission Dividends-Warrants Equivalent amount Interest Miscellaneous Purchase Returned item Sale Standing order Transfer 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)
78
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.
79
MT 608
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 D 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 GOZ GRM KLO LOT TAL TOL UNT Fine ounce Gross ounce Gramme Kilo Lot Tael Tola Unit
NETWORK VALIDATED RULES Date must be a valid date expressed as YYMMDD (Error code(s): T50).
80
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 D 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 GOZ GRM KLO LOT TAL Fine ounce Gross ounce Gramme Kilo Lot Tael
81
MT 608
TOL UNT
Tola 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 D 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 GOZ GRM KLO LOT Fine ounce Gross ounce Gramme Kilo Lot
82
MT 608
TAL TOL UNT
Tael Tola 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.
83
MT 609
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 Statement of Metal Contracts Status M M M O -----> M -----> M -----> M -----| -----| O -----| M = Mandatory O = Optional 72 Sender to Receiver Information 6*35x 8 68a Transaction Details B or C 7 26C Identification of the Metal [3!a]/15x/5!a4!a[4x][//8x] 6 23 Further Identification 16x 5 Tag 27 20 31C 30 Sequence of Total Transaction Reference Number Statement Date Date Prepared Field Name Content/Options 1!n/1!n 16x 6!n 6!n No. 1 2 3 4

C1 Field 68B must be used when the immediately preceding field 23 contains either SPOTS or FORWARDS (Error code(s): C85).
84
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.

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 on the metal contracts outstanding at the date specified in field 31C.

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).
85
MT 609
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).

FORMAT 16x
PRESENCE Mandatory DEFINITION This field identifies the type of contract listed in the sequence of fields 26C and 68a immediately following it.
86
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): SPOTS FORWARDS OPTIONS The following is a list of all undelivered spots as at a specified date. The following is a list of all outstanding forward contracts as at a specified date. The following is a list of all unexercised options as at a specified date.

where: Subfield 1 2 3 4 5 6 Format [3!a] /15x /5!a 4!a [4x] [//8x] Delivery Details Availability Allocation Type Denomination Form Name
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 Specifies the metal is allocated Specifies the metal is unallocated
87
MT 609
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 AMEG ANUG CORO BRIT DUCA FRFR GECU KRUG LBTY MAPL MEXP NSOV NOBL Coin Name AMERICAN EAGLE AUSTRALIAN NUGGET AUSTRIAN CORONA BRITANNIA DUCAT FOURFOLD SINGLE FRENCH FRANCS GOLDEN ECU KRUGER RAND LIBERTY DOLLAR MAPLE MEXICAN PESO NEW SOVEREIGN NOBLE 50 1/1 100 1/1 4 20 50 1/1 20 1/1 50 1/1 1/1 1/2 10 1/2 20 1/2 1/4 5 1/4 10 1/10 5 1/10 25 1/2 20 1/2 1 Denomination 10 1/4 10 1/4 1/10 5 1/10
88
MT 609
Code OSOV SAEG SECU STAT VREN COIN
Coin Name OLD SOVEREIGN SILVER AMERICAN EAGLE SILVER ECU STATUE VRENELI OTHER COINS 1/1 1/1 5 20 20 10 10 1/2
Denomination
7. Field 68a: Transaction Details

FORMAT Option B Option C 6!n6!n16x/1!a3!a15d3!a15d/6!n3!a15d 4a/4a/1!a[6!n]3!a15d3!a15d3!a15d3!a15d
where Option B is: Subfield 1 2 3 4 5 6 7 8 Format 6!n 6!n 16x /1!a 3!a15d 3!a15d /6!n 3!a15d Trade Date Maturity Date Contract Number Indicator Unit and Quantity of Metal Currency and Price Per Unit Value Date (of the Consideration) Currency and Consideration Name
89
MT 609
and where Option C is: Subfield 1 2 3 4 5 6 7 8 Format 4a /4a /1!a [6!n] 3!a15d 3!a15d 3!a15d 3!a15d Buy/Sell Indicator Call/Put indicator Style Indicator Date Contract Agreed Unit and Amount of the Underlying Metal Currency and Strike Price of the metal option per unit of the underlying metal Currency and Premium Price per unit of the underlying metal Currency and Premium Payment of the metal option. Name
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 S The Sender bought the metal 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 GOZ GRM KLO Fine ounce Gross ounce Gramme Kilo
90
MT 609
LOT TAL TOL UNT
Lot Tael Tola Unit
CODES In option C, subfield 1, Buy/Sell Indicator, must contain one of the following codes: BUY SELL The Sender has bought the option The Sender has sold the option
CODES In option C, subfield 2, Call/Put Indicator, must contain one of the following codes: CALL PUT The option is a call 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 E This is an American style option This is a European style option
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).
91
MT 609
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.

PRESENCE Optional DEFINITION This field specifies additional information for the Receiver.
92
MT 609
CODES One or more of the following codes may be used: BROKER PHON TELEX ELEC Identification of the broker negotiating the contract on behalf of one of the parties. The deal was arranged by telephone. The deal was arranged by telex. 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.
93
MT 690
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.
94
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.
95
MT 692
MT 692 Request for Cancellation

Please refer to Category n - Common Group Messages, Chapter n92 Request for Cancellation for details concerning this message type.
96
MT 695
MT 695 Queries
Please refer to Category n - Common Group Messages, Chapter n95 Queries for details concerning this message type.
97
MT 696
MT 696 Answers
Please refer to Category n - Common Group Messages, Chapter n96 Answers for details concerning this message type.
98
MT 698
MT 698 Proprietary Message

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

Please refer to Category n - Common Group Messages, Chapter n99 Free Format Message for details concerning this message type.
100
Table Of Contents
Table of Contents
Legal Notices . . . . . . . . . . . . . Overview . . . . . . . . . . . . . Added Message Types . . . . . . . . . . Removed Message Types . . . . . . . . . Modified Message Types . . . . . . . . . MT 600 Precious Metal Trade Confirmation . . . . . . MT 600 Scope . . . . . . . . . . . . MT 600 Format Specifications . . . . . . . . MT 600 Network Validated Rules . . . . . . . . MT 600 Usage Rules . . . . . . . . . . MT 600 Field Specifications (updated) . . . . . . 1. Field 20: Transaction Reference Number . . . . . 2. Field 21: Related Reference . . . . . . . . 3. Field 22: Code/Common Reference . . . . . . 4. Field 30: Date Contract Agreed/Amended . . . . . 5. Field 26C: Identification of the Metal . . . . . . 6. Field 33G: Price Per Unit . . . . . . . . 7. Field 71C: Details of Adjustments . . . . . . 8. Field 72: Sender to Receiver Information . . . . . 9. Field 32F: Quantity of the Metal . . . . . . . 10. Field 87a: Receiver of the Metal (updated) . . . . 11. Field 34P: Consideration . . . . . . . . 12. Field 53a: Senders Correspondent (updated) . . . . 13. Field 57a: Account With Institution (updated) . . . . 14. Field 32F: Quantity of the Metal . . . . . . 15. Field 87a: Deliverer of the Metal (updated) . . . . 16. Field 34R: Consideration . . . . . . . . 17. Field 57a: Account With Institution (updated) . . . . MT 601 Precious Metal Option Confirmation . . . . . . MT 601 Scope . . . . . . . . . . . . MT 601 Format Specifications . . . . . . . . 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 23: Further Identification . . . . . . . 5. Field 30: Date Contract Agreed/Amended . . . . . 6. Field 26C: Identification of the Metal . . . . . . 7. Field 31C: Earliest Exercise Date . . . . . . . 8. Field 31G: Expiry Details . . . . . . . . 9. Field 32F: Unit and Amount of the Metal . . . . . 10. Field 32B: Strike Price . . . . . . . . . 11. Field 33B: Premium Price . . . . . . . . 12. Field 34a: Premium Payment . . . . . . . 13. Field 53a: Senders Correspondent (updated) . . . . 14. Field 57a: Account With Institution (updated) . . . . 15. 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 (updated) . . . . . . 1. Field 26C: Identification of the Metal and the Metal Account 2. Field 25: Further Account Identification . . . . . 3. Field 30: Value Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 3 3 3 4 4 4 5 5 6 6 6 7 8 8 10 11 12 13 14 15 15 16 16 17 18 18 20 20 20 21 21 21 21 22 22 23 24 25 27 27 28 28 29 29 30 31 31 33 33 33 34 34 34 34 36 36
Table Of Contents
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 (updated) . . . . . 11. Field 87a: Receiver of the Metal (updated) . . . . 12. Field 88a: Beneficiary of the Metal (updated) . . . 13. 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 (updated) . . . . . . 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 (updated) . . . . . 11. Field 87a: Deliverer of the Metal (updated) . . . . 12. Field 88a: Beneficiary of the Metal (updated) . . . 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 (updated) . . . . . . 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 (updated) . . . . . 9. Field 87a: Receiver of the Metal (updated) . . . . 10. Field 88a: Beneficiary of the Metal (updated) . . . 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 (updated) . . . . . . 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 (updated) . . . . . 9. Field 87a: Deliverer of the Metal (updated) . . . . 10. Field 72: Sender to Receiver Information . . . . MT 608 Statement of a Metal Account . . . . . . MT 608 Scope . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37 . 38 . 38 . 39 . 39 . 39 . 40 . 41 . 41 . 42 . 44 . 44 . 44 . 45 . 45 . 45 . 45 . 45 . 47 . 48 . 48 . 49 . 49 . 50 . 50 . 51 . 51 . 52 . 52 . 54 . 54 . 54 . 54 . 54 . 55 . 55 . 55 . 58 . 58 . 58 . 59 . 60 . 60 . 60 . 61 . 63 . 63 . 63 . 63 . 63 . 63 . 64 . 64 . 67 . 67 . 67 . 68 . 68 . 69 . 69 . 71 . 71 .
ii
Table Of Contents
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 . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. 71 . . 72 . . 72 . . 72 . . 72 . . 72 . . 75 . . 75 . . 75 . . 76 . . 80 . . 81 . . 82 . . 84 . . 84 . . 84 . . 84 . . 85 . . 85 . . 85 . . 85 . . 86 . . 86 . . 86 . . 87 . . 89 . . 92 . . 94 . . 95 . . 96 . . 97 . . 98 . . 99 . . 100 .
iii

Swift Standards Category 6 Treasury Markets Precious Metals MT600 MT699

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Swift Standards Category 6 Treasury Markets Precious Metals MT600 MT699

Enviado por

Direitos autorais:

Formatos disponíveis

SWIFTStandards

Category 6 Treasury Markets Precious Metals

Standards Release Guide 2003 - Final edition - February 2003

Added Message Types

Removed Message Types

Modified Message Types

Standards Release Guide 2003 - Final edition - February 2003

MT 600 Precious Metal Trade Confirmation

MT 600 Format Specifications

Optional Sequence B Precious Metal Bought

Standards Release Guide 2003 - Final edition - February 2003

Tag 32F 87a 34P 53a 57a

MT 600 Network Validated Rules

MT 600 Usage Rules

Standards Release Guide 2003 - Final edition - February 2003

MT 600 Field Specifications

2. Field 21: Related Reference

Standards Release Guide 2003 - Final edition - February 2003

3. Field 22: Code/Common Reference

CANCEL EXOPTION NOTICE

Standards Release Guide 2003 - Final edition - February 2003

4. Field 30: Date Contract Agreed/Amended

5. Field 26C: Identification of the Metal

Standards Release Guide 2003 - Final edition - February 2003

Standards Release Guide 2003 - Final edition - February 2003

Denomination 10 1/4 1/10

6. Field 33G: Price Per Unit

Standards Release Guide 2003 - Final edition - February 2003

7. Field 71C: Details of Adjustments

Standards Release Guide 2003 - Final edition - February 2003

8. Field 72: Sender to Receiver Information

Standards Release Guide 2003 - Final edition - February 2003

9. Field 32F: Quantity of the Metal

Standards Release Guide 2003 - Final edition - February 2003

TAL TOL UNT

Tael Tola Unit

10. Field 87a: Receiver of the Metal

Standards Release Guide 2003 - Final edition - February 2003

11. Field 34P: Consideration

12. Field 53a: Senders Correspondent

Standards Release Guide 2003 - Final edition - February 2003

13. Field 57a: Account With Institution

14. Field 32F: Quantity of the Metal

PRESENCE Mandatory in an optional sequence

Standards Release Guide 2003 - Final edition - February 2003

15. Field 87a: Deliverer of the Metal

Standards Release Guide 2003 - Final edition - February 2003

16. Field 34R: Consideration

17. Field 57a: Account With Institution

Standards Release Guide 2003 - Final edition - February 2003

Standards Release Guide 2003 - Final edition - February 2003

MT 601 Precious Metal Option Confirmation

MT 601 Format Specifications

Standards Release Guide 2003 - Final edition - February 2003

Field Name Sender to Receiver Information 6*35x

MT 601 Network Validated Rules

MT 601 Usage Rules

MT 601 Field Specifications

Standards Release Guide 2003 - Final edition - February 2003

2. Field 21: Related Reference

3. Field 22: Code/Common Reference

Standards Release Guide 2003 - Final edition - February 2003

4. Field 23: Further Identification

Buy/Sell Indicator Call/Put Indicator Style Indicator