TRACE Reporting: The 15-Minute Clock for Corporate and Agency Bonds

The most recent Rule 6730 amendments now in force took effect on 8 June 2026 without the shorter reporting timeframe the SEC had approved in September 2024. The one-minute TRACE reporting limit was rescinded before it took effect, and the outer limit for TRACE reporting of corporate and agency bond trades stayed at 15 minutes after execution. What did change is narrower: clarified wording on reporting “as soon as practicable”, a “reasonable justification” factor in the late-reporting test, and an optional single report for allocations by firms that are both broker-dealers and investment advisers.

The 15-minute obligation has applied to corporate bonds since 1 July 2005 and to agency debt since 1 March 2010. Subject to the transaction exclusions and applicable ATS exemptions, each FINRA member that is a party to a reportable TRACE transaction must submit the required report to FINRA’s Trade Reporting and Compliance Engine. For a reportable transaction between two members, both members report their respective sides unless an applicable exemption modifies the reporting arrangement. FINRA uses the reports for surveillance and the audit trail and publishes most corporate and agency reports as soon as it receives them. The same rules also govern securitized products and U.S. Treasury securities on different clocks; the corporate and agency debt facility is the product described in FINRA’s TRAQS user guide v6.3 and its two FIX specifications.

Related reading: RTRS Reporting: Municipal Trades to the MSRB Within 15 Minutes

The legal basis for TRACE: FINRA’s Rule 6700 Series

TRACE reporting is a FINRA rule obligation. According to the TRAQS user guide, the SEC approved the original rules requiring FINRA members to report over-the-counter secondary market transactions in eligible fixed income securities on 23 January 2001; Rule 6730’s own amendment history shows it was adopted under rule filing SR-NASD-99-65 with effect from 1 July 2002. Later amendments came as rule filings with the SEC, numbered SR-NASD through 2006 and SR-FINRA from 2007; the three that shape current reporting were approved by Exchange Act release and their dates are given under changes below. The rules sit in the Rule 6700 Series:

• Rule 6710 (Definitions) sets the perimeter: “TRACE-Eligible Security”, “Party to a Transaction”, “Time of Execution”, “TRACE System Hours”, and the List or Fixed Offering Price and Takedown definitions that decide whether a primary market trade gets T+1.
• Rule 6720 (Participation in TRACE) makes participation mandatory for trade reporting, conditions it on a signed TRACE participant agreement, and requires each alternative trading system to hold a separate MPID for its TRACE reporting.
• Rule 6730 (Transaction Reporting) is the operative rule: who reports, the timeframes, the 15 items in each report, price, size and modifier conventions, the transactions that are not reported, and late-reporting compliance.
• Rules 6731 and 6732 set out exemptions from the reporting obligation for certain alternative trading systems and for certain transactions on an ATS.
• Rule 6750 governs dissemination, and Rule 6760 the notice a managing underwriter generally gives FINRA before the first trade in a new TRACE-eligible security.

Two points in the source documents need care. The TRAQS user guide still introduces a TRACE-eligible security in older terms (registered with the SEC, or issued under Section 4(2) and traded under Rule 144A, with agency debt flagged “effective March 1, 2010”). Rule 6710(a) defines it by issuer type: a U.S. dollar-denominated debt security of a U.S. or foreign private issuer (a restricted security only if sold under Rule 144A), of an Agency or government-sponsored enterprise, of the U.S. Treasury, or of a foreign sovereign. Where the two differ, the rule governs.

The second point is timing. FINRA’s online text of Rules 6710 and 6730 already shows the “Affiliate” definition and the affiliate principal transaction indicator as amended by SR-FINRA-2026-009, and each rule’s history carries the line “Amended by SR-FINRA-2026-009 eff. Aug. 2, 2027”. Until that date the mandatory indicator covers back-to-back trades with non-member affiliates only, so a desk procedure copied from today’s web text describes a requirement that becomes mandatory in August 2027.

Who must report to TRACE: every FINRA member that is a party to the trade

Rule 6730(a) places the obligation on “each member that is a Party to a Transaction” in a TRACE-eligible security. Rule 6710(e) defines a Party to a Transaction as an introducing broker-dealer, an executing broker-dealer or a customer, and counts a broker-dealer that is not a FINRA member as a customer. Rule 6730(b) then allocates the reports:

• Trade between two FINRA members: both members report, the buyer and the seller.
• Trade between a member and a non-member, including a customer: the member reports.

