Universal Business Language is a royalty-free library of XML document definitions covering invoices, orders, despatch advices, credit notes and much of the rest of the commercial document set. It is maintained as an open standard and is one of the two syntaxes European e-invoicing commonly uses, the other being CII.
UBL supplies the grammar rather than the meaning. EN 16931 defines what an invoice’s fields mean; UBL defines how to write those fields as XML elements. Peppol BIS Billing combines the two and narrows the remaining choices so every document on the network is structured identically.
Why It Matters
Most businesses never edit UBL by hand, but the name appears constantly in software documentation, national mandate specifications and access point feature lists. Recognising that UBL is a syntax — not a competing standard to EN 16931, and not something you choose instead of Peppol — makes those specifications far easier to read. It is also why an invoice can be described as "UBL 2.1, EN 16931-compliant, Peppol BIS Billing 3.0" without contradiction: those are three layers, not three alternatives.
Example
A supplier exports an invoice as UBL 2.1. The file is plain XML: elements for the issue date, a sequential identifier, the supplier and customer parties with their tax identifiers, each line with quantity and price, and tax totals per rate. Any system that understands UBL can read it without a mapping document.
Frequently Asked Questions
Is UBL the same as XML?
No. XML is the general-purpose markup language; UBL is a specific set of document definitions written in XML. Every UBL file is XML, but the vast majority of XML is not UBL.
Do I need to understand UBL to send e-invoices?
No. Your software or access point produces and consumes it. The term is worth recognising mainly so you can tell whether a product’s stated capabilities match what a mandate or a customer requires.