EDGAR HTML and Inline XBRL are related, but they are not interchangeable descriptions of the same service. HTML provides the readable document structure. Inline XBRL embeds structured information in a document that people can also read. The SEC describes Inline XBRL as a single document serving both human and machine readers. SEC overview.
Two outputs to think about, one integrated document
A reader wants headings, tables and notes that make sense. A machine needs tagged facts with the correct reporting meaning and context. Inline XBRL joins those needs, but the work still involves distinct skills. A conversion team can preserve a table beautifully without making the accounting judgments required to select its tags.
For operating companies, the SEC's overview identifies cover-page and financial-statement information in Forms 10-K and 10-Q and describes other form-specific requirements. It also discusses certain 8-K information and other disclosures. Do not apply a blanket assumption that every filing has identical tagging requirements. Form-specific scope overview.
Define ownership before a quote
Ask whether the provider is offering source cleanup, HTML conversion, tagging, validation, filing-agent coordination or some combination. A low quote for conversion is not directly comparable with a quote that includes structured-data preparation and review.
- Who owns approved disclosure and accounting decisions?
- Who converts the source and handles layout corrections?
- Who chooses or reviews tags, contexts, units and relationships?
- Who runs technical validation and resolves the findings?
- Who authorizes the final package for submission?
The answers should be written into the handoff, especially when several providers work on the same filing.
A visible number has more than one attribute
Consider an illustrative revenue amount shown in a table. A reader sees the amount, period heading and currency label. Structured data needs to identify the fact in a way consistent with the applicable taxonomy and its reporting context. Repeating the visible amount in an HTML cell does not itself perform that work.
This distinction is useful when planning revisions. A disclosure change may require an update to the visible text, the tags or both. After a change, ask the tagging owner whether the structured-data relationships remain appropriate; do not assume an unchanged screen appearance proves that nothing else changed.
Use current technical references
The September 2026 Filer Manual update moved technical XBRL submission information into the EDGAR XBRL Guide. The SEC also announced taxonomy-acceptance changes in Release 26.3. Together, those developments make reference-version checks a sensible part of a 2026 production handoff. Manual update and taxonomy notice.
Review and validation are complementary
Visual proofing can reveal clipping, misplaced headings and broken notes. Technical validation addresses another set of issues. Neither automatically establishes that the disclosure is legally sufficient or the accounting is correct. Keep the responsible legal and accounting reviewers involved.
If your request is only for document conversion, say so. If the filing requires Inline XBRL, name the specialist responsible for that work before the deadline becomes urgent. A precise scope protects both the schedule and the integrity of the final filing package.
Primary sources & scope
- SEC — Inline XBRL overview and form-specific scope
- SEC — Adoption of Updated EDGAR Filer Manual, Release 33-11438 (effective October 6, 2026)
- SEC — EDGAR 26.3 Release XBRL Taxonomies Update (September 15, 2026)
Prepared with AI assistance from the linked sources. Operational examples are illustrative, not claimed client results. Requirements can change; verify current official instructions and obtain appropriate professional review before acting. How this resource is produced.
