TT® FIX Order Routing

Identifying instruments in order-routing messages

Identifying instruments in order-routing messages

This page outlines the various message tags used by FIX order routing sessions to identify instruments.

FIX Tag Descriptions

Tag Directory

Click the links below to navigate to the documentation for that tag.

Tag Field Name Description
48 SecurityID TT security ID that uniquely identifies the instrument in the TT platform.
22 SecurityIDSource Source for the value of tag 48 (SecurityID).
207 SecurityExchange Name of the market where the instrument trades.
100 ExDestination Name of the sub-market where the instrument trades.
55 Symbol Exchange-provided product symbol for the tradable product.
167 SecurityType Asset class of the instrument.
461 CFICode Type of security using ISO 10962 standard, Classification of Financial Instruments (CFI code) values. ISO 10962 is maintained by ANNA (Association of National Numbering Agencies) acting as Registration Authority.
200 MaturityMonthYear Month and year the instrument reaches maturity in the format YYYYMM.
205 MaturityDay Day of expiration for the instrument.
202 StrikePrice Strike price for an option.
201 PutorCall Whether the option represents a put or call.
541 MaturityDate Maturity date in format YYYYMMDD.
1194 ExerciseStyle Type of exercise for a derivatives security.
454 NoSecurityAltID Number of alternate security IDs contained in this repeating group.
>455 SecurityAltID Alternate ID for an instrument or security, typically for display purposes.
>456 SecurityAltIDSource Identifies class or source of the SecurityAltID (455) value.
>16207 BloombergSecurityExchange Name of the market where the instrument of the SecurityAltID (Tag 455) value trades.
555 NoLegs Number of legs in the repeating group.
>616 LegSecurityExchange Multi-leg instrument's individual security's SecurityExchange.
>18100 LegExDestination Execution destination for the leg order as defined by the institution.
>602 LegSecurityId TT security ID that uniquely identifies the instrument in the TT platform.
>603 LegIDSource Multileg instrument's individual security's SecurityIDSource.
>600 LegSymbol Multi-leg instrument's individual security's Symbol.
>608 LegCFICode Multileg instrument's individual security's CFICode (tag 461).
>609 LegSecurityType Multi-leg instrument's individual security's SecurityType.
>764 LegSecuritySubType SecuritySubType of the leg instrument.
>624 LegSide The side of this individual leg (multi-leg security).
>610 LegMaturityMonthYear Multi-leg instrument's individual security's MaturityMonthYear
>611 LegMaturityDate Multi-leg instrument's individual security's MaturityDate.
>18314 LegMaturityDay Multi-leg instrument's individual security's MaturityDay.
>612 LegStrikePrice Multi-leg instrument's individual security's StrikePrice.
>1358 LegPutOrCall Whether the option represents a put or call.

Order Routing Session Tag Usage

  1. When a FIX message is received, the values from the relevant FIX tags of the message are searched through PDS to identify an instrument.
  2. For all cases, SecurityID (Tag 48) and SecurityIDSource (Tag 22) can be used.
  3. Alternatively, SecurityAltID (Tag 455) and SecurityAltIDSource (Tag 456) along with SecurityExchange (Tag 207) or ExDestination (Tag 100), can be used
  4. If the tags above are not present, the following tags are used:
  5. Ambiguity is avoided by using additional tags where necessary.
  6. If multiple instruments are returned, the message is rejected.

SecurityID (Tag 48) and SecurityIDSource (Tag 22)

SecurityIDSource (Tag 22) values supported by TT

Usage

96: TT security ID

5: RIC code

4: ISIN number

X: Series key

Unique identifier of an instrument and can be used on its own.

A: Bloomberg code

S: OpenFIGI ID

Identifies instrument along with tag 207.

8: Exchange symbol

97: Alias

98: Name

Unique within a specific market; therefore, to avoid ambiguity either tag 207 (SecurityExchange) or 100 (ExDestination) is also required to identify the instrument.

H: Clearing House (Inbound Drop Copy only)

91: Ticker symbol

Not applicable for order routing.

Example 1 - ICE - BRN (Fut) by SecurityID using RIC

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=ICE | 21=1 | 55=BRN | 22=5 | 48=LCOQ6 | 10=178 |

Example 2 - CME - ES (MLEG) by SecurityID using TT Security ID

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 21=1 | 55=ES | 22=96 | 48=13575348896651708455 | 10=251 |

Example 3 - ICE - BRN (Fut) by SecurityID using Bloomberg Code

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=ICE | 21=1 | 55=BRN | 22=A | 48=COQ6 Comdty | 10=178 |

Example 4 - ICE - BRN (Fut) by SecurityID using Exchange Symbol

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=ICE | 21=1 | 55=BRN | 22=8 | 48=6018418 | 10=178 |

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 100=IFEU | 21=1 | 55=BRN | 22=8 | 48=6018418 | 10=178 |

SecurityAltID (Tag 455) and SecurityAltIDSource (Tag 456)

SecurityAltIDSource (Tag 456) values supported by TT

Usage

5: RIC code

4: ISIN number

Unique identifier of an instrument and can be used on its own.

A: Bloomberg code

S: OpenFIGI ID

Identifies instrument along with tag 16207.

8: Exchange symbol

97: Alias

98: Name

Unique within a specific market; therefore, to avoid ambiguity either tag 207 (SecurityExchange) or 100 (ExDestination) is also required to identify the instrument.

