E-invoicing mandates by country: the complete 2026 tracker

Every major economy is mandating e-invoicing. The systems are different. The timelines are different. The penalties are different. And if your business operates across even two or three of these jurisdictions, you are managing a compliance surface that no spreadsheet can contain. This article is a country-by-country reference for CFOs, tax managers, and ERP evaluators who need to understand exactly where each mandate stands in 2026 and what your finance systems must do to stay legal.

We cover eight jurisdictions: Nigeria, Saudi Arabia, Italy, India, the EU (Germany, France, Poland), Mexico, the United Kingdom, and Kenya. For each one, we explain what the system is called, who it applies to, what the technical model is, and what the penalties are for non-compliance.

Why this matters more in 2026 than it did two years ago

The pace of mandate rollout has accelerated sharply. In 2022, a business could operate across five countries and face a serious e-invoicing obligation in only one or two of them. In 2026, that same business is almost certainly in scope in every jurisdiction it touches. Tax authorities are no longer piloting: they are enforcing. The EU's ViDA (VAT in the Digital Age) package locked in timelines. Saudi Arabia's ZATCA clearance waves reached mid-market businesses. Nigeria launched NRS MBS. India extended its IRN threshold down to small businesses. Mexico moved all taxpayers to CFDI 4.0.

The core risk for finance teams is this: a mandate you do not know about is a mandate you cannot comply with. And an ERP that does not update its connectors before a deadline leaves you exposed on the date the regulator starts issuing penalties.

Country-by-country breakdown

Nigeria: NRS Mandatory Billing System (NRS MBS)

What it is: The Nigeria Revenue Service Mandatory Billing System is Nigeria's real-time e-invoicing infrastructure, operated by the Nigeria Revenue Service (NRS).

Who it applies to: All VAT-registered businesses operating in Nigeria above the VAT registration threshold.

Technical model: Clearance-adjacent reporting. Invoices must be submitted to the NRS portal in real time at the point of issuance. A QR code, generated from the NRS portal response, must appear on every invoice delivered to the buyer.

Penalty: Fines for late or missing submissions, and potential VAT deregistration for persistent non-compliance. Deregistration effectively bars a business from charging VAT, which is operationally disabling for any B2B operation.

ERP requirement: Your accounting system must have a live API connection to the NRS portal, generate compliant QR codes, and embed them in the invoice PDF before the document is sent.

Zinye connector: Zinye ships a native NRS MBS connector. Invoice submission, QR code generation, and status reconciliation are handled within the ERP workflow without manual intervention.

Saudi Arabia: ZATCA Fatoorah (Phase 2 Clearance)

What it is: Fatoorah is Saudi Arabia's national e-invoicing mandate, administered by the Zakat, Tax and Customs Authority (ZATCA). Phase 1 (generation-only, launched December 2021) required structured electronic invoice generation. Phase 2 (integration and clearance) introduced mandatory real-time clearance.

Who it applies to: Phase 2 rollout proceeded in waves, tiered by annual revenue. By 2026, the clearance obligation covers the vast majority of VAT-registered taxpayers in Saudi Arabia, including mid-market companies.

Technical model: Clearance model. Before an invoice reaches the buyer, it must be submitted to the ZATCA portal for cryptographic signing and clearance. The portal returns a cleared, signed invoice. The buyer receives only the cleared version. A QR code encoding key invoice fields is mandatory on every document.

Penalty: Fines scaled to invoice value for missing clearance. Repeat violations attract escalating penalties and potential suspension of the taxpayer's e-invoicing licence.

ERP requirement: Real-time API integration with ZATCA's Fatoorah platform, cryptographic certificate management, and compliant XML generation in the format ZATCA specifies.

Zinye connector: Zinye's ZATCA connector handles certificate onboarding, clearance API calls, and QR code embedding. Certificate renewal is managed automatically.

Italy: SDI / FatturaPA

What it is: Italy's Sistema di Interscambio (SDI), operated by Agenzia delle Entrate, is one of the oldest and most established e-invoicing mandates in Europe. FatturaPA is the XML invoice format it requires.

Who it applies to: All B2B and B2G (business-to-government) invoices issued by Italian VAT-registered entities. There are no revenue thresholds: this applies to every VAT-registered business in Italy.

Technical model: Routing and validation model. Invoices are sent to SDI in FatturaPA XML format. SDI validates, delivers to the recipient, and returns delivery confirmation or rejection codes. Invoices are not considered legally issued until SDI accepts them.

Penalty: Invoices not transmitted via SDI are legally non-existent for VAT deduction purposes. The issuer loses the right to recover VAT on the transaction, and the buyer cannot deduct input VAT. Financial penalties apply on top of this.

ERP requirement: FatturaPA XML generation, SDI submission, and receipt-of-delivery confirmation handling. The system must process acceptance and rejection responses and link them back to the original document.