The hook is FINRA membership. A non-member counterparty, whether an institutional client, a non-member broker-dealer or a member’s non-member affiliate, has no TRACE obligation of its own; the member reports its side and identifies the contra as “C” for a customer or “A” for a non-member affiliate.

The security test does the rest. Rule 6710(a) covers U.S. dollar-denominated debt in four issuer categories: a U.S. or foreign private issuer, an Agency or government-sponsored enterprise, the U.S. Treasury, and a foreign sovereign, which paragraph (kk) defines to include a foreign government, its political subdivisions and a supranational entity. Money Market Instruments are excluded. Under Rule 6710(o) that means a debt security, other than a Treasury, with a maturity at issuance of one calendar year or less, or one calendar year and one day or less for an Agency or GSE discount note. Primary market trades have been reportable since 1 March 2010, but Rule 6710(c) generally excludes a sale from an issuer to underwriters or initial purchasers as part of an offering from the definition of a Reportable TRACE Transaction. It expressly preserves an exception for sales of Agency Pass-Through Mortgage-Backed Securities by a securitizer to any purchaser.

Agency debt has its own boundary. Rule 6710(l) excludes from “Agency Debt Security” any securitized product where an Agency or GSE is the securitizer or guarantor, so agency-guaranteed mortgage pools are reported as securitized products on their own clocks. Paragraph (l)(iii) pulls the other way: debt issued by a trust or other entity that a GSE established or sponsored to issue debt, where the GSE provides collateral or keeps a material net economic interest in the reference tranches, counts as agency debt.

Rule 6730 contains no minimum trade size and no firm-level activity threshold for corporate and agency reporting. The volume tests that do appear in the rule, the $10 billion monthly test for covered ATSs in Supplementary Material .06 and the $10 million average daily par value test in Supplementary Material .07, apply only to U.S. Treasury Securities.

There is no consolidation level either. Each member reports under its own MPID, and a clearing firm that reports for a correspondent does so as a give-up under a service agreement, with the correspondent’s MPID on the report. Rule 6730(a)(6) keeps primary responsibility for timely, accurate and complete reporting with the member that owes the report, whoever transmits it. Rule 6730, the TRAQS user guide and the FIX specifications say nothing specific about U.S. branches of foreign banks or other third-country arrangements; the rule text works through the two tests above, FINRA membership and the security definition.

The user guide is blunt on one point that trips correspondent structures: FINRA members cannot designate each other as customers. Only a non-member end customer may carry “C”. A clearing firm that also executes for its correspondents must identify each correspondent by MPID, either through the correspondent’s own reports or through give-up reports under a pre-signed agreement, because a “C” in that field would leave the correspondent anonymous to surveillance staff and break the audit trail.

What the report contains: the 15 items in Rule 6730(c), field by field

A TRACE report describes one trade in one security from the reporting member’s side. Rule 6730(c) lists the content, and the TRAQS Trade Entry screen and the inbound FIX Trade Capture Report (message type AE) carry it as follows.

Units and formats come from the specifications. Size is the total par or principal value traded under Rule 6730(d)(2)(A); TRAQS treats the quantity field as a dollar amount, accepts values up to 99,999,999,999.99 without commas, and reads 1000 as 1000.00. Price is a percentage of par with up to six decimals, so a bond at 98.625 is reported as 98.625; equity-linked notes are the exception and report a dollar price per share. On a principal trade the price includes the mark-up or mark-down, and on an agency trade it excludes the commission, which goes in its own field. Commission is a flat dollar amount, and TRAQS accepts it only when capacity is agent. Neither the rule nor the user guide or FIX specifications sets a rounding convention beyond these format masks.

Time of Execution needs care on spread-priced trades. Rule 6710(d) defines it as the moment the parties agree all terms sufficient to calculate the dollar price, and for a trade priced as a yield spread over a benchmark security, the moment the yield is agreed. The time zone then depends on the channel. TRAQS takes execution time in Eastern Time as HHmmss, and seconds may be entered as 00 if the firm’s system cannot capture them. FIX carries execution time in TransactTime (Tag 60) in UTC, while TradeDate (Tag 75) stays an Eastern Time date; FIX would allow milliseconds, but the TRACE solution does not use them.

Agency trades are the standard non-example of “one ticket, one report”. In the user guide’s own example, a firm sells $10,000 of a corporate bond for a customer, as agent, to dealer ABC. The firm files two reports: a buy from “C” as agent at 98 with the $50 commission, and a sell to ABC as agent at 98. TRACE wants the firm to appear between the customer and the contra party, exactly as a principal trade would, even though the firm’s internal ticket probably shows a single sell.

