SEC compliance data from EDGAR and XBRL

SEC compliance data is public, but public access is not the same as usable compliance infrastructure. EDGAR, XBRL APIs, filing indexes, and bulk archives expose the records. Teams still need parsing, normalization, source references, and review notes before the data can support monitors or AI workflows.

Short answer: Use SEC compliance data by mapping the filing type, source endpoint, entity identifier, parsed fields, source record, and review path. Start with EDGAR search, CompanyFacts/XBRL, filing indexes, or bulk archives, then attach source records to every alert or extracted value.

This map shows what is available, where it lives, and how to make it reviewable.

What SEC compliance data covers

The SEC's EDGAR system contains filings from roughly 150,000 entities: public companies, investment funds, asset-backed trusts, broker-dealers, and investment advisers. There are about 16,000 registered investment advisers alone.

For compliance purposes, the filings that matter most break into a few categories:

Corporate filings

10-K: annual reports. Financial statements, risk factors, MD&A, executive compensation. The most comprehensive disclosure a public company makes.

10-Q: quarterly reports. Same structure as 10-K but for interim periods. Less comprehensive but more frequent.

8-K: material events. Triggered by specific events: executive changes, acquisitions, earnings, material agreements. These are time-sensitive and must be filed within four business days of the event.

DEF 14A: proxy statements. Board composition, executive compensation, shareholder proposals. Required before annual meetings.

Fund filings

NPORT-P: quarterly portfolio holdings. Every registered investment company, including mutual funds and ETFs, files complete position-level holdings with every security, CUSIP, and dollar value. This is the filing that DealCharts parses for its fund holdings data.

N-CEN: annual fund census data. Registration details, service providers, fee structures.

Structured finance

ABS-EE: asset-backed securities. Loan-level data for securitized pools such as auto loans, mortgages, credit cards, and CLOs. Filed at issuance and updated monthly or quarterly.

Insider activity

Forms 3, 4, 5: insider ownership and transactions. Required when officers, directors, or 10%+ shareholders buy or sell company stock.

Where the data lives

All of this is on EDGAR, but EDGAR is not one tidy system. It is a collection of systems built over 30 years. Knowing which endpoint to use for each job saves a lot of time.

EDGAR full-text search

The EFTS API lets you search across all filings by keyword. It is useful for finding specific disclosures or entities by name. Rate-limited to 10 requests per second.

CompanyFacts API

The CompanyFacts API returns structured XBRL data for any company by CIK. Financial statement line items, standardized, with dates. This is the best endpoint for quantitative fundamental data.

Filing index

The filing index lets you browse all filings for a given entity by type and date range. Returns links to the actual filing documents.

XBRL viewer

The SEC's inline XBRL viewer renders financial data from filings with tagged line items. It is useful for human review but not great for automation.

Bulk data

For large-scale processing, EDGAR provides bulk download archives organized by quarter. These are the raw filing packages; you need to parse the XML/XBRL yourself.

Available is not usable

All of this data is accessible. Very little of it is ready to use.

NPORT-P filings are XML documents buried inside filing archives. To get fund holdings, you need to download the archive, find the right XML document, parse it, map the fields, and normalize the output. Per filing. For thousands of funds. Every quarter.

10-K and 10-Q filings contain XBRL-tagged financial data, but the tagging is inconsistent across companies, fiscal years, and even between different sections of the same filing. Getting consistent time-series data out of XBRL is a real engineering problem.

8-K filings are semi-structured at best. The event types are standardized (Item 1.01, Item 2.01, etc.), but the content is free text. Extracting structured information requires either manual review or NLP. NLP without source references creates another trust problem.

This is the gap we have been filling. DealCharts parses NPORT-P filings into structured JSON: fund identifiers, holdings with CUSIPs and dollar values, asset categories, filing dates. Every data point links back to the source filing by accession number. The search API and facts endpoints give you the parsed data directly, no key required, under a CC-BY 4.0 license.

