6*35x(Narrative - Structured 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]] |
|
Optional
This field specifies additional information for the Receiver or other party specified. This information is relevant to the specific transaction in the sequence.
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 |
| INS |
The instructing institution which instructed the Sender to execute the transaction |
| INT |
Instructions following are for the intermediary |
| PHON |
Please advise account with institution by phone |
| PHONBEN |
Please advise/contact beneficiary/claimant by phone |
| PHONIBK |
Please advise intermediary by phone |
| REC |
Instructions following are for the Receiver |
| TELE |
Please advise the account with institution by the most efficient means of telecommunication |
| TELEBEN |
Please advise the beneficiary/claimant by the most efficient means of telecommunication |
| TELEIBK |
Please advise the intermediary by the most efficient means of telecommunication |
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.
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'.
In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.
