In Phases 2a or 2b, events subsequent to an internal route modification may be populated with any orderID that allows the event to be linked to the order lifecycle. For example, an order that was internally routed from a sales desk to a trading desk is subsequently modified at both the sales and trading desks, and ultimately executed at the trading desk. The sales desk and trading desk maintain different orderIDs. In this example, in Phase 2a the orderID on the related Trade event may link to either the MEIR reported by the trading desk or the MEOM reported by the sales desk. Starting in Phase 2c, the Trade event must link to the MEIM reported by the trading desk. Additionally, beginning on December 5, 2022, if an order is partially routed internally and a new orderID is not assigned, the deskOrderID field is required to be populated in the Order Internal Modified event (MEIM, MOIM or MLIM). If a new deskOrderID is assigned, the deskOrderID of the event being modified must be reported in the priorDeskOrderID field.
- FAQs Last Updated:
Order Internal Route Modified events are not required to be reported to CAT until Phase 2c. In Phase 2a, what orderID should be populated on events subsequent to the internal route modification (e.g., MEOR, MEOT)?
Order Internal Route Modified events are not required to be reported to CAT until Phase 2c. In Phase 2a, what orderID should be populated on events subsequent to the internal route modification (e.g., MEOR, MEOT)?