The Trading Market Indicator sets the clock. It is a TRAQS drop-down and FIX Tag 22016, and it reads S1 for a secondary market trade or a primary market trade at market price, both on the 15-minute clock, and P1 for a List or Fixed Offering Price Transaction or a Takedown Transaction, which runs to T+1. An in-house cross becomes two reports under Rule 6730(d)(3), the member’s purchase and its sale.

TRACE reporting deadlines: the 15-minute clock, T+1 and the 6:30 p.m. close

Each TRACE report runs on its own clock, which starts at the Time of Execution; the regime has no reference date or reporting period, so the first deadline arrives with the first reportable trade. The dates that move are rule effective dates, covered in the changes section. Under Rule 6710(t), TRACE System Hours run from 8:00:00 a.m. to 6:29:59 p.m. Eastern Time on a business day, unless FINRA announces otherwise.

Agency debt follows the corporate column; Rule 6730(a)(1) is the general rule for both. Foreign sovereign debt follows Rule 6730(a)(5).

The 15 minutes are a ceiling. Rule 6730(a) requires reporting “as soon as practicable”, and Supplementary Material .03 requires policies, procedures and systems that start the reporting process at the Time of Execution without delay. A firm with those arrangements is generally not treated as breaching the standard for delays caused by extrinsic factors that are not reasonably predictable, but no firm may purposely withhold reports, for example by programming its systems to release them at the end of the window. Where a firm reports manually, FINRA takes the manual nature of the process into account when judging whether the procedures are reasonably designed.

The user guide and both FIX specifications list a 5:15 p.m. “Market Close” alongside the 6:30 p.m. “System Close”. The reporting rule keys on the system close: for corporate and agency trades, Rule 6730(a)(1)(C) moves only trades executed less than 15 minutes before 6:30:00 p.m. to the next business day. A trade executed at 5:30 p.m. is still due within 15 minutes. FINRA publishes holiday closures and early closes on its TRACE holiday calendar.

An S1 trade executed on a weekend or holiday is reported in the first 15 minutes of the next business day as an as-of trade carrying the actual non-business execution date and time. TRACE designates anything reported outside its window as “late”, and Rule 6730(f) states that a pattern or practice of late reporting without exceptional circumstances or reasonable justification may be considered conduct inconsistent with high standards of commercial honor and just and equitable principles of trade, in violation of Rule 2010.

Submission: TRAQS web entry, FIX 4.4 sessions and the agreements behind give-ups

Before the first report, the firm needs entitlements as well as connectivity. Rule 6720 requires a signed TRACE participant agreement. The TRAQS user guide adds that every user of the corporates and agencies website, whether a member firm or a third-party reporting intermediary, works under a FINRA Transparency Services Participation Agreement (FPA), with users managed in FINRA’s Participant Data Management system and multi-factor authentication on the website. TRAQS inactivates a user who has not logged in for 90 days, which matters for backup users who only log in when the primary feed fails.

Four routes carry reports:

• TRAQS Trade Entry, at finratraqs.org: single trades, original or as-of.
• TRAQS Multi-Trade Entry: up to 50 trades at a time in a grid.
• Trade Report File Upload: an Excel template with worksheets for entries, cancels, corrections and reversals, capped at 1,000 rows in total per file. FINRA grants access case by case when a firm has serious systemic problems and suspends it once the upload is done, so it serves as a contingency route.
• FIX: Trade Capture Reports over a FIX 4.4 session, with acknowledgements to the reporting party and allege messages to the contra party.

FINRA publishes two FIX specifications for corporates and agencies, both dated 4 February 2026 and both built on FIX 4.4 with FINRA extension tags. The legacy FIX reporting connection is scheduled for retirement: FINRA’s Technical Notice of 29 June 2026 sets 11 December 2026 as the final cutover date for TRACE production ports to Native FIX. Firms and service bureaus using legacy ports must order Native FIX ports through the Native FIX Port Request Form and separately request removal of legacy ports. FINRA strongly encourages testing in its test facility followed by a Saturday production test before the cutover.