1: CUSIP

H: Clearing House (Inbound Drop Copy only)

92: TT product family ID

93: TT product ID

99: Other

94: Alt Symbol

95: Clearport

91: Ticker symbol

Not applicable for order routing.

Example 5 - CME - ES (Fut) by SecurityAltID using RIC

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=CME | 21=1 | 55=ES | 454=1 | 455=ESU26 | 456=5 | 10=178 |

Example 6 - CME - ES (Fut) by SecurityAltID using Bloomberg Code

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 100=XCME | 21=1 | 55=ES | 454=1 | 455=ESZ6 Index | 456=A | 16207=CME | 10=178 |

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=CME | 21=1 | 55=ES | 454=1 | 455=ESZ6 Index | 456=A | 10=178 |

Symbol (Tag 55)

If the security ID is not defined in the FIX message, the system uses the Symbol (Tag 55), along with SecurityType (Tag 167) or CFICode (Tag 461), MaturityMonthYear (Tag 200) and MaturityDay (Tag 205) or MaturityDate (Tag 541).

Notes

  • Either the SecurityExchange (Tag 207) or ExDestination (Tag 100) must be specified.
  • ExerciseStyle (tag 1194) is utilized at times of ambiguity to identify the correct instrument.
  • For options (SecurityType=OPT), StrikePrice (Tag 202) and PutorCall (Tag 201) are required.
  • For multi-leg instruments, the SecuritySubType (Tag 762) can be used to narrow down the search.

Example 7 - ICE - BRN (Fut) by Symbol

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 207=ICE | 21=1 | 55=BRN | 167=FUT | 200=202608| 10=178 |

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 100=IFEU | 21=1 | 55=BRN | 167=FUT | 200=202608| 10=178 |

8=FIX.4.4 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 100=IFEU | 21=1 | 55=BRN | 461=FXXXXX | 200=202608| 10=178 |

Example 8 - CME - ES (Opt) by Symbol

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 21=1 | 207=CME | 55=ES | 167=OPT | 201=0 | 202=150000 | 541=20260320 | 10=027 |

8=FIX.4.4 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 21=1 | 100=XCME | 55=ES | 461=OPXXXX | 201=0 | 202=150000 | 200=202603 | 205=20 | 10=143 |

Example 9 - MEFF - ENC(Opt) by Symbol

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 21=1 | 207=MEFF | 55=ENC | 167=OPT | 201=1 | 202=2.5 | 200=202510 | 205=17 | 1194=0 | 10=143 |

8=FIX.4.2 | 9=164 | 35=D | 49=USERABC_OR | 56=TT | 34=40 | 52=20251030-20:39:52 | 11=1892337812 | 54=1 | 40=1 | 38=10 | 1=Abraxas_P | 116=USERABC | 21=1 | 207=MEFF | 55=ENC | 167=OPT | 201=1 | 202=2.5 | 541=20251017 | 1194=1 | 10=143 |

LegInstrumentGrp (Tag 555)

For multi-leg instruments (SecurityType=MLEG), the individual leg instruments can serve as an alternative means of identification.

The tags within LegInstrumentGrp (Tag 555) correspond to tags found in the security ID and symbol sections. Either the security ID or symbol, along with the corresponding tags, need to be defined for each leg to identify the leg instruments.

  1. Defining the correct pair of LegSecurityId (Tag 602) and LegIDSource (Tag 603) along with the LegSide (Tag 624) will identify the correct instrument. By default, the LegSide (Tag 624) is considered as buy; therefore, specifying the leg side is essential.
  2. Else, defining the LegSymbol (Tag 600) along with LegCFICode (Tag 608) or LegSecurityType (Tag 609) and the relevant maturity date, price and type tags based on the leg instrument, will assist in identifying the instrument.

Example 10 - CME - ES (Spread) by Repeating Group Tag 555

8=FIX.4.2 | 9=230 | 35=D | 49=USERABC_OR | 56=TT | 34=549 | 52=20251031-15:04:55 | 11=1314667219 | 54=2 | 40=2 | 44=120000 | 38=2 | 1=Abraxas_P | 116=USERABC | 55=ES | 207=CME | 167=MLEG | 762=Calendar | 555=2 | 600=ES | 602=ESU26 | 603=5 | 624=2 | 600=ES | 609=FUT | 610=202706 | 616=CME | 10=052 |

Best Practices for Instrument Identification

  • Consistent tag usage: Ensure that all parties involved in a FIX session consistently use the same tags and values for instrument identification. Discrepancies can lead to order rejections or misinterpretations.
  • Utilize standard identifiers: Wherever possible, use standardized identifiers like ISIN or RIC. Using the TT security ID guarantees the instrument identification at all times.
  • Provide sufficient details: For options or multilegs, always provide all necessary identifying tags (e.g., SecurityType, MaturityMonthYear, MaturityDay StrikePrice) to ensure precise identification.
  • In messages, provide either MaturityMonthYear (Tag 200) and MaturityDay (Tag 205) or MaturityDate (Tag 541), but not both.
  • Provide a unique set of identifiers and not all. Send either one type of SecurityID or Symbol along with relevant tags. Avoid sending multiple SecurityID pairs where possible.
  • For options, provide either the CFICode (Tag 461) or PutorCall (Tag 201) and not both. If both are provided, CFICode takes precedence over PutorCall.