FINRA Rule 7340

The second is trade acceptance, where the Reporting Party enters its version of the trade into the System and the contra party reviews the trade report before accepting or declining it; an acceptance results in a locked-in trade. 

This dual-method structure gives ORF Participants meaningfully more flexibility in how a given trade actually reaches locked-in status than a Participant using the FINRA/NYSE Trade Reporting Facility would have, since that facility requires lock-in to be achieved entirely outside the System before submission, without any equivalent internal matching or acceptance mechanism available to fall back on.

A declined trade report under the trade acceptance method is carried over at the end of trade date processing and remains in the System, but is not subject to the automatic lock-in process described below. If the declined trade was originally reported to the System for dissemination purposes, the Reporting Party must affirmatively cancel it pursuant to Rule 6622(f). 

This obligation prevents a declined, disputed trade from lingering indefinitely in a state that could confuse the System's records or FINRA's audit trail, requiring the party that originated the report to take responsibility for formally closing it out once the contra party has declined to accept it, rather than leaving that closure to happen passively or by default.

Carryover, Automatic Lock-In, and the Declined Trade Exception

Any trade that remains open, meaning unmatched or unaccepted, at the end of its entry day is carried over for continued comparison and reconciliation rather than being purged from the System outright. The System will automatically lock in and submit to DTCC any carried-over T through T+21 calendar day trade that remains open as of noon Eastern Time, a specific cutoff time that Participants need to track closely if they are relying on the System's automatic lock-in mechanism to resolve a trade that did not match or was not accepted on its original entry day. 

This noon cutoff is itself a distinguishing operational detail worth committing to memory, since it differs from the afternoon cutoffs governing equivalent carryover mechanics at other FINRA facilities, and a firm's internal monitoring should be calibrated to this specific timing rather than assumed to align with cutoffs used elsewhere.

This carryover and automatic lock-in structure closely mirrors the equivalent mechanics found in Rule 7240A governing the FINRA/Nasdaq Trade Reporting Facility, reinforcing that the ORF belongs functionally within the same comparison-enabled category as that facility rather than within the FINRA/NYSE Trade Reporting Facility's lock-in-only category. 

Firms that have already built operational familiarity with Rule 7240A's carryover mechanics, including the distinction between a merely open trade eligible for automatic lock-in and a declined trade excluded from that process, can extend much of that same operational understanding to ORF processing under Rule 7340, adjusting only for the ORF's own specific cutoff time and the underlying security population Rule 7310 places within its jurisdiction, a comparatively light lift given how closely the two rules otherwise track one another.

Trades That Age Beyond the Automatic Lock-In Window

The T to T+21 calendar day window governing automatic lock-in is itself a meaningful boundary, and Participants should not assume that a trade aging beyond this window simply continues indefinitely in an open, unresolved state within the System. 

Once a carried-over trade ages past the point where automatic lock-in remains available, it falls outside the mechanism Rule 7340 describes for resolving open trades without further action from the parties, meaning firms with trades that have not matched or been accepted well before reaching this outer boundary need to treat the aging trade as an active operational problem requiring direct resolution between the parties, rather than something the System will eventually resolve on its own regardless of how long it remains unmatched.

This design reflects a broader principle that recurs across FINRA's trade reporting facility rules: automatic processing mechanisms exist to handle routine timing gaps and momentary comparison delays, not to serve as a substitute for genuine trade confirmation between counterparties over an extended period. 

A firm that discovers a pattern of trades regularly approaching or exceeding the automatic lock-in window should treat that pattern as a signal of an underlying operational weakness in its trade confirmation process with particular counterparties, warranting direct outreach and process improvement rather than continued reliance on the System's carryover mechanics to eventually resolve the backlog, since the rule provides no guarantee that such resolution will actually occur without deliberate intervention by the parties themselves.

Why the ORF Retained Full Comparison Functionality

The ORF's retention of genuine trade-by-trade matching and trade acceptance functionality, in contrast to the FINRA/NYSE Trade Reporting Facility's lock-in-only design, reflects the different transactional environment each facility was built to serve. OTC Equity Securities and Restricted Equity Securities transactions often involve counterparties without the kind of pre-established give-up agreement infrastructure common among firms regularly executing exchange-listed trades through the FINRA/NYSE Trade Reporting Facility. 

