Mandatory e-invoicing starts with a connection: a certificate, a platform contract, a Peppol registration. This page sets out what each regime requires first and where the authority says so.
E-invoicing access works differently from tax filing: in most countries tracked the business connects through a provider or platform rather than registering with the tax authority itself. Poland is the exception that needs the most preparation — KSeF authentication first, then separate certificates for authentication and offline mode, each valid for a maximum of two years.
| Jurisdiction | What you need first | Stated lead time | Register or connect by | Authority source |
|---|---|---|---|---|
| Germany | None — no portal, no accreditation | Not applicable | In force since 1 January 2025 | FAQ E-Rechnung — Bundesfinanzministerium ↗ |
| France | Contract with a plateforme agréée (PDP) | Not stated by DGFiP | 1 September 2026 | Fiche plateformes agréées — DGFiP ↗ |
| Italy | SdI routing identifier and transmission channel | Not stated | In force since 1 January 2019 | DLgs 127/2015, art. 1 — Normattiva ↗ |
| Spain | None stated for Veri*Factu | Not stated | Before 1 January 2027 (corporate income tax payers); before 1 July 2027 (others), as extended by Real Decreto-ley 15/2025 | Veri*Factu — cuestiones generales, AEAT ↗ |
| Belgium | Peppol access point via a certified service provider | Not stated | In force since 1 January 2026 — the trigger is any invoice drawn up, issued or sent on or after that date | When is e-invoicing mandatory — einvoice.belgium.be ↗ |
| Poland | KSeF authentication, then a KSeF certificate | Not stated | 1 February 2026 | KSeF plan wdrożenia — Ministerstwo Finansów ↗ |
| European Union — ViDA | None — this is a directive, not a platform | Not applicable | — | VAT in the Digital Age — European Commission ↗ |
Lead times are shown only where the authority states one. “Not stated” means the authority has not published it — not that it is quick.
The access register lists the common failure for every jurisdiction, alongside the credentials to hold, who may hold them and the steps in order.
A legal entity authenticates with a qualified electronic seal containing the NIP, a qualified signature with the NIP, a Profil Zaufany or a token. Without a qualified seal it files ZAW-FA to designate one natural person to manage permissions. KSeF certificates are then issued to authenticated entities, valid for a maximum of two years, one purpose each.
Every business must contract with a plateforme agréée (PDP) immatriculated by DGFiP. There is no self-service government channel for B2B invoices. A group running its own platform must itself be immatriculated.
AEAT states no prior registration is required. Compliance rests on a declaración responsable from the software producer, not the taxpayer.
Through a certified Peppol service provider. Your software connects and registers you as a Peppol participant. There is no tax-authority accreditation of the taxpayer.
Each row is read from the same dataset as the jurisdiction pages and links to the authority page it was checked against. Where an authority has not published a fact the row says so rather than filling it in. Dataset last reviewed 4 November 2026.
Saurabh Satija, “E-invoicing access requirements by country”, https://saurabhsatija.com/e-invoicing-access-requirements, accessed [date].
The underlying data is open as JSON, archived with DOI 10.5281/zenodo.23426086 under CC BY-NC 4.0.