FIX Version FIX.Latest Extension Pack EP277

Approval Date 2023-04-15T00:00:00

Description Market Model Typology v4.0 Support




Field Changes

Updated Fields

TagNameTypeAssociatedDataTagAbbrNameBaseCategoryBaseCategoryAbbrNameNotReqXMLEnumDatatypeUnionDataTypeDescriptionElaborationDeprecated
828Type of trade assigned to a trade. SecondaryTrdType(855) and TertiaryTrdType(2896) may be used in addition to TrdType(828) to assign up to three different trade types to a single trade.



New Fields

TagNameTypeAssociatedDataTagAbbrNameBaseCategoryBaseCategoryAbbrNameNotReqXMLEnumDatatypeUnionDataTypeDescriptionElaboration
2963MultiJurisdictionReportingIndicatorintMultiJrsdctnRptInd0Indicate whether a trade is eligible to be reported to more than one regulatory jurisdictions, e.g. due to overlapping reporting rules that require reporting to different jurisdictions.



Enumerations

Updated Enumerations

TagValueSymbolicNameGroupSortDescriptionElaborationDeprecated
82865May be used to identify the pseudo-trade of a stream or collection of trades to be transacted, cleared and be reported as an atomic unit. In the context of MiFIR RTS 1, this is the "CONT" flag. In the context of MiFIR RTS 2 Article 1(1)(b), may be used to refer to package transactions (excluding exchange for physicals). In the context of Market Model Typology (MMT), use of this value applies to SecondaryTrdType(855) or TertiaryTrdType(2896), and when used for MMT market data publication requires MDEntryType(269) = 2 (Trade).
183916Per MiFIR Article 23, these types of trades are not exempted from post-trade transparency if reported to a trading venue under MiFID II and deemed on exchange, however, they are ignored for price formation despite published by venue. For the UK implementation of MiFIR RTS 1, this is the "TNCP" flag.
183917In the context of MiFIR RTS 1, RTS 2, and RTS 22, this is the "PNDG" flag.
183918In the context of MiFIR RTS 1, RTS 2, and RTS 22, this is the "NOAP" flag.

Enumerations Added

TagValueSymbolicNameGroupSortDescriptionElaboration
29630NotMultiJrsdctnEligible0Trade not eligible for multi-jurisdiction reporting
29631MultiJrsdctnEligible1Trade eligible for multi-jurisdiction reporting
1430zOtherMarket13Other market (lowercase "z")A market that does not fall under any of the market types defined for VenueType(1430).

Message/Component Content

Message/Components Content Changes

ComponentIDTagTextIndentPositionReqdDescription
100355Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles) Use "[N/A]" for products which do not have a symbol. Required if the Instrument component is marked as required where the component is used.
1005600Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles) Use "[N/A]" for products which do not have a symbol. Required if the InstrumentLeg component is marked as required where the component is used.
1021311Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles) Use "[N/A]" for products which do not have a symbol. Required if the UnderlyingInstrument component is marked as required where the component is used.
21401214Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles) Use "[N/A]" for products which do not have a symbol. Required if DerivativeInstrument component is marked as required where the component is used.

Messages/Components  Content Added

ComponentIDTagTextIndentPositionReqdDescription
6429630157.50
20312963131.2150For optional use in reporting trades.
20322963124.070For optional use in reporting trades.