Reference

Validation-category reference

Interpret structural, data-quality, cross-template, taxonomy, and jurisdiction findings.

Version 2026.8.1Administrator · Preparer · ReviewerReviewed 2026-07-25

Structural and required-data findings

Identify missing facts, invalid types, unusable contexts, or required reporting structures. Check applicability and source completeness first.

In-table findings

Compare values within one template, such as totals, signs, ranges, or mutually constrained cells.

Cross-template findings

Compare facts across selected templates. A correction can belong in either source fact, so inspect the complete relationship.

Calculated-field findings

Explain a mismatch or missing dependency in a product calculation. Correct the inputs rather than the displayed calculated output.

Taxonomy or formula findings

Come from rules implemented for the pinned taxonomy package. Read the rule identity and disclosed coverage; not every source formula is necessarily executable in the current product.

Jurisdiction findings

Apply only to the selected authority profile and implemented national forms or validations. Profile-specific evidence and readiness requirements can also block export.

Severity and disposition

Severity communicates product classification, not an automatic legal conclusion. Follow organization policy for correction, evidence, escalation, and review. A finding should never be hidden merely to reach approval.

Related tasks

Your privacy choices

We use essential storage for security and preferences. With your permission, PostHog EU measures filing steps and records a privacy-masked session replay so we can find and fix usability bottlenecks. Replays hide all text, form contents, media, console logs and network contents. This helps us improve SolvencyBridge.

Privacy details