Show/Hide TOC

MT 102 STP Field Specifications

29. Field 72: Sender to Receiver Information

FORMAT

6*35x (Narrative Structured Format)

The following line formats 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)

PRESENCE

Optional in mandatory sequence C

DEFINITION

This field specifies additional information for the Receiver.

CODES

Unless bilaterally agreed otherwise between the Sender and the Receiver, the following code may be used in Code, placed between slashes ('/'):

INS Instructing institution The instructing institution which instructed the Sender to execute the transaction.

NETWORK VALIDATED RULES

If the code /INS/ is used at the beginning of a line, it must be followed by a valid financial institution BIC and be the only information on that line (Error code(s): T27,T28,T29,T44,T45,T46).

If the code /INS/ is present at the beginning of a line, it must not be used again at the beginning of any other line (Error code(s): T47).

If the code /INS/ is used anywhere else than at the beginning of a line, it is treated as free text and is ignored as far as validation is concerned. In this case, there is no validation of the following BIC either.

The codes /REJT/ or /RETN/ must not be used in this field (Error code(s): T81).

This field must not include ERI (Error code(s): T82).

USAGE RULES

Field 72 must never be used for information for which another field is intended.

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.

Use of field 72 with uncoded instructions is not allowed.

It is strongly recommended to use the standard code proposed above. In any case, where bilateral agreements covering the use of codes in this field are in effect, the code must conform to the structured format of this field.