Global e-Invoicing Compliance in 2026: Mandates, Standards and Deadlines by Country

What is e-invoicing compliance?

E-invoicing compliance is the practice of meeting a country's legal rules for electronic invoices. That covers four things: the format the invoice must take (a structured, machine-readable file, not a PDF or a scan), how it is transmitted (a government platform, an accredited network, or a direct API), what the tax authority does with it (clear it before issue, receive it in real time, or audit it later), and which transactions are in scope (B2G, B2B, B2C, or a mix).

A true e-invoice carries structured data such as UBL or CII XML, or India's GST JSON, that flows straight into the buyer's and the tax authority's systems. A PDF emailed to a customer is a digital document, not an e-invoice, and it will not satisfy a structured mandate. See e-Invoicing Explained for the underlying concepts and Why PDF Invoices Are Becoming Obsolete for the shift away from unstructured formats.

Because every jurisdiction makes its own choices, compliance is country-specific. A system built for Italy's clearance platform will not satisfy India's reporting portal or Belgium's Peppol network without adaptation. The global overview dashboard tracks the current status, scope, and deadline for every country in one place.

Why is 2026 a turning point for global e-invoicing compliance?

2026 is the year the rollouts overlap. Belgium made B2B e-invoicing mandatory on 1 January 2026, Poland's KSeF reaches its largest taxpayers on 1 February 2026, Saudi Arabia's ZATCA brings Wave 24 in by 30 June 2026, France's national mandate begins on 1 September 2026, and Malaysia, Singapore, and Spain each move further into scope during the year. A business trading across borders now faces several deadlines in parallel rather than one at a time.

This guide is the reference for that picture. It explains the five compliance models, the standards that sit under every mandate, and the country-by-country deadlines, then sets out how to stay compliant in more than one market at once. For a region-first view, read Global e-Invoice Mandates in 2026 and e-Invoice Requirements by Country.

What are the five e-invoicing compliance models?

The post-audit model is the lightest. Businesses exchange invoices freely and the tax authority reviews records afterwards. The United Kingdom and Canada work this way.

The decentralised exchange model uses a four-corner network, almost always Peppol, where invoices pass between accredited access points with no central government platform. Belgium, Singapore, Norway, and Australia use it.

The real-time reporting model, known as Continuous Transaction Controls (CTC), requires invoice data to reach the tax authority as invoices are issued. The authority receives a copy in real time but does not block issuance. India, Malaysia, and Saudi Arabia follow this model.

The centralised platform model routes every invoice through a government-run system that validates it in real time, as in China and Taiwan.

The clearance model is the strictest: the tax authority must approve each invoice before it reaches the buyer, and an uncleared invoice has no legal standing. Brazil, Mexico, Italy, and Colombia operate clearance systems. For worked examples of each, see The Five Compliance Models in Global e-Invoicing and e-Invoice Compliance Mandates Explained. Compare models side by side with the country comparison tool.

Which standards and formats must a compliant e-invoice use?

EN 16931 is the European core data model for an e-invoice. It supports two syntaxes, UBL 2.1 and UN/CEFACT CII, and most EU mandates require one or both. The standard has been updated by CEN to align with ViDA. The full breakdown is in EN 16931 Demystified.

UBL 2.1 underpins Peppol BIS Billing 3.0, Germany's XRechnung, and many national core invoice usage specifications. CII is the alternative EN 16931 syntax and the basis for the hybrid Factur-X and ZUGFeRD formats, which embed structured XML inside a PDF.

Several countries require their own schema. Italy uses FatturaPA XML, Mexico uses CFDI 4.0, Malaysia uses the MyInvois XML schema, and India submits a GST JSON payload. A vendor that handles UBL and CII will not automatically support these national formats, so format coverage is one of the first things to check when you evaluate systems. The country comparison tool lists the required format for each market.

How does Peppol fit into e-invoicing compliance?

Peppol, governed by the OpenPeppol association, lets a sender reach any receiver through registered access points using the AS4 protocol, with no central government hub in the middle. The default document is Peppol BIS Billing 3.0, a UBL profile that conforms to EN 16931. What Is Peppol? explains the network in full.

