E-Invoicing Mandates in Europe: A Country-by-Country Guide for AP Teams (2026 to 2030)

DocLib guide to e-invoicing mandates in Europe, with a timeline from Italy in 2019 to the EU ViDA deadline in July 2030

E-invoicing in Europe is moving from optional to mandatory, one country at a time. Italy, Romania, Germany, Croatia, Belgium, Poland, Greece and France already mandate B2B e-invoicing, and the UK follows on April 1, 2029. From July 1, 2030, the EU’s VAT in the Digital Age (ViDA) package makes e-invoicing mandatory for all intra-EU B2B transactions.

For US manufacturers, this is not only a European problem. If you have a subsidiary or branch in any of these countries, its AP team already has to receive invoices as data, validate them and post them to your ERP without anyone retyping them.

This guide draws on DocLib’s November 2026 webinar with Dokapi and on the latest official timelines. It is current as of November 2026.

Do European e-invoicing mandates apply to US companies?

Yes, through your European entities. A German GmbH, a French SAS or a Belgian branch is treated like any other local business, with no exemption for having a US parent. Each entity has to meet its own country’s receiving and sending deadlines.

  • Your European entities are in scope. An entity established in a country with a live mandate, such as Germany, France or Italy, must already be able to receive e-invoices, and must send them on that country’s timeline.
  • Your US entity is generally out of scope. National mandates mostly cover domestic transactions between businesses established in that country, so a US entity invoicing from the US is usually not covered.
  • Your European customers will still ask. AP teams that run on structured data treat a PDF as an exception, so expect European buyers to request e-invoices even where the law does not require them from you (Accounting Today).
  • ViDA widens the scope in 2030. From July 1, 2030, B2B transactions between businesses in different EU countries must be e-invoiced and reported.

A VAT registration without a local establishment can change the answer. Romania, for example, also covers VAT-registered businesses with no Romanian establishment, so confirm each entity’s position with your tax advisor.

What is an e-invoice?

An e-invoice is a structured, machine-readable invoice in a standard XML format that systems can process without manual data entry. A PDF sent by email is not an e-invoice. Neither is a paper invoice, a scan, a photo, or a Word or Excel file. Each of those still needs a person, or OCR, to turn it into data.

Three principles apply across Europe:

  • The European standard is EN 16931. National formats such as Germany’s XRechnung and the Peppol BIS Billing 3.0 format are built on it.
  • The XML is the legal invoice. Where a PDF travels with the data, the PDF is only a readable copy.
  • Exchange is automated. The invoice moves from the supplier’s system to the buyer’s system.

For AP teams, the result is faster processing, fewer errors, lower cost per invoice and a cleaner VAT position.

Why are European countries making e-invoicing mandatory?

Governments are mandating e-invoicing to close the VAT gap, see transactions as they happen, and standardize how businesses trade.

  1. Closing the VAT gap. EU member states lose billions of euros in VAT every year, much of it to fraud.
  2. Real-time visibility. Tax authorities want transaction data when the sale happens, not months later in a VAT return.
  3. Efficiency and one standard. A common European format replaces country-by-country rules, and machine-processed invoices get paid faster.

What does ViDA require by July 2030?

ViDA makes EN 16931 e-invoicing and near real-time digital reporting mandatory for intra-EU B2B transactions from July 1, 2030. The Council of the EU formally adopted the package on March 11, 2025, and it phases in through January 2035 (European Commission).

Three points matter for finance teams:

  • Cross-border comes first. The 2030 obligation covers intra-EU B2B sales. Member states can extend it to domestic transactions, and several already have.
  • Member states need no EU permission. Countries can now mandate domestic e-invoicing for established businesses without an EU derogation, and from 2030 a compliant e-invoice no longer needs the buyer’s acceptance.
  • The channel is still open. The EU has not named a single exchange network. Peppol is widely expected to carry much of the traffic, because many member states already mandate it and the infrastructure is in place.

National mandates continue alongside ViDA. That is why each country’s own timeline still decides when your entities need to be ready.

Which European countries require B2B e-invoicing, and when?

At least eight European countries already mandate B2B e-invoicing. Slovakia, Luxembourg, Ireland, the UK and the Netherlands follow between 2027 and 2030, several more are preparing their own, and every EU member state is preparing for the ViDA deadline of July 1, 2030.

