In addition to narrative text, structured text with the following formats may be used:
Optional
This field specifies additional information for the Receiver or other party specified.
Unless bilaterally agreed otherwise between the Sender and the Receiver, one of the following codes must be used placed between slashes ('/'):
Field 72 must never be used for information for which another field is intended.
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.
It is strongly recommended to use the standard codes proposed above. 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.
Each item for which a code exists must start with that code and may be completed with additional information.
Each code used must be between slashes and appear at the beginning of a line. It may be followed by additional narrative text.
Narrative text relating to a preceding code, which is continued on the next line(s), must start with a double slash '//', and, if used, must begin on a new line. Narrative text should preferably be the last information in this field.
The codes REJT/RETN may be used in this field. If either of these codes is used in the first position of the first line, placed between slashes ('/'), it is mandatory to follow the Generic Payment Reject Mechanism described in Standards Usage Guidelines.
This field may include ERI to transport dual currencies, as specified in the chapter entitled Euro-Impact on Category 1 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.