FINRA Rule 6730

The Baseline Timing Standard

Each member that is a Party to a Transaction in a TRACE-Eligible Security must report that transaction as soon as practicable, but no later than within 15 minutes of the Time of Execution, except as otherwise specifically provided elsewhere in the rule. Transactions not reported within this window are designated late. The precise timing framework varies depending on when execution occurs relative to TRACE System Hours: transactions executed at or after 12:00:00 a.m. through 7:59:59 a.m. Eastern Time must be reported the same day, no later than 15 minutes after the TRACE system opens; transactions executed during standard TRACE System Hours, 8:00:00 a.m. through 6:29:59 p.m., must be reported within 15 minutes of execution; transactions executed less than 15 minutes before the 6:30:00 p.m. close must instead be reported no later than 15 minutes after the system opens the next business day, designated "as/of" with the execution date; and transactions executed from 6:30:00 p.m. through 11:59:59 p.m., or on a Saturday, Sunday, or holiday, must similarly be reported the next business day on an "as/of" basis.

U.S. Treasury Securities carry a longer, separate outer limit: transactions must be reported within 60 minutes of execution during standard TRACE System Hours, with parallel "as/of" treatment for trades executed near or outside those hours, and an exception available to members with limited trading volume in Treasuries. Electronically executed Treasury transactions must be reported in the finest time increment the executing system captures, again subject to the limited-volume exception.

The 2022 to 2025 Reporting Speed Saga

No aspect of Rule 6730 has attracted more sustained industry engagement than the question of whether the 15-minute standard should be shortened. FINRA first floated the idea in Regulatory Notice 22-17, noting that roughly 82% of covered transactions were already being reported within one minute, and asking whether technological advances over the nearly two decades since the 15-minute standard was adopted justified tightening it. FINRA formally proposed the change on January 11, 2024, seeking to reduce the outer limit to one minute for corporate bonds, agency debt securities, asset-backed securities, and agency pass-through mortgage-backed securities traded to-be-announced, while building in a de minimis exception for firms with limited reporting activity and a phased, three-year transition to a five-minute limit for manual trades.

The SEC approved this proposal in September 2024, with FINRA noting that approximately 83% of covered transactions were already reported within one minute even under the existing 15-minute rule, framing the change as a modernization exercise rather than a response to any specific market failure. The approved amendments were never implemented, however. Continued engagement with member firms surfaced concerns about the feasibility of one-minute reporting for more complex workflows, particularly allocations to managed customer accounts and portfolio trades, and firms also flagged how FINRA's existing correction-handling logic, which could mark a trade late based on a subsequent correction rather than only the original report's timeliness, compounded the practical difficulty of the shorter window. FINRA ultimately filed a further proposal maintaining the 15-minute standard for all trade types, which the SEC approved in September 2025, formally superseding the one-minute reduction before it ever took effect and simultaneously updating the correction-handling logic so that a timely original report followed by a later correction no longer triggers a late designation on its own.

Primary Market Transactions: List or Fixed Offering Price and Takedown Transactions

A List or Fixed Offering Price Transaction and a Takedown Transaction, both defined in Rule 6710(q) and (r) and identified using the "P1" modifier, are primary market sale transactions occurring on a security's first day of trading, generally at a published fixed offering price or, for Takedown Transactions, at a discount from that price extended to syndicate or selling group members. Unlike ordinary secondary market transactions, these primary market trades are reported on a T+1 basis rather than within 15 minutes, and, at least initially, are not disseminated to the public at all; FINRA stated it would study the reported data over time and separately determine whether and how dissemination should eventually apply.

FINRA extended a related accommodation to Treasury hedging activity connected to these primary market transactions. Effective June 1, 2020, members executing a Treasury Security transaction specifically to hedge a P1 transaction receive additional time to report, until 6:29:59 p.m. Eastern Time on T+1, and must append a distinct modifier identifying the trade as a hedge of that kind. FINRA has clarified through its FAQ guidance that this accommodation travels with the underlying hedging relationship rather than the identity of the reporting firm: a syndicate member selling directly to customers at the list price, who also executes the customer's Treasury hedge, may use the extended time and modifier, but the extension is not available where a firm's Treasury hedging activity is unconnected to any actual P1 transaction. FINRA has also clarified that the hedge modifier must be appended whenever it applies, even where a firm chooses to report on trade date rather than availing itself of the extra time.

