FINRA Rule 6720

Rule 6720 traces directly to former NASD Rule 6220, which served the identical function under the original NASD Rule 6200 Series before the 2008 Consolidated FINRA Rulebook initiative renumbered it as part of that broader rulebook reorganization effort. The core mandatory-participation language has remained substantively unchanged across that renumbering, though FINRA added a significant new requirement in 2014 addressing how alternative trading systems must identify themselves when reporting to TRACE, discussed in detail below.

The Core Participation Requirements

Participation in TRACE is conditioned on a TRACE Participant's initial and continuing compliance with two baseline requirements. First, a TRACE Participant must execute, and continue to comply with, a TRACE Participant application agreement together with all applicable rules and operating procedures of FINRA and the SEC. Second, a TRACE Participant must maintain the physical security of the equipment located on its premises to prevent unauthorized entry of information into TRACE, a requirement paralleling the identical physical security obligation found across FINRA's other trade reporting facility rules, including the ADF and the OTC Reporting Facility.

Each TRACE Participant is separately obligated to inform FINRA of any non-compliance with, or changes to, these participation requirements. This ongoing disclosure obligation means a firm cannot simply execute the application agreement once and consider its Rule 6720 obligations satisfied indefinitely; a material change to the firm's circumstances, such as a lapse in the physical security protocols the firm originally certified, must be affirmatively reported to FINRA rather than left for FINRA to discover independently. Upon execution and FINRA's receipt of the TRACE Participant application agreement, a TRACE Participant may commence input of trade information in TRACE-Eligible Securities, accessing the service through a FINRA-approved facility during TRACE System Hours.

The Application Agreement in Practice

The practical mechanism firms use to satisfy the application agreement requirement is the FINRA Transparency Services Participation Agreement, a single form covering access to multiple FINRA trade reporting facilities, including the ADF, the ORF, and TRACE. A firm completing this agreement indicates the specific facility or facilities it intends to report to, its clearing number where required by the relevant facility, and the contacts associated with its participation. Once FINRA's Market Operations group has processed a submitted agreement, it cannot be modified directly; any subsequent correction or change requires the firm to submit an entirely new participation agreement rather than amending the original.

This single-form, multi-facility structure reflects FINRA's broader effort to streamline participant onboarding across its various trade reporting facilities rather than requiring a firm to execute entirely separate, facility-specific agreements for the ADF, the ORF, and TRACE individually. A firm expanding its trading activity from equities into TRACE-eligible debt securities, or vice versa, typically extends its existing participation agreement to cover the additional facility rather than starting the onboarding process from scratch. This efficiency matters most for smaller and mid-sized firms without dedicated onboarding staff, since consolidating the administrative burden of facility access into a single recurring form reduces the operational friction of expanding into a new asset class or trading venue.

The 2014 Alternative Trading System MPID Requirement

The most significant substantive amendment to Rule 6720 since the 2008 consolidation addressed how alternative trading systems identify themselves when reporting to TRACE. The SEC approved this change on January 17, 2014, alongside a related but separate amendment adopting new Rule 4552, which required ATSs to report weekly volume information to FINRA. Under the Rule 6720 amendment, described in Regulatory Notice 14-07, a TRACE Participant that operates an ATS, as defined in Rule 300 of SEC Regulation ATS, must obtain a single, unique Market Participant Identifier designated for exclusive use in reporting that specific ATS's transactions to TRACE.

This MPID requirement carries several important operational restrictions. A firm cannot use multiple MPIDs for a single ATS, and the designated MPID may not be used to report any transaction that was not actually executed within that ATS. A firm operating multiple ATSs must obtain a separate, dedicated MPID for each one, meaning a firm running two distinct ATS platforms cannot consolidate their TRACE reporting under a shared identifier even if both platforms are operated by the same legal entity. Firms must also notify FINRA before changing the usage of an MPID in any way, including repurposing an MPID that previously reflected ATS activity to instead cover a different line of business at the firm.

The implementation timeline for this requirement shifted after its initial adoption. The ATS weekly volume reporting requirement under new Rule 4552 took effect May 12, 2014, with the first reports due by May 28, 2014. The MPID requirement itself was originally set to take effect November 10, 2014, but FINRA filed a rule change on October 2, 2014, postponing that implementation date to February 2, 2015, giving firms additional time to obtain and configure the required dedicated MPIDs before the obligation became operative.

The Limited Exception for Dual MPID Use

