UBL 2.5 is here: what changes for your business, and what doesn’t

What happened

On 12 August 2026 the Universal Business Language, better known as UBL, was approved as an OASIS Standard at version 2.5. OASIS announced it on 26 August.

The release adds eight new document types and a long list of smaller changes. It is backward compatible with every earlier 2.x version, which means an invoice that validated last month still validates today. This article sets out what the specification contains, and checks four claims made about the release against it.

What UBL is, and what it is not

UBL is a shared vocabulary for business documents: orders, despatch advices, invoices, credit notes and close to a hundred others. It defines what each piece of information is called and where it sits, so that two systems that have never met can still read the same invoice. It has been developed since 2001 and is published by ISO as ISO/IEC 19845.

Think of it as a dictionary. A new version adds words to the dictionary. It does not decide which words you must use, and it does not decide whether you must write at all. Those decisions sit one and two layers above UBL: in the specifications built on top of it, and in the law that points at those specifications.

That layering explains why a major standards announcement can be significant without, by itself, changing what businesses are required to do. The European standard for e-invoicing, EN 16931, can be written in two technical formats, which the European Commission’s eInvoicing resources list as UBL 2.1 and UN/CEFACT CII. Peppol BIS Billing 3.0, the invoicing specification used on the Peppol network, also checks invoices against UBL 2.1. A new UBL release does not change either of them by itself.

How big a release is this?

Counted by document types added, the eight in 2.5 compare with 34 in 2.1 (2013), 16 in 2.2, ten in 2.3 and two in 2.4.

The OASIS announcement points to other changes: 2.5 is the first release that can mark parts of the standard for possible removal, it adds support for ISO 14000 environmental information, and it lays the foundation for JSON and other formats in future releases.

UBL 2.1, the version the European standard and Peppol BIS Billing 3.0 use, was published in November 2013. Three releases followed it, adding 28 document types between 2018 and 2024.

What is new

The release adds eight new documents, shown below in four groups by purpose. It also changes the invoice itself, adding lines for amounts collected on behalf of a third party.

The changes in more detail

Invoice status. The Invoice Status Request and Invoice Status Response give businesses a standard way to ask where an invoice has got to, and to answer. The response is not limited to one invoice at a time, and it can carry payment details alongside the status: amount paid, date paid, and a transaction reference.

Delivery notes and work reports. The Delivery Note confirms what was actually delivered, with items, quantities and shipment information. The Work Report records work carried out. Invoices, credit notes and debit notes can now reference both.

Waste, and procurement progress. The remaining four documents cover waste shipments and public procurement. OASIS describes the circular economy as a major focus of the release: Waste Notification tells the competent authorities about a planned movement of waste, and Waste Movement travels with each consignment. Procurement Status and Procurement Status Request let a contracting authority report on the progress of a procurement procedure, project or lot.

Collections for someone else, which is the change to the invoice. Invoices, credit notes and debit notes can now carry separate lines for amounts collected on behalf of a third party, and documents can identify a beneficiary party: the party a transaction is ultimately intended for, even where that party is not the buyer.

Where the new documents sit in a transaction

Taken together, the new documents cover the stages around the invoice: what was delivered, what work was done, where the invoice has got to, and whether it has been paid.

Invoices could already reference the order, the despatch advice and the receipt advice in UBL 2.0 (2006), and line by line in UBL 2.1 (2013). UBL 2.5 adds references to the Delivery Note and the Work Report, and a status request and response built for invoices.

What 2.5 flags for removal, and why nothing breaks

UBL 2.5 is the first version that can mark parts of the standard as deprecated, meaning flagged for possible removal. Five document types and a handful of fields are now flagged.

A deprecated component is still valid, still fully supported by the 2.5 schemas, and documents that use it remain conformant. OASIS says its use is discouraged and that it may be removed in a future major version. UBL has not had a major version since 2.0 in 2006. The release also includes optional versions of its schemas that leave out deprecated content, which software providers can use to find deprecated items in existing documents.

Four claims, and what the standard says

Four claims have been circulating since the announcement. The right-hand column sets out what the specification and the OASIS announcement say.

The bottom line

UBL 2.5 is the latest version of a standard OASIS describes as the leading interchange format for business documents. It adds document types for the stages around the invoice, including an invoice status request and response, a delivery note and a work report, without invalidating any document issued under an earlier 2.x version.

UBL 2.5 does not create an obligation by itself. Obligations to use e-invoicing, and any particular UBL version, are set by governments and tax authorities.