ViDA stands for VAT in the Digital Age, the European Union's package to modernise VAT. It has three parts: digital reporting and e-invoicing for transactions between member states, VAT rules for digital platforms, and a single VAT registration. For businesses, the practical effect is that structured electronic invoices become the norm instead of PDFs.
What ViDA is trying to fix
VAT fraud and inefficiency across borders cost EU governments a great deal, and businesses carry the compliance burden of dealing with different rules in every country. A company selling into several member states can end up registered in many of them, issuing invoices in different formats and filing separate returns. ViDA is the EU's attempt to standardise that, make reporting faster, and let tax authorities see transactions closer to when they happen.
This post explains the structure of the package in plain language. It deliberately gives no dates and no thresholds. Those details are set in the legal text and by each member state, they have been adjusted during negotiation, and they differ between countries. Check the current official text or your tax adviser for the timetable that applies to you. We are an ERP and AI company, not a tax adviser, and nothing here is tax advice.
The three pillars of ViDA explained
Digital reporting requirements and e-invoicing
This is the pillar that affects most businesses. It moves towards structured electronic invoices for business-to-business sales between member states, with the data reported to tax authorities in a standard way. A structured e-invoice is not a PDF sent by email. It is a machine-readable file that carries the invoice data in fixed fields, so a system can read it without a person retyping anything. The European standard for the data model behind these invoices is known as EN 16931, and many countries build their rules on it.
Member states are also allowed to keep or introduce their own national e-invoicing systems, which is why the picture stays complicated in practice. If you trade in Europe, expect a mix of the EU framework and national rules for some time.
VAT rules for the platform economy
The second pillar changes who is responsible for collecting VAT when services are sold through digital platforms, with short-term accommodation and passenger transport as the main examples. If your business is a platform or sells through one in those sectors, this part matters. For most manufacturers, distributors and service companies, it does not.
Single VAT registration
The third pillar aims to reduce the number of separate VAT registrations a business needs in different member states. The idea is that a company can handle more of its cross-border VAT through one registration in its home country. The aim is to cut the administrative burden of trading across the EU, and the details of how it works depend on the final rules.
Not sure whether your ERP can produce structured e-invoices?
Send us how you invoice today. We will tell you honestly what your system can already do, what an adapter would need to add, and what to ask your tax adviser.
Talk to an E-Invoicing SpecialistWhat ViDA means for your invoicing system
Your ERP has to produce data, not documents
The shift is from invoices as documents to invoices as data. Your ERP must hold the fields that a structured invoice requires, such as accurate tax identifiers, tax categories, unit codes and payment details, and it must output them in the format required. Missing or inconsistent master data is the most common cause of rejection in every e-invoicing scheme we have seen, and it is far cheaper to clean up before a deadline than after.
Customer and supplier records matter more
If every invoice is validated automatically, a wrong VAT number or an incomplete address stops the invoice. Review who owns customer data in your business, how it is checked when a record is created, and who fixes it when an invoice is rejected.
Connecting to the network
Most structured invoicing schemes involve sending the invoice through a network or service provider rather than directly to the customer. Which route applies depends on the country. Treat this as an integration question: your ERP needs a reliable way to send, receive and track the status of each invoice. We explain the same pattern for the Gulf in our guide to the five-corner e-invoicing model.
How ViDA relates to other e-invoicing rules
ViDA is not the only e-invoicing change in the world, and it is not the first. Saudi Arabia, the UAE and several European countries have their own programmes, each with its own format and timetable. If you operate in more than one region, the lesson is the same everywhere: clean master data, an ERP that can export structured invoices, and a tested connection to the required network. Our posts on ZATCA Phase 2 with Odoo and whether Odoo supports UAE e-invoicing show how we approach it for those markets, and our UAE e-invoicing page has the detail.
A practical readiness plan without the dates
You do not need the final timetable to start. First, list every system that issues invoices: the ERP, a web shop, a billing tool, a spreadsheet someone still uses. Second, check which of them can produce structured data today. Third, audit your customer and product master data for missing tax fields. Fourth, ask your tax adviser which obligations apply to your countries and when. Fifth, plan the integration to a network or provider once you know which one applies.
If you run Odoo, a custom connector or adapter can add what the standard setup lacks, and our development team builds those. We would rather tell you what your system already does than sell you work you do not need.
Who is most affected by ViDA
Businesses that sell goods or services to other businesses in different EU countries feel the e-invoicing pillar first, because that is where cross-border reporting changes. Companies that already issue structured invoices in one country, for example for public-sector customers, are usually a step ahead, since they have already solved the data and network questions once. Smaller businesses that invoice only domestically may see change later and through national rules rather than the EU package directly. Platforms in accommodation and passenger transport are affected by the second pillar. Everyone else should still pay attention, because supply chains move together: if your largest customers require structured invoices, you will be asked for them whatever the legal position of your own business.
Questions to ask your software vendor
Whether you use Odoo or another system, ask your vendor four plain questions. Which structured formats can the system produce today? Which fields does it hold for tax categories and identifiers, and are they mandatory on customer records? How does it send invoices to a network, and how does it show a rejection? Who updates it when the rules change, and at what cost? A vendor who answers clearly is easier to plan with than one who says the update will arrive in due course. If your system cannot answer, a small adapter built around it is often cheaper than replacing the whole platform.
What not to assume
Do not assume ViDA applies in the same way in every member state, that your current invoicing tool already complies, or that a deadline far away means you can wait. Equally, do not rush to buy a product before you know which rules apply to you. Understanding your invoice data and your customers is useful whichever way the details land.