The following illustrates the mapping of a single-transaction MT 101 onto an equivalent MT 103:
National and Banking practices may differ from the mapping shown above.
Mapping onto an MT 103 core is shown for illustration purposes. A multiple MT 101 could also be mapped onto an MT 102 or onto several MTs 103. Mapping onto an MT103+ may require more constraints.
Notes:
Fields 20, 21R, 28D, 51A, 25, 21F and 25A should not be mapped onto the MT 103.
(a): If both field 50a Instructing Party (50C or L) or field 50a Ordering Customer (50G or H) are present in the MT 101 then, per default, 50a Ordering Customer should be mapped onto the subsequent MT 103, unless 50a Instructing Party is present in sequence B. If 50a Instructing Party is present in any sequence B, 50a Instructing Party should be mapped to field 50a of the MT 103.
(b): Field 30 of the MT 101 is used to construct subfield 1 of field 32A of the MT 103. Whenever relevant, the Interbank Settlement Date of the MT 103 takes into account the instruction codes present in field 23E of the MT 101 (eg RTGS).
(c): As a general rule, field 23E of the MT 101 is mapped to field 23E of the MT 103.However codes CMSW, CMTO, CMZB, NETS and URGP should be mapped in field 70 of the MT 103.
Remarks:
Some codes require specific mapping action at the executing institution, eg:
RTGS mapped from the MT 101 to the MT 103 may require the payment to be executed via an RTGS system or code //RT to be added in field 57a of the MT 103
CHQB in the MT 101 will lead to the issuance of a cheque by the executing institution when fields 56a and 57a are not present or by specified correspondent when fields 56a and/or 57a are present.
PHON in the MT 101 should be mapped to PHOB in the MT 103
(d): When present, field 33B of the MT 101 is mapped onto field 33B of the MT 103. If field 33B is not present in the MT 101, field 32B of the MT 101 is mapped onto field 33B of the MT 103. In all other cases, field 32B of the MT 101 is used to build subfields 2 and 3 of field 32A of the MT 103.
Remarks:
Charges for the processing of the MT 101 are to be accounted for separately and posted to the account mentioned in field 25A of the MT 101, when present. Below charges relate to the processing of the MT 103 only.
If field 71A of the MT 101 contains SHA, field 32B of the MT 101 is mapped to subfields 2 and 3 of field 32A of the MT 103.
If field 71A of the MT 101 contains OUR and charges are known, charges for the entire transaction are added to field 32B of the MT 101 and mapped in field 32A of the MT 103. In this case, field 71G of the MT 103 may be present.
If field 71A of the MT 101 contains OUR and charges are not known, field 32B of the MT 101 is mapped onto field 32A of the MT 103 and field 71G is not present (in this case, the executing institution will be charged back by the next party(ies) in the transaction chain).
If field 71A contains BEN, charges of the executing bank are deducted from field 32B from the received MT 101. The result is mapped onto field 32A of the MT 103. In this case, charges of the executing bank will be quoted into field 71F of the MT 103.
(e): Fields 56a and 57a:
If both fields 56a and 57a are not present in the MT 101, the MT 101 triggers a book transfer at the executing institution or issuance of a cheque.
If both fields 56a and 57a are present, field 56a maps to the Receiver of the MT 103 and field 57a is mapped in field 57a of the MT 103.
If only field 57a is present in the MT 101, field 57a is mapped onto Receiver of the MT 103.
(f): It is not mandatory to map field 21 of the MT 101 in the MT 103. However, if desired, it should be mapped onto field 70 of the MT 103 as follows: :70:/ROC/value.
