Featured

5MM+ Is a Cap, Not a Size: Six Capped Trades Redefine Monthly Par Volume

A corporate bond print crosses at 99.412 with a size field reading 5MM+. To the system that produced it, nothing is ambiguous. To a reader it is equally consistent with a five-million-dollar trade and a two-hundred-million-dollar trade.

The size on a disseminated TRACE print is the smaller of the trade size and a dissemination cap. That opens a harder question: when a monthly file reports aggregate par value volume for the same bond, which of the two sizes did it add up? FINRA Rule 7730 gives two answers, selected by a count, and the switch point is six.

Two Readings of One Size Field

Start with the dissemination rule. FINRA Rule 6750 (Dissemination of Transaction Information) paragraph (a) reads: "FINRA will disseminate information on all transactions in TRACE-Eligible Securities, including transactions effected pursuant to Securities Act Rule 144A, immediately upon receipt of the transaction report, except as provided in paragraphs (b) through (d) of this Rule." It never says the disseminated size equals the reported size, and it never mentions a cap. The load-bearing word is "information", whose composition the rule leaves elsewhere.

The caps sit outside the rule text, as an operational parameter on FINRA's TRACE Reporting and Dissemination page: "transaction size caps of $5 million for Investment Grade securities...and $1 million for Non-Investment Grade securities," so that "Investment Grade trades over $5 million in size are disseminated as '5MM+'" and non-investment grade trades over $1 million as "1MM+". The same page sets $10 million for asset-backed securities and $25 million for agency pass-through mortgage-backed securities in good delivery.

FINRA Regulatory Notice 19-12 states the mechanism: above the cap, "FINRA disseminates all of the same information, but with the size of the trade capped as '5MM+' (for IG) and '1MM+' (for non-IG)."

Every trade above the cap leaves two numbers behind: the reported size, a non-public regulatory record, and the cap the tape showed. The second is not an estimate of the first. It is a censored observation with a known censoring point.

Reporting speed does not touch this. The posted corporate timeframe is "Within 15 minutes of time of execution", and paragraph (a) publishes on receipt whatever that deadline becomes. A faster print is not an uncapped one.

Which Cap Applies Is a Rating Question

The cap governing a print is not a property of the trade. It is a property of a classification, and that classification has its own tie-breaker. FINRA Rule 6710 (Definitions) paragraph (h) defines "Investment Grade" as "a TRACE-Eligible Security that, if rated by only one nationally recognized statistical rating organization ("NRSRO"), is rated in one of the four highest generic rating categories; or if rated by more than one NRSRO, is rated in one of the four highest generic rating categories by all or a majority of such NRSROs; provided that if the NRSROs assign ratings that are evenly divided between (i) the four highest generic ratings and (ii) ratings lower than the four highest generic ratings, FINRA will classify the TRACE-Eligible Security as Non-Investment Grade for purposes of TRACE. If a TRACE-Eligible Security is unrated, for purposes of TRACE, FINRA may classify the TRACE-Eligible Security as an Investment Grade security. FINRA will classify any Agency Debt Security as defined in paragraph (l) as an Investment Grade security for purposes of the dissemination of transaction volume."

Paragraph (i) mirrors the rating test and closes the loop on unrated paper: "Except as provided in paragraph (h), if a TRACE-Eligible Security is unrated, FINRA may classify the TRACE-Eligible Security as a Non-Investment Grade security."

Three clauses there change how a screen reads. The even-split proviso resolves ties downward, so a split-rated bond takes the one-million cap. An unrated security is classified at FINRA's discretion either way, the paragraphs stitched together by that "Except as provided in paragraph (h)", so its cap is not derivable from the bond's documents. And the agency clause is scoped to "the dissemination of transaction volume": it fixes the cap, it does not describe the credit.

So the field flips with no change in the trade. A three-million-dollar par trade prints at actual size in an investment grade name and as "1MM+" in a non-investment grade name. Ratings migrate, so one CUSIP can cross the boundary mid-life and its history of uncapped prints is not a constant-definition series — the same trap as a share-count cap that moves while you measure against it, traced in Rule 144 Volume Caps: One Percent of Shares or the Four-Week Average.

Where the size field stops telling you the size Cap or mask threshold, $ millions of par. Log scale. Corporate, non-inv. grade $1MM Corporate, inv. grade $5MM Municipal (MSRB mask) $5MM Asset-backed securities $10MM Agency pass-through MBS $25MM Treasury 20y and 30y $50MM Treasury 7y and 10y $150MM Treasury 2y, 3y and 5y $250MM Treasury caps: on-the-run nominal coupons, end-of-day.

Six Capped Trades Change What the Monthly Total Counts

Now pick up a monthly file, on the theory that aggregates wash the censoring out. FINRA Rule 7730 (Trade Reporting and Compliance Engine) defines the TRACE Security Activity Report as a monthly product whose columns include "aggregate par value volume information, number of transactions, number of unique market participant identifiers ('MPIDs')" for disseminated transactions in corporate and agency bonds.

