FINRA Rule 6622

A dedicated search for third-party legal commentary on this rule found comparatively little independent law firm analysis, for a specific reason worth noting directly. FINRA does not rely primarily on external enforcement narratives to police this rule. It operates two dedicated internal compliance monitoring products, the Reporting Firm 10 Second Compliance Report Card and the Executing Firm 10 Second Compliance Report Card, both issued monthly directly to member firms through FINRA's own compliance reporting tools. These reports are the actual operative enforcement mechanism practitioners deal with day to day, far more than any published disciplinary action, and their existence explains why so much of the practical guidance on this rule comes from FINRA's own FAQ publications rather than from outside commentary.

The Core Ten-Second Standard

Under paragraph (a)(1), OTC Reporting Facility Participants must transmit last sale reports to the ORF as soon as practicable, but no later than 10 seconds after execution, for transactions in OTC Equity Securities executed during normal market hours. If the ORF is unavailable due to system or transmission failure, the report must instead be made by telephone to the Operations Department. Any transaction not reported within 10 seconds after execution is designated late, regardless of the reason for the delay, and this designation attaches automatically rather than requiring any separate FINRA determination.

Reporting outside normal market hours follows a related but distinct set of rules. Last sale reports of transactions executed between 8:00 a.m. and 9:30 a.m. Eastern Time must still be reported within 10 seconds of execution, but the report must additionally carry a unique trade report modifier FINRA specifies to denote execution outside normal market hours. This modifier requirement exists because pre-market last sale data needs to be clearly distinguishable from regular-session activity once it reaches the tape, since a data consumer viewing last sale information needs to know immediately whether a printed price reflects thin pre-market liquidity or the deeper regular-session market.

Restricted Equity Securities effected under Securities Act Rule 144A carry a materially different deadline. Transactions executed between 8:00 p.m. and midnight Eastern Time, or on any non-business day, must be reported by the following business day by 8:00 p.m. Eastern Time and designated as "as/of" trades. This considerably longer window reflects the different, less continuous trading pattern typical of Rule 144A restricted securities compared to actively quoted OTC Equity Securities, where negotiated private placements and resales do not generate the kind of continuous two-sided market that would make a 10-second reporting standard practical or meaningful.

The Cascading Late Reporting Framework

Rule 6622 builds a specific hierarchy for handling missed deadlines. Any transaction not reported within 10 seconds is designated late from that point forward. If a transaction required to be reported on trade date is not reported that day, it must instead be reported on an "as/of" basis on a subsequent date, and it remains designated late regardless of when that subsequent report occurs.

The same cascading logic applies to Restricted Equity Securities. If a transaction required to be reported "as/of" the following business day is not reported by that day, it must be reported on a later date still and will likewise be marked late. This structure means a firm cannot cure a missed deadline by simply reporting late; the transaction carries the late designation permanently once the original window has passed, which is precisely why the designation feeds directly into FINRA's monthly compliance report cards rather than disappearing once the trade is eventually reported.

The As Soon As Practicable Standard

FINRA's own supplementary guidance addresses what "as soon as practicable" means in practice, and this is a frequently misunderstood aspect of the rule. A member must adopt policies and procedures reasonably designed to achieve prompt reporting, and must implement systems that begin the reporting process without delay upon execution. Where such policies and systems are genuinely in place, a firm generally will not be viewed as violating the standard because of delays caused by extrinsic, unpredictable factors it did not intend to cause, such as a temporary connectivity issue between the firm's own systems and the ORF.

FINRA has drawn a clear line, however, around deliberate delay. In no event may a member purposely withhold trade reports, for example by programming systems to delay reporting until the last permissible second of the 10-second window. This distinction between incidental delay and engineered delay is central to how FINRA evaluates a firm's compliance posture, not just its raw timing statistics, since two firms with identical average reporting times can be treated very differently depending on whether that timing reflects genuine system limitations or deliberate throttling.

FINRA has also addressed the specific case of manual trade entry. Where a firm must manually enter trade details following execution, and has established efficient reporting processes but still cannot complete reporting within 10 seconds, FINRA will consider the complexity and manual nature of the transaction, including factors like a volume-weighted average price trade or a trade involving a basket of securities, in determining whether reasonable justification exists to excuse what might otherwise look like a pattern of late reporting. This case-by-case treatment means firms relying on manual processes cannot assume automatic protection; they must actually demonstrate that their procedures were efficient and that the delay stemmed from genuine complexity rather than a poorly designed workflow.

Content, Price, and Capacity Requirements

