--- title: "CUSIP Basics: The 9-Character Security ID for 13F Readers" type: learn slug: cusip-basics-9-character-security-id-13f-reader-guide canonical_url: https://13finsight.com/learn/cusip-basics-9-character-security-id-13f-reader-guide published_at: 2026-05-13T04:49:00.996Z updated_at: 2026-05-13T04:49:04.601Z author: Sarah Mitchell author_title: Education Editor author_url: https://13finsight.com/authors/sarah-mitchell word_count: 1080 locale: en source: 13F Insight --- # CUSIP Basics: The 9-Character Security ID for 13F Readers > CUSIP is the 9-character identifier that anchors every 13F filing line, every 13D filing, and every Form 4 transaction. Tickers can change, company names can rename, but a CUSIP stays put. Here's how the format works, why mixed-case CUSIPs matter, and what to watch for when joining datasets. Every line item on a 13F filing, every share class cited in a Schedule 13D, and every transaction on a Form 4 carries a 9-character CUSIP. The CUSIP is the durable security identifier. Tickers change when a company renames, gets acquired, or relists; company names drift in spelling and capitalization across filings; CUSIPs do not. If you are joining institutional ownership data across quarters, across filer types, or across data vendors, the CUSIP is the join key that survives.It is also a common source of subtle bugs. CUSIPs are case-sensitive in some data systems, mixed-case in their canonical form, and occasionally re-used across structurally different securities (Class A vs Class B, ADR vs common). This is a short reader's guide to what CUSIPs mean, how they are structured, and where they trip up institutional-ownership joins.What a CUSIP isCUSIP stands for Committee on Uniform Securities Identification Procedures — a U.S. and Canadian standard administered by CUSIP Global Services. Every publicly-traded security in the U.S. has a CUSIP. The format is fixed:Total length: 9 characters.First 6 characters: the issuer base — same across all securities issued by the same legal entity.Characters 7-8: the issue identifier — different securities from the same issuer (Class A, Class B, preferred, convertibles, notes) carry different combinations here.Character 9: a check digit calculated from the prior 8 characters via a standardized algorithm.Example: Apple Inc.'s common stock CUSIP is 037833100. The base 037833 identifies Apple. The 7-8 issue characters '10' identify common stock. The check digit '0' validates the prior 8.Mixed-case CUSIPs are realThis is where joining institutional data trips most retail readers. CUSIPs are not always pure numeric. Many CUSIPs contain alphabetic characters in the first 6 issuer-base positions or in the issue characters. Two examples:NVIDIA Corp common stock: CUSIP 67066G104. The 'G' is uppercase letter.Meta Platforms Class A: CUSIP 30303M102. The 'M' is uppercase letter.Many SEC filings store CUSIPs in mixed-case in the raw XML, and downstream data warehouses sometimes normalize them inconsistently — some uppercase everything, some preserve the source casing, some lowercase the alphabetic characters. The same security can appear under 67066G104, 67066g104, or 67066G104 in different tables. Case-sensitive joins on mixed-case CUSIPs are the single most common cause of phantom 'zero holdings' rows in 13F data.The fix is uppercase-on-write at the data ingestion layer, paired with case-sensitive joins downstream. The platform our team runs normalizes CUSIPs to uppercase at extraction and joins are case-sensitive after that point.Why CUSIPs matter for 13F readersThree structural reasons CUSIPs anchor every serious institutional-ownership join:1. Tickers change; CUSIPs persistConsider any company that has gone through a name change, ticker change, share-class restructuring, or corporate inversion. The ticker symbol on the prior filing may no longer exist. The CUSIP base (first 6 characters) typically does. Joining a 2020 13F position to a 2026 13F position by ticker is unreliable; joining by CUSIP base is durable.2. Multi-class share structures are CUSIP-distinguishableCompanies with Class A and Class B common stock issue them as separate CUSIPs. The first 6 characters (issuer base) match; characters 7-8 differ. When a Form 4 reports Class A and Class B activity, the CUSIPs make the distinction explicit even when the share-class disclosure language in the filing is ambiguous.3. CUSIPs survive corporate actions cleanlyA 2-for-1 stock split, a special dividend, a tracking-stock spinoff — these events leave the issuer's CUSIP intact for the surviving security and assign new CUSIPs to any spun-off securities. The 13F holdings table reflects the surviving CUSIP in the next quarterly filing. Joining across the corporate action with a CUSIP key works automatically; joining by share count or value requires manual reconciliation.CUSIPs vs CINS, ISIN, SEDOLFour security-identifier formats appear in cross-border institutional data. Quick reference:CUSIP: 9 characters. U.S. and Canadian securities. SEC filings use CUSIPs almost exclusively.CINS: 9 characters, CUSIP-format. CUSIPs for non-U.S./non-Canadian securities issued under the CUSIP system. First character is always a letter (e.g., 'G' for British issuers).ISIN: 12 characters. International Securities Identification Number. The middle 9 characters of an ISIN are a CUSIP or CINS for U.S./Canadian/CINS-eligible securities.SEDOL: 7 characters. London Stock Exchange identifier. Used heavily in European data systems; not used in SEC filings.For SEC-filings-driven institutional ownership work, CUSIP is the primary key. ISIN is occasionally useful when joining to international data; SEDOL and CINS show up rarely in retail-facing US-equity workflows.Where CUSIPs appear on 13F InsightEvery holding record on the platform carries a normalized uppercase CUSIP. Every stock page URL accepts either a ticker or a CUSIP — the 9-character CUSIP route is the canonical path because it survives ticker changes. Filer holdings tables, holder rosters, and 13D/G filing endpoints all expose the CUSIP for downstream joins.Practical example: a stock page for AAPL resolves to Apple Inc. The same data is reachable via the CUSIP route /stocks/037833100. If the ticker changes in the future, the CUSIP URL keeps working; the ticker URL may redirect or stop resolving.Watch-outsThree CUSIP-specific gotchas worth keeping in mind:Re-use after retirement. When a security is retired or merged out of existence, its CUSIP can occasionally be re-assigned to a new security years later. Production data systems guard against this by versioning CUSIPs against an effective-date range. Retail-facing tools usually don't, so a CUSIP join across decade boundaries deserves a sanity check.Case sensitivity in mixed-case CUSIPs. Already discussed above; the most common source of phantom zero-holdings rows.CUSIP base collision across unrelated issuers. Extremely rare — CUSIP Global Services manages the namespace to prevent it — but historical filings can show the same base on two technically distinct entities if one was a predecessor. The check digit and the issue characters disambiguate, but a base-only join (first 6 characters) is unsafe across long historical windows.A working readIf you are looking at a 13F holding line and want to verify it joins cleanly to other data:Read the full 9-character CUSIP. Uppercase any alphabetic characters.Check the issue characters (positions 7-8) for share-class signals. Common stock typically '10' or '20'; preferred and convertibles usually different.Use the CUSIP as the join key against other 13F filings, 13D/G filings, and Form 4 records. Tickers and company names should be display-only.The 9-character CUSIP is the most underrated tool in retail-facing institutional-ownership research. Knowing how it is structured turns brittle ticker-based joins into durable security-identifier joins.FAQWhat is a CUSIP?CUSIP is a 9-character identifier assigned to publicly-traded U.S. and Canadian securities. The first 6 characters identify the issuer, characters 7-8 identify the specific issue (share class, preferred, convertible), and the 9th character is a check digit. The format is administered by CUSIP Global Services. ## FAQ ### What is a CUSIP? CUSIP is a 9-character identifier assigned to publicly-traded U.S. and Canadian securities. The first 6 characters identify the issuer, characters 7-8 identify the specific issue (share class, preferred, convertible), and the 9th character is a check digit. The format is administered by CUSIP Global Services. ### Why are some CUSIPs mixed-case (containing letters)? CUSIPs are alphanumeric — they can contain letters in either the issuer base or the issue characters. NVIDIA's CUSIP (67066G104) and Meta's (30303M102) are common examples. Different data systems sometimes normalize the case inconsistently, which is the leading cause of phantom 'zero holdings' rows in 13F data when joins are case-sensitive. ### Why use CUSIP instead of ticker symbol for joining institutional data? Tickers change when companies rename, get acquired, or relist. CUSIPs persist through those events. Joining a 2020 13F position to a 2026 13F position by ticker is unreliable; joining by CUSIP base (first 6 characters) is durable. Multi-class share structures are also explicitly distinguishable by the 7-8 issue characters. ### How is a CUSIP different from an ISIN? An ISIN is a 12-character international security identifier. For U.S. and Canadian securities, the middle 9 characters of the ISIN are exactly the CUSIP. ISIN adds a 2-character country code prefix and a 1-character check digit suffix. SEC filings use CUSIPs almost exclusively; international data systems often prefer ISINs. ### Can a CUSIP be reused? Rare but possible. When a security is retired or merged out of existence, its CUSIP can be re-assigned to a new security years later. Production data systems guard against this by versioning CUSIPs against an effective-date range. Joining institutional data across decade boundaries by CUSIP alone deserves a sanity check on issuer name continuity. ### Where can I look up a security's CUSIP on 13F Insight? Every stock page on 13F Insight exposes the CUSIP, and stock URLs accept either ticker or CUSIP as the path parameter (the CUSIP route is canonical because it survives ticker changes). Filer holdings tables, holder rosters, and 13D/G filing endpoints all surface the CUSIP for downstream joins. --- Source: 13F Insight — https://13finsight.com/learn/cusip-basics-9-character-security-id-13f-reader-guide Author: Sarah Mitchell — https://13finsight.com/authors/sarah-mitchell Last updated: 2026-05-13T04:49:04.601Z