Ask most finance teams when VAT in the Digital Age starts to affect them and you’ll hear “2030.” That’s the date in the legislation. It’s also the wrong date to plan around.
France’s e-invoicing obligation came into force on September 1 this year. Belgium switched on in January. Poland’s second phase landed in April. Germany’s first issuing deadline arrives in January 2027. None of those are ViDA deadlines in the strict sense, but all of them are consequences of it, and every one of them lands in the same place: on the people who process invoices and the people who collect the cash.
If you run accounts payable or accounts receivable in a shared services center, ViDA isn’t a tax project you’ll be consulted on somewhere down the line. It’s a change to how your process works. And the tax department is not the function that will notice what breaks.
That holds whether you’re reading this from Frankfurt or from Chicago. A US-headquartered group with a French subsidiary sits inside France’s mandate on exactly the same timetable as a French-owned business. A US manufacturer selling into Germany will be asked for a structured invoice whether or not any American regulator ever requires one. The obligation is European. The process work lands wherever your shared services center happens to be.
What ViDA actually is
The EU Council adopted the VAT in the Digital Age package on March 11, 2025. It entered into force on April 14 that year. The package covers three areas: digital reporting and e-invoicing, VAT rules for the platform economy, and single VAT registration.
The first of those is the one that reaches into your process.
From July 1, 2030, cross-border B2B transactions inside the EU must be invoiced in a structured electronic format and reported to tax authorities close to real time. Structured means machine-readable data that conforms to the European standard EN 16931. A PDF doesn’t qualify. Neither does a scanned image with good character recognition behind it.
The timings are tight. Suppliers have ten days from the chargeable event to issue the invoice, then ten days from issuing it to report. Where a member state also requires the buyer to report, that window is five days from receipt. Summary invoicing survives, but only within the same calendar month and only where the member state hasn’t flagged the supply type as fraud-sensitive.
By January 1, 2035, national systems that predate 2024, including Italy’s SdI, have to converge on the same standard. You can read the Commission’s own summary of the package on the EU taxation site.
Why 2030 is the wrong date to plan around
The part of ViDA that changed things immediately got much less attention than the 2030 headline.
Before April 2025, a member state that wanted to make domestic B2B e-invoicing mandatory had to apply to the EU Council for a derogation. That requirement is gone. Member states can now mandate domestic e-invoicing on their own timetable, and they can oblige the buyer to accept an electronic invoice rather than having to ask for consent first.
The practical result is that the pace is now set by 27 national governments rather than by Brussels. Here’s where the larger markets stand as of September 2026.
Italy has run mandatory B2B e-invoicing through the SdI platform since 2019.
Belgium went live for all businesses in January 2026 through the Peppol network, with no phasing by company size.
Poland brought KSeF in for taxpayers above PLN 200 million in revenue in February 2026, then extended it to everyone else in April. The Commission maintains a current summary of the Polish requirements.
France required every business to be able to receive structured e-invoices from September 1, 2026, with large and mid-sized companies also obliged to issue from that date. Small and micro-enterprises follow on September 1, 2027. The Commission’s France factsheet tracks the phasing.
Germany has required businesses to be able to receive EN 16931-compliant invoices since January 2025. Issuing becomes mandatory in January 2027 for businesses above 800,000 euros in turnover, and in January 2028 for everyone else. XRechnung, ZUGFeRD 2.1, and Peppol BIS are all accepted. The German factsheet has the detail.
If you operate entities in more than two of those countries, your first real deadline has either passed already or arrives next year.
What ViDA means if you’re headquartered outside the EU
The rules follow the transaction, not the head office
There are two ways a non-European company ends up inside a European mandate, and only one of them is legal.
The first is straightforward. If your group has a legal entity in France, Belgium, Poland, or Germany, that entity is subject to its country’s requirements on the same schedule as a locally owned competitor. Where the parent is incorporated makes no difference to the tax authority in Warsaw.
The second route is commercial. A US exporter with no European entity may carry no direct obligation at all, but its European customers do. Once a customer is pulling invoices from a national platform rather than an inbox, an emailed PDF stops fitting the way they work. You won’t hear about that as a compliance problem. You’ll hear about it as a payment that didn’t arrive, from a customer who can point to a system that has no record of your invoice.
Your shared services center feels it before your tax team does
Plenty of US-headquartered groups run European AP and AR from a hub in North America, or from Kraków, or from Bangalore. The obligation is European. The queue is wherever the queue is.
That split is worth planning around. The person who has to resolve a failed validation against a French platform is rarely the person who sat through the tax briefing, and the gap between those two people is where readiness programs tend to fail.
If you’ve worked in Latin America, you’ve seen this model before
For US multinationals with operations in Mexico or Brazil, the mechanics will feel familiar. Mexico’s CFDI and Brazil’s NF-e have run on clearance principles for well over a decade, where an invoice isn’t legally an invoice until the tax authority has validated it.
The European models aren’t identical, and the formats are entirely different. But the operational lesson carries over cleanly: the compliance layer and the business process have to be the same thing. Groups that bolted a separate CFDI solution onto the side of their Mexican operation generally spent the following years reconciling two versions of the same invoice.
Before you start from a blank page, it’s worth asking whether anyone in your organization has run a CFDI or NF-e implementation. That experience is more useful than most of the vendor material you’ll read.
The US is moving too, along different lines
There’s no federal US e-invoicing mandate, and nothing currently suggests one is close. What does exist is the Digital Business Networks Alliance, which operates a voluntary open exchange network for B2B documents in the United States, built on interoperable-network principles closer to Peppol than to the clearance models used in Europe and Latin America.
We’d be guessing if we put a date on wider US adoption, so we won’t. The more defensible observation is about direction. Structured, network-exchanged invoicing is becoming the default in more markets each year, and Peppol itself now reaches well beyond Europe into Singapore, Australia, New Zealand, Japan, and Malaysia. The capability you build to handle one French entity is not a single-country investment, which changes how the business case should be written.
What changes inside accounts payable
The invoice stops being something you can renegotiate quietly
In a clearance or reporting model, the invoice your supplier issues is the invoice the tax authority already holds. You can’t ask for a corrected version by email and process the second one as though the first never happened. Corrections run through credit notes, in the system of record, with their own trail.
A surprising amount of everyday AP practice depends on exactly the flexibility that’s going away. It’s worth finding out how much of yours does before a deadline finds out for you.
Exception handling becomes a clock
Ten days to issue. Ten to report. Five on the buyer side where a member state requires it. Those windows don’t pause because an invoice landed in a mismatch queue.
So the question to put to your team is a simple one: what’s our average time to resolve a price or quantity exception? If the answer is twelve days, that’s the gap. If nobody can answer it, that’s a bigger one. Teams that have already moved exception handling onto AI that can act on a case rather than just classify it are in a better position here, because the constraint stops being how many people you can put on the queue.
Data quality moves upstream
A structured invoice either passes validation or it doesn’t. There’s no keying around a missing VAT registration number, no workaround for a supplier whose master record was never cleaned up after an acquisition. Vendor master data becomes the thing that decides whether invoices flow.
That’s also true of fraud controls. Structured, validated, authority-visible invoices close off some familiar attack routes and open others, which is worth thinking through if you’re already asking what AI can and can’t catch in AP fraud.
What changes in accounts receivable
Your customer’s platform decides whether your invoice exists
Sending an invoice used to be a two-party exchange. Under most national models it becomes a four or five-corner one, routed through a platform such as the French PPF or Poland’s KSeF, or over Peppol. Your customer pulls the invoice from there.
If your invoice never reaches the platform, or reaches it in a format that fails validation, it isn’t late. As far as your customer’s AP system is concerned, it was never sent. Collections calls that begin with “we never received it” are about to get a much stronger factual basis.
Structured data is an opportunity for cash application
There’s an upside here that’s easy to miss while you’re focused on the compliance side. The same structured identifiers that satisfy a tax authority are the identifiers that make remittance matching work. Invoice references stop being free text buried in a payment advice.
That only pays off if AR is set up to capture and use them, which is one reason it’s worth revisiting how your cash application process handles structured remittance data rather than treating the mandate purely as an outbound problem. The same goes for deductions and short pays, where clean line-level data changes how quickly a dispute can be settled.
The gap most teams haven’t measured
Before you scope anything, four numbers are worth pulling.
How many invoice formats do you currently receive, counting the PDFs that arrive by email as one and the EDI feeds as separate lines? How many of your entities sit in countries with a live or announced mandate, counting Latin America and Asia alongside Europe? What proportion of your supplier master records would pass a strict EN 16931 validation today? And how long does an exception actually take to clear, measured from receipt rather than from when someone opened the case?
Most teams find the first and last numbers uncomfortable. That’s useful information, because it tells you whether this is a systems problem or a process problem before you go looking for budget.
How to prepare without building a compliance silo
The tempting move is to bolt a compliance layer onto the side of AP and AR. Buy something that talks to the national platforms, wire it to the ERP, tick the box.
It works for the audit. It also leaves you running two invoice flows: the compliant one that satisfies the tax authority, and the real one where matching, approvals, and cash application happen. Every reconciliation between those two flows is manual work you’ve just created for yourself, and it grows with every new country that goes live.
A more durable approach looks like this.
Start with where your invoices actually sit. If your process runs inside SAP, compliance handling that runs inside SAP avoids a second copy of the truth. If you’re on a mix of ERPs, or migrating, a cloud-native option that connects to all of them is the better fit. Serrala supports both, and the honest answer to which one suits you depends on your ERP roadmap rather than on anything about the mandates themselves. If S/4HANA migration is on your plan for the next two years, sequence the two together rather than doing compliance twice.
Then treat validation as part of intake, not as a separate gate. An invoice that fails a structural check should surface in the same queue as a price mismatch, handled by the same people, measured the same way.
Fix master data before the deadline rather than during it. This is the least interesting work in the program and the most likely to determine whether it lands.
And give AR the same attention as AP. Most readiness programs are written from the buying side, which is how organizations end up compliant at receiving invoices and quietly late at issuing them.
For groups operating across regions, scope the capability rather than the country. A program built to satisfy France alone will be rebuilt for Germany, then again for whatever comes next. A program built to handle structured invoice exchange as a normal part of AP and AR absorbs the next mandate as configuration, and it absorbs the ones already running in Mexico and Brazil at the same time.
None of this requires certainty about 2030. It requires knowing which of your entities is affected next year, and having a process that can absorb the country after that without a new project. That’s the same question that sits underneath aligning finance transformation with your ERP roadmap, and it’s worth answering once.
Frequently asked questions
Does ViDA apply to domestic invoices?
The July 2030 digital reporting requirement covers cross-border B2B transactions within the EU. Domestic mandates are set by individual member states. ViDA’s contribution on the domestic side was removing the need for member states to seek EU approval before introducing one, which is why national rollouts accelerated from 2025 onward.
Is a PDF an e-invoice under ViDA?
No. ViDA requires a structured electronic format conforming to EN 16931, meaning machine-readable data. A PDF sent by email is a digital document, not a structured invoice. Hybrid formats such as ZUGFeRD and Factur-X, which embed XML inside a PDF, do qualify where the national mandate accepts them.
If ViDA harmonizes everything, do we still need country-by-country compliance?
Yes, for now. Member states keep control of their own domestic systems, formats, and platforms. Systems introduced before 2024 have until January 2035 to converge on the ViDA standard. Between now and then you’re dealing with several national models at once.
What is EN 16931?
EN 16931 is the European standard that defines the semantic data model for an electronic invoice: which fields must be present and what they mean. It was originally developed for public procurement invoicing and has become the reference point for B2B mandates across the EU. A modernized version was adopted in February 2026.
Does ViDA affect businesses outside the EU?
Yes, in two ways. If you issue or receive invoices for transactions that fall within an EU member state’s VAT scope, you’re subject to that country’s rules regardless of where your headquarters sits, and non-EU groups with European subsidiaries are affected on the same timetable as everyone else. Separately, if you sell into Europe without a local entity, your customers’ platforms will effectively require structured invoices from you even where no law obliges you directly.
Does a US company with no European entity need to do anything about ViDA?
Not as a legal matter. Commercially, it depends on your customers. If you invoice European businesses, expect requests for structured formats to increase as each national mandate goes live, and expect payment cycles to stretch where you can’t meet them. The practical step is to ask your largest European customers which platform or network they’re using, rather than waiting to be told.
Is the United States introducing an e-invoicing mandate?
There’s no federal mandate and no announced plan for one. The Digital Business Networks Alliance runs a voluntary open exchange network for US B2B documents, built on interoperable-network principles rather than the government clearance model used in Europe and Latin America. Anyone predicting a US mandate date is speculating.
When do we actually need to be ready for ViDA?
Work backward from your entity footprint rather than from 2030. If you have a French, Polish, or Belgian entity, the answer is already. If your largest exposure is Germany, you have until January 2027 or January 2028 depending on turnover. Most groups with a European presence have a live obligation somewhere within the next fifteen months.
