How to Prepare for EU ViDA: A Practical Checklist for Businesses

ViDA — VAT in the Digital Age — entered into force on 14 April 2025. Mandatory cross-border e-invoicing under EN 16931 arrives on 1 July 2030. That is roughly four years away. It sounds like plenty of time, but companies that wait until the last moment then discover their ERP cannot produce a structured invoice, their accountant has never heard of PEPPOL, and the implementation takes longer than anyone expected.

This article is practical. I will walk you through the steps that make sense to take now — not in a panic a year before the deadline.

What ViDA Actually Brings

I covered the detailed breakdown of the pillars and the full timeline in a separate article on ViDA. Here I will only summarise the key dates so the checklist makes sense without jumping between tabs.

• 14 April 2025 — ViDA entered into force. Member states may introduce their own e-invoicing obligations under certain conditions without EU approval.
• 1 January 2030 — the mandatory recipient consent for e-invoices is abolished; member states may require domestic e-invoicing without exception.
• 1 July 2030 — mandatory EN 16931 e-invoicing for cross-border B2B transactions within the EU; invoice within 10 days of the taxable event and simultaneous digital reporting.
• 1 January 2035 — older national systems introduced before 1 January 2024 (Italy, Poland, France and others) must align with the ViDA model and EN 16931.

The Czech Republic does not yet have a national B2B e-invoicing mandate. If you invoice into Poland, however, the obligation is already live — KSeF has been mandatory since February 2026 for large VAT payers and since April 2026 for all others.

Checklist: What to Do While You Have Time

1. Map Your Invoice Volume and Types

Before anything else, find out how many invoices you issue and receive per year, which countries they go to, and what share are cross-border B2B transactions within the EU. ViDA 2030 applies to cross-border B2B. If you mostly invoice within the Czech Republic and only occasionally abroad, your priorities and scope of preparation will differ from a company that invoices heavily into Poland, Germany, or France.

This step does not take long and gives you a concrete number: how many invoices will need to be in EN 16931 format from 2030. Without it, you do not know what you are actually dealing with.

2. Check Whether Your ERP Supports EN 16931

EN 16931 is the European semantic data model for e-invoices. It is not a specific XML file — it is a standard from which various national profiles derive (UBL, CII, PEPPOL BIS Billing 3.0, etc.). Your ERP or invoicing software must be able to generate an invoice conforming to this model.

Ask your ERP vendor directly: "Can you export an invoice according to EN 16931? In which format and from which version?" If the answer is vague or they send you a marketing link, push for a concrete output sample and the version of the standard it targets.

If your ERP handles invoicing only as PDF or proprietary XML, now is the time to find out what the vendor's roadmap looks like — and if the roadmap is absent, to start looking for alternatives or a conversion middleware layer.

3. PEPPOL Readiness

PEPPOL is the network for exchanging electronic documents. PEPPOL BIS Billing 3.0 is the EN 16931 profile that is today the standard for cross-border invoices in the EU and for B2G supplies in the Czech Republic. Being PEPPOL ready means: having access to the network via a certified PEPPOL access point, and being able to send and receive invoices in PEPPOL BIS Billing 3.0 format.

Check whether your ERP or invoicing system has a native PEPPOL connector, or whether you will need middleware. You do not run a certified access point yourself — it is a third-party service that connects you to the network.

If PEPPOL means nothing to you today, this is a good time to at least get familiar with it. Implementing a PEPPOL connector is not trivial, especially if your system has not produced structured invoices before.

4. Audit the Invoice Lifecycle from Issuance to Archiving

Trace the full invoice lifecycle: how it is created, who approves it, how it reaches the recipient, how incoming invoices are received, where they are stored and for how long. ViDA does not just bring a different format — it brings reporting at the moment of issuance. That assumes the invoice exists as a data structure before it is sent, and that the system tracks every state it passes through.

