7 Checks Before You Submit Your XBRL Filing

What goes wrong: A company prepares its filing against the prior year’s taxonomy out of habit. A concept it used was deprecated in the current version, so on submission the regulator’s system rejects the file outright — nothing about the numbers was wrong, but the filing never gets in the door.

Catch it by confirming three things before you tag anything: the exact mandate you’re filing under, the current period and taxonomy version the regulator has published for it, and that your report structure matches the framework. Treat this as a gate, not a formality.

What goes wrong: Revenue is entered as 12,500 with a decimals value that says the figure is exact — but the source statement reports in thousands, so the filing now claims revenue of twelve thousand five hundred dollars instead of $12.5 million. The number “looks right” on screen; the machine-readable fact is off by three orders of magnitude.

Catch it by reviewing periods, entity identifiers, and units/decimals/scaling together — never the fact in isolation.

1.

2.

What goes wrong: A team creates a custom element for “Net Revenue” when a perfectly good standard element already exists. Now analysts and aggregators can’t line that figure up against peer filings, and some regulators will flag the unnecessary extension in review.

Catch it by searching the base taxonomy for a standard element first, extending only when nothing fits, and adding proper labels and anchoring so any custom element is still interpretable.

What goes wrong: A cash outflow is tagged with a positive sign, or a “loss” is tagged as a positive value. The calculation may still technically validate, but the disclosure now says the opposite of what the financials mean. Flipped signs and wrong data types (a monetary value tagged as text, a date mistyped) are the most common — and most quietly damaging — tagging errors.

Catch it by mapping each tag to the correct concept (not just a plausible-looking one), verifying signs and value types line by line, and confirming nothing required was silently left untagged. This is exactly where AI-assisted tagging in Integix cuts manual rework and the errors that ride along with it.

What goes wrong: Assets don’t equal liabilities plus equity because one component was tagged twice. A well-formedness check says the file is fine; a calculation-consistency check catches that the numbers don’t add up. Skip the second and the error travels straight to the regulator.

Catch it by running validation for missing/duplicate/inconsistent facts and calculations, invalid relationships and dates, and the mandate’s own rule set (SEC EDGAR Filer Manual checks, ESEF rules, and so on). Purpose-built review and validation in XOR is built to surface these before submission — a basic technical check isn’t enough.

What goes wrong: A lengthy note — say, accounting policies — is captured as a single text block, but in the iXBRL viewer it renders as run-together text with collapsed tables and lost line breaks. Every fact is valid and the file passes validation, but a person opening the filing sees a garbled, hard-to-read disclosure. Validation checks the data; it doesn’t check whether the document is readable.

Catch it by opening the rendered iXBRL in a viewer and actually reading it — confirming tables and text display cleanly, that the human-readable page matches what’s tagged, and that every section the form requires to be tagged is present. Rendering affects usability and trust even when the file is technically valid.

What goes wrong: Three drafts sit in a shared folder. A late edit corrects a number in draft 3, but at submission someone uploads draft 2. The filing is now accurate in every respect except that it’s the wrong version — and it’s already live with the regulator.

Catch it by reviewing every change with a clear trail, reconciling the final file to the approved statements, and confirming that the correct submission version is being used. XOR adds an extra safeguard by warning users if they attempt to download an older version for final submission, helping reduce the risk of the wrong file being submitted at the finish line.

1.

2.

3.

Tag accurately. Review thoroughly. File confidently.

See how Ez-XBRL makes your next filing accurate, validated, and governed — from taxonomy selection through final sign-off.

Book a Demo

•

•

•