Skip to content

Peppol e-invoicing

Electronic invoicing (e-invoice) explained

An e-invoice is not a PDF sent by email. We explain what a structured e-invoice is (UBL, EN 16931), its mandatory fields, and why it is faster, cheaper and error-free compared with paper and PDF.

Updated 2026-06-17

The term electronic invoice (e-invoice) is often confused with a PDF sent by email. That’s a misunderstanding that will start costing companies time and money as mandates roll out. A true e-invoice is a structured data document, not an image. This article explains what it looks like, its mandatory fields, and why it is fundamentally better than paper and PDF.

A PDF is not an e-invoice

A PDF invoice is essentially a scanned or printed image of text. A human reads it fine, but a computer cannot — the buyer’s accounting system has to retype it manually or run error-prone OCR. That’s why a PDF emailed as an attachment does not meet the structured e-invoicing requirements introduced by the 2027 mandate and ViDA.

Structured e-invoices: UBL and the EN 16931 norm

A real e-invoice is a file in UBL (Universal Business Language) — a machine-readable document where every value has a precisely defined place. The European norm EN 16931 defines which fields an invoice must contain and in what form; Peppol BIS Billing 3.0 is the profile these invoices travel in across the Peppol network.

The benefit: when an invoice conforms to the norm, any system on the other side reads it without errors — whether the buyer runs SAP, a local accounting package or a custom ERP.

Mandatory fields of an e-invoice

An e-invoice contains the same details as a classic invoice, just in a precise structure:

  • identification of supplier and buyer, including company and VAT IDs,
  • dates of issue, supply and payment,
  • individual line items with quantity and unit price,
  • VAT rates and amounts by tax treatment,
  • payment method and details (IBAN, reference),
  • reference data (order number, contract, etc.).

A good Access Point validates every invoice against EN 16931 before sending, so formal errors — a missing VAT ID, a wrong rate — are caught up front rather than surfacing as a buyer dispute.

Why an e-invoice beats paper and PDF

  • No retyping or OCR — data flows straight into accounting.
  • Fewer errors and disputes — mandatory fields are verified.
  • Faster payment — the invoice is in the buyer’s system in seconds.
  • Lower cost — no paper, postage or manual processing.
  • Audit trail — delivery is confirmed and traceable.

How to start sending and receiving e-invoices

You don’t need to change your accounting software or set up an IT department. Either you use the Peppol Box web inbox, or we connect your accounting/ERP system via REST API and invoices flow automatically. Receiving e-invoices is free forever with Verteco, with sending on a clear flat fee — details in the pricing.

Get ready ahead of time — activate your free inbox today.

Peppol FAQ

Frequently asked questions

Is a PDF invoice an electronic invoice?

In the legal sense of the new regime, no. A PDF is an image of a document a human or OCR must read. A true e-invoice is a structured data document (UBL / EN 16931) that an accounting system processes automatically. That is the format Peppol and the mandate require.

What fields must an electronic invoice contain?

The same as a classic invoice (supplier and buyer details, VAT ID, supply and due dates, line items, tax rates and amounts, payment details) — but in the precisely defined structure of EN 16931. Validation against the norm catches missing or incorrect fields before sending.

Do I have to archive e-invoices?

Yes, there is a statutory duty to retain invoices. Verteco archives every document for the statutory 10-year period in the EU and in an audit-ready form — the archive is included.

Keep reading

More from the Peppol hub

Get ready before 2027

Activate your free Peppol inbox today

Receiving e-invoices is free forever on our own certified Slovak Access Point — no card, no lock-in, live in minutes. Sending and ERP integration when you need them.