Look for steps in the invoicing process that depend on manual intervention — someone exports a PDF, sends it by email, another person manually re-enters it into a different system. Every such step is a weak point that will become a problem when structured reporting is mandatory.

5. Solve Durable Sending

This is the technical point businesses underestimate most. A structured e-invoice sent to a clearing system or directly to a recipient via PEPPOL is not like sending an email. If the send fails, the system must know what state the invoice is in and be able to retry — without creating a duplicate on the recipient's or tax authority's side.

You need:

• Idempotent sending — each invoice has a deterministic identifier; retrying a send does not create a duplicate.
• Retry with exponential backoff — transient network errors or system outages are handled automatically, not by manual intervention.
• Reconciliation — a periodic check that every sent invoice received an acknowledgement. Without it, you do not know what silently fell through.

This is not excessive. It is the same machinery you need today for KSeF in Poland — and for the same reason: government systems have outages, rate limits, and asynchronous acknowledgement. We covered why fire-and-forget is not enough using KSeF as the example.

6. Monitor National Mandates in Countries You Invoice Into

ViDA is an EU framework. The specific obligations in any given country depend on how that country implements it. Poland has KSeF, Italy has SdI, France is rolling out Chorus Pro and preparing its extension. Germany launched a national e-invoicing obligation on 1 January 2025 for receiving invoices, and from 2027 for issuing them as well.

If you invoice into multiple EU countries, you need to track the legislation of each separately. The ViDA 2030 deadline is shared, but national mandates arrive earlier and have their own specifics — schema, clearing system, time limits.

Set up an alert for legislative updates in at least the countries you invoice into regularly. It does not have to be complex — following official journals or checking the status quarterly with a tax adviser who has international practice is enough.

How We Help

This is the area where clients come to us. Either because they are dealing with KSeF for the Polish market right now, or because they want to build their invoicing system on EN 16931 and PEPPOL from the start — not rebuild it again in 2029.

Specifically, we do:

• Invoicing flow audit — we review your system and identify the weak points from a ViDA and structured e-invoicing perspective.
• KSeF integration — for companies invoicing into Poland. Durable pipeline with idempotency, retry, reconciliation, and monitoring. See our production experience with 15,141 recovered documents.
• PEPPOL integration — connecting your system to the PEPPOL network via a certified access point.
• EN 16931 in Business Central — if you use Microsoft Dynamics 365 Business Central, we know how to configure and extend it for structured e-invoicing.

If you do not know where to start, the simplest entry point is a short audit — we review your current state and tell you what the priority is. Get in touch.

FAQ

The Czech Republic does not yet have mandatory e-invoicing. Do I need to deal with this now?

Not necessarily — if you invoice exclusively within the Czech Republic and the obligation will not reach you before 2030 via the cross-border route. But if you invoice into Poland, you are dealing with it now because of KSeF (mandatory since February and April 2026). And if you are touching your invoicing system anyway — for a new ERP, an integration, anything — it makes sense to target EN 16931 and PEPPOL directly, rather than a format you will have to map again in a few years.

When exactly will the obligation arrive in the Czech Republic?

The Czech Republic has not announced a national B2B mandate yet. ViDA gives member states the option to introduce their own obligations from 14 April 2025, but the Czech Republic is still waiting. The hard European deadline for cross-border B2B is 1 July 2030. The Czech Republic may set a national obligation for domestic invoices from 1 January 2030, but when and how it will do so is not yet known. Monitor legislative updates or consult a tax adviser.

What is EN 16931 and how does it differ from ISDOC or KSeF?

EN 16931 is the European semantic standard — it defines what data an invoice must contain and what each field means. PEPPOL BIS Billing 3.0 is a specific technical profile of that standard for cross-border exchange. ISDOC is the Czech national format, KSeF FA(3) is the Polish one — both are independent dialects that are not automatically equivalent to EN 16931 and will be mapped to it over time. If you are building or selecting an invoicing system today, aim for EN 16931 as your baseline.