Electronic invoicing

E-invoice

An e-invoice is an invoice issued, transmitted and received in a structured data format that allows automatic electronic processing. In the EU standards context, emailing a PDF or image does not by itself create an e-invoice because its data is not structured for direct machine processing. Specific formats, exchange methods and national rules determine what a recipient can accept.

Also called: Electronic invoice, structured electronic invoice, eInvoice
Core characteristic: Machine-readable, structured invoice data
Different from: An ordinary PDF, image, scan or unstructured email
Examples: Structured XML using an accepted syntax and profile
Last reviewed: 3 September 2026

Why this matters when you invoice

A buyer's system can import structured invoice fields without retyping them. That can support routing, matching and approval, but only when the document structure, business rules and exchange method meet the recipient's requirements.

What makes the invoice electronic and structured

The invoice data is represented in defined, machine-readable fields.
The sender issues and transmits that structured invoice.
The receiver can accept and electronically process the structure.
The syntax, profile, identifiers and delivery route match the applicable requirements.

A readable screen or print view can be generated from the data. Its appearance is useful to people, but it is not what makes the document a structured e-invoice.

Worked example

PDF attachment versus structured invoice data

A supplier emails a visually clear PDF to a customer. A person can read it, but the accounting system may need manual entry or extraction. If the supplier instead sends correctly structured invoice data in a format and route the customer accepts, the customer's system can import and process the fields directly.

Common mistakes

Calling any invoice sent by email an e-invoice.
Assuming an XML file is valid merely because it can be opened.
Confusing a readable rendering with the structured invoice itself.
Assuming one format or delivery route works for every country and recipient.

Create or inspect structured invoice XML

InvoiceCraftly can export an EN 16931 / UBL XML invoice file in beta when the required invoice details are ready. You can also use the XML viewer to open supported Peppol, UBL, OIOUBL or Finvoice XML, inspect mapped invoice details and review deterministic preflight findings.

View supported e-invoice XML Compare with a PDF invoice

The XML export and viewer do not certify formal EN 16931, Peppol, national-profile, or recipient compliance. Peppol, EHF, NemHandel, and other network delivery remain separate steps through a compatible service or network.

Official references

Sources and terminology reviewed 3 September 2026. Next evidence review: 2 December 2026.

Frequently asked questions

Is a PDF invoice an e-invoice?

An ordinary PDF is not an e-invoice under the EU structured-data definition because its invoice data is not issued, transmitted and received for automatic electronic processing.

Can a structured e-invoice be read by a person?

Yes. Software can render structured invoice data into a human-readable view, but the structured data remains the invoice's machine-processable foundation.

Can InvoiceCraftly export a structured e-invoice?

Yes. InvoiceCraftly can export an EN 16931 / UBL XML invoice file in beta when the required invoice details are ready. Network delivery and formal compliance or recipient acceptance remain separate requirements.