Version 1.6 returns the legacy reject codes (4001 to 4071) and identifies a service bureau as an extra party on the reporting side. The “native FIX” specification, version 2.1, introduces service-bureau identification in the FIX message header, using Tags 115 and 116 inbound and Tags 128 and 129 outbound. However, its revision history states that Entering Firm (PartyRole 7) was removed as an applicable party role, whereas section 4.5.7 and the service-bureau example still require that party role. FINRA’s published specification is therefore internally inconsistent on this point. A service-bureau implementation should confirm the accepted PartyRole treatment with FINRA or its designated technical support before changing message construction.

Revision 2.0 of the native specification also added Confirmed Match Status messages (CAMA) for matched inter-dealer trades and for trades that become unmatched after previously matching; open unmatched trades do not generate CAMA confirmations, and customer, affiliate and locked-in trades are also excluded from CAMA confirmations. It also lists a native reject code set beside the legacy table. The session rules are the same in both: TargetCompID “FNRA”, TargetSubID “CA”, a 30-second heartbeat, no encryption, and a session lifetime of one trading day with sequence numbers reset to one each morning. The specifications list FINRA Client and System Management as the contact for corporates and agencies trade reporting questions, and Nasdaq technical support for FIX connectivity.

No taxonomy, XBRL or XML reporting schema applies. Reports go in as FIX messages, through TRAQS web entry or, where FINRA has granted access, through the xlsx Trade Report File Upload template, for which the user guide sets no naming convention. The user guide also describes CSV exports from screens such as Trade Management, Reject Scan and Unmatched Trade Reports, and API file downloads; these retrieve data and are not submission routes.

Reporting for another member needs a written relationship that TRACE recognises. The user guide calls it a Uniform Services Agreement (and, in another passage, a Participant Service Agreement); the FIX specifications require a TRACE Service Bureau/Executing Broker Supplement, Attachment B of the TRACE Participation Agreement. The agreements run one way: permission for A to report for B gives B no right to report for A. Locked-in reports, where a clearing firm or member ATS reports both sides in one report, must be entered as sells from the seller’s perspective with the reporting firm’s own MPID in the contra party field, and TRAQS rejects a locked-in buy. One locked-in report satisfies both sides’ obligation, but the customer sides remain separate reports.

Corrections run on a rolling window. Cancels and corrections (no/was) are available for reports submitted in the past 20 business days, including the current day (T-20). For anything older, the firm submits a reversal, which must repeat all the values of the original trade, and corrects an old trade with a reversal followed by a new as-of report carrying the right details.

Validation: TRACE rejects, price checks and FINRA’s report cards

Validation happens at submission. An accepted report comes back with a control date and a ten-digit control number, the identifiers the firm can then use to cancel or correct it. A rejected report returns a reject control number, a reject code and a reason; in FIX the code and reason sit in Tag 751 and Tag 58. Warnings are a third outcome: TRAQS flags some input problems, such as a non-numeric price or an invalid symbol, without assigning a reject control number, and those entries cannot be repaired through Reject Scan.

Price validation has its own escalation path. TRACE compares the reported price with recent trades in the same security and rejects a price substantially different from its view of the current market. The Price Override flag (a TRAQS checkbox; FIX Tag 9854) widens the tolerance, but both the user guide and the FIX specification restrict it to a resubmission after an initial price reject. If the override still fails, the user guide directs the firm to report the trade by telephone to FINRA Operations, which will ask why the price departs from normal conditions.

The legacy and native reject tables in the v2.1 specification together list more than a hundred codes. The specifications do not rank them by frequency, so the selection below follows the traps covered in this guide.

Rejects have a short life. Reject Scan lets the reporting party repair rejected entries, corrections and reversals whether they came by web or FIX, but only for the current day; prior-day rejects within the T-20 window are view-only, and rejects left untouched at the daily system close are closed automatically. The user guide warns about a duplicate trap: a reject fixed directly on the Trade Entry form still appears in Reject Scan, and repairing it there as well creates a second trade report. A P1 trade that rejects is corrected and resubmitted within its T+1 window.

FINRA also reviews quality after the fact and gives each firm the results through the Report Center. The TRACE Quality of Markets Report Card for corporate bonds and agency debt shows, for the report month, the firm’s late same-day and late as-of reports against industry and peer averages, followed by a trade reporting analysis that FINRA says does “not definitively indicate problems”. Among its flags are inter-dealer reports with no matching contra report, reports by other firms naming the firm as contra that the firm never matched, matched trades whose execution time differs from the contra firm’s by 15 minutes or more, and intra-firm trades where both MPIDs map to the same CRD number, which FINRA notes “may indicate trade reports where there was no beneficial change of ownership”. A separate daily corporate bond report card adds a non-match rate and late counts by contra type, on a T+4 delay, with data back to 1 January 2025.

