A United States Securities and Exchange Commission (SEC) registrant submits a 10-K in Inline XBRL (iXBRL, where XBRL is the eXtensible Business Reporting Language) to the Electronic Data Gathering, Analysis, and Retrieval system (EDGAR). EDGAR runs the file through `validate/EFM`, a rule pack that checks the filing against three taxonomies layered together: United States Generally Accepted Accounting Principles (US-GAAP), the SEC Reporting Taxonomy (SRT), and Document and Entity Information (DEI). Each carries a different slice of the vocabulary, and treating them as interchangeable is one of the more common mistakes a newcomer makes.
The legal instrument is Regulation S-T together with the EDGAR Filer Manual (EFM), Volume II Chapter 6, the SEC's binding technical rulebook and the closest American counterpart to a European Regulatory Technical Standard (RTS). Where the ESEF RTS fixes format and taxonomy for European issuers, Regulation S-T and the EFM fix them for anyone filing with the SEC. One routing detail matters when you chase a rule to its source: the current manual moved the detailed XBRL requirements into the companion EDGAR XBRL Guide, and the familiar `EFM.6.05.*` identifiers survive as validator codes that reference the legacy numbering.
The Financial Accounting Standards Board (FASB) issues the US-GAAP Financial Reporting Taxonomy: assets, liabilities, equity, revenue, expenses, segment reporting, and the bulk of the statement-level vocabulary an issuer needs. Two companion taxonomies fill in what US-GAAP does not cover. SRT supplements US-GAAP with concepts and axes useful specifically for SEC filings, among them statement-presentation axes and reconciliation concepts. DEI carries cover-page metadata instead of financial facts: `dei:DocumentType`, `dei:EntityRegistrantName`, `dei:EntityCentralIndexKey`, `dei:EntitySmallBusiness`, and `dei:EntityEmergingGrowthCompany` are typical examples. Whether a filing carries every DEI fact a given document type requires surfaces as the legacy-numbered validator code `EFM.6.05.40` when incomplete (the requirement itself now lives in the EDGAR XBRL Guide); a segment axis, by contrast, almost always belongs to US-GAAP or SRT, since DEI has no financial-statement role at all.
The entry point decides the Discoverable Taxonomy Set (DTS): the filer's own extension schema imports the US-GAAP, DEI, and SRT versions for that filing, drawn from the SEC's published list of accepted Standard Taxonomies. The rule is to pick one mutually compatible release family: a 2026 taxonomy is compatible only with other 2026 taxonomies, so mixing a stale US-GAAP edition with a current DEI edition does not merely look sloppy, it produces an invalid DTS that EDGAR rejects at acceptance, long before any comment letter.
Custom, or extension, concepts are common in US-GAAP filings but are not the SEC's preference. The EDGAR XBRL Guide (carrying the legacy EFM 6.11 and 6.12 material) governs how an extension has to be built: its schema, presentation, calculation, definition, and label linkbases must all be wired correctly, or the filing fails validation under the `EFM.*` code family. Longstanding SEC guidance pushes filers toward the base US-GAAP concept before reaching for an extension, and persistent overuse of extensions where a perfectly good base concept already exists is exactly the kind of pattern that draws a comment letter, independent of whether the extension itself is technically well formed.
The practical payoff for a reviewer is a short checklist. Check that DEI cover-page facts are complete for the document type before looking at anything else, since `EFM.6.05.40` fires first and loudest. Check that US-GAAP, SRT, and DEI are all drawn from the same accepted vintage. And before accepting an extension concept, ask whether US-GAAP or SRT already declares the base concept the filer reinvented; if it does, the extension is the defect, not a legitimate customization.
The legal instrument: United States Securities and Exchange Commission (SEC) registrants file Inline XBRL (iXBRL, where XBRL is the eXtensible Business Reporting Language) under Regulation S-T. The filing platform is the Electronic Data Gathering, Analysis, and Retrieval system (EDGAR), and the EDGAR Filer Manual (EFM), Volume II Chapter 6, is the binding technical rulebook — the American counterpart of a European Regulatory Technical Standard (RTS). Detailed XBRL requirements now live in the companion EDGAR XBRL Guide; the familiar EFM.6.05.* identifiers survive as validator codes referencing the legacy numbering.
The Financial Accounting Standards Board (FASB) issues the Financial Reporting Taxonomy for United States Generally Accepted Accounting Principles (the US-GAAP taxonomy). Companion taxonomies — the SEC Reporting Taxonomy (SRT) and Document and Entity Information (DEI) — cover SEC-specific concepts.
DEI carries cover-page concepts (DocumentType, EntityRegistrantName, EntityCentralIndexKey, EntitySmallBusiness, EntityEmergingGrowthCompany). Incomplete cover pages surface as the legacy-numbered validator code EFM.6.05.40; the requirement itself now lives in the EDGAR XBRL Guide.
SRT supplements US-GAAP with concepts useful for SEC reporting (statement-presentation axes, reconciliation concepts).
The entry point decides the Discoverable Taxonomy Set (DTS): the filer's own extension schema imports the us-gaap, dei, and srt versions drawn from the SEC's published list of accepted Standard Taxonomies. Pick ONE mutually compatible release family — a 2026 taxonomy is compatible only with other 2026 taxonomies, so mixing vintages produces an invalid DTS at EDGAR acceptance, not merely a style problem.
Custom (extension) concepts are common in US filings; the EDGAR XBRL Guide (carrying the legacy EFM 6.11/6.12 material) governs extension structure (schema, presentation, calculation, definition, label). Validators speak the EFM.* code family.
3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.