Glossary
UBL
Also known asUBL 2.1UBL XMLUBL invoice
UBL 2.1 is the XML syntax in which Peppol writes a structured invoice: it defines the element names that carry the data set by the European standard EN 16931, without saying which values are allowed.
EN 16931 recognises two XML syntaxes for a European e-invoice, UBL 2.1 and UN/CEFACT CII. Peppol BIS Billing requires UBL, a receiver may accept CII in addition, and Belgian law names Peppol BIS in its UBL version as the default format for structured invoices; another syntax is possible only by agreement with the customer. In UBL an invoice and a credit note are two different documents, Invoice and CreditNote, which Peppol treats as two separate document types.
UBL is the first of three layers checked when an invoice is validated: the UBL 2.1 schema tests whether the file follows the structure, the EN 16931 business rules test whether the data and sums hold together, and the Peppol BIS Billing rules add Peppol’s restrictions and code lists. A business never writes this XML itself. It enters correct business data, and its invoicing software turns them into a valid file, in which a readable PDF copy and attachments can be embedded.
In practice
- For an invoice within the Belgian obligation the UBL file is the invoice; a PDF that travels with it is a readable copy.
- A validation error is fixed by correcting the source data and generating the file again, not by editing the XML by hand, which creates new mismatches.
- FPS Finance strongly recommends keeping the original XML of every invoice sent and received for the seven-year retention period, although the law does not impose the original format.