Alternative LMF mapping for Tag 35B

The documentation provided here presents an alternative LMF mapping of Tag 35B, using the format given by the Usage Rules.

In the SWIFT User Handbook, the Usage Rules for 35B state the following:

When an ISIN identifier is not used, one of the following codes must be used as the first characters of the Description of Security (Subfield 2):
  • [/2!a/] The ISO two-digit country code, followed by the national scheme number.
  • [/TS/] Followed by the ticker symbol.
  • [/XX/] Bilaterally agreed, or proprietary scheme which can be further identified by a code, or short description identifying the scheme used.
  • [/4!c/] Code identifying the type of security identifier used. this code must be one published by ISO 20022 (ExternalFinancialInstrumentIdentificationTypeCode).

Since Usage Rules are not enforced on the SWIFT Network, the SWIFT component does not enforce these rules either. Although SWIFT has suggested an alternative format for 35B, it is not validated. It is therefore up to you, as a user of this format, to ensure that it conforms to the format expected by the recipient of the message.

In the LMF maps, Tag 35B is treated as a simple text field, either with, or without an ISIN.

It is possible, however, to amend the LMF maps to separate these fields and map them individually to and from the LMF, if that is a requirement of your system.

Note: This alternative LMF mapping has not been incorporated into the LMF maps in the pack, and so any implementation of these rules must be reapplied to subsequent releases of the pack.

See the example for details.