Caveats and interactions: exclusions, affiliates, dissemination and neighbouring regimes

Transactions Rule 6730(e) keeps out of TRACE

Rule 6730(e) lists eight categories that are not reported. Five of them are:

• bona fide repurchase and reverse repurchase transactions;
• transfers made solely to create or redeem an instrument such as an exchange-traded fund;
• trades in exchange-listed TRACE-eligible securities that are executed on, reported to and disseminated by the exchange;
• trades on an NYSE facility under NYSE Rules 1400, 1401 and 86, for as long as the FINRA and NYSE data sharing agreement remains in effect;
• transactions resulting from the exercise or settlement of an option, or the termination or settlement of a credit default swap or other swap.

The remaining three cover trades at a price substantially unrelated to the current market (a gift, for example), transfers under a court-approved asset purchase agreement in insolvency whose price cannot reflect current market prices, and Treasury Auction Transactions. Supplementary Material .05 separately exempts STRIPS separation and reconstitution.

The affiliate indicator suppresses publication only

A back-to-back trade with an affiliate is still reported. Where a member trades as principal with its non-member affiliate and has traded, or reasonably believes it will trade, the same security on the same day at the same price with another contra party, it appends the affiliate principal transaction indicator (“A” in the TRAQS Special Processing field; FIX Tag 22005 = A), and Rule 6750(d) keeps that report out of dissemination. Regulatory Notice 26-16, citing FINRA’s TRACE FAQ 3.1.74, adds that the trade with the other contra party must be for a quantity equal to or greater than the inter-affiliate trade. The FIX specification describes the qualifying trade as one with no mark-up or commission assessed. SR-FINRA-2026-009 extends the indicator to member affiliates: both members must share the reasonable belief and both must append it, and where a member has traded the same security on the same day at the same price with both a member affiliate and a non-member affiliate, and neither member affiliate trades with an unaffiliated contra-party on those terms, the member appends the indicator to only one of the two inter-affiliate reports.

No Remuneration and what the public tape shows

The No Remuneration indicator (Rule 6730(d)(4)(F); FIX Tag 22034 = N) applies where a report reflects no commission, mark-up or mark-down, except on inter-dealer trades and P1 trades, and the FIX specification accepts it only on customer and affiliate trades. On the publication side, Rule 6750 disseminates reports immediately on receipt, with exceptions: List or Fixed Offering Price and Takedown Transactions, affiliate-indicator trades and Foreign Sovereign Debt Securities are not disseminated. Large trades appear with capped sizes, “5MM+” above $5 million par for investment grade corporate bonds and “1MM+” above $1 million par for non-investment grade, and the uncapped sizes are released in the Historic Corporate Bond Data Set six months after the quarter. Rule 6710(h) classifies every Agency Debt Security as Investment Grade for the dissemination of transaction volume.

Other TRACE products and neighbouring regimes

The same members may report other TRACE-eligible securities on different clocks. U.S. Treasury Securities generally have a 60-minute reporting limit during TRACE System Hours, subject to the opening, closing and non-business-day provisions in Rule 6730(a)(4)(A). Rule 6730(a)(4)(B) separately allows until T+1 during TRACE System Hours for Treasury transactions executed to hedge List or Fixed Offering Price Transactions or Takedown Transactions. For electronically executed Treasury trades, the timestamp requirements in Supplementary Materials .04 and .07 prescribe an increment no longer than one second and no shorter than one microsecond, with the limited-volume exception applying as specified in .07. Securitized products split further: CMBS and CDOs executed by 5:00 p.m. are due the same day; agency pass-through TBA trades not for good delivery, specified pool trades, SBA-backed ABS traded TBA or in specified pools, and CMOs at or after issuance are due within 60 minutes; asset-backed securities and TBA good delivery trades follow the 15-minute clock.

Municipal securities sit outside the four Rule 6710(a) issuer categories. Dealers report municipal trades under MSRB Rule G-14, customer trades to the MSRB’s Real-Time Transaction Reporting System and inter-dealer trades eligible for clearance through a registered clearing agency through the RTTM comparison process, on a 15-minute requirement with exceptions; our RTRS reporting guide covers that regime. A U.S. dealer group with European affiliates meets a different design again: under MiFIR Article 26(7), transaction reports go to the competent authority, sent by the firm, an approved reporting mechanism or the trading venue. Our MiFIR transaction reporting guide sets out that regime, and the UK bond consolidated tape article covers the UK’s route to bond post-trade transparency.

