CAT Reporting Technical Specifications for Industry Members 2024-07-24 Consolidated Audit Trail, LLC [Orchestra v1.0](https://www.fixtrading.org/packages/fix-orchestra-technical-specification-v1-0/) Copyright 2024 Atomic Wire Technology Limited This document describes the requirements for the reporting of data to CAT by Industry Members, including detailed information about data elements and file formats of each Reportable Event. It also describes how Industry Members submit files to CAT, including access instructions, network and transport options, and testing requirements. Requirements for the reporting of data to CAT by Industry Members Atomic Wire Technology Limited CAT, OATS, FINRA [CAT Reporting Technical Specifications for Industry Members](https://www.catnmsplan.com/sites/default/files/2022-12/12.16.2022_CAT_Reporting_Technical_Specifications_for_Industry_Members_v4.0.0r18_CLEAN.pdf) Infrastructure messages for application sequencing, business reject, network and user management. Post trade messages including trade reporting, allocation, collateral, confirmation, position maintenance, registration instruction, and settlement instructions. A description added to the PreTrade section. Session level messages to establish and control a FIX session. Order handling and execution messages. A string, composed only of letters and digits [a-zA-Z0-9]. When an Alphanumeric type is described, it will include a number, indicating the maximum length of the field. For example, Alphanumeric (7) means that the field can contain up to 7 characters. Alphanumeric values are case sensitive. A string, composed only of letters and digits [a-zA-Z0-9]. When an Alphanumeric type is described, it will include a number, indicating the maximum length of the field. For example, Alphanumeric (7) means that the field can contain up to 7 characters. Alphanumeric values are case sensitive. seqNum: 10987 A value with two choices: true or false. In CSV representation, the value must equal <code>true</code> or <code>false</code> (no quotation marks). In JSON representation, if the field is not present, the value is considered <code>false</code>. Boolean values are NOT case sensitive. A value with two choices: true or false. In CSV representation, the value must equal <code>true</code> or <code>false</code> (no quotation marks). In JSON representation, if the field is not present, the value is considered <code>false</code>. Boolean values are NOT case sensitive. manualFlag: false Alphanumeric (7) - a CAT Reporter IMID. Alphanumeric (7) - a CAT Reporter IMID. CATReporterIMID: BRK1 A unique ID assigned by CAT to the CAT Reporting Agent. A unique ID assigned by CAT to the CAT Reporting Agent. TBC An 8-digit integer representing the date in YYYYMMDD. An 8-digit integer representing the date in YYYYMMDD. tradeDate: 20180427 Alphanumeric (7) – identifier that applies to exchanges. Alphanumeric (7) – identifier that applies to exchanges. destination: EXCH1 Text (16) – CRD and SRO-assigned Market Participant Identifier assigned by an SRO to one of its members.<br><br>Formatted as `<CRD of the Market Participant>:<SRO-assigned Market Participant Identifier>`.<br><br>Example: CRD 123, IMID ABCD is populated as 123:ABCD Text (16) – CRD and SRO-assigned Market Participant Identifier assigned by an SRO to one of its members.<br><br>Formatted as `<CRD of the Market Participant>:<SRO-assigned Market Participant Identifier>`.<br><br>Example: CRD 123, IMID ABCD is populated as 123:ABCD senderIMID: 123:FRMA An integer value (positive, negative, or zero), with no decimal fraction component, in the inclusive range from −9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 (the same range as a 64-bit signed integer). An integer value (positive, negative, or zero), with no decimal fraction component, in the inclusive range from −9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 (the same range as a 64-bit signed integer). fieldName: -100 Alphanumeric (5) indicating the type of message being reported. Alphanumeric (5) indicating the type of message being reported. type: MENO Unsigned field representing the number of entries in a repeating group. Value must be positive. Composed of digits with an optional decimal point. Values must represent the exact value as per the examples: <br> 1235 <br> -1235 <br> 1235.67 <br> -1235.67 <br> <br> Numeric data types described in this document will include two numbers, the first is the maximum number of digits before the decimal point, and the second is the maximum number of digits after the decimal point. For example, Numeric (6,4) indicates that the number can have a maximum of 6 digits before the decimal point and a maximum of 4 digits after the decimal point. <br> <br> Examples which comply with Numeric (6,4) include: <br> -999999.9999 <br> -0.1 <br> 0 <br> 0.0001 100 <br> 100.100 <br> 999999.99 <br> 0.25 <br> 099999.9990 <br> 0999999.99990 <br> <br> Numeric values must always include a digit in the portion before the decimal. The fractional portion is optional (for example, 0.25 cannot be represented as .25). <br> Examples which do not comply with Numeric (6,4) include: <br> 1234567.0 <br> .123 <br> 1.12345 <br> 10. <br> 40a <br> <br> Numeric data types that require 0 digits after the decimal place should not include a decimal. The following example does not comply with Numeric (6,0): <br> 1234.5 <br> 1234.0 Composed of digits with an optional decimal point. Values must represent the exact value as per the examples: <br> 1235 <br> -1235 <br> 1235.67 <br> -1235.67 <br> <br> Numeric data types described in this document will include two numbers, the first is the maximum number of digits before the decimal point, and the second is the maximum number of digits after the decimal point. For example, Numeric (6,4) indicates that the number can have a maximum of 6 digits before the decimal point and a maximum of 4 digits after the decimal point. <br> <br> Examples which comply with Numeric (6,4) include: <br> -999999.9999 <br> -0.1 <br> 0 <br> 0.0001 100 <br> 100.100 <br> 999999.99 <br> 0.25 <br> 099999.9990 <br> 0999999.99990 <br> <br> Numeric values must always include a digit in the portion before the decimal. The fractional portion is optional (for example, 0.25 cannot be represented as .25). <br> Examples which do not comply with Numeric (6,4) include: <br> 1234567.0 <br> .123 <br> 1.12345 <br> 10. <br> 40a <br> <br> Numeric data types that require 0 digits after the decimal place should not include a decimal. The following example does not comply with Numeric (6,0): <br> 1234.5 <br> 1234.0 Numeric (10,8), which supports prices in the inclusive range from -9999999999.99999999 to 9999999999.99999999. Numeric (10,8), which supports prices in the inclusive range from -9999999999.99999999 to 9999999999.99999999. price: 10.00 Numeric (12,6) with up to 12 digits before the decimal point and up to 6 digits after the decimal point. However, the type Real Quantity cannot have trailing zeros in the decimal quantities. Trailing zeros in the decimal quantity will result in a rejection. <br> <br> For example, a value of 100.00 would not be accepted for the type Real Quantity, only 100 would be accepted. Similarly, a value of 100.10 would not be accepted, only 100.1 is acceptable for the type Real Quantity. Real Quantity must not be a negative value. Numeric (12,6) with up to 12 digits before the decimal point and up to 6 digits after the decimal point. However, the type Real Quantity cannot have trailing zeros in the decimal quantities. Trailing zeros in the decimal quantity will result in a rejection. <br> <br> For example, a value of 100.00 would not be accepted for the type Real Quantity, only 100 would be accepted. Similarly, a value of 100.10 would not be accepted, only 100.1 is acceptable for the type Real Quantity. Real Quantity must not be a negative value. quantity: 1000 Numeric (12,0). An integer value with no decimal fraction component. Whole Quantity must not be a negative value. Numeric (12,0). An integer value with no decimal fraction component. Whole Quantity must not be a negative value. minQty: 100 Alpha-numeric free format strings, can include any character or punctuation except the delimiter. All String fields are case sensitive (i.e. morstatt != Morstatt). Alpha-numeric free format strings, can include any character or punctuation except the delimiter. All String fields are case sensitive (i.e. morstatt != Morstatt). Text (22). Refer to Section 2.4.3 and Section 2.4.4 for more details on Equity and Options symbols. The string is case sensitive. Text (22). Refer to Section 2.4.3 and Section 2.4.4 for more details on Equity and Options symbols. The string is case sensitive. symbol: XYZ A string, composed of any printable ASCII character from 32 to 126. The string may not include the following characters which serve as delimiters:<br>comma (ASCII decimal 44, hex 2C),<br>pipe (ASCII decimal 124, hex 7C),<br>double quote (ASCII decimal 34, hex 22),<br>and @ (ASCII decimal 64, hex 40).<br><br>When a Text data type is described, it will include a number, indicating the maximum length of the field. For example, Text (7) means that the field can contain up to 7 characters. Text values are case sensitive.<br><br>When represented in JSON, the following rule applies:<br><br>Backslash ‘\\’ is a reserved printable character in JSON and must be escaped in order to be used in strings by inserting a backslash prior to it within the string. For example: routedOrderID = 1234\\ABCD must be reported to CAT as “routedOrderID”:”1234\\\\ABCD”.<br><br> If the backslash is not escaped, it will be omitted from the string. For example, if the following is reported to CAT, “routedOrderID”:”1234\\ABCD”, it will be stored as routedOrderID = 1234ABCD.<br> <br> Escape characters do not participate in the field value length. A string, composed of any printable ASCII character from 32 to 126. The string may not include the following characters which serve as delimiters:<br>comma (ASCII decimal 44, hex 2C),<br>pipe (ASCII decimal 124, hex 7C),<br>double quote (ASCII decimal 34, hex 22),<br>and @ (ASCII decimal 64, hex 40).<br><br>When a Text data type is described, it will include a number, indicating the maximum length of the field. For example, Text (7) means that the field can contain up to 7 characters. Text values are case sensitive.<br><br>When represented in JSON, the following rule applies:<br><br>Backslash ‘\\’ is a reserved printable character in JSON and must be escaped in order to be used in strings by inserting a backslash prior to it within the string. For example: routedOrderID = 1234\\ABCD must be reported to CAT as “routedOrderID”:”1234\\\\ABCD”.<br><br> If the backslash is not escaped, it will be omitted from the string. For example, if the following is reported to CAT, “routedOrderID”:”1234\\ABCD”, it will be stored as routedOrderID = 1234ABCD.<br> <br> Escape characters do not participate in the field value length. A timestamp represents a moment in time. Two timestamp formats are supported including STRING and NUMBER. <br> <br> Timestamps formatted as a STRING have a maximum length of 25 and are formatted as ‘YYYYMMDD HHMMSS.CCCNNNNNN’ with the Date and Time portions, separated by a space (ASCII decimal 32, hex 20) or the letter T (ASCII decimal 84, hex 54). All timestamps submitted in STRING format must be in Eastern Time (ET). <br> • The Date portion must include four digit year, two digit month, and two digit day. Valid values: YYYY = 0000 - 9999, MM = 00 - 12, DD = 00 – 31. <br> • The Time portion must include a two digit hour, two digit minute, two digit seconds. Valid values: HH = 00 - 23, MM = 01 - 59, SS = 01 - 59, CCC = 000 – 999, NNNNNN = 000000 - 999999. <br> <br> Examples which comply with Timestamp in STRING format: <br>• 20190617T000120.000000000<br>• 20190617T000120<br>• 20190617T000120.000<br>• 20170107T213000.123456789<br>• 20170107 213000.123456789<br>• 20190617 000120.123000000<br><br>Examples which do not comply with Timestamp in STRING format:<br>• 20190617T0120<br>• 20190617T000120.<br><br>As an alternative format, timestamp can be submitted as a value of type Unsigned, representing the number of nanoseconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds. This is also commonly known as POSIX time or UNIX time. The same point in time from the above example would be represented as the number 1483842600123456789. Timestamps submitted in UTC must not be adjusted for Eastern Time.<br><br>Note that the data type is different between the two formats. In JSON, the first representation requires it to be surrounded by double quotes, while the second does not.<br><br>Examples which comply with Timestamp in NUMBER format:<br>• 1483842600123456789<br><br>Examples which do not comply with Timestamp in NUMBER format:<br>• 20190617T000120<br>• 20190617 000120 A timestamp represents a moment in time. Two timestamp formats are supported including STRING and NUMBER. <br> <br> Timestamps formatted as a STRING have a maximum length of 25 and are formatted as ‘YYYYMMDD HHMMSS.CCCNNNNNN’ with the Date and Time portions, separated by a space (ASCII decimal 32, hex 20) or the letter T (ASCII decimal 84, hex 54). All timestamps submitted in STRING format must be in Eastern Time (ET). <br> • The Date portion must include four digit year, two digit month, and two digit day. Valid values: YYYY = 0000 - 9999, MM = 00 - 12, DD = 00 – 31. <br> • The Time portion must include a two digit hour, two digit minute, two digit seconds. Valid values: HH = 00 - 23, MM = 01 - 59, SS = 01 - 59, CCC = 000 – 999, NNNNNN = 000000 - 999999. <br> <br> Examples which comply with Timestamp in STRING format: <br>• 20190617T000120.000000000<br>• 20190617T000120<br>• 20190617T000120.000<br>• 20170107T213000.123456789<br>• 20170107 213000.123456789<br>• 20190617 000120.123000000<br><br>Examples which do not comply with Timestamp in STRING format:<br>• 20190617T0120<br>• 20190617T000120.<br><br>As an alternative format, timestamp can be submitted as a value of type Unsigned, representing the number of nanoseconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds. This is also commonly known as POSIX time or UNIX time. The same point in time from the above example would be represented as the number 1483842600123456789. Timestamps submitted in UTC must not be adjusted for Eastern Time.<br><br>Note that the data type is different between the two formats. In JSON, the first representation requires it to be surrounded by double quotes, while the second does not.<br><br>Examples which comply with Timestamp in NUMBER format:<br>• 1483842600123456789<br><br>Examples which do not comply with Timestamp in NUMBER format:<br>• 20190617T000120<br>• 20190617 000120 eventTimestamp: 20180417T151018.123456 An unsigned value, greater than or equal to zero, with no decimal fraction component, in the inclusive range from 0 to 18,446,744,073,709,551,615 (the same range as a 64-bit unsigned integer). An unsigned value, greater than or equal to zero, with no decimal fraction component, in the inclusive range from 0 to 18,446,744,073,709,551,615 (the same range as a 64-bit unsigned integer). errorROEID: 123456789 An institutional account as defined in FINRA Rule 4512(c) An employee or associated person of the Industry Member or an employee or associated person of affiliated group companies A non-broker-dealer foreign affiliate or non-reporting foreign broker-dealer An account that does not meet the definition of “institution” as defined in FINRA Rule 4512(c) and is also not a proprietary account. See CAT FAQ C5 and CAT FAQ B68 Firm agency average price account Other proprietary Error account of the firm Represents the type of beneficial owner of the account for which an order was received or originated, or to which the shares/contracts are allocated. New record. Correction of events initiated by firms. Repair of events for which a CAT error was provided in feedback. Record level delete instruction. When deleting a record, Industry Members must not restate the event that is being deleted. Refer to Section 7 for instructions on record level deletions. Indicates whether the event is a new event, a correction, a repair or a record level deletion. Order is routed to or received from an affiliate. Order is routed to or received from a non-affiliate. Indicates if the order is being routed to an affiliate or received from an affiliate of the Industry Member. For definition of affiliate, refer to CAT FAQ C4. Allocation to a custody account Allocation to a DVP/RVP account Allocation to a custody account free of payment (if available in the booking system) Allocation to a DVP/RVP account free of payment (if available in the booking system) Options CMTA Correspondent Flip An allocation to a firm owned or controlled account Step out/Step In Other non-reportable transactions (e.g., option exercises, conversions, allocations to the account of a CAT Reporting Industry Member) Indicates the type of allocation being made. Refer to FAQ U26 for additional information. Order is displayed outside of the ATS to subscribers only Order is displayed outside of the ATS to subscribers only, aggregated by price level on a timer basis Order is displayed outside of the ATS via public quotation Order is not displayed outside of the ATS ATS only field. Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. Trade event was cancelled upon rejection by the TRF/ADF/ORF; or fulfillment was cancelled. trade event was not cancelled or cancellation was reported to the TRF/ADF/ORF; or fulfillment event was not cancelled. Represents instances when a trade was cancelled because the trade was rejected by the TRF/ADF/ORF, when a trade executed in a foreign market was cancelled, or when a customer/client fulfillment is cancelled. In such instances, set to ‘true’. Refer to CAT FAQ E25, CAT FAQ E29 and CAT FAQ E30 for additional information. Agency Principal Riskless principal Specifies the capacity in which the Industry Member acted. Customer/client has instructed that a limit order should not be displayed or that a block size order be displayed. No instruction has been received from the customer/client that a limit order should not be displayed or that a block size order should be displayed. Indicates if a customer/client has instructed that a limit order must not be displayed or that a block size order must be displayed contrary to what is required by SEC Rule 604 or FINRA’s Customer Limit Order Display Rule. A desk or department where orders may be routed to other trading centers, either by a trading system or with the assistance of traders. This would include smart routers and algorithmic trading. A trading system that meets the definition of “Alternative Trading System” under Regulation ATS. For CAT reporting purposes, represents when an Industry Member permits a customer to use a market participant identifier assigned to the Industry Member to route orders directly to market centers. For CAT reporting purposes, represents when an Industry Member permits another broker-dealer to use a market participant identifier assigned to the Industry Member to route orders directly to market centers. A desk or department where orders are executed. This may be interpreted as either a trading system or a desk or department where orders are executed with the assistance of traders. A department that does not execute orders or route orders to other trading centers. The value of ‘O’ must only be used on events that are followed by Internal Route Accepted events. Represents the internal department, unit or desk originating or accepting the order. Facility operated by a national securities association. Routing destination is an Industry Member. Routing destination is an exchange. Routing destination is foreign broker-dealer. Not applicable to options events. OTC Equity symbol in a foreign security was sent to another Industry Member, who may route the order to a foreign market for execution. Indicates whether the destination of the route is an Industry Member, an exchange or a foreign broker-dealer. Event contains a duplicated routedOrderID or routedQuoteID. Event does not contain a duplicated routedOrderID or routedQuoteID. On Order Route events and Route Modified events, indicates when a modification to an order previously routed to a national securities exchange requires the use of the original routedOrderID. On New Quote and Quote Received events, indicates when the quote event maintains the same routedQuoteID. Event is a duplicative electronic message. Event is not a duplicative electronic message. Indicates whether the event is a duplicative electronic message of a manual event. Must be present if true. FINRA Alternative Display Facility NYSE American Equities NYSE American Options NYSE ARCA Equities NYSE ARCA Options BOX Options Exchange Boston Security Token Exchange Nasdaq BX Equities Cboe BYX Exchange Cboe BZX Equities Cboe BZX Options Cboe C2 Options Cboe Exchange NYSE CHX Cboe EDGA Exchange Cboe EDGX Equities Cboe EDGX Options MIAX Emerald Nasdaq GEMX Investors Exchange Nasdaq ISE Long Term Stock Exchange Members Exchange Miami International Securities Exchange Nasdaq MRX Nasdaq BX Options Nasdaq Options Nasdaq Stock NYSE National The New York Stock Exchange MIAX PEARL MIAX PEARL Equities Nasdaq PHLX Options Nasdaq PHLX Equities The SRO-assigned identifier of the Exchange to which an order was routed. Fulfillment on an order routed to a foreign destination, no linkage required Representative Order, linkage required Order eligible for customer/client fills via an unlinked system (unlinked OMS-EMS or position fill). <br> All Industry Members will be required to provide representative order linkages to unlinked OMS/EMS and position fill scenarios no later than July 31, 2024 due to the expiry of the exemptive relief granted by the SEC on July 8, 2022. Fill from pre-existing Principal order or pre-existing quote, linkage required Representative Order, linkage required, details provided in a supplement event Options Order Fulfillment Combined Options Order, linkage required, details provided in a supplement event Multi-Leg Options Order Fulfillment Specifies the type of the fulfillment. Refer to Appendix C for additional information on Representative Order linkage requirements. Initiated by the Customer/Client Initiated by the firm Indicates who initiated a cancel or modification request. If an order is modified or cancelled based on an implicit customer/client instruction, then the initiator field must be populated with a value of ‘F’. Refer to CAT FAQ B63 for additional information. Account meets the definition of institution under FINRA Rule 4512(c). Account does not meet the definition of institution under FINRA Rule 4512(c). Indicates if the account meets the definition of institution under FINRA Rule 4512(c). Intermarket Sweep Order - Day Intermarket Sweep Order – IOC Not applicable Indicates the order was an Intermarket Sweep Order NYSE American NYSE OTCBB NYSE ARCA Nasdaq OTC Equity IEX Cboe BZX The primary listing exchange of the instrument. Event was received/handled manually. Event was not received/handled manually. Indicates whether an order was received or handled manually. FINRA Alternative Display Facility FINRA/Nasdaq Chicago Trade Reporting Facility FINRA/NYSE Trade Reporting Facility FINRA/Nasdaq Trade Reporting Facility OTC Reporting Facility NYSE MKT Nasdaq BX Boston Security Token Exchange NYSE National Non-US Exchange MIAX PEARL Equities International Securities Exchange Cboe EDGA Exchange Cboe EDGX Exchange Long Term Stock Exchange NYSE Chicago Stock Exchange New York Stock Exchange NYSE Arca The Nasdaq Stock Market Members Exchange Investors Exchange Cboe Stock Exchange Nasdaq PSX Cboe BYX Exchange Cboe BZX Exchange NYSE ARCA Options NYSE American Options BOX Options Exchange Cboe BZX Options Exchange Cboe C2 Options Cboe Exchange NYSE CHX Cboe EDGX Options MIAX Emerald Nasdaq GEMX Nasdaq ISE Miami International Securities Exchange Nasdaq MRX NASDAQ BX Options NASDAQ Options Market MIAX PEARL NASDAQ PHLX Options For equities MEOT events, the national securities exchange or transaction reporting system operated by a registered securities association where the trade was reported. For options MOOT events, the options exchange where the trade occurred. Open Close Market Participant Status Code - indicates if the market maker's quote was open or closed. The immediately preceding event in the order life cycle is a Multi-Leg order event. The immediately preceding event in the order life cycle is not a Multi-Leg order event. Indicates when the immediately preceding event in the order life cycle is a Multi-Leg order event. Refer to Section 5.2.2 for additional guidance. Direct SIP NBBO Source of Hybrid is used in instances where the firm uses a combination of Direct and SIP feeds as its NBBO Source. Not applicable ATS only field. Source of the NBBO data used. NBBO Source of ‘NA’ is used when the NBBO Engine Look up Date and Time is not applicable for the ATS Order Type or the ATS cancelled the order without referencing the NBBO. If this value is used, the related NBBO price and quantity fields must be populated with a value of ‘0’ and the nbboTimestamp must be blank. Indicates the trade is a result of a negotiation. Indicates the trade is not the result of a negotiation. Identifies if an order is the result of a negotiated trade between two parties. System allows only one quote. System allows multiple quotes. Identifies instances when the quoting system allows only one quote to be active at a time for the particular market maker. Order marked as open upon entry into the exchange. Order marked as close upon entry into the exchange. Indicates when exchange rules require an order to be marked as open or close upon entry into the exchange. Must be reported as a point-in-time value on each event (therefore, this may differ between New Option Order and Option Order Route for the same orderID). Cabinet order Limit order Market order The type of order being submitted. “Per Unit” price representing the leg ratios as specified in the legDetails block “Total Cash” amount to settle the full quantity of all legs (i.e., inclusive of the 100 multiplier for option legs) “Total Strategy” price for the full quantity of all legs On multi-leg order events, indicates how the net price was represented in the price field. Quote was rejected or no response was received from the destination. Quote was not rejected by the destination. Indicates if the quote was not accepted by the destination. Ask wanted Bid wanted Indicates if the quote message received by an IDQS is a request for a bid or an ask. Agency Arbitrage Block trading Convertible desk Central risk book Derivatives Equity capital markets Floor broker International Institutional Other Preferred trading Proprietary Program trading Sales Swaps Trading desk Treasury Indicates the type of desk or department within the firm that received the order. More granular than the field deptType. Only required when the destination of an internal route is a desk. Industry Member was the contra side of the trade report for a trade which was reported to a TRF/ORF/ADF via a QSR or AGU. Reported on Form T pursuant to FINRA Trade Reporting Rules. Trade was executed by a non-FINRA member and reported to the TRF by the FINRA member counterparty. Intra–firm order where there is no change in beneficial ownership. Indicates the reason that a unique identifier (e.g., Branch Sequence Number, Compliance ID) was not supplied to a transaction reporting system. Representative order, linkage required Representative eligible - Order eligible for customer/client fills via an unlinked system (unlinked OMS-EMS or position fill workflow). <br> All Industry Members will be required to provide representative order linkages to unlinked OMS/EMS and position fill scenarios no later than July 31, 2024 due to the expiry of the exemptive relief granted by the SEC on July 8, 2022. Representative order, pricing guarantee, no linkage required. <br> All Industry Members will be required to provide representative order linkages to unlinked OMS/EMS and position fill scenarios no later than July 31, 2024 due to the expiry of the exemptive relief granted by the SEC on July 8, 2022. Representative order, linkage required; details in supplement event Not a representative order, linkage is not applicable Indicates the type of representative order being reported and whether linkage is required. Refer to Appendix C for additional information on Representative Order linkage requirements. Ask Bid Combined Quote containing Ask and Bid Neither Details in supplement event Indicates if the quote represents customer/client orders. Routed order was rejected or no response was received from the destination. Routed order not rejected by the destination. Indicates the routed order was not accepted by the destination (i.e., rejected, no response). Refer to Section 2.6.3.5 for additional information. Exchange Industry Member OTC Equity symbol in a foreign security was sent by another Industry Member, who may not have a CAT reporting obligation Identifies from where a routed order originated. Buy Sell long Short sale Short sale exempt Side of the event. Allowable side values are based on the corresponding Event Type and side as shown below. The Trade event is one sided, and the reporter is on the Buy side of the trade. Only the buyDetails are populated. The Trade event is one sided, and the reporter is on the Sell side of the trade. Only the sellDetails are populated. Not Applicable – the Trade event is not one sided. Identifies if a Trade event is one sided, and which side of the trade the Industry Member is populating in the Trade Side Details. Event was received or originated as the result of a response to an RFQ or other solicitation process. Event was not received or originated as the result of a response to an RFQ or other solicitation process. 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. To be executed only on a Foreign Market Pre-Market Only Pre-Market and Regular Regular Only Regular and Post-Market Post-Market Only Pre-Market and Post-Market Order can trade in any available session at the venue where it is sent. Refer to FAQ D32 for additional information. The trading session(s) during which an order is eligible to trade. Reported when an Industry Member originates an order, receives a customer order, originates a bunched, representative or proprietary order, or receives an order from a non-reporting foreign entity. Supplement to the New Order event, used when the New Order event exceeds the maximum length allowed, or when the orders being represented are not captured in the New Order Event. Also used to provide an FDID once known if not available at time of reporting a MENO. Reported when an Industry Member routes an order to another broker-dealer, exchange or ATS. Reported when an Industry Member modifies a route that was sent to another broker-dealer, exchange or ATS. Reported when an Industry Member cancels a route that was sent to another broker-dealer, exchange or ATS. Supplement to the Order Route event, optionally used to populate the routeRejectedFlag. Supplement to the Route Modified event, optionally used to populate the routeRejectedFlag. Supplement to the Route Cancelled event, optionally used to populate the routeRejectedFlag. Reported when an Industry Member, including an ATS, accepts a routed order that originated at another broker-dealer. Reported when an order moves within an Industry Member to another desk or other department. Reported when an Order Internal Route Accepted was modified. Reported when an Order Internal Route Accepted was cancelled. Reported when a modification to an internal route was requested. Reported when the cancellation of an internal route was requested. Reported when an order is sliced within the desk or department it is being worked, and is assigned a new order identifier. Reported when a Child Order is modified. Reported when a Child Order is cancelled. Reported when changes to the Material Terms of an order are made, or an order is cancel/replaced. Supplement to the Order Modified event, used when the Order Modified event exceeds the maximum length allowed, or when the orders being represented are not captured in the Order Modified event. Reported when a request to modify an order is received. Used to report simple order modifications including changes to the price or quantity of the order. Reported when an Industry Member fully or partially cancels an order. Reported when a request to cancel an order is received. Reported when quotations in equity Eligible Securities are originated that are ultimately sent to a quote display facility or quote driven ATS. Supplement to the New Quote event, used when the number of Aggregated Orders included in the askAggregatedOrders or bidAggregatedOrders fields cause the New Quote event to exceed the maximum allowed message length, or when the orders being represented are not captured in the New Quote event. Reported when quotations in equity Eligible Securities are sent to a quote display facility or quote driven ATS. Supplement to the Routed Quote event, used when reporting in scenarios where a quote route is rejected by the venue to which it was routed, and the Industry Member chooses to report the quoteRejectedFlag in this separate Routed Quote Supplement event. Reported when a quote is received by an Industry Member. Reported when a quote is cancelled. Reported when a quote is modified and the venue supports more than one quote per symbol for an Industry Member at one time. Reported when the status of a quote is changed. Reported by the executing venue where the trade occurred, with details associated with each side of the trade. Reported when there is more than one order associated with one side of a trade. Reported when the execution of a customer/client order is not required to be reported for public dissemination. The event includes details associated with the customer/client side and firm side. Reported when there is more than one representative proprietary order associated with the fill of a customer/client order. Reports the amendment of a previously reported fulfillment, including the full restatement of the event with applicable changes represented. Reported when executed shares are allocated to end customer accounts during post-trade processing. Reported when an amendment occurs to a previously reported post- trade allocation. Reported when an order or an underlying condition of an order becomes effective. The generic message is for testing purposes only. Reportable Events for equities that are Eligible Securities. The following table lists each equity event type with its corresponding Message Type code. Unsolicited Bid and Ask Unsolicited Ask Unsolicited Bid Not Unsolicited Indicates when the quote is unsolicited. Quote is unpriced. Quote is not unpriced. Indicates when a quote is unpriced. Text(64) Text(64) IndustryMemberID/ExchangeID Text(40) Text(4) Text(40) Text(64) Text(64) Text(20) Text(64) Text(64) Text(40) Text(40) Text(22) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(64) Text(0) Text(0) Text(64) Text(64) Text(64) IndustryMemberID/ExchangeID Alphanumeric(40) Text(40) Text(40) Text(64) Primary Listing Exchange. Add on Order. The customer adds additional shares to the order after it was fully executed. Automated Investment Plan. Customer order was originated in accordance with an Automated Investment Plan. Order was received or originated with instructions to work using a Trading Algorithm as defined in the Glossary. Order originally received with instructions to work using a Trading Algorithm is later modified by the customer/client to use a different Trading Algorithm or change the settings of the trading algorithm. Indicates that the event is part of an algorithmic strategy where the specific quantity may not be explicitly provided. Add Liquidity Only At or Between. Instructs the trader to execute at a trade price equal to the NBBO or between the NBBO and the midpoint. Auction or Kill. Applicable to exchange auctions. All or None Attributable. Order is routed to an exchange or ATS with instructions that the order is attributable. Buy-In – An order executed pursuant to SEC or SRO rules (e.g., to comply with the close out requirements of Regulation SHO or FINRA Rule 4320, or the buy-in requirement of SEA Rule15c3-3). Refer to CAT FAQ B37. Customer Accommodation Correction. ‘COR’ event was submitted to CAT as the result of a customer accommodation. Not to be used if the ‘COR’ event was submitted to correct an error by the Industry Member. Contingent on Market Conditions Electronic message representing an individual simple option or equity leg of a complex option order that was optionally reported to CAT. Conditional Order. An order where the terms and conditions of the order are derived from a related transaction. Counterparty Restriction. Instructions that the order cannot be placed against certain counterparties. OTC Link ATS Counter Message. Indicates that a New Order event, Order Route event or Order Accepted event represents the origination, route or receipt of a counter message through OTC Link ATS. Contingent on Spread Condition - order with a condition that may cause the order to become active or inactive multiple times throughout the day. Delivery Instruction: Cash trade settles on the same date. Discretionary Peg Delta-Adjusted at Close. A DAC order is an options order that executes during the trading day and, for which, the execution price is adjusted based on a delta value applied to the change in the price of the underlying reference price from the time of order execution to the market close. Directed Orders – Orders that meet the definition of “Directed Order” under Regulation NMS (formerly defined under SEC Rule 11Ac1–6), or any other order that is received or originated with instructions to route to a particular venue for execution. Dividend Reinvestment Order. Order is part of a dividend reinvestment program. Do Not Increase Do Not Reduce Do Not Route Exchange Retail Provider – An order routed to an exchange to interact with retail orders as part of a retail pricing program. Pricing, display and counterparty eligibility for exchange retail provider orders are subject to the rules of the receiving exchange. Exchange for Physical Transaction – Equity trade component of an “exchange for physical” transaction. An exchange for physical transaction involves two parties simultaneously executing a futures contract and an equity transaction (for the securities covered by the futures contract), typically involving baskets that replicate common indices. Cboe Floor Broker. Indicates that the order is directed to a Cboe floor broker. NYSE Floor Broker Algorithm indicates that the order is routed to the Exchange via a NYSE Floor Broker Algorithm. Fill or Kill - Indicates the order is intended for immediate execution in its entirety, and if not executed in its entirety, the order is cancelled Suspend Futures Related Trade. Price or size of a cash order is contingent upon a related futures trade. G Order – An order for an account covered by Exchange Act §11(a) that relies on §11(a)(1)(G) as an exemption to §11(a)(1). Guaranteed Price. Order was received or originated with instructions to execute at a guaranteed price. Intra-Day Cross Imbalance Only Limit on Close - Instructs the trader to execute the order at the closing price provided that the closing price is at or within the limit specified. Limit on Open - Instructs trader to execute the order at the opening price provided that the opening price is at or within the limit specified. Midpoint Peg Market at Close. Instructs the trader to execute the order at the closing inside quote price of regular market hours. Market at Open. Instructs the trader to execute the order at the opening inside quote price of regular market hours. OTC Link ATS Message MAX instruction. Reflects the maximum number of shares to be executed between selected market makers. Midpoint or Better. Instructs the trader to execute at a trade price equal to the midpoint or better. Market on Close. Instructs the trader to execute the order at the closing last sale price of regular market hours. Market on Open. Instructs the trader to execute the order at the opening print price of regular market hours. Merger Related Transfer Position Market to Limit. An order that is sent in as a market order to execute at the current best price. If the entire order does not immediately execute at the market price, the remainder of the order is resubmitted as a limit order with the limit price set to the price at which the original order executed. Net Asset Value. Order was received or originated with instructions to execute at a Net Asset Value. OTC Link ATS No Counter. Indicates if an OTC Link ATS message cannot be countered with an inferior price. Delivery Instructions: Next Day – equity trade settles on next trade date. Not applicable to options. Not Held OTC Link ATS instruction to cancel after partial execution. Price includes offset Opt Out of Locked Market Options Related Trade. Price or size of a cash order is contingent upon a related option trade Refer to CAT FAQ K5 for additional information. Over the Day. Requires that a trader break up an order into several partial executions. The customer may specify the number of executions. Market Peg Price Based on Greeks - Indicates that the limit price is to be determined by Greeks or other formula based on market conditions. Position Compression Service – Indicates that the order is to be executed through an exchange position compression service. Indicates that the limit price is to be determined by a specific market price and/or volume factor or that the limit price should be determined pursuant to a specific formula. Route was related to an order that was sent as a Qualified Contingent Cross. Primary Peg Routed as Received. For orders routed without any changes to the handling instructions, reporters may use this code to indicate that the handling instructions are equal to the received order. Retail Liquidity Order. Order is routed to an exchange marked as a retail order. Reserve Size Order. Required for an order for which a customer has authorized the public display of part of the full size of the order with the remainder held in reserve on an undisplayed basis to be displayed in whole or in part as the displayed part is executed. Scale. Requires partial executions that are not more than a specified price increment apart. Slide. Order is routed to an exchange or ATS with an instruction to adjust the limit price to prevent a locked or crossed market. Strategy Legs Later. Indicates that the multi-leg strategy order contains multiple option legs, where at least one leg is known and the receiving party determines one or more of the leg(s). Stop Limit on Quote. An order that is triggered by a quotation at which point the stopped order becomes a limit order. Delivery Instructions: Seller’s Option - trade settles on the date determined by a seller. Stop on Quote. An order that is triggered by a quotation at which point the stopped order becomes a market order. Stop Formula – exact stop price is unknown because it is either based on an underlying condition or will be determined by the destination venue. Self Trade Prevention TS Trailing Stop Trailing stop Tied to Fixed Income Tied to a product that is not CAT reportable and is not identified through any other handlingInstructions value. Tied to Stock Tied to Simple Option Tied to Unlisted Option Unpriced Quote on an Order Driven Market – Applicable to orders received by Global OTC. Unsolicited Quote on an Order Driven Market – Applicable to orders received by Global OTC. With Discretion Price - Discretion on Limit Price Within a Specified Range. Work. Leaves the time of execution to the trader’s discretion either full execution or partial executions are accepted. Auction Response. Requires the Auction ID value for option orders originated in response to an exchange auction. If there is no Auction ID, must be populated with a value of ‘NOAUCID’ Cash Order. Instructs the Trader to buy or sell as much of a security as possible for a specified amount. Display Price. The display price at the time the order is received, originated, or routed. Requires a numeric value representing the display price (e.g., DISP=10.00) Display Quantity. The display quantity at the time the order is received, originated, or routed. Requires a numeric value representing the display quantity (e.g., DISQ=1000) Data Type: Real Quantity OTC Link ATS Message delivered from instruction. On an Order Accepted event reflecting the receipt of an OTC Link Message from OTC Link ATS or an Order Route event reflecting the route of an OTC Link Message by OTC Link ATS, reflects the IMID of the Industry Member that the OTC Link Message was delivered from (e.g., DLVF:IMID) OTC Link ATS Message deliver to instruction. On an Order Route event reflecting the route of an OTC Link Message to OTC Link ATS or an Order Accepted event reflecting the receipt of an OTC Link Message by OTC Link ATS, reflects the IMID of the Industry Member that the OTC Link Message was delivered to (e.g., DLVT:IMID) Stop Price - requires a Numeric value representing the stop price (e.g., STOP=17.95) Stop Stock Transaction – Any transaction resulting from an order for which a member and another party agree that the order will be executed at a Stop Stock Price or better. Requires a numeric value representing the agreed stop price. Stop Stock Quantity - requires a Numeric value representing the quantity of shares of a stop stock order being stopped if the entire shares quantity of the order is not being stopped (e.g., SWQ=500). When SWQ is populated, SW must also be populated. The trigger time of the Time Managed Order (e.g. the specific date and time that an order becomes a market or limit price order) - requires a Timestamp value. Text(0) Text(0) Text(0) Text(0) Text(0) Text(0) Text(0) Text(0) Text(0) timeInForce timeInForce timeInForce timeInForce timeInForce timeInForce timeInForce timeInForce timeInForce Add on Order. The customer adds additional shares to the order after it was fully executed. Automated Investment Plan. Customer order was originated in accordance with an Automated Investment Plan. Order was received or originated with instructions to work using a Trading Algorithm as defined in the Glossary. Order originally received with instructions to work using a Trading Algorithm is later modified by the customer/client to use a different Trading Algorithm or change the settings of the trading algorithm. Indicates that the event is part of an algorithmic strategy where the specific quantity may not be explicitly provided. Add Liquidity Only At or Between. Instructs the trader to execute at a trade price equal to the NBBO or between the NBBO and the midpoint. Auction or Kill. Applicable to exchange auctions. All or None Attributable. Order is routed to an exchange or ATS with instructions that the order is attributable. Buy-In – An order executed pursuant to SEC or SRO rules (e.g., to comply with the close out requirements of Regulation SHO or FINRA Rule 4320, or the buy-in requirement of SEA Rule15c3-3). Refer to CAT FAQ B37. Customer Accommodation Correction. ‘COR’ event was submitted to CAT as the result of a customer accommodation. Not to be used if the ‘COR’ event was submitted to correct an error by the Industry Member. Contingent on Market Conditions Electronic message representing an individual simple option or equity leg of a complex option order that was optionally reported to CAT. Conditional Order. An order where the terms and conditions of the order are derived from a related transaction. Counterparty Restriction. Instructions that the order cannot be placed against certain counterparties. OTC Link ATS Counter Message. Indicates that a New Order event, Order Route event or Order Accepted event represents the origination, route or receipt of a counter message through OTC Link ATS. Contingent on Spread Condition - order with a condition that may cause the order to become active or inactive multiple times throughout the day. Delivery Instruction: Cash trade settles on the same date. Discretionary Peg Delta-Adjusted at Close. A DAC order is an options order that executes during the trading day and, for which, the execution price is adjusted based on a delta value applied to the change in the price of the underlying reference price from the time of order execution to the market close. Directed Orders – Orders that meet the definition of “Directed Order” under Regulation NMS (formerly defined under SEC Rule 11Ac1–6), or any other order that is received or originated with instructions to route to a particular venue for execution. Dividend Reinvestment Order. Order is part of a dividend reinvestment program. Do Not Increase Do Not Reduce Do Not Route Exchange Retail Provider – An order routed to an exchange to interact with retail orders as part of a retail pricing program. Pricing, display and counterparty eligibility for exchange retail provider orders are subject to the rules of the receiving exchange. Exchange for Physical Transaction – Equity trade component of an “exchange for physical” transaction. An exchange for physical transaction involves two parties simultaneously executing a futures contract and an equity transaction (for the securities covered by the futures contract), typically involving baskets that replicate common indices. Cboe Floor Broker. Indicates that the order is directed to a Cboe floor broker. NYSE Floor Broker Algorithm indicates that the order is routed to the Exchange via a NYSE Floor Broker Algorithm. Fill or Kill - Indicates the order is intended for immediate execution in its entirety, and if not executed in its entirety, the order is cancelled Suspend Futures Related Trade. Price or size of a cash order is contingent upon a related futures trade. G Order – An order for an account covered by Exchange Act §11(a) that relies on §11(a)(1)(G) as an exemption to §11(a)(1). Guaranteed Price. Order was received or originated with instructions to execute at a guaranteed price. Intra-Day Cross Imbalance Only Limit on Close - Instructs the trader to execute the order at the closing price provided that the closing price is at or within the limit specified. Limit on Open - Instructs trader to execute the order at the opening price provided that the opening price is at or within the limit specified. Midpoint Peg Market at Close. Instructs the trader to execute the order at the closing inside quote price of regular market hours. Market at Open. Instructs the trader to execute the order at the opening inside quote price of regular market hours. OTC Link ATS Message MAX instruction. Reflects the maximum number of shares to be executed between selected market makers. Midpoint or Better. Instructs the trader to execute at a trade price equal to the midpoint or better. Market on Close. Instructs the trader to execute the order at the closing last sale price of regular market hours. Market on Open. Instructs the trader to execute the order at the opening print price of regular market hours. Merger Related Transfer Position Market to Limit. An order that is sent in as a market order to execute at the current best price. If the entire order does not immediately execute at the market price, the remainder of the order is resubmitted as a limit order with the limit price set to the price at which the original order executed. Net Asset Value. Order was received or originated with instructions to execute at a Net Asset Value. OTC Link ATS No Counter. Indicates if an OTC Link ATS message cannot be countered with an inferior price. Delivery Instructions: Next Day – equity trade settles on next trade date. Not applicable to options. Not Held OTC Link ATS instruction to cancel after partial execution. Price includes offset Opt Out of Locked Market Options Related Trade. Price or size of a cash order is contingent upon a related option trade Refer to CAT FAQ K5 for additional information. Over the Day. Requires that a trader break up an order into several partial executions. The customer may specify the number of executions. Market Peg Price Based on Greeks - Indicates that the limit price is to be determined by Greeks or other formula based on market conditions. Position Compression Service – Indicates that the order is to be executed through an exchange position compression service. Indicates that the limit price is to be determined by a specific market price and/or volume factor or that the limit price should be determined pursuant to a specific formula. Route was related to an order that was sent as a Qualified Contingent Cross. Primary Peg Routed as Received. For orders routed without any changes to the handling instructions, reporters may use this code to indicate that the handling instructions are equal to the received order. Retail Liquidity Order. Order is routed to an exchange marked as a retail order. Reserve Size Order. Required for an order for which a customer has authorized the public display of part of the full size of the order with the remainder held in reserve on an undisplayed basis to be displayed in whole or in part as the displayed part is executed. Scale. Requires partial executions that are not more than a specified price increment apart. Slide. Order is routed to an exchange or ATS with an instruction to adjust the limit price to prevent a locked or crossed market. Strategy Legs Later. Indicates that the multi-leg strategy order contains multiple option legs, where at least one leg is known and the receiving party determines one or more of the leg(s). Stop Limit on Quote. An order that is triggered by a quotation at which point the stopped order becomes a limit order. Delivery Instructions: Seller’s Option - trade settles on the date determined by a seller. Stop on Quote. An order that is triggered by a quotation at which point the stopped order becomes a market order. Stop Formula – exact stop price is unknown because it is either based on an underlying condition or will be determined by the destination venue. Self Trade Prevention TS Trailing Stop Trailing stop Tied to Fixed Income Tied to a product that is not CAT reportable and is not identified through any other handlingInstructions value. Tied to Stock Tied to Simple Option Tied to Unlisted Option Unpriced Quote on an Order Driven Market – Applicable to orders received by Global OTC. Unsolicited Quote on an Order Driven Market – Applicable to orders received by Global OTC. With Discretion Price - Discretion on Limit Price Within a Specified Range. Work. Leaves the time of execution to the trader’s discretion either full execution or partial executions are accepted. Auction Response. Requires the Auction ID value for option orders originated in response to an exchange auction. If there is no Auction ID, must be populated with a value of ‘NOAUCID’ Cash Order. Instructs the Trader to buy or sell as much of a security as possible for a specified amount. Display Price. The display price at the time the order is received, originated, or routed. Requires a numeric value representing the display price (e.g., DISP=10.00) Display Quantity. The display quantity at the time the order is received, originated, or routed. Requires a numeric value representing the display quantity (e.g., DISQ=1000) Data Type: Real Quantity OTC Link ATS Message delivered from instruction. On an Order Accepted event reflecting the receipt of an OTC Link Message from OTC Link ATS or an Order Route event reflecting the route of an OTC Link Message by OTC Link ATS, reflects the IMID of the Industry Member that the OTC Link Message was delivered from (e.g., DLVF:IMID) OTC Link ATS Message deliver to instruction. On an Order Route event reflecting the route of an OTC Link Message to OTC Link ATS or an Order Accepted event reflecting the receipt of an OTC Link Message by OTC Link ATS, reflects the IMID of the Industry Member that the OTC Link Message was delivered to (e.g., DLVT:IMID) Stop Price - requires a Numeric value representing the stop price (e.g., STOP=17.95) Stop Stock Transaction – Any transaction resulting from an order for which a member and another party agree that the order will be executed at a Stop Stock Price or better. Requires a numeric value representing the agreed stop price. Stop Stock Quantity - requires a Numeric value representing the quantity of shares of a stop stock order being stopped if the entire shares quantity of the order is not being stopped (e.g., SWQ=500). When SWQ is populated, SW must also be populated. The trigger time of the Time Managed Order (e.g. the specific date and time that an order becomes a market or limit price order) - requires a Timestamp value. Order handling instructions qualify the pricing, quantity, execution timing, or execution method of an order. All instructions that apply to the order must be included. The handlingInstructions field may contain zero or more order handling instruction codes. There is no limit to the number of handlingInstructions that may be populated in a record. Codes which require a value will include that value immediately after the code Field Name and a single equal sign (ASCII decimal 61, hex 3D). Allowed Values include both choice fields and Name/Value Pairs. Name/Value Pairs must be accompanied by a Value. Values are case sensitive. Day Order – Requires the expiration date which must be equal to Event Date or Event Date plus one Trading Day. OTC Link ATS message Good for Duration – Requires the duration in the number of whole seconds. Only Applicable to order events representing OTC Link ATS messages. Good till Cancelled Good till Date – Requires the expiration date. Good this Month – Valid until last business day of the month in which the order originated. Good till Time – Requires the expiration timestamp. Good till Crossing – Requires the expiration date which must be equal to Event Date or Event Date plus one Trading Day. Immediate or Cancel Immediate or Return – Only applicable to options floor brokers. Specifies the Time in Force for an order. Repeating group below should contain unique combinations of orderID and orderKeyDate Repeating group of aggregatedOrders components. Used to specify the individual customer/client order(s) being represented by a New Order event. orderID of the order being represented. orderKeyDate of the order being represented. Required when a partial quantity of the order is being represented. 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. The reporting of Aggregated Order Details indicated below is applicable only for an Industry Member generating quotes and displaying them on a Display-only Facility. The Aggregated Order Details associated with fields: askAggregatedOrders and bidAggregatedOrders: orderID of the order being represented. orderKeyDate of the order being represented. Required when a partial quantity of the order is being represented. 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. The reporting of Aggregated Order Details indicated below is applicable only for an Industry Member generating quotes and displaying them on a Display-only Facility. The Aggregated Order Details associated with fields: askAggregatedOrders and bidAggregatedOrders: Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID of the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field is Reserved for Future Use and must remain blank. Field position is retired and must remain blank. The execution quantity associated with this orderID. 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. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID of the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field position is retired and must remain blank. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. 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. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. The orderKeyDate of the order on this side. Required if orderID is populated. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. The execution quantity associated with this orderID. 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. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. The orderKeyDate of the order on this side.<br><br>When orderID is populated, firmDesignatedID must be blank. When orderID is blank, firmDesignatedID must be populated. The order ID of the order on this side. The side of the trade. Field is Reserved for Future Use and must remain blank. 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. Required when a market maker was not required to report a New Option Order event in accordance with the November 12, 2020 Exemptive Order filed by the SEC10. Must be populated with the FDID of the market maker’s account.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account associated with the firmDesignatedID. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field position is retired and must remain blank. Applicable to firmDetails when fulfillmentLinkType ’YE’ or ‘YP’ is populated, as described in Appendix C. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. C Represents the type of account against which a customer/client order is being filled. 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. Specifies the Order Key and additional information for a Customer/Client Order or Firm Originated Order for which a fulfillment event is associated. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field position is retired and must remain blank. Applicable to firmDetails when fulfillmentLinkType ’YE’ or ‘YP’ is populated, as described in Appendix C. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. C Represents the type of account against which a customer/client order is being filled. 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. Specifies the Order Key and additional information for a Customer/Client Order or Firm Originated Order for which a fulfillment event is associated. Limited to 1 set of details for each side. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the fulfillment. Field position is retired and must remain blank. Applicable to firmDetails when fulfillmentLinkType ’YE’ or ‘YP’ is populated, as described in Appendix C. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. The execution quantity associated with this orderID. 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. The Fulfillment Side Details associated with fields: clientDetails and firmDetails. Limited to 1 set of details for each side. Limited to 1 set of details for each side. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the fulfillment. Field position is retired and must remain blank. Applicable to firmDetails when fulfillmentLinkType ’YE’ or ‘YP’ is populated, as described in Appendix C. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. 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. The Fulfillment Side Details associated with fields: clientDetails and firmDetails. Limited to 1 set of details for each side. Limited to 1 set of details. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. The side of the trade. The execution quantity associated with this orderID. 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. The Fulfillment Side Details associated with fields: firmDetails. Limited to 1 set of details. Limited to 1 set of details for each side. The orderKeyDate of the order on this side. The order ID assigned by the Industry Member to the order on this side. The side of the fulfillment. Field position is retired and must remain blank. 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. The Fulfillment Side Details associated with fields: clientDetails and firmDetails. Limited to 1 set of details for each side. Number of legs in the repeating group. Unique identifier of the leg. The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. Required if the leg being represented is an equity leg. Must be blank if optionID is populated. The 21-character OSI Symbol of the option. For FLEX Percent options, a percentage symbol (%) is appended before the OSI symbol elements. See the Option Symbols section for more information.<br><br>Required if the leg being represented is an option leg. Must be blank if symbol is populated. Indicates whether the action taken (buy or sell) will open a new position or will close an existing position in the order originator’s account. Required when the exchange’s rules require a leg to be marked as open or close upon entry into the exchange.<br><br>Must be blank if symbol is populated. The side of the leg. The ratio of quantity for this individual leg relative to the entire multi-leg security. May be represented as the entire quantity for the leg, or as the lowest common factor. Captures the leg level details for each leg associated with a Multi-Leg order event. This field is in the format of Leg Details, a compound data type that consists of a list of fields (see Section 2.5 Data Types). The legDetails field is used in all Multi-Leg order events to capture the leg level details of each event. Refer to Section 5.2 for the legDetails required in each Multi-Leg order event. If there are more legDetails than can be represented in one event, any additional legDetails must be populated in separate Multi-Leg Order Supplement events. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID of the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field is Reserved for Future Use and must remain blank. Field position is retired and must remain blank. The execution quantity associated with this orderID. 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. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. Required if orderID is populated. The orderKeyDate of the order on this side. The order ID of the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. Field position is retired and must remain blank. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. 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. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. The orderKeyDate of the order on this side. Required if orderID is populated. The order ID assigned by the Industry Member to the order on this side. When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. The side of the trade. The execution quantity associated with this orderID. 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. Applicable to internalized trades as described in Section 4.11 Trade. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account against which a customer/client order is being filled. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. Repeating group below should contain unique combinations of orderKeyDate and either orderID or firmDesignatedID. The orderKeyDate of the order on this side.<br><br>When orderID is populated, firmDesignatedID must be blank. When orderID is blank, firmDesignatedID must be populated. The order ID of the order on this side. The side of the trade. Field is Reserved for Future Use and must remain blank. 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. Required when a market maker was not required to report a New Option Order event in accordance with the November 12, 2020 Exemptive Order filed by the SEC10. Must be populated with the FDID of the market maker’s account.<br><br>When firmDesignatedID is populated, orderID must be blank. When orderID is populated, firmDesignatedID must be blank. Required if firmDesignatedID is populated. Represents the type of account associated with the firmDesignatedID. Captures the Order Key and additional information for the Order associated with the buy or sell side of a Trade Event. 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MENO 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the orderID was assigned. 7 The internal order ID assigned to the order by the Industry Member. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 Must be marked as ‘true’ if the order is received or captured manually. 11 Indicates whether this is a duplicative electronic message of a manual event. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The orderKeyDate of the related manual order. Required when manualOrderID is populated. 14 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’. 15 This is the category of internal department, unit or desk originating or receiving the order. 16 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. 17 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. 18 The side of the order. 19 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’. 20 The order quantity. 21 The minimum quantity of an order to be executed, required when applicable. Must be > 0. 22 The type of order being submitted. 23 The Time in Force for the order. 24 The trading session(s) during which an order is eligible to trade. 25 The order handling instructions for the order. 26 Indicates if a customer/client has instructed that a limit order should not be displayed or that a block size order should be displayed. 27 Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. 28 Represents the type of beneficial owner of the account for which the order was received or originated. 29 Indicates if the routing party is an affiliate of the Industry Member. 30 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. 31 When applicable, the order ID of each customer/client order being represented. Refer to Appendix C for representative order linkage requirements. 32 Indicates whether the trade is a result of a negotiation. 33 Indicates if the order is a representative order and if linkage is required. 34 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. Only required for ATSs. 35 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 36 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”. 37 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”. 38 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’. 39 Shows the ATS-specific order type as selected from a list of order types defined by this reporter via the CAT Reporter Portal. 40 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’. 41 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’. 42 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’. 43 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’. 44 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. 45 The date/time at which the NBBO was referenced A upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 46 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. 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Order Key: aggregatedOrders.orderKeyDate, CATReporterIMID, symbol, aggregatedOrders.orderID * Manual Order Key: manualOrderKeyDate, CATReporterIMID, symbol, manualOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MENOS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the related New Order event which this event is supplementing. 7 The orderID of the related New Order event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the related New Order event which this event supplements (including scenarios in which the supplement is created at a later time). 11 When applicable, the order ID of each customer/client order being represented. Refer to Appendix C for representative order linkage requirements. 12 Required when reporting a supplement to an MENO event that was reported prior to the FDID being available. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. The New Order Supplement event is a supplement to the New Order event. One New Order event can have multiple New Order Supplement events. Multiple New Order Supplement events are considered as additions, not replacements or modifications. This event accommodates reporting in the following scenarios: **Aggregated Orders** This event accommodates reporting in scenarios when the number of Aggregated Orders included in the aggregatedOrders field causes the New Order event to exceed the maximum allowed message length, or when the orders being represented are not captured in the New Order Event. The aggregatedOrders field in the New Order Supplement event must contain the additional Aggregated Orders that were not captured in the original New Order event, or another Supplement event for the same order. **FDID** This event accommodates reporting in scenarios when an Industry Member receives an order for a new account and the new account number, on which the FDID is based, is not yet available for creation and reporting of the CAT new order event. If an FDID has not yet been created when an order has been received, the Industry Member must populate the firmDesignatedID field in its New Order event with a value of ‘PENDING’. Once the FDID becomes available, the Industry Member must report the actual FDID in the firmDesignatedID field in a New Order Supplement event. Any New Order Supplement event with an FDID populated will not be considered late for CAT reporting purposes if it is received by T+3 @ 8:00 AM ET. Refer to the [CAT CAIS Industry Member Reporting Scenarios](https://catnmsplan.com/specifications/imreportingscenarios) for additional information on how the firmDesignatedID will be reflected in the CAIS. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Order Key: aggregatedOrders.orderKeyDate, CATReporterIMID, symbol, aggregatedOrders.orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the event which is being routed. 7 The orderID of the order event which is being routed. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 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. 11 Must be marked as ‘true’ if the order is routed manually. 12 Indicates whether this is a duplicative electronic message of a manual event. 13 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 14 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’. 15 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. 16 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. 17 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’. 18 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. 19 The side of the order. 20 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’. 21 The order quantity. 22 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 23 The type of order being routed. 24 The Time in Force for the order. 25 The trading session(s) during which an order is eligible to trade. 26 Indicates if the order is being routed to an affiliate of the Industry Member. 27 Indicates the order was routed as an Intermarket Sweep Order. 28 The order handling instructions for the order. 29 Indicates the routed order was not accepted by the destination (rejected or no response) when marked ‘true’. 30 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’. 31 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 32 Indicates when the order being routed is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. 33 The pairedOrderID field may be populated if two or more offsetting orders are routed with instructions to cross. 34 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. 35 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. 36 The date and time the quoteID was assigned. Required when quoteID is populated. Must be blank when quoteID is blank. 37 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. 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Route Linkage Key: Event Date, senderIMID, destination, symbol, session, routedOrderID * IDQS Linkage Key: quoteKeyDate, CATReporterIMID, destination, symbol, quoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEMR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the event which is being modified. 7 The orderID of the route which is being modified or the orderID of the immediately preceding Order Modified event. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the route modification. 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. 11 Must be marked as ‘true’ if the route is modified manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The IMID used to identify the Industry Member that is routing the modification, known by the destination. Must equal the senderIMID on the Order Route event being modified. 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’. 14 The destination of the route modification. Must equal the destination on the Order Route event being modified. 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’. 15 Indicates whether the destination of the route modification is an Industry Member, an exchange or a foreign broker-dealer. Must equal the destinationType on the Order Route event being modified. destinationType ‘O’ must only be populated if the symbol is an OTC symbol in a foreign equity security. 16 The ID assigned to the order by the Industry Member when routing the modification to the destination. When dupROIDCond is ‘false’, 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’. 17 The routedOrderID of the Order Route event being modified if the routedOrderID changed when the modification was routed to the destination. Must be populated when routedOrderID is populated and dupROIDCond is ‘false’. Must be blank when dupROIDCond is ‘true’. 18 The session ID used when routing the modification. Must be equal to the session on the Order Route event being modified. 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. 19 The side of the order. For this Reportable Event, only same-side adjustments are allowed (e.g., sell long to short sell). 20 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’. 21 The order quantity. 22 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 23 Field position is retired and must remain blank. 24 The type of order being routed. 25 The Time in Force for the order. 26 The trading session(s) during which an order is eligible to trade. 27 Indicates if the order is being routed to an affiliate of the Industry Member. 28 Indicates the order was routed as an Intermarket Sweep Order. 29 The order handling instructions for the order. 30 Indicates the route modification was not accepted by the destination (rejected or no response) when marked ‘true’. 31 Indicates when a modification to a route maintains the original routedOrderID. 32 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 33 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. 34 Indicates the route modification is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. Industry Members must report a Route Modified event to CAT when the Material Terms of a route have been changed (e.g., price, quantity), or when a route is cancel/replaced. All attributes and Material Terms of the route listed on this event must be restated with the modification(s) reflected. The side field is required to be reported, but side adjustments are only allowed for same-side changes, including changes between Short Sale and Sell Long. Route Modified events must not be used to reflect a change in senderIMID, destination, or destinationType. These changes must be reflected as a Route Cancelled event followed by a new Order Route event. The routedOrderID of the Order Route event being modified must be reflected in the Route Modified event. If the routedOrderID changed when the route was modified, the routedOrderID of the Order Route event being modified must be populated in the priorRoutedOrderID field. If the routedOrderID did not change when the route was modified, the routedOrderID of the Order Route event must be populated in the routedOrderID field, and the dupROIDCond must be populated as ‘true’. If a route modification request is rejected by the destination venue, the Route Modified event must be reported with a routeRejectedFlag of true. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Route Linkage Key: Event Date, senderIMID, destination, symbol, session, routedOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MECR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the route which is being cancelled. 7 The orderID of the route which is being cancelled or the orderID of the immediately preceding Order Modified event. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the route cancellation. 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. 11 Must be marked as ‘true’ if the route being cancelled was a manual route. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The quantity being cancelled. 14 Field position is retired and must remain blank. 15 The IMID used to identify the Industry Member that is routing the cancellation, known by the destination. Must equal the senderIMID in the Order Route event being cancelled. 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’. 16 When destinationType is ‘F’, this value is the IMID used to identify the Industry Member that is routed order. Must equal the destination in the Order Route event being cancelled, and 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’. 17 Indicates whether the destination of the original Order Route event was 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. 18 The ID assigned to the Order Route event being cancelled. This value must match the value for routedOrderID reported by the destination in their Order Accepted report. Required when destinationType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. 19 The session ID used when routing the order. Must equal the session in the Order Route event being cancelled. 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. 20 Indicates the route cancellation was not accepted by the destination (rejected or no response) when marked ‘true’. 21 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 22 Indicates the route modification is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. Industry Members must report a Route Cancelled event to CAT when a route has been fully or partially cancelled. Partial cancellations of a route may be reported to CAT using a Route Cancelled event or a Route 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. The routedOrderID of the Order Route event being cancelled must be reflected in the Route Cancelled event. If a route cancellation request is rejected by the destination venue, the Route Cancelled event must be reported with a routeRejectedFlag of ‘true’. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEORS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the related Order Route event which this event is supplementing. 7 The orderID of the related Order Route event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the related Order Route event this event supplements (including scenarios in which the supplement is created at a later time). 11 The manualFlag of the related Order Route event this event supplements. Must be marked as ‘true’ if the order is routed manually. 12 The senderIMID of the Order Route event that this event supplements. 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’. 13 The destination of the Order Route event that this event supplements. 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. 14 The destinationType of the Order Route event that this event supplements. 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. 15 The ID assigned to the order by the Industry Member when routing the order to the destination. Must match the routedOrderID of the Order Route event that this event supplements. Required when destinationType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. 16 The session of the Order Route event that this event supplements. 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. 17 Indicates the routed order was not accepted by the destination (rejected or no response) when marked ‘true’. The Order Route Supplement event is a supplement to the Order Route event. Order Route Supplement events are considered as additions to an Order Route event, not replacements or modifications. This event accommodates reporting in scenarios where a route is rejected by the venue to which an order was routed, and the Industry Member chooses to report the routeRejectedFlag in this separate Order Route Supplement event. An Order Route Supplement event may not be used to supplement an Order Route event where the dupROIDCond field is ‘true’. These supplement events will be accepted by CAT, but credit will not be provided to any exchange linkage errors on the Order Route event where the dupROIDCond field is ‘true’. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Route Linkage Key: Event Date, senderIMID, destination, symbol, session, routedOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEMRS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the related Route Modified event this event is supplementing. 7 The orderID of the related Route Modified event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the related Route Modified event this event supplements (including scenarios in which the supplement is created at a later time). 11 The manualFlag of the related Route Modified event this event supplements. Must be marked as ‘true’ if the route modification was sent manually. 12 The senderIMID of the Route Modified event that this event supplements. 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’. 13 The destination of the Route Modified event that this event supplements. 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’. 14 The destinationType of the Route Modified event that this event supplements. 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. 15 The ID assigned to the order by the Industry Member when sending the route modification to the destination. Must match the routedOrderID of the Route Modified event that this event supplements. Required when destinationType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. 16 The session of the Route Modified event that this event supplements. 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. 17 Indicates the route order was not accepted by the destination (rejected or no response) when marked ‘true’. 18 Indicates the route modification is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. The Route Modified Supplement event is a supplement to the Route Modified event. Route Modified Supplement events are considered as additions to a Route Modified event, not replacements or modifications. This event accommodates reporting in scenarios where a route modification is rejected by the venue to which the route modification was sent, and the Industry Member chooses to report the routeRejectedFlag in this separate Route Modified Supplement event. A Route Modified Supplement event may not be used to supplement a Route Modified event where the dupROIDCond field is ‘true’. These supplement events will be accepted by CAT, but credit will not be provided to any exchange linkage errors on the Route Modified event where the dupROIDCond field is ‘true’. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Route Linkage Key: Event Date, senderIMID, destination, symbol, session, routedOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MECRS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the related Route Cancelled event this event is supplementing. 7 The orderID of the related Route Cancelled event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the related Route Cancelled event this event supplements (including scenarios in which the supplement is created at a later time). 11 The manualFlag of the related Route Cancelled event this event supplements. Must be marked as ‘true’ if the route cancellation was sent manually. 12 The senderIMID of the Route Cancelled event that this event supplements. 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’. 13 The destination of the Route Cancelled event that this event supplements. When destinationType is ‘F’, this value is the IMID used to identify the Industry Member that is routed order. Must equal the destination in the Order Route event being cancelled, and 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’. 14 The destinationType of the Route Cancelled event that this event supplements. 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. 15 The ID assigned to the order by the Industry Member when sending the route cancellation to the destination. Must match the routedOrderID of the Route Cancelled event that this event supplements. Required when destinationType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. 16 The session of the Route Cancelled event that this event supplements. 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. 17 Indicates the routed order was not accepted by the destination (rejected or no response) when marked ‘true’. 18 Indicates the route modification is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. The Route Cancelled Supplement event is a supplement to the Route Cancelled event. Route Cancelled Supplement events are considered as additions to a Route Cancelled event, not replacements or modifications. This event accommodates reporting in scenarios where a route cancellation is rejected by the venue to which the route cancellation was sent, and the Industry Member chooses to report the routeRejectedFlag in this separate Route Cancellation Supplement event. A Route Cancellation Supplement event may not be used to supplement a Route Cancelled event where the dupROIDCond field is ‘true’. These supplement events will be accepted by CAT, but while Route Cancelled events are not subject to exchange linkage, Route Cancelled events where the dupROIDCond field is ‘true’ will not be considered supplemented. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOA 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the orderID was assigned. 7 Order ID assigned to the order by the Industry Member upon acceptance. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 Must be marked as ‘true’ if the order is received or captured manually. 11 Indicates whether this is a duplicative electronic message of a manual event. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The IMID of the Industry Member receiving the order. When senderType is ‘F’, this value must equal the destination field on the Order Route event reported by the routing Industry Member. When senderType is ‘O’, this value must equal the destination on the Order Route event if an Order Route event is reported by the destination. When senderType is ‘E’, this value must equal the routingParty on the Order Route event reported by the exchange. 14 When senderType is ‘F’, this value is the IMID of the sending Industry Member from which the order is routed, and must equal senderIMID in the Order Route event reported by the routing Industry Member. When senderType is ‘O’, this value is the IMID of the sending Industry Member from which the order is routed, and must equal the senderIMID in the Order Route event if an Order Route event is reported by the routing Industry Member. When senderType is ‘E’, this value is the Exchange ID of the sending entity from which the order is routed, and must equal the exchange field in the Order Route event reported by the exchange. 15 Indicates the type of origin from which the order is routed. senderType ‘O’ must only be populated if the symbol is an OTC symbol in a foreign equity security. 16 The ID for the order as sent by the routing entity. Must be unique per combination of Event Date, symbol, senderIMID, and receiverIMID. Required when manualFlag is ‘false’. 17 The orderKeyDate of the related manual order. Required when manualOrderID is populated. 18 When this is a duplicative electronic message of a previously (separately) reported manual Order Accepted event, this field is to capture the internal order ID of the manual order. Required when electronicDupFlag is ‘true’. 19 Indicates if the routing party is an affiliate of the Industry Member. 20 This is the category of internal department, unit or desk receiving the order. 21 The side of the order. 22 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’. 23 The order quantity. 24 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 25 The type of order as routed to the destination reporting the accepted event. 26 The Time in Force for the order. 27 The trading session(s) during which an order is eligible to trade. 28 Indicates the order was accepted as an Intermarket Sweep Order. 29 The order handling instructions for the order. 30 Indicates if a customer/client has instructed that a limit order should not be displayed or that a block size order should be displayed. 31 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. 32 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 33 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 34 The displayed price for the 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’. 35 The working price of the order at the time it wasaccepted. When provided, must be greater than or equal to zero. If no current workingPrice, value must be ‘0’. 36 The displayed quantity of the 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’. 37 Shows the ATS-specific order type as selected from a list of order types defined by this Industry Member via the CAT Reporter Portal. 38 The NBBO at the moment the order was 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’. 39 The NBBO at the moment the order was 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’. 40 The NBBO at the moment the order was 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’. 41 The NBBO at the moment the order was 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’. 42 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. 43 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 44 Indicates if the order was received 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. 45 The pairedOrderID field may be populated if two or more offsetting orders are received with instructions to cross. 46 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. An Order Accepted event must be reported to CAT when an Industry Member receives an order from another CAT Reporter (i.e., Industry Member, ATS or exchange), or from another IMID belonging to the same Industry Member (i.e., the same CRD). New customer orders, orders received from a non-broker-dealer affiliate, and orders received from a non-reporting foreign broker-dealer must be reported using a New Order event. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Route Linkage Key: Event Date, senderIMID, receiverIMID, symbol, routedOrderID * Manual Order Key: manualOrderKeyDate, CATReporterIMID, symbol, manualOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEIR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the orderID was assigned. 7 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. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 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. 11 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. 12 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. 13 Must be marked as ‘true’ if the order is routed to another desk manually. 14 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 15 The category of department, unit, or desk that received this Order Internal Route Accepted event. 16 Indicates the type of desk or department receiving the order. More granular than the field deptType. 17 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. 18 The side of the order. 19 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’. 20 The order quantity. 21 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 22 The type of order received from the routing desk or department. 23 The order handling instructions for the order. 24 The Time in Force for the order. 25 The trading session(s) during which an order is eligible to trade. 26 Indicates when the order that was routed internally is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. 27 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. 28 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. 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Parent Order Key: parentOrderKeyDate, CATReporterIMID, symbol, parentOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEIM 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of the order that was internally routed. 7 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. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Order ID has been assigned, this is the orderKeyDate of the event being modified. 10 If a new Order ID has been assigned, this is the orderID of the event being modified. When populated, the priorOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time the internal route was modified (e.g., the time that the order was confirmed to be modified 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. 13 Must be marked as ‘true’ if the internal route is modified manually. 14 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 15 The category of department, unit, or desk that received the internal route. 16 Indicates the type of desk that received the internal route. More granular than the field deptType. 17 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. 18 Indicates who initiated the internal route modification. 19 The side of the order. 20 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’. 21 The order quantity. 22 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 23 The number of shares of the order left open at the receiving desk after the modification has occurred. Must be less than or equal to quantity. 24 The type of order received from the routing desk or department. 25 The order handling instructions for the order. 26 The Time in Force for the order. 27 The trading session(s) during which an order is eligible to trade. 28 The date/time the internal route modification was requested. Required if the request was received from the sending desk, and the request is not captured in a separate MEIMR event. Must not be populated if the request is captured in a separate MEIMR 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. 29 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. 30 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. 31 If a new deskOrderID has been assigned, this is the deskOrderID of the event being modified. When populated, the priorDeskOrderID must not be equal to the deskOrderID. Industry Members must report an Order Internal Route Modified event to CAT when the Material Terms of the internal route have been changed (e.g., price, quantity). All attributes and Material Terms of the modified internal route listed on this event must be restated with the modification(s) reflected. Industry Members may assign a new Order Key to Order Internal Route Modified events. If a unique orderID is assigned, the priorOrderID must be populated with the orderID of the Order Internal Route Accepted event that is being modified, and the priorOrderKeyDate must be populated. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Prior Order Key: priorOrderKeyDate, CATReporterIMID, symbol, priorOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEIC 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the internal route which is being cancelled. 7 The orderID of the internal route which is being cancelled. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time the internal route 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. 11 Must be marked as ‘true’ if the order is cancelled manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The quantity being cancelled. 14 The number of shares of the order left open at the receiving desk after the modification has occurred. 15 Indicates who initiated the internal route cancellation. 16 The date/time the internal route cancellation was requested. Required if the request was received from the sending desk, and the request is not captured in a separate MEICR event. Must not be populated if the request is captured in a separate MEICR 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. 17 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. 18 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. If an internal route is cancelled, an Order Internal Route Cancelled event must be reported. Partial cancellations may be reported using an Order Internal Route Modified event or Order Internal Route Cancelled event with leavesQty. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEIMR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the order event for which the internal route modification was requested. 7 The orderID of the order event for which the internal route modification was requested. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time the internal route modification request was received. 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. 11 Must be marked as ‘true’ if the internal route modification was requested manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The category of department, unit, or desk that received the internal route modification request. 14 Indicates the type of desk that received the internal route modification request. More granular than the field deptType. 15 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. 16 The side of the order. 17 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’. 18 The order quantity. 19 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 20 Field position is retired and must remain blank. 21 The type of order received from the routing desk or department. 22 The order handling instructions for the order. 23 The Time in Force for the order. 24 The trading session(s) during which an order is eligible to trade. 25 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. 26 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. Industry Members must report an Order Internal Route Modification Request event to CAT when a desk within the firm receives a request to modify the Material Terms of an internal route if the request is not captured in the requestTimestamp field of the Order Internal Route Modified event. All attributes and Material Terms of the modified internal route listed on this event must be restated with the requested modification(s) reflected. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEICR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the order event for which the cancellation was requested. 7 The orderID of the order event for which the cancellation was requested. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time the internal route cancellation request was received. 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. 11 Must be marked as ‘true’ if the cancel request was received manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The quantity requested to be cancelled. May populate a zero value to indicate that the cancel was for the full remaining quantity. 14 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. Industry Members must report an Order Internal Route Cancel Request event to CAT when a desk within the firm receives a request to cancel an internal route if the request is not captured in the requestTimestamp field of the Order Internal Route Cancelled event. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MECO 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the orderID was assigned. 7 The internal order ID assigned to the child order by the Industry Member. Must be unique with the orderKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The orderKeyDate of the event from which the Child Order originated. 10 The orderID of the event from which the Child Order originated. The parentOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time at which the child order was originated. Timestamp must be reported to milliseconds or a finer increment up to nanoseconds. 13 The side of the order. 14 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’. 15 The Child order quantity. 16 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 17 The type of order. 18 The Time in Force for the order. 19 The trading session(s) during which an order is eligible to trade. 20 The order handling instructions for the order. 21 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 22 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 23 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”. 24 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”. 25 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”. 26 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’. 27 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’. 28 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’. 29 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’. 30 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. 31 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 32 Indicates when the Child Order was originated from a multi-leg order event. Refer to Section 5.2 for additional guidance. 33 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. 34 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. 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Parent Order Key: parentOrderKeyDate, CATReporterIMID, symbol, parentOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MECOM 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of the Child Order event which is being modified. 7 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 Child Order being modified. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Order ID has been assigned, this is the orderKeyDate of the event being modified. 10 If a new Order ID has been assigned, this is the orderID of the event being modified. When populated, the priorOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time at which the child order was modified (e.g., the time that the child order was confirmed to be cancelled in the firm’s OMS/EMS). Timestamp must be reported to milliseconds or a finer increment up to nanoseconds. 13 The side of the order. 14 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’. 15 The Child order quantity. 16 The minimum quantity of an order to be executed. Must be > 0. 17 The number of shares of the Child Order left open after the modification has occurred. Must be less than or equal to quantity. 18 The type of order. 19 The Time in Force for the order. 20 The trading session(s) during which an order is eligible to trade. 21 The order handling instructions for the order. 22 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 23 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 24 The displayed price of 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”. 25 The working price of the order at the time it was originated. When provided, must be greater than or equal to zero. If no current workingPrice, value must be “0”. 26 The displayed quantity of the 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”. 27 The NBBO at the moment the order was routed. 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’. 28 The NBBO at the moment the order was routed. 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’. 29 The NBBO at the moment the order was routed. 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’. 30 The NBBO at the moment the order was routed. 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’. 31 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. 32 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 33 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. Industry Members must report a Child Order Modified event to CAT when the Material Terms of the child order have been changed (e.g., price, quantity). All attributes and Material Terms of the modified child order listed on this event must be restated with the modification(s) reflected. A Child Order Modified event may not be used when modifying an Order Internal Route Accepted event. Industry Members may assign a new Order Key to Child Order Modified events. If a unique orderID is assigned, the priorOrderID must be populated with the orderID of the Child Order event that is being modified, and the priorOrderKeyDate must be populated. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Prior Order Key: priorOrderKeyDate, CATReporterIMID, symbol, priorOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MECOC 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the Child Order event which is being cancelled. 7 The orderID of the Child Order event which is being cancelled. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time at which the child order was cancelled (e.g., the time that the child order was confirmed to be cancelled in the firm’s OMS/EMS). Timestamp must be reported to milliseconds or a finer increment up to nanoseconds. 11 The side of the order. 12 The quantity of the Child order being cancelled. 13 The number of shares of the Child Order left open after the cancellation. Full cancellation will result in a zero in this field. 14 Field is Reserved for Future Use and must remain blank. 15 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. If a child order is cancelled, a Child Order Cancelled event must be reported. Partial cancellations may be reported using a Child Order Modified event or Child Order Cancelled event with leavesQty. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOM 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of the CAT event which is being modified. 7 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 Order Modified (Cancel/Replace) event which is being modified. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Order Key has been assigned, this is the orderKeyDate of the event being modified. 10 If a new Order Key has been assigned, this is the orderID of the event being modified. When populated, the priorOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time the order was modified (e.g., the time that the order was confirmed to be modified 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. 13 Must be marked as ‘true’ if the order is modified or replaced manually. 14 The orderKeyDate of the related manual order. Required when manualOrderID is populated. 15 When this is a duplicative electronic message of a previously (separately) reported manual Order Modified and Cancel/Replaced event, this field is to capture the internal order ID of the manual order. Required when electronicDupFlag is ‘true’. 16 Indicates whether this is a duplicative electronic message of a manual event. 17 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 18 Required when the modification is received from an Industry Member or an exchange. The IMID of the Industry Member receiving the routed order modification. When senderType is ‘F’, this value must equal the destination field on the Order Route event reported by the routing Industry Member. When senderType is ‘O’, this value must equal the destination on the Order Route event if an Order Route event is reported by the destination. When senderType is ‘E’, this value must equal the routingParty on the Participant Order Modification event reported by the exchange. 19 Required when the modification is received from an Industry Member or an exchange. When senderType is ‘F’, this value is the IMID of the sending Industry Member from which the order is routed, and must equal the senderIMID in the Order Route event reported by the routing Industry Member. When senderType is ‘O’, this value is the IMID of the sending Industry Member from which the order is routed, and must equal the senderIMID in the Order Route event if an Order Route event is reported by the routing Industry Member. When senderType is ‘E’, this value is the Exchange ID of the sending entity from which the order is routed, and must equal the exchange field in the Participant Order Modification event reported by the exchange. 20 Required when the modification is received from an Industry Member or an exchange. Indicates the type of origin from which the order is routed. 21 The ID for the order as sent by the routing entity. Must be unique per combination of Event Date, symbol, senderIMID, and receiverIMID. Required when senderType is ‘F’, ‘E’, or ‘O’, and manualFlag is ‘false’. 22 The date/time the modification was requested. Required if a request was received, and the request is not captured in a separate MEOMR event. Must not be populated if the request is captured in a separate MEOMR 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. 23 Field is Reserved for Future Use and must remain blank. 24 Field is Reserved for Future Use and must remain blank. 25 Field is Reserved for Future Use and must remain blank. 26 Indicates who initiated the order modification. 27 The side of the order. For this Reportable Event, only same-side adjustments are allowed (e.g., sell long to short sell). 28 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’. 29 The order quantity. 30 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 31 The number of shares of the order left open after the modification has occurred. Must be less than or equal to quantity. 32 The type of order being submitted (e.g., market, limit). 33 The Time in Force for the order (e.g. DAY, IOC, GTC). 34 The trading session(s) during which an order is eligible to trade. 35 Indicates the order was an Intermarket Sweep Order. 36 The order handling instructions for the order. 37 Indicates if a customer/client has instructed that a limit order should not be displayed or that a block size order should be displayed. 38 Specifying 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. 39 When applicable, the order ID of each customer/client order being represented. Refer to Appendix C for representative order linkage requirements. 40 Indicates if the order is a representative order and if linkage is required. 41 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 42 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 43 The displayed price of 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”. 44 The working price of the order at the time of the modification. When provided, must be greater than or equal to zero. If no current workingPrice, value must be “0”. 45 The displayed quantity for this order at the time the order was modified. 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”. 46 Shows the ATS-specific order types as selected from a list of order types defined by this ATS. 47 The NBBO at the moment the order was modified. 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’. 48 The NBBO at the moment the order was modified. 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’. 49 The NBBO at the moment the order was modified. 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’. 50 The NBBO at the moment the order was modified. 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’. 51 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. 52 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 53 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. Industry Members must report an Order Modified event to CAT when the Material Terms of an order have been changed (e.g., price, quantity) or when an order is cancel/replaced. All attributes and Material Terms of the modified order listed on this event must be restated with the modification(s) reflected. If the order is a representative order, the aggregatedOrders field must be restated every time the order is modified or cancel/replaced. Changes to the orders being represented in the aggregatedOrders field are considered a modification to the order. The side field is required to be reported, but side adjustments are only allowed for same-side changes, including changes between Short Sale and Sell Long. If a modification results in the generation of new order with a new Order Key which replaces the prior order, the orderID field must capture the identifier for the new order, and the prior order fields must reflect the order that is being replaced. If the order has been modified more than once with a new orderID assigned with each modification, the priorOrderID must refer to orderID of the immediately preceding modification which will not be the original Order ID. If the orderID remains the same during the modification, the priorOrderID must remain blank. Industry Members are not required to report the modification 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 modification request was received that was too late to modify, 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 Modification Request event. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Order Key: aggregatedOrders.orderKeyDate, CATReporterIMID, symbol, aggregatedOrders.orderID * Prior Order Key: priorOrderKeyDate, CATReporterIMID, symbol, priorOrderID * Route Linkage Key: Event Date, symbol, receiverIMID, senderIMID, routedOrderID * Manual Order Key: manualOrderKeyDate, CATReporterIMID, symbol, manualOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOMS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the related Order Modified (Cancel/Replace) event which this event is supplementing. 7 The orderID of the related Order Modified (Cancel/Replace) event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of the Order Modified this event supplements. 11 The order ID of each customer/client order being represented. Refer to Appendix C for representative order linkage requirements. The Order Modified Supplement event serves as a supplement to the Order Modified event, just as the New Order Supplement event serves as a supplement to the New Order event. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Order Key: aggregatedOrders.orderKeyDate, CATReporterIMID, symbol, aggregatedOrders.orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOMR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the order event for which the modification was requested. 7 The orderID of the order event for which the modification was requested. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of receipt of the modification request. 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. 11 Must be marked as ‘true’ if the modification is requested manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 Required when the modification request is received from an Industry Member or an exchange (senderType is ‘F’, ‘E’, or ‘O’). The IMID of the Industry Member receiving the modification request. 14 Required when the modification request is received from an Industry Member or an exchange. When senderType is ‘F’ or ‘O’, this value is the IMID of the sending Industry Member from which the order is routed. When senderType is ‘E’, this value is the Exchange ID of the sending entity from which the modification was requested. 15 Required when the modification request is received from an Industry Member or an exchange. Indicates the type of origin from which the modification was requested. senderType ‘O’ must only be populated if the symbol is an OTC symbol in a foreign equity security. 16 Field is Reserved for Future Use and must remain blank. 17 Field is Reserved for Future Use and must remain blank. 18 The side of the order. For this Reportable Event, only same-side adjustments are allowed (e.g., sell long to short sell). 19 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’. 20 The order quantity. 21 The minimum quantity of an order to be executed. Required when applicable. Must be > 0. 22 The type of order being submitted (e.g., market, limit). 23 The Time in Force for the order (e.g., DAY, IOC, GTC). 24 The trading session(s) during which an order is eligible to trade. 25 Indicates the order was an Intermarket Sweep Order. 26 The order handling instructions for the order. 27 Indicates if a customer/client has instructed that a limit order should not be displayed or that a block size order should be displayed. 28 Specifying 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. 29 Field is Reserved for Future Use and must remain blank. 30 Field is Reserved for Future Use and must remain blank. 31 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 32 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 33 The displayed price of 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”. 34 The working price of the order at the time of the modification request. When provided, must be greater than or equal to zero. If no current workingPrice, value must be “0”. 35 The displayed quantity for this order at the time of the modification request. 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”. 36 Shows the ATS-specific order types as selected from a list of order types defined by this ATS. 37 The NBBO at the time of the modification request. 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’. 38 The NBBO at the time of the modification request. 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’. 39 The NBBO at the time of the modification request. 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’. 40 The NBBO at the time of the modification request. 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’. 41 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. 42 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 43 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. The Order Modification Request event is required when a request is received to modify the Material Terms of an order if the request is not captured in the requestTimestamp field of the Order Modified event. Industry Members are not required to report an Order Modification Request event 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOJ 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of order event which is being modified. 7 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 order event which is being modified. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Order ID has been assigned, this is the orderKeyDate of the event being adjusted. 10 If a new Order ID has been assigned, this is the orderID of the event being adjusted. When populated, the priorOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time at which the order was modified (e.g., the time that the order was confirmed to be modified 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. 13 Must be marked as ‘true’ if the order is adjusted manually. 14 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 15 Indicates who initiated the order adjustment. 16 The limit price of the order. When provided, must be greater than or equal to zero. Required when price, displayPrice, or workingPrice changed. 17 The order quantity. Required when quantity, minQty, leavesQty, or displayQty changed. 18 The minimum quantity of an order to be executed. Required when applicable and when quantity, minQty, leavesQty, or displayQty changed. Must be > 0. 19 The number of shares of the order left open after the adjustment/modification has occurred. Required when quantity, minQty, leavesQty, or displayQty changed. Must be less than or equal to quantity. 20 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 21 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 22 The displayed price of the order. When provided, must be greater than or equal to zero. Required when applicable and when price, workingPrice, or displayPrice changed. 23 The working price of the order. When provided, must be greater than or equal to zero. Required when applicable and when price, workingPrice, or displayPrice changed. 24 The displayed quantity for this order. Required when applicable and when quantity, minQty, leavesQty, or displayQty changed. 25 The NBBO at the moment the order was modified. 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’. 26 The NBBO at the moment the order was modified. 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’. 27 The NBBO at the moment the order was modified. 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’. 28 The NBBO at the moment the order was modified. 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’. 29 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. 30 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 31 The Time in Force for the order. 32 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. Required if changed. An Order Adjusted event must be used when the display price or quantity changes as the result of a Display ATS matching engine action and not from a customer/client instruction. The Order Adjusted event may be used by non-ATS firms instead of an Order Modified event to report changes to the price or quantity of an order. The following rules apply: * If any of the price fields change, then all price fields (i.e., price, displayPrice, and workingPrice) must be reported to represent current state of the order relative to price. The quantity fields are not required. * If any of the quantity fields change, then all quantity fields (i.e., quantity, minQty, leavesQty, displayQty) must be reported to represent the current state of the order relative to quantity. The price fields are not required. Any modification that cannot be fully represented in this Reportable Event must be reported via the Order Modified event. This includes modifications received from another Industry Member where a routedOrderID is required, and modifications to the orderType. Industry Members may assign a new Order Key to Order Adjusted events. If a unique orderID is assigned, the priorOrderID must be populated with the orderID of the order that is being adjusted, and the priorOrderKeyDate must be populated. If the order has been adjusted more than once, the priorOrderID must refer to orderID of the immediately preceding adjustment which will not be the original Order ID. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Prior Order Key: priorOrderKeyDate, CATReporterIMID, symbol, priorOrderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOC 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the order event which is being cancelled. 7 The orderID of the order event which is being cancelled. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 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. 11 Must be marked as ‘true’ if the order is cancelled manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The quantity being cancelled. 14 The number of shares of the order left open after the cancel event. The full cancel will result in zero in this field. 15 Indicates who initiated the order cancellation. 16 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 17 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. 18 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. 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOCR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The orderKeyDate of the order event for which the cancellation was requested. 7 The orderID of the order event for which the cancellation was requested. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time of receipt of the cancel request. 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. 11 Must be marked as ‘true’ if the cancellation is requested manually. 12 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 13 The quantity requested to be cancelled. May populate a zero value to indicate that the cancel was for the full remaining quantity. 14 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 15 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. The Order Cancel Request event is required when a request is received to cancel an order if the request is not captured in the requestTimestamp field of the Order Cancelled event. Industry Members are not required to report an Order Cancel Request event 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. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MENQ 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the quoteID was assigned. 7 The internal quote ID assigned to the quote by the Industry Member. Must be unique within quoteKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 Field position is retired and must remain blank. 10 Field position is retired and must remain blank. 11 The date/time the quote was originated by the Industry Member. If manualFlag is ‘true’, must be reported to seconds or a finer increment up to nanoseconds. If manualFlag is ‘false’, must be reported to milliseconds or a finer increment up to nanoseconds. 12 The sequence number assigned to the quote by the reporter. Any alphanumeric not containing a delimiter. Required if two MENQs are submitted by an Industry Member using the onlyOneQuoteFlag method to modify a quote, and both MENQ events have the same timestamp. 13 Field position is retired and must remain blank. 14 Field position is retired and must remain blank. 15 Field position is retired and must remain blank. 16 Value is ‘true’ if the recipient only allows one quote per symbol for this Industry Member. Otherwise, false. 17 Price being bid. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the askPrice field is blank. 18 Quantity being bid. Must be populated with a value greater than ‘0’ if the bidPrice field is populated with a value greater than ‘0’. 19 Price being asked. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the bidPrice field is blank. 20 Quantity being asked. Must be populated with a value greater than ‘0’ if the askPrice field is populated with a value greater than ‘0’. 21 Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. Required when representativeQuoteInd is null. Not required for an Industry Member generating quotes and displaying them on a Display-only Facility. (i.e., Not required when representativeQuoteInd is present.) 22 Represents the type of account that originated this quote. Must be provided when firmDesignatedID is present. Not required for an Industry Member generating quotes and displaying them on a Display-only Facility. (i.e., Not required when representativeQuoteInd is present.) 23 Indicates whether this is an unsolicited quote. 24 Field position is retired and must remain blank. 25 Field position is retired and must remain blank. 26 If this is an unpriced quote, must be populated as ‘true’. When unpricedInd is ‘true’, bid and ask fields are not required. 27 Must be marked as ‘true’ if the quote is received or captured manually. 28 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 29 Indicates if the quote represents Customer/Client orders. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. 30 The orderID of each Customer/Client order being aggregated into a quote on the ask side. See Table 40: Aggregated Orders below. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. Required when representativeQuoteInd is ‘A’ or ‘C’. Must be blank when representativeQuoteInd is ‘N’ or ‘S’. 31 The orderID of each Customer/Client order being aggregated into a quote on the bid side. See Table 40: Aggregated Orders below. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. Required when representativeQuoteInd is ‘B’ or ‘C’. Must be blank when representativeQuoteInd is ‘N’ or ‘S’. The New Quote Event is used to report the following: * Quotes originated in OTC equity securities ultimately sent to an inter-dealer quotation system operated by an Industry Member * Quotes originated in OTC Equity securities ultimately sent to a quotation venue not operated by a CAT Reporter. * Any other electronic quotes which are provided by or received in a CAT Reporter’s order/quote handling or execution systems in CAT reportable securities and are provided by an Industry Member to other market participants off a national securities exchanges, as described in CAT FAQ B45. For two-sided quote events, the bidPrice, bidQty, askPrice, and askQty fields must be populated. For one-sided quote events, the price and quantity of the applicable side must be populated. For quotes representing a name only quote for which a price and quantity is not applicable, the price and quantity of the applicable side must be blank or must be populated with zero, and the unpricedInd must be populated as ‘true’. If the field onlyOneQuoteFlag is populated as ‘true’, any New Quote event offered by the same CATReporterIMID to the same destination in the same symbol will be considered cancelled and replaced by CAT. Modifications reflected using the onlyOneQuoteFlag method may maintain the same quote ID. However, if a quote is cancelled and a new quote is reported to CAT, the New Quote Event must not maintain the same quote ID as the quote that was cancelled. Modifications to a quote when the onlyOneQuoteFlag is populated as ‘true’ must not be captured using the Quote Modified event. Quotes entered directly into an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be originated manually, and the manualFlag must be populated as ‘true’. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MENQS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the quoteID was assigned. 7 The internal quote ID assigned to the quote by the Industry Member. Must be unique within quoteKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time the quote was originated by the Industry Member. 10 Indicates if the quote represents Customer/Client orders. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. ‘S’ or ‘N’ are not valid values for this event. 11 The orderID of each Customer/Client order being aggregated into a quote on the ask side. See Table 40: Aggregated Orders on page 111. Required when representativeQuoteInd is ‘A’ or ‘C’. 12 The orderID of each Customer/Client order being aggregated into a quote on the bid side. See Table 40: Aggregated Orders on page 111. Required when representativeQuoteInd is ‘B’ or ‘C’. The New Quote Supplement event is a supplement to the New Quote event. One New Quote event can have multiple New Quote Supplement events. Multiple New Quote Supplement events are considered as additions, not replacements or modifications. This event accommodates reporting in scenarios when the number of Aggregated Orders included in the askAggregatedOrders or bidAggregatedOrders fields cause the New Quote event to exceed the maximum allowed message length, or when the orders being represented are not captured in the New Quote event. The askAggregatedOrders and bidAggregatedOrders fields in the New Quote Supplement event must contain the additional Aggregated Orders that were not captured in the original New Quote event, or another Supplement event for the same quote. This event is applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MERQ 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the quoteID was assigned. 7 The internal quote ID assigned to the quote by the Industry Member. Must be unique within quoteKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time the quote was sent by the Industry Member. 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. 10 The sequence number assigned to the quote by the reporter. Any alphanumeric not containing a delimiter. Required if two MERQs are submitted by an Industry Member using the onlyOneQuoteFlag method to route a modified quote, and both MERQ events have the same timestamp. 11 The IMID of the Industry Member that is sending the quote, as known by the destination. This value must match the senderIMID on the Quote Received event reported by the destination. 12 When destinationType is ‘F’, this field contains the SRO-assigned identifier of the destination Industry Member. This value must match the receiverIMID field on the Quote Received event reported by the destination. When destinationType is ‘D’, this field contains the identifier of the Display-only Facility. 13 The quote ID sent to the recipient of the quote. Required when manualFlag is ‘false’. Not required when manualFlag is ‘true’. When dupROIDCond is ‘false’, must be unique per combination of Event Date, symbol, destination, and senderIMID. 14 Price being bid. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the askPrice field is blank. 15 Quantity being bid. Must be populated with a value greater than ‘0’ if the bidPrice field is populated with a value greater than ‘0’. 16 Price being asked. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the bidPrice field is blank. 17 Quantity being asked. Must be populated with a value greater than ‘0’ if the askPrice field is populated with a value greater than ‘0’. 18 If the result of the quote is rejected or no response was received, value should be ‘true’. 19 If this is an unpriced quote, must be populated as ‘true’. When unpricedInd is ‘true’, bid and ask fields are not required. 20 Indicates when a Routed Quote event maintains the original routedQuoteID. 21 Must be marked as ‘true’ if the quote is sent manually. 22 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 23 Indicates whether the destination of the route is an Industry Member or a Display-only Facility. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. 24 The session ID used when routing the quote. Must equal the session in the quote received event reported by the Display-only Facility. Applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. Required when destinationType is ‘D’. The Routed Quote Event is used to report the following: * Quotes in OTC equity securities sent to an inter-dealer quotation system operated by an Industry Member * Quotes in OTC Equity securities sent to a quotation venue not operated by a CAT Reporter. * Any other route of electronic quotes which are provided by or received in a CAT Reporter’s order/quote handling or execution systems in CAT reportable securities and are provided by an Industry Member to other market participants off a national securities exchanges, as described in [CAT FAQ B45](https://catnmsplan.com/faq%23B45. For two-sided quote events, the bidPrice, bidQty, askPrice, and askQty fields must be populated. For one-sided quote events, the price and quantity of the applicable side must be populated. For quotes representing a name only quote for which a price and quantity is not applicable, the price and quantity of the applicable side must be blank or must be populated with zero, and the unpricedInd must be populated as ‘true’. Quotes entered directly into an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be routed manually, and the manualFlag must be populated as ‘true’. The routedQuoteID field is not required for manual routes. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID * Quote Route Key: Event Date, senderIMID, destination, symbol, routedQuoteID, session 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MERQS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The quoteKeyDate of the related Routed Quote event this event is supplementing. 7 The quoteID of the related Routed Quote event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time of the related Route Quote event this event supplements (including scenarios in which the supplement is created at a later time). 10 The IMID of the Industry Member that is sending the quote, as known by the destination. This value must match the senderIMID on the Quote Received event reported by the destination. 11 When destinationType is ‘F’, this field contains the SRO-assigned identifier of the destination Industry Member. This value must be a valid IMID and must match the receiverIMID field on the Quote Received event reported by the destination. When destinationType is ‘D’, this field contains the identifier of the Display-only Facility. This value must be a valid Display-only Facility value and must equal the receiverIMID field on the quote received event reported by the Display-only Facility. 12 The quote ID sent to the recipient of the quote. Must match the routedQuoteID of the Routed Quote event that this event supplements. 13 If the result of the quote is rejected or no response was received, value should be ‘true’. 14 Indicates whether the destination of the route is an Industry Member or a Display-only Facility. 15 The session ID used when routing the quote. Must equal the session in the quote received event reported by the Display-only Facility. Required when destinationType is ‘D’. The Routed Quote Supplement Event is a supplement to the Routed Quote event. Routed Quote Supplement events are considered as additions to a Routed Quote event, not replacements or modifications. This event accommodates reporting in scenarios where a quote route is rejected by the venue to which it was routed, and the Industry Member chooses to report the quoteRejectedFlag in this separate Routed Quote Supplement event. This event is applicable for an Industry Member generating quotes and displaying them on a Display-only Facility. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEQR 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the quoteID was assigned. 7 The internal quote ID assigned to the quote by Industry Member. Must be unique within quoteKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The quote ID as received by the Industry Member inter-dealer quotation system, must match the routedQuoteID in the Routed Quote event created by the issuer of the quote. Required when manualFlag is ‘false’. Not required when manualFlag is ‘true’. When dupROIDCond is ‘false’, must be unique per combination of Event Date, symbol, destination, and senderIMID. 10 The date/time the quote was received by the Industry Member inter-dealer quotation system. 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. 11 The sequence number assigned to the quote received message by the reporter. Any alphanumeric not containing a delimiter. 12 The IMID of the Industry Member receiving the quote (the Industry Member reporting this Reportable Event). It must match the destination field on the New Quote event reported by the routing entity. 13 The IMID of the Industry Member providing the quote. This value must match the senderIMID in the New Quote event reported by the routing Industry Member. 14 ‘true’ if the Industry Member only allows one quote per symbol for the issue of the quote; false otherwise. 15 Field position is retired and must remain blank. 16 Field position is retired and must remain blank. 17 Price being bid. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the askPrice field is blank. 18 Quantity being bid. Must be populated with a value greater than ‘0’ if the bidPrice field is populated with a value greater than ‘0’. 19 Price being asked. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the bidPrice field is blank. 20 Quantity being asked. Must be populated with a value greater than ‘0’ if the askPrice field is populated with a value greater than ‘0’. 21 Field position is retired and must remain blank. 22 Indicates whether this is an unsolicited quote. 23 Indicates if the quote message received by an IDQS is a request for a bid or an ask. This field is only applicable to IDQSs. When quoteWantedInd is populated, bid and ask fields are not required. 24 If this is an unpriced quote, must be populated as ‘true’. When unpricedInd is ‘true’, bid and ask fields are not required. 25 Indicates when a Quote Received event maintains the original routedQuoteID. 26 Must be marked as ‘true’ if the quote is received or captured manually. 27 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. The Quote Received event is used to report Quotes in OTC Equity securities received by an Industry Member inter-dealer quotation system. For two-sided quote events, the bidPrice, bidQty, askPrice, and askQty fields must be populated. For one-sided quote events, the price and quantity of the applicable side must be populated. For quotes representing a name only quote for which a price and quantity is not applicable, the price and quantity of the applicable side must be blank or must be populated with zero, and the unpricedInd must be populated as ‘true’. If the field onlyOneQuoteFlag is populated as ‘true’, any Quote Received event offered by the same CATReporterIMID from the same senderIMID in the same symbol will be considered cancelled and replaced by CAT. Modifications reflected using the onlyOneQuoteFlag method may maintain the same quote ID. However, if a quote is cancelled and a new quote is reported to CAT, the Quote Received Event must not maintain the same quote ID as the quote that was cancelled. Modifications to a quote when the onlyOneQuoteFlag is populated as ‘true’ may alternatively be captured using the Quote Modified event. Quotes entered directly into an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be received manually, and the manualFlag must be populated as ‘true’. The routedQuoteID field is not required for manual routes. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID * Quote Route Key: Event Date, senderIMID, receiverIMID, symbol, receivedQuoteID * IDQS Linkage Key: quoteKeyDate, senderIMID, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEQC 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The quoteKeyDate of the Quote event which is being cancelled. 7 The quoteID of the Quote event which is being cancelled. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time the quote was cancelled. 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. 11 The sequence number of the quote cancel message. Any alphanumeric not containing a delimiter. Required for inter-dealer quotation systems only. 12 Field is Reserved for Future Use and must remain blank. 13 Indicates who initiated the order cancellation. 14 Field position is retired and must remain blank. 15 Must be marked as ‘true’ if the quote is cancelled manually. 16 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. Reported when a quote is cancelled. If a quote is cancelled that was sent to by an Industry Member to an Industry Member inter-dealer quotation system, then both the sender of the quote and the inter-dealer quotation system that accepted the quote must report Quote Cancelled events. Orders cancelled directly in an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be cancelled manually, and the manualFlag must be populated as ‘true’. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEQM 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the quoteID was assigned. 7 The internal quote ID assigned to the quote by the Industry Member. Must be unique within quoteKeyDate, CATReporterIMID, and symbol combination. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Quote ID has been assigned, this is the quoteKeyDate of the event being modified. 10 If a new Quote Key has been assigned, this is the orderID of the event being modified. When populated, the priorQuoteID must not be equal to the quoteID within the record. 11 The date/time the quote was modified. 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. 12 The sequence number assigned to the quote by the reporter. Any alphanumeric not containing a delimiter. Required for inter-dealer quotation systems only. 13 Price being bid. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the askPrice field is blank. 14 Quantity being bid. Must be populated with a value greater than ‘0’ if the bidPrice field is populated with a value greater than ‘0’. 15 Price being asked. When provided, must be greater than or equal to zero. When unpricedInd is ‘true’, must be blank, or populated with a value of ‘0’. When unpricedInd is ‘false’, must be populated with a value greater than 0 if the bidPrice field is blank. 16 Quantity being asked. Must be populated with a value greater than ‘0’ if the askPrice field is populated with a value greater than ‘0’. 17 Indicates whether this is an unsolicited quote. 18 If this is an unpriced quote, must be populated as ‘true’. When unpricedInd is ‘true’, bid and ask fields are not required. 19 Must be marked as ‘true’ if the quote is modified manually. 20 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. Reported when a quote is modified, and the venue supports more than one quote per symbol for an Industry Member at one time. If the field onlyOneQuoteFlag field on the related New Quote or Quote Received event is populated as ‘true’, the Quote Modified event must not be used. If a modification to a quote results in the generation of a new quoteID with a new Quote Key which replaces the prior quoteID, the quoteID field must capture the newly assigned quoteID, and the prior quote fields must reflect the quote that is being modified. If the quote has been modified more than once with a new quoteID assigned with each modification, the priorQuoteID must refer to quoteID of the immediately preceding modification which will not be the original Quote ID. If the quoteID remains the same during the modification, the priorQuoteID must remain blank. Orders modified directly in an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be modified manually, and the manualFlag must be populated as ‘true’. Linkage Keys for this Reportable Event * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID * Prior Quote Key: priorQuoteKeyDate, CATReporterIMID, symbol, priorQuoteID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEQS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The quoteKeyDate of the Quote event which is being updated. 7 The quoteID of the Quote event which is being updated. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 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. 10 The date/time the quote status was updated. 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. 11 The sequence number of the quote cancel message. Any alphanumeric not containing a delimiter. Required for inter-dealer quotation systems only. 12 Market Participant Status Code, indicates if the market maker's quote is open or closed. 13 Must be marked as ‘true’ if the quote is modified manually. 14 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. Reported when the status of a quote is changed to be opened or closed. If a quote that was sent by an Industry Member to an Industry Member inter-dealer quotation system is opened or closed by the Industry Member that sent the quote, then both the sender of the quote and the inter-dealer quotation system that accepted the quote must report Quote Status events. If the status of a quote that was sent by an Industry Member to an Industry Member inter-dealer quotation system is changed as a result of an automatic process, then a Quote Status event is only required to be reported by the inter-dealer quotation system. Refer to [CAT FAQ J5](https://www.catnmsplan.com/faq%23J5) for additional information. Orders updated directly in an inter-dealer quotation system’s platform that are not sent to the inter-dealer quotation system electronically (e.g., via FIX) are considered to be updated manually, and the manualFlag must be populated as ‘true’. Linkage Keys for this Reportable Event: * Quote Key: quoteKeyDate, CATReporterIMID, symbol, quoteID 1 Indicates whether the event is a new event, firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOT 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the tradeID was assigned. 7 Unique ID assigned to this execution by the Industry Member. This ID will be used in subsequent events when a specific trade needs to be identified. The combination of date, CATReporterIMID, symbol, and tradeID must be unique. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time at which the trade was executed. 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. 10 Must be marked as ‘true’ if this is a manual execution. 11 The time at which the event is systematized. 12 Must be marked as ‘true’ if the execution is cancelled and was not reported to the TRF/ADF/ORF. 13 When cancelFlag is ‘true’, the time at which the execution was cancelled. 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. 14 Field position is retired and must remain blank. 15 Field position is retired and must remain blank. 16 Quantity of the trade. 17 The execution price of the trade. Must be greater than or equal to zero. 18 The capacity in which the Industry Member acted. 19 The unique identifier reported by the Industry Member to the TRF/ADF/ORF based on the reporting specifications of the specific facility, required when the ID was supplied to a transaction reporting system: Compliance ID in ORF and ADF Branch Sequence Number in FINRA/NQ TRF FINRA Compliance Number in FINRA/NYSE TRF Must be unique per combination of Event Date, CATReporterIMID, marketCenterID and symbol. The tapeTradeID may link to either the reporting side or the contra-side of the media tape report. When the reportingExceptionCode field is blank, the tapeTradeID field must be populated. When the reportingExceptionCode field is populated, the tapeTradeID field must be blank. 20 The national securities exchange or transaction reporting system operated by FINRA where the trade was reported. When the marketCenterID field is blank, the reportingExceptionCode must be populated with a value other than ‘C’. When the marketCenterID field is populated, the reportingExceptionCode field must be blank, or must be populated with a value of ‘C’. 21 Identifies if a Trade event is one sided, and which side of the trade the Industry Member is populating in the Trade Side Details. When sideDetailsInd is ‘BUY’, only the buyDetails are populated. When sideDetailsInd is ‘SELL’, only the sellDetails are populated. 22 table49 See Table 49: Trade Side Details below. Applicable if there is only one orderID associated with this side of the trade. If there is more than one orderID, must be populated in separate MEOTS events. 23 table49 See Table 49: Trade Side Details below. Applicable if there is only one orderID associated with this side of the trade. If there is more than one orderID, must be populated in separate MEOTS events. 24 Indicates the reason that a unique identifier (e.g., Branch Sequence Number, Compliance ID) was not supplied to a transaction reporting system. Must be provided if the execution is not reported to a FINRA transaction reporting system. When the tapeTradeID field is blank, the reportingExceptionCode field must be populated. When the tapeTradeID field is populated, the reportingExceptionCode field must be blank. When the marketCenterID field is blank, the reportingExceptionCode field must be populated. When the marketCenterID field is populated, the reportingExceptionCode must be blank. 25 The sequence number assigned to the Reportable Event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 26 The NBBO at the moment the trade occurred. 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 value of ‘0’. 27 The NBBO at the moment the trade occurred. 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 value of ‘0’. 28 The NBBO at the moment the trade occurred. 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 value of ‘0’. 29 The NBBO at the moment the trade occurred. 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 value of ‘0’. 30 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. 31 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 32 Field position is retired and must remain blank. 33 The clearing number of the Industry Member’s clearing firm. Required when the reportingExceptionCode is ‘C’. 34 The counterparty to the trade. Required when the reportingExceptionCode is ‘C’. 35 Indicates when the execution is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. 36 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. A Trade Event is used when the Industry Member acts as the executing broker and is required to report the trade for public dissemination purposes. When an Industry Member is not required to report the execution of a customer/client order for public dissemination purposes, with the exceptions noted below, an Order Fulfillment event must be used. See Section Order Fulfillment for more details. **Reporting Exception Codes** In general, Trade events are required to match to a TRF/ORF/ADF report. However, there are four circumstances when an MEOT would not be able to be linked to a TRF report and a Reporting Exception Code (REC) is required on a Trade event to allow the Processor to identify that there will be no link to a TRF/ORF/ADF report: * An Industry Member executes a trade between two desks or departments of the same firm, but because there is no change in beneficial ownership, no trade is reported for public dissemination. In this instance a REC of “P” should be used on the Trade event. * An Industry Member executes a trade and must report the trade via Form T. In this instance, a REC of “F” should be used on the Trade event. * A trade was executed by a non-FINRA member firm and was reported to the TRF by the FINRA member counterparty. In this instance, the non-FINRA member must populate a REC of “N” on the Trade event. * Industry Member was the contra side of the trade report which was reported to a TRF/ORF/ADF via a QSR or AGU, and was therefore unable to populate a tapeTradeID. In this instance, a REC of ‘C’ should be used on the Trade event to reflect a linkage to the related TRF/ORF/ADF report could not be made. The following rules apply when REC ‘C’ is used: * The marketCenterID field must be populated. * The clearingFirm and counterparty fields must be populated. * The cancelFlag and cancelTimestamp must be populated accordingly for all trades that are reported to a TRF via a QSR or AGU and later cancelled, as the CAT would not be able to link to a related TRF cancellation. FINRA CAT will closely monitor all uses of REC ‘C’ to ensure compliance with the above noted guidelines. **Trade Side Details** Trade events are two-sided, containing information on both sides of the trade. Exceptions requiring only one side of the Trade event to be populated are noted below. The details of each side are reported using Trade Side Details. The data type Trade Side Details is described as a list of fields in Table 49 below. Trade Side Details must contain only one orderID per side. The buyDetails must contain the orderID of the buy side of the trade and the sellDetails must contain the orderID of the sell side of the trade. If there is more than one orderID associated with one side of the trade, the Trade Side Details related to each orderID must be populated in a separate Trade Supplement event. **Internalized Trade** When an Industry Member internalizes an order by filling it from a proprietary account, the Industry Member must report the orderID on the customer/client side and the FDID and the accountHolderType of the proprietary account on the firm side. In this scenario, no orderID is required on the firm side of the Trade event. However, if the Industry Member generates a proprietary order to facilitate the execution of the customer/client order, the Industry Member must report the orderID of both the customer/client side and the firm side of the Trade event. Refer to CAT FAQ B41 for additional information. **One-Sided Trade events** There are several exceptions which only require one side of a Trade event to be populated. These exceptions include: * Trade is executed as the result of a negotiation between two Industry Members. * Order is routed by a FINRA Member to a non-FINRA member, and the FINRA Member has the obligation to submit a media trade report to a TRF/ADF/ORF. * Order is routed by an Industry Member to a foreign broker-dealer, and the foreign broker-dealer executes the order at a net price, creating a media trade reporting obligation in the United States. In these scenarios, each party that is required to report a Trade event to CAT must populate the sideDetailsInd indicating which side of the trade the Industry Member was associated with, and which Trade Side Details will be populated in the Trade event. **Cancelled Trades** In accordance with CAT FAQ E25, the cancelFlag must be set to true only in instances when a trade is cancelled because the trade report is rejected by the TRF/ORF or ADF. For all instances where a trade is reported to, and accepted by, the TRF/ORF or ADF, including those that are cancelled or busted in the trade reporting data, the cancelFlag must be set to false. Refer to CAT FAQ E29 and CAT FAQ E30 for additional information. Linkage Keys for this Reportable Event: * Order Key: buyDetails.orderKeyDate, CATReporterIMID, symbol, buyDetails.orderID * Order Key: sellDetails.orderKeyDate, CATReporterIMID, symbol, sellDetails.orderID * Trade Key: tradeKeyDate, CATReporterIMID, symbol, tradeID * TRF Linkage Key: Event Date, CATReporterIMID, symbol, tapeTradeID, marketCenterID * Exchange Trade Linkage Key: Event Date, symbol, tapeTradeID, marketCenterID, side 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOTS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The tradeKeyDate of the Trade event which this event is supplementing. 7 The tradeID of the Trade event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time at which the trade was executed. This must match the eventTimestamp value reported on the Trade this event supplements (including scenarios in which the supplement is created at a later time). 10 table51 Required if the subject order was a buy order. See Table 51: Trade Side Details below. 11 table51 Required if the subject order was a sell order. See Table 51: Trade Side Details below. 12 Indicates when the execution is related to a multi-leg order event. Refer to Section 5.2 for additional guidance. The tables below describe the data elements used to report when there is more than one order associated with one side of the trade. Linkage Keys for this Reportable Event: * Order Key: buyDetails.orderKeyDate, CATReporterIMID, symbol, buyDetails.orderID * Order Key: sellDetails.orderKeyDate, CATReporterIMID, symbol, sellDetails.orderID * Trade Key: tradeKeyDate, CATReporterIMID, symbol, tradeID 1 Indicates whether the event is a new event, firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOF 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The date and time the fulfillmentID was assigned. 7 The unique identifier for the fulfillment. The combination of reporter, fillKeyDate, symbol and fulfillmentID must be unique. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time when the fulfillment was processed by the Industry Member. 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. 10 Must be marked as ‘true’ if this is a manual process. 11 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 12 Refer to Appendix C for representative order linkage requirements. 13 Must be marked as ‘true’ if the fulfillment was cancelled. 14 When cancelFlag is ‘true’, the time at which the fulfillment was cancelled. 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. 15 Quantity being executed and assigned. It may or may not be the full quantity of the order. 16 Price of the executed shares. Must be greater than or equal to zero. 17 The capacity in which the Industry Member acted. 18 table53 See Table 53: Fulfillment Side Details below. 19 table53 Used to capture the Industry Member side order details. Applicable if there is only one orderID associated with this side of the fulfillment. If more than one representative order was used to fill the customer/client order, this field must be blank and the firmDetails for each related representative order must be populated in separate MEOFS events. If firmDetails are captured in an MEOFS event, the fulfillmentLinkType field must be populated with a value of ‘YS’. See Table 53: Fulfillment Side Details below. Refer to Appendix C for more details. 20 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. The Order Fulfillment event is used to report the execution of a customer/client order that is not required to be reported for public dissemination purposes. Order Fulfillment events are required in scenarios where: * A representative order was used to facilitate the execution of the customer/client order. * An order is routed to a foreign market and the resulting foreign execution is not captured by CAT. The Order Fulfillment event is designed to capture the customer/client details and the firm side details. Firm side details provide linkage to the representative order used to facilitate the execution of the customer/client order. The fulfillmentLinkType field is used to indicate if the firm side details are required. 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. Linkage Keys for this Reportable Event: * Order Key: firmDetails.orderKeyDate, CATReporterIMID, symbol, firmDetails.orderID * Order Key: clientDetails.orderKeyDate, CATReporterIMID, symbol, clientDetails.orderID * Fulfillment Key: fillKeyDate, CATReporterIMID, symbol, fulfillmentID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOFS 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 The fillKeyDate of the Order Fulfillment event which this event is supplementing. 7 The fulfillmentID of the Order Fulfillment event which this event is supplementing. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time at which the fulfillment was processed by the Industry Member. This must match the eventTimestamp value reported on the Order Fulfillment this event supplements (including scenarios in which the supplement is created at a later time). 10 table55 Used to capture the Industry Member side order details. See Table 55: Fulfillment Side Details below. Refer to Appendix C for more details. The tables below describe the data elements used to report a customer/client order filled from multiple representative orders. Only one orderID may be represented in each Order Fulfillment Supplement event. If multiple representative orders were used to fill a customer/client order, the orderID for each representative order must be populated in its own Order Fulfillment Supplement event. Linkage Keys for this Reportable Event: * Order Key: firmDetails.orderKeyDate, CATReporterIMID, symbol, firmDetails.orderID * Fulfillment Key: fillKeyDate, CATReporterIMID, symbol, fulfillmentID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. 4 MEFA 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Fulfillment Key is assigned, the date and time the fulfillmentID was assigned. When a new Fulfillment Key is not assigned, the fillKeyDate of the fulfillment event being modified. 7 When a new Fulfillment Key is assigned, the internal fulfillment ID assigned to the fulfillment event by the Industry Member. Must be unique within fillKeyDate, CATReporterIMID, and symbol combination. When a new Fulfillment Key is not assigned, the fulfillmentID of the fulfillment event being modified. 8 In cases when a new fulfillmentID is assigned, the priorFillKeyDate is the fillKeyDate of the fulfilment that is being modified. Required if priorFulfillmentID is populated. 9 If a new fulfillment ID is assigned, this is the fulfillmentID of the event being modified. 10 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 11 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. 12 The date/time when the fulfillment was processed by the Industry Member. 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. 13 Must be marked as ‘true’ if this is a manual process. 14 The time at which the event is systematized. Required when manualFlag is ‘true’ and the event is systematized. 15 Quantity being executed and assigned. It may or may not be the full quantity of the order. 16 The capacity in which the Industry Member acted. 17 Price of the executed shares. Must be greater than or equal to zero. 18 Refer to Appendix C for representative order linkage requirements. 19 table53 Refer to Fulfillment Side Details in Table 53: Fulfillment Side Details. Required if changed. 20 table53 Refer to Fulfillment Side Details in Table 53: Fulfillment Side Details. Required if changed. This CAT event is used to report the amendment of a previously reported fulfillment that occurs on the same day or on a subsequent day. An Order Fulfillment Amendment event is required to be reported to CAT if the fill to the customer/client was changed after the final fulfillment had been provided to the customer/client. This Reportable Event must capture the entire state of the fulfillment after it has been amended, even though some of the data elements may remain unchanged. However, Side Details are only required to be restated if changed. When the fulfillmentLinkType value ‘YS’ is used, Side Details must be restated using an MEOFS event if changed. Order Fulfillment Amendments are not required in scenarios where: * Executions against an order are tracked throughout the day but a single average price fill is provided to the customer/client after the order is completed or at the end of the day. Some systems may provide intraday transparency to the progress of executing an order as informal information that is not considered by the firm to be ‘final’ fulfillments, and these should not be reported to CAT as fulfillments and fulfillment amendments. Refer to [CAT FAQ B64](https://catnmsplan.com/faq%23B64) for additional information. * An Industry Member makes a correction via a debit/credit to the customer's/client’s account instead of modifying the executed shares given back to the customer/client. * Changes do not impact CAT reportable attributes of the fulfillment. Linkage Keys for this Reportable Event: * Order Key: firmDetails.orderKeyDate, CATReporterIMID, symbol, firmDetails.orderID * Order Key: clientDetails.orderKeyDate, CATReporterIMID, symbol, clientDetails.orderID * Fulfillment Key: fillKeyDate, CATReporterIMID, symbol, fulfillmentID * Prior Fulfillment Key: priorFillKeyDate, CATReporterIMID, symbol, priorFulfillmentID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’ 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEPA 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. 6 The date and time the allocationID was assigned. 7 The internal allocation ID assigned to the allocation event by the Industry Member. The combination of CATReporterIMID, allocationKeyDate, symbol and allocationID must be unique. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 The date/time the shares allocated are booked into the customer’s/client’s account. Timestamp must be reported to seconds or a finer increment up to nanoseconds. 10 Must be marked as ‘true’ if the allocation was cancelled. 11 When cancelFlag is ‘true’, the time at which the allocation was cancelled. 12 Quantity being allocated. 13 Price of the allocated shares. Must be greater than or equal to zero. 14 The side of customer/client receiving the allocation. 15 The FDID of the account receiving the allocation, including subaccounts. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. 16 Field position is retired and must remain blank. 17 Indicates if the account meets the definition of institution under FINRA Rule 4512(c). 18 The trade date of the securities being allocated. Used to validate the symbol field on this event. 19 The settlement date of the securities being allocated. Not required for when-issued securities. 20 Indicates the type of allocation being made (e.g., custody, DVP, step out, correspondent flip). 21 Required when allocationType is ‘DVP’ or ‘DVPF’. If the custodian is a US broker-dealer, this field must be populated with the clearing number of the custodian. If the custodian is a bank and is not a registered broker-dealer, this field must be populated with the DTC number of the bank. If there is no clearing number or DTC number, this field must be populated with a value of ‘FOREIGN’. Refer to CAT FAQ U19 for additional guidance. 22 The CRD number of the related Introducing Broker or Correspondent firm, if applicable. 23 The FDID of the related New Order event, if available in the booking system. Requirements for populating this field may be expanded in future phases of CAT. 24 The date/time the time the allocation instruction was received. 25 Field position is retired and must remain blank. 26 Represents the type of beneficial owner of the account to which the shares were allocated. Industry Members that perform allocations are required to submit a Post-Trade Allocation event to CAT any time shares are allocated to a customer account regardless of whether the Industry Member was involved in executing the underlying order(s). Refer to Section 3.3 for additional information on the requirements for reporting allocation events to CAT. Linkage Keys for this Reportable Event: * Allocation Key: allocationKeyDate, CATReporterIMID, symbol, allocationID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’ 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEAA 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. 6 When a new Allocation Key is assigned, the date and time the allocationID was assigned. When a new Allocation Key is not assigned, the allocationKeyDate of the allocation event being modified. 7 When a new Allocation Key is assigned, the internal allocation ID assigned to the allocation event by the Industry Member. Must be unique within allocationKeyDate, CATReporterIMID, and symbol combination. When a new Allocation Key is not assigned, the allocationID of the allocation event being modified. 8 In cases when a new allocationID is assigned, the priorAllocationKeyDate is the allocationKeyDate of the allocation event that is being modified. Required if priorAllocationID is populated. 9 If a new allocation ID is assigned, this is the allocationID of the event being modified. 10 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 11 The date/time the time the allocation amendment was processed. Timestamp must be reported to seconds or a finer increment up to nanoseconds. 12 Quantity being allocated. 13 Price of the allocated shares. Must be greater than or equal to zero. 14 The side of customer receiving the allocation. 15 The FDID of the account receiving the allocation, including subaccounts. Refer to Appendix G: Data Dictionary for definition and guidance for populating this field. 16 Field position is retired and must remain blank. 17 Indicates if the account meets the definition of institution under FINRA Rule 4512(c). 18 The trade date of the securities being allocated. Used to validate the symbol field on this event. 19 The settlement date of the securities being allocated. Not required for when-issued securities. 20 Indicates the type of allocation being made (e.g., custody, DVP, step out, correspondent flip). 21 Required when allocationType is ‘DVP’ or ‘DVPF’. If the custodian is a US broker-dealer, this field must be populated with the clearing number of the custodian. If the custodian is a bank and is not a registered broker-dealer, this field must be populated with the DTC number of the bank. If there is no clearing number or DTC number, this field must be populated with a value of ‘FOREIGN’. Refer to CAT FAQ U19 for additional guidance. 22 The CRD number of the related Introducing Broker or Correspondent firm, if applicable. 23 The FDID of the related New Order event, if available in the booking system. Requirements for populating this field may be expanded in future phases of CAT. 24 The date/time the time the allocation amendment instruction was received. 25 Must be marked as ‘true’ if the allocation was cancelled. 26 When cancelFlag is ‘true’, the time at which the allocation was cancelled. 27 Field position is retired and must remain blank. 28 Represents the type of beneficial owner of the account to which the shares were allocated. An Amended Allocation event is used to report to CAT when an allocation is updated such that a CAT reportable attribute is changed after the shares/contracts were originally booked in a customer account, and must always reflect the current state of the allocation. This Reportable Event must capture the entire state of the allocation after it has been amended, even though some of the data elements may remain unchanged. Changes to CAT reportable attributes of an allocation after the original booking of shares/contracts are required to be reported to CAT as either an Allocation Amendment event or the cancellation of a Post-Trade Allocation event followed by a new Post-Trade Allocation event regardless if they occur pre-settlement or post-settlement. Since changes to an allocation may occur any time after the original booking, the Amended Allocation event is due at 8AM on the next CAT Trading Day after the change was booked, even if it is on a different day than the original Allocation event. Refer to [CAT FAQ U14](https://catnmsplan.com/faq%23U14) for additional information. Amended Allocation events must not be reported to CAT in scenarios where: • An Industry Member makes a correction via a debit/credit to the customer's/client’s account instead of modifying the allocation given to the customer/client. • Changes do not impact CAT reportable attributes of the allocation. Any changes to the FDID that the shares/contracts were originally booked to may be reported as either an Amended Allocation event or the cancellation of a Post-Trade Allocation event followed by a new Post-Trade Allocation event regardless if they occur pre-settlement or post-settlement. Amended Allocation events must not be used to correct ingestion errors on a previously submitted MEPA/MEAA event. Linkage Keys for this Reportable Event: * Allocation Key: allocationKeyDate, CATReporterIMID, symbol, allocationID * Prior Allocation Key: priorAllocationKeyDate, CATReporterIMID, symbol, priorAllocationID 1 Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. 2 Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. 3 An identifier assigned to the record by the reporting firm. Formatted as <Event Date>_<firm ROE Identifier> Must be unique for the Event Date and CAT Reporter IMID. 4 MEOE 5 The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. 6 When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of the CAT event which is being modified. 7 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 Order Modified (Cancel/Replace) event which is being modified. 8 The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. 9 If a new Order Key has been assigned, this is the orderKeyDate of the event being modified. 10 If a new Order Key has been assigned, this is the orderID of the event being modified. When populated, the priorOrderID must not be equal to the orderID within the record. 11 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. 12 The date/time the order or underlying condition became effective. 13 The Time in Force for the order (e.g., DAY, IOC, GTC). 14 The trading session(s) during which an order is eligible to trade. 15 Field is Reserved for Future Use and must remain blank. 16 The side of the order. For this Reportable Event, only same-side adjustments are allowed (e.g., sell long to short sell). Required if the field changed when the order or underlying condition became effective. 17 The limit price of the order. When provided, must be greater than or equal to zero. Required if the field changed when the order became effective. 18 The order quantity. Required if the field changed when the order or underlying condition became effective. 19 The minimum quantity of an order to be executed. Required if the field changed when the order or underlying condition became effective. Must be > 0. 20 The type of order being submitted (e.g., market, limit). Required if the field changed when the order became effective. 21 The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. 22 Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. 23 The displayed price of the order. When provided, must be greater than or equal to zero. Required when applicable and the field changed when the order or underlying condition became effective. 24 The working price of the order. When provided, must be greater than or equal to zero. Required when applicable and the field changed when the order or underlying condition became effective. 25 The displayed quantity for this order. Required when applicable and the field changed when the order or underlying condition became effective. 26 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’. 27 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’. 28 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’. 29 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’. 30 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. 31 The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. 32 The price at which the order became effective. Required in scenarios where the trigger price was not explicitly captured in the handlingInstructions field on the related new order (e.g., Stop Formula, Trailing Stop) 33 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. The Order Effective event is used to indicate that an order, or an underlying condition of an order, has become effective. This event is applicable to orders such as conditional (Refer to [FAQ D26](https://catnmsplan.com/faq%23D26)), Stop, Stop Limit, Trailing Stop, Trailing Stop Limit, Stop on Quote, and Stop Limit on Quote orders. This event is NOT applicable to Stop Stock transactions. The Order Effective event must be reported by the party that was holding the order at the time the order or condition became effective. If the triggering event causing the order to become effective was a specific price, such as a stop price, the triggerPrice field must be populated in scenarios where the trigger price was not explicitly captured in the handlingInstructions field on the related new order (e.g., Stop Formula, Trailing Stop). In scenarios where the stop price was captured in prior CAT events associated with the order (e.g., as a name/value pair in handlingInstructions on MENO and/or MEOA events), then the information may be optionally restated in the triggerPrice field on the Order Effective event; however, it is not required to be reported again. If a new order ID is generated when the order becomes effective, which replaces the prior order ID, the orderID field must capture the new order ID, and the priorOrderID field must reflect the order ID that is being replaced. If the orderID remains the same when the order becomes effective, the priorOrderID and priorOrderKeyDate must remain blank. Linkage Keys for this Reportable Event: * Order Key: orderKeyDate, CATReporterIMID, symbol, orderID * Prior Order Key: priorOrderKeyDate, CATReporterIMID, symbol, priorOrderID