Zinye connector: Zinye's SDI connector manages end-to-end FatturaPA submission and tracks document status in the invoice register.

India: IRN e-Invoice (GSTN)

What it is: India's e-invoicing mandate is run through the GST Network (GSTN). When a qualifying business issues an invoice, it must be reported to the Invoice Registration Portal (IRP) to receive an Invoice Reference Number (IRN) and a signed QR code.

Who it applies to: All GST-registered businesses above the applicable annual turnover threshold. Thresholds were lowered progressively from the initial Rs 500 crore limit. By 2026, the mandate covers businesses with turnover above Rs 5 crore, which encompasses a very large share of India's formal business sector. Businesses below the current threshold are expected to be brought in on a continuing schedule.

Technical model: Reporting model. The invoice is generated by the business first, then reported to the IRP. The IRP signs it and returns an IRN and QR code. The invoice is then sent to the buyer with both embedded. Critically, an invoice without a valid IRN is not legally valid for GST input tax credit purposes.

Penalty: Invoices without IRN are invalid for GST credit. The recipient cannot claim input tax credit, which creates strong buyer-side pressure to enforce compliance even before regulators act directly. Direct penalties include fines and interest on outstanding tax.

ERP requirement: GSTN IRP API integration, IRN fetching, QR code embedding, and e-way bill reconciliation where goods are involved.

Zinye connector: Zinye's IRN connector integrates with GSTN's IRP, fetches IRNs at the point of invoice saving, and embeds the signed QR code in the outbound document.

EU Peppol: B2G and National B2B Mandates

What it is: Peppol (Pan-European Public Procurement On-Line) is the network standard underlying most European e-invoicing infrastructure. It defines the network, access points, and document formats (BIS Billing 3.0 based on UBL/CII). Individual EU countries layer their own mandates on top of Peppol.

Who it applies to: B2G (invoicing public sector buyers) is mandatory across most EU member states. B2B mandates vary by country. Three significant national rollouts are active in 2026.

Germany (ViDA / ZUGFeRD / XRechnung): Germany's B2B e-invoicing obligation began phased rollout in 2025 under the ViDA framework. Large businesses are in scope first. The formats are XRechnung (pure XML) and ZUGFeRD (hybrid PDF/XML). Businesses must be able to receive structured e-invoices. Issuance obligations follow on the ViDA timeline.

France (PPF / PDP): France's B2B mandate, originally planned for 2024, was restructured around a new framework: the Portail Public de Facturation (PPF) for public sector, and a network of certified private dematerialization operators (PDPs) for B2B. Large businesses and mid-market businesses are in scope in 2026, with the full mandate reaching small businesses on a defined timeline.

Poland (KSeF): Poland's Krajowy System e-Faktur (KSeF) is a centralized government platform. All B2B invoices must be issued and received through KSeF. Poland's mandate was delayed from its original 2024 dates but is active and enforced in 2026 for the large taxpayer segment.

Technical model: Varies by country: Germany uses receiver-mandate with format compliance; France uses a clearance-adjacent PDP routing model; Poland uses a government clearance hub (KSeF is the single issuing and receiving channel).

Penalty: Varies by country. Non-compliant invoices may be rejected for VAT deduction, and direct fines apply for systemic failures.

ERP requirement: Peppol access point connectivity, format support for XRechnung, ZUGFeRD, UBL, and country-specific XML schemas, plus API connections to national clearance platforms (KSeF, PPF).

Zinye connector: Zinye's EU Peppol connector covers Peppol network access and the major national format variants. Country-specific platform connections (KSeF, PDP/PPF) are included in the EU compliance module.

Mexico: CFDI 4.0

What it is: Mexico's Comprobante Fiscal Digital por Internet (CFDI) is one of the world's oldest and most mature e-invoicing mandates, administered by the Servicio de Administración Tributaria (SAT). Version 4.0 is the required format from 2022 onward. Earlier versions are no longer accepted.

Who it applies to: All Mexican taxpayers issuing invoices, including individuals and legal entities of all sizes. There is no revenue threshold exemption.

Technical model: Clearance model. Invoices must be submitted to an SAT-authorized certifying service provider (PAC) for digital sealing before they are delivered to the buyer. The PAC adds its own digital seal and a Folio Fiscal UUID. An invoice without a valid UUID from an authorized PAC is legally void.

Penalty: Invoices without valid CFDI certification cannot be deducted for income tax or VAT purposes. SAT audits specifically check CFDI status. Fines, back-tax assessments, and interest apply where invalid invoices were used for deductions.

ERP requirement: PAC API integration, XML generation to CFDI 4.0 schema (including the addendum for payroll and complementos for specific transaction types), UUID management, and cancellation workflow (CFDI cancellation also requires PAC processing).

Zinye connector: Zinye's CFDI connector integrates with certified PACs, handles CFDI 4.0 generation and sealing, and manages the cancellation flow.

United Kingdom: Making Tax Digital

