Indexes

Message Layouts
PostTrade
PreTrade
Trade

Message

ChildOrder (MECO)

ID31758

The Child Order is used to represent instances when an order is sliced within the desk or department it is being worked, and is assigned a new order identifier. While all CAT reportable activity must be reported to CAT in applicable phases, Child Order events are not required to be utilized for CAT reporting. These event types are for the convenience of Industry Members to help model these types of order handling scenarios.

Child Order events are defined to include only the key data elements that may be changed when the event is created including fields to link to the parent order. The following rules apply with respect to Child Orders:

  • Child Order events can only be reported when new order IDs are assigned within the same desk. An Order Internal Route Accepted event must be reported when routed to another desk.
  • A child order may be generated off of another child order without limitation.
  • Child Order events must belong to the same FDID as the parent order. Child Orders must not be used to create representative orders. If the FDID changes, a representative New Order event must be reported and not a Child Order.
  • Child Order events must not be used to represent a multi-leg option order being “legged out”. However, the Child Order event may be used in scenarios where an order is “legged out” and subsequently entered into another OMS/EMS or Algo within the same desk or department where a new orderID is assigned to each leg upon entry.
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

MECO

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 child order by the Industry Member. Must be unique with the 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.

83
Y

The orderKeyDate of the event from which the Child Order originated.

82
Y

The orderID of the event from which the Child Order originated. The parentOrderID must not be equal to the orderID within the record.

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 at which the child order was originated. Timestamp must be reported to milliseconds or a finer increment up to nanoseconds.

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 Child order quantity.

60

The minimum quantity of an order to be executed. Required when applicable. Must be > 0.

79
Y

The type of order.

Y

The Time in Force for the order.

129
Y

The trading session(s) during which an order is eligible to trade.

The order handling instructions for the order.

117

The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter.

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 the atsDisplayInd is ‘N’, displayPrice must be “0”.

135

The working price of the order at the time it was originated or received. 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”.

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 upon the receipt of the order. Must be blank if nbboSource is ‘NA’.

62
Y

Indicates when the Child Order was originated from a multi-leg order event. Refer to Section 5.2 for additional guidance.

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.

Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy