FINRA Rule 6732

That scope changed materially in 2022: FINRA filed SR-FINRA-2021-029 on November 15, 2021, the SEC approved it on January 12, 2022, and the amended rule took effect October 3, 2022 per Regulatory Notice 22-13, extending the exemption to transactions involving at least one FINRA member other than the ATS, opening it to arrangements between a member subscriber and a non-member counterparty such as a bank.

Why This Rule Exists at All

FINRA's own stated rationale for the original 2016 rule is worth understanding directly, since it explains the entire structure that follows. Members raised concerns that certain ATS models simply did not involve the platform in clearance and settlement, meaning a subscriber's own back-office systems, built to settle against the counterparty named on the trade report, were mismatched against a trade report that named the ATS instead. Rule 6732 resolved this by letting FINRA exempt a qualifying ATS from the ordinary reporting obligation, so that a subscriber could instead report directly against the actual counterparty it would clear and settle with.

The Conditions for Exemption

Since the 2022 expansion, FINRA staff may grant this exemption where a trade involves at least one FINRA member, other than the ATS itself, that satisfies the "Party to a Transaction" definition under Rule 6710(e). The trade cannot pass through any ATS account, and the ATS cannot exchange TRACE-Eligible Securities or funds on behalf of the subscribers, take either side of the trade for clearing or settlement purposes at DTC or elsewhere, or otherwise insert itself into the transaction in any capacity. The ATS must agree to provide FINRA, on a monthly basis or as FINRA otherwise prescribes, data covering each exempted trade occurring on its system, and failing to do so both violates FINRA's rules independently and automatically revokes any exemption already granted.

Two additional conditions distinguish this rule from Rule 6731. The ATS must remit to FINRA a transaction reporting fee, calculated under the fee schedule in Rule 7730(b)(1), for each exempted sell transaction occurring on its system, a per-transaction cost that Rule 6731 does not impose. The ATS must also enter into a written agreement with each member that is a Party to a Transaction on an exempted trade, specifying that the member itself must report the trade under Rule 6730(c)(13), identifying the trade as having occurred on the ATS using that ATS's own dedicated MPID obtained under Rule 6720(c). FINRA has been explicit on one particular point of practice here: a negative consent letter, informing a subscriber of the new reporting arrangement unless it objects, does not satisfy this written agreement requirement. The agreement has to reflect actual, affirmative consent from the member.

How This Changed the Dissemination Picture

The 2022 expansion carries a genuinely interesting dissemination consequence worth understanding on its own terms. Under FINRA's ordinary display conventions, a transaction between two FINRA members generates only one disseminated report, reflecting the sell side of the trade; a transaction between a member and a non-member, by contrast, generates dissemination of that specific transaction regardless of which side it represents. Before 2022, because Rule 6732 covered only member-to-member trades, an exempted transaction fit neatly within the member-to-member display convention. Extending the exemption to member-to-non-member transactions meant FINRA had to think through how dissemination would work once one side of an exempted trade was, by definition, not a FINRA member at all.

FINRA's answer preserves transparency rather than sacrificing it: even where the ATS itself is exempted from reporting, the member subscriber that is a Party to the Transaction still reports and FINRA still disseminates that report, meaning the market continues to see the trade even though the ATS never appears as the reporting party. FINRA characterized this as actually streamlining the process in one respect, since a single disseminated report now reflects the transaction rather than the two separate reports that might otherwise result from an ATS-as-counterparty structure. The underlying legal logic ties directly to Rule 6710(e)'s Party to a Transaction definition: an exemption is available at all only because the ATS itself is not a legal counterparty to the trade, so shifting the reporting obligation to the actual subscriber aligns the reporting party with the entity that is genuinely economically and legally on the hook for the transaction.

The Covered ATS Overlay for Large Treasury Platforms

