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.

EstoniaFinantsinspektsioon

Estonia moves DORA incident reports to joint portal from 1 November

Encrypted e-mail runs only to 31 October 2026; from 1 November DORA incident and cyber-threat reports must use the joint data-collection portal, with money fields in thousands.

By Taxxa AI OyPublished 19 October 2026

IT, Cybersecurity & Data

Industry: Financial and insurance activities

Financial entities in Estonia that file reports under the EU digital operational resilience framework must change how they submit them. Until 31 October 2026 inclusive, DORA reports go by electronic mail to intsident@fi.eeFI, encrypted with DigiDoc to the Finantsinspektsioon certificate "Finantsinspektsioon: Dokumendi kinnitus". From 1 November 2026, notices and reports on serious information and communication technology (ICT) incidents under Article 19(1) of Regulation (EU) 2022/2554 and voluntarily submitted significant cyber-threat notifications under Article 19(2) must be filed through the joint Eesti Pank and Finantsinspektsioon data-collection portal at aruandlus.eestipank.ee.FI The portal guide also keeps an e-mail route into the portal, to fiaruanded@fi.ee, with the report prepared under the reporting schema and encrypted and digitally signed.

The portal workflow runs per calendar date. The reporter first creates the filing obligation by choosing report 4422 DORA intsidentide aruanne and setting the period end to the incident date, or the notification date for a cyber-threat notice. Only one obligation can be created per date, and it can carry several incidents or notified threats sharing that date. Inside the obligation the reporter enters the incident number from field 2.1 of the report file, selects the report type — initial notice (a), interim reports (b1 to b5), final report (c), reclassification as non-serious (d), or significant cyber threat (CT) — uploads the XLSX file and may add a comment, for example identifying corrected information on re-submission. File names are free but should avoid diacritics, and the file must be verified before upload because no format or content check happens at that stage.

Submission is save-and-check, then submit with signature. After signature the status reads Kontrollimisel while the report moves to Finantsinspektsioon and other competent authorities; Korras means all required positive confirmations arrived, Vigadega means errors were found and the report must be corrected and re-submitted. The automatic Korras status is the Finantsinspektsioon confirmation of correct receipt within the meaning of Article 22(1), and a notification for its appearance can be ordered in the portal. If the status is still Kontrollimisel the next day, the reporter is asked to contact the portal contact person.

Follow-up and corrected reports stay inside the same date's obligation: open it, choose Muuda aruande andmeid, change the report type, add the new file, save-and-check and submit, which creates a new version. The comment field should point at the correction. Changing the incident number in field 2.1 is a special case: first reclassify the wrongly numbered incident as non-serious, then submit a new initial notice with the new number under the same date. Interim and final reports submitted together go out as the final report, and where several incidents share one obligation they must be matched by incident number.

Two filing details apply to every report. Percentage fields convert automatically and assume a dot decimal separator, so an Excel set to comma decimals needs reconfiguring (File, Options, Advanced, Editing options: clear Use system separators, set Decimal separator to a dot). Monetary values in fields 3.11, 4.13 and 4.14 must be stated in thousands.FI Forms are in English but may be completed in Estonian or English using the 24 January 2025 templates, following the joint European Supervisory Authorities guidance on serious ICT incident reporting. In case of doubt whether the serious-incident threshold is met, the incident must be reported; it can later be reclassified if analysis shows the thresholds were not met. If the initial notice cannot technically be submitted in the required form and manner, Finantsinspektsioon must be notified by another means.

Legal basis is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA), Articles 19 and 22(1).

File any DORA serious-incident or cyber-threat report concerning 1 November 2026 onwards through report 4422 in the joint data-collection portal, and state monetary fields 3.11, 4.13 and 4.14 in thousands.

Sources