FINRA Rule 7330

This twenty-minute window is a genuinely distinctive feature of Rule 7330 with no parallel in either Rule 7230A or Rule 7230B, both of which operate on a ten-second reporting standard throughout. The distinction reflects the different market structure the ORF serves; OTC Equity Securities transactions, often involving thinly traded Pink Sheets or OTC Bulletin Board names, do not move through the same high-velocity comparison and acceptance cycle that NMS stock trading requires, and FINRA calibrated this rule's timing accordingly rather than importing the Trade Reporting Facilities' ten-second standard wholesale into a market segment where it would not fit the underlying trading pattern.

Trade Information To Be Input

Subsection (d) enumerates fifteen distinct data elements a Reporting Member must submit for each transaction, considerably more granular than the comparable lists under Rule 7230A(d) and Rule 7230B(d). Beyond the familiar security identification symbol, share quantity, unit price, execution time, capacity indicator, and Executing Party or Contra Party designation, Rule 7330(d) requires identification of the reporting side's Clearing Broker where different from normal, the reporting side's executing broker in a give-up arrangement, the contra side's executing broker, the contra side's introducing broker in a give-up trade, and the contra side's Clearing Broker where different from normal. This level of granularity reflects the layered correspondent clearing structure Rule 7310 establishes for the ORF, requiring the trade report itself to carry enough detail to identify every party potentially involved in a give-up arrangement.

Subsection (d)(13) adds a requirement not found in either Trade Reporting Facility rule: for any transaction involving an order for which a member has recording and reporting obligations under Rule 6830 and Rule 6870, the trade report must include an order identifier meeting FINRA-prescribed parameters that uniquely identifies the order for the date it was received. 

This order identifier requirement connects Rule 7330 to FINRA's broader order-tracking infrastructure in a way that Rule 7230A and Rule 7230B do not need to replicate, since the securities those rules cover are typically also captured through other order audit trail mechanisms not equally applicable to the OTC Equity Securities universe the ORF serves. Firms handling orders subject to this recording obligation need to ensure their trade reporting infrastructure can actually surface and transmit the correct order identifier at the point of trade report submission, rather than treating order identification and trade reporting as two disconnected workflows managed by separate systems.

Reporting Cancelled and Reversed Trades

Subsection (f) requires members to report to the System the cancellation or reversal of any trade previously submitted, with a narrow exception for trades cancelled directly by FINRA staff under the Rule 11890 Series. Responsibility for submitting the cancellation or reversal report falls specifically on the member responsible under FINRA rules for the original trade report, and members must comply with the deadlines and other requirements set forth in Rule 6622 governing cancelled and reversed trades. 

This structure closely parallels the cancellation and reversal frameworks found in Rule 7230A and Rule 7230B, reflecting FINRA's consistent approach across its trade reporting rules: the party that created the original record bears responsibility for correcting it, and the specific timing mechanics live in the underlying Rule 6000 Series transaction reporting rule rather than in the Rule 7300 Series input rule itself.

This consistency is worth noting precisely because so much else about Rule 7330 diverges from its Trade Reporting Facility counterparts. A firm that has already built solid cancellation and reversal handling processes for Rule 7230A or Rule 7230B compliance can extend that same operational logic to ORF reporting with relatively little modification, unlike the timing and aggregation provisions discussed elsewhere in this entry, which genuinely require facility-specific configuration rather than a shared, portable approach.

Aggregation Permitted, Unlike Rule 7230B

Subsection (e) permits individual executions of orders in a security at the same price and with the identical contra party to be aggregated into a single report for clearing purposes only, provided a Reporting Party does not withhold reporting a trade in anticipation of such aggregation. 

This places Rule 7330 in alignment with Rule 7230A's permissive approach rather than Rule 7230B's flat prohibition on aggregation. Firms that have internalized the aggregation divergence between the two Trade Reporting Facility rules need to extend that same careful, facility-specific thinking to the ORF: Rule 7330 allows what Rule 7230B forbids, and a firm's reporting logic needs to reflect this correctly for each facility rather than assuming a single aggregation policy applies universally across every FINRA trade reporting destination it services.

Reporting Certain Transactions for Regulatory Transaction Fee Assessment

Subsection (g) is unique to Rule 7330 among the trade report input rules discussed across this dictionary. It requires specific categories of transactions subject to a regulatory transaction fee under Section 3 of Schedule A to the FINRA By-Laws to be reported in a manner denoting they are submitted for regulatory purposes rather than dissemination, with a hard 8:00 p.m. Eastern Time submission deadline. 