Requiring lock-in to be achieved entirely outside the System before submission, the model Rule 7240B imposes, would place a heavier operational burden on ORF Participants than the underlying market structure generally supports, particularly for firms trading lower-tier OTC names on a less frequent or less systematic basis than firms active in the more liquid, exchange-listed segment of the market.

By retaining internal comparison functionality, Rule 7340 allows ORF Participants to achieve lock-in through the System itself when a pre-existing give-up arrangement is unavailable or impractical for a given counterparty relationship. 

This flexibility comes at the cost of additional processing complexity, the carryover, automatic lock-in, and declined trade cancellation mechanics discussed above, but that added complexity reflects a deliberate tradeoff FINRA made in designing the ORF around the actual needs of the market it serves, rather than importing a simpler processing model that would have fit that market poorly, and firms should recognize this tradeoff as intentional rather than as an unnecessary complication to be engineered around.

Comparison Functionality and Its NSCC Clearance Limitation

The full trade-by-trade matching and trade acceptance functionality Rule 7340 describes is not available for every transaction the ORF processes. As discussed in connection with Rule 7310's definitions, the ORF's comparison function is unavailable for OTC Equity Securities and Restricted Equity Securities that are not eligible for clearance and settlement through the facilities of the National Securities Clearing Corporation, even though the facility still supports entry and dissemination of last sale data for those securities. 

Rule 7340's matching and processing mechanics, in other words, apply fully only to the subset of ORF-reportable transactions that clear through NSCC; transactions outside that subset still get reported and disseminated, but without the benefit of the System's comparison and automatic lock-in functionality this rule otherwise describes.

This limitation reinforces a point worth repeating precisely because it is easy to lose track of across the several rules that touch on it: the ORF is neither uniformly comparison-enabled like the FINRA/Nasdaq Trade Reporting Facility nor uniformly lock-in-only like the FINRA/NYSE Trade Reporting Facility. Firms need to track, at the individual security level, whether a given OTC Equity Security or Restricted Equity Security actually qualifies for NSCC clearance before assuming Rule 7340's matching and automatic lock-in mechanics will apply to trades in that security, since assuming uniform treatment across the ORF's full security population would lead to incorrect operational expectations for a meaningful share of ORF-reported activity, and that mistaken expectation is precisely the kind of gap a careful onboarding process should be designed to close.

Regulatory History and Rulebook Placement

Rule 7340 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. 

Its carryover and automatic lock-in provisions have been amended periodically since, including through Regulatory Notice 24-04's elimination of the Next Day Trade modifier requirement previously cross-referenced in the parallel provisions governing the ADF, both FINRA/Nasdaq Trade Reporting Facilities, and the ORF together, illustrating FINRA's continued practice of amending Rule 7140, Rule 7240A, and Rule 7340 as a coordinated set even though each governs a distinct facility. 

This coordinated amendment pattern is itself informative: FINRA treats these three comparison-enabled facilities as sharing a common processing architecture worth maintaining in parallel, even while each retains its own facility-specific participant base and jurisdictional scope.

The rule sits between Rule 7330, Trade Report Input, and Rule 7350, Obligation to Honor Trades, occupying the same structural position that Rule 7240A occupies within the Rule 7200A Series. 

Unlike Rule 7240B, which sits in the analogous position within the Rule 7200B Series but describes an almost entirely different processing model, Rule 7340's placement and substance both track Rule 7240A closely, reflecting the ORF's shared comparison-enabled architecture with the FINRA/Nasdaq Trade Reporting Facility rather than the FINRA/NYSE Trade Reporting Facility's lock-in-only design, a pairing worth keeping firmly in mind whenever these three rules come up together.

Examination Relevance Across the FINRA Exam Suite

Series 24 candidates should understand both matching methods Rule 7340 describes, trade-by-trade matching and trade acceptance, along with the specific noon Eastern Time cutoff governing automatic lock-in of carried-over trades. 

A General Securities Principal supervising ORF trade reporting also needs to understand the NSCC clearance limitation on comparison functionality well enough to ensure supervisory procedures do not assume uniform matching behavior across every security the firm reports through the ORF, and should be prepared to explain why the ORF's processing model resembles Rule 7240A's rather than Rule 7240B's despite all three governing facilities that exist within the broader family of FINRA trade reporting rules.

