Europe eInvoicing
Two layers of rules, not one deadline: national mandates and the EU-wide ViDA framework.
The two layers
Layer 1: national mandates
Each EU country can require structured eInvoicing for transactions within its own borders, independently of the others and on its own schedule. At the time of writing:
| Country | Status |
|---|---|
| Italy | Long-standing mandatory system (SdI), already in force for several years |
| Romania | Mandatory system (RO e-Factura) already in force |
| Belgium | Mandatory from January 2026 |
| Poland | Mandatory system (KSeF), phased from February 2026 |
| Greece | Mandatory for large taxpayers from March 2026 (myDATA) |
| France | Mandatory from September 2026 |
| Germany | Phased mandatory requirements through 2027 and 2028 |
Layer 2: ViDA — the EU-wide framework
VAT in the Digital Age was adopted on 11 March 2025 and entered into force on 14 April 2025. It covers three areas: mandatory structured eInvoicing and digital reporting for cross-border B2B transactions between EU countries, new VAT rules for platforms such as short-term rental and transport services, and an expanded One Stop Shop for VAT registration.
The eInvoicing pillar has its own timeline, separate from any national mandate:
- 2028 — businesses must be capable of receiving structured eInvoices for in-scope transactions
- 1 July 2030 — structured eInvoicing and digital reporting become mandatory for cross-border intra-EU B2B transactions
- 1 January 2035 — member states that already run their own real-time domestic reporting must align those systems with the cross-border framework
This applies regardless of whether any country involved has an earlier domestic mandate. A German company invoicing a customer in Spain is a cross-border transaction under ViDA even if neither country's national mandate has taken effect yet.
The format: EN 16931
Both layers rely on the same underlying standard, maintained by the European standards body CEN. An updated version has been going through formal approval during 2026 to add fields needed for the new digital reporting requirements. Some countries use their own compliant variants built on the same standard — Germany's ZUGFeRD and France's Factur-X are hybrid formats that embed structured XML data inside a PDF, treated as compliant because of the structured layer inside them, not the PDF itself.
What this means if you invoice into Europe from the UAE
Two questions decide what applies:
- Is this a domestic-style transaction inside one EU country, or genuinely cross-border between two? A UAE business invoicing a customer in France is not itself "inside" France's domestic mandate in the way a French company invoicing another French company would be — but your counterparty's own obligations, and what they will accept from you, are shaped by their national rules.
- What does your counterparty actually require? The practical step is to ask the business you are invoicing which format and delivery method they need, since compliance obligations often sit with the receiving party as much as the sender.
Where iSAP Exchange fits — and where it does not
What we can help with is the same gap as on the UAE side: connecting the payment to the invoice record. Compliance schemes govern how an invoice is formatted and transmitted; they do not connect that invoice to the money that settles it. Through our ERP integration, a payment made via iSAP Exchange can update the corresponding invoice record in your system, so the two stay in step without manual matching — regardless of which European compliance layer produced the invoice in the first place.
What to do now
- List the countries you invoice into or from, and separate domestic-style relationships from genuinely cross-border ones.
- Check the current national mandate date for each country on that list.
- Confirm your invoicing system can produce EN 16931-compliant structured data, since it covers both layers at once.
- Plan for 1 July 2030 regardless of national timing, for any genuinely cross-border intra-EU invoicing.
- Ask your EU counterparties directly what they require from you — this is often more current and more specific than any general summary.
See also UAE eInvoicing if you operate in both markets.
Frequently asked questions
Is there one European eInvoicing deadline?
No, and treating it as one date is the most common mistake. There are two separate layers. Each EU country can set its own mandate for domestic transactions, on its own timeline. Separately, the EU-wide ViDA rules require structured eInvoicing for cross-border transactions between businesses in different EU countries from 1 July 2030. A business can face a national deadline, the 2030 cross-border deadline, or both, depending on who it invoices.
What is ViDA?
VAT in the Digital Age, an EU directive adopted on 11 March 2025 and in force since 14 April 2025. It has three parts: mandatory structured eInvoicing and digital reporting for cross-border intra-EU B2B transactions from 1 July 2030, new VAT rules for platforms such as short-term rental and transport platforms, and an expanded One Stop Shop for VAT registration. The eInvoicing pillar is the one that affects how invoices are issued and exchanged.
Do national mandates disappear once ViDA applies?
No. National mandates govern domestic transactions inside that country and continue to operate on their own terms. ViDA specifically covers cross-border transactions between EU member states. By 1 January 2035, member states that already have their own real-time domestic reporting are required to align those systems with the cross-border framework, but domestic mandates are not replaced by ViDA.
What format do European eInvoices use?
The European standard EN 16931, maintained by CEN. An updated version, adding fields to support the new digital reporting requirements, has been going through formal approval during 2026. Some countries use their own compliant variants — Germany's ZUGFeRD and France's Factur-X are hybrid PDF/XML formats built to meet the same underlying standard.
Does this apply to a UAE business invoicing a European customer?
It can. If you invoice a company in a specific EU country for a domestic-style transaction there, that country's national mandate may apply to your counterparty's obligations. For genuinely cross-border invoicing between two different EU countries, the 2030 ViDA deadline is the relevant date. The practical step is to ask your EU counterparty which regime applies to invoices from you, since requirements are set at their end as much as yours.
Which countries already require eInvoicing?
Coverage and dates vary and continue to move. At the time of writing, Belgium, Poland, Greece and France have mandates taking effect at different points in 2026, and Germany is phasing requirements through 2027 and 2028. Italy and Romania already operate long-standing mandatory systems. Always confirm the current position for a specific country before relying on a date, since several have already shifted once.
What happens if I do nothing until 2030?
For domestic transactions in a country with an earlier national mandate, you would already be non-compliant well before 2030. For cross-border transactions, 2030 is a real deadline, but the businesses least prepared tend to be the ones that treated a five-year runway as a reason to wait rather than a reason to start early, given how much ERP and process change is typically involved.
Is a PDF invoice acceptable under ViDA?
For transactions in scope of the cross-border mandate from 2030, no — the requirement is structured data in the EN 16931 format, not a PDF or scanned document. Some transitional hybrid formats that embed structured data inside a PDF, like ZUGFeRD or Factur-X, are treated as compliant because the structured layer is present, not because the PDF itself satisfies the rule.
Where does iSAP Exchange fit into this?
The same place as with the UAE mandate: we are not an accredited service provider or a certified Peppol access point, and you would appoint one separately for actual compliance with either the national mandate or ViDA. What we can help with is connecting the payment side to the invoice record in your ERP, so that once a payment is made through iSAP, the corresponding invoice updates automatically rather than being reconciled by hand.
Find this useful? Make iSAP Exchange a preferred source on Google, and our guides will surface more easily when you search.
