EDGARAPI.AIFind an API
Implementation guide · Reviewed 2026-08-10

XBRL: structure without false simplicity.

XBRL turns disclosures into machine-readable facts. It does not automatically make every company, period and accounting concept comparable.

A fact is a contextual observation

A useful record includes concept, value, unit, entity, period, dimensions, filing and accession. A revenue fact might look like:

{
  "concept": "us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax",
  "value": 391035000000,
  "unit": "USD",
  "period": { "start": "2024-09-29", "end": "2025-09-27" },
  "form": "10-K", "accession": "..."
}

From source facts to comparable views

  1. Store immutable as-reported facts and contexts.
  2. Select the correct filing, period, unit and dimensional context.
  3. Map issuer extensions only when accounting meaning is defensible.
  4. Build standardized statements downstream and retain the mapping lineage.

Extensions and dimensions

US GAAP concepts provide shared vocabulary; issuer extensions represent disclosures that do not fit it. Dimensions can split one concept by geography, segment or product. Discarding them may turn a component value into an apparent consolidated total.

Failure modes

  • Mixing instant and duration periods.
  • Comparing USD with shares, ratios or differently scaled units.
  • Double-counting amended and original filings.
  • Selecting a segment fact when a consolidated fact was intended.
  • Assuming two differently named extension concepts are equivalent.

Start with Company Facts and official SEC access; compare deeper structured-data options such as EdgarTools and Calcbench.

Choose with evidence

Build on SEC data without guessing.

Compare 10 providers