The Portfolio Trade Modifier

Effective May 15, 2023, FINRA added paragraph (d)(4)(H), requiring members to append a distinct modifier to corporate bond trades that are part of a qualifying portfolio trade. A portfolio trade for this purpose is a transaction between exactly two parties involving a basket of at least 10 unique corporate bond issues, priced at a single aggregate figure for the entire basket. This threshold was actually lower than what the Fixed Income Market Structure Advisory Committee had originally recommended, a 30-unique-issuer minimum, reflecting FINRA's judgment that a smaller basket size still warranted flagging for market participants trying to interpret whether an individual bond's reported price reflects its own independent market or merely its place within a broader basket negotiation.

FINRA's subsequent FAQ guidance clarified several edge cases worth understanding. The modifier applies based on counting unique securities by identifier, such as CUSIP, regardless of whether multiple bonds in the basket share a common or affiliated issuer; a basket mixing corporate bonds with other security types only triggers the modifier if the corporate bond count alone reaches the 10-issue threshold, and only the qualifying corporate bond reports themselves carry the modifier, not reports for the non-corporate-bond components; and a subsequent partial cancellation that drops a basket below 10 bonds does not require correcting the remaining reports to remove a modifier that was correctly applied at the time of execution, though a modifier applied in error from the outset must still be corrected once discovered.

Securitized Product and Special Pricing Indicators

Rule 6730(d)(4)(D) requires specific indicators for transactions in Securitized Products: the ".O" indicator for a Specified Pool Transaction, ".N" for a Stipulation Transaction, ".D" for a Dollar Roll, and ".L" where a single transaction combines both a Dollar Roll and a Stipulation Transaction. Separately, a "special price" modifier applies where a transaction is not executed at a price reflecting the current market, such as a debt security conventionally traded without a due bill or warrant attached but reported here with one attached; the reporting method's special price memo field must then explain the reason. This special price modifier does not apply to transactions priced using a weighted average price methodology, which instead carry their own distinct ".w" modifier.

The No-Remuneration Indicator

Effective May 23, 2016, Rule 6730 requires a "No Remuneration" indicator on trade reports that do not reflect any commission, mark-up, or mark-down, a mechanism designed to distinguish transactions genuinely lacking remuneration from transactions where remuneration existed but simply was not known or captured at the time of reporting. Three categories are excepted from this indicator requirement: List or Fixed Offering Price Transactions, Takedown Transactions, and inter-dealer transactions, reflecting that remuneration works differently, or is structurally embedded differently, in each of these transaction types compared to an ordinary customer-facing secondary market trade.

Reporting Method and Good Faith Obligations

Where electronic submission into TRACE is not possible, a member may be required to report as soon as practicable to the Market Regulation Department on a paper form, though this paper fallback is unavailable for transactions that can otherwise be reported into TRACE, including trades executed on weekends or holidays that can still be submitted electronically on an "as/of" basis. Rule 6730(a)(8) imposes an important good-faith obligation: where a member makes a good faith determination that a transaction involves a TRACE-Eligible Security, it must report that transaction under this rule even if the security has not yet been entered into the TRACE system itself, promptly notifying FINRA Operations with the new-security information required under Rule 6760(b) as part of that process rather than waiting for the security to already appear in TRACE before reporting begins.

Exclusions from the Reporting Obligation

Two categories of transfer fall outside Rule 6730's reporting obligation entirely. Transfers of TRACE-Eligible Securities executed solely to create or redeem an instrument that evidences ownership of, or tracks, the underlying transferred securities, such as the creation or redemption process for an exchange-traded fund, are not reportable transactions under this rule. Transactions in TRACE-Eligible Securities that are listed on a national securities exchange, where the transaction is both executed on and reported to that exchange and disseminated publicly through the exchange's own mechanism, are similarly excluded, avoiding duplicative reporting of the same transaction through two separate regulatory channels.

How TRACE Displays What It Receives