Changes to TRACE reporting: the one-minute rule withdrawn, allocations and member affiliates

The current text is the product of three rule filings in two years, and the first of them was largely rescinded before it applied.

• 20 September 2024: the SEC approved SR-FINRA-2024-004 (Exchange Act Release No. 101121). It would have cut the 15-minute outer limit to one minute, with exceptions for members with de minimis reporting activity and for manual trades, and required a new manual trade indicator.
• 16 September 2025: the SEC approved SR-FINRA-2025-008 (Release No. 103986, 90 FR 45283). It rescinds the SR-FINRA-2024-004 changes apart from some clarifying amendments, keeps the 15-minute outer limit, and adds the allocation alternative.
• 4 December 2025: Regulatory Notice 25-17 announced 8 June 2026 as the effective date.
• 4 February 2026: TRAQS user guide v6.3 added the Allocations field to the entry, correction, reversal and repair screens and the upload template; FIX specification v1.6 and native FIX v2.1 added Tag 80 (AllocQty) to trade, correction and reversal messages.
• 8 June 2026: the clarified “as soon as practicable” wording in Rule 6730(a)(1), “reasonable justification” in Rule 6730(f), a clarifying change to Supplementary Material .03, and the allocation alternative in paragraph (c)(14) and Supplementary Material .08 took effect.
• 24 July 2026: the SEC approved SR-FINRA-2026-009 (Release No. 105991, 91 FR 47909), extending the affiliate principal transaction indicator to member affiliates; Regulatory Notice 26-16 followed on 26 August 2026.
• 31 August 2026: voluntary compliance with the member-affiliate indicator began.
• 2 August 2027: compliance with the member-affiliate indicator becomes mandatory.

The allocation alternative is narrower than its name suggests. Regulatory Notice 25-17 limits it to a firm that is both a broker-dealer and an investment adviser, allocating an aggregate order to managed customer accounts at that firm. Each aggregate report must cover allocations at the same price and Time of Execution, go in within the normal Rule 6730(a) timeframe, and carry the number of managed accounts (2 to 99,999 in the Allocations field or Tag 80, reporting side only); in the notice’s example, where no mark-up or commission is charged, the report also carries the No Remuneration indicator. The route is optional, and a BD/IA can keep reporting each allocation separately. FINRA disseminates the number of accounts and the aggregate volume, subject to the size caps.

Earlier milestones explain today’s scope: 15-minute reporting for corporate bonds from 1 July 2005, agency debt and primary market trades from 1 March 2010, foreign sovereign debt from 6 November 2023 under SR-FINRA-2022-011, and end-of-day dissemination of on-the-run nominal coupon Treasuries from 25 March 2024 under SR-FINRA-2023-015.

One change still has no date. SR-FINRA-2019-008, FINRA’s filing to establish a corporate bond new issue reference data service, appears in Rule 6760’s history without an effective date, and a later filing, SR-FINRA-2021-007, extended the time to announce the implementation schedule. Rule 6760(b)(2) lists the additional fields for new Corporate Debt Security issues, among them ISIN, currency, issue date, coupon frequency and rating, while Rule 6710(jj) shows the definition of “Corporate Debt Security” with the notation “(implementation date to be announced)”.

Frequently Asked Questions

Can a correction change the trade date of a report we filed today?

For a regular report, the FIX specification bars any change of trade date through a correction: the firm cancels the original and submits a new report with the intended date. An as-of report can be corrected to an earlier trade date only; moving it to a later date again requires a cancel and a new as-of report.

A bond we just traded looks TRACE-eligible but is missing from the TRACE security list. What now?

Rule 6730(a)(8) requires the member, once it has made a good faith determination that the security is TRACE-eligible, to report the trade and, because the security is not in the system, first to notify FINRA Operations promptly with the information Rule 6760(b) requires. For a new issue, the managing underwriter’s notice under Rule 6760 is generally due before the first transaction of the offering, so for a newly issued bond the first check is whether that notice was given.

A portfolio trade covers 12 corporate bonds at one basket price. How is it flagged?

Rule 6730(d)(4)(H) requires the Portfolio Trade modifier where a corporate bond trade is between only two parties, involves a basket of at least 10 unique issues and is done at a single agreed price for the whole basket. TRAQS carries it as “P” in Modifier 4, and FIX as TradeModifier4 (Tag 22004) = P. Each TRACE report identifies one CUSIP under Rule 6730(c)(1), so each bond in the basket is reported separately carrying the modifier. A basket of nine issues, or one with a third party involved, does not qualify.

