The Reference eGuide
Global eInvoicing Mandates: The Reference eGuide
A working guide to understanding the eInvoicing mandates reshaping B2B trade across Europe, the Middle East, Africa, and Asia-Pacific and where automation fits.
An eInvoicing mandate is a government requirement to issue and exchange invoices as structured, machine-readable data through approved channels, rather than as a PDF, a scan, or paper. The specifics (which formats, which deadlines, who is in scope) vary by country, as this guide maps out.
How to use this guide
A reference, not a read-through
This is a working reference for the eInvoicing mandates affecting B2B suppliers: which countries are mandating what, by when, in which formats, and how to tell if you are in scope. It is built to be looked up, not read cover to cover. Use the quick-reference table to jump to your country, then drop into the regional sections for details on format and scope.
For the bigger-picture case on why these mandates can work in your favour, see the companion blog, “eInvoicing Mandates Are a Deadline. They’re Also an Advantage”.
Why it matters
The short version
In mandated markets, compliance is increasingly a condition of doing business, and suppliers that cannot support the required invoice formats may face rejected invoices, payment delays, buyer onboarding friction, or an inability to transact through mandated channels.
In many VAT (value-added tax) regions, invoice validity can affect the buyer’s ability to reclaim VAT, which gives buyers a direct financial reason to push suppliers toward compliant formats.
Depending on the country and enforcement model, non-compliance can carry penalties and firm deadlines (see the country tables): fines, blocked invoices, and, under clearance models, invoices that may not be treated as valid until the government authorises them.
This guide is a general orientation to the eInvoicing mandate landscape, not compliance advice. Always confirm the specifics for your situation with your tax, legal, or local advisors. For the upside (faster payments, fewer disputes, better visibility) and the full case, see the companion blog post.
START HERE
Are you affected?
You may be affected by an eInvoicing mandate if your business issues, receives, or processes invoices connected to a mandated market. Scope depends on the country, transaction type, entity structure, revenue threshold, and enforcement model, so the key question is not just where your company is headquartered, but where and how your transactions occur.
You may need to evaluate your readiness if any of the following are true:
You sell to or buy from businesses in a country with an active or upcoming eInvoicing mandate
Your buyers are asking for structured invoice formats, Peppol exchange, government portal submission, or other mandate-driven invoice requirements
Your supply chain, billing process, ERP, eCommerce platform, or procurement workflows touch any mandated market
You issue domestic B2B invoices through a subsidiary, branch, office, or registered entity in a mandated country
Your enterprise buyers are multinationals that are pushing local compliance requirements down to their suppliers
Key Terms
The vocabulary, in plain language
APP (Access Point Provider)
An accredited provider required in some regimes (for example, Nigeria) to transmit compliant invoices on your behalf, similar to an ASP.
ASP (Accredited Service Provider)
A provider you must appoint in some regimes (for example, the UAE) to transmit compliant invoices on your behalf.
Clearance
The strictest model: the government must pre-authorise an invoice before it can be sent to the buyer.
CTC (Continuous Transaction Controls)
Real-time or near-real-time reporting of each transaction to the tax authority as it happens.
Data Dictionary
The official reference that defines every required and optional field in a structured invoice format, used to build compliant e-invoices (as in UAE’s and Oman’s PINT specifications).
EN 16931
The European standard that defines what a compliant structured eInvoice must contain.
Fiscalisation
Real-time reporting of transaction data to a tax authority, often paired with a separate exchange mechanism like Peppol, as in Croatia.
Five-corner model
A Peppol variant that adds the tax authority as a fifth party alongside supplier, buyer, and their two access points, used where Peppol transport is combined with government clearance.
IRN (Invoice Reference Number)
A unique identifier issued by a government portal (India’s IRP, Nigeria’s NRS Merchant Buyer Solution) once an invoice is validated, confirming it’s cleared for legal use.
PA (Approved Platform)
The accredited platform required under France’s e-invoicing model. Unlike an ASP, a PA also handles government reporting, not just transmission.
Peppol
An international network and standard for exchanging structured business documents (orders, invoices) between trading partners.
Peppol Access Point
An accredited provider that connects you to the Peppol network. You connect through one rather than directly to the network.
PINT
The Peppol International invoice specification. Country variants exist, such as PINT AE for the UAE.
Post-audit
The lightest model: invoices are exchanged freely, and the authority reviews records after the fact.
VAT (value-added tax)
Consumption tax is used across the EU, the UK, the Gulf, and much of Asia-Pacific (not the US or Canada). Most of these mandates exist to close VAT gaps.
ViDA (VAT in the Digital Age)
The EU’s framework to modernise VAT reporting and eInvoicing. Sets standardised intra-EU structured eInvoicing from 2030.
THE BASICS
What an eInvoicing mandate actually requires
The compliance model varies by country (covered next), but the direction is consistent: structured data, automated exchange, and government visibility into the transaction layer.
01
Issued in a structured, machine-readable format (typically XML), not a PDF, not a scan
02
Transmitted through a government-approved platform or network, not directly by email
03
In many countries, reported to the tax authority in real time or near-real time
04
Stored for audit purposes, sometimes up to 10 years (UAE requirement)
TECHNICAL FRAMEWORK
The 6 compliance models (and why they matter)
Not all mandates work the same way. The model a country uses determines the technical approach and the solution you need.
Peppol Network
Invoices are exchanged across a decentralised network of certified access points. Businesses connect through an accredited provider, not directly.
Countries: Belgium · Singapore · Oman (expected) · United Kingdom · Ireland (planned) · Norway · Sweden · Denmark · Estonia · Latvia · Lithuania · Croatia (partial) · Luxembourg · Slovakia
Centralised Platform
Every invoice must first flow through a single government-operated portal, which receives and validates it before it moves on. No direct exchange.
Countries: Italy (SdI), Poland (KSeF), Malaysia (MyInvois), China (e-Fapiao), Croatia (partial, see blend note), Romania (RO e-Factura)
Real-Time Reporting (CTC)
The tax authority receives each transaction as it happens, in real time or near real time. The invoice still reaches the buyer. The government watches the flow but does not block it.
Countries: Spain’s SII regime, Portugal
Clearance (Pre-Authorisation)
The government must authorise each invoice before it can reach the buyer. Until it is cleared, the invoice is not valid. The strictest model.
Countries: Saudi Arabia, India, UAE (via accredited ASP), Nigeria (via accredited APP), Greece (myDATA)
Decentralised Clearance (Accredited Platforms)
Clearance and reporting run through privately operated platforms that meet government requirements, rather than one central portal. It blends decentralised exchange with clearance-level control, and it is the direction the EU is broadly moving under ViDA. In both France and Spain, a copy of the invoice must still reach the tax authority even when exchange happens privately.
Countries: France (PA, formerly PDP), Spain
Post-Audit
Businesses exchange invoices freely; the tax authority reviews records after the fact. The lightest model, with no pre-clearance required. Some countries in this group, such as Germany, still mandate a structured invoice format even though no network or portal is required.
Countries: Switzerland · Czech Republic · Cyprus · Germany
Note: some countries blend models. The UAE, for example, uses Peppol transport but adds accredited-platform clearance (its ASP requirement), so it appears under Clearance here.
Quick reference
All key deadlines at a glance
Find your country, then open a row for format, scope, compliance model, and where TradeCentric fits. Regional tables below add the full detail.
Beyond the cards
Additional countries
eInvoicing is moving beyond the countries above. These markets are earlier-stage, live in one segment only, running their own domestic systems, or still in consultation. For the latest detail on any of these, each country’s tax authority or the European Commission’s eInvoicing Country Factsheets are the best current source.
Live today — B2G via Peppol
These countries already require Peppol-based eInvoicing for government contracts. B2B isn’t mandated yet, but if you’re selling into government here, TradeCentric’s Peppol Access Point integration supports that exchange today.
Countries: Netherlands · Austria · Malta · Iceland
Live today — own domestic system or reporting regime (not Peppol)
These countries have active eInvoicing mandates, but run on their own national systems rather than Peppol. Invoice Automation can help produce the structured invoice data these systems expect, even where TradeCentric isn’t directly connected to the mandated channel. Check each country’s tax authority for current requirements.
Countries: Turkey · Albania · Egypt · Morocco · South Africa · Israel · Ghana · Hungary · Kenya
No mandate confirmed yet
These markets are in consultation, drafting legislation, or monitoring EU/regional developments. No B2B or B2G mandate is confirmed yet. Check each country’s tax authority for the latest.
Countries: Bulgaria · Cyprus · Czech Republic · Switzerland · Bosnia & Herzegovina · Bahrain · Qatar · Kuwait
EU ViDA
ViDA (VAT in the Digital Age) is the EU’s framework for cross-border eInvoicing and digital VAT reporting. It is not a country mandate, and doesn’t replace domestic mandates like Poland’s KSeF or Belgium’s Peppol rule. Instead, it standardises the layer that applies once an invoice crosses an EU border.
Adopted in 2025, ViDA removed the need for member states to get EU approval before mandating domestic eInvoicing, part of why so many countries moved quickly on their own systems since. 2025 was the legal green light, not the finish line: the rules now roll out in phases through 2035, giving member states and businesses time to align systems before cross-border reporting becomes mandatory.
2028
Digital reporting starts for intra-EU transactions
2030
EN 16931 becomes mandatory for cross-border eInvoices
2035
Full harmonisation target across all member states
For suppliers, this means the domestic mandate in front of you today is just the first step. Cross-border requirements are coming next, on the timeline above, so systems built Peppol-ready now carry forward instead of needing a second overhaul later.
Requirements still vary by country. Use this as context, not a substitute for checking each mandate.
BY REGION
Format and scope, region by region
The deeper tables. Sources are the official country factsheets from each tax authority or the European Commission.
Region: Europe
The EU’s ViDA initiative, short for VAT in the Digital Age, is the bloc’s plan to modernise how VAT is reported and collected in a digital economy. Formally adopted in 2025, it removed the requirement for member states to get approval from Brussels before mandating domestic eInvoicing. Several countries moved immediately.
Key Point: France, September 2026
France’s mandate is now live and is the largest in Europe by transaction volume. Since September 1, 2026, every VAT-registered business in France must be able to receive eInvoices, and large and mid-sized companies must also issue them. If your buyers include French companies, this affects them, and by extension, you.
Key Point: Greece, October 2026
Phase 1 went live in March 2026. From October 1, 2026, every remaining Greek-established business must issue B2B invoices electronically through myDATA. There’s a transition period to December 31, but the obligation starts October 1.
Region: Middle East & Africa
UAE: What you need to know right now
- • The voluntary pilot has been open since July 1, 2026. Businesses that join early are exempt from penalties before their mandatory date.
- • Businesses with revenue ≥ AED 50M must appoint an Accredited Service Provider (ASP) by October 30, 2026.
- • Mandatory go-live for large businesses: January 1, 2027.
- • The UAE uses the Peppol 5-corner model. Your ERP must generate valid PINT AE XML; a PDF email has zero compliance value.
- • Penalties: AED 5,000/month for failure to use an ASP; AED 10,000 for non-compliant invoice format.
Region: Asia-Pacific
hOW TRADECENTRIC HELPS
Where TradeCentric fits, and how we help
Requirements vary by country, transaction type, and enforcement model, so use TradeCentric as part of a broader readiness strategy — not a substitute for tax, legal, or local compliance advice.
Direct fit
Peppol-based markets
These markets run on Peppol, either because the mandate requires it or because Peppol is an accepted route. Through our integration with a Certified Peppol Access Point, TradeCentric connects into Peppol-enabled ecosystems to support structured eInvoice exchange. Several are B2G today with B2B still phasing in, so check the country card for what applies to you.
Belgium · Germany · Singapore · Oman · Norway · Sweden · Denmark · Estonia · Latvia · Lithuania · United Kingdom · Ireland (planned) · Croatia (partial) · Luxembourg · Slovakia
Data-readiness fit
Structured-format & portal markets
A country-specific format or government portal is required, or exchange runs through platforms you connect to rather than the tax authority directly. Invoice Automation produces the structured data these channels expect, keeping your systems ready to feed the mandated format. This isn’t a direct connection to the compliance step itself.
Italy · Poland · Spain · Portugal · Malaysia · China · France · Romania
Partial fit
Accreditation-gated markets
A government portal (Saudi Arabia, India) or a government-accredited provider (Greece, UAE, Nigeria) has to complete the final compliance step in these markets. TradeCentric doesn’t hold that accreditation. Invoice Automation still produces the structured data those channels expect, and in the UAE and Nigeria our Peppol integration sits underneath the ASP and APP layer the mandate runs on.
Greece · Saudi Arabia · India · UAE · Nigeria
TradeCentric helps suppliers:
Exchange structured invoice data electronically
Integrate supplier and buyer procurement systems
Support invoice automation workflows
Connect into Peppol ecosystems via certified partners
TradeCentric does not currently act as:
A tax advisor
A government clearance platform
A French Approved Platform (PA)
A UAE Accredited Service Provider (ASP)
Questions worth working through:
01
Which of your active invoicing markets are now mandated?
02
Do your invoice formats and data fields meet their requirements?
03
Are buyers or their platforms asking for different formats?
04
Where are the gaps between what you send and what’s required?
Ready to talk through your situation?
Your TradeCentric account team can walk through your current setup and flag where the mandate landscape intersects with your active integrations. Reach out directly or contact us to get the conversation started.
TradeCentric — B2B eCommerce & eProcurement Integration. Information current as of September 4, 2026.
TradeCentric is not a tax advisor and does not determine legal compliance; customers should validate country-specific requirements with their tax, legal, or local compliance advisors. This guide is for general informational purposes only and is not guaranteed to be accurate or complete. eInvoicing mandates change frequently, so please consult your country’s official mandate guidance, local tax authority, or legal counsel for the most up-to-date requirements before making implementation decisions.