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.

FinlandTulli

Export declarations must switch office code on 1 October

Export declarations in UTU must switch office code FI002002 to FI002000 on 1 October 2026; old-code filings are rejected, and pre-lodged, simplified and correction cases each have their own rule.

By Taxxa AI OyPublished 25 September 2026

Tax

Industry: Across industries

The export-place office code FI002002 (Helsinki, Sähköinen Tullauskeskus, vienti) can no longer be used in the Tulliselvitysjärjestelmä (UTU) from 1 October 2026Tulli. In its place, declarations must carry office code FI002000 (Tulliselvityskeskus)Tulli. The change affects all export declarationsTulli, and a new declaration filed with the old code after the switch is rejectedTulli (follow-up and correction cases for pre-October declarations keep the original codeTulli, as detailed below).

The cutover has a hard edge in both directions. The replacement code FI002000 can only be taken into use starting 1 OctoberTulli — the current code FI002002 must be used until 30 SeptemberTulli. Filing early with the new code is therefore just as invalid as filing late with the old oneTulli Tulli, and declarants should schedule their submissions around the exact date boundary rather than switching systems in advance.

Three declaration situations need specific handling. A pre-lodged export declaration (types D, F) with presentation on 1 October or later that still carries FI002002 will error at the moment of releaseTulli: where presentation is known to fall on or after 1 October, the declaration must only be lodged after the changeTulli, and an already lodged faulty declaration requires requesting invalidation of the export declaration and lodging a replacementTulli. For simplified export declarations (two-stage lodging, C, F), the follow-up declaration (Y) carries the original code FI002002 if Tulli accepted the declaration before 1 OctoberTulli, and FI002000 if acceptance came on or after 1 OctoberTulli — the decisive moment is when the first acceptance message (FI528) arrived from TulliTulli. Where a correction or invalidation is requested after 1 October for a declaration made before it, the request carries the original code FI002002Tulli; if the old code can no longer be used technically in a correction or follow-up, a new export declaration must be lodged and invalidation requested for the originalTulli.

The switch coincides with a service break in UTU during which no customs declarations can be lodgedTulli; Tulli will announce the exact timing separately. Users of the Tulliselvityspalvelu need take no action on the code itself since it fills in automatically, but the pre-lodging, simplified-declaration, correction and invalidation points above still apply to themTulli. Note also that Tulli's 4 September 2026 customer bulletin on this change originally contained an error in the office codeTulli, now correctedTulli — anyone who configured systems on the basis of the 4 September text should re-check against the corrected notice.

Source: Tullin tiedote 25.9.2026, correcting the office code error in asiakastiedote 4.9.2026.

Switch export declarations from office code FI002002 to FI002000 for 1 October 2026, keep the original code on follow-ups and corrections of pre-October declarations, and re-check any setup based on the 4 September bulletin.

Sources

Huomioi vienti-ilmoittamisessa: vientipaikan toimipaikkakoodi FI002002 poistuu käytöstä 1.10.2026