Peppol is the backbone of compliance in a growing list of markets: Belgium, the Nordics, Singapore through InvoiceNow, Australia and New Zealand through PINT A-NZ, and the UAE through the PINT AE profile and a five-corner model. Peppol's PINT (Peppol International) specification is how the network is being adapted for use beyond Europe.

Because one connection serves many countries, Peppol is often the most efficient route to multi-country compliance. The trade-off is that Peppol alone does not cover clearance or centralised-platform markets such as Italy, Mexico, or Saudi Arabia, where a different integration is still required.

What does EU ViDA require, and when?

ViDA is the EU framework that standardises e-invoicing and VAT reporting across all member states. The package was adopted on 11 March 2025 and rolls out in stages. From 1 July 2030, intra-EU cross-border B2B transactions must use structured e-invoices that conform to EN 16931, reported under new Digital Reporting Requirements that replace today's recapitulative statements, and existing national systems must become interoperable with the EU system by 2035.

A change that already matters: since ViDA entered into force in April 2025, member states can mandate domestic e-invoicing without first seeking a special EU derogation, and a structured e-invoice is the default. That is why countries such as Belgium, Poland, and France have been able to move quickly. The full timeline is in What Is ViDA?, and the EU's e-Invoicing Directive reality check covers what it means for finance teams in practice.

Which European countries require e-invoicing in 2026?

Italy runs the longest-standing B2B mandate in Europe, with all invoices passing through the SDI clearance platform since 2019 in the FatturaPA format. See the Italy guide.

Poland rolls out KSeF in 2026: businesses whose 2024 sales exceeded PLN 200 million must issue invoices through KSeF from 1 February 2026, all other VAT-registered businesses from 1 April 2026, and penalties for breaches apply from 1 January 2027. The Poland guide and Poland KSeF mandate guide have the detail.

France begins its mandate on 1 September 2026, when large and intermediate-sized enterprises must issue structured e-invoices and every business must be able to receive them. SMEs and micro-enterprises follow on 1 September 2027. From the start date, businesses must send and receive invoices through a state-accredited platform, known as a PDP; the public portal (PPF) was scaled back under the 2025 Finance Act and now acts only as a directory and data concentrator, not a free invoicing service. Read the France guide and France e-Invoicing Reform for Finance Teams.

Germany has required all domestic businesses to receive e-invoices since 1 January 2025, with mandatory issuing phased in from 1 January 2027, and from 1 January 2028 for businesses with prior-year turnover up to EUR 800,000, using XRechnung and ZUGFeRD. See the Germany guide and XRechnung 4 in Germany.

Belgium made structured B2B e-invoicing mandatory on 1 January 2026 over the Peppol network, using the Peppol BIS format; see the Belgium guide. Romania has required B2B reporting through its RO e-Factura system since 1 January 2024, and made it the sole channel for B2B invoices from 1 July 2024; see the Romania guide. Spain is moving on two tracks: its Veri*Factu certified-software rules take effect in 2027 (corporate income tax payers from 1 January 2027 and other taxpayers from 1 July 2027), and a B2B e-invoicing mandate was approved in March 2026 under Royal Decree 238/2026, which will phase in once the implementing ministerial order is published, starting with businesses whose turnover exceeds EUR 8 million. The Spain guide and Spain mandatory B2B e-invoicing track both.

What are the e-invoicing compliance rules in the Middle East?

Saudi Arabia runs the ZATCA Fatoora system, now in its Phase 2 integration stage. Wave 24 lowers the threshold to taxpayers with VAT-taxable revenue above SAR 375,000, who must integrate with Fatoora by 30 June 2026. Invoices carry cryptographic stamps and QR codes. See the Saudi Arabia guide and ZATCA Fatoora guide.

