Quick Answer
CAT covers National Market System (NMS) securities, including listed options, and eligible over-the-counter (OTC) equities. Initial reports are due 8 a.m. ET on the CAT trading day after recording or receipt, as applicable. Corrections are due 8 a.m. T+3 from the event's CAT trading day. Report the member's actual applicable events.
A Trade Reporting Facility (TRF), the Alternative Display Facility (ADF), the Over-the-Counter Reporting Facility (ORF) and the Trade Reporting and Compliance Engine (TRACE) serve their respective transaction-reporting regimes. CAT captures applicable order receipt, modification, routing, execution and cancellation events in eligible securities.
The supervisor's job is to ensure the firm's systems produce this lifecycle data and submit it on time, with synchronized clocks.
Coverage and Scope
CAT captures the full lifecycle of every:
- Order (including the receipt of a customer order)
- Cancel
- Modification
- Route (to another broker-dealer or venue)
- Execution
CAT-eligible securities include NMS securities, including listed options, and OTC equity securities. Members report the applicable events they actually handle. A firm with no reportable options activity does not invent options events merely because options are covered products. Trade Reporting and Compliance Engine (TRACE) reporting of debt does not place that debt within CAT.
An Industry Member is a member of a national securities exchange or national securities association required to record and report under the CAT framework. Status does not depend on trading volume or on how much business the firm does. Its event-reporting duties depend on actual reportable activity.
Adviser registration, custody or sending an order to a broker-dealer does not itself confer qualifying membership. An advisory operation within an Industry Member broker-dealer's legal entity is subject to that broker-dealer's applicable CAT rules.
Determine the reporting party from the actual order flow. For example, an advisory operation within broker-dealer A may place an order directly in its client's account at broker-dealer B. If A has no order in that flow, B reports the new order and its subsequent reportable actions; the advisory operation's connection to A does not create an order for A to report.
Recorded Industry Member Data is due by 8:00 a.m. ET on the CAT Trading Day after recording. Received Industry Member Data is due by 8:00 a.m. ET on the CAT Trading Day after receipt. Errors must be corrected by 8:00 a.m. ET on T+3, measured from the event's CAT Trading Day. Weekends and market holidays affect the count.
For Industry Members, a CAT Trading Day begins immediately after 4:15 p.m. ET on one trade date and ends at exactly 4:15 p.m. ET on the next trade date. An execution after 4:15 p.m. on Monday belongs to Tuesday's CAT Trading Day, with an initial deadline of Wednesday at 8 a.m. ET, assuming no market holiday.
| CAT Deadline | Standard |
|---|---|
| Recorded data submission | By 8:00 a.m. ET on the CAT Trading Day after recording |
| Received data submission | By 8:00 a.m. ET on the CAT Trading Day after receipt |
| Error correction | By 8:00 a.m. ET on T+3, measured from the event's CAT Trading Day |
Think of it this way: CAT has daily reporting deadlines rather than a real-time tape deadline. For initial submission, identify whether the data is recorded or received, then use the CAT Trading Day of recording or receipt. For error correction, use the original event's CAT Trading Day. Discovery of an error does not restart the correction clock, and late corrections remain required.
Exam Tip: Gotchas
- Initial deadlines depend on recording or receipt; corrections use the event’s CAT Trading Day and a separate T+3 deadline.
- A never-submitted event is late under the initial deadline, not a correction; submit it even after that deadline.
- Coverage includes listed options and eligible OTC equities, but report only the events the member handled.
Correcting CAT Errors
Send every CAT correction to CAT itself. The Central Repository is the CAT database. It receives, consolidates and retains all information reported to CAT. The Plan Processor operates CAT for the industry, and a Financial Industry Regulatory Authority (FINRA) subsidiary is the current Plan Processor. A TRF is not a destination for a CAT correction, because a TRF serves a separate transaction-reporting regime.
An Industry Member has three ways to repair a record that CAT rejected:
- Regenerate the repaired record and send it in a new data file.
- Start from the CAT feedback file, which pre-fills the rejected records.
- Make the repair in the CAT Reporter Portal.
CAT may already have accepted a record that is wrong. The firm then sends a correction record. If the firm should never have sent the record, it sends a deletion. A customer's change to an order is a different case. Report that change as an Order Modified event, not as a correction.
Every rejection, correction and deletion has one deadline: 8:00 a.m. ET on T+3, where T is the event's CAT Trading Day. The period up to that cutoff is the T+3 error-correction window. CAT marks a later repair as late.
Exam Tip: Gotchas
- Correct CAT data in CAT; a trade-facility correction does not repair it.
- A customer’s order change is a modification, not a correction of the firm’s error.
Clock Synchronization
Before investigating clocks, distinguish a late event file from a clock-reporting violation. For a short transmission outage, record the outage in the firm's books and records and transmit as soon as possible. Opening a CAT Help Desk case is recommended; it does not cure lateness.
Assess any separate regulatory-event reporting duty on its own conditions, including applicable significance and impact standards. Do not infer a universal notice requirement to both FINRA and the Plan Processor solely from a late CAT file.
CAT depends on accurate timestamps, so industry members must synchronize business clocks used to record event timestamps:
| Clock Type | Tolerance |
|---|---|
| Business clocks recording CAT events, except the limited category below | Within 50 milliseconds of the National Institute of Standards and Technology (NIST), including transmission delay and drift |
| Clocks used solely for manual order events or solely for allocations | Within 1 second of NIST, even if the clock is computerized |
Synchronize every business day before market open, then check and resynchronize as necessary throughout the day. Document the procedures and results. A pre-open check alone does not excuse later drift. An average offset within tolerance does not establish continuous compliance. Obtain suitable evidence, such as maximum-offset monitoring; no particular statistical format is prescribed. Retain synchronization logs for at least five years.
Report clock-synchronization violations to the Plan Processor and FINRA pursuant to the Operating Committee's reporting thresholds. This is a separate duty; fulfilling it does not cure the underlying synchronization violation. Correct the clock and satisfy any applicable report requirement.
Think of it this way: Clock alignment helps reconstruct the lifecycle, but receipt and routing are different events. An order received at 10:30:00.500 may legitimately route at 10:30:00.800. That interval does not prove clock drift. Compare each clock's offset from NIST and apply the tolerance for its actual use.
Exam Tip: Gotchas
- Clock use determines whether the 50-millisecond or one-second tolerance applies.
- Synchronize before market open and resynchronize as necessary; retain clock logs five years.
CAT Definitions and Recordkeeping
| Topic | Scope |
|---|---|
| CAT definitions | Key CAT terms (Industry Member, CAT Reporter, Customer-ID, Firm Designated ID) |
| CAT member event-data recordkeeping | Three years, with the first two years easily accessible, under the applicable member record-retention provision |
Keep the member event-data period separate from the five-year clock-log requirement. Another applicable record category or preservation hold can require longer retention. The Firm Designated ID identifies a trading account or permitted relationship consistently over time; it is not simply any customer account number.
Exam Tip: Gotchas
- Member event records require three years, first two accessible; blotters require six years, first two accessible.
- Membership and actual order flow determine reporting duties; adviser registration alone does not confer membership.
- Customer-ID and Firm Designated ID are distinct CAT identifiers; misassignment affects data quality.
How CAT Connects to Other Reporting
CAT does not replace trade-facility reporting. Assess each reporting regime independently. When an execution falls within both CAT and a member's facility-reporting duties, the systems track different aspects. CAT eligibility alone does not require a member equity-facility report for a listed option or an exchange stock execution:
| Report | Purpose | Deadline |
|---|---|---|
| Applicable trade-facility report | Transaction report; public dissemination depends on the product and report | Facility-, product-, and session-specific deadline |
| CAT lifecycle reports | Order receipt, modifications, cancels, routes, fills | 8:00 a.m. ET on T+1 |
Compare corresponding execution events, their quantities, prices and applicable identifiers. Account for event mapping and timestamp precision: the public print time, report-transmission time and execution time are different measures. A receipt-to-route interval is not a same-event discrepancy. Different identifiers may be permitted for different reporting roles or fields. Verify the applicable mapping before treating an identifier difference as an error.
The 50-millisecond tolerance is a CAT clock standard. The trade-facility rules set their own time-of-execution format (hours, minutes and seconds) and a separate 10-second reporting deadline. A reporting deadline does not set clock precision.
For conflicting execution-time records, investigate each relevant clock's offset from NIST, event mapping and timestamp capture. A difference between two fields does not by itself prove a clock violation. For example, two clocks at opposite permitted 50-millisecond offsets can differ by 100 milliseconds. Correct any inaccurate data or synchronization violation found.
Exam Tip: Gotchas
- CAT and trade-facility reporting are independent when the activity falls within both; debt reporting to TRACE does not bring debt into CAT.
- Compare corresponding events and investigate mapping and precision before treating a difference as an error.
- A provider may assist, but the member retains responsibility for controls and timely resolution.
What Should You Check on Exam Day?
- Do you know the CAT submission deadline of 8:00 a.m. ET on T+1, and the separate error-correction deadline of T+3?
- Do you know where a CAT correction goes, and when a firm sends a correction record, a deletion or an Order Modified event?
- Can you distinguish the usual 50-millisecond clock tolerance from the one-second exception for clocks used solely for manual events or allocations?
- Do you know how long CAT records and synchronization logs must be retained, and how much must stay easily accessible?
- Can you distinguish CAT lifecycle reporting from trade-report facility reporting, and state why a firm compares corresponding events across both?