Rule 613 Explained: What the Consolidated Audit Trail Actually Requires

Rule 613 requires exchanges and FINRA to build a consolidated audit trail of quotes, orders and reportable events in NMS securities, reported by 8 a.m. ET the next trading day.

Rule 613 is the provision the US Securities and Exchange Commission adopted to create a comprehensive consolidated audit trail (CAT). Its stated purpose is to let regulators efficiently and accurately track activity throughout US markets in National Market System (NMS) securities. In practical terms, it is a data-reporting rule aimed at self-regulatory organizations and their members, not a rule that assigns obligations to retail account holders directly.

What Rule 613 requires

The rule does not itself build the database. It requires the self-regulatory organizations (SROs) to jointly submit a plan, called an NMS plan, to create, implement and maintain the consolidated audit trail. The rule also specifies what type of data is collected and when that data must be reported to a central repository.

On the reporting side, the NMS plan must require each national securities exchange and FINRA, along with their respective members, to send detailed information to a newly created central repository. That information covers each quote and order in an NMS security, plus each reportable event linked to a quote or order, including origination, modification, cancellation, routing and execution.

Timing and clock rules

Certain data must reach the central repository by 8 a.m. Eastern Time the following trading day and then be available to regulators for analysis. The rule also requires SROs and their members to synchronize the business clocks used to record the date and time of any reportable event, and it requires timestamps sent to the repository to be in millisecond or finer increments.

Another requirement is lifecycle linkage: all reportable events must be reported in a way that lets the repository efficiently and accurately link them to an order through its entire life cycle, from generation through routing, modification, cancellation or execution.

Identifier codes for firms and accounts

Rule 613 mandates unique and consistent codes at two levels. Each broker-dealer and national securities exchange must be assigned a code that identifies it, and that code is reported to the central repository with every reportable event. Separately, each account holder, and any person with trading discretion over an account holder's account, must be assigned a code that uniquely and consistently identifies that holder or person.

That account-level code is reported to the central repository for every order originated. This is the part of the rule most likely to matter to an individual with a brokerage account, but the obligation described is a reporting one carried out through the member firm and the plan, not a filing duty the rule places on the account holder.

Format flexibility with a uniformity constraint

The rule allows the SROs to determine the specifics of how market participants report data to the central repository. That latitude might permit multiple electronic formats. However, the data must still be reported in a way that enables the central repository to send it to regulators in a uniform electronic format.

The SROs have made available a wide range of information about the current status of the system, including FAQs, technical specifications for reporting and related activities, and phase and reporting timelines.

Why this matters for account-level verification

For readers who verify US platform availability and account conditions, Rule 613 is best understood as a market-structure and recordkeeping rule. It does not, on its own, grant or deny access to any product in any state, and the source material reviewed does not describe any consumer-facing eligibility test. What it does show is that order and quote activity in NMS securities is intended to be captured, coded and time-stamped at a granular level, with account-level identifiers attached to originated orders.

That distinction matters when a platform or firm describes its regulatory posture. A statement that CAT reporting exists is not the same as a statement about which services a given account may use. The rule text here addresses data collection and reporting mechanics.

Status: adopted rule, plan-based implementation

The source states that the Commission adopted Rule 613. It describes the NMS plan mechanism and the data and timing requirements the plan must impose. It does not, in the material reviewed, provide a compliance calendar, a list of which phases are complete, or per-firm reporting statistics. Those details are pointed to the SROs' published information rather than restated in the rule description.

What the source does not say

Where a reader needs current operational status, the source directs attention to the SROs' published FAQs, technical specifications and phase timelines rather than to the rule description itself.

References in the source

The page also lists related material, including a May 27, 2026 item titled "CAT on a Hot Tin Roof" by Director Jamie Selway of the Division of Trading and Markets, an SEC press release seeking public comment on the Consolidated Audit Trail and other audit trails and data sources, and a statement on the CAT concept release by Commissioner Hester M. Peirce titled "Cattywampus." These are cited as related reading; the substantive requirements summarized above come from the rule description.

Sources

Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.