For MT541, Field 35B indicates the Identification of the Financial Instrument. According to SWIFT Specification 2017 https://www2.swift.com/uhbonline/books/public/en_uk/us5mb_20160722/index.htm, ISIN is used at the beginning of Identification of Security and must be composed of uppercase letters only, for example ":35B:ISIN US0123456704". In SWIFT plugin 5.16.0, we added an internal validation for MT 541 Field 35B, i.e., when the incoming message including the Identification of Security, the SWIFT plugin will validate if the string starts with "ISIN" in uppercase. 

Because the "ISIN+Space" must exist at the beginning of Identification of Security, the SWIFT plugin's parser will have the output of Identification of Security to have the complete Identification of Security data value, such as "<ISINIdentifier>ISIN US0123456704</ISINIdentifier>"

This behavior is different from the previous version 5.15.0. With version 5.15.0, the XML output does not include the "ISIN+Space", e.g.,  " <ISINIdentifier>US0123456704</ISINIdentifier>, as we had assumed that the incoming Swift messages will always have the first 5 characters of this 35B field starts with "ISIN ". This worked well when the messages  directly received from Swift network, but may miss the validation if the message is from other data sources. Now, we have added the validation to ensue the Identification of Security starts with "ISIN" according to swift specification. 

Validation rules for MT Parser and Renderer in SWIFT plugin 5.16.0:
===========
There are two parts in field 35B: Identification of security and/or description of security. Format: [ISIN1!e12!c][4*35x]

For identification of security:
1. It should be in format ISIN [A-Z0-9]{12}; 
2. If 'isin' is used instead of 'ISIN' it throws error T12:"ISIN needs to be in upper case";
3. For any other violation it throws error T12:"Invalid format of ISIN";

For description of security:
4. Description of security field is free format.
5. The maximum number of lines can be 4 each having 35 characters.
If this is violated it throws error T12:"Invalid format of ISIN".
​
Examples:
Valid cases:
MT361_2017
:35B:ISA2C4E6G8I0K2
Valid case:
Considers it as Description of security
MT600_2016
:35B:REJT AB1234512345
Valid case:
Considers it as Description of security
MT341_2017
:35B:ISIN BE0000120628
BELGO ORD
Invalid cases:
MT600_2017
:35B:isin 12CHARACTERS
===========

For MX Parser and Renderer:

The MX Parser and Renderer can accept only 12 characters. Customer might need to apply substring in MX when both MT and MX are involved.

<FinInstrmDtls>
<Id>
<ISIN>GB0123456789</ISIN>
</Id>
</FinInstrmDtls>


 

There are some changes made for the processing of 35B field (e.g, in MT541) in TIBCO ActiveMatrix BusinessWorks(TM) Plug-in for SWIFT according to the SWIFT 2017 MT specification

Operation Systems: All

For customers who migrates their BW Swift plugin project from v5.15.0 to v5.16.0, string subtraction on the Identification of the security needs to be applied to retrieve the 12 characters ID.