Published method

What UK Filing checks — and what it does not.

Every supported workflow separates deterministic file checks from warnings that need your judgement. The exact framework, template version and source-review date are shown before purchase.

Check framework coverage Validate a file free

Three levels of implemented checks

Structure checks

Sheets, headers, required fields, data types, date formats, field lengths and file limits. A structural error blocks a ready result.

Plausibility warnings

Duplicate identities, arithmetic differences, reporting periods and unusual changes from the prior recorded month. A warning asks for review and does not decide the business facts.

Framework-specific rules

Only rules listed for the exact verified coverage entry, such as published identifiers, allowed values and supported template combinations.

What the evidence records

The free validator can download a local report with the file hash, coverage version, checks run, known limits and findings. A paid monthly run also records compact rule and count metadata, the output hash, approval and an optional customer-entered submission reference.

A validation report or submission reference is a record of the implemented checks and customer action. It is not portal acceptance, proof of operator receipt, a legal opinion or a guarantee that the source export is complete.

How coverage stays honest

  1. An exact agreement, official template and documented rules are reviewed.
  2. Valid and invalid fixtures exercise the listed rules.
  3. The catalogue publishes the template version, verification date, next source-review date, checks and exclusions.
  4. Checkout stops automatically after the review date until the entry is checked and re-dated.
  5. A changed or unsupported framework returns to “Framework review required”.