CountryMust receive fromMust send fromExchange channelStatus (Nov 2026)
ItalyJan 1, 2019Jan 1, 2019 (all businesses since Jan 1, 2024)SdI government platformIn force
RomaniaJan 1, 2024Jan 1, 2024RO e-Factura government platformIn force
GermanyJan 1, 2025Jan 1, 2027 (prior-year revenue above €800,000); Jan 1, 2028 (all)Free choice: email, portal, EDI or PeppolIn force
CroatiaJan 1, 2026Jan 1, 2026 (VAT-registered businesses)Peppol, with real-time reportingIn force
BelgiumJan 1, 2026Jan 1, 2026PeppolIn force
PolandFeb 1, 2026Feb 1, 2026 (large taxpayers); Apr 1, 2026 (most others); Jan 1, 2027 (smallest businesses)KSeF government platformIn force
GreeceNot set separatelyEarly 2026 (larger businesses); Nov 2, 2026 (all others)Certified providers reporting to myDATAIn force
FranceSep 1, 2026Sep 1, 2026 (large and mid-sized); Sep 1, 2027 (SMEs and micro)Accredited platform (plateforme agréée)In force
SlovakiaJan 1, 2027Jan 1, 2027Certified delivery providersLaw approved by parliament
LuxembourgJan 1, 2028Jul 1, 2028 (large and medium); Jan 1, 2029 (others)PeppolDraft law
IrelandNov 1, 2028Nov 1, 2028 (large corporates); Nov 2029 (next phase)Peppol as defaultAnnounced, legislation pending
United KingdomApr 1, 2029Apr 1, 2029 (all VAT invoices, B2B and B2G)PeppolAnnounced, legislation pending
NetherlandsJul 1, 2030Jul 1, 2030Not yet decidedAnnounced, legislation pending
All EU (ViDA, intra-EU B2B)Jul 1, 2030Jul 1, 2030Not yet decidedAdopted

Germany: receiving since 2025, sending from January 2027

Every business in Germany has had to accept e-invoices since January 1, 2025. Businesses with 2026 revenue above €800,000 must send them from January 1, 2027, and all businesses from January 1, 2028. Germany mandates the EN 16931 format but not the channel, so Peppol is optional. The Federal Ministry of Finance also plans national e-reporting from July 1, 2030, in step with ViDA (VATupdate).

Belgium: Peppol for every business since January 2026

Since January 1, 2026, every VAT-registered business established in Belgium must send and receive structured e-invoices for domestic B2B transactions through Peppol, using Peppol BIS Billing 3.0. There is no revenue threshold and no phasing. A tolerance period for penalties ran until March 31, 2026 (Andersen Belgium). Belgium has also approved a draft law for near real-time e-reporting from January 1, 2028, which is not yet enacted.

France: e-invoicing and e-reporting since September 2026

Since September 1, 2026, every VAT-registered business established in France must be able to receive e-invoices through an accredited platform, known as a plateforme agréée. Large and mid-sized companies must also issue e-invoices and e-report transaction and payment data from that date. SMEs and micro-businesses follow on September 1, 2027 (EY). France goes further than invoicing: e-reporting gives the tax authority data on transactions that e-invoices do not cover.

Luxembourg: receiving from January 2028 (proposed)

Luxembourg’s Bill 8815, submitted to parliament on July 30, 2026, would require all businesses to receive e-invoices for domestic B2B from January 1, 2028. Large and medium businesses would issue them from July 1, 2028, and all others from January 1, 2029 (Deloitte Luxembourg). The proposal reuses Peppol, which Luxembourg already uses for public-sector invoicing. Dates may change before the bill becomes law.

Ireland: large corporates from November 2028

Ireland’s Revenue plans to require large corporates managed by its Large Corporates Division to issue e-invoices for domestic B2B and report invoice data in real time from November 1, 2028. From the same date, every Irish business must be able to receive structured e-invoices. A second phase in November 2029 extends the rules to more businesses, and Peppol will be the default network (Forvis Mazars). The program is announced; the legislation is still going through the process.

The Netherlands: domestic B2B from July 2030

The Dutch cabinet announced in September 2026 that e-invoicing will be mandatory for domestic and intra-EU B2B transactions from July 1, 2030, with domestic e-reporting from July 1, 2031 (Grant Thornton Netherlands). The exchange infrastructure is not final, and Peppol is one of the main options. Draft legislation is due for consultation in late 2026.

United Kingdom: all VAT invoices from April 2029

From April 1, 2029, the UK will require VAT invoices between businesses, and to public bodies, to be issued and received as e-invoices (HMRC policy paper). Peppol is the core framework, with HMRC becoming the UK Peppol Authority. The first phase covers e-invoicing only, with no invoice clearance or real-time reporting to HMRC (KPMG). Detailed rules and legislation are still to come.

The UK sits outside the EU and ViDA, so it runs on its own timeline. Because it chose Peppol, UK entities can join the same network Belgium already mandates and Luxembourg and Ireland plan to use.

