XBRL (eXtensible Business Reporting Language) is the SEC's structured data format for financial statements. Every S-1, 10-K, 10-Q, and most other financial filings must include XBRL-tagged financial data. The tags make individual financial data points machine-readable by investors, analysts, and SEC staff. For first-time filers, XBRL is primarily a financial printer concern — but understanding the requirements helps you evaluate printer capabilities and avoid timeline surprises.
What XBRL Is and Why the SEC Requires It
XBRL tags individual items in a financial statement — each line of the income statement, balance sheet, and cash flow statement — with standardized labels from the FASB's US-GAAP XBRL taxonomy. The tags allow the SEC's EDGAR system to extract and compare financial data across companies without manual data entry.
Since 2020, the SEC has required Inline XBRL (iXBRL), which embeds the tags directly in the HTML version of the filing rather than as a separate document. This means the human-readable and machine-readable versions are the same file. Your financial printer handles the technical tagging; what you need to understand is what gets tagged and what the deadlines are.
What Must Be Tagged in an S-1 and 10-K
The tagging requirements differ by filing type and filer category:
| What Gets Tagged | S-1 (IPO Filing) | 10-K (Annual Report) | 10-Q (Quarterly) |
|---|---|---|---|
| Financial statements (income, balance sheet, cash flows) | Yes — all historical periods | Yes | Yes |
| Notes to financial statements | Yes | Yes | Yes |
| Cover page data (company info, filer category) | Yes | Yes | Yes |
| MD&A narrative text | Not tagged | Not tagged | Not tagged |
| Risk factors | Not tagged | Not tagged | Not tagged |
| Executive compensation tables (proxy) | N/A | Yes (DEF 14A) | N/A |
The EGC XBRL Accommodation
Emerging Growth Companies (EGCs — companies with less than $1.235B in annual revenue at IPO) receive a phase-in for certain XBRL requirements. However, it is important to note what the accommodation does and does not cover:
- EGCs are still required to comply with XBRL requirements — the phase-in relates to the detailed tagging of financial statement notes, not the core financial statements themselves
- The core financial statements (income statement, balance sheet, cash flows) must be tagged by all filers including EGCs
- EGCs have phased compliance for the most granular note disclosures, which can reduce initial XBRL workload
May 2026 SEC Proposed Rule — New EGC Accommodations
In May 2026, the SEC published a proposed rule, Enhancement of Emerging Growth Company Accommodations and Simplification of Filer Status, that would further streamline reporting obligations for EGCs. The proposal is not yet finalized. Check the SEC's website for the current status before making compliance decisions. Source: XBRL.us / SEC.gov.
Inline XBRL — How It Works in Practice
The SEC requires Inline XBRL (iXBRL) — a format where the XBRL tags are embedded directly in the HTML document rather than existing as a separate XML file. This means readers see a human-readable document; machines see the embedded structured data simultaneously.
- How it looks: The 10-K or S-1 filed with the SEC is a single HTML file with XBRL attributes embedded in the code. When the SEC's EDGAR system processes the file, it extracts the tagged data and makes it searchable in its XBRL viewer.
- The EDGAR Inline XBRL Viewer: After filing, any investor can view the XBRL-tagged financial data through the SEC's interactive viewer at sec.gov. This tool lets users see exactly which elements have been tagged and compare tags across companies.
- Separate XBRL instance document: The SEC also requires a separate XBRL instance document (R9999.htm) containing the structured data extracted from the iXBRL filing — this is the machine-readable file used by financial data aggregators like Bloomberg and FactSet to populate their databases.
US GAAP Taxonomy and Custom Extensions
XBRL tagging uses a standard taxonomy — the US GAAP Taxonomy published annually by FASB — which defines thousands of standard elements for financial statement line items. Matching a financial statement line to a taxonomy element requires judgment:
- Exact match: Many common line items (Revenue, Net Income, Cash and Cash Equivalents) have direct taxonomy equivalents. Taggers use the standard element.
- Extension elements: When no standard taxonomy element accurately describes a company-specific line item, the company creates a custom extension element. Extensions are permitted but discouraged — the SEC has stated that excessive extensions suggest the company's disclosures are not comparable to peers.
- Negative labeling: Some amounts are tagged with a negative sign when the taxonomy element is defined as a positive amount in the opposite direction. Errors in sign convention are among the most common XBRL validation errors.
- Annual taxonomy updates: FASB publishes updated taxonomies annually to reflect new accounting standards. Companies transitioning to a new standard (ASC 842, ASC 326) must ensure their XBRL tagging uses the appropriate taxonomy version.
Common XBRL Errors and SEC Comments
The SEC runs automated validation on all XBRL submissions and can issue XBRL-specific comment letters. The most frequently cited errors:
| Error Type | Description | How to Avoid |
|---|---|---|
| Incorrect element selection | Using a broad element (e.g., "Other Income") when a more specific element is available | Review element definitions carefully; use the XBRL US Data Quality Committee rules as a checklist |
| Calculation inconsistency | Tagged subtotals don't sum to the tagged totals in the XBRL calculation linkbase | Run the financial printer's calculation checker before filing |
| Sign errors | An expense tagged as a positive number when the taxonomy defines it as negative (or vice versa) | Verify against the XBRL viewer after filing a test document |
| Missing required elements | Required disclosures (EPS denominator, shares outstanding) not tagged | Cross-check against the SEC's XBRL US filing rules |
| Duplicate facts | The same value tagged twice with different contexts | Review all extension elements for duplication against standard elements |
| Stale taxonomy | Using last year's taxonomy when a new standard was adopted this year | Confirm taxonomy version with the financial printer at the start of each filing |
Detail Tagging — What Changes in Year 2
The XBRL tagging requirements escalate in the second year as a public company. In the first annual report, only the financial statement face pages require full interactive data tagging (with footnotes in "block text" — the entire footnote is a single tagged element). Beginning with the second 10-K filing:
- Financial statement footnotes must be tagged in "detail" — individual facts within footnotes (specific dollar amounts, dates, percentages) each receive their own XBRL tag
- This dramatically increases the number of XBRL tags per filing — from a few hundred in year 1 to potentially thousands in year 2
- The additional work increases the financial printer's XBRL tagging fee — budget accordingly
- Companies that switch financial printers between year 1 and year 2 should ensure the new provider has the prior year's XBRL taxonomy structure to maintain consistency
EDGAR Next — What Changed in September 2025
In September 2025, the SEC transitioned to EDGAR Next, a major update to the SEC's filing infrastructure. Key changes that affect IPO companies:
- New authentication system: EDGAR Next uses a modern credential-based authentication system replacing the legacy username/password model. All filers must enroll and delegate filing access to their agents (financial printers) under the new system.
- Enrollment deadline was September 12, 2025. Companies that did not enroll faced filing delays after December 19, 2025. Your financial printer should have managed this transition for any clients that were already public.
- For new IPO filers: Your financial printer sets up EDGAR Next access as part of the IPO onboarding process. DFIN, Workiva, and Toppan Merrill all completed their own transitions and are filing on the new platform.
How Workiva vs. DFIN Handle XBRL
Workiva
Workiva's platform handles XBRL tagging as part of the S-1 drafting workflow — financial data is tagged as it is entered, linked to source systems, and validated before submission. This eliminates the traditional "send to printer for tagging" step and allows for real-time XBRL validation throughout the drafting process. Workiva's approach significantly reduces last-minute XBRL errors.
DFIN (Donnelley Financial)
DFIN handles XBRL tagging as a service — the client's financial statements are provided to DFIN's tagging team, who apply the US-GAAP taxonomy tags and return the tagged filing for review. DFIN is the #1 SEC filing agent by volume and completed its own EDGAR Next transition in August 2025, ahead of the deadline.
SEC Reference Sources
EDGAR XBRL Guide (July 2025)
The SEC staff's official guide to XBRL requirements — updated July 2025. Covers filing specifications, error handling, and filer category requirements. The authoritative technical reference.
EDGAR Filer Information
The SEC's main EDGAR filer resource page — filing forms, technical specifications, and EDGAR Next enrollment information.
Selecting a Financial Printer / EDGAR Agent
XBRL capability and EDGAR Next readiness are key criteria when evaluating financial printers. Read the full selection guide.