Which countries have mandatory e-invoicing?

QUICK ANSWER

More than 30 countries now require mandatory e-invoicing, including Italy, Poland, Belgium, Croatia, Greece, Romania, France, Saudi Arabia, Turkey, India, Brazil and Mexico. Germany, Spain, the UAE and Slovakia are phasing theirs in; the UK follows in April 2029 and the EU-wide regime under ViDA in July 2030. Most of these mandates apply to businesses established in the country — a VAT registration alone is usually not enough to bring you into scope.

If you sell across borders, the honest starting point is that this question has two answers. There is the list of countries that have passed an e-invoicing law — long, growing, and easy to find. And there is the much shorter list of countries whose law actually reaches your business. Most published guides give you the first and leave you to work out the second on your own.

That gap matters commercially. We regularly speak to sellers who have bought e-invoicing software for a market they were never in scope for, and to sellers who assumed a foreign VAT registration kept them safely outside a regime that was already reporting on them. Both mistakes cost money; the second one also costs penalties.

This guide sets out where mandatory e-invoicing applies as at September 2026, and gives you a scope test you can apply to your own structure before you read the table. For the underlying mechanics — what a structured invoice is and how it moves — see our guide to how e-invoicing works.

Why governments are making e-invoicing mandatory

The driver is the VAT gap. When invoice data reaches a tax authority in a structured format at or near the time of the transaction, missing-trader fraud becomes far harder and audit becomes far cheaper. That is why the countries with the largest historic VAT gaps moved first, and why the model spread from Latin America to southern Europe before reaching northern Europe and the Gulf.

For businesses the effect is mixed but broadly positive once implemented: faster payment cycles, fewer disputes, less rekeying. We have written separately on what businesses actually gain from e-invoicing. The difficulty is not the destination. It is that thirty-odd governments are arriving there by different routes, on different dates, using different formats.

What counts as a compliant e-invoice

A PDF emailed to a customer is an electronic document. It is not, in most jurisdictions, an electronic invoice. The legal test is almost always the same: the invoice must be issued, transmitted and received in a structured electronic format that another system can process automatically, without anyone rekeying it. Common formats include UBL 2.1, UN/CEFACT CII, and hybrid formats such as Factur-X and ZUGFeRD, most of them conforming to the European standard EN 16931.

Separately, several countries require the invoice to be cleared, validated or reported to the tax authority within a set window. Countries broadly split into two architectures: a clearance model, where the invoice passes through or is reported to a government platform before it is legally valid (Italy, Poland, Brazil, Saudi Arabia), and a post-audit or network model, where invoices are exchanged directly between accredited providers and the authority looks at them later (Germany, Belgium, and the UK from 2029). The distinction changes what you have to build.

None of this changes what has to be on the invoice. The mandatory content rules are unchanged — see what a compliant VAT invoice must contain.

Does any of this reach your business? A five-question scope test

Work through these before you look at the table. They decide which rows are relevant to you, and in our experience they resolve most of the confusion in about ten minutes.

1. Are you established in the country?

This is the single most important question, and the one most often answered wrongly. Most domestic B2B e-invoicing mandates apply to businesses established in the country concerned — a local entity, or a fixed establishment with the human and technical resources to make and receive supplies. Holding a VAT registration there is not the same thing. Poland states this explicitly: the KSeF obligation follows a registered office or fixed establishment in Poland, not a Polish VAT number.

2. If you are only VAT-registered, what are your reporting obligations?

This is where “not in scope” stops being the end of the answer. Several regimes catch non-established but VAT-registered businesses through e-reporting or digital reporting rather than through the invoicing mandate itself. Hungary’s real-time reporting is a long-standing example; France’s e-reporting obligations are a live and contested one. And under ViDA, EU digital reporting for intra-Community transactions is not conditional on domestic establishment. If you are registered somewhere, check the reporting rules separately from the invoicing rules — see how ViDA and IOSS affect non-EU sellers.

3. Do you supply any public body?

B2G e-invoicing has been mandatory across all 27 EU Member States since 2019 under Directive 2014/55/EU, and B2G rules frequently apply regardless of where you are established. In the UK, public bodies covered by the Public Procurement Act 2023 must already accept compliant e-invoices, and NHS Supply Chain requires suppliers to invoice via Peppol today. If you have a single public-sector customer anywhere, you may already be in scope.

4. Are you selling B2C or through marketplaces?

Consumer sales sit outside most B2B invoicing mandates but inside a growing number of transaction-reporting regimes. If you are distance-selling into the EU, your OSS or IOSS position interacts with this. Marketplace reporting under DAC7 is a separate obligation again and should not be confused with invoice reporting — see DAC7 explained. Sellers of software, subscriptions and digital content have their own treatment; our guide to VAT for digital services covers it.

5. Are your customers in scope, even if you are not?

This is the quiet one. Once a buyer is legally required to receive structured invoices, they will require it of their suppliers commercially, whatever the law says about you. Group structure matters here too: one entity established in a mandate country brings that entity into scope even where the parent sits outside. In practice, customer pressure pulls more businesses into e-invoicing each year than legislation does.

E-invoicing countries: the mandate table

The list below is selective rather than exhaustive. It covers the markets AVASK clients actually trade in; several trackers list ninety or more countries, most of which will never be relevant to a cross-border e-commerce seller. Country names link to our global VAT guides where one exists. The final column is a general indication only — establishment tests vary in detail and should be confirmed for your structure.