Italy, Romania, Poland, Greece and Croatia: mandates already live

If you have entities in any of these countries, the mandate already applies.

  • Italy has required B2B e-invoices through its government platform, the Sistema di Interscambio (SdI), since January 2019, and for businesses of all sizes since January 2024 (European Commission).
  • Romania has required B2B e-invoices through its RO e-Factura platform since January 1, 2024. The tax authority validates each invoice before the buyer receives it (European Commission).
  • Poland runs e-invoicing through KSeF, a central government platform. Large taxpayers, with 2024 revenue above PLN 200 million, have issued through KSeF since February 1, 2026, most other businesses since April 1, 2026, and the smallest businesses join on January 1, 2027 (KPMG Poland).
  • Greece requires B2B e-invoices through certified providers connected to its myDATA platform. Larger businesses started in early 2026 and all others on November 2, 2026, with a transition period until January 31, 2027 (Taxually).
  • Croatia introduced Fiscalization 2.0 on January 1, 2026. VAT-registered businesses exchange domestic B2B e-invoices over Peppol and report them to the tax authority in real time (vatcalc).

Slovakia: domestic B2B from January 2027

Slovakia’s parliament has approved a law requiring VAT-registered businesses to issue and receive domestic B2B e-invoices through certified delivery providers from January 1, 2027, with cross-border reporting from July 1, 2030 (Sovos).

How do e-invoicing models differ across Europe?

European mandates share one standard, EN 16931, but differ in how invoices travel and what the tax authority sees. A US manufacturer with entities in several countries will usually run more than one model at the same time.

ModelHow it worksCountries
Format mandate, free channelThe law sets the format; businesses choose email, portal, EDI or PeppolGermany
Peppol exchangeInvoices travel between certified access points; the tax authority does not see each invoiceBelgium, Luxembourg (proposed), UK (planned)
Peppol exchange with real-time reportingInvoices travel over Peppol and invoice data goes to the tax authority as it is issuedCroatia, Ireland (planned)
Accredited provider with reportingInvoices pass through a government-approved provider that reports invoice data to the tax authorityFrance, Greece
Central government platformInvoices pass through a state system that validates or records them before the buyer receives themItaly (SdI), Poland (KSeF), Romania (RO e-Factura)

For AP, the consequence is the same everywhere. Invoices arrive through several channels, and every one still needs the same matching, approval and posting rules. Every model converges on EN 16931, and most on Peppol.

Do you need Peppol?

Peppol is mandatory in Belgium and planned in Luxembourg, Ireland and the UK, but optional in Germany. It is a secure network for exchanging e-invoices between certified access points, and it is widely expected to carry much of the traffic under ViDA.

Think of it like a mobile network. You subscribe once through an access point, get a Peppol ID, and can then exchange invoices with any business registered on Peppol, in any country. Compared with the alternatives:

PeppolEDIEmail
OnboardingRegister once, reach every Peppol participantBuild a connection per trading partnerChase each supplier for the right address
Proof of deliveryAlwaysDepends on setupNone; invoices land in spam or dead inboxes
SecurityEncrypted and signed; cannot be altered in transitSecure point to pointNot secure or verified
ValidationChecked by the access point on sending and receivingDepends on setupNone

In the webinar, Fairouz Ben Guirat of Dokapi put it simply: “Do not wait for a mandate to register on Peppol.” Registering now means your suppliers in Belgium, and soon Luxembourg, Ireland and the UK, can reach you on the network they are required to use.

What should AP teams do now?

Start with receiving. It is already mandatory in at least eight European countries, and it is the step most likely to break a scanning-based AP process.

  1. List every European entity and its VAT registration. This tells you which mandates apply and when, including for entities run from your US headquarters.
  2. Confirm every European entity can receive e-invoices. Italy has required it since 2019 and Romania since 2024. Germany followed in January 2025, and Croatia, Belgium, Poland, Greece and France during 2026.
  3. Map suppliers by country and deadline. The next sending waves start on January 1, 2027 in Germany and Slovakia, and on September 1, 2027 in France, so e-invoice volumes will change in months, not years.
  4. Choose a channel for each entity. Use Peppol, an accredited platform or the government system wherever the country requires one, and decide whether Peppol is worth it where it is optional.
  5. Tell your suppliers how to invoice you. Add your Peppol ID to purchase orders, your email signature and a short supplier note.
  6. Make sure AP reads data, not scans. Plan how invalid invoices are rejected and returned to suppliers.
  7. Track what is still moving. Luxembourg, Ireland, the UK, the Netherlands and Germany’s e-reporting plans are not final.

How do you get European e-invoices into QAD or NetSuite?

