E-Invoicing System Guide: Global Mandates, Compliance and What AP Teams Must Know in 2026
Tax authorities in more than 80 countries no longer accept PDF invoices for B2B transactions. They require structured, machine-readable electronic documents transmitted through government-approved platforms, in many cases cleared in real time before a transaction carries any legal weight.
Belgium's mandate went live in January 2026. Poland's KSeF system became mandatory for large businesses in February. France follows in September. India, Saudi Arabia, and Italy each run live electronic invoicing clearance systems affecting any organisation with a registered entity or meaningful supplier relationships in those markets. If your finance team has not yet mapped its infrastructure against these requirements, the gap is almost certainly larger than expected.
Why Are Governments Requiring Structured E-Invoicing Now?
Because governments are losing VAT revenue to fraud and manual reporting gaps. Structured e-invoicing is the mechanism they have chosen to close it. When every B2B invoice passes through a government-validated platform in machine-readable format, tax authorities can cross-reference transactions in real time rather than waiting for quarterly returns.
For finance teams, this translates into a technology requirement. The workflow that worked last year, a PDF created in the ERP and emailed to the supplier, no longer satisfies the legal definition of an invoice in a growing number of countries. In Belgium as of January 2026, that PDF is not a valid B2B invoice. In Poland since February, the same is true for large taxpayers. France follows in September. Several of these deadlines have already passed.
What Is an E-Invoicing System?
The term gets used loosely. An e-invoicing system is not software that creates PDFs and emails them. It is a platform that generates invoices in structured data formats that a computer can read, validate, and process without human intervention, and transmits them through the channels that tax authorities in each country require. In practice, a complete e-invoicing system handles four functions:
Generation: creating the invoice in the exact structured format each jurisdiction requires
Transmission: sending it through the right network or government clearance platform
Validation: in clearance countries, receiving government confirmation that the invoice is legally valid
Archiving: storing the original format with the metadata each country's retention rules require
The Two Mandate Models: What They Mean for Your Finance Team
Every e-invoicing mandate follows one of two models. This distinction matters more than the country-specific format details because it determines how deeply the mandate changes your existing AP workflow.
Post-audit model | Clearance model |
|---|---|
Invoice issued and transaction proceeds normally | Invoice submitted to government platform before it is legally valid |
Invoice reported to tax authority within a set period | Tax authority validates in real time or near real time |
Authority reviews and may audit after the fact | Transaction cannot proceed without clearance confirmation |
Format compliance is the main requirement | Real-time system connectivity is a hard requirement |
AP workflow impact is moderate: formats and reporting change, timing does not | AP workflow impact is significant: a new blocking step exists before payment |
Example: Germany's early B2G requirements | Examples: Italy SdI, Poland KSeF, Saudi Arabia ZATCA Phase 2 |
Sources: Precoro 2026 Mandate Guide, ZATCA official guidance, India GSTN advisory, Telema country updates
Is Your Current AP Setup Compliant? Four Questions to Answer
Before engaging any vendor or beginning a configuration project, these four questions reveal where your compliance gaps actually sit.
1. Can your system receive structured invoices in the formats mandates require?
Receiving a PDF and manually re-entering the data is not a compliant receipt. Your AP platform needs to accept XML, UBL, Factur-X, and other structured formats natively, validate them against mandate requirements, and feed the data directly into your ERP. If it cannot, every compliant invoice your supplier sends will create a manual exception.
2. Does your ERP or AP platform connect to Peppol and government clearance platforms?
For Belgium, you need a Peppol access point. For Poland, a KSeF API connection. For Saudi Arabia, integration with the Fatoora portal. For India, connectivity to the IRP. Most ERP native modules cover one or two jurisdictions. Organisations with a five-country footprint typically have gaps that only appear during implementation.
3. What happens when a supplier sends you a non-compliant invoice in a mandate country? In a clearance-model country, that invoice is not a valid legal document. Your AP team cannot process it as-is. You need a workflow that identifies the format failure, notifies the supplier, and tracks the corrected invoice back to the transaction. If your current system has no structured exception workflow for non-compliant e-invoices, that gap becomes visible at volume.
4. Does your invoice archive store the original structured format?
Italy requires the original FatturaPA XML to be retained for ten years. India's IRN and signed QR code are legally part of the invoice record. A PDF export from a structured invoice does not satisfy these requirements. If your archiving process converts everything to PDF, you have a compliance gap built into the archive from day one. Mindsprint's SprintAP maintains original structured format archiving as a core platform function, not a reporting add-on.
What Is Peppol and Why Do Multiple Mandates Use It?
Peppol is an open network and set of standards for exchanging structured business documents, originally developed for European public procurement and now used as the transmission infrastructure for multiple B2B mandates. Belgium's 2026 mandate runs on Peppol. The UAE's incoming mandate uses a Peppol-based model. Singapore, Australia, New Zealand, and Japan have all adopted versions of Peppol.
For finance teams evaluating platforms, Peppol connectivity is necessary but not sufficient. The relevant question is which country-specific format profiles and access points a platform supports within Peppol. Belgium requires Peppol BIS 3.0. Singapore requires a different format profile. E-invoicing software that claims Peppol connectivity but does not support the correct country profile does not satisfy the mandate.
Peppol is complementary to, not a replacement for, country-specific government systems. Poland's KSeF, Italy's SdI, India's IRP, and Saudi Arabia's Fatoora are all national clearance platforms that operate independently of Peppol. A complete e-invoicing system needs both.
E-Invoicing Compliance Readiness Checklist
Work through these before starting any vendor evaluation or system configuration. The gaps you identify here determine the scope of e-invoice compliance work needed before your next relevant deadline.
Mandate exposure
List every country where your business has a registered entity. Cross-reference each one against the mandate table above. Focus first on Belgium, Poland, France, Italy, India, and Saudi Arabia. Any match is a live or imminent compliance requirement, not a future planning item.
Identify which mandates are clearance-based and which are post-audit. For clearance mandates (Poland KSeF, Italy SdI, Saudi Arabia ZATCA), your AP system must transmit invoices to the government platform before the transaction proceeds. That is a deeper technical requirement than format compliance alone.
Map your nearest upcoming deadline and check the implementation window. Belgium is already live. France is September 2026. ERP configuration and supplier onboarding typically take three to six months. If your nearest deadline is within that window and you have not started, the gap needs to close now.
System capability
Ask your ERP vendor specifically which mandate jurisdictions their native module covers. Most cover one to two countries. If your mandate footprint is broader than that, your ERP module alone is not sufficient. You need a dedicated e-invoicing solution or AP platform that fills the gap across formats and government platform connections.
Verify Peppol and government platform connectivity. For Belgium, you need a Peppol access point. For Poland, a KSeF API connection. For India, IRP connectivity. For Saudi Arabia, Fatoora API integration. Connectivity claims in vendor sales conversations are not the same as tested, live integrations. Ask for proof specific to your jurisdictions.
Confirm your invoice archive stores the original structured format. Italy requires the original FatturaPA XML to be retained for ten years. India's IRN and signed QR code are part of the legal invoice record. If your archive process converts everything to PDF, you are building a compliance gap into the archive from the first invoice processed.
Supplier readiness
Identify which key suppliers are in clearance-model countries. In those jurisdictions, a supplier invoice in the wrong format is not a valid legal document. Your AP team cannot process and pay it until a compliant version is issued. At scale, that creates a payment backlog that looks like an AP operations problem but is actually a supplier compliance problem.
Check whether your AP platform has a supplier portal for structured format submission. Asking suppliers to connect to government platforms independently works for large, well-resourced suppliers. For smaller suppliers or those in early-stage mandate markets, a portal that accepts their invoice and converts or validates the format on their behalf significantly reduces onboarding friction.
Align your supplier onboarding timeline with your mandate deadline, not after it. Most organisations plan supplier onboarding as a post-go-live activity. In clearance-model countries, that sequencing means non-compliant invoices arrive from day one of the mandate. Supplier onboarding needs to run in parallel with system configuration, not after it.
For organisations preparing for France's September 2026 deadline, configuration and supplier onboarding typically take three to six months. Mindsprint's SprintNow service is structured to configure core e-invoicing compliance within six to eight weeks without disrupting the existing ERP. Speak to the Mindsprint team to confirm whether that timeline is achievable for your mandate footprint.
How Mindsprint Approaches E-Invoicing Compliance
SprintAP handles e-invoicing compliance as a built-in platform capability, not a country-specific module to be licensed and configured separately. This distinction matters for organisations with multi-jurisdiction mandate exposure.
Receives structured invoices in Peppol BIS, UBL, ZUGFeRD, Factur-X, and government XML formats
Supports clearance workflow integration with government platforms where real-time validation is required
Includes a supplier portal for structured format submission, reducing onboarding friction across mandate countries
Archives original structured format with jurisdiction-specific retention management, not PDF conversion
Integrates natively with SAP, Oracle, Dynamics, and NetSuite with no middleware
Combining e-invoicing compliance with broader invoice automation, Mindsprint works with enterprise finance teams across manufacturing, healthcare and life sciences, and global supply chains where multi-jurisdiction compliance is a current operational requirement, not a future planning item. Outcomes are on the Mindsprint success stories page. For teams combining AP automation with upstream procurement compliance, ProcureSPRINT integrates natively with SprintAP for end-to-end source-to-pay visibility.
Conclusion
E-invoicing compliance has moved from future planning to present obligation. Belgium and Italy are live. Poland is live for large businesses. France's September deadline is closer than most finance teams' implementation timelines allow.
The finance teams handling this well are the ones that treated electronic invoicing as an infrastructure decision from the start, not a per-country compliance project. They mapped their mandate exposure, audited their ERP and AP platform against structured format requirements, and chose platforms that maintain compliance as mandates evolve rather than requiring custom development for each country update.
For a conversation about how your current AP infrastructure maps to your specific mandate footprint, Mindsprint's team works with finance directors and group controllers across multiple jurisdictions. More on finance operations automation and enterprise AI is on the Mindsprint blog.
Frequently Asked Questions
Is a PDF invoice the same as an e-invoice?
No. A PDF contains readable text. An e-invoice contains structured data in a format that a government platform or trading partner system can parse and validate automatically. Belgium, Poland, France, Italy, India, and Saudi Arabia all define e-invoicing in terms of structured data formats and explicitly reject PDFs as insufficient for compliance.What is the difference between Peppol, KSeF, IRP, and ZATCA?
Peppol is a global transmission network and standard. KSeF (Poland), IRP (India), and Fatoora/ZATCA (Saudi Arabia) are government-run clearance platforms in specific countries. Some countries use Peppol as their transmission network (Belgium, UAE).When does France's mandate take effect and who does it cover?
September 2026, for large and mid-sized businesses. From that date, they must both issue and receive structured e-invoices through platforms connected to France's PPF infrastructure. Smaller businesses follow by September 2027.What are the penalties for getting this wrong?
In clearance-model countries, a non-compliant invoice is not a valid legal document, which means the transaction itself is at risk, not just a compliance filing. India applies penalties of up to INR 10,000 per invoice or 100% of the tax due.How do I know if my current ERP handles this?
Ask your ERP vendor which mandate jurisdictions their native module covers, in what formats, and how they update when a mandate format changes. Most cover one to three countries at most. Organisations with a broader footprint typically need an AP automation platform that manages multi-jurisdiction compliance at the layer above the ERP.
Not sure which mandates apply to your business?
Mindsprint works with finance teams to map mandate exposure and configure SprintAP for multi-jurisdiction compliance.
Talk to a compliance expert | Explore SprintAP | Read more on the Mindsprint blog
