Skip to content

Term explained

UBL e-invoice (EN 16931)

The structured XML invoice format used across Peppol so systems exchange line-level data without retyping.

What it is and why it matters

Universal Business Language (UBL) places every invoice element — supplier identifiers, PO reference, line items, VAT breakdown and totals — in a standardized XML structure under European norm EN 16931. Accounting and P2P software reads it deterministically without OCR guesswork.

How it works in Fiatto

Fiatto issues sales e-invoices in EN 16931 UBL over Peppol and ingests incoming UBL and CII e-invoices straight into duplicate detection and three-way matching. Learn more →

UBL e-invoicing in practice

A PDF invoice is formatted for human eyes, forcing OCR tools to guess which text is the PO number, line quantity or tax rate. A UBL file stores every field in standardized EN 16931 XML tags so receiving software reads line items deterministically.

That precision unlocks reliable line-level three-way matching: order references, unit prices and quantities map straight onto the purchase order without manual field corrections.

Frequently asked questions

What is the difference between UBL and Peppol?

UBL is the structured XML data format of the electronic invoice itself, whereas Peppol is the secure delivery network used to route that UBL invoice from sender to recipient.

Can finance staff still read a UBL invoice visually?

Yes. Purchasing and accounting software renders every UBL file into a clean human-readable invoice view on screen, and many UBL messages also carry an embedded visual representation.

Want to see how this works in your own process?