TRACE is unavailable. Can we report on paper?

Only within Rule 6730(a)(7). FINRA may require a member to report to Market Regulation on a paper form when electronic submission into TRACE is not possible, but any trade that can be reported into TRACE, including on a later date as an as-of report, is not reported on paper. For a firm-side outage, FINRA can authorise the Trade Report File Upload as a temporary route. During an Emergency Market Condition halt, TRAQS shows the halt and resume messages in System Alerts.

Is a dollar bond issued by a supranational development bank reported on the corporate clock?

It is reportable, on the foreign sovereign timetable. Rule 6710(kk) includes supranational entities in “Foreign Sovereign Debt Security”, and TRAQS handles these trades as the SOVN sub-product within the corporates and agencies screens. They are not disseminated. A euro-denominated bond from the same issuer falls outside TRACE, because Rule 6710(a) requires U.S. dollar denomination.

Our trade was executed on an ATS. Do we and the ATS both report?

Where the ATS is a party, it reports like any other member, under the separate MPID that Rule 6720(c) requires. Following amendments effective 3 October 2022 (Regulatory Notice 22-13), Rule 6732 permits FINRA staff, on application and subject to the rule’s conditions, to exempt a member ATS from reporting eligible transactions involving at least one FINRA member other than the ATS. This includes transactions between a FINRA-member subscriber and a non-member counterparty. The ATS must not route the trade through an ATS account, exchange securities or funds on subscribers’ behalf, participate in clearing or settlement, or otherwise insert itself into the transaction. It must provide FINRA with the prescribed trade data, pay the applicable reporting fee on exempt sell transactions, and maintain written agreements requiring its member subscribers to report. The reporting members name a contra party other than the ATS and enter the ATS’s MPID in the ATS Execution MPID field (FIX Tag 22036).

We report by symbol. What changes when a new bond moves from when-issued to regular way?

A CUSIP report is recognised as when-issued or regular way from the settlement date, but a symbol report depends on the firm choosing the right symbol. The same CUSIP can carry two reporting symbols while the issue trades when-issued, and after the settlement date TRAQS refuses a regular-way trade under the when-issued symbol unless it is an as-of submission.

Related Articles

• RTRS Reporting: Municipal Trades to the MSRB Within 15 Minutes: how dealers report municipal securities trades to the MSRB, the regime that sits beside TRACE for municipal bonds.
• MiFIR Transaction Reporting: Complete Guide to Article 26 Compliance: the EU transaction reporting obligation for investment firms and what each report must contain.
• UK Bond Consolidated Tape: What Real-Time Transparency Means for Post-Trade Reporting Under UK MiFIR: the UK’s consolidated tape for bonds and its link to post-trade reporting.
• Transaction Reporting Simplification: ESMA’s EUR 1bn Plan: ESMA’s plan to simplify transaction reporting across EMIR, MiFIR and SFTR.

Key Takeaways

• Audit report-release logic for timers or batching: a report held to minute 14 by design conflicts with Supplementary Material .03 even though TRACE never flags it late.
• Evening cut-over: only trades executed after 6:15 p.m. ET roll corporate and agency reports to T+1; the 5:15 p.m. market close moves nothing.
• Store execution time twice over: Eastern Time for TRAQS, UTC for FIX Tag 60, with the Tag 75 trade date in Eastern Time, and test the conversion across daylight-saving changes.
• BD/IA desks: the single allocation report has been available since 8 June 2026; using it is a choice, and separate allocation reports remain available.
• Schedule a TRAQS login for every backup user inside each 90-day period; an inactivated account cannot carry reports on the day the primary feed fails.
• Read the contra-side unmatched count on the monthly report card: it lists reports other firms filed naming your MPID that your own reports never matched.
• Treat a bond that is missing from the TRACE security list as a reporting event: notify FINRA Operations with the Rule 6760(b) data before submitting the report.

Sources and References

