SEC STRUCTURED DATA

Inline XBRL (iXBRL) Tagging

Your financial statements, footnotes, and cover pages, tagged accurately, validated against SEC and data-quality rules, and proofed before they file. We handle the structured-data layer so your EDGAR filing goes through clean the first time.

Full-Service iXBRL Tagging

Inline XBRL is no longer optional or a separate exhibit you can tackle later. It is embedded directly in your 10-K, 10-Q, 8-K, 20-F, or 40-F and filed at the very same moment. Get it wrong and you risk EDGAR rejections, data-quality flags, and SEC comment letters. Get it right and your numbers are machine-readable for the SEC, investors, and analysts exactly as you intend.

We provide end-to-end tagging as part of your EDGAR filing, or as a standalone service if you draft your own documents. Either way, you approve a rendered proof before anything is transmitted.

Financial statement tagging: every line on the face of the statements, detail-tagged to the correct standard elements.
Detailed footnote tagging: both block-text and element-level tagging of the notes, the heaviest part of the job.
Cover-page & DEI tagging: the cover-page data (entity name, CIK, ticker, filer status) required on 10-K, 10-Q, 8-K, 20-F and 40-F.
Taxonomy selection & extensions: correct supported taxonomy version, minimal, well-justified custom elements.
Validation: EDGAR Filer Manual (EFM) checks plus the XBRL US Data Quality Committee (DQC) rule set.
Rendered proof: you see exactly how the tagged report renders in the SEC viewer before it files.
Get an iXBRL quote

Bundled with your filing or standalone. Revisions to the proof are included.

XBRL vs. Inline XBRL: what's the difference?

XBRL

eXtensible Business Reporting Language, an open, global standard that attaches a machine-readable tag to each reported value, capturing what it is, its period, and its unit. Historically it was submitted as a separate set of data files alongside the human-readable filing.

Inline XBRL (iXBRL)

The current format. The tags are embedded directly inside the HTML document, so one file is both human-readable and machine-readable. There is no longer a standalone XBRL exhibit to reconcile against the document; the document is the data.

"Structured data"

The SEC's term for disclosure submitted in a defined, tagged format that computers can read and compare without re-keying, the opposite of a flat PDF. It powers EDGAR's full-text search, financial-statement data sets, and the financial report viewer.

Important: XBRL data is treated as filed (not merely furnished) for liability purposes. It is read by the SEC, investors, and data aggregators, so the tagged values need to match your statements exactly.

Who has to file in iXBRL, and on what forms

The phase-in is over. Every category of operating-company filer, including smaller reporting companies, is now fully subject to Inline XBRL. If your form carries financial information, it almost certainly carries tags.

Operating companies
  • • Form 10-K & 10-Q (statements + cover)
  • • Form 8-K (cover page on every 8-K; financials when applicable)
  • • Registration statements (S-1, S-3, S-4, S-11) once they carry the required financials
Foreign private issuers
  • • Form 20-F (US GAAP or IFRS)
  • • Form 40-F (Canadian MJDS filers)
  • • Cover-page tagging applies here too
Funds & others
  • • Mutual funds: risk/return summaries
  • • Closed-end funds & BDCs: Form N-2 items + cover
  • • Employee plans: Form 11-K financial statements

What actually gets tagged

Core financial reporting

  • • Face of the financial statements, detailed and line-by-line
  • • Footnotes / notes: block-text and detailed element tagging
  • • Financial statement schedules
  • • Auditor name, location and PCAOB Firm ID (annual reports)

Cover page & entity data

  • • Cover-page data on 10-K, 10-Q, 8-K, 20-F, 40-F
  • • Document & Entity Information (DEI): name, CIK, ticker, filer status
  • • Filing-fee exhibits, tagged in iXBRL

Newer tagged disclosures

Good to know

Detailed footnote tagging is the part most filers underestimate. Every number and many narrative values inside the notes must be tagged individually, not just summarized, which is where most of the time and most of the errors live.

Proxy · 10-K · 10-Q

ECD Tagging

Pay-versus-performance (Item 402(v)), award-timing (Item 402(x)), and the quarterly trading-arrangement flags (Item 408(a)), tagged using the SEC's ECD taxonomy.

Learn more
10-K · 20-F · 8-K Item 1.05

CYD Tagging

Annual cybersecurity risk-management and governance disclosures plus material-incident reporting, tagged using the SEC's CYD taxonomy. No exemptions.

Learn more

Taxonomies we work in

A taxonomy is the standardized dictionary of elements you tag against. The US GAAP taxonomy is republished by FASB every year, and EDGAR only accepts supported versions, so picking the right one matters.

US GAAP (GRT)

FASB Financial Reporting Taxonomy. We file on the current SEC-supported version: the 2026 taxonomy (accepted by EDGAR since March 2026), with 2025 still supported.

DEI

Document & Entity Information: the cover-page and entity-identifying data set.

SRT

SEC Reporting Taxonomy: schedules, dimensional axes/members, and SEC-specific disclosures.

IFRS

For foreign private issuers reporting under IFRS on Form 20-F.

ECD

Executive Compensation Disclosure: pay-versus-performance, award timing, and trading-arrangement tagging. Full details →

CYD

Cybersecurity Disclosure taxonomy for the 10-K/20-F and 8-K cyber items. Full details →

CEF

Closed-End Fund taxonomy for N-2 tagging by CEFs and BDCs.

Filing on a retired taxonomy is a common cause of EDGAR errors. SEC staff encourage using the most recent version; support for the 2024 taxonomies is being retired around mid-2026.

Where filings go wrong, and how we prevent it

Wrong or over-extended elements

Creating a custom ("extension") element when a standard one exists hurts comparability and draws scrutiny. We map to standard elements first and justify every extension.

Broken calculations & sign errors

Calculation and dimensional (axis/member) relationships are the most error-prone area. We validate that totals foot and signs are correct before filing.

EFM + DQC validation

We run every filing through EDGAR Filer Manual checks and the XBRL US Data Quality Committee rule set (the same free DQC checks the SEC's own quality signals draw on) to catch issues before submission.

Rendered proof, every time

Tagging that validates can still render wrong. You review the report exactly as the SEC viewer displays it, and approve, before we transmit.

Why it's worth the care: inaccurate tags don't trigger a flat fine, but they do propagate into investor-facing datasets, undermine your machine-readable financials, and are a recurring source of SEC comment letters and costly remediation.

When is the XBRL due?

There is no separate XBRL deadline anymore. Because the tags live inside the document, your Inline XBRL is filed at the same time as the report itself, when your 10-K, 10-Q, or 8-K is due. The old 30-day first-filing grace period and the separate detailed-footnote grace period are long gone, so the tagging has to be ready when the filing is.

Official resources

Rules evolve; these are the authoritative SEC sources we track so your filings stay current:

Note: the SEC's 2024 climate-disclosure rule (which included iXBRL tagging) is currently not in effect. We monitor its status and will tag any climate data only if and when a rule becomes operative.

Start your iXBRL project ← Back to EDGAR services