E-invoicing

The defining feature is structure. A PDF attached to an email is not an e-invoice; it is a picture of one. A true e-invoice is issued as structured data, commonly an XML format such as UBL, that the receiving system can validate and post without any extraction step.

That is also the difference from invoice automation: automation copes with whatever format arrives, including scans and PDFs, while e-invoicing fixes the input itself so there is nothing left to interpret. The two are complements, and clean structured input is what lets automation reach very high touchless rates.

Governments are the main force behind adoption. Tax authorities in countries including Italy, Mexico, and Brazil require invoices to be issued or cleared through official platforms, and the list grows every year, so for companies operating in those markets e-invoicing is a compliance obligation rather than an efficiency project. Peppol, a delivery network and format standard that began in European public procurement, gives trading partners one connection instead of dozens of one-off integrations.

Manufacturers have run a version of this for decades over electronic data interchange, where the invoice travels alongside orders and ship notices. The real work for an accounts payable team is supplier onboarding, country-by-country rules, and archiving requirements, not the file format.

Frequently asked questions

What is e-invoicing?

E-invoicing is the exchange of invoices as structured electronic data passed directly between supplier and buyer systems, so the invoice arrives as machine-readable fields rather than paper or a scanned image. A true e-invoice is issued in a structured format, commonly XML such as UBL, that the receiving system can validate and post without any extraction step.

Is a PDF invoice an e-invoice?

A PDF attached to an email is a picture of an invoice rather than an e-invoice, because every PDF still needs extraction and review. One supplier that switched from mailed paper to emailed PDFs saw the buyer's touchless rate stay flat; when the same supplier later sent structured invoices over a network connection, 19 of 20 posted without a human touch.

What is the difference between e-invoicing and invoice automation?

Invoice automation processes whatever format arrives, including scans and PDFs, while e-invoicing fixes the input itself so there is nothing left to interpret. The two are complements: clean structured input is what lets automation reach very high touchless rates, so mature accounts payable teams pursue both.

Why do governments mandate e-invoicing?

Tax authorities use e-invoicing for tax control. Countries including Italy, Mexico, and Brazil require invoices to be issued or cleared through official platforms, and the list grows every year, so for companies operating in those markets e-invoicing is a compliance obligation rather than an efficiency project.

What is Peppol?

Peppol is a delivery network and format standard, originating in European public procurement, that lets trading partners exchange compliant e-invoices through one connection instead of dozens of one-off integrations. One contract manufacturer that registered through a Peppol access point saw its 40 largest customers receive structured invoices directly, rekeying disputes fade, and average approval time fall from 9 days to 3.

What is the hard part of an e-invoicing rollout?

The real work in e-invoicing is supplier onboarding, country-by-country compliance rules, and archiving requirements rather than the file format itself. Manufacturers have run structured invoicing for decades over EDI, where the invoice travels alongside orders and ship notices, so the technical pattern is proven; the operational rollout is what takes the time.