Validation Rules

Validation is now split across two surfaces:

• Legacy v1 validation For the older statement-shaped filing model.
• Canonical v2 validation For the current fact-centric filing model.

If you are building new integrations, use canonical v2 validation.

Canonical Validation

The main entry point is:

import { validateCanonicalFiling } from '@sureshake/sfrs-validator';

const result = validateCanonicalFiling(filing);

The result contains:

• valid
• errors
• warnings
• info
• summary

Validation Layers

Canonical v2 validation currently checks:

1. document integrity
2. entity and identifier integrity
3. taxonomy presence
4. context integrity
5. unit integrity
6. fact integrity
7. footnote linkage
8. relationship linkage
9. profile-specific requirements

What Is Checked

Document Layer

Examples:

• document.version must match the canonical model
• document.documentType must be a supported canonical type
• document.profile must be present for profile-aware validation

Context Layer

Examples:

• facts must reference existing contextRef values
• contexts must contain a valid period definition
• dimensional qualifiers must be structurally valid

Unit Layer

Examples:

• numeric facts should reference known units
• unit definitions must contain valid measures

Fact Layer

Examples:

• a fact cannot be both populated and nil
• numeric facts should carry the right reference structure
• concept and context references must resolve

Footnotes And Relationships

Examples:

• footnotes must point to existing facts
• footnote relationships must resolve correctly
• non-footnote relationships must point to supported targets

Profile Checks

The current prerelease includes profile-level checks for:

• sec-us-gaap-annual
• ifrs-esef-annual

These checks currently enforce a first profile layer, including:

• required identifier schemes
• required headline facts
• profile compatibility for packaging/export flows

That is useful, but it is not yet full submission-grade conformance.

Severity Levels

Example

import { validateCanonicalFiling } from '@sureshake/sfrs-validator';

const result = validateCanonicalFiling(filing);

console.log(result.valid);
console.log(result.summary.errorCount);
console.log(result.errors.map((issue) => issue.code));

API Validation

You can also validate through the API:

{
  "document": {},
  "modelVersion": "v2"
}

Endpoint:

• POST /api/v1/validate

When modelVersion is set to "auto", the API will try to detect canonical v2 documents automatically.

What Validation Does Not Yet Claim

Canonical validation is still prerelease. It does not yet claim:

• full regulator-ready conformance
• full taxonomy/disclosure coverage across real public filing corpora
• complete jurisdiction packs beyond the currently registered profiles

Read the current milestone entry in Release Notes together with validation claims.