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 moves Y-codes; new export error logged

From 12 September Y-codes belong in data element 12 04 except Y128 in 12 03, and pre-lodged IM/D declarations need review. Toldstyrelsen also logged error TMA-2648 on invalidating exited export declarations.

By Taxxa AI OyPublished 4 September 2026

Tax

Industry: Across industries

Import declarants using DMS must place Y-codes in data element 12 04 after the service updateToldst on 12 September 2026Toldst. The exception is Y128, the CBAM account-number code, which stays in data element 12 03.Toldst Toldstyrelsen says declarations of types IM/A and IM/D with wrongly placed codes will fail after the change.Toldst

The change also reaches declarations lodged in advance. Where an IM/D declaration was completed before 12 September with the affected Y-codes in 12 03 and the goods are presented after the update, the GPR presentation message fails.Toldst Only that message is rejectedToldst, so the declaration can be corrected and presented again, and it can be amended both before and after the GPR message is sent. Declarants with IM/D declarations completed before the update but presented after it should therefore correct the Y-code placement first. A declaration still uncorrected at the update produces a goods registration (vareregistrering) instead.Toldst

The DMS Export error log gained a new known errorToldst on 31 August 2026: an export declaration already marked as exited (udpasseret, TMA-2648) cannot be invalidated and stays in the exited statusToldst. On contact, Toldstyrelsen notes in the system that the declaration should stand as invalidated and will complete the invalidation once the system allows it.

The 12 September update is also expected to fix the B2 outward-processing package-count defect: a B2 declaration currently accepts at most 8 in package count per goods item (data element 18 06 004 000), rejecting higher values with "Must be less than or equal to 8 (DK)"Toldst. Until fixed, declarants must spread goods and package counts across several goods items with no more than 8 packages each.Toldst On the import side, the same update is expected to fix the additions-and-deductions defect where changes to data element 14 04 000 000 at header level fail to trigger a recalculation of the customs debtToldst: the interim response is to invalidate the declaration and submit a new one with corrected data, or to submit a correction deleting the header-level entry and placing it at item level insteadToldst.

The current transit instructions require either the principal's EORI number or the principal's name and address details, not both.Toldst The log (TMA-2398) records a validation defect that currently accepts all those fields together without rejecting the declarationToldst; the stated correct completion is one of the two alternatives.

The source is Toldstyrelsen's rolling DMS status page with update, error and interim-workaround instructions for DMS Import, Export and Transit.

Review Y-code placement on pending import declarations before the 12 September update and use the stated workarounds for exited-export invalidation, B2 package counts and header-level additions and deductions.

Sources

Opdateringer, fejl og midlertidige arbejdsgange i DMS