Companies exchange large volumes of documents with one another every day: quotes, orders, order confirmations, shipping notices, invoices, and credit memos. Many of these documents are still sent as PDFs, via email, or through separate portals. While these are easy for people to read, such documents are often not immediately usable by systems.
Universal Business Language, better known as UBL, was developed to enable the exchange of business documents not only digitally but also in a structured format. The data in an invoice, purchase order, or delivery note is assigned a fixed meaning and position.
This allows software to process the information directly.
UBL thus forms an important technical foundation for electronic data exchange between organizations. The standard is used internationally and plays a central role in electronic invoicing and Peppol, among other areas.
1. What is UBL?
UBL stands for Universal Business Language. It is an open standard developed by OASIS for the electronic exchange of business documents.
The standard defines data structures for various commercial documents. These include not only invoices and credit memos, but also, for example, orders, order confirmations, catalogs, shipping notices, and acknowledgments of receipt.
UBL describes how the information in such a document is structured and recorded.
For an invoice, this might include:
- invoice number;
- invoice date;
- supplier;
- customer;
- VAT ID;
- currency;
- order reference;
- invoice lines;
- quantities;
- prices;
- VAT rates;
- payment details;
- and totals.
This data is not placed randomly. UBL defines which elements are available and how they relate to one another.
The information is typically recorded in XML. This results in a file that is less readable by humans but is, in fact, very well-suited for processing by software.
UBL and XML are not the same thing.
XML is the technical language used to store data in a structured format. UBL then determines which business data elements appear within that structure and what they mean.
2. From Digital Invoice to Structured Invoice
An important distinction in electronic invoicing is the difference between a digital document and a structured electronic document.
A PDF invoice is digital, but it is primarily intended to be read by people.
For example, the invoice states:
Invoice number: 2026-10453
An employee immediately understands what this means. For software, however, that meaning is less obvious. First, the system must determine where the invoice number is located and which text or value corresponds to it.
OCR or document recognition can be used for this purpose.
With a UBL invoice, this is not necessary. The invoice number is located in a data element designated for that purpose. As a result, the receiving system immediately knows that the value in question is the invoice number.
The same applies to other data.
An amount is not merely displayed as text but is assigned a specific meaning within the data structure—such as line item amount, VAT amount, or total amount due. The currency, supplier, and references are also recorded as separate data points.
This enables direct system processing.
3. UBL Is More Than Just an Invoice Format
In the Netherlands, UBL is often primarily associated with electronic invoices. This is because UBL is widely used in e-invoicing and Peppol.
But the standard is considerably broader.
UBL includes data models for various steps within commercial processes. In addition to Invoice and CreditNote, there are, for example, document types for Order, OrderResponse, Catalog, DespatchAdvice, and ReceiptAdvice.
This allows a larger portion of a Purchase-to-Pay or Order-to-Cash process to be digitized according to the same principles.
Consider, for example, a procurement process:
order → order confirmation → shipment → receipt → invoice
When these messages are exchanged in a structured manner, systems can refer to the same transactions and references throughout the entire process.
For example, an order contains an order number. That order number can reappear in the order confirmation, the shipping notification, and ultimately the invoice.
This creates a digital chain of related transactions.
4. UBL, Peppol, and EN 16931 each have a different role
UBL is often mentioned in the same breath as Peppol. However, the terms are not interchangeable.
UBL primarily describes how an electronic business document can be technically structured.
Peppol goes further.
Peppol provides standards for interoperability and a network through which organizations can exchange electronic business documents. Within Peppol, there are Business Interoperability Specifications (BIS), which precisely define which data must be used for a specific process and which rules apply.
EN 16931 also plays an important role in electronic invoicing in Europe.
EN 16931 defines the semantic data model for the core data of an electronic invoice. It thus describes what business information an e-invoice contains and what that information means.
UBL can then be used as the technical syntax in which that data is defined.
Peppol combines these different layers.
EN 16931
specifies what information a European electronic invoice contains semantically.
UBL
provides a technical structure in which that information can be recorded.
Peppol BIS/PINT
defines how a specific subset of that information must be used within a business process.
Peppol network
ensures that the message can be transmitted from the sender to the recipient.
5. Not every UBL invoice is the same
This is one of the most important considerations regarding UBL.
The standard has been deliberately designed to be comprehensive.
This makes UBL suitable for a wide range of countries, sectors, and business processes, but it also means that two organizations may use different parts of the standard.
So, if Organization A creates a UBL file and Organization B also supports UBL, full interoperability is not automatically guaranteed.
Additional agreements are required to ensure this.
For example, a specification might stipulate:
- which UBL elements are mandatory;
- which elements may not be used;
- which code lists are permitted;
- how parties must be identified;
- which VAT rules apply;
- and what business rules apply between values.
Peppol does exactly that.
A Peppol BIS does not make unlimited use of all the capabilities of UBL, but applies a specific set of rules.
6. The value of UBL lies in automated processing
Sending an XML file is not an end in itself.
The true value of UBL lies in the ability to automatically process the data on the receiving end.
For example, when an invoice is received, a technical check can first be performed to verify that the document conforms to the agreed-upon structure.
Additional checks can then be performed.
Does the supplier exist? Does the VAT number match? Is there an order number? Has the invoice been received before? Are the amounts and VAT calculations correct?
Afterward, the invoice can, if necessary, be automatically linked to a purchase order and a receipt.
When the purchase order, receipt, and invoice match, further manual processing can largely be eliminated.
This enables straight-through processing.
The difference from document recognition is fundamental.
With a PDF, software first attempts to determine what information is contained in the document. With UBL, that meaning is already defined before the document is sent.
Recognition gives way to validation.
7. UBL as Part of a Broader Document Exchange Landscape
In practice, virtually no organization works exclusively with UBL.
Suppliers and customers use different ERP systems, networks, messaging standards, and transport channels.
One supplier sends a UBL invoice via Peppol. Another delivers an XML file via SFTP. A major trading partner uses EDI. A smaller supplier still sends a PDF via email. Within a specific sector, DICO may also be used, for example.
On the receiving end, an organization ultimately wants to abstract these differences as much as possible.
This is where an integration layer such as 4CEE Exchange comes into play.
Various channels can converge there, such as Peppol, API, SFTP, EDI, and email. Messages can be validated and, where necessary, converted between formats such as UBL, Peppol BIS, DICO, XRechnung, Factur-X, or an ERP-specific format.
UBL is a key building block within such a landscape.
Its strength lies not only in XML or in the standard itself, but in the fact that organizations agree in advance on the meaning of the data.
As a result, an invoice no longer needs to be read to understand its contents.
The data can move directly from system to system.