OrderInternalRouteAccepted (MEIR)
| ID | 20870 |
An Order Internal Route Accepted event must be reported when an order is passed to a different department or desk within the CATReporterIMID. Routes between different IMIDs attributed to the same Industry Member must be reported as Order Route and Order Accepted events.
An Order Internal Route Accepted event is required to be reported from the perspective of the recipient desk, and indicates that an order was received by an internal destination. In Phase 2d, Industry Members may choose to assign a new Order Key to an Order Internal Route Accepted event. If a new orderID is assigned, the parentOrderID must be populated with the orderID of the event that was internally routed, and the parentOrderKeyDate must be populated.
An Industry Member may generate child orders using the Child Order event prior to routing internally to another desk. This approach is acceptable for CAT reporting and will not result in unlinked events.
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 | MEIR | |||
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 date and time the orderID was assigned. | |||
77 | Y | When a new Order Key is assigned, the internal order ID assigned to the order by the Industry Member. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. When a new Order Key is not assigned, the orderID of the event that was internally routed. | |||
123 | Y | The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. | |||
83 | If a new Order ID has been assigned, this is the orderKeyDate of the event from which the Order Internal Route Accepted event originated. Required when the parentOrderID is populated. Must be blank when parentOrderID is blank. | ||||
82 | If a new Order ID has been assigned, this is the orderID of the event from which the Order Internal Route Accepted event originated. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. When populated, the parentOrderID must not be equal to the orderID within the record. Required when the parentOrderKeyDate is populated. If a new Order ID has not been assigned, must be blank. | ||||
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 receipt by the receiving desk. 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 to another desk manually. | |||
37 | The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. | ||||
28 | Y | The category of department, unit, or desk that received this Order Internal Route Accepted event. | |||
103 | Y | Indicates the type of desk or department receiving the order. More granular than the field deptType. | |||
48 | Specifies the identifier of the information barrier in place for the desk to which the order was routed that will meet the criteria of the “no-knowledge” exception in FINRA Rule 5320.02. Any alphanumeric not containing a delimiter. | ||||
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 received from the routing desk or department. | |||
handlingInstructions | The order handling instructions for the order. | ||||
timeInForce | Y | The Time in Force for the order. | |||
129 | Y | The trading session(s) during which an order is eligible to trade. | |||
62 | Y | Indicates when the order that was routed internally is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. | |||
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. | ||||
29 | Internal identifier assigned to this event by the department or desk. Required when the order is routed partially and a new orderID is not assigned to this event. Not required when the order is routed in full or when a new orderID is assigned to this event. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy