FINRA Rule 7140

The Two Matching Methods

The ADF supports two distinct methods for determining a locked-in trade. Under trade acceptance and comparison, the Reporting Party enters its version of the trade into the System, and the contra party then reviews that submission and either accepts or declines it. 

An acceptance results in a locked-in trade. Under trade-by-trade match, by contrast, both parties to the trade independently submit their own version of the transaction data, and the System itself performs an online comparison, locking in the trade once both submissions match. 

FINRA's own guidance, issued through a Trade Reporting Notice dated October 7, 2016, formally distinguished these two methods using the terms "Trade Acceptance" and "Trade Match," and confirmed that member firms electing to have the ADF submit their locked-in trades to the National Securities Clearing Corporation for clearance and settlement may use either method, provided the trade is genuinely locked in, whether through mutual party agreement or through the System's own processing.

Declined Trades: A Meaningful Change From Earlier Practice

Under Rule 7140, a declined trade report is carried over at the end of trade date processing and remains available in the System, though it is not subject to the automatic lock-in process described below. This represents a genuine change from the ADF's earlier operational practice under NASD Rule 6140A, which had provided that a declined trade report was simply purged from the TRACS system at the end of trade date processing, disappearing from the System entirely rather than remaining available for further action. 

FINRA revised this treatment through guidance issued in a Trade Reporting Notice dated July 11, 2014, and further described in Regulatory Notice 14-21, clarifying that trades declined by a contra party are no longer purged but instead remain available for cancellation or correction by the reporting party, or for subsequent acceptance by the contra party, up to T+1.

This change matters practically because it corrects for a genuine, foreseeable error scenario: a contra party might decline a trade report by mistake, perhaps due to a data entry error or a momentary system issue, and under the older purge-at-end-of-day approach, that error would have permanently eliminated the trade record, potentially leaving both parties needing to resolve the resulting discrepancy entirely outside the System through manual, off-system communication. 

Under the current framework, that same contra party can simply accept the previously declined trade the next day if it discovers the decline was erroneous, without needing to resubmit the transaction from scratch or coordinate an entirely separate off-system correction process. 

A declined trade must still be affirmatively cancelled by the Reporting Party under Rule 6282(g), however, if that trade was originally reported to the System for public dissemination purposes, since a merely declined but uncancelled trade could otherwise create ambiguity about whether it remains a genuine, disseminated last sale report.

The Automatic Lock-In Mechanism and Its 2024 Timing Change

Any trade that remains open, meaning unmatched or unaccepted, at the end of its entry day carries over for continued comparison and reconciliation on the following business day. The System will automatically lock in and submit to DTCC, as such, any carried-over trade ranging from trade date through T+21 calendar days, provided that trade remains open as of a specific cutoff time on the next business day. 

This cutoff time itself changed recently: FINRA amended Rule 7140(a)(3), along with the parallel provisions governing the FINRA/Nasdaq Trade Reporting Facility and the OTC Reporting Facility, to move the automatic lock-in submission time from 2:30 p.m. Eastern Time to noon Eastern Time, specifically to allow NSCC sufficient time to process the resulting trade under the market's shortened settlement cycle. 

This amendment, filed under SR-FINRA-2023-017 and described in Regulatory Notice 24-04, became operative May 28, 2024, the same date the SEC's broader transition from a two-business-day settlement cycle, T+2, to a one-business-day cycle, T+1, took effect under amended SEC Rule 15c6-1 and new Rule 15c6-2.

This same 2024 filing eliminated an entirely different mechanism that had existed alongside the automatic lock-in process: the "Next Day Trade" modifier previously required under Rules 6282(a)(4)(D), 6380A(a)(5)(D), 6380B(a)(5)(D), and 6622(a)(5)(D). Under the older T+2 settlement framework, a trade settling on a next-day basis was distinguishable enough from the standard settlement cycle to warrant its own specific modifier; once T+1 became the market's new standard settlement cycle, what previously would have been flagged as a distinct "Next Day Trade" simply became the ordinary, default Regular Way Trade, making the special modifier unnecessary and redundant. FINRA deleted this modifier requirement as part of the same broader T+1 conformance package that adjusted Rule 7140's automatic lock-in timing.

