Make SAF-T testing a maintained dependency.

A defect in one export implementation can affect files from many customer businesses. Saftlint packages the test knowledge as a maintained, versioned dependency instead of something every product team builds alone.

If your software generates SAF-T

You probably already maintain some combination of:

• XSD validation and mapping checks.
• Reference and reconciliation checks.
• SAF-T fixtures and regression tests.
• Interpretations of the Norwegian Tax Administration's documentation.
• Migration tests between SAF-T versions.

Local testing with Saftlint

• Run locally. Financial data stays in your environment.
• Run in CI. Catch regressions before release.
• Pin the ruleset. The same rules produce the same result in reproducible builds.
• Receive maintained releases. Checks, fixtures, code lists and SAF-T versions are updated together.
• Dispute a finding. We investigate the source, document the interpretation and turn resolved cases into regression tests.

Web validator or local evaluation?