Status key: Live — obligations in force. Phasing in — some cohorts in scope, others to follow. Confirmed — legislated with a fixed date. Proposed — announced or under development.

What the table means, region by region

Europe

Europe is where the picture changed most in 2026. Belgium and Croatia went live on 1 January, Greece on 2 February, and Poland’s KSeF opened to its largest taxpayers on 1 February and to most other VAT-registered businesses on 1 April. France then went live on 1 September 2026: every business established in France must now be able to receive a structured invoice, and large and mid-sized companies must issue them too, with smaller businesses following in September 2027. Our full guide to the French mandate covers the platform model and the e-reporting split in detail.

Poland is the clearest illustration of why establishment matters. KSeF is a clearance system — an invoice is not legally delivered until it has passed through the platform — but the obligation follows a Polish registered office or fixed establishment. Most non-Polish e-commerce sellers with a Polish VAT number are outside it. We set out the detail in our guide to Poland’s KSeF mandate.

Germany sits in the middle of its rollout: every domestic business has had to be able to receive e-invoices since January 2025, and the issuing obligation arrives in January 2027, extending to smaller businesses in January 2028. Spain has moved twice and should be treated as unsettled — the Veri*Factu certified-software rules were pushed out to January and July 2027, and the separate B2B mandate phases in once the implementing order is published. Italy, meanwhile, has run the longest-established regime in Europe through SdI since 2019; non-EU sellers should also read our note on Italy’s rules for non-EU sellers.

Above all of this sits ViDA. From 1 July 2030, e-invoicing and digital reporting apply to intra-EU B2B transactions under EN 16931, and Member States must align pre-existing domestic regimes by 1 January 2035. Two points are worth being precise about: the earlier proposal referenced 2028, which is no longer the agreed position; and ViDA reporting for intra-Community transactions is not conditional on domestic establishment. We cover the programme in what VAT in the Digital Age means and the future of e-invoicing in the EU.

The UK is the outlier that isn’t. Mandatory e-invoicing for B2B and B2G VAT invoices arrives on 1 April 2029, and in June 2026 the government confirmed Peppol as the core interoperability network. It will be a four-corner model with no live reporting to HMRC in the initial phase, and the detailed roadmap is expected at the November 2026 Budget. Businesses moving goods through Northern Ireland should plan for both the UK regime and ViDA. If Europe is your growth market, our EU and UK expansion hub sets out the wider compliance picture.

Middle East and Africa

Saudi Arabia has run ZATCA’s Fatoora regime since 2021 and continues to bring taxpayer groups into the integration phase in waves. The UAE is the market to watch: a voluntary pilot opened on 1 July 2026, businesses above AED 50 million come into scope on 1 January 2027, and everyone else on 1 July 2027, using a five-corner Peppol model through accredited service providers. Turkey extended e-Arşiv to all businesses on 1 January 2026. Africa has moved faster than most people realise — Morocco, Nigeria, Angola, Cameroon and others have all announced or begun rollouts since 2024. If you are entering these markets, our rest-of-world solutions hub is the place to start.

Asia-Pacific

The region is fragmented by design. India has run a clearance system through the Invoice Registration Portal since 2020, now reaching businesses above INR 5 crore. Malaysia is completing the phased MyInvois rollout. Singapore is bringing newly incorporated GST registrants onto InvoiceNow, its Peppol-based network, from 2026. China is extending fully digitalised e-fapiao through to 2027. Japan is the important exception: its Qualified Invoice System changes invoice content and registration rather than mandating structured transmission, so it is often miscategorised in global trackers. Australia mandates e-invoicing for government suppliers via Peppol but leaves B2B voluntary.

Latin America

Latin America invented this. Brazil’s NF-e has run since 2006 and Mexico’s CFDI is universal; Chile, Argentina, Colombia, Peru, Ecuador and Uruguay all operate mature clearance regimes. For a foreign seller the practical point is different from Europe: in most of these markets you cannot transact at all without a local registration, and once you have one, e-invoicing is not an add-on obligation but the mechanism by which invoicing works.

North America

There is no federal e-invoicing mandate in the United States and no VAT for one to attach to. Adoption is market-led, with the DBNAlliance building a voluntary exchange network. Canada has adopted Peppol for public-sector invoicing but has set no B2B mandate. For US sellers the relevance of this article is therefore entirely outbound: nothing changes at home, and a good deal changes the moment you register in Europe.

What to do now

• Map your entities against your registrations. Write down, for every country, whether you have an establishment, a VAT registration, or both. This one exercise resolves most scope questions.
• Separate invoicing obligations from reporting obligations. They have different scope tests and different dates. Being outside one says nothing about the other.
• Check your receiving capability before your issuing capability. Receiving obligations almost always arrive first and apply more broadly. Germany and France both did it this way.
• Look at your invoice data, not just your invoice format. Structured invoices fail on missing or inconsistent master data far more often than on format. Data problems usually pre-date the project by years, which is why they are slow to fix.
• Ask your largest customers what they will require. Commercial deadlines frequently land before legal ones.
• Prioritise by revenue, not by date. A mandate in a market that is 40% of your turnover matters more than one arriving sooner in a market that is 2%.

Frequently asked questions