Trades older than T+21 calendar days follow a different path: the System will carry over any T+22 or older "as/of" trade that remains open, but such a trade is not subject to the automatic lock-in process at all, meaning the parties themselves must take affirmative action to resolve it rather than relying on the System's automated mechanism. T+N, or "as/of," entries may be submitted until 6:30 p.m. Eastern Time each business day, and the System imposes hard outer limits on what it will ever submit to clearing: "as/of" reports of trades executed on non-business days, and any T+365 or greater trade, will never be submitted to clearing by the System under any circumstance, regardless of how long the trade remains open or carried over.

The 2016 Disablement of Automatic Lock-In on the ADF

A genuinely significant, and easily overlooked, operational fact concerns how the ADF's automatic lock-in functionality actually operates today relative to what the rule's plain text might suggest. FINRA's October 7, 2016 Trade Reporting Notice, alongside industry commentary describing that notice, confirmed that FINRA disabled the ADF's automatic lock-in functionality entirely, effective October 24, 2016. Practically, this means a Participant submitting a Trade Match or Trade Acceptance transaction on the ADF needs to identify a genuine ADF participant, one with actual access to the ADF and the ability to view and act on the reporting party's submission, since the System itself no longer forces an automatic lock-in the way the underlying rule text describing the T-to-T+21 mechanism might suggest in isolation.

This has a direct, meaningful liability consequence firms should understand precisely. Under the FINRA Participation Agreement every ADF participant executes, a reporting party that submits a trade to the ADF for Trade Match or Trade Acceptance processing against a counterparty that turns out not to be an actual ADF participant accepts any and all potential liability resulting from that non-participant's failure to honor the trade. Because the ADF system itself does not prevent a firm from entering a trade against a party that is not genuinely an ADF participant, a reporting firm bears real, direct exposure if it submits a trade against a counterparty it has not properly confirmed is an actual, currently active ADF participant. FINRA maintains a published list of current ADF participants specifically so firms can verify counterparty status before relying on this functionality.

A Worked Example Bringing These Elements Together

Consider a Participant that submits a Trade Acceptance report on the ADF on a Tuesday, identifying a specific contra party. If that contra party is not, in fact, a genuine, currently active ADF participant, perhaps because its participation lapsed or it never completed the necessary onboarding, the System will not itself prevent the reporting Participant from submitting the trade against that counterparty, since the automatic verification and lock-in functionality that once might have caught this issue has been disabled since October 2016. Under the FINRA Participation Agreement, the reporting Participant bears the resulting liability if that non-participant counterparty fails to honor the trade, a consequence the reporting firm assumes by virtue of having submitted the trade without first confirming genuine participant status.

Suppose instead that the counterparty genuinely is an active ADF participant, but mistakenly declines the trade report due to an internal data entry error on its own end. Under the current rule, this declined trade is not purged; it remains available in the System, and the contra party can accept the previously declined trade up to T+1 once it discovers its own error, without requiring the reporting party to resubmit the transaction from scratch. If the trade remains genuinely unresolved, neither accepted nor properly cancelled, it carries forward as an open trade, and the System will automatically lock it in and submit it to DTCC if it remains open as of noon Eastern Time on the following business day, provided the trade falls within the T+21 calendar day window; beyond that window, the trade continues carrying over but no longer benefits from this automatic lock-in safety net, placing the burden squarely on the parties themselves to resolve it directly.

This sequence illustrates why firms need genuine operational fluency with each of these interacting mechanisms rather than a surface-level understanding of any single piece in isolation, since a real-world trade reporting scenario can move through several of these distinct rules and thresholds in succession, with the ultimate outcome, and the allocation of any resulting liability, depending on precisely which mechanism actually applies at each stage.

