Why do e-invoice requirements differ so much between countries?
No two countries implement e-invoicing the same way. Differences in format, transmission protocol, and compliance model mean that a solution built for one market rarely works in another without adaptation.
Every country that mandates e-invoicing makes its own choices about which invoice format to require, how invoices must be transmitted, and what role the tax authority plays in the process. These decisions are shaped by existing tax infrastructure, international commitments (like the EU's EN 16931 standard), and the government's compliance objectives.
For businesses operating across borders, this means a single invoicing system or vendor is unlikely to cover every requirement out of the box. The key is to understand the specific requirements for each country in your supply chain and plan accordingly.
This article provides a region-by-region overview of the most important requirements. For detailed country-specific information, follow the links to our country guides and country pages.
What are the e-invoice requirements across Europe?
The EU's EN 16931 standard provides a common semantic framework, but each member state adds its own national rules, formats, and timelines.
EN 16931 is the European standard for the core data model of an e-invoice. It supports two syntaxes: UBL 2.1 and UN/CEFACT CII. Most EU mandates require one or both of these formats. See EN 16931 Demystified for the full breakdown.
Italy requires the FatturaPA XML format, transmitted through the SDI clearance platform. All B2B, B2G, and B2C transactions must go through SDI. Italy guide.
France requires invoices in Factur-X (CII-based hybrid), UBL, or CII format, transmitted through accredited platforms (PAs) or the government PPF portal. Large and intermediate-sized enterprises must issue e-invoices from September 2026; SMEs follow from September 2027. France guide.
Germany supports XRechnung (UBL-based) and ZUGFeRD (Factur-X-compatible) formats. Mandatory receiving since January 2025; mandatory sending phased through 2027-2028. Germany guide.
Belgium requires Peppol BIS Billing 3.0 (UBL) for B2B e-invoicing since January 2026. Belgium guide. Spain is rolling out **Veri*Factu** for real-time reporting alongside its B2B mandate. Spain guide.
The Nordic countries (Norway, Denmark, Sweden, Finland) have long-established Peppol networks for B2G and are expanding B2B adoption. Romania, Greece, Poland, Croatia, and Portugal each have their own rollout timelines and platform requirements.
What are the e-invoice requirements across Asia-Pacific?
India uses a JSON-based format submitted to authorised Invoice Registration Portals (IRPs). The system generates an Invoice Registration Number (IRN) and QR code for each validated invoice. All B2B and B2G transactions above the INR 5 crore threshold must comply. India guide.
Malaysia requires invoices to be validated through the MyInvois portal operated by LHDN. The system uses a government-defined XML schema. Since January 2026, businesses with annual revenue above RM 1 million must comply; those below RM 1 million are exempt. Malaysia guide.
Singapore uses the Peppol network through its InvoiceNow initiative. B2G e-invoicing is mandatory for government suppliers, with broader mandates planned for 2031. The format is Peppol BIS Billing 3.0 (PINT). Singapore guide.
Australia and New Zealand share the Peppol PINT A-NZ format for e-invoicing. Government adoption is growing, but B2B remains voluntary. Australia guide and New Zealand guide.
The Philippines is piloting its Electronic Invoicing System through the BIR, while South Korea and Japan maintain their own well-established reporting systems.
What are the e-invoice requirements in the Americas?
Latin American countries pioneered the clearance model. Pre-authorisation is the norm, not the exception.
Mexico requires CFDI (Comprobante Fiscal Digital por Internet) for all transactions. Invoices must be generated through an authorised PAC (Proveedor Autorizado de Certificacion) and cleared by the SAT tax authority before delivery. Mexico guide.
Colombia mandates electronic invoicing through DIAN using a clearance model. The UBL 2.1-based format must be validated by DIAN before the buyer receives it. Colombia guide.
Brazil operates two systems: NF-e for goods (national) and NFS-e for services (municipal). Both use XML formats and require pre-clearance from the tax authority. Brazil also has CT-e for transport documents. Brazil country page.
The United States has no federal e-invoicing mandate. The DBNAlliance operates a Peppol-based network for voluntary B2B exchange. Federal agencies use electronic invoicing for procurement, but there is no economy-wide requirement. USA guide.
What are the e-invoice requirements in the Middle East and Africa?
Saudi Arabia requires e-invoicing through the FATOORA platform operated by ZATCA. The integration phase mandates real-time reporting via API. Invoices must include cryptographic stamps and QR codes. Saudi Arabia guide.
The UAE has introduced an e-invoicing framework with penalties under Cabinet Decision No. 106/2025. The system is being rolled out in phases. UAE guide.
Israel is implementing a clearance-based system through the Israel Tax Authority with a phased rollout. Israel guide.
African markets are at earlier stages. Kenya has introduced the Tax Invoice Management System (TIMS), Nigeria is developing its framework, and Egypt has mandated electronic invoicing for registered businesses. Coverage varies significantly across the continent.
Use the global overview to filter countries by region and see the current status for every country we track.
Which invoice formats matter most?
The most widely used e-invoice formats globally are UBL 2.1 (Universal Business Language), UN/CEFACT CII (Cross Industry Invoice), and various country-specific XML schemas. Understanding which formats your target countries require is essential for system configuration.
UBL 2.1 is the basis for Peppol BIS Billing, XRechnung, and many national CIUS (Core Invoice Usage Specifications). If your business operates primarily in Europe and Peppol-connected countries, UBL support is essential.
CII is the alternative syntax under EN 16931 and is the basis for Factur-X and ZUGFeRD hybrid formats. These formats embed structured data inside a PDF, making them useful for businesses transitioning from paper-based processes.
Country-specific formats like FatturaPA (Italy), CFDI (Mexico), and MyInvois XML (Malaysia) require dedicated support. A vendor that handles UBL and CII may not automatically support these formats.
The country comparison tool lets you view format requirements side by side. For a deeper understanding of the standards behind these formats, see What Is Peppol? and EN 16931 Demystified.
How to use this information
Start by identifying your priority countries on the global overview dashboard. Filter by mandate status (mandatory, phased, planned) and transaction type (B2B, B2G, B2C) to see where immediate action is required.
For each country, read the detailed country guide to understand the specific format, transmission protocol, deadlines, and penalties. The guide pages include FAQs, exemption details, and links to official sources.
If you need to evaluate vendors for multi-country compliance, use the vendor match wizard to filter by country coverage, supported formats, and compliance models. The vendor directory lists providers with their capabilities and coverage.
Bookmark this page as a starting point, and check the news and updates page for the latest regulatory changes across all countries.
Explore e-Invoice.app
Real-time compliance data, peer discussions, and cross-functional tools for every stakeholder.
Compare Countries
Side-by-side comparison of mandates, timelines, and technical requirements.
Open Compare ModeFind the Right Vendor
Get matched with e-invoicing vendors for your countries and ERP.
Start vendor match