E-Invoicing Becomes Mandatory: The 2026–2030 Country Map

Electronic invoicing is not a PDF sent by email. Under the mandates now taking effect across Europe, an invoice is a structured data file exchanged through a defined channel and, in most countries, reported to the tax authority at or near the moment of issue. A PDF is a picture of an invoice. From the point of view of the new rules, it is not one.

That distinction is the whole practical problem. Most small businesses believe they already send electronic invoices, discover otherwise a few weeks before a deadline, and then have to change an accounting system, a web shop and a set of habits at once. This note sets out where the mandates stand as of August 2026, what actually has to change, and how much lead time each piece needs.

The three things a mandate usually requires

National rules differ in detail and agree on structure. Almost every mandate combines the same three obligations, and it is worth separating them because they arrive on different dates.

• A structured format. XML or a hybrid PDF with embedded XML, conforming to the European standard. Machine-readable by definition; human readability is a rendering, not the document.
• A defined exchange channel. Either a national platform through which invoices pass, or an interoperable network — most commonly Peppol — where accredited access points deliver documents between parties.
• Reporting to the tax authority. Either the platform reports automatically because it is the channel, or a separate real-time or near-real-time report is required.

The obligation to receive almost always lands before the obligation to issue, and it is the one businesses overlook. Being unable to receive a compliant invoice from a supplier is a commercial problem on the first day of the mandate, not a tax problem later.

The country map, as of August 2026

Dates move. This is the position in August 2026, and anything scheduled more than a year out should be treated as an intention rather than a fact.

The VAT in the Digital Age package is the reason the national timetables converge rather than diverge. Cross-border B2B transactions inside the EU move to structured invoicing and near-real-time digital reporting by the end of the decade, which is why building for a single national platform today is usually the more expensive choice.

What actually has to change on the website

Four changes cover most cases, and all four are small if done before the deadline and awkward afterwards.

1. Collect the business identifiers at checkout. A “company purchase” option that captures registered name, VAT number and legal address, validated against the EU VAT database where available. Without this, every B2B order becomes a manual correction.
2. Separate legal address from delivery address. They are different fields with different rules, and merging them is the single most common cause of rejected invoices.
3. Make order data exportable in a structured form. Your invoicing tool needs machine-readable order data, not a report designed for humans. This is usually an API question rather than a template question.
4. Store and serve the invoice as the legal document. Retention periods apply to the structured file, not to the pretty PDF. If your shop emails a PDF and keeps nothing else, that is a compliance gap and a support problem in equal measure.

These are the same integration concerns that decide whether an order flows into a CRM cleanly, and the same failure mode: data that was never collected cannot be reconciled downstream.

Who is affected sooner than they expect

Three groups are consistently caught out.

Businesses selling B2B into a mandate country. Your customer’s obligation becomes your requirement. A French or Belgian buyer will ask you to send structured invoices to their platform, and the alternative is being paid late or not at all. This includes Ukrainian and other non-EU suppliers, for whom no local mandate applies at all — the requirement arrives through the counterparty exactly as NIS2 obligations do, which is the mechanism examined in our note on how a client’s contract carries a regulation to you.

Shops that sell to both consumers and businesses. The same checkout has to produce a consumer receipt and a compliant B2B invoice from different data. Retrofitting that after launch costs several times what it costs to plan.

Anyone selling cross-border inside the EU. Cross-border B2B is precisely what ViDA targets, so a business already handling multiple countries has more to reconcile — the same population dealing with the VAT and checkout rules in our note on cross-border selling and OSS VAT.

Practical preparation, in order

The sequence matters more than the tooling, because each step depends on the previous one.

Start by establishing which mandate applies to you and on what date, from the tax authority of the country in question rather than from a vendor’s marketing page. Vendors have an interest in earlier dates and broader scope.

Then audit your data: take twenty recent B2B orders and check whether each contains a valid VAT number, a registered legal name and a legal address. The failure rate in that sample is your real project size.

Choose an exchange route next. For most small and medium businesses that means an accredited Peppol access point or an invoicing service that includes one, rather than a direct connection to a national platform. It costs less and it survives the next country you sell into.

Then fix the collection points on the website, test with a real counterparty in the target country before the deadline, and keep the structured file as the archived original.

Budget realistically: for a small business with a standard accounting package and a straightforward shop this is a few days of integration work plus a modest monthly service fee. It becomes expensive only when the order data is wrong at source or when the deadline arrives first.

Four questions for whoever supplies your accounting software

Most of this project is decided by a vendor you already pay. Ask before the deadline, in writing, because the answers determine whether the work is configuration or replacement.

1. “Which mandates do you support today, and which are on your roadmap with dates?” Supported and planned are different products. A roadmap entry three months before a deadline is a risk you are carrying, not one they are.
2. “Do you include an accredited access point, or do I contract one separately?” Bundled is simpler and usually cheaper at small volumes; separate is not wrong, but it means two suppliers pointing at each other when a document fails to arrive.
3. “What happens to a rejected invoice?” You need to know where the rejection appears, who is notified and how a correction is issued. If the answer is that a status changes silently in a screen nobody opens, your first mandated month will be unpleasant.
4. “How is the structured file archived, and can I export it?” The legal original is the XML. If it lives only inside the vendor’s platform and cannot be exported, you have made a retention obligation dependent on a subscription.

What this changes beyond compliance

Two consequences are worth planning for rather than merely absorbing.

Payment timing shifts. When invoices arrive as structured data, buyers’ systems can process them without manual entry, and the excuse of an invoice sitting in someone’s inbox disappears. Businesses that send compliant invoices tend to be paid faster; businesses that send PDFs into a mandated environment get paid last.

Error rates fall, then become visible. Structured invoices are validated on receipt, so mistakes are rejected immediately instead of surfacing at the quarter end. That is an improvement, but it front-loads the pain: the first month of a mandate typically produces a spike of rejections caused by data that was always wrong and never checked.

Key takeaways

• A PDF is not an e-invoice. Mandates require a structured format, a defined exchange channel and reporting to the tax authority.
• Receiving obligations land before issuing obligations, and they are the ones most businesses miss.
• The map as of August 2026: Italy and Romania long mandatory, Belgium since January 2026, Poland phased from February 2026, Greece from March 2026, France receiving from September 2026, Germany issuing from 2027, Bulgaria still voluntary for B2B with phased SAF-T under way.
• ViDA pulls everything towards 2030, so build for interoperability rather than for one national platform.
• The website is part of the project. Capture registered name, VAT number and legal address at the order, keep the legal address separate from delivery, and make order data machine-readable.
• Non-EU suppliers are affected through their customers, not through any local law.