Norway SAF-T version, period and mapping errors

Open this fictional error →Local rule-only example; choose Check locally. Official XSD validity remains unverified.

Use the source line and XML path to fix the ERP generator, then inspect each validation layer.

Choose the financial version explicitly

Skatteetaten publishes the Norway SAF-T Financial schemas in its own repository. Its current documentation allows 1.40 already and requires it from 1 January 2027. The older 1.20 and 1.30 forms remain available for earlier financial years through 2026. This tool deliberately supports only 1.30 and 1.40. A shared Norway namespace alone does not identify the version, so the selected version must agree with Header/AuditFileVersion.

NO-VERSION-YEAR flags a 1.30 extraction or transaction assigned to a financial year after 2026. A 1.40 historical export is not rejected simply because the year precedes 2027. Changing the header version string cannot migrate the underlying structure. Regenerate from the ERP using the appropriate exporter, then validate every layer again with an authorised original schema when available.

Read the extraction interval

SelectionCriteria can provide a date interval or an accounting-period interval. NO-PERIOD identifies missing, invalid or reversed boundaries. The date check uses real calendar dates, so a string shaped like a date is not enough. For a date extraction, the independent preflight compares GLPostingDate with the selection interval. TransactionDate can differ and is checked for being a real date without assuming it must equal the posting date.

The fictional period error moves GLPostingDate from 5 November to 5 December while keeping the extraction in November. NO-RECORD-PERIOD locates the posting-date field. Decide whether the extraction boundaries or the source posting belong to a different period. For an accounting-period selection the checker compares the period/year pair. Period zero and periods above twelve produce a review warning: special periods need the accounting calendar and are not automatically equated with calendar months.

Check mapping presence and references separately

NO-ACCOUNT-MAPPING checks that GroupingCategory and GroupingCode are present on accounts. NO-VAT-MAPPING checks that each supplied TaxCodeDetails has a StandardTaxCode. A transaction’s TaxType and TaxCode are matched as a pair against TaxTable; a missing pair triggers NO-TAX-REFERENCE. Multiple matching details need review because effective dates and tax rates require context. The sentinel NA also creates a review warning rather than proving a valid tax treatment.

These are independently written completeness and link checks. They do not establish membership in official code lists, the correct tax percentage, the meaning of the selected account grouping or financial correctness. The examples intentionally use invented DEMO mapping values. The restricted Regnskap Norge account descriptions are not redistributed. Obtain suitable mapping material and rights separately and have the accounting configuration reviewed by someone with the needed context.

Separate XSD evidence from business evidence

The XSD-error fixture adds UnexpectedForTest at the end of AuditFile. Our independently authored test subset rejects it at that line. This is teaching evidence, not an official Skatteetaten XSD result. The rule-only demo executes no XSD. With an authorised complete local schema, the report records the original-byte SHA256, supplied metadata and schema result separately. Unknown profiles never receive full green approval, including when the syntax is well formed.

One file is free; Pro and Team batches use existing limits and isolate a malformed file. CSV and JSON exports include versions, scope, layers and provenance. XML content, amounts and identifiers remain local and are not analytics fields. Reports do not automatically repair financial values.

Primary sources and scope

Skatteetaten version documentation and the official 1.30 schema / official 1.40 schema were rechecked on 6 November 2026. The repository rights notice restricts standard-account list use. Public access and a free reference validator do not establish blanket commercial rights. No official schemas or protected rules are distributed here. Each supplied artifact requires concrete sufficient processing rights and notices.

These checks establish no tax assessment, audit acceptance, actual submission or full financial correctness. Opening and closing balances, foreign-currency conversion, official list membership and SourceDocuments business rules remain unchecked. SAF-T delivery is commonly requested for inspection; this guide does not advertise a mandatory monthly return.

Norway SAF-T validator → · Developer scope