Rule 6720(c)(2) provides a narrow exception to the single-MPID rule: an ATS is permitted to use two separate MPIDs, but only where one MPID is used exclusively for reporting transactions to TRACE and the other is used exclusively for reporting transactions to the equity trade reporting facilities, meaning the ADF, the ORF, the FINRA/Nasdaq TRF, or the FINRA/NYSE TRF. This accommodates an ATS that handles both TRACE-eligible debt securities and equity securities within the same platform, allowing it to maintain distinct identifiers for each asset class's separate reporting infrastructure rather than forcing an artificial single-MPID structure across fundamentally different reporting facilities.

Connection to Rules 6730 and 6732

The MPID an ATS obtains under Rule 6720(c) is not a standalone administrative requirement; it becomes directly operative in other TRACE rules. Rule 6730(c)(13) requires a member reporting a transaction that occurred on an ATS pursuant to the Rule 6732 exemption to include that ATS's separate MPID, obtained in compliance with Rule 6720(c), as part of the trade report's content. Similarly, when FINRA expanded the Rule 6732 exemption's scope in 2022 to cover transactions involving only one FINRA member, described in Regulatory Notice 22-13, the amended rule continued to require that an exempted ATS's identity be reported using precisely the same Rule 6720(c) MPID, and that the ATS enter into a written agreement, rather than rely on a negative consent letter, with each member that is or may be a Party to an exempt transaction.

This layering illustrates how Rule 6720's participation and identification infrastructure functions as a foundational requirement that other, more substantively focused TRACE rules build directly upon. A firm that fails to properly obtain or maintain its Rule 6720(c) MPID is not merely at risk of a standalone Rule 6720 violation; it risks being unable to correctly comply with the reporting content requirements of Rule 6730 or to properly avail itself of an exemption under Rule 6732, since both of those rules depend on the MPID infrastructure Rule 6720 establishes.

The Physical Security Requirement in Context

The physical security obligation under Rule 6720(a)(2)(B) is easy to overlook given how much attention the 2014 MPID amendments have since attracted, but it remains an independently operative condition of TRACE participation. This requirement traces back to an earlier era of market infrastructure when direct physical access to reporting terminals posed a more significant risk of unauthorized data entry than it typically does today, yet FINRA has never removed or substantially modernized this language despite the shift toward encrypted, credentialed electronic access across virtually all TRACE connectivity methods.

Firms should not assume that modern network security controls automatically satisfy this specific rule text, since Rule 6720(a)(2)(B) speaks specifically to physical security of equipment on a Participant's premises rather than to cybersecurity controls generally. A firm's TRACE participation compliance program should treat this as a distinct, if narrower, requirement from the broader information security obligations a firm maintains under Regulation S-P, FINRA's cybersecurity guidance, and its own internal data governance policies, even though in practice a well-designed physical and information security program will typically satisfy both sets of obligations simultaneously.

Consequences of Non-Compliance

Rule 6720 does not itself specify a standalone penalty provision the way some FINRA rules do; instead, a firm's failure to maintain the participation requirements set out in this rule exposes it to FINRA's general enforcement authority, including potential termination of TRACE service under Rule 6740 and broader disciplinary action for conduct inconsistent with FINRA's rules and procedures. A firm that fails to notify FINRA of a material change to its participation circumstances, as required under Rule 6720(a)(3), compounds a single underlying compliance gap into an additional, independent disclosure failure, since the obligation to inform FINRA exists separately from whatever the underlying non-compliance happens to be.

This layered exposure is particularly relevant to the MPID requirements discussed above. A firm that discovers it has been using an ATS's dedicated MPID to report non-ATS transactions, whether through a technology error or an internal misunderstanding of the restriction, faces two distinct issues: the underlying MPID misuse itself, and a separate question of whether the firm promptly notified FINRA once it discovered the error, as Rule 6720(a)(3) requires. Firms that self-identify and promptly disclose this kind of issue are generally viewed more favorably than firms where FINRA independently discovers a long-standing, undisclosed MPID misuse pattern during a routine examination.

Series 7 and SIE Relevance

The SIE and Series 7 do not test Rule 6720's participation mechanics, since these exams do not address the operational infrastructure underlying FINRA's fixed income trade reporting facilities. Series 7 candidates should understand conceptually that FINRA membership carries mandatory reporting obligations for debt securities transactions, reinforcing broader awareness of the regulatory framework surrounding fixed income trading, but are not expected to know the specific MPID requirements or application agreement mechanics.

