What sources does Taxxa search?

Taxxa searches a continuously updated collection of more than one million pages from tax authorities, government publications, legislation and case law across the European jurisdictions it covers. Every response cites the underlying material, so a professional can inspect the rule, its jurisdiction and whether it is current before relying on the result.

Can Taxxa work with a team’s own documents?

Yes. Research can combine the public knowledge base with a team’s own PDF, DOCX, CSV and TXT files in one workspace. That makes it possible to compare a client document with the relevant guidance, trace a conclusion to its source and prepare a draft without losing the evidence that supports it.

Who is Taxxa built for?

Accountants, auditors, tax advisors, payroll specialists, bookkeepers and advisory teams working across European jurisdictions. Shared workspaces keep research available to colleagues, and citations make review easier.

Where is customer data stored, and is it used to train models?

Customer data stays in the European Union and is never used to train language models.

Does Taxxa replace professional judgement?

No. Taxxa is a research and drafting workspace. It helps professionals reach an informed starting point faster; the professional still reviews the evidence and makes the final decision. It does not file returns, post bookkeeping entries or give legal advice.

NorwaySkatteetaten

A-melding reconciliation API changes response formats on 12 October

Null-valued fields will disappear from responses, and all date-time fields will gain a time zone. Both changes are already available for testing before the production rollout.

By Taxxa AI OyPublished 11 September 2026

Payroll & Labour

Systems consuming Skatteetaten's a-melding reconciliation-report API need to be ready for two response-format changes scheduled for production on Monday 12 October 2026Skatteetaten. Fields with null values will be omittedSkatteetaten, while all date-time fields will include a time zoneSkatteetaten. Skatteetaten says both changes have already been deployed to the test environmentSkatteetaten.

The first change affects integrations that assume a field will always appear in a response, even when its value is null. That assumption will no longer match the API's behaviour: a null-valued field will not be included at allSkatteetaten. The authority expressly says that solutions relying on those fields always being present must be adapted.

For development and testing teams, the practical task is to check how the reconciliation-report consumer handles a missing field. Include responses with omitted fields in compatibility testing, and check any validation or processing that currently expects an explicit null value. The change concerns the presence of the field in the response, so a check limited to the value of a field that is present would not cover the announced behaviour.

The second change concerns every date-time field. These fields currently lack a time zoneSkatteetaten; Skatteetaten says a time zone will be added as required by the OpenAPI specification. Teams should therefore test the parts of their integration that read and process date-time values against responses from the updated test environment, alongside their checks for omitted fields.

The testing and production stages are distinct. The new behaviour is already available for testingSkatteetaten, while 12 October is the announced production changeoverSkatteetaten. Use that interval to check both changes together and adapt affected consumers before the production release. Payroll teams relying on a supplier's integration should establish whether that supplier has tested the revised reconciliation responses and completed any necessary adjustments.

Skatteetaten announced the changes in “Ny versjon av avstemmingsrapport-API”, published on 11 September 2026.

Test reconciliation-report responses for omitted null-valued fields and time-zone-bearing date-time values, and adapt affected integrations before 12 October 2026.

Sources

Ny versjon av avstemmingsrapport-API