Then it gives two computations for the same column. "If there are six or more capped transactions disseminated during the calendar month, the aggregate par value volume information will reflect the actual trade size of each transaction, as well as the par value traded within specified size categories." And: "If there are fewer than six disseminated capped transactions during the calendar month, the aggregate par value volume information will reflect the capped volumes disseminated by TRACE."

One field name, two definitions, selected per security per month by a count, and nothing in the column says which one you hold. Take a non-investment grade bond, cap one million par. The month holds five trades of $4,000,000, each printed "1MM+", plus twenty smaller trades summing to $3,000,000 at actual size. Fewer than six capped transactions, so the aggregate reflects capped volumes: five times $1,000,000 plus $3,000,000, or $8,000,000. Add a sixth $4,000,000 trade and the aggregate reflects actual sizes: six times $4,000,000 plus $3,000,000, or $27,000,000.

One extra four-million-dollar trade moved the published total from $8,000,000 to $27,000,000, a jump of $19,000,000. Had the definition not switched, that month would have read $9,000,000. Two readings of one month, differing by a factor of three.

The transaction-count column turns on the same test from one side only: at six or more the report adds an estimate of how many trades fell in each size bucket, "provided as incremental ranges". The rule states no counterpart for months below six, so what that column shows there is not fixed by the rule text. The product is also late by design: "The TRACE Security Activity Report will be delayed a minimum of 90 days."

One extra trade, a three-fold move in the published total Non-investment grade bond, $1MM cap. Aggregate par value volume, millions. 0 10 20 30 $8MM 5 capped trades published, capped basis $27MM 6 capped trades published, actual sizes $9MM 6 capped trades capped basis, not published Six $4MM trades plus twenty smaller ones totaling $3MM.

When the Uncapped Size Appears, and Where It Does Not

The censored size is not sealed forever. Notice 19-12 states the corporate rule: "The full, uncapped size of trades above the caps is later published as part of an historical dataset six months after the calendar quarter in which they are reported." Rule 7730 delays that set by "a minimum of six months" while covering "all historic transactions in corporate bonds reported to TRACE, except Rule 144A transactions", the securitized products set by 18 months, and the academic corporate file by 36 months, which "will not include MPIDs, but will substitute a masked dealer identifier for each MPID included in the data."

Note that exclusion. Rule 6750(a) disseminates Rule 144A trades in real time, capped like everything else, but the historic corporate file routes them to a separate set, so a correction fitted there and applied to a tape containing 144A prints excludes part of what it corrects. eCFR, 17 CFR 230.144A (Private resales of securities to institutions) defines that population by purchaser, not by size.

Municipals run the same idea on a different clock, which shows the cap for what it is: a dial. MSRB Informational Notice IF-1 (Real-Time Transaction Reporting and Price Dissemination) defines the disseminated "Par Traded" element as "The par value of the trade as reported by the dealer. Trades with a par amount over $5 million will indicate par value as 'MM+' until five (5) weekdays (including holidays) after the stated trade date, at which time the par will be unmasked." The MSRB Trade Data Subscriptions page adds that "The exact par value on all transactions is disseminated in the T+5 and T+20 reports," after showing "as 'MM+' in the T+1 reports."

Same threshold, five million dollars. The municipal mask lifts after five weekdays including holidays; the corporate cap lifts six months after the quarter ends. Two settings of one dial: about a week against six to nine months.

Treasuries are a third setting. The SEC Order Approving a Proposed Rule Change Relating to Dissemination of Information on Individual Transactions in U.S. Treasury Securities lists caps by tenor: "Two Years: $250 million; Three Years: $250 million; Five Years: $250 million; Seven Years: $150 million; 10 Years: $150 million; 20 Years: $50 million; and 30 Years: $50 million." Rule 6750(c) pairs them with publication of "individual transactions in On-the-Run Nominal Coupons on an end-of-day basis." FINRA calibrated them "to the maturity, liquidity, and trading concentration of the underlying security to preserve the anonymity of market participants trading large transactions." The cap is anonymity engineering, not rounding.

How long the real size stays out of view Earliest availability of a trade's size. Point in time What the size field shows Execution + 15 min Actual size reported to FINRA, not public On receipt Public print, shown as 5MM+ or 1MM+ Municipal T+1 MSRB par masked as MM+ above $5MM Municipal T+5 MSRB exact par unmasked Plus 90 days minimum Monthly aggregate, basis set by six-trade test Plus 6 months Historic corporate set, uncapped, no 144A Plus 18 months Historic securitized products set Plus 36 months Academic corporate set, MPIDs masked

The Prints That Never Appear

A cap changes a value. Paragraph (d) removes rows, beginning with transactions "identified with the Affiliate—principal transaction indicator pursuant to Rule 6730(d)(4)(E)" and certain merger-related position transfers.

