OrderRoute (MEOR)
| ID | 30926 |
Industry Members are required to report an Order Route event to CAT in the following scenarios when an order is routed in full or in part:
- Routing to another Industry Member
- Routing to foreign broker-dealers
- Routing to exchanges
- Routing between two IMIDs (e.g., two different FINRA MPIDs) attributed to the same legal entity (i.e., the same CRD).
When routing between two IMIDs of the same legal entity, the affiliateFlag must be populated as ‘true’ in accordance with CAT FAQ E27. Internal routes to another desk or department within an Industry Member are reported using an Order Internal Route Accepted event. Refer to the Order Internal Route Accepted section for more details.
Handling Instructions on Order Route Events
Handling Instructions are required to be reported on the Order Route event. The handling instructions included in this event must represent the handling instructions sent by the routing firm to the receiving destination. If the handling instructions do not change when the order is routed externally from the handling instructions received by the Industry Member and reported on the Order Accepted or New Order event associated with the order, Industry Members may use the handling instruction code ‘RAR’ (Routed as Received) instead of repeating each individual handling instruction.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
2 | Y | Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. | |||
38 | Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. | ||||
44 | Y | An identifier assigned to the record by the reporting firm. Formatted as Must be unique for the Event Date and CAT Reporter IMID. | |||
131 | Y | MEOR | |||
22 | The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. | ||||
78 | Y | The orderKeyDate of the event which is being routed. | |||
77 | Y | The orderID of the order event which is being routed. | |||
123 | Y | The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. | |||
80 | An identifier used in instances of a merger or acquisition where the originating firm had open limit orders on its books that will be executed or otherwise resolved under the surviving firm. Must be provided to support linkage to an event that was reported with a different CATReporterIMID. | ||||
39 | Y | The date/time of the Order Route. If manualFlag is ‘true’, timestamp must be reported to seconds. If manualFlag is ‘false’, timestamp must be reported to milliseconds or a finer increment up to nanoseconds. | |||
56 | Y | Must be marked as ‘true’ if the order is routed manually. | |||
36 | Y | Indicates whether this is a duplicative electronic message of a manual event. | |||
37 | The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. | ||||
115 | The IMID used to identify the Industry Member that is routing the order, known by the destination. When destinationType is ‘F’, this value must equal the senderIMID on the Order Accepted event reported by the destination. When destinationType is ‘O’, this value must equal the senderIMID on the Order Accepted event if an Order Accepted event is reported by the destination. When destinationType is ‘E’, this value must equal the routingParty reported by the exchange on the Participant Order Accepted event. Not required when destinationType is ‘N’. | ||||
30 | When destinationType is ‘F’, this value is the IMID used to identify the Industry Member that is receiving this routed order, and it must equal the receiverIMID field on the Order Accepted event reported by the destination Industry Member. When destinationType is ‘O’, this value is the IMID used to identify the Industry Member that is receiving this routed order, and it must equal the receiverIMID field on the Order Accepted event if an Order Accepted event is reported by the destination Industry Member. When destinationType is ‘E’, this value is the Exchange ID of the destination exchange, and it must equal the exchange field on the Order Accepted event reported by the destination exchange. Not required if destinationType is ‘N’. If optionally populated when destinationType is ‘N’, CRD Prefix is not required. | ||||
31 | Y | Indicates whether the destination of the route is an Industry Member, an exchange or a foreign broker-dealer. destinationType ‘O’ must only be populated if the symbol is an OTC symbol in a foreign equity security. | |||
111 | The ID assigned to the order by the Industry Member when routing the order to the destination. This value must match the value for routedOrderID reported by the destination in their Order Accepted report. Must be unique per combination of Event Date, symbol, destination, senderIMID, and session (applicable only on routes to exchanges). Required when destinationType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. | ||||
118 | The session ID used when routing the order. Must only be populated when destinationType is ‘E’. This must match the session ID reported in the Participant Order Accepted event by the receiving exchange. | ||||
120 | Y | The side of the order. | |||
84 | The limit price of the order. When provided, must be greater than or equal to zero. Required when orderType is ‘LMT’. Must be blank when orderType is ‘MKT’. | ||||
96 | Y | The order quantity. | |||
60 | The minimum quantity of an order to be executed. Required when applicable. Must be > 0. | ||||
79 | Y | The type of order being routed. | |||
timeInForce | Y | The Time in Force for the order. | |||
129 | Y | The trading session(s) during which an order is eligible to trade. | |||
3 | Y | Indicates if the order is being routed to an affiliate of the Industry Member. | |||
51 | Y | Indicates the order was routed as an Intermarket Sweep Order. | |||
handlingInstructions | The order handling instructions for the order. | ||||
113 | Y | Indicates the routed order was not accepted by the destination (rejected or no response) when marked ‘true’. | |||
34 | Y | Indicates when a modification to an order previously routed to a national securities exchange requires the use of the original routedOrderID. This field can only be populated as ‘true’ on Order Route events when destinationType is ‘E’. | |||
117 | The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. | ||||
62 | Y | Indicates when the order being routed is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. | |||
81 | The pairedOrderID field may be populated if two or more offsetting orders are routed with instructions to cross. | ||||
48 | Specifies the identifier of the information barrier in place for a trading unit that will meet the criteria of the “no-knowledge” exception in FINRA Rule 5320.02. Any alphanumeric not containing a delimiter. | ||||
70 | The net price of the order when tied to stock, tied to fixed income, tied to futures, tied to a non-CAT reportable product, or part of another trading strategy in which the order is traded at a net price. When netPrice is populated, the price field must be blank or populated with a value of zero. Refer to CAT FAQ B71 for additional information. | ||||
98 | The date and time the quoteID was assigned. Required when quoteID is populated. Must be blank when quoteID is blank. | ||||
97 | Required for Order Route events reported by an IDQS directed to a specific quote displayed on the IDQS, this is the IDQS assigned quoteID of the related Quote Received event reported by the IDQS. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy