Evaluate Saftlint in your own environment.

Saftlint can be supplied as a JAR or native CLI. Both let software vendors run the same XSD and ruleset on their own SAF-T files without sending them to saftlint.no.

Delivery: JAR for Java 21 or newer, or native CLI
Execution: Locally or in CI
Output: Readable report, JSON, exit code and validation receipt
Network: No activation or network access during validation

How it is used

saftlint validate report.xml
saftlint validate --json report.xml
saftlint validate --receipt report.xml

Exit code 0 means no errors, 1 means validation errors and 2 means a parsing or execution error. The web validator and local edition use the same XSD and semantic ruleset.

Web validator or CLI?

	Web validator	Saftlint CLI
Use	Manual check of one file	Development, regression testing and CI
Data	File is sent to saftlint.no	File remains in your environment
Interface	Browser	CLI, JSON and exit codes
Automation	Not offered	Yes

Included

XSD validation for Norwegian SAF-T Financial 1.40
42 semantic checks with stable rule IDs
Text report and machine-readable JSON output
Deterministic validation receipts and documented exit codes

Maintenance

The licence includes maintained releases with updated checks, code lists and documented interpretations. When the Norwegian Tax Administration publishes a new SAF-T version, such as 1.50, the engine and migration material are updated for it.

Delivered releases continue to work offline. The licence applies per software product and includes 12 months of updates and rule support.

Interested in evaluating Saftlint locally? Contact kontakt@saftlint.no.