Rule 6732 intersects with a separate, more recent requirement affecting the largest Treasury-focused ATSs. Where a transaction covered by this exemption involves a "covered ATS," a defined term tied to Supplementary Material .07 of Rule 6730 covering platforms executing very large monthly volumes of Treasury transactions against non-FINRA member subscribers, the ATS must provide the member subscriber with a FINRA-assigned identifier for each non-FINRA member subscriber, and that identifier must appear both in the member subscriber's TRACE report and in the ATS's own monthly transaction files submitted to FINRA. This overlay ensures that even as the largest Treasury ATSs rely on this exemption for operational relief, FINRA retains a specific, traceable identifier connecting each non-member subscriber to its actual trading activity, preventing the exemption from creating a gap in FINRA's ability to identify who is actually trading on these platforms.

Submission Mechanics

An ATS relying on this exemption reports its required monthly transaction information to FINRA through Secure File Transfer Protocol rather than through an ad hoc or manual submission process. A platform without an existing FTP account configured for this purpose must request one before it can begin submitting the required data, meaning firms considering this exemption should build the necessary technical account setup into their compliance timeline well before they expect FINRA to actually grant the exemption itself.

What Distinguishes This From Rule 6731 in Practice

The clearest way to separate these two exemptions is by asking what problem each one solves. Rule 6731 exists for platforms where trading itself is genuinely negotiated, non-automated, and conducted in a manner that makes attributing the trade to the ATS inappropriate from the moment of execution onward. Rule 6732 exists for platforms where execution may look entirely ordinary, but the ATS simply never touches clearance and settlement, creating a mismatch between the reported counterparty and the actual settling counterparty. A platform could, in principle, qualify for one exemption but not the other, depending on which underlying operational reality actually describes its business.

The fee and MPID-disclosure requirements unique to Rule 6732 also reflect this different underlying rationale. Because Rule 6732 exists specifically to accommodate a clearing and settlement mismatch rather than to recognize genuinely negotiated trading, FINRA built in a per-transaction fee and a more detailed identification framework, including the covered ATS overlay for large Treasury platforms, that Rule 6731 simply does not carry. A firm should not assume that satisfying one rule's criteria implies satisfying the other's, since the two exemptions were designed around different operational realities from the outset.

A Worked Example

Consider a Treasury-focused ATS where a FINRA member subscriber routinely trades against non-member banks that clear directly with the member rather than through the ATS itself. Absent this exemption, TRACE's ordinary rules would require a trade report naming the ATS as the counterparty, even though the member's own back-office systems are configured to settle against the actual bank counterparty, creating a persistent, avoidable mismatch every single trading day. Once FINRA grants this ATS a Rule 6732 exemption, the member subscriber instead reports the trade under Rule 6730(c)(13), naming the bank as its counterparty and identifying the ATS using that platform's dedicated MPID, precisely matching what its clearing systems already expect.

If that same ATS also qualifies as a "covered ATS" under Rule 6730's Supplementary Material .07 because of its Treasury trading volume against non-member subscribers, the picture gains one further layer: the ATS must supply the member subscriber with a FINRA-assigned identifier specific to that particular bank, and the member must include that identifier in its own TRACE report alongside the ATS's MPID. FINRA thereby preserves a granular, subscriber-level audit trail even though the day-to-day reporting burden has shifted away from the ATS itself. A firm evaluating whether its own ATS relationships might qualify for this exemption should walk through this exact chain, from the underlying clearing mismatch through the required written agreement to the specific identifiers a report must contain, rather than assuming eligibility from a surface-level read of the rule's criteria alone.

The Fee Obligation as an Ongoing Cost Center

The per-transaction fee Rule 6732 imposes deserves treatment as a genuine, recurring cost of maintaining this exemption rather than a one-time administrative charge. Every exempted sell transaction generates a fee obligation under the Rule 7730(b)(1) schedule, meaning an ATS with substantial trading volume relying on this exemption is committing to an ongoing expense proportional to that volume for as long as the exemption remains in force. This stands in direct contrast to Rule 6731, where no comparable per-transaction cost attaches to the ATS itself.

