Nasdaq Nordic and Baltic have announced a number of changes to the INET Nordic Cash Equity trading system to be introduced in April, 2016.
This reminder summarizes the changes going into production on Monday April 25, 2016.
1. EUSIPA instrument code for Exchange Traded Products
As previously announced in IT-Notice 16/16 , Nasdaq Nordic is introducing an additional reference data field to further enhance the identification of Exchange Traded Products on Nasdaq Stockholm, Nasdaq Helsinki and Nasdaq Copenhagen. The addition of a new reference data field, namely the EUSIPA instrument code, has been previously communicated within the GCF/TIP release notification on January 25, 2016. The INET ITCH protocol is not affected.
Genium Consolidated Feed (GCF) will be updated to version 3.2. A new reference data field will be added for EUSIPA code.
2. Knock-Out Buy-Back and Buy-Back Note Codes for Exchange Traded Products
As previously announced in IT-Notice 17/16 , Nasdaq Nordic is introducing two additional note codes for Exchange Traded Products on Nasdaq Stockholm, Nasdaq Helsinki and Nasdaq Copenhagen.When the Knock-Out Buy-Back or the Buy-Back note codes are applied, only selling back to the market maker is allowed. The specific uses of these additional note codes are reflected in the Market Model.
3. Allowing true Mid-point matching for Pegged Large In Scale (LIS) Orders
As previously announced in IT-Notice 19/16 , Nasdaq Nordic desided that the pegging functionality will be enhanced, allowing matching at the true Mid-point, up to four decimals.
Example:
The Member sends in a Buy Mid-point Pegged Non-display LIS Order.
BBO=100,10---100,20 (0,10 is valid tick)
The Buy Mid-point Pegged Order is placed in the book as a Non-display order at 100,15 (off-tick and two decimals). The Order may match towards any Sell Order that is priced at 100,10 or lower (or a Sell Mid-point Pegged Non-display LIS Order).
Note that a Non-displayed Order has to be large in scale (LIS) at the time of entry. If the volume is reduced due to a partial execution, the Order with limit price remains non-displayed even when smaller than large in scale (LIS).
4. Smart Order Routing, routing instruction handling
As previously announced in IT-Notice 22/16 , Nasdaq Nordic had decided to align the Order validation rules and order handling between the two methods to populate tag 76, in order to avoid unnecessary Order rejects.
The change will mean that Nasdaq will align the Order validation rules to follow current method used for Default routing strategy (on FIX port level for automatic population of tag 76). This means that going forward also the indicated routing strategy (at Order entry via ExecBroker field, tag 76) will be ignored and will not be applied to such Orders which have such other order conditions that normally would lead to a reject by the router (for example pegging instruction). In those cases the Order will be treated as a regular non-routable order designated for the Lit Order book, honoring the other order conditions specified by the Member.
Protocol specifications
Current and future versions of INET protocol specifications are available at the Nasdaq Nordic Technical Information website, under INET Nordic Protocol Specifications . GCF/TIP protocols are available under Genium Consolidated Feed Protocol Specifications .
INET Nordic Market Model:
These changes will be reflected in the Market Model effective as of April 25, 2016 .
Support
For technical questions, please contact Nasdaq Cash Equity Operations: Tel: +46 8 405 6410, E-mail: operator@nasdaq.com
Best regards,
Nasdaq Nordic and Nasdaq Baltic
Nasdaq Nordic represents the common offering by Nasdaq Copenhagen A/S, Nasdaq Helsinki Ltd, Nasdaq Iceland h.f. and Nasdaq Stockholm AB. Nasdaq Baltic represents the common offering by Nasdaq Tallinn AS, Nasdaq Riga AS, and AB Nasdaq Vilnius.