Series 63 and Series 65 Relevance

Series 63 and Series 65 candidates do not need this rule at any operative level. These exams address state securities registration and investment adviser fiduciary obligations rather than FINRA's facility participation infrastructure, and candidates preparing for either exam can disregard Rule 6720 entirely.

Series 24 Relevance

Series 24 candidates supervising a firm that operates an ATS handling TRACE-eligible securities should understand Rule 6720's MPID requirements as a foundational compliance obligation with direct consequences for the firm's ability to correctly report under Rules 6730 and 6732. A principal should ensure the firm has properly obtained a dedicated MPID for each ATS it operates, has not inadvertently used an ATS-designated MPID to report non-ATS transactions, and has promptly notified FINRA of any change in how an existing MPID is being used.

Series 24 candidates should also understand the practical mechanics of the FINRA Transparency Services Participation Agreement, since a principal overseeing a firm's onboarding to a new FINRA facility, or a change in the firm's clearing arrangements, needs to know that a previously processed agreement cannot simply be edited; a new agreement must be submitted, and any errors in a pending submission must be corrected before FINRA processes it, since a processed agreement becomes effectively locked.

Series 57 Relevance

Series 57 candidates working at firms that operate an ATS handling TRACE-eligible securities should know precisely when the dual-MPID exception under Rule 6720(c)(2) applies: only where one MPID is dedicated exclusively to TRACE reporting and a separate MPID is dedicated exclusively to equity trade reporting facility reporting, never as a general-purpose accommodation for using multiple MPIDs on a single ATS handling only TRACE-eligible securities. Series 57 candidates should also be able to trace how a Rule 6720(c) MPID becomes operative in an actual trade report under Rule 6730(c)(13), correctly including the ATS's designated MPID when reporting a transaction that occurred on an ATS relying on the Rule 6732 exemption.

Relevance to Working Financial Services Professionals

For compliance officers at firms operating one or more alternative trading systems, Rule 6720's MPID requirements demand careful, ongoing administrative discipline rather than a one-time setup exercise. A firm that later repurposes an ATS's dedicated MPID for a different trading desk without first notifying FINRA, even inadvertently through a technology migration or platform consolidation, creates a compliance gap that can affect not just Rule 6720 itself but the accuracy of every downstream trade report that relies on correctly identifying which trades occurred within that specific ATS.

Firms undergoing any kind of platform consolidation, merger integration, or ATS restructuring should specifically audit their MPID usage against Rule 6720(c)'s requirements before completing the transition, since combining previously separate ATS platforms under a single technology stack can easily result in inadvertent MPID misuse if the underlying reporting logic is not carefully reconfigured to preserve the one-MPID-per-ATS structure the rule requires. Firms should also recognize that the FINRA Transparency Services Participation Agreement's inability to be directly amended once processed means administrative accuracy at the time of submission matters considerably; a firm should verify all facility elections, clearing numbers, and contact information carefully before submitting, since correcting even a minor error afterward requires a full new submission rather than a simple update.

Firms operating large Treasury-focused ATSs should also be aware that FINRA has continued to build additional identification requirements on top of the Rule 6720 MPID framework as TRACE's scope has expanded. Supplementary Material to Rule 6730 now requires a "covered ATS," defined as an ATS executing $10 billion or more in monthly par value of U.S. Treasury Security transactions against non-FINRA member subscribers for any two months in the preceding calendar quarter, to provide FINRA with a list of its non-FINRA member subscribers and obtain a separate MPID for each one, extending the same identification philosophy Rule 6720 established for the ATS itself down to the level of individual non-member subscribers on sufficiently large Treasury platforms.

Firms should treat this trajectory as instructive for planning purposes: FINRA has repeatedly shown a willingness to extend the same core identification logic first established in Rule 6720, a dedicated, exclusively-used identifier tied to a specific trading venue or counterparty relationship, into new corners of the TRACE framework as market structure and trading volumes evolve. A firm building internal systems around today's Rule 6720 requirements should design that infrastructure with enough flexibility to accommodate similar identification requirements FINRA may introduce for other categories of participant or venue in the future, rather than treating the current MPID rules as a fixed, final state of the reporting infrastructure. Firms that build rigid, narrowly scoped MPID management systems tied only to today's specific rule text often find themselves undertaking costly technology rework when FINRA subsequently extends the same underlying identification philosophy to a new category of market participant.