SIE candidates should retain the general principle that the ORF, unlike the FINRA/NYSE Trade Reporting Facility, provides genuine trade comparison functionality, without needing to master the specific cutoff times or matching methods in detail. Series 7 candidates have limited direct exposure to Rule 7340's mechanics, since trade processing operates at the operations and systems level rather than the individual representative level. Series 63 and Series 65 candidates will not encounter Rule 7340 on either exam, as both are oriented toward state securities law and investment adviser regulation rather than FINRA facility-level trade processing mechanics.

Professional and Industry Relevance for Working Practitioners

For operations teams managing ORF connectivity, Rule 7340's dual matching methods give firms genuine operational choice not available at the FINRA/NYSE Trade Reporting Facility, and firms should evaluate which method, trade-by-trade matching or trade acceptance, better fits their own counterparty relationships and technology capabilities rather than defaulting to whichever method happens to be easiest to implement initially. 

Firms relying on the trade acceptance method in particular need robust internal processes for identifying and promptly cancelling declined trades that were originally reported for dissemination, since Rule 6622(f) places that cancellation obligation squarely on the Reporting Party rather than leaving it to resolve itself automatically, and a firm that lets declined trades linger uncancelled risks accumulating exactly the kind of stale, ambiguous System records this obligation is designed to prevent.

For compliance and operations personnel reconciling ORF trade activity, tracking the NSCC clearance status of the specific securities a firm regularly reports is a practical prerequisite to correctly interpreting the System's processing behavior for any given trade. 

A firm that discovers a trade behaving differently than expected, failing to match or lock in through the comparison process it anticipated, should check NSCC clearance eligibility for that security before assuming a system malfunction or an internal reporting error, since the absence of comparison functionality for non-NSCC-eligible securities is an expected and rule-based limitation rather than an anomaly.

Firms should also build monitoring specifically around trades approaching the outer edge of the T to T+21 automatic lock-in window, treating an aging open trade as an escalating operational priority rather than a static item that can wait indefinitely for eventual resolution. 

A dashboard or exception report flagging open trades by age relative to this window gives operations teams meaningful lead time to resolve a comparison dispute directly with a counterparty before the trade ages past the point where the System's own mechanics can help resolve it, reducing the risk that a stale, unresolved trade becomes a genuine audit trail or settlement problem later.

Firms should periodically test their own trade acceptance workflows against both realistic accept and realistic decline scenarios, rather than validating only the accept path during initial ORF onboarding. Because a declined trade triggers a distinct cancellation obligation under Rule 6622(f) that does not arise at all when a trade is simply accepted, a firm that has never exercised its decline-and-cancel workflow in practice risks discovering gaps in that process only when an actual dispute arises, at exactly the moment when a well-functioning process matters most.

Examination Relevance and Key Takeaways

Rule 7340 establishes the ORF's trade matching and lock-in mechanics, offering both trade-by-trade matching and trade acceptance methods that place the facility functionally alongside the FINRA/Nasdaq Trade Reporting Facility rather than the lock-in-only FINRA/NYSE Trade Reporting Facility. 

Trades remaining open at the end of their entry day carry over for continued reconciliation and are automatically locked in and submitted to DTCC if still open as of noon Eastern Time on a subsequent business day within the T to T+21 calendar day window, while declined trades are excluded from this automatic process and must be affirmatively cancelled by the Reporting Party where originally reported for dissemination. 

Trades aging beyond this window fall outside the automatic resolution mechanism entirely, requiring direct action between the parties rather than continued reliance on the System's carryover mechanics. This comparison functionality, however, applies fully only to ORF-reportable securities eligible for NSCC clearance, leaving a meaningful subset of ORF activity to proceed without the matching and automatic lock-in mechanics this rule otherwise describes.

Series 24 candidates and operations supervisors carry the greatest practical stake in mastering both matching methods and the NSCC clearance limitation, while SIE candidates need only the conceptual grasp that the ORF provides genuine comparison functionality distinct from the FINRA/NYSE Trade Reporting Facility's lock-in-only model. Series 7 candidates retain limited exposure, and Series 63 and Series 65 candidates can treat this rule as entirely outside their tested scope. 

For working operations professionals, tracking NSCC clearance eligibility at the individual security level, and monitoring open trades against the automatic lock-in window before they age past the point of automatic resolution, remain the two most reliable disciplines for managing this rule's obligations in practice, and building both into a single dashboard is the most efficient way to keep both disciplines consistently in view.