The list continues: "(3) a List or Fixed Offering Price Transaction or a Takedown Transaction; (4) a Securitized Product that is: a CMBS; a CDO; or a CMO if the CMO transaction value is $1 million or more (calculated based upon original principal balance) and the transaction does not qualify for periodic dissemination under paragraph (b) of this Rule, except as may be otherwise provided in Rule 7730; (5) a U.S. Treasury Security other than an On-the Run Nominal Coupon; or (6) a Foreign Sovereign Debt Security."

Item (3) reshapes a new issue's first day. Rule 6710 defines a List or Fixed Offering Price Transaction as "a primary market sale transaction sold on the first day of trading" at published prices. Those never print, so first-day volume is secondary only.

Supplementary Material .01 then lets FINRA publish statistics on that suppressed population anyway, "Notwithstanding the provisions of paragraph (d)," provided they "will not be published or distributed by individual security, and will not identify individual market participants or transactions." Suppressed rows can sit inside a market-wide total while invisible per bond — the shape of An Odd Lot Prints, Adds to Volume, and Never Sets the Last Sale.

Concrete Framework

1. Classify the field. Reported size, disseminated size or historic uncapped size. Only the third is the trade; the first is non-public; the second is a floor.

2. Resolve the cap from the classification, not the name. Apply Rule 6710(h) and (i), even-split proviso and unrated discretion included. A three-million-par print is uncapped in one bucket, capped in the other.

3. Write every capped print as a floor. "Size at or above the cap," never the cap itself. Sums are lower bounds; averages are biased down by an unknown amount.

4. Count the capped trades before using a monthly aggregate. Two securities on opposite sides of six are not comparable, and one crossing six between months produces a step that is definitional, not economic.

5. Anchor the unmasking clock per market. Corporate, six months after the quarter, in a set excluding Rule 144A; 144A corporate lands instead in the Historic Rule 144A Data Set, which carries "a delay consistent with the delay period applicable to the component security type." Municipal, five weekdays. Securitized, eighteen months.

6. Check the exclusion list before computing any share. A denominator of disseminated prints omits affiliate-principal trades, qualifying merger transfers, list or fixed offering price and takedown transactions, CMBS, CDOs, most large CMOs, off-the-run Treasuries and foreign sovereign debt. Then date-stamp the parameter set: each item is set by rule filing, and each has moved.

What Would Invalidate This

The next change is already posted: Rule 6750 shows "Amended by SR-FINRA-2026-009 eff. Aug. 2, 2027." The SEC Order Approving a Proposed Rule Change To Amend the FINRA Rule 6700 Series (TRACE) describes the affiliate-principal indicator as designed to "suppress from dissemination inter-affiliate transactions that do not provide pricing information different from the disseminated transaction," now extended to include transactions between member affiliates trading as principal "where the transaction with the member affiliate occurs within the same trading day, at the same price, and in the same TRACE-Eligible Security as a transaction executed by one of the members with another contra-party." Since paragraph (d)(1) withholds anything carrying it, widening the indicator widens the suppressed set: a volume series spanning that date is two series.

The cap levels have been contested. Notice 19-12 sought comment on a pilot of three test groups, not one change: Test Group 1, "a 48-hour dissemination delay with no change to the current dissemination caps"; Test Group 2, in which "TRACE would increase dissemination caps to $10 million for IG corporate bond trades and $5 million for non-IG corporate bonds trades, without applying a 48-hour dissemination delay"; and Test Group 3, "both a 48-hour dissemination delay and increased dissemination caps." Under the Recommendation "the full size of the capped trade would be published three months after the calendar quarter in which the capped trade was reported to FINRA". Adopt any version and every sentence above naming five million or one million fails from its compliance date. The delay groups would also create a state the framework above has no slot for: "no information about the trade would be disseminated for 48 hours", and only then are "the trade's time of execution, the price of the trade and a capped trade size ($10MM+)" released — absent from the tape first, still capped after.

Three sharper tests. If the historic corporate file and the monthly aggregate agree to the dollar for a bond with five capped trades, Rule 7730's fewer-than-six branch is not operating as written. If a split-rated bond prints four-million-dollar sizes uncapped, the even-split proviso is not resolving to Non-Investment Grade. If a new issue's first-day volume matches its deal size, item (3) is not suppressing what it claims.

Two limits on scope. The reporting deadline is in transition: Rule 6730(a) and the TRACE timeframe page both read 15 minutes when I retrieved them, while the reduction to "as soon as practicable, but no later than within one minute of the Time of Execution" is already approved in the SEC Order Approving a Proposed Rule Change To Amend FINRA Rule 6730 To Reduce the 15-Minute TRACE Reporting Timeframe to One Minute, which records that FINRA "would continue to make information on the transactions publicly available immediately upon receipt of the trade reports." Second, this post is about what the size field counts, not whether a large print is informative — as a position file is only a snapshot of one date, in Which Settlement Date Does the Short Interest Number on Your Screen Describe.

The narrow claim stands on its own. Three characters on a bond print, 5MM+, state a rule parameter and a lower bound. The monthly column that appears to aggregate those prints changes definition at six capped trades. Both facts are in the rulebook, neither is in the field, and a dashboard that drops them produces a number nobody can reconcile.

Comments