An ATS operator modeling the economics of seeking this exemption should treat the fee obligation as a permanent line item rather than a transitional cost that fades once the exemption is established. For a high-volume platform, this fee can represent a meaningful ongoing expense, and an ATS should weigh that recurring cost against the operational relief the exemption provides, particularly the elimination of the settlement mismatch problem that motivated the rule's creation in the first place. A platform with genuinely high trading volume and a persistent settlement mismatch problem will typically find the tradeoff worthwhile, but the calculation is not automatic, and a smaller platform facing only occasional mismatch issues may find the ongoing fee obligation outweighs the benefit of formal exemptive relief.

Relevance Across FINRA's Exam Programs

This rule sits well outside what the SIE, Series 63, and Series 65 test, since none of those three exams reaches facility-specific exemptive relief mechanisms for fixed income alternative trading systems. A Series 7 candidate gains only indirect value here, mostly in reinforcing a general sense that debt market infrastructure includes specialized reporting arrangements uncommon in the equity world tested more heavily elsewhere on that exam.

Anyone preparing for the Series 24 who might supervise a firm's ATS relationships should treat the distinction between this rule and Rule 6731 as a genuine, testable-in-practice judgment call rather than rote memorization: correctly identifying which exemption, if either, actually applies to a given platform depends on understanding whether the underlying issue is negotiated trading mechanics or a clearing and settlement mismatch. Someone working toward the Series 57 who trades on an ATS relying on this exemption needs the practical skill of recognizing, from the written agreement the ATS is required to maintain, exactly which counterparty they must name and which MPID they must reference when filing their own TRACE report, since getting either detail wrong produces a report that fails to match what the exemption actually requires.

Practical Considerations for ATS Operators and Subscribers

An ATS operator weighing whether to pursue this exemption should be candid with itself about which problem it is actually trying to solve, since conflating the two rationales can lead a platform to apply for the wrong exemption entirely or to build compliance infrastructure that doesn't match its actual operational needs. A platform whose subscribers routinely encounter settlement friction because their clearing arrangements do not match the ATS-as-counterparty structure of ordinary TRACE reporting is the paradigm case Rule 6732 was built for; a platform whose real issue is that trading is too negotiated and manual to fit standard automated reporting logic likely fits Rule 6731 better instead, or possibly neither rule depending on the specifics.

Subscribers relying on an ATS's Rule 6732 exemption should treat the written agreement the ATS is required to maintain as their primary reference document for correct reporting, checking it whenever there is any doubt about which counterparty to name or which MPID to reference on a given TRACE report. Given that FINRA has explicitly rejected negative consent as a substitute for genuine written agreement, a subscriber should confirm it has affirmatively executed, rather than merely received and not objected to, whatever documentation its ATS relies on to satisfy this condition, since a gap here could leave a subscriber uncertain whether it is actually covered by the exemption at all.

Firms should also build periodic reconciliation into their own compliance monitoring for any ATS relationship covered by this exemption, comparing the trades their own systems believe were executed on the exempted platform against the counterparty and MPID information actually appearing on their submitted TRACE reports, ideally on a recurring monthly or quarterly cadence rather than only in response to an external prompt. A mismatch discovered only during a FINRA examination, rather than through the firm's own ongoing review, suggests a systemic gap between how the firm's trading desk understands its ATS relationships and how its trade reporting function is actually implementing the exemption's requirements in practice. Given that the exemption's entire purpose is to align reported counterparties with actual clearing and settlement relationships, a firm that discovers persistent mismatches between the two has strong reason to suspect either a misunderstanding of the underlying written agreement or a technical implementation error in how its reporting systems are configured.

Firms should further recognize that an ATS's exemption status is not necessarily permanent, and a platform can lose its exemption through the automatic revocation mechanism if its monthly data reporting to FINRA lapses. A subscriber that has built its own reporting workflows around the assumption that a given ATS remains exempt should build in some mechanism for learning promptly if that status changes, since continuing to report as though an exemption remains in force after FINRA has actually revoked it would itself generate a new and entirely avoidable reporting error, layered on top of whatever originally caused the ATS to lose its exemption in the first place.