For CMBS and ABS deals, the same pattern applies: loan-level data parsed from ABS-EE filings, organized by deal, and traceable to source.

Building compliance monitoring on SEC data

Once the data is structured, monitoring becomes a pipeline problem. We use this architecture:

Detect

Poll EDGAR for new filings. The ATOM feeds update in near-real time. When a new 10-K, 8-K, or NPORT-P appears for a tracked entity, the pipeline picks it up.

Parse

Extract structured data from the filing. For XBRL filings, map the tagged data to canonical fields. For XML (NPORT-P, ABS-EE), parse the document structure. For free-text (8-K items), extract the structured elements and flag the rest for review.

Compare

This is where the value is. Compare the new filing against the prior state. What changed? Did a company's risk factors expand? Did a fund's top holdings shift? Did a BDC's portfolio concentration increase?

The comparison requires temporal versioning. You need to know what the system believed before the new filing arrived. Without that, you can detect new filings but you cannot detect changes.

Alert with source records

Every alert links back to the source filing. A useful alert says: Company X filed a 10-K on 2026-03-10 (accession 0001234567-26-000789), compared against the prior filing from 2025-03-11, with links to both documents and a summary of what changed.

That alert can be reviewed. An examiner can verify it. An AI agent can cite the exact filing.

What this looks like in practice

Our SEC Filing Monitor runs this pipeline for any set of companies. You pick your issuers, choose your filing types, select a delivery channel (email, Slack, webhook), and the system monitors EDGAR continuously.

Every notification includes a link to the source filing, a summary of what changed, and a source record that captures the detection chain: when the filing appeared, when it was parsed, what was compared, and what was delivered.

For fund holdings, DealCharts runs the same pipeline at scale. Thousands of NPORT-P filings are parsed into structured JSON, searchable by fund name, and queryable by API. The data is used by portfolio managers, data vendors, and AI systems that need fund holdings with inspectable source links.

For AI systems

If you are building AI applications on SEC data, the compliance data layer is the foundation. An LLM can summarize a filing. A RAG pipeline can retrieve relevant disclosures. An agent can monitor for changes.

All of those capabilities require structured, traceable data underneath. The model is only as trustworthy as its inputs, and outputs cannot be audited if the inputs do not carry source references.

This is why we built the SEC EDGAR MCP Server, a Model Context Protocol server that lets Claude, Codex, or any MCP client query EDGAR filings in natural language. The structured data layer does the heavy lifting. The AI system gets clean inputs with source attribution. The compliance team gets outputs they can verify.

SEC compliance data is free. Making it reviewable is the hard part. That is where we spend our time.

SEC compliance data FAQ

Where can I find SEC compliance data?

SEC compliance data is publicly available through EDGAR, including full-text search, CompanyFacts XBRL APIs, filing indexes, and bulk archives. Use the endpoint that matches the filing type and preserve the accession number or source URL with each extracted record.

What SEC filings matter most for compliance monitoring?

Common monitoring targets include 10-K, 10-Q, 8-K, DEF 14A, NPORT-P, N-CEN, ABS-EE, and Forms 3, 4, and 5. The right set depends on whether you track public companies, funds, structured finance deals, or insider activity.

How do you automate SEC compliance monitoring?

A reviewable SEC monitor detects new filings, parses EDGAR or XBRL records, compares the new filing with prior state, and delivers an alert that keeps the filing link, timestamp, parsed fields, comparison method, and review path together.

---

Related:

• SEC Filing Monitor - Automated EDGAR monitoring with source records
• SEC EDGAR MCP Server - Query filings from Claude, Codex, or any MCP client
• Regulatory State, Not Filings - Why the maintained record matters more than filing alerts
• SEC EDGAR API Guide - CompanyFacts endpoint, CIK lookup, and Python examples
• How to Look Up ETF Holdings - Fund holdings from NPORT-P filings via API
• Is Data Lineage Required for Compliance? - The broader regulatory picture