What it is: Making Tax Digital (MTD) is HMRC's digital tax compliance programme. MTD for VAT has been mandatory since 2022 for all VAT-registered businesses. MTD for Income Tax Self Assessment (ITSA) is rolling out to sole traders and landlords.

Who it applies to: MTD for VAT: all VAT-registered businesses in the UK. MTD for ITSA: sole traders and landlords with qualifying income, phased by income level through 2026 and 2027.

Technical model: The UK does not yet operate a clearance or real-time invoice submission model. MTD requires digital record-keeping and digital submission of VAT returns via API-compatible software. It is a reporting mandate, not an invoice-level clearance mandate.

Penalty: Failure to use MTD-compatible software results in points-based penalties under HMRC's penalty regime. Accumulated points lead to financial penalties.

ERP requirement: MTD-compatible software bridging or native MTD API submission for VAT returns. Direct record-keeping in digital format. No invoice-level API submission is required currently.

Zinye note: Zinye supports MTD VAT filing and digital record-keeping. The UK is on a trajectory toward fuller e-invoicing, and Zinye's compliance team monitors HMRC consultations for changes.

Kenya: eTIMS

What it is: Kenya Revenue Authority's Electronic Tax Invoice Management System (eTIMS) is an active mandate covering VAT-registered businesses in Kenya.

Who it applies to: VAT-registered businesses. KRA has been extending eTIMS obligations and integrating it with the broader tax compliance framework.

Technical model: Reporting model. Businesses submit invoice data to eTIMS at point of sale. Compliant invoices carry a KRA-generated QR code and a control unit number. The system integrates with electronic tax registers (ETRs) for retail and with API-based integration for larger businesses.

Penalty: Non-compliant invoices cannot be used as valid tax documents. KRA enforcement includes audits, fines, and potential deregistration.

ERP requirement: eTIMS API integration, QR code generation, and control unit number management. The system must handle real-time submission and response handling.

Zinye note: Zinye's Africa compliance module includes eTIMS integration for Kenyan operations.

Quick reference: e-invoicing mandates at a glance (2026)

What your ERP must actually do

The table above describes the compliance requirements. What it does not make obvious is the operational complexity behind each row. A clearance model like ZATCA or CFDI is not simply a matter of sending a file. It requires certificate enrollment, cryptographic signing, real-time API calls within the invoice issuance workflow, error handling for portal downtime, and status reconciliation to confirm the cleared invoice matches the one in your books.

A reporting model like India's IRN or Nigeria's NRS MBS requires the ERP to hold the invoice in a pre-send state, obtain the registration response, update the document with the IRN and QR code, and then release it to the buyer. If any step fails, the workflow must surface the failure clearly so the finance team can act. Silent failures are not acceptable when the result is an invoice the buyer cannot use for input tax credit.

An ERP that treats e-invoicing as a bolt-on, updated annually if someone remembers, is a liability. Regulators update formats, rotate certificates, change API endpoints, and tighten validation rules without long notice periods. Businesses that rely on manual tracking of regulator updates routinely find themselves out of compliance for weeks or months before anyone notices.

How Zinye handles mandate updates

Zinye's built-in compliance connectors cover all ten jurisdictions in this guide: EU Peppol, India IRN (GSTN), Italy SDI (Agenzia delle Entrate), Saudi Arabia ZATCA (Fatoorah Phase 2), Mexico CFDI (SAT), and Nigeria NRS MBS, with the Africa module covering Kenya eTIMS and extending to further African markets.

The critical difference in Zinye's approach is this: connector updates ship before customer deadlines. Zinye's compliance team tracks regulator publications, sandbox updates, and certification requirement changes for each jurisdiction. When a regulator changes a format, rotates a root certificate, or updates an API version, the update is tested and deployed to Zinye customers before the effective date. Customers do not carry the burden of monitoring six or more regulatory bodies across multiple jurisdictions.

Because Zinye is fully managed, there is no customer-side IT work required to receive compliance updates. The connector update is deployed at the infrastructure layer. Your finance team continues working in the same interface, and the updated format or API version is used transparently.

For businesses operating in multiple jurisdictions, this is not a minor convenience. It is the difference between a compliance function that runs reliably and one that surfaces crises at quarter-end.

The right question to ask your ERP vendor

If you are evaluating ERP platforms for a multi-jurisdiction operation, the question is not "does your system support e-invoicing?" Every vendor says yes. The right questions are:

• How quickly do you ship connector updates after a regulator publishes a format change?
• Who monitors the regulatory calendars for each jurisdiction where I operate?
• What happens on the day a regulator rotates a certificate or changes an API endpoint? Do I find out before or after invoices start failing?
• Is the update process managed by you, or does it require my IT team to deploy something?

Chioma Adeleke is Solutions Lead for Africa at Zinye, based in Lagos. She works with finance teams across Nigeria and the broader continent on ERP implementation, tax compliance, and multi-jurisdiction operations.