• FINRA Rule 6730, Transaction Reporting: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6730
• FINRA Rule 6710, Definitions: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6710
• FINRA Rule 6720, Participation in TRACE: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6720
• FINRA Rule 6732, Exemption from Trade Reporting Obligation for Certain Transactions on an Alternative Trading System: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6732
• FINRA Rule 6731, Exemption from Trade Reporting Obligation for Certain Alternative Trading Systems: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6731
• Rule filing SR-FINRA-2019-008 (corporate bond new issue reference data service): https://www.finra.org/rules-guidance/rule-filings/sr-finra-2019-008
• Rule filing SR-FINRA-2021-007 (extension of time to announce the implementation schedule): https://www.finra.org/rules-guidance/rule-filings/sr-finra-2021-007
• FINRA Regulatory Notice 22-13, Exemption From Trade Reporting Obligation for Certain Transactions on Alternative Trading Systems: https://www.finra.org/rules-guidance/notices/22-13
• FINRA Rule 6750, Dissemination of Transaction Information: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6750
• FINRA Rule 6760, Obligation To Provide Notice and Dissemination of Corporate Debt Security New Issue Reference Data: https://www.finra.org/rules-guidance/rulebooks/finra-rules/6760
• FINRA Regulatory Notice 25-17, Rule 6730 amendments on allocation reporting for BD/IAs (4 December 2025): https://www.finra.org/rules-guidance/notices/25-17
• FINRA Regulatory Notice 26-16, FINRA Expands the Scope of the TRACE Non-Member Affiliate-Principal Transaction Indicator (26 August 2026): https://www.finra.org/rules-guidance/notices/26-16
• FINRA Technical Notice, Reminder: TRACE Transition to Native FIX (29 June 2026): https://www.finra.org/filing-reporting/technical-notices/reminder-trace-transition-to-native-fix-20260629
• Rule filing SR-FINRA-2024-004: https://www.finra.org/rules-guidance/rule-filings/sr-finra-2024-004
• Rule filing SR-FINRA-2025-008: https://www.finra.org/rules-guidance/rule-filings/sr-finra-2025-008
• Rule filing SR-FINRA-2026-009: https://www.finra.org/rules-guidance/rule-filings/sr-finra-2026-009
• Rule filing SR-FINRA-2022-011 (foreign sovereign debt): https://www.finra.org/rules-guidance/rule-filings/sr-finra-2022-011
• Rule filing SR-FINRA-2023-015 (Treasury dissemination): https://www.finra.org/rules-guidance/rule-filings/sr-finra-2023-015
• FINRA, TRAQS TRACE Corporate Bonds and Agency Debt User Guide, version 6.3 (4 February 2026): https://www.finra.org/sites/default/files/2026-02/TRAQS_CA_User_Guide_v6.3.pdf
• FINRA, FIX Specifications for TRACE, Corporates and Agencies, version 1.6 (4 February 2026): https://www.finra.org/sites/default/files/2026-02/FIX-Specs-CorpsAgencies-v1.6.pdf
• FINRA, FIX Specifications for TRACE, Corporates and Agencies (native FIX), version 2.1 (4 February 2026): https://www.finra.org/sites/default/files/2026-02/FIX_Specification_for_Corps_Agcys_v2.1.pdf
• FINRA, TRACE Quality of Markets Report Card, Corporate Bond and Agency Debt: https://www.finra.org/compliance-tools/report-center/trace/quality-of-markets-corporate-bond-agency-debt
• FINRA, TRACE Corporate Bonds Daily Report Card: https://www.finra.org/compliance-tools/report-center/trace/corporate-bonds-daily
• MSRB Rule G-14, Reports of Sales or Purchases: https://www.msrb.org/Rules-and-Interpretations/MSRB-Rules/General/Rule-G-14
• MSRB, Real-Time Transaction Reporting System (RTRS) Web Manual, draft version 3.9 (October 2025): https://www.msrb.org/sites/default/files/RTRSWeb-Users-Manual.pdf
• Regulation (EU) No 600/2014 (MiFIR), Article 26: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014R0600

Upcoming TRACE milestones: Native FIX cutover and member-affiliate reporting

Corporate and agency desks face a confirmed Native FIX production-port cutover on 11 December 2026, followed by the mandatory implementation of the expanded member-affiliate indicator under FINRA’s separate compliance timetable. From 2 August 2027 the affiliate principal transaction indicator becomes mandatory for back-to-back trades between member affiliates, and both members must append it. If only one does, Regulatory Notice 26-16 says TRACE still suppresses the sell-side report, but both firms receive a mismatch report on their TRACE Match Status Reports. Voluntary compliance has been open since 31 August 2026, so the artifact to build now is the list of member-affiliate flows in TRACE-eligible securities, each with the same-day, same-price and equal-or-greater-quantity test it has to meet, ready for testing with the affiliate’s reporting team before August 2027.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.