Why we validate before the supervisor does

Every reporting team knows the worst moment in the cycle: the submission is in, the deadline has passed, and the supervisor’s systems answer with a list of validation errors.

The errors were knowable all along. The EBA publishes its validation rules — thousands of them — together with a severity for each: some findings block a submission, some are warnings the supervisor expects you to have considered. The rules are not the problem. Finding out too late is the problem.

Sigill’s position is simple: the same checks the supervisor runs after the deadline should run in your report view before it.

• As you type: sign conventions, datatypes and the EBA’s consistency checks are evaluated live in the grid, pinned to the exact cell — not to a line number in a rejection file.
• Before you file: the full taxonomy validation runs server-side with Arelle, the same processor supervisors use, so the result you see is the result they will see.
• With the right severities: blocking and warning come from the EBA’s own validation rule list, filtered by your reference date — retired rules do not haunt your report.

The submission that leaves Sigill is one you have already seen pass. That is what the seal means.