Paragraph (d) governs the substantive content a last sale report must contain, and this is where much of the rule's remaining technical detail sits. For agency transactions, the member reports the number of shares and the execution price, excluding any commission charged on the trade. For principal transactions, each purchase and each sale is generally reported separately, again reporting shares and price, but the reported price must exclude any mark-up, mark-down, or service charge the firm applies.

The reported price for a principal transaction must also be reasonably related to the prevailing market at the time, a standard FINRA assesses by looking at market conditions in the security, the number of shares involved, published bids and offers with displayed size in any inter-dealer quotation system at the time of execution, and the costs and expenses of execution and clearance. This "reasonably related to the market" standard gives FINRA a basis to question a reported price that looks disconnected from contemporaneous quoting activity, even where the mechanical timing of the report itself was fully compliant, which means a firm can pass every timing test and still face scrutiny purely on pricing grounds.

Rule 6622 also addresses Stop Stock Transactions specifically. Where a trade is a Stop Stock Transaction, as defined in Rule 6420, the transaction report must include both the time of execution of the trade and the separate time at which the member and the other party agreed to the Stop Stock Price. If the Stop Stock Transaction is executed and reported within 10 seconds of the time the parties agreed to that Stop Stock Price, the designated modifier is not required and only the actual time of execution needs to be reported.

A related provision addresses transactions reported at a price different from the current market because the execution price is based on a prior reference point in time. In that scenario, the report must include both the time of execution and the prior reference time. If the trade is executed and reported within 10 seconds of that prior reference point, again, the designated modifier is not required and only the time of execution needs to be included.

Where electronic submission of a last sale report to the ORF is not possible, for example because a ticker symbol is no longer active or the relevant market participant identifier has lapsed, members must report as soon as practicable to the Market Regulation Department using Form T. This paper-based fallback exists specifically to prevent a technical system limitation from becoming an excuse for non-reporting, and firms are still expected to meet the underlying timeliness standard even when using this alternative submission method.

Determining the Reporting Party

A separate, heavily tested dimension of Rule 6622 is determining which party to a trade actually bears the reporting obligation. FINRA defines the "Executing Firm" as the member that receives an order for handling or execution, or is presented an order against its quote, does not subsequently re-route that order, and executes the transaction. In a transaction between two members where both could technically satisfy the executing party definition, such as a manually negotiated telephone transaction, the member representing the sell side reports the transaction, unless the parties agree otherwise and the sell-side member contemporaneously documents that agreement.

This differs meaningfully from the older NASD Rule 6620 framework, which assigned reporting responsibility based on OTC Market Maker status: the sell-side market maker reported in market-maker-to-market-maker trades, the market maker always reported against a non-market maker, and the sell side reported between two non-market makers. The current executing-party framework is more functional and less status-based, focused on which firm actually controlled execution rather than which firm held a market maker designation in that security, reflecting the broader decline of the formal market maker designation as the primary organizing concept in OTC equity trading.

Give-Up Agreements

Paragraph (h) permits a member to allow another member to report and lock in trades on its behalf, provided both parties have completed a written "give-up agreement" in the form FINRA specifies and submitted it to the ORF. Critically, the member with the underlying reporting obligation remains responsible for the transaction even after delegating the mechanical reporting task. Both the member with the reporting obligation and the member submitting the trade on its behalf share responsibility for ensuring the submitted information complies with all applicable rules, meaning delegation reduces operational burden without reducing legal exposure.

Direct Participation Program Securities

Supplementary Material .01 addresses a narrower category: secondary market transactions in non-exchange-listed Direct Participation Program securities. Because DPP interests often trade through negotiated terms rather than continuous quotation, Rule 6622 defines "date of execution" and "time of execution" for these securities as the date and time when the parties have agreed to all essential terms, including price and the number of units traded, rather than by reference to a continuous market price. This bespoke definition exists because DPP interests, unlike actively quoted OTC Equity Securities, typically change hands through individually negotiated transactions where no observable market price exists at the moment of agreement.

Timestamp Granularity

Firms are not required to report execution time in milliseconds if their underlying system does not capture time at that granularity, and may continue reporting in seconds instead. Where a firm's system, including an ATS, does capture time in milliseconds, however, that system is expected to report in milliseconds rather than rounding to the nearest second. FINRA has tied this millisecond reporting expectation directly to the timestamp granularity requirements under Rule 6860 of the Consolidated Audit Trail Compliance Rule Series, meaning a firm's CAT reporting obligations and its Rule 6622 reporting obligations are expected to use consistent timestamp precision across both regulatory regimes rather than treating them as separate technical requirements.