The UAE uses a five-corner Peppol model with the PINT AE profile. The pilot launches on 1 July 2026, large taxpayers above AED 50 million must appoint an Accredited Service Provider by 30 October 2026, and their mandatory go-live stays at 1 January 2027. Under Ministerial Decisions 243 and 244 of 2025, businesses below AED 50 million follow on 1 July 2027 and government entities on 1 October 2027, with penalties set under Cabinet Decision No. 106 of 2025. See the UAE guide, the PINT AE guide, and the ASP deadline update.

Israel is phasing in a clearance-style allocation-number model through the Israel Tax Authority; the Israel guide covers the current thresholds. Other Gulf states, including Qatar, are at the planning stage.

How does e-invoicing compliance work across Asia-Pacific?

India operates one of the largest systems in the world. Businesses with annual aggregate turnover of INR 5 crore or more must register each B2B invoice with an authorised Invoice Registration Portal (IRP), which returns an Invoice Registration Number (IRN) and a QR code in a GST JSON exchange. See the India guide.

Malaysia validates invoices through the LHDN MyInvois portal. Under the LHDN implementation timeline, Phase 4 brings businesses with annual turnover up to RM 5 million into scope from 1 January 2026, with the smallest businesses phased in from 1 July 2026 and those below the exemption threshold excluded. The Malaysia guide and MyInvois guide track the current thresholds.

Singapore uses Peppol through GST InvoiceNow, which began with newly registered businesses in late 2025 and 2026 and extends to all GST-registered businesses in phases through to 2031, as set out by IRAS/gst-invoicenow-requirement). See the Singapore guide.

Australia and New Zealand share the Peppol PINT A-NZ format. Government adoption is growing while B2B exchange stays voluntary; see the Australia guide and New Zealand guide. The Philippines is expanding its Electronic Invoicing System.

What are the e-invoicing requirements in the Americas?

Mexico requires CFDI 4.0 for all transactions, generated through an authorised PAC and cleared by the SAT tax authority before delivery. The Mexico guide covers PAC providers and technical rules.

Brazil runs NF-e for goods and NFS-e for services, both XML-based and both requiring pre-clearance, one of the most mature ecosystems anywhere; see the Brazil country page. Colombia mandates UBL 2.1 invoices cleared by DIAN before the buyer receives them, covered in the Colombia guide.

The United States has no federal e-invoicing mandate. Adoption is market-driven through the DBNAlliance, a Peppol-based exchange framework for voluntary B2B invoicing. The USA guide sets out the current position.

What are the penalties for e-invoicing non-compliance?

Financial fines are the most common. In Italy, failure to issue invoices through SDI is penalised under Article 6 of Legislative Decree 471/1997, which sets the fine as a percentage of the VAT involved. The UAE imposes AED 5,000 per month for failure to implement the required system under Cabinet Decision No. 106 of 2025.

Denied deductions raise the cost of every non-compliant transaction. India refuses GST input tax credit for invoices without a valid IRN, so a missing registration directly increases tax payable.

Operational blocks are the harshest. In clearance countries such as Brazil and Mexico, an invoice that has not been cleared is not legally valid: the buyer cannot process it and the seller cannot recognise the revenue. Each country page lists the specific fines, thresholds, and enforcement dates, and e-Invoice Compliance Mandates Explained compares enforcement across models.

How do you stay compliant across multiple countries?

Start by listing every country where you issue or receive invoices, then check the status of each on the global overview dashboard, filtering by mandate scope (B2B, B2G, B2C) and stage (mandatory, phased, planned). This shows where action is needed now and where deadlines are approaching.

For each market, confirm three things from the country guides: the required format, the transmission channel, and whether pre-clearance applies. Then assess whether your ERP or invoicing platform can produce those formats and connect to those channels. The e-Invoice Readiness Scorecard gives a structured assessment across regulatory awareness, technical capability, process maturity, vendor readiness, and organisational preparedness.

Where there are gaps, use the Vendor Match Tool to find providers that cover your specific countries, formats, and compliance models, and the vendor directory to compare their capabilities. Build timelines that work backwards from each enforcement date, leaving room for vendor selection, integration, and testing with the tax authority, and track changes on the news and updates page as deadlines and scopes move.