Glossary
Definition. Electronic invoicing (e-invoicing) is the issuing, transmission and receipt of invoices in a structured digital format that machines can process automatically. Under many tax mandates it also feeds invoice data to the tax authority, distinguishing it from a PDF or paper invoice.
E-invoicing is often misread as any invoice sent by email. In a regulatory sense it means something narrower: an invoice created, exchanged and stored in a defined structured format, such as UBL or the EN 16931 European standard, that another system can read and process without a human retyping it. A PDF is a picture of an invoice; a structured e-invoice is data.
The distinction matters because e-invoicing is the vehicle for continuous transaction controls. Once invoice data is structured, a tax authority can require it to be cleared before issuance, or reported within a short window, turning the invoice into both a commercial document and a compliance signal. Interoperability frameworks such as Peppol provide the shared network and format rules that let structured invoices move between different systems and across borders.
Adoption is being driven largely by mandates. Italy made structured e-invoicing compulsory across the economy, Poland is rolling out its KSeF platform, France, Belgium and Germany are phasing in obligations, and the EU's ViDA package makes structured e-invoicing the default for intra-EU B2B trade from July 2030. Each mandate sets its own formats, timelines and clearance rules, which the country tracker on this site is built to compare.
E-invoicing matters because it is the foundation layer: without structured invoice data there is no real-time reporting, no automated matching and no compliance by design. The honest nuance is that e-invoicing is a means, not an end. A mandate can improve tax collection and cut administrative cost, but it also standardises a large flow of commercial data, so how that data is protected and who can see it are design questions that sit alongside the format itself.