Trade Report Input
FINRA Rule 7230A governs the actual content, timing, and mechanics of a trade report submitted to the FINRA/Nasdaq Trade Reporting Facility, performing the same operational core function for this facility that Rule 7130 performs for the ADF, discussed extensively elsewhere in this dictionary.
While the two rules share substantially parallel structure and content, Rule 7230A carries several genuinely distinct features worth understanding on their own terms, particularly its precise alignment with CAT's own timestamp requirements and its specific provisions addressing aggregated clearing reports.
The Core Reporting Framework
Members must comply with the Rule 7200A Series when reporting transactions to the System, including executions of less than one round lot where those executions are to be compared and locked-in. Like the ADF, the FINRA/Nasdaq TRF offers both trade acceptance and comparison functionality, where a Reporting Party submits trade information and the contra party then accepts or declines it, and matching functionality, where both parties independently submit their own version of the trade and the System performs the match.
Parties must use the trade acceptance and comparison functionality specifically where no give-up agreement exists between them, mirroring the identical structural choice discussed in the Rule 7130 entry elsewhere in this dictionary.
The contra party generally has 20 minutes from the time of execution to accept or decline trade information submitted by the reporting party. Where a trade is executed while the facility is closed, this acceptance window instead runs until a specific reopening deadline, and this deadline differs meaningfully by facility: a firm has until 4:20 a.m. Eastern Time to accept or decline a trade reported to the FINRA/Nasdaq TRF, compared to 8:20 a.m. Eastern Time for the ADF or the OTC Reporting Facility.
This earlier FINRA/Nasdaq TRF deadline reflects the facility's historically earlier reopening relative to the ADF and ORF, a gap that has become even more pronounced following the 2026 extension of TRF operating hours to a 4:00 a.m. opening discussed in the Rule 7210A entry elsewhere in this dictionary.
Content Requirements and the CAT Timestamp Alignment
Rule 7230A(d) requires the same core content elements discussed in the Rule 7130 entry for the ADF: a buy, sell, or cross indicator, a short sale or short sale exempt indicator where applicable from either the Reporting Member's or contra side's perspective, an indicator of principal, riskless principal, or agent capacity, identification of the reporting side's clearing broker where different from normal, identification of any "give-up" executing broker, and, for orders carrying CAT recording and reporting obligations under Rules 6830 and 6870, an order identifier uniquely identifying that order for the date it was received.
This last requirement connects to a significant, precisely engineered alignment between Rule 7230A's timestamp requirements and CAT's own granularity standards. The SEC approved amendments on November 12, 2020, described in Regulatory Notice 20-41, requiring firms to report time fields in trade reports submitted to a FINRA equity trade reporting facility using the identical timestamp granularity they use when reporting the corresponding order execution event to CAT.
This means a firm with a CAT reporting obligation requiring nanosecond-level timestamp precision, discussed in the Rule 6860 entry elsewhere in this dictionary, must report that same nanosecond granularity to the FINRA/Nasdaq TRF as well, rather than potentially reporting a coarser granularity to the trade reporting facility even while capturing finer precision for CAT purposes.
FINRA identified one narrow but genuinely important exception to this alignment: Rule 144A restricted equity securities, which must be reported to the OTC Reporting Facility but carry no corresponding CAT reporting obligation given their exclusion from CAT's Eligible Security scope, discussed in the Rule 6810 entry elsewhere in this dictionary. For this specific category, a firm may continue reporting in seconds, or in milliseconds if its system captures that granularity, without being required to match a CAT-level nanosecond standard that, for these particular securities, simply does not exist in the first place.
Aggregation of Transaction Reports for Clearing Purposes
Rule 7230A(e) permits a specific, limited form of trade aggregation: individual executions of orders in a security at the same price and with the identical contra party may be aggregated into a single report submitted to the System for clearing purposes only.
This provision carries an important anti-gaming limitation: a Reporting Party may not withhold reporting a trade in anticipation of aggregating it with other, later transactions. This means the aggregation accommodation exists to simplify clearing mechanics for genuinely simultaneous or near-simultaneous executions at identical terms, not to create an incentive for delayed reporting while a firm waits to accumulate a larger batch of same-price, same-counterparty trades.
Step-Out and Step-In Reporting
Rule 7230A also addresses a specific clearing-only scenario involving position transfers between members: where both parties are submitting a clearing-only report to effectuate what the industry refers to as a step-out, the member transferring the position out reports a "step-out," while the member receiving that position reports a corresponding "step-in." This paired reporting convention allows the System to correctly reflect a position transfer between two members' clearing accounts without requiring either party to report the transaction as though it were an ordinary, price-discovering market transaction, since a step-out by its nature does not represent new price discovery in the same sense an ordinary execution does.
The Fee Transfer Mechanism
Rule 7230A(h) permits the same transaction fee transfer mechanism discussed in the Rule 7130 entry for the ADF: members may agree in advance to transfer a transaction fee charged by one member to another on a transaction in NMS stocks executed otherwise than on an exchange, reported through a clearing report to the FINRA/Nasdaq TRF. A member selling 100 shares at $10 with a $0.01 per share transaction fee reports 100 shares at $10, the price exclusive of the fee, for public dissemination, while separately reporting a $10.01 per share price inclusive of the fee for clearance and settlement through NSCC.
Before submitting any such report, both members and their respective clearing firms must have executed the required agreement and submitted it to the FINRA/Nasdaq TRF, with these agreements treated as member records under Rule 4511 subject to FINRA's ordinary recordkeeping obligations, and this mechanism does not relieve either member of its separate obligations under Rule 2232 and SEA Rule 10b-10 governing customer confirmations.
Contrasting the FINRA/NYSE TRF's Different Structure
Candidates and practitioners working toward the Rule 7200B Series governing the FINRA/NYSE Trade Reporting Facility, discussed elsewhere in this dictionary, should understand a fundamental structural difference from the outset: the FINRA/NYSE TRF does not provide trade acceptance and comparison functionality at all. Trades must already be locked-in before they can be submitted to that facility, a meaningfully different operational model from the FINRA/Nasdaq TRF, the ADF, and the ORF, each of which offers the two-step acceptance and comparison process discussed above. Firms operating across multiple trade reporting facilities should not assume the FINRA/NYSE TRF's submission workflow mirrors the FINRA/Nasdaq TRF's; a firm's own internal system logic needs to correctly branch based on which specific facility a given trade is being reported to.
A Worked Example of the Timestamp Alignment Requirement
Consider a firm operating a high-frequency trading desk whose order management system captures execution time in nanoseconds, generating a CAT order execution event reported at that same nanosecond precision under Rule 6860. When that same execution also generates a corresponding trade report to the FINRA/Nasdaq TRF, Regulatory Notice 20-41's alignment requirement means the firm must report that trade using the identical nanosecond granularity to the TRF, not simply whatever coarser granularity the TRF's own baseline rules might otherwise permit in isolation, since the alignment requirement specifically ties the two reporting obligations together rather than allowing them to be satisfied independently at different levels of precision. If this same firm also handles occasional Rule 144A restricted equity security transactions reported to the OTC Reporting Facility, however, it faces no equivalent nanosecond obligation for those specific trades, since those securities carry no CAT reporting obligation for the alignment requirement to actually anchor itself to; the firm may report those particular trades in seconds or milliseconds according to the ORF's own baseline granularity rules, entirely independent of whatever precision the firm's systems use elsewhere.
This example illustrates why firms handling a mixed portfolio of security types need genuinely granular, security-type-aware reporting logic rather than a single, uniform timestamp policy applied indiscriminately across every trade report the firm submits. A firm that mistakenly applies its CAT-matching nanosecond obligation to Rule 144A transactions that carry no such underlying CAT obligation is not violating any rule by over-reporting precision, but a firm that fails to apply the CAT-matching obligation where it genuinely does apply, for its NMS stock and other CAT-eligible security transactions, creates a genuine compliance gap under Regulatory Notice 20-41's alignment requirement.
The Executing Party Concept and Its Connection to Fees
Beyond Rule 7230A's own content requirements, the broader Rule 7200A Series relies on an "Executing Party" concept defined in Supplementary Material .01 to Rule 7620A, meaning the member bearing the trade reporting obligation under FINRA's rules, with the contra-side member correspondingly referred to as the "Contra." This same Executing Party and Contra framework that determines reporting responsibility under Rule 7230A also determines fee liability under Rule 7620A, discussed in the Rule 7600A entry elsewhere in this dictionary, meaning correctly applying this determination has consequences reaching well beyond the immediate trade reporting content itself.
FINRA's own recent rulemaking activity illustrates how directly this fee structure has evolved alongside the facility's growing trading volume. A 2024 filing noted that FINRA/Nasdaq TRF trade reporting activity had grown substantially over the preceding five years while the underlying fee caps and thresholds had remained unchanged over that same period, prompting Nasdaq, as the facility's Business Member discussed in the Rule 7210A entry, to propose raising the Cap Qualifying Activity threshold and introducing new tiered discounted fee structures to better reflect the facility's actual current volume and cost profile. Retail Participants, a specifically defined category under Rule 7620A, are exempt from FINRA/Nasdaq TRF trade reporting fees entirely, reflecting FINRA's broader policy interest in avoiding fee structures that might disproportionately burden retail-facing order flow relative to institutional trading activity.
Relevance Across FINRA's Examination Programs
The SIE, Series 63, and Series 65 do not test Rule 7230A's specific content and timing requirements, since these exams do not reach into facility-level trade reporting mechanics at this level of technical detail. Series 7 candidates should understand conceptually that trade reports to the FINRA/Nasdaq TRF must contain specific, standardized information within defined timeframes, reinforcing broader awareness of OTC trade reporting generally.
Series 24 candidates supervising FINRA/Nasdaq TRF activity need precise command of the CAT timestamp alignment requirement, since a principal's supervisory procedures should specifically confirm that the firm's trade reporting timestamp granularity genuinely matches its CAT reporting granularity for the same underlying orders, given how directly Regulatory Notice 20-41 ties these two obligations together. A principal should also understand the aggregation and step-out provisions precisely, ensuring the firm's clearing-only reporting practices correctly distinguish genuine simultaneous-execution aggregation from any pattern resembling prohibited delayed reporting. Series 57 candidates handling actual trade submission need working fluency with the facility-specific reopening deadlines, recognizing that the FINRA/Nasdaq TRF's 4:20 a.m. cutoff differs from the ADF and ORF's 8:20 a.m. cutoff, a distinction that matters directly when handling trades executed while a facility is closed.
Practical Guidance for Firms
Firms should build automated verification confirming that trade reporting timestamp granularity genuinely matches CAT reporting granularity for the same underlying order, rather than relying on two separate, independently configured systems that could drift out of alignment over time as either system's underlying capability changes. Given how specifically Regulatory Notice 20-41 ties these two reporting streams together, a firm whose CAT and TRF timestamp granularity diverge, even inadvertently through a system upgrade affecting only one reporting path, creates a compliance gap that a dedicated cross-system validation check could catch before it becomes a pattern.
Firms relying on the aggregation provision for clearing-only reports should build clear internal documentation distinguishing legitimate, contemporaneous aggregation of same-price, same-counterparty executions from any practice that could be characterized as withholding a trade report in anticipation of later aggregation, since the rule's prohibition on this latter practice is specific and firms should be able to demonstrate their aggregation practice reflects genuine simultaneity rather than deliberate reporting delay.
Firms with meaningful step-out and step-in clearing activity should ensure both parties to any such position transfer correctly and consistently apply the paired reporting convention, since a mismatch between one party's step-out report and the other party's step-in report could create a reconciliation discrepancy within the System that neither party's own internal records would necessarily reveal without a specific cross-check against the counterparty's own reporting.
Firms should build clear internal documentation identifying which security types within their trading activity carry a CAT reporting obligation and which do not, given how directly this determination controls whether the CAT timestamp alignment requirement actually applies to a given trade report. A firm's compliance and technology teams should maintain a shared, accurate reference distinguishing CAT-eligible securities from the narrow category of exceptions, such as Rule 144A restricted equity securities, ensuring the firm's reporting systems correctly apply the appropriate granularity standard to each specific transaction type rather than defaulting to a single, undifferentiated policy across the firm's entire trading activity.
Firms should also periodically review their Executing Party and Contra classifications against FINRA's evolving fee structure, particularly given the kind of periodic threshold and tier adjustments illustrated by the 2024 filing discussed above. A firm that has not revisited its own understanding of the applicable Cap Qualifying Activity thresholds or available fee tiers in some time may find its internal cost projections increasingly inaccurate as FINRA continues adjusting these figures to reflect the facility's growing trade volume, and firms should build periodic fee-schedule review into their broader regulatory change management process rather than assuming the fee structure they originally onboarded under remains permanently current.