For real-time dissemination purposes, TRACE generally displays the sell side of a transaction occurring between two FINRA members, and displays all transactions occurring between a FINRA member and a non-member counterparty. This convention shapes how market participants should interpret disseminated TRACE data: a single inter-dealer trade between two members generates one disseminated report reflecting the sell side, not two separate, duplicative reports for each side of the same underlying transaction.

What This Rule Means Across FINRA's Exam Tracks

The reporting mechanics in Rule 6730 sit almost entirely outside the SIE, Series 63, and Series 65 syllabi, all three of which test broader market structure or state-law concepts rather than facility-specific fixed income reporting mechanics; a candidate for any of these three exams can treat this rule as background context at most. The Series 7 syllabus touches fixed income products directly, so a basic sense that bond trades carry their own distinct, rapid reporting obligation reinforces general product knowledge, though the exam does not probe the specific modifiers or timing exceptions covered here.

The Series 24 and Series 57 populations, by contrast, have genuine, hands-on reason to master this rule's mechanics rather than merely recognize its existence. A principal building supervisory procedures around a fixed income desk needs the 2022-2025 reporting speed history well in hand, since it illustrates precisely how FINRA weighs transparency benefits against documented operational feasibility concerns, a judgment call a principal may need to make internally long before FINRA revisits the question again. That same principal also needs working fluency in the portfolio trade modifier's 10-issue threshold, the P1 transaction framework's T+1, non-disseminated treatment, and the distinction between the special price and weighted-average-price modifiers, since a firm's own written supervisory procedures should specifically address correct modifier selection as a distinct compliance risk from mere reporting timeliness.

A trader or trade reporting specialist preparing for the Series 57 benefits from working through this rule the way one might work through a decision tree: identify the security type and transaction structure first, determine which timing standard and modifier set applies as a consequence, and only then execute the report. Getting the classification wrong at the front end, mistaking a Takedown Transaction for an ordinary secondary trade, for instance, cascades into an incorrect timing deadline, an incorrect dissemination outcome, and potentially an incorrect fee assessment, all stemming from a single upstream misclassification.

The Correction-Handling Change in Practical Terms

The 2025 update to how corrections affect lateness deserves closer attention than a single sentence can give it, since it reverses a source of real friction firms had lived with for years. Under the framework that existed before this change, a member could report a transaction well within the 15-minute window, only to discover an error in a disseminated field, such as an incorrect price or quantity, sometime after that window had closed. Correcting that error, even though the original report had been perfectly timely, could itself cause the trade to be marked late, since FINRA's system logic at the time evaluated timeliness based on the correction's submission time rather than the original report's.

This created a genuine disincentive around correction behavior: a firm discovering a minor, immaterial error in an already-timely report faced the prospect of converting a clean, timely trade into a late one simply by fixing it. FINRA's 2025 change eliminates this dynamic by anchoring the lateness determination solely to the original report's submission time, meaning a firm can now correct a disseminated field without fear of retroactively creating a late designation, provided the original submission was itself timely. Firms that had previously built internal escalation procedures around this correction-triggered lateness risk should revisit those procedures in light of the updated system logic, since a control designed around the old framework may now be addressing a risk that no longer exists in the same form.

Building This Into a Firm's Compliance Architecture

A trade reporting supervisory program built around Rule 6730 works best when it treats modifier selection as at least as important as raw timeliness, since FINRA's own recent rulemaking history shows sustained regulatory attention to both dimensions rather than timing alone. Firms handling portfolio trades regularly should build automated basket-counting logic directly into their order management systems rather than relying on manual identification of the 10-unique-issue threshold, given how easily a mixed basket of corporate bonds and other instruments can produce an incorrect modifier determination if counted by hand.

Firms with meaningful primary market or syndicate desk activity should specifically train staff on the P1 transaction framework's distinctive non-disseminated, T+1 treatment, since staff accustomed to the ordinary 15-minute, immediately-disseminated secondary market standard can easily misapply that more familiar framework to a first-day primary transaction that actually calls for entirely different handling. Finally, firms should treat FINRA's walk-back of the one-minute reporting proposal as a live illustration of how regulatory feedback loops function in practice: documented, specific operational concerns, rather than blanket objection, produced a genuine reversal of an already-SEC-approved rule change, a precedent worth remembering the next time FINRA proposes a similarly ambitious tightening of TRACE's reporting speed.