Relevance Across FINRA's Examination Programs

The SIE, Series 63, and Series 65 do not test Rule 7140's processing mechanics, since these exams do not reach into facility-level trade matching and clearance timing at this level of technical detail. Series 7 candidates should understand conceptually that submitted trade reports must be matched or accepted before becoming genuinely locked in for clearance, reinforcing broader awareness of how OTC trade processing functions, without needing command of the rule's specific timing thresholds.

Series 24 candidates supervising a firm's ADF trading relationships need precise, current understanding of the 2016 automatic lock-in disablement and its liability consequences, since a principal's supervisory procedures should specifically address how the firm verifies counterparty ADF participation status before relying on Trade Match or Trade Acceptance functionality, given the direct liability exposure a reporting firm assumes under the FINRA Participation Agreement for trades against non-participants. A principal should also understand the current noon Eastern Time automatic lock-in cutoff, and the T+21 versus T+22-and-older distinction, precisely enough to correctly interpret the firm's own trade reporting exception reports. Series 57 candidates handling actual trade submission need working fluency with the distinction between Trade Match and Trade Acceptance, and should understand that declined trades remain available for correction up to T+1 rather than disappearing permanently, since a trader who mistakenly assumes an erroneous decline is unrecoverable might unnecessarily resubmit an entire transaction rather than simply accepting the already-declined trade the following day.

Practical Guidance for Firms

Firms relying on the ADF's Trade Match or Trade Acceptance functionality should build a specific, mandatory counterparty verification step into their trade reporting workflow, confirming against FINRA's current published participant list that a given counterparty is genuinely an active ADF participant before submitting a trade against it, given the direct liability a reporting firm assumes under the FINRA Participation Agreement for trades against non-participants. Given that the System itself will not prevent this kind of submission error, this verification step functions as the firm's own primary safeguard against exactly the liability exposure this 2016 change created.

Firms should also update any internal training materials or documentation still describing the ADF's automatic lock-in process as a fully self-executing mechanism firms can rely on without independent verification, ensuring staff correctly understand that this automatic functionality has not operated on the ADF since October 2016, notwithstanding language in the underlying rule text that might otherwise suggest an automated process functioning without any need for the firm's own counterparty diligence.

Firms should build the T+1 settlement cycle's impact on the automatic lock-in cutoff time, and the corresponding elimination of the Next Day Trade modifier, into their operational documentation as a genuine, dated change firms needed to implement by May 28, 2024, rather than treating it as a minor technical adjustment. A firm's own compliance calendar and system documentation should reflect the current noon Eastern Time cutoff accurately, since continuing to operate under an assumption of the prior 2:30 p.m. cutoff risks a mismatch between a firm's own internal processing expectations and how the System actually now operates.

Firms should also train trade reporting and operations staff specifically on the distinction between a declined trade that remains available for correction and an unmatched, open trade that carries forward toward possible automatic lock-in, since these are genuinely different states within the System carrying different practical consequences and different available remedies. Staff who conflate these two categories risk either taking unnecessary corrective action on a trade that would have resolved itself through the automatic lock-in process, or failing to take timely action on a declined trade that genuinely requires the contra party's affirmative acceptance before it can move forward toward settlement.

Firms with any meaningful ongoing reliance on ADF Trade Match or Trade Acceptance functionality should periodically audit their own counterparty verification practices against FINRA's current published participant list, treating this as a recurring compliance control rather than a one-time check performed only when a new trading relationship is first established. Given that a counterparty's ADF participation status can change over time, a firm relying on outdated verification performed only at the outset of a relationship risks unknowingly submitting trades against a counterparty whose participation has since lapsed, precisely the scenario in which the reporting firm's own liability exposure under the FINRA Participation Agreement becomes most acute.