You need a receiving channel for each country and one AP workflow that reads the XML, matches it and posts it to your ERP. DocLib integrates natively with QAD and NetSuite, and connects to other ERPs through an integration scoped to your environment, so every e-invoice ends up as a correct voucher in your ERP, whichever way it arrives.

  • Through Peppol. Since October 2026, DocLib customers can register on Peppol through DocLib and receive validated e-invoices via Dokapi, a certified Peppol access point since 2019. Invoices are checked against the relevant standard before they reach you. There is no separate project.
  • By email. Where Peppol is optional, suppliers can keep emailing XRechnung or ZUGFeRD files. DocLib processes both.
  • One workflow for every entity. DocLib reads the structured XML directly, so there is nothing to retype and no OCR step. PO invoices are matched to the purchase order and goods receipt in your ERP, and clean 3-way matches post automatically. Differences go to an AP user to review. Your German, French and Belgian entities follow the same rules, and DocLib brings deep experience in complex, multi-entity QAD environments.
  • Invoices without a PO. The supplier is identified and remembered, the invoice is routed to the right approvers by amount, and approved invoices post to your ERP.
  • Built-in controls. DocLib validates tax against the tax setup in your ERP, or against rules configured in DocLib, and stops duplicates, whether they are already in a workflow or already booked in your ERP.

Already on DocLib? Contact us to register on Peppol.

New to DocLib? Request a demo to see e-invoices posting in your own ERP setup.

Have German entities? Watch our webinar with Dokapi on German e-invoices in QAD, from receipt to posted voucher.

This article is for general information only and does not constitute legal or tax advice.

Frequently asked questions about e-invoicing in Europe

When does e-invoicing become mandatory across the EU?

E-invoicing becomes mandatory for intra-EU B2B transactions on July 1, 2030 under the EU’s VAT in the Digital Age (ViDA) package. Domestic deadlines are set by each country: Italy, Romania, Germany, Croatia, Belgium, Poland, Greece and France already have mandates in force.

Do EU e-invoicing mandates apply to US companies?

They apply to your European entities. A subsidiary or branch established in a country with a mandate must follow it, with no exemption for a US parent. A US entity invoicing from the US is generally out of scope, though European customers increasingly expect e-invoices.

When does e-invoicing become mandatory in the UK?

From April 1, 2029, UK VAT invoices between businesses, and to public bodies, must be issued and received as e-invoices. Peppol is the core framework. The UK is outside the EU, so its mandate runs separately from ViDA.

Is a PDF invoice an e-invoice?

No. A PDF is an image of an invoice. An e-invoice is structured XML data that follows the European standard EN 16931 and can be processed by systems without manual entry. In a hybrid format such as ZUGFeRD, only the embedded XML is the legal invoice.

What is EN 16931?

EN 16931 is the European standard that defines the data an e-invoice must contain. National formats such as XRechnung, ZUGFeRD and Peppol BIS Billing 3.0 are built on it, which is what lets invoices move between systems and countries.

Do e-invoicing mandates apply to cross-border invoices?

Mostly not yet. Most national mandates cover domestic B2B transactions between businesses established in that country. From July 1, 2030, ViDA adds mandatory e-invoicing and digital reporting for intra-EU B2B transactions.

What should a business with entities in several European countries do first?

Confirm each entity can receive e-invoices in the format and channel its country requires. Then route every invoice, whatever its channel, into one AP workflow, so matching and approval rules stay the same in every country.

Which European countries use Peppol for e-invoicing?

Belgium mandates Peppol for domestic B2B e-invoicing, and Croatia uses it for its real-time model. Luxembourg, Ireland and the UK plan to build their mandates on it, and the Netherlands is considering it. Germany accepts Peppol but does not require it.

Can QAD or NetSuite receive Peppol e-invoices?

Yes, through an AP automation layer connected to a Peppol access point. DocLib receives Peppol e-invoices through Dokapi, matches them to purchase orders and receipts, and posts them to QAD or NetSuite.

What is a Peppol ID?

A Peppol ID is the identifier a business receives when it registers on the Peppol network through an access point. Suppliers use it to address e-invoices to you, much like a phone number. You only register once to reach every Peppol participant.

What happens if you receive an invalid e-invoice?

Reject it and ask the supplier to correct and resend it. Paying an invalid e-invoice creates a compliance risk. Validation errors are common with hybrid PDF and XML formats, so automated validation on receipt matters.

Sources

Published on November 10, 2026

Last Updated on November 10, 2026

Ready to transform your AP automation?

Doclib favicon author

AP Automation, built for complex finance teams. Streamline invoice processing, approvals, and reporting in real time — designed to align with your ERP environment.

Continue reading