The EU VAT Migration Playbook

Who this is for: EU-based creators, freelancers and small SaaS businesses selling digital products, services, courses or SaaS across the EU — still on legacy Taxdoo data, on a stopgap, or shopping around.

1. Where things stand — September 2026

Multiple industry sources reported that Taxdoo's VAT compliance services ended on 30 April 2026. Some commentary at the time linked the exit to the broader shift toward automated VAT compliance under ViDA (VAT in the Digital Age); treat that as industry commentary rather than a published Taxdoo statement. Nearly five months on, here's how the ground has settled.

What stays with you, and what moves — depends on your model

How responsibilities shift depends on whether you move to advisory software or appoint a full-service representative.

If you move to advisory software (VatForge is in this category): your VAT registrations, transaction data, filing responsibility, and communication with tax authorities generally remain with you (and your accountant, if you use one). The software helps you prepare; you review and file.

If you appoint a full-service representative: authorisations (Power of Attorney), authority correspondence and filing responsibility depend on the engagement and the country. Confirm in writing what transfers and what stays with you.

In both cases, keep your own copies of your VAT registration numbers, your Taxdoo export, and your existing filings. OSS records should be retained for 10 years from the end of the year in which the transaction was carried out (Article 369k).

2. Key dates

3. The 10 questions every buyer should ask

Get material commitments reflected in the provider's contract, order form or applicable service description; an informal sales email may not override the governing terms.

1. Coverage — every EU country where Taxdoo filed for you; get the list in writing (watch for BG, RO, HR, LT, LV, EE).
2. OSS and IOSS — if you use both Union OSS (intra-EU B2C) and IOSS (for eligible distance sales of imported goods in consignments not exceeding €150), confirm both are in scope.
3. Intrastat — if you move goods across EU borders, check the current Intrastat thresholds and reporting requirements in each relevant Member State, and confirm whether the provider covers Intrastat. Most digital-first tools, including VatForge, do not.
4. UK VAT — ask about UK VAT and MTD separately; most EU-only tools (including VatForge) do not cover it.
5. Filing model — full-service, assisted (e-gov APIs), or advisory (structured data you submit yourself)? Get it in writing.
6. Handover timeline — a written migration plan: any authorisations required, tax-authority notification, first parallel-validated filing.
7. Historical data — will all Taxdoo-era transactions, filings and documents be imported, and for how many years? OSS retention is 10 years (Article 369k).
8. Audit export — can the provider generate a read-only audit pack covering both eras in one file? Confirm exactly which historical records are included.
9. Languages and support hours — and response-time commitments.
10. Pricing transparency — flat vs per-transaction, per-country filing fees, per-registration fees; total cost of ownership at your volume, in writing.

4. The migration sequence

Steps 1, 2, 4 and 5 apply whether you move to software or a full-service representative; Step 3 applies only if you appoint a representative.

1. Archive your Taxdoo data properly (transactions, filings, registrations, any POA history, supporting documents) in two places. Keep OSS records for 10 years from the end of the year of the transaction (Article 369k). Not every document in a Taxdoo export is necessarily subject to the same 10-year rule — but keeping the full export is the safe default.
2. Shortlist three replacement providers and ask the 10 questions. Weight coverage, filing model and migration timeline highest. Price last.
3. If you appoint a full-service representative, sort out authorisations early — ask whether new or replacement authorisations (e.g. Power of Attorney) are required in each jurisdiction, and on what timeline. Advisory software does not require a filing POA, and switching software does not by itself require notifying every tax authority.
4. Run parallel validation for Q3 2026 — file through the new provider or process, keeping prior data as reconciliation reference. Reconcile any material differences to documented causes; do not accept an unexplained variance merely because it is a small percentage.
5. Archive everything in two places, retained for the applicable statutory retention period (10 years from the end of the year of the transaction for the OSS trail, Article 369k).

5. Replacement providers at a glance

An honest starting point — not a complete or independently ranked market comparison. VatForge is the publisher of this playbook. Provider details change, so treat the notes below as prompts to verify: confirm each provider's current pricing, integrations, filing model and geographic coverage on its own website before relying on anything here. Reviewed on 14 September 2026.

6. About VatForge

VatForge is a creator-first EU VAT compliance dashboard for EU-based creators, freelancers and small SaaS businesses selling digital products across the EU. Flat pricing (see pricing). Advisory model — VatForge prepares reviewable figures; you (or your accountant) review and file. Live since 1 September 2026.

What VatForge does: brings your connected sales data into one dashboard; tracks your €10,000 pan-EU B2C threshold; applies configured VAT rates based on available transaction and category data, for review, across 27 EU countries at the date of supply — you can sanity-check a rate with the EU VAT checker; produces reviewable OSS aggregation and per-country subtotals for SE/DE/NL/BE/FR (you enter and submit the figures through your national portal); provides a CESOP exposure indicator (informational, not a seller filing obligation or compliance determination); supports VIES validation of B2B VAT numbers; helps collect customer-location evidence under Articles 24b–24f of Implementing Regulation 282/2011, subject to the applicable presumption and evidence requirements; excludes platform-remitted / merchant-of-record transactions from your OSS figures where the platform documentation and transaction evidence establish that the platform accounted for the VAT; MCP integration for compatible AI-assistant clients (read-only); support for importing available Taxdoo-era transaction data, subject to file format and data quality; historical transaction and audit exports for supported data.

What VatForge does not do (yet): UK VAT / MTD; Intrastat; full-service filing with POA (advisory model; assisted filing via e-gov APIs is on the roadmap); Amazon FBA-specific storage/threshold mapping; a direct invoicing module (roadmap); SOC 2 / ISO 27001 certification — VatForge does not hold these (infrastructure providers hold their own; VatForge itself is early-stage and does not yet hold independent certifications, on the roadmap as we scale).

Where your data lives: EU-hosted via Supabase (Ireland). VatForge uses nine named sub-processors (see /security/subprocessors), last reviewed September 2026. VatForge's retention schedule is designed to help customers meet applicable record-keeping requirements, including the ten-year OSS record period under Article 369k. Retention and deletion are governed by VatForge's Privacy Policy, Data Processing Agreement and the customer's lawful instructions. No certifications are claimed here.

Pricing: VAT Radar — Free · EU SME Scheme — €19/mo · OSS Filing — €79/mo · VAT Operations — €249+/mo. VAT Operations is a sales-led tier — talk to us.

Disclaimer: This playbook is for informational purposes only and is not tax or legal advice. VAT rules vary by country and change frequently; verify specific obligations with a qualified adviser before acting on any decision.