Data sourced from Dakota Marketplace, the global LP and GP intelligence platform trusted by thousands of investment professionals. Learn More | Book a Demo
A "reportable security" isn't a judgment call. It's a specific, defined status: a security either appears on the SEC's Official List of Section 13(f) Securities for a given quarter, or it doesn't. There's no gray area, and no discretion for a manager to include something they think is relevant but isn't on the list, or leave off something that is.
Here's how the SEC defines the term, how the list actually gets built, and a couple of mechanical quirks that trip people up when they're preparing or reading a filing.
The Legal Definition
Under Rule 13f-1(c), a "Section 13(f) security" is any security on the SEC's Official List, published quarterly under Section 13(f)(4) of the Exchange Act. The list itself pulls from equity securities that trade on a national securities exchange, plus certain over-the-counter equities, closed-end fund shares, and specified options and warrants on those securities.
The list is identified by CUSIP number, not by company name or ticker. Two share classes of the same company can have different CUSIPs and different reportability status, so checking "is this company on the list" isn't the same as checking "is this specific security on the list."
How the List Gets Built and Updated
The SEC publishes a new Official List every quarter, and it isn't static; names are added and dropped constantly as companies list, delist, get acquired, or otherwise change status. A recent quarter's list ran to tens of thousands of individual CUSIPs, dominated by exchange-listed common stock but also including a long tail of SPACs, warrants, and thinly traded issuers.
Managers are allowed to rely on the most recently published list at the time they're preparing a filing, even if it's slightly out of date relative to a mid-quarter change. What they can't do is use an old list once a new one has been published, or apply their own judgment about what should count.
A Reporting Quirk: How Options Get Listed
Options and warrants on a reportable security are themselves reportable, but they don't get their own line describing the option contract. Instead, the filer lists the CUSIP of the underlying security and separately flags the position as a PUT or CALL in the amount-and-type field. In other words, an option position is reported by pointing back to the stock it's tied to, not by describing the option itself. This is a common source of filing errors, since it's easy to mistakenly report the option's own CUSIP if one exists, rather than the underlying's.
What Gets Misclassified in Practice
A few situations account for most reportability mistakes:
- Assuming a company is covered because it's well known. Reportability is a CUSIP-level, list-based fact, not a reflection of how large or prominent the company is.
- Reporting a security that was on last quarter's list but has since been removed. The list changes every quarter, and using a stale version produces an inaccurate filing even if the manager's actual holdings didn't change.
- Confusing an option's CUSIP with the underlying's. As above, this produces a filing that doesn't match SEC formatting expectations.
- Assuming OTC securities are automatically excluded. Some over-the-counter equities are included on the Official List; exclusion isn't automatic just because a security doesn't trade on a major exchange.
Why the Definition Matters for Reading Filings, Not Just Writing Them
If you're on the reading side of a 13F rather than the filing side, the CUSIP-based definition matters just as much. A raw 13F lists CUSIPs and share counts. Turning that into "this firm holds Apple stock" or "this firm holds a call option on this ETF" requires mapping each CUSIP back to a real security and, ideally, to the strategy and sub-asset class it represents. That mapping work is exactly where a lot of the value in 13F data either gets captured or lost.
How Dakota Marketplace Handles the CUSIP-Level Work
Dakota ingests every 13F filing and resolves each reported CUSIP down to the actual security, issuer, and instrument type, then classifies it across a taxonomy of 19 asset classes and 236 sub-asset classes. Option and warrant positions are matched back to their underlying security and tagged accordingly, so a filer's exposure shows up correctly instead of as an unresolved line item.
Each filing is also matched to a known allocator profile and linked to confirmed, active contacts, so the output isn't a spreadsheet of CUSIPs but a usable view of what a firm holds and who to talk to about it.
Fund managers can filter Dakota's 13F holdings data by investment firm, product structure, AUM, asset class, sub-asset class, active or passive management, and filing period.
Book a demo to see 13F holdings resolved down to the security level, not just a list of CUSIPs.