The three enumerated categories are transactions where the buyer and seller have agreed to trade at a price substantially unrelated to the current market with consideration given, commonly called away-from-market sales; transactions effected pursuant to the exercise of an OTC option; and transfers of proprietary securities positions effected in connection with a merger or direct or indirect acquisition that are not in furtherance of a trading or investment strategy, which additionally require three business days advance written notice to FINRA of the member's intent to rely on this exception.

This structure exists because Section 31 of the Exchange Act requires FINRA to pay transaction fees and assessments to the SEC to help fund the government's market supervision, and FINRA in turn collects corresponding regulatory transaction fees from its own membership. 

Certain transaction types, precisely because they do not represent ordinary arm's-length market activity, require distinct reporting treatment to ensure the regulatory transaction fee framework operates correctly without distorting public market data through dissemination of prices substantially unrelated to genuine market conditions. 

Firms engaged in corporate reorganizations, mergers, or acquisitions involving proprietary security position transfers need to be particularly alert to the three-business-day advance notice requirement, since failing to provide it in time forecloses reliance on this specific reporting exception.

The requirement that members report qualifying proprietary position transfers on the same day as the ultimate transfer of positions on their books and records, absent circumstances warranting later reporting, adds a further operational wrinkle. 

Firms cannot treat the three-business-day advance notice as satisfying their entire reporting obligation; the notice merely establishes eligibility to use the exception, while the actual transaction report must still track the timing of the underlying books-and-records transfer itself. 

Compliance teams coordinating these transfers across legal, operations, and trading desk functions benefit from mapping both deadlines explicitly, since missing either independently undermines the firm's ability to rely on this reporting treatment.

Non-Tape Reports and Clearing-Only Reporting

Subsections (h) and (i) closely mirror the non-tape report restrictions and transaction fee facilitation provisions found in Rule 7230B, prohibiting non-tape reports tied to previously unreported trades except in narrow riskless principal circumstances, and requiring executed agreements before members may facilitate transaction fee transfers through clearing reports. 

Subsection (h)(4) further details the clearing-only, non-regulatory report mechanism, permitting a member to submit a report solely for clearing purposes where the underlying regulatory reporting obligation has already been satisfied through a separate tape or non-tape report, while making clear that a clearing-only report cannot itself satisfy any regulatory reporting requirement, a limitation that mirrors the equivalent certification concept already familiar from the parallel Trade Reporting Facility provisions. 

This requirement that members retain and produce documentation relating to any associated previously reported trade, whenever a non-tape report references it, gives FINRA a concrete verification mechanism separate from the report's own content, reinforcing the audit trail integrity concerns that run throughout FINRA's trade reporting rulebook more broadly.

Regulatory History and Rulebook Placement

Rule 7330 was adopted by SR-FINRA-2008-021, effective December 15, 2008, alongside the rest of the original Rule 7300 Series established during the Consolidated FINRA Rulebook process described in Regulatory Notice 08-57. 

It has since been amended more extensively than perhaps any other rule discussed in this dictionary series, with recorded amendments spanning from SR-FINRA-2009-024 through SR-FINRA-2021-017, reflecting more than a dozen distinct rule filings addressing timing standards, order identifier requirements, transfer reporting exceptions, and technical refinements over more than a decade. 

Regulatory Notice 10-24 alone reflects a significant substantive change, the SEC's approval of amendments requiring OTC equity trade reporting within thirty seconds of execution as an intermediate step in FINRA's broader multi-year effort to tighten reporting timeliness standards across its facilities, a standard later tightened further still as FINRA continued refining its reporting timeliness expectations across the OTC equity market.

The rule sits between Rule 7320, Trade Reporting Participation Requirements, and Rule 7340, Trade Report Processing, occupying the same structural position that Rule 7230A occupies within the Rule 7200A Series and Rule 7230B occupies within the Rule 7200B Series. 

Its unusually extensive amendment history relative to its counterparts reflects the ORF's ongoing evolution as FINRA has continued refining OTC Equity Securities reporting standards well after the Trade Reporting Facility rules reached comparative stability.

Examination Relevance Across the FINRA Exam Suite

Series 24 candidates should focus on three distinctive features of this rule: the twenty-minute accept-or-decline window that departs from the ten-second standard governing the Trade Reporting Facilities, the aggregation permission under subsection (e) that aligns with Rule 7230A rather than Rule 7230B, and the regulatory transaction fee reporting category under subsection (g) that has no direct counterpart elsewhere. 