Series 7 and SIE Relevance

The SIE tests OTC market structure only at a conceptual level and does not require candidates to know Rule 6622's specific deadlines. Series 7 candidates should retain the basic concept that OTC Equity Security trades must be reported to FINRA promptly after execution, since this reinforces broader product knowledge about how non-exchange-listed securities function in practice compared to exchange-listed securities. Series 7 candidates are not expected to know the precise 10-second figure, the Stop Stock Transaction mechanics, or the give-up agreement framework in any operative detail.

Series 63 and Series 65 Relevance

Series 63 and Series 65 candidates do not need this rule at any operative level. These exams test state securities law and investment adviser fiduciary obligations, not the mechanics of FINRA's equity trade reporting infrastructure. Candidates preparing for either exam can set this rule aside entirely without any exam-readiness risk, since neither exam blueprint touches trade reporting mechanics of this kind.

Series 24 Relevance

Series 24 candidates should understand Rule 6622 as one of the more actively supervised rules in the FINRA rulebook, precisely because FINRA issues monthly Reporting Firm and Executing Firm 10 Second Compliance Report Cards directly to member firms. A principal reviewing these report cards needs to distinguish properly modified late trades from late trades that were not modified and from improperly modified trades, since each category carries a different supervisory response and a different remediation path.

Series 24 candidates should also understand the enforcement bridge this rule shares with Rule 6623: a pattern or practice of late reporting without reasonable justification exposes the firm to a Rule 2010 violation, not merely a technical trade reporting deficiency. A principal's written supervisory procedures should specifically address how the firm reviews its own compliance report card data, how it monitors principal transaction pricing against the "reasonably related to the market" standard, and what escalation occurs when late-trade counts rise above an internally defined threshold.

Series 57 Relevance

Series 57 candidates have the strongest direct relationship to Rule 6622 of any exam population, since Series 57 is built specifically around order handling, execution, and trade reporting. Series 57 candidates should know the 10-second standard precisely, along with its variations: the additional modifier requirement for pre-market transactions between 8:00 a.m. and 9:30 a.m., and the materially longer next-business-day, 8:00 p.m. deadline for Restricted Equity Securities under Rule 144A.

Series 57 candidates should also be able to correctly identify the reporting party in a given trade scenario using the executing-party framework, correctly apply the Stop Stock Transaction and prior-reference-time modifier exceptions, and know when a principal transaction's reported price could draw scrutiny under the "reasonably related to the market" standard. A trader unable to correctly identify who bears the reporting obligation in a given transaction is at direct risk of causing an unreported or duplicate-reported trade, either of which creates its own compliance exposure independent of any timing violation.

Relevance to Working Financial Services Professionals

For compliance officers, Rule 6622 is not a rule that gets reviewed periodically; it generates its own ongoing, firm-specific data feed through FINRA's monthly Report Cards. A mature trade reporting supervisory program treats these Report Cards as a primary compliance input, tracking trends in late-trade counts and improperly modified reports over time rather than waiting for FINRA to initiate a formal inquiry based on the same underlying data that the firm already has access to.

The distinction between incidental delay and engineered delay matters enormously for how a firm should design its reporting infrastructure. A firm whose systems are configured to report as close to the 10-second boundary as possible, even if technically compliant on any single trade, is building exactly the kind of pattern FINRA's guidance specifically warns against, and a sustained pattern of near-boundary reporting can itself become the basis for an inference of purposeful delay regardless of whether any individual trade was reported late in isolation.

Firms transitioning legacy manual trade entry workflows should pay close attention to FINRA's guidance on reasonable justification for manual trades, since this is one of the few areas where FINRA has explicitly acknowledged that perfect 10-second compliance may not be achievable for certain trade types. Documenting the complexity factors FINRA has identified, including basket trades and volume-weighted average price transactions, as part of a firm's own exception-handling procedures gives a firm a stronger evidentiary basis if FINRA later questions a pattern of manual-trade lateness during an examination.

Firms should also build periodic review of principal transaction pricing into their supervisory procedures, since the "reasonably related to the market" standard under paragraph (d) creates an independent basis for scrutiny separate from timing compliance altogether. A firm that has never received a late-trade flag can still face a Rule 6622 inquiry if its principal transaction pricing consistently diverges from contemporaneous quoted markets, which is why pricing supervision deserves its own dedicated line item in a firm's written supervisory procedures rather than being folded silently into general trade reporting oversight.