2026 updates

The 2026 Filer Manual update: where XBRL guidance moved

The October 6, 2026 effective rule moved technical XBRL submission guidance into the EDGAR XBRL Guide. Update your production reference library.

Sources checked 2026-10-21 · AI-assisted; no named human review recorded

Illustrative digital document research workspace
AI-generated illustration. Not an SEC document, office or endorsement.

A filing checklist is only as reliable as the references behind it. The SEC's updated EDGAR Filer Manual rule became effective on October 6, 2026. It incorporates Volume II, Version 78, dated September 2026, and explains that technical XBRL submission information is moving from Chapter 6 into the EDGAR XBRL Guide. Read the adopted rule.

Why a reference change matters

A team can follow a familiar checklist and still consult an obsolete technical chapter. The practical risk is version drift: the conversion provider, tagging specialist and filing agent may be working from different saved documents. A reference-library update is therefore a production-control task, not just a bookmark change.

The SEC describes the moved material as highly technical information about submitting Inline XBRL documents. Do not infer that the move removes tagging obligations or changes every disclosure requirement. The rule concerns the manual and related filing procedures; the applicable reporting rules still need to be read separately.

Replace a single-manual habit with a reference map

Keep a short reference map for each filing workflow. It should identify the applicable form instructions, the current Filer Manual, relevant technical specifications and the tagging guidance used for the package. Record the version or retrieval date rather than naming a file only as "latest manual."

  • Disclosure owner: applicable form and substantive reporting requirements.
  • Conversion owner: document construction and permitted-format requirements.
  • Tagging owner: EDGAR XBRL Guide and applicable taxonomy resources.
  • Submission owner: current filing-system instructions and acceptance messages.

These are suggested operational responsibilities, not a substitute for your organization's formal delegation of authority.

Other changes in the same release

The rule also discusses corrections to the Form 13F and 13F-CTR cover-page template references and the introduction of electronic interfaces for ANE Exception Notices and Form 1 variants. Those changes are targeted; they are not a new universal deadline for all SEC filings.

For affected filers, the adopted rule states that ANE Exception Notices and withdrawals must move to EDGAR on January 1, 2027. Form 1 and related variants have a March 2, 2027 electronic-filing transition date. The rule describes earlier live and test availability beginning September 14, 2026. Teams in those workflows should read the detailed provisions, including access requirements, instead of applying an operating-company checklist unchanged. Transition details in the rule.

A small audit with a useful output

Take one recent production instruction and follow every reference it contains. If a link points to an archived manual, replace it with the current official entry point. If the instruction quotes Chapter 6 for detailed XBRL mechanics, verify where the relevant requirement is now documented. Note the owner who will maintain each reference.

The useful deliverable is a dated one-page reference register, not a large policy document. Include the reference title, official URL, applicable workflow and next review trigger. A new EDGAR release or an important change in filing scope should trigger another check.

Before your next conversion request

Tell your provider which reference set the filing team is using. An older template may still be a helpful layout starting point, but it should not silently become the authority for technical compliance. Follow the current Filer Manual entry point and the SEC technical specifications to resolve version questions.

Primary sources & scope

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.

FROM RESEARCH TO PRODUCTION

Have an approved document
that needs a clear next step?

Tell us the filing type, source format and target timing.
Keep confidential files and credentials out of the public form.

Discuss your project ↗