A General Securities Principal supervising OTC Equity Securities trading needs working familiarity with all three to properly calibrate supervisory procedures for ORF-reported activity, and should additionally understand the order identifier requirement under subsection (d)(13) well enough to confirm that supervisory review of Rule 6830 and Rule 6870 order activity actually connects back to the corresponding trade reports.

SIE candidates should retain the general principle that different FINRA trade reporting facilities can apply meaningfully different timing standards depending on the market structure each serves, without needing to master the specific twenty-minute figure. 

Series 7 candidates have limited direct exposure to Rule 7330's mechanics, though representatives working with clients trading OTC Bulletin Board or Pink Sheets securities benefit from understanding that these trades follow a distinct reporting timeline from exchange-listed securities. 

Series 63 and Series 65 candidates will not encounter Rule 7330 on either exam, as both are oriented toward state securities law and investment adviser regulation rather than FINRA facility-level trade reporting mechanics.

Professional and Industry Relevance for Working Practitioners

For operations teams building ORF reporting infrastructure, Rule 7330's twenty-minute accept-or-decline window and its subsection (e) aggregation allowance are exactly the kind of facility-specific parameters that must be explicitly configured rather than inherited from Trade Reporting Facility logic. 

A firm that applies its FINRA/NYSE Trade Reporting Facility timing assumptions, or its Rule 7230B aggregation prohibition, to ORF reporting without adjustment risks systematic reporting errors that a well-designed, facility-aware system would avoid entirely, precisely the kind of avoidable error a careful pre-launch configuration review is meant to catch.

For compliance officers overseeing corporate transaction activity, subsection (g)'s three-business-day advance notice requirement for proprietary position transfers connected to mergers or acquisitions deserves a dedicated place in deal-related compliance checklists. 

Because this notice requirement is a precondition to using the exception rather than a formality that can be satisfied after the fact, firms engaged in M&A-related security transfers need this requirement flagged early in deal planning, well before the transfer itself is scheduled to occur, to avoid missing the window and losing access to the appropriate reporting treatment.

For firms tracking millisecond-level execution timing, the Supplementary Material .01 requirement, that all time fields be reported in hours, minutes, seconds and milliseconds where the member's system captures time in milliseconds, deserves attention alongside the twenty-minute accept-or-decline standard rather than being treated as a separate, unrelated technical requirement. 

A firm whose order management system captures millisecond-level timestamps cannot report only to the second simply because the ORF's overall accept-or-decline window is comparatively generous; the underlying execution time field itself must still reflect the full precision the firm's own systems are capable of capturing, consistent with the same millisecond reporting expectation that applies across FINRA's other trade reporting facilities.

Examination Relevance and Key Takeaways

Rule 7330 governs the substantive mechanics of ORF trade reporting, distinguished from Rule 7230A and Rule 7230B primarily by its twenty-minute accept-or-decline timing standard, its permissive aggregation treatment aligned with Rule 7230A, its expanded fifteen-element data requirement including an order identifier tied to Rule 6830 and Rule 6870, and its unique regulatory transaction fee reporting category under subsection (g) covering away-from-market sales, OTC option exercises, and qualifying proprietary position transfers. 

Its cancellation and reversal framework under subsection (f), by contrast, closely mirrors the equivalent provisions in Rule 7230A and Rule 7230B, illustrating that not every aspect of Rule 7330 requires facility-specific reinterpretation. The rule's unusually extensive amendment history reflects FINRA's sustained, multi-year refinement of OTC Equity Securities reporting standards well beyond the point of relative stability reached by the Trade Reporting Facility rules.

Series 24 candidates and operations supervisors carry the greatest practical stake in mastering these facility-specific distinctions, while SIE candidates need only the conceptual grasp that timing and aggregation standards vary meaningfully across FINRA's trade reporting facilities. Series 7 candidates retain limited but useful context regarding OTC Equity Securities reporting timelines, and Series 63 and Series 65 candidates can treat this rule as entirely outside their tested scope. For working operations and compliance professionals, treating each of Rule 7330's distinctive provisions, timing, aggregation, and regulatory transaction fee reporting alike, as facility-specific parameters requiring explicit configuration remains the most effective way to avoid reporting errors traceable to assumptions carried over from the Trade Reporting Facility rules.