Exemption from Trade Reporting Obligation for Certain Alternative Trading Systems
FINRA Rule 6731 lets FINRA staff exempt a member alternative trading system from the ordinary TRACE trade reporting obligation under Rule 6730, but only for a specific, negotiated style of trading that looks quite different from the continuously matched, automated execution most people picture when they think of an ATS. FINRA adopted this rule through SR-FINRA-2012-016, giving debt market ATSs a reporting framework tailored to negotiated trading rather than forcing every ATS transaction into the same reporting posture as a fully automated match executed continuously against resting orders.
This rule sits alongside two close relatives elsewhere in the FINRA rulebook: Rule 6183, which provides the equivalent relief for the ADF and the two equity Trade Reporting Facilities, and Rule 6732, which provides a related but meaningfully broader exemption for a narrower category of TRACE-eligible ATS transactions. Understanding how these three rules diverge, despite sharing an obvious common ancestry, is arguably more useful for a compliance professional than memorizing any one of them in isolation, since real-world ATS platforms rarely fit neatly into just one of these three frameworks over their operating lifetime.
What the Exemption Actually Requires
FINRA staff, acting under the Rule 9600 Series and for good cause shown after weighing all relevant factors, may grant this exemption upon application, provided doing so is consistent with the protection of investors and the public interest. Four cumulative conditions must be satisfied before that happens. The trade must occur between ATS subscribers that are both FINRA members, a threshold eligibility requirement that immediately narrows this exemption's availability compared to Rule 6732's broader current scope.
The ATS's system must not permit automatic execution; a subscriber has to take an affirmative step beyond simply submitting an order before a trade is agreed with another subscriber, meaning the exemption exists for genuinely negotiated trading arrangements rather than algorithmically matched liquidity. The trade cannot pass through any ATS account, and the ATS cannot in any way hold itself out as a party to the trade. Beyond that, the ATS cannot exchange TRACE-Eligible Securities or funds on behalf of its subscribers, cannot take either side of the trade for clearing or settlement purposes, and cannot otherwise insert itself into the transaction in any capacity resembling a counterparty, a restriction FINRA drafted broadly enough to capture novel arrangements an ATS might attempt that technically avoid the specifically enumerated prohibited functions while still achieving the same practical effect of standing between the two subscribers.
The ATS and its subscribers must also put their arrangement in writing, expressly acknowledging that the ATS will not be treated as a party to the trade for reporting purposes and that reporting responsibility instead falls to whichever member subscriber satisfies the "Party to a Transaction" definition under Rule 6710(e). Finally, the ATS has to agree to give FINRA monthly volume data, broken out by security, reflecting the trading its subscribers conducted using its system; failing to provide that data is treated as an independent rule violation in its own right and results in automatic revocation of whatever exemption had been granted.
Where the Reporting Obligation Actually Lands
Once FINRA grants the exemption, paragraph (b) makes the consequence explicit: trades must be reported to FINRA under Rule 6730 by whichever member subscriber, as between the two parties, satisfies the Rule 6710(e) definition of Party to a Transaction. The ATS itself never assumes that reporting role under this rule, which is precisely the point of seeking the exemption in the first place, but the practical effect is that the reporting burden simply relocates to the subscribers rather than disappearing.
How Rule 6731 Differs From Rule 6732
The most consequential distinction between these two sibling rules concerns eligibility scope. Rule 6731 has never been expanded beyond its original two-FINRA-member requirement; both parties to an exempted trade must still be FINRA members today. Rule 6732, by contrast, was amended effective October 3, 2022, under SR-FINRA-2021-029, specifically to permit exemption applications for transactions involving only one FINRA member, opening the door to arrangements between a member subscriber and a non-member entity such as a bank, a participant type increasingly common in the Treasury and broader debt markets.
The two rules also diverge on fees. Rule 6732 requires the ATS itself to remit a transaction reporting fee to FINRA under Rule 7730(b)(1) for each exempted sell transaction, and requires the exempted trade to be identified using the ATS's own dedicated MPID obtained under Rule 6720(c). Rule 6731 carries no equivalent per-transaction fee obligation running through the ATS; its reporting relocates to the subscribers without a corresponding fee mechanism sitting at the platform level. A firm evaluating which exemption framework fits its trading model should treat this fee distinction as more than a technicality, since it changes who bears the ongoing cost of maintaining the exemption over time, and that cost allocation can matter considerably to a platform operating on thin margins across a high volume of otherwise small individual transactions.
The Underlying Market Structure Rationale
It helps to understand why FINRA built this specific carve-out rather than simply requiring every ATS to report every trade itself. Many debt market ATSs, particularly those handling less liquid corporate bonds or specialized instruments, function more as negotiation venues than as continuous, anonymous matching engines; two subscribers might use the platform to identify each other and begin a conversation, then finalize terms bilaterally rather than through automated matching. Forcing the ATS itself to report a trade it never actually executed, cleared, or settled would misattribute the transaction to an entity that played only a facilitative, introductory role, distorting the accuracy of TRACE's audit trail rather than improving it.
By instead requiring the actual transacting subscribers to report under Rule 6730, using the same Party to a Transaction framework that governs ordinary bilateral TRACE reporting, FINRA keeps the reporting obligation attached to the entities that genuinely negotiated and executed the trade. The monthly volume reporting FINRA still requires from the ATS preserves aggregate market transparency even though the ATS is relieved of transaction-by-transaction reporting duty. This structure reflects a broader theme across FINRA's approach to alternative trading systems generally: relief from a specific mechanical obligation is rarely absolute, and is instead typically paired with a substitute transparency mechanism designed to preserve FINRA's overall visibility into market activity even as individual reporting burdens shift between parties.
The Application Process Itself
Rule 6731's exemption is not granted automatically simply because an ATS's business model happens to fit the five criteria on paper. The rule operates through the Rule 9600 Series, FINRA's general exemptive relief framework, which requires a written application and gives FINRA staff genuine discretion rather than a mechanical approval process. An ATS satisfying every enumerated criterion is not guaranteed relief; staff evaluates the application for good cause shown, considering the totality of circumstances rather than treating the five conditions as a simple checklist to tick off.
This matters practically because an ATS preparing an application benefits from explaining, in its own words, why its trading model genuinely fits the negotiated-trading rationale underlying this exemption, rather than submitting a bare assertion that each criterion is technically met. FINRA staff reviewing an application wants to understand how subscribers actually interact on the platform, what affirmative steps beyond order submission subscribers must take to agree to a trade, and how the ATS's proposed monthly volume reporting will give FINRA meaningful ongoing visibility into the exempted activity. An application that reads as a template exercise, rather than a genuine account of the platform's mechanics, is more likely to generate follow-up questions or delay.
FINRA staff also retains authority to attach specific terms and conditions to any grant beyond the baseline criteria, tailoring relief to the particular ATS involved. Two platforms with superficially similar business models should not assume they will receive identical treatment or identical conditions; each application stands on its own facts, and a previously granted exemption for one ATS creates no binding precedent guaranteeing the same outcome for another, even where the two platforms appear to an outside observer to operate in materially indistinguishable ways.
Comparing All Three Sibling Exemptions Together
Placing Rule 6731 side by side with both Rule 6183 and Rule 6732 clarifies what genuinely varies across FINRA's three parallel ATS exemption frameworks, rather than leaving the comparison as a simple two-rule contrast. All three share the foundational architecture: application-based relief under the Rule 9600 Series, a requirement that trading be negotiated rather than automatically executed, a written acknowledgment shifting reporting duty to the subscribers, and continuing FINRA data-reporting obligations as a condition of keeping the exemption. Where they genuinely diverge is in eligibility scope and market-specific mechanics layered on top of that shared foundation.
Rule 6183 governs equity trading through the ADF and the two Trade Reporting Facilities and has historically included a requirement that member subscribers be fully disclosed to one another, a feature not explicitly carried into Rule 6731's text for the debt market context. Rule 6732 alone has been expanded to accommodate single-member transactions and alone carries a per-transaction fee remitted by the ATS itself. Rule 6731 sits in between conceptually: narrower than Rule 6732 in its eligibility requirements, since it has never dropped the two-member threshold, yet simpler than Rule 6732 in its absence of any ATS-level transaction fee. A firm operating across multiple asset classes, with ATS relationships touching equities, corporate debt, and instruments falling under the newer single-member exemption, needs to track three separate rule frameworks rather than assuming a single unified standard governs all of its exempted ATS activity.
The Monthly Volume Reporting Obligation in Practice
The monthly volume data condition deserves more attention than a passing mention, since it functions as the primary ongoing mechanism through which FINRA monitors an exempted ATS's continued eligibility. This is not a one-time disclosure made at the time of application; it is a recurring obligation that persists for as long as the exemption remains in effect, and FINRA has been explicit that a lapse in this reporting, even an inadvertent one, triggers automatic revocation rather than a warning or grace period.
An ATS relying on this exemption should build the monthly reporting process into its core operational infrastructure rather than treating it as a peripheral compliance task handled manually each month. A platform that experiences a data quality issue, a staffing gap, or a technology outage affecting its ability to compile and submit this volume data on schedule faces a genuinely severe consequence: the automatic loss of an exemption it may have spent considerable time and expense obtaining in the first place, with no explicit cure period built into the rule text itself. This asymmetry, a straightforward reporting lapse triggering an outsized loss of previously granted relief, is a compliance risk worth flagging prominently in any ATS's internal risk assessment.
Where This Fits for Exam Candidates
Candidates for the SIE, Series 63, and Series 65 will not encounter this rule in any meaningful way, since none of those three exams reaches into facility-specific exemptive relief for fixed income alternative trading systems. Series 7 candidates likewise face no direct testing here, though understanding that ATSs handling debt securities can operate under specialized reporting arrangements rounds out a broader picture of how fixed income market structure differs from equities.
A Series 24 candidate responsible for a firm that subscribes to, or operates, a debt-focused ATS gains real practical value from this rule, since correctly identifying whether a given transaction falls under an exempted ATS's arrangement, and therefore whose obligation it is to report that trade, is exactly the kind of judgment call a principal's supervisory procedures need to anticipate in advance rather than resolve after an examination finding turns up a gap. A Series 57 candidate working the trading side of that same relationship needs the mirror-image skill: recognizing, in the moment, whether their own firm has become the reporting party for a given trade executed on an exempted ATS, since assuming the platform handles reporting when it has, in fact, shifted that duty entirely to the subscribers is a genuine and recurring source of reporting gaps.
Practical Guidance for Firms and ATS Operators
An ATS operator considering whether to pursue this exemption, rather than the broader Rule 6732 exemption or no exemption at all, should think carefully and realistically about its actual subscriber base. If the platform's activity is limited to trades between two FINRA members, and involves no non-member counterparties, Rule 6731 remains a viable and arguably simpler path, since it avoids the per-transaction fee obligation Rule 6732 imposes. An ATS whose business increasingly involves bank counterparties or other non-member entities, however, will find Rule 6731 structurally unavailable regardless of how well it otherwise fits the platform's negotiated trading model, since the two-member requirement admits no exceptions.
Firms relying on subscriber status at an exempted ATS should build their own trade reporting supervisory procedures around the specific written agreement Rule 6731(a)(3) requires, confirming precisely which trades that agreement covers and verifying, on an ongoing basis, that the firm's own systems correctly flag those trades for Rule 6730 reporting rather than assuming the ATS has already handled it. Given that failing to report a trade the firm itself was obligated to report carries the same consequences as any other missed TRACE report, a subscriber's compliance program should treat participation in an exempted ATS as a trigger for heightened attention to reporting responsibility, not a reason to relax it.
Firms should also periodically confirm that the underlying facts supporting an ATS's exemption remain accurate over time, rather than treating a granted exemption as a permanently settled matter that never requires revisiting once obtained. An ATS that gradually introduces automated matching functionality into what was originally a purely negotiated platform, for example, may inadvertently invalidate the very foundation of its exemption without necessarily recognizing the significance of that change internally. Subscribers relying on the exemption's continued validity have a genuine interest in understanding whether the platform's underlying mechanics have shifted, since a subscriber's own reporting obligations depend entirely on the exemption remaining properly in force.
Legal and compliance teams advising an ATS on whether to seek this exemption in the first place should weigh the relief against its ongoing maintenance burden honestly rather than treating the exemption as a one-time administrative win. The monthly volume reporting requirement, the risk of automatic revocation for even an inadvertent lapse, and the need to maintain accurate, current written agreements with every subscriber whose trades fall under the exemption collectively represent a meaningful and continuing compliance workload. For an ATS with a genuinely negotiated, low-automation trading model and a stable, all-FINRA-member subscriber base, that workload is usually a worthwhile tradeoff against the alternative of reporting every transaction itself; for a platform whose business model or subscriber base is still evolving, the ongoing maintenance burden deserves careful, realistic consideration before committing to the application process at all.
