 6*35x |
(Narrative) |
The following line format must be used:
| Line 1 |
/8c/[additional information] |
(Code)(Narrative) |
| Lines 2-6 |
[//continuation of additional information]or[/8c/[additional information]] |
(Narrative)or(Code)(Narrative) |
Optional in optional sequence C
This field specifies additional information for the Receiver and applies to the whole message.
One of the following codes, or bilaterally agreed codes, may be used in Code:
If code VALD is used:
it must appear in the first six characters of the first line and in no other place, followed by a date expressed as YYYYMMDD and the end of line separator (that is :72:/VALD/YYYYMMDDCrLf) (Error code(s): C58).
If code SETC is used:
it must appear in the first six characters of the second line and in no other place and /SETC/ must be followed by a valid ISO 4217 currency code and the end of line code, that is CrLf (Error code(s): C59)
the first six characters of the first line must be /VALD/ (Error code(s): C59)
If the code SRCE is used:
/SRCE/ must be at the start of the third line and in no other place (Error code(s): C59)
the first six characters of the second line must be /SETC/ (Error code(s): C59)
Code must not be UTI, PUTI, USI or PUSI (Error code(s): T49).
Code must not be FIX, SETC, SRCE or VALD (Error code(s): T70).
Each code used must be put between slashes and appear at the beginning of a line.
All alphabetic characters in a code must be in upper case.
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.
Field 72 must not be used for information for which another field is intended.
The use of this field with unstructured text may require manual intervention and thus cause delay in automated systems.
If the scope of operation (field 94A) is ASET and the advice relates to the fixing of a Non Deliverable Forward (NDF), the reference of the opening confirmation must appear on the first line, preceded by /FIX/. If the scope of operation is ASET and the advice relates to the opening of an NDF, its valuation date has to be confirmed on the first line of this field, preceded by /VALD/ and the settlement currency on the second line, preceded by /SETC/.
The settlement currency (/SETC/) may be populated with 'XXX'.
If the first six characters of the first line are equal to /VALD/, if the settlement currency of the non deliverable trade is known, then the second line must be present and contain /SETC/ followed by a currency code, and the end of line code, that is CrLf .
Optionally the settlement rate source for cross currency NDF can be confirmed on the third line.
The settlement rate source is only to be used:
in conjunction with a bilaterally agreed master confirmation agreement and
where the transaction is a cross currency NDF, that is, where /SETC/ is not followed by USD.
Where available, the settlement rate source should conform to the 1998 FX and Currency Option Definitions (the FX definitions, as published by the International Swaps and Derivatives Association, Inc., the Emerging Markets Traders Association and The Foreign Exchange Committee) as amended and supplemented from time to time. Otherwise, this may be a bilaterally agreed value.
Settlement rate source may optionally be followed by a time in format /HHMM, which refers to the local time of the centre in which it is published, for example, RCE/EUR1 or SRCE/ECB37 USD/EUR (where the definitions include the time), or SRCE/EUR3 or SRCE/TKFE USD/EUR/1500 (where the definitions do not include a time).
