what are the most common errors in 13F filings?

the recurring ones are the pre-2023 thousands-convention error (positions reported 1,000× too small), stale or wrong CUSIPs that map to the wrong ticker, omitted or confidentially-treated holdings, single rows mis-scaled up or down, and mislabeled option or share-type fields.

what is the 13F thousands-convention error?

since january 3, 2023 the SEC requires 13F values in whole dollars, but some funds still file in the old thousands convention. a $10 million position is then written as the number 10,000, and any tool reading it as whole dollars shows it 1,000× too small.

how can i tell if a 13F has a data error?

verify each position with shares times the quarter-end price and compare it to the reported value. a ~1,000× gap means the thousands convention; an issuer name that doesn't match the resolved ticker means a CUSIP problem; an implausible value means a mis-scaled row.

do funds correct 13F errors?

sometimes, by filing an amendment (13F-HR/A). but many errors are never corrected because they are technically faithful to how the fund entered the data — the filer used the wrong convention, not the wrong numbers. screeners then inherit the error.

why do screeners show wrong 13F data?

most screeners ingest the filing's value field at face value and assume every filer follows current rules. when a filer doesn't — wrong units, stale CUSIP, mislabeled option — the screener faithfully displays the wrong number with no flag.

5 common 13F filing errors that distort what funds actually own

the unit-convention bug is just one of them. five recurring 13F filing errors that distort fund positions — with EDGAR examples you can verify.

by hedgewatch researchpublished june 22, 20269 min read

13F holdings are legally attested, but the data is far from clean. a handful of errors recur every quarter, and because most screeners ingest filings at face value, those errors propagate everywhere at once. the thousands-convention bug is the most consequential, but it's one of five. here are the recurring distortions, how each misleads, and how to catch them — with filings you can verify yourself.

// key_takeaways

→1. thousands convention — real position rendered 1,000× too small.
→2. stale/wrong CUSIP — share count paired with the wrong stock's price.
→3. omitted holdings — confidential treatment hides a position being built.
→4. mis-scaled rows — a single line 1,000× too large or small.
→5. mislabeled fields — options or share-type flags that distort exposure.

the_five_errors

1 · the thousands-convention error

the big one. since 2023-01-03 the SEC requires values in whole dollars, but some funds still file in thousands — so a real position reads 1,000× too small. in Q1 2026, Tieton Capital reported its Core Molding (CMT) stake with a value field of 10,302 — but 459,890 shares at the ~$22.40 quarter-end close is a $10.3 million position, not $10,302. the full breakdown is in the thousands-convention deep dive.

2 · stale or wrong CUSIPs

a CUSIP that went stale after a merger or ticker change — or a simple transcription error — maps a real share count onto the wrong security's price. the value then looks plausible but describes the wrong company. catch it by confirming the resolved ticker's issuer matches the filing's nameOfIssuer; see CUSIP to ticker.

3 · omitted and confidential holdings

a manager can request confidential treatment to delay disclosing a position — often while still building it. the holding is simply absent from the public filing until the request lapses. you can't catch what isn't there, but a later amendment that suddenly adds a large position is the tell.

4 · mis-scaled single rows

even in a correctly-filed report, one row can be off — entered in thousands while the rest are in dollars, or fat-fingered 1,000× too large. these row anomalies and overstated positions distort a single line without flagging the whole filing, which makes them easy to miss. the fix is the same: check every row against shares × price.

5 · mislabeled options and share types

a blank putCall on what is actually an option, or a PRN principal amount read as a SHshare count, misstates the size and even the direction of a fund's exposure. these labeling errors are subtle but change what the position means.

error_to_symptom_map

Five common 13F errors, the symptom each produces, and how to detect it.
error	symptom	how to catch it
thousands convention	position ~1,000× too small	shares × price vs reported value
stale/wrong CUSIP	wrong issuer or price	match resolved ticker to nameOfIssuer
omitted holding	position missing entirely	watch for later amendments
mis-scaled row	one implausible line	per-row value sanity check
mislabeled field	wrong size or direction	check putCall and sshPrnamtType

the_pattern_behind_all_five

every one of these survives because screeners trust the filing's fields instead of verifying them. the single discipline that catches most of them is the same: recompute value from shares × quarter-end priceand flag any row that doesn't reconcile. that is exactly what HedgeWatch's detector does on every 13F-HR the moment it lands — and why the convention errors that hide in micro-caps, covered in institutional ownership in micro-cap stocks, don't slip through.

a 13F error isn't always a mistake in the numbers — it's often a faithful entry under the wrong convention. that's why these are never auto-corrected, and why verification has to happen on the reader's side.

faq

what are the most common errors in 13F filings?: the recurring ones are the pre-2023 thousands-convention error (positions reported 1,000× too small), stale or wrong CUSIPs that map to the wrong ticker, omitted or confidentially-treated holdings, single rows mis-scaled up or down, and mislabeled option or share-type fields.
what is the 13F thousands-convention error?: since january 3, 2023 the SEC requires 13F values in whole dollars, but some funds still file in the old thousands convention. a $10 million position is then written as the number 10,000, and any tool reading it as whole dollars shows it 1,000× too small.
how can i tell if a 13F has a data error?: verify each position with shares times the quarter-end price and compare it to the reported value. a ~1,000× gap means the thousands convention; an issuer name that doesn't match the resolved ticker means a CUSIP problem; an implausible value means a mis-scaled row.
do funds correct 13F errors?: sometimes, by filing an amendment (13F-HR/A). but many errors are never corrected because they are technically faithful to how the fund entered the data — the filer used the wrong convention, not the wrong numbers. screeners then inherit the error.
why do screeners show wrong 13F data?: most screeners ingest the filing's value field at face value and assume every filer follows current rules. when a filer doesn't — wrong units, stale CUSIP, mislabeled option — the screener faithfully displays the wrong number with no flag.

related_reading

get_access

hedgewatch reads every 13F-HR the second it files — detecting the unit-convention error that hides real institutional positions, and surfacing the true size with the filing receipts attached. access is invite-only and reviewed by hand.

or read the api reference and pricing.

// hedgewatch research

the hedgewatch research desk parses every 13F-HR filing on SEC EDGAR as it lands — comparing each holding's reported value against shares × quarter-end price. these guides come from reading the raw filings directly, not from secondary summaries.

this page is informational and educational only and does not constitute investment advice. all figures are derived from public SEC EDGAR filings; quarter-end prices are approximate. verify every figure against the primary filing before acting on it.