MT 204 Field Specifications
11. Field 72: Sender to Receiver Information
FORMAT
6*35x |
(Narrative - Structured Format) |
The following line formats must be used:
Line 1 |
/8c/[additional information] |
|
Lines 2-6 |
[//continuation of additional information]
or
[/8c/[additional information]] |
|
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver or another party specified. This information is relevant to the specific transaction in the sequence.
CODES
One or more of the following codes may be used, placed between slashes ('/'):
ACC |
Instructions following are for the account with institution |
BNF |
Information following is for the beneficiary |
CUST |
The amount to be debited corresponds to a margin call on segregated customer (client) trades/account |
CUSTMAR |
The amount to be debited corresponds to initial/original margin on customer trades (customer account margin) |
CUSTVAR |
The amount to be debited corresponds to variation margin on customer trades (customer account variation) |
HOUSE |
The amount to be debited corresponds to a margin call on house trades (proprietary funds) |
HOUSEMAR |
The amount to be debited corresponds to initial/original margin on house trades (house account margin) |
HOUSEVAR |
The amount to be debited corresponds to variation margin on house trades (house account variation) |
METALS |
Metals call |
MKTMAR |
The amount to be debited corresponds to initial/original margin on market-maker (specialist) trades/account (market-maker account margin) |
MKTMKR |
The amount to be debited corresponds to a margin call on market-maker (specialist) trades/account |
MKTVAR |
The amount to be debited corresponds to variation margin on market-maker (specialist) trades/account (market-maker account variation) |
MMPLDG |
Market-maker pledge |
OPTPREM |
Options premium |
REC |
Instructions following are for the Receiver |
TENDER |
The amount to be debited corresponds to a payment in respect of a tender (delivery) |
VARIATN |
General variation |
XMGN |
Cross-margin account (covers positions hedged, offset or spread over two exchanges) |
XMGNMAR |
Cross-margin account margin (for initial/original margin) |
XMGNVAR |
Cross-margin account margin (for variation margin) |
The codes /REJT/ or /RETN/ may be used in this field. If either of these codes is used in the first position of the first line, it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.
USAGE RULES
Field 72 must never be used for information for which another field is intended.
Each item of information contained in this field must be preceded by a code which specifically indicates the party for which it is intended.
Codes must be placed between slashes and at the beginning of a line. Additional explanatory information, which may be continued on the next lines, is preceded by a double slash '//'.
Narrative text that is not qualified by a code, must start with a double slash '//' on a new line, and, should preferably be the last information in this field.
It is strongly recommended to use the standard codes. However, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structure of this field.
Use of field 72, particularly with uncoded instructions, may cause delay, because in automated systems, the presence of this field will normally require manual intervention.
This field may contain ERI to transport dual currencies, as explained in the chapter 'Euro - Impact on Category 2 Message Standards'.