# E-Invoicing Compliance: A Guide for Global SaaS

> How e-invoicing mandates work for software companies selling internationally: clearance vs post-audit models, Peppol, structured formats, and who carries the obligation.
- **Author**: Aarthi Poonia
- **Published**: 2026-07-28
- **Category**: Tax, Compliance, SaaS
- **URL**: https://dodopayments.com/blogs/e-invoicing-compliance-global-saas

---

A SaaS company in Bangalore sells a EUR 4,000 annual plan to a business customer in Munich, generates a PDF invoice, and emails it. Since 1 January 2025, German VAT law no longer treats that PDF as an electronic invoice at all. It is a "sonstige Rechnung" (other invoice), and the buyer's accounts payable team is legally required to be able to receive a structured one instead.

E-invoicing is the exchange of invoices in a structured, machine-readable format that a buyer's system and often a tax authority can process automatically without human transcription. It is not a PDF attached to an email, and it is not a nicely designed HTML receipt. That distinction is the entire compliance problem, because more than 60 jurisdictions now legislate against a technical definition of "invoice" rather than a visual one.

This guide covers what the mandates actually require, how the three enforcement models differ, where the major regimes stood as of July 2026, and what changes when you use a merchant of record instead of carrying the obligation yourself.

## What e-invoicing actually means

An e-invoice is an invoice issued, transmitted, and received in a structured electronic format that permits automated processing. The German Federal Ministry of Finance states this directly: since 1 January 2025, a simple PDF document does not qualify, because it has no structured format. The same logic underpins every serious mandate worldwide.

Two structural standards do most of the work in Europe. EN 16931 is the CEN semantic standard that defines what data fields an invoice must carry and how they relate. UBL (Universal Business Language) and CII are the XML syntaxes that carry those fields on the wire. Hybrid formats such as Factur-X and ZUGFeRD embed the XML inside a PDF/A-3 container, so a human sees a document and a machine sees data.

The practical test is simple. If a buyer's ERP cannot ingest your invoice, post it to a payables ledger, and match it to a purchase order without a person retyping the line items, it is not an e-invoice. If you currently generate documents through a templating engine, read our guide to [automating invoice generation for SaaS](https://dodopayments.com/blogs/automated-invoices-saas) before you assume your existing pipeline is compliant.

