Indexes

Message Layouts
PostTrade
PreTrade
Trade

Message

OrderCancelled (MEOC)

ID22852

The Order Cancelled event is reported when an order is fully or partially cancelled. Partial cancellations of an order may be reported to CAT using an Order Cancelled event or an Order Modified event. However, when routing between Industry Members, both parties must communicate and use the same method to report to CAT. If one party reports to CAT using the cancellation method and the other party reports to CAT using a modification method, this will result in unlinked records that must be resolved.

Implicit order cancellations, such as cancellations due to expiration of Time in Force, are not required to be reported to CAT.

Order Cancelled events are required to be reported by the entity that initiated the cancellation. When an Order is routed from Firm A to Firm B, the following rules apply:

  • If Firm A or its customer/client initiates the cancel, Firm A and Firm B must report the Order Cancelled event.
  • If Firm B initiates the cancel, Firm B must report the Order Cancelled event.

Industry Members are not required to report the cancel request to CAT if the order is terminal (e.g., it has already been fully executed or cancelled) in Phase 2d. However, this activity may be required in future phases of CAT. If a cancellation request was received that was too late to cancel, and the order was not terminal (e.g., the order was “in-flight” and there was no confirmation time), the request must be reported as an Order Cancel Request event.

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

MEOC

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 order event which is being cancelled.

77
Y

The orderID of the order event which is being cancelled.

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 the order was cancelled (e.g., the time that the order was confirmed to be cancelled in the firm’s OMS/EMS).

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 cancelled manually.

37

The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized.

18
Y

The quantity being cancelled.

52
Y

The number of shares of the order left open after the cancel event. The full cancel will result in zero in this field.

49
Y

Indicates who initiated the order cancellation.

117

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

109

The date/time the cancellation was requested. Required if a request was received, and the request is not captured in a separate MEOCR event.

Must not be populated if the request is captured in a separate MEOCR event.

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.

Not required if the order is terminal (e.g., it has already been fully executed or cancelled) in Phase 2d. May be required in future phases of CAT.

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.

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