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.

DenmarkToldstyrelsen

DMS 12 September update: Y-codes move, '0' rejected, deadline 12 October

From 12 September DMS moves Y-codes to data element 12 04 (except Y128), rejects '0' in supplementary units with a transition to 12 October, and carries the H7 Y199 gap into the new section.

By Taxxa AI OyPublished 16 September 2026

Tax

From the 12 September 2026 DMS update, all Y-codes except one move to a new fieldToldst: they must be entered in Supplerende reference kode (data element 12 04 002 000)Toldst instead of Dokumenttype kode (data element 12 03 002 000)Toldst. The exception is Y128, the CBAM account number, which stays in 12 03 002 000Toldst. Declarations filed incorrectly (IM/A and IM/D) fail after 12 September 2026Toldst.

The presentation message (GPR) fails too when an IM/D declaration completed before 12 September with Y-codes (other than Y128) still in 12 03 002 000 is presented after that dateToldst. Only the presentation message is rejectedToldst, so the declaration itself can be corrected and presented again, both before and after the message was sent. A declaration not corrected before 12 September whose goods are presented via Manifest instead generates a goods registration (vareregistrering)Toldst.

The same update tightens validation of supplementary units (data element 18 02 001 000) on pre-lodged declarationsToldst: the value 0 is no longer accepted at presentationToldst. A filer who ignores the warning and presents without removing the 0 has the presentation rejected with the message that supplementary units must have a value greater than zeroToldst, but can correct the declaration and submit again. Two scenarios apply depending on timing. Pre-lodged declarations filed before 12 September 2026 are rejected automatically at presentation because supplementary units must not be zeroToldst; the filer must create a correction, remove the 0 and present againToldst. This route only matters during a 30-day transitionToldst ending 12 October 2026Toldst Toldst. Pre-lodged declarations filed on or after 12 September 2026 trigger a non-rejecting warning already at filingToldst; the filer must correct the declaration on the basis of the warning before presentationToldst.

The long-standing H7 gap for document type Y199 has moved verbatim from the August list into the new 12 September section: when completing Supplerende reference document type (12 04 000 000) on an H7 declaration, the type is chosen from a drop-down list that lacks Y199Toldst, so it cannot be statedToldst, and system-to-system filings that do state Y199 are rejected because the type is absent from the code listToldst. A fix is expected with the update.

Basis: Toldstyrelsen's overview of completed DMS updates with the 12 September changes, and its notice on where Y-codes go after 12 September.

Move Y-codes to data element 12 04 before 12 September, strip any '0' from supplementary units on pre-lodged declarations, and diary 12 October for the end of the transition.

Sources