Note that "e-invoice" is a narrower concept than the commercial documents you may already produce. A [commercial invoice](https://dodopayments.com/blogs/commercial-invoice-guide) and a [proforma invoice](https://dodopayments.com/blogs/proforma-invoice-vs-invoice) serve different legal purposes and are usually outside the scope of a VAT e-invoicing mandate.

## The three e-invoicing models, compared

Jurisdictions enforce e-invoicing through one of three architectures. Which one applies determines whether your invoice needs government approval before your customer ever sees it.

| Model | How it works | Tax authority role | Latency | Example regimes |
| --- | --- | --- | --- | --- |
| Clearance (CTC) | The invoice is submitted to a government platform first, validated, and only then delivered to the buyer | Gatekeeper. An unvalidated invoice has no legal force | Real time to a few days | Italy (SdI), Poland (KSeF), Saudi Arabia Phase 2 standard invoices |
| Post-audit | You issue and send the invoice directly to the buyer, then retain and report it. Authorities inspect later | Auditor after the fact | Periodic reporting | Historic EU default; Germany's issuance rules today |
| Decentralised (four-corner) | Certified service providers exchange invoices over a shared network; data is reported to the authority in parallel | Supervisor of accredited providers | Near real time | France's approved-platform regime, Peppol-based national systems |

Clearance is the strictest. In Italy, an invoice that is not passed through the Sistema di Interscambio is legally considered not issued, which means it cannot support the buyer's input VAT deduction. Post-audit is the most permissive and is what most sellers have implicitly relied on for decades. The decentralised model is where the European Union is converging, because it scales without a single national bottleneck.

Understanding which model applies matters more than knowing the file format, because it dictates whether a failed submission blocks your revenue recognition. If you are still mapping your indirect tax exposure generally, start with [VAT compliance for digital products](https://dodopayments.com/blogs/vat-compliance-digital-products) and [VAT vs sales tax for SaaS](https://dodopayments.com/blogs/vat-vs-sales-tax-saas).

## Where major mandates stand as of July 2026

Country timelines have slipped repeatedly. France alone moved from an original 1 July 2024 start to September 2026. Treat the table below as a directional map verified against government sources in July 2026, and confirm current status with a tax advisor before you build against any date.

| Jurisdiction | Model | Status as of July 2026 |
| --- | --- | --- |
| European Union (ViDA) | Framework | Package adopted 11 March 2025, in force 14 April 2025. Digital Reporting Requirements for cross-border B2B apply from 1 July 2030 |
| Italy | Clearance | Mandatory B2B and B2C since 1 January 2019 via SdI, FatturaPA XML. B2G since 31 March 2015 |
| Germany | Post-audit, phased | Receipt capability mandatory since 1 January 2025. Issuance transition runs through 2026, extended to end of 2027 for smaller issuers |
| France | Decentralised | Receipt obligation for all French-established VAT-taxable businesses from 1 September 2026; issuance phased from that date |
| Poland | Clearance | KSeF issuance from 1 February 2026 for the largest taxpayers, 1 April 2026 for the rest; receipt via KSeF from 1 February 2026 |
| India | Clearance-style reporting | Reporting to an Invoice Registration Portal required above a INR 5 crore aggregate turnover threshold, effective 1 August 2023 |
| Saudi Arabia | Clearance | Fatoora Phase 1 since 4 December 2021; Phase 2 integration since 1 January 2023, rolled out in waves by turnover |

A few details are worth pulling out because they change what you have to build.

The EU's VAT in the Digital Age package was published in the Official Journal on 25 March 2025 as Directive (EU) 2025/516 and its accompanying regulations. Its immediate effect was permissive rather than prescriptive: on entry into force, Member States gained the ability to impose mandatory domestic e-invoicing without first requesting a derogation, which is precisely why national mandates accelerated. The Commission's own estimate is that the reform could cut VAT fraud by up to EUR 11 billion a year and reduce administrative and compliance costs for EU traders by over EUR 4.1 billion a year over ten years.

Germany's split between receipt and issuance is the detail most sellers miss. There is no transitional relief for receipt: every domestic business has had to be able to accept a structured invoice since 1 January 2025, and the ministry has confirmed that an ordinary email inbox satisfies this. Issuance is where the phasing sits, with issuers whose prior-year total turnover did not exceed EUR 800,000 permitted to keep using other formats until the end of 2027. Small-value invoices up to EUR 250 and transport tickets sit outside the obligation. Germany has also signalled a second stage, a transaction-level reporting system layered on top of e-invoicing, but the go-live for that stage was not settled law as of July 2026, so do not plan against a fixed date.

France requires that invoices flow through a state-registered platform under Article 289 bis of the Code général des impôts, alongside a separate e-reporting obligation covering transaction and payment data. The tax administration published startup guidance in July 2026 confirming that penalties will not be applied to businesses that hit implementation difficulties while demonstrably working toward compliance. That is a grace period on enforcement, not on the legal obligation. Our [French merchant of record guide](https://dodopayments.com/blogs/merchant-of-record-in-france) covers the wider local picture.

Poland's KSeF splits by size in a way that catches mid-market sellers quickly: issuance obligations begin 1 February 2026 for taxpayers whose 2024 sales value including tax exceeded PLN 200 million, and 1 April 2026 for everyone else, with the smallest taxpayers deferred to 1 January 2027. Receiving through KSeF became mandatory for all taxpayers on 1 February 2026. See our [Poland merchant of record overview](https://dodopayments.com/blogs/merchant-of-record-poland) for context.

India's regime is often mislabelled. GST e-invoicing does not mean the government generates your invoice; it means you report specified documents to an Invoice Registration Portal and receive an Invoice Reference Number back. The threshold has walked down steadily, from INR 500 crore aggregate turnover in October 2020 to INR 5 crore effective 1 August 2023 under Notification 10/2023 - Central Tax. It covers B2B supplies and exports along with credit and debit notes, and excludes categories including SEZ units, banking and insurance, goods transport agencies, and passenger transport. Our [Indian GST guide for SaaS](https://dodopayments.com/blogs/navigating-indian-gst-saas) goes deeper.

Saudi Arabia runs the cleanest two-phase design. Phase 1, Generation, has applied to all resident VAT taxpayers since 4 December 2021 and simply requires compliant electronic generation and storage. Phase 2, Integration, began 1 January 2023 and requires systems to connect to ZATCA by API, submitting UBL 2.1 XML or PDF/A-3 with embedded UBL. Standard tax invoices are cleared before use; simplified invoices are reported afterwards within 24 hours. ZATCA notifies each wave at least six months ahead, and the turnover threshold has fallen with each successive wave rather than following a published end-state, so check your wave status directly rather than inferring it.

## What an e-invoicing mandate changes in your stack

A mandate is not a formatting change. It introduces a synchronous external dependency into a flow that was previously entirely under your control.

Four things break first:

- **Data completeness.** Structured formats reject invoices with missing mandatory fields. Italy's SdI validates that the supplier VAT number and the buyer's VAT number or tax code exist in the tax register, that a destination code is populated, and that the file is not a duplicate. If any check fails, it returns a rejection receipt and the invoice is treated as never issued. You need the buyer's tax identifier captured at checkout, not chased afterwards.
- **Timing.** SdI delivery normally completes in minutes but can take up to five days when volume peaks. If your revenue recognition or entitlement grant is coupled to "invoice issued", that coupling now depends on a government queue. Decouple them.
- **Immutability and correction.** You cannot quietly edit a cleared invoice. Corrections move through credit notes and debit notes, which are themselves in scope of the mandate. Systems that rely on regenerating a PDF will need rebuilding.
- **Archiving.** Mandates carry retention obligations measured in years, in the original structured format, with integrity guarantees. Storing a rendered PDF is not sufficient evidence.

There is also an identity problem. Applying the correct VAT treatment to a cross-border B2B sale depends on validating the buyer's VAT number at the point of sale so reverse charge can be applied. Dodo Payments handles this at checkout through [B2B tax ID validation](https://docs.dodopayments.com/features/b2b-payments), and the resulting document flows into [automated invoice generation](https://docs.dodopayments.com/features/invoice-generation). If your [order to cash process](https://dodopayments.com/blogs/order-to-cash-process) collects tax IDs after the fact, mandates will expose that gap fast.

## Peppol e-invoicing and the four-corner network

Peppol is the interoperability layer that lets any seller reach any buyer without a bilateral integration for each trading partner. It is governed by OpenPeppol AISBL, a non-profit association based in Brussels, and it is the backbone that several national mandates either use directly or model themselves on.

The architecture is the four-corner model:

- Corner 1 is the seller's billing or ERP system.
- Corner 2 is the seller's certified Access Point, which converts the document to the agreed format, validates it, signs it, and finds the recipient.
- Corner 3 is the buyer's Access Point, which verifies and forwards.
- Corner 4 is the buyer's accounting system.

Corners 1 and 4 never talk directly. Discovery happens through a two-tier lookup: the sending Access Point queries the Service Metadata Locator, a DNS-based directory, which points to the Service Metadata Publisher holding the recipient's capabilities and endpoint. Transport runs over AS4.

The document standard is Peppol BIS Billing 3.0, a Core Invoice Usage Specification of EN 16931 that uses UBL as its syntax. In practice this means a Peppol-valid invoice is also EN 16931-valid, which is why so many European mandates can accept it. Documents are checked against both the CEN business rules and the Peppol-specific rules before an Access Point will accept them, so validate before you send rather than discovering failures in production.

The strategic point for a software seller is that Peppol converts an N-by-N integration problem into a single connection. That is the same argument for consolidating payment and tax obligations behind one provider rather than assembling country-by-country coverage, which we cover in [how to automate global tax compliance](https://dodopayments.com/blogs/how-to-automate-global-tax-compliance-a-solopreneur-s-toolkit).

## Build, buy, or delegate

Three options exist, and they carry very different cost curves.

Building in-house means implementing EN 16931 semantics, at least two XML syntaxes, per-country extensions, clearance API integrations, digital signature handling, archiving with integrity proofs, and a correction workflow. Every country you add multiplies the surface. This makes sense only if invoicing is core to what you sell.

Buying a compliance vendor and bolting it onto your existing gateway keeps you as the legal seller. You still register for VAT where required, you still file returns, and you still own the liability if a clearance submission fails. The vendor handles format and transport, not obligation. Our comparison of [top cross-border sales tax challenges](https://dodopayments.com/blogs/top-sales-tax-challenges-for-cross-border-businesses) explains why the residual burden is heavier than it looks.

Delegating means someone else becomes the legal seller. That is the merchant of record model, and it is the only option that moves the obligation rather than the workload.

## How a merchant of record absorbs the obligation

Under a merchant of record arrangement, the provider is the legal seller to your customer. Because e-invoicing obligations attach to the entity making the supply, they attach to the merchant of record, not to you.

Concretely, this changes four things:

- The provider's entity appears on the invoice and the customer's card statement, and the provider's tax registrations determine which mandates apply.
- Tax determination, collection, filing, and remittance sit with the provider. Dodo Payments operates this way across 220+ countries and regions, as described in the [merchant of record introduction](https://docs.dodopayments.com/features/mor-introduction).
- Invoice generation, delivery, and format compliance become a platform concern rather than an engineering roadmap item.
- Your integration stays a single API. Adding a country does not add an e-invoicing project.

The tradeoff is real and worth stating plainly. You give up direct control over the invoice document and the legal seller relationship, and you pay a platform fee on top of processing. For a company selling in three countries with an in-house finance team, that may not be worth it. For a company selling in thirty, where each new mandate is a quarter of engineering time, it usually is. Our breakdown of [merchant of record legal and compliance responsibilities](https://dodopayments.com/blogs/merchant-of-record-legal-compliance) sets out exactly where the line falls, and [what a merchant of record is](https://dodopayments.com/blogs/what-is-a-merchant-of-record) covers the fundamentals.

One caveat that catches founders: a merchant of record handles indirect taxes on customer transactions. Your own corporate income tax on the payouts you receive remains yours. See [SaaS accounting fundamentals](https://dodopayments.com/blogs/saas-accounting-guide) and our [EU VAT guide for SaaS](https://dodopayments.com/blogs/eu-vat-saas-guide-2026) for how those interact.

You can review pricing at [dodopayments.com/pricing](https://dodopayments.com/pricing), or see how tax is calculated and displayed at [checkout](https://docs.dodopayments.com/features/checkout).

## FAQ

### Is a PDF invoice sent by email an e-invoice?

No. Under German VAT law since 1 January 2025, and under every clearance regime, an invoice only qualifies if it is issued, transmitted, and received in a structured format that permits automated processing. A plain PDF is classified as an "other invoice" because it carries no structured data. Hybrid formats such as Factur-X and ZUGFeRD embed XML inside a PDF/A-3 container and do qualify.

### Does e-invoicing apply to me if I only sell to consumers?

Usually not, but not always. Most mandates target B2B supplies, which is why Germany's obligation applies to domestic business-to-business transactions. Italy is the notable exception: its Sistema di Interscambio requirement has covered both B2B and B2C transactions between Italian-established parties since 1 January 2019.

### What is the difference between clearance and post-audit e-invoicing?

Under clearance, the invoice goes to a government platform first and is only legally valid once validated, as with Italy's SdI and Poland's KSeF. Under post-audit, you send the invoice straight to the buyer and the tax authority inspects it later. Clearance turns invoice issuance into a synchronous dependency on a government system, which is the bigger engineering change.

### Do I need to join Peppol to be compliant?

Only if the jurisdiction you are selling into runs on it or accepts it. Peppol is an interoperability network governed by OpenPeppol, not a legal requirement in itself. Its value is that a Peppol BIS Billing 3.0 document is also EN 16931-compliant, so one integration satisfies several European mandates at once.

### Does a merchant of record remove my e-invoicing obligation entirely?

For the transactions it processes, yes, because the obligation follows the legal seller and the merchant of record is the legal seller. It does not cover invoices you issue outside that relationship, such as enterprise contracts billed directly from your own entity, and it does not cover your corporate income tax filings.

## Conclusion

E-invoicing mandates are not a formatting exercise. They redefine what counts as an invoice, insert government systems into your revenue flow, and multiply with every country you sell into. The EU has already legislated the direction through ViDA, with cross-border Digital Reporting Requirements landing 1 July 2030 and national systems required to converge by 1 January 2035.

Two things follow. Capture buyer tax identifiers at checkout rather than chasing them later, and decouple your entitlement and revenue logic from "invoice issued" so a government queue cannot stall your product. Then decide honestly whether you want to own this obligation or hand it to the entity that becomes the legal seller.

If you would rather ship product than track mandate timetables across thirty jurisdictions, [Dodo Payments](https://dodopayments.com) operates as the merchant of record and carries the tax and invoicing obligation on the transactions it processes. Confirm your specific position with a qualified tax advisor before you rely on any date in this article.
---
- [More Tax articles](https://dodopayments.com/blogs/category/tax)
- [All articles](https://dodopayments.com/blogs)