NewOrder (MENO)
| ID | 26358 |
New Order events represent the beginning of the order lifecycle in CAT. An Industry Member must report a New Order event to CAT when an order is received or originated including:
- New customer orders
- Representative orders
- Proprietary orders
- Order(s) received from a foreign broker-dealer or affiliate that is not a CAT Reporter.
An order received from another CAT Reporter (US broker-dealer, ATS or an exchange) must be reported as an Order Accepted event.
Representative Orders
Industry Members are required to link representative street-side orders with the related customer order or client order being represented. The Industry Member must report a New Order event for the creation of the representative order, and populate the representativeInd field to indicate that it is a representative order. The Industry Member must also populate the aggregatedOrders field linking the representative order to the underlying orders.
Appendix C contains detailed descriptions of representative order scenarios and illustrates when marking of the representative order, linkage between the represented order and the representative order, and Order Fulfillment linkage is required.
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 | MENO | |||
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 | The internal order ID assigned to the order by the Industry Member. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. | |||
123 | Y | The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. | |||
39 | Y | The date/time of receipt of the order. 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 received or captured 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. | ||||
58 | The orderKeyDate of the related manual order. Required when manualOrderID is populated. | ||||
57 | When this is a duplicative electronic message of a previously (separately) reported manual New Order event, this field is to capture the internal orderID of the manual order. Required when electronicDupFlag is ‘true’. | ||||
28 | Y | This is the category of internal department, unit or desk originating or receiving the order. | |||
122 | Y | Indicates if the order was originated in response to an RFQ or other solicitation process. This field is not used to indicate if a registered representative of the firm solicited a customer/client order. | |||
110 | For New Order events representing a response to an RFQ or solicitation, the ID assigned to the related RFQ or solicitation being responded to. Must be populated when available. | ||||
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 submitted. | |||
timeInForce | Y | The Time in Force for the order. | |||
129 | Y | The trading session(s) during which an order is eligible to trade. | |||
handlingInstructions | The order handling instructions for the order. | ||||
27 | Y | Indicates if a customer/client has instructed that a limit order should not be displayed or that a block size order should be displayed. | |||
42 | Y | Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. | |||
1 | Y | Represents the type of beneficial owner of the account for which the order was received or originated. | |||
3 | Y | Indicates if the routing party is an affiliate of the Industry Member. | |||
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. | ||||
aggregatedOrders | When applicable, the order ID of each customer/client order being represented. Refer to Appendix C for representative order linkage requirements. | ||||
69 | Y | Indicates whether the trade is a result of a negotiation. | |||
105 | Y | Indicates if the order is a representative order and if linkage is required. | |||
117 | The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. Only required for ATSs. | ||||
12 | Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. | ||||
32 | The displayed price for this order. When provided, must be greater than or equal to zero. If atsDisplayInd is ‘Y’, ‘S’, or ‘A’, displayPrice must be the price at which the order was displayed. If atsDisplayInd is ‘N’, displayPrice must be “0”. | ||||
135 | The working price of the order at the time it was accepted. When provided, must be greater than or equal to zero. If no current workingPrice, value must be “0”. | ||||
33 | The displayed quantity for this order. If the atsDisplayInd is populated as ‘Y’, ‘S’, or ‘A’, displayQty must be the quantity at which the order was displayed. If the atsDisplayInd is ‘N’, displayQty must be ‘0’. | ||||
13 | Shows the ATS-specific order type as selected from a list of order types defined by this reporter via the CAT Reporter Portal. | ||||
65 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
66 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
67 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
68 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
63 | Source of the NBBO data used. If nbboSource is ‘NA’, NBBO price and quantity fields must be populated with a value of ‘0’ and the nbboTimestamp must be blank. | ||||
64 | The date/time at which the NBBO was referenced A upon the receipt of the order. Must be blank if nbboSource is ‘NA’. | ||||
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. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy