EDGAR conversion quality control: 12 checks beyond appearance

A polished proof is necessary, but it is not the whole quality-control process. A reliable conversion also preserves reading order, financial meaning, links and version traceability. Technical requirements come from the relevant EDGAR instructions and Filer Manual. The checks below are a suggested production method, not an SEC certification. Official Filer Manual.

Start with the baseline: checks 1 to 3

1. Approved source: record the exact source version and the authorized approver. If the source is still changing, label the output accordingly.
2. Completeness: compare the section list, tables, notes and supplied exhibits with the conversion scope. Do not rely on a similar page count.
3. Reading order: inspect headings and paragraphs around tables, graphics and page transitions. Information should remain logically connected when viewed as a web document.

An illustrative issue is a table footnote separated from its table by a misplaced heading. The words may all be present, yet the reader's interpretation can still change. Completeness and reading-order review catch different problems.

Protect the financial meaning: checks 4 to 6

1. Numbers and signs: reconcile minus signs, parentheses, dashes, decimals and units with the approved source.
2. Table relationships: confirm that each value remains under the correct year, period and currency heading, including multi-row headings.
3. Notes and references: check footnote markers, note sequence and links between referenced material and the relevant disclosure.

Do not change a number because it appears inconsistent. Raise the issue with the authorized disclosure or accounting reviewer. Production quality control preserves approved information; it does not replace the underlying review of that information.

Test the package: checks 7 to 9

1. Links: test intended navigation and exhibit references in the package context, not only in an isolated local preview.
2. Characters: inspect symbols, smart punctuation, special characters and text extracted from scanned material.
3. Assets and filenames: reconcile included graphics and document files with the manifest and applicable document-construction requirements.

The SEC's overview explains that accepted document formats vary and that supporting graphics are part of the submission where used. Follow the actual specifications rather than assuming that an ordinary website asset is automatically suitable for EDGAR. Format overview.

Close the loop: checks 10 to 12

1. Revision reconciliation: account for every approved correction and ensure the proof is not assembled from conflicting versions.
2. Structured-data ownership: identify who handles tagging and validation where required. HTML appearance alone does not establish Inline XBRL correctness.
3. Final release evidence: associate approval with the exact files handed to the authorized submission owner and retain the submission response.

Make the checklist usable

Give each check an owner and a status such as complete, query open or not applicable. A checkbox without a reference is weak evidence; a short note identifying the proof or file version is more helpful. Keep unresolved questions visible until the appropriate person answers them.

Use a second-person review for high-risk areas when the organization's process permits it. The goal is not a universal "error-free" promise. It is a controlled, repeatable way to identify and resolve production issues before release. Acceptance by EDGAR and legal sufficiency remain separate questions from visual conversion quality.