What happened
UBL 2.5 is a standard, not a requirement. Documents valid under earlier 2.x versions remain valid, and the mandates cited in this article name UBL 2.1.
12 Aug 2026
Approved as an OASIS Standard
8
New document types
101
UBL document types in total, up from 93
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. If your organisation sends or receives e-invoices in Europe, there is a good chance UBL is already working somewhere in the background of your finance systems, whether or not anyone in the business has heard the name.
The release adds eight new document types and a longer list of smaller changes. It is backward compatible with every earlier 2.x version: a document that validated against an earlier 2.x schema validates against the 2.5 version of that schema. This article sets out what the specification says, what has been claimed about it since the announcement, and which UBL version the current mandates name.
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 read the same invoice. It has been developed since 2001 and is published by ISO as ISO/IEC 19845.
A dictionary is the nearest comparison. A new version adds entries. Which entries must be used is set by the specifications built on top of UBL, and whether e-invoicing is required at all is set by law. Those are two separate layers above the vocabulary itself.
The European standard for e-invoicing, EN 16931, has its own syntax bindings, which the European Commission’s eInvoicing resources describe as covering UBL 2.1 and UN/CEFACT CII. Peppol BIS Billing 3.0, the invoicing specification used on the Peppol network, validates invoices against UBL 2.1. A new UBL release does not change either of them.
National legislation and EU rules. Who must send and receive e-invoices, from when, and what happens if they do not.
France’s reform in force since 1 September 2026, Belgium since 1 January 2026, ViDA
Sets the obligationThe profiles built on top of UBL. They pin a version, narrow the vocabulary and add their own rules.
EN 16931, Peppol BIS Billing 3.0, national profiles. Both of the first two are bound to UBL 2.1.
Sets the fields and the versionUBL itself. A dictionary of business documents and the fields inside them. It defines what exists, never what you must use.
UBL 2.5, approved 12 August 2026
UBL 2.5 changed this layer, and only this layerHow big a release is this?
"UBL 2.5 is our most significant release since UBL 2.1." Kenneth Bengtsson, Chair of the OASIS UBL Technical Committee, 26 August 2026.
Counted by document types added, 2.5 is a mid-sized release: eight, against 34 for 2.1 in 2013, 16 for 2.2, ten for 2.3 and two for 2.4.
The reasons OASIS gives for the description are of a different kind. The announcement cites the introduction of component deprecation, support for ISO 14000 in the environmental structures, and groundwork for JSON and other syntax bindings in future releases.
UBL 2.1, the version that EN 16931’s syntax bindings and Peppol BIS Billing 3.0 use, was published in November 2013. The three releases since then added 28 document types between 2018 and 2024. Both bindings continue to use UBL 2.1.
UBL 1.0
2004
UBL 2.0
Dec 2006
UBL 2.1
Nov 2013
UBL 2.2
Jul 2018
UBL 2.3
Jun 2021
UBL 2.4
Jun 2024
UBL 2.5
Aug 2026
What is new
Four changes stand out. Three add new documents, and the diagram below groups all eight by purpose. The fourth is a change to the invoice itself.
Process: Billing
Invoice Status Request
Requests the status of a previously issued invoice.
Invoice Status Response
Answers for one invoice or several, and can carry payment details: amount paid, date paid, transaction reference.
Processes: Logistics (Delivery Note); seller to buyer (Work Report)
Delivery Note
Confirms the actual delivery of goods or services: items, quantities and shipment information.
Work Report
Reports work performed, from seller to buyer.
Process: Waste Shipment Management
Waste Notification
Notifies the competent authorities of a planned movement of waste.
Waste Movement
Reports the transport of waste, may reference the notification, and accompanies the consignment.
Contracting party to economic operator
Procurement Status
Describes the status of a procurement procedure, project or lot.
Procurement Status Request
Requests that status.
What each change contains
Invoice status. The Invoice Status Request asks for the status of a previously issued invoice. The Invoice Status Response answers. One response can cover several invoices, 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 the actual delivery of goods or services, with items, quantities and shipment information. The Work Report reports work performed, from seller to buyer. Invoices, credit notes and debit notes can reference both.
Waste, and procurement progress. The remaining four documents are for specific processes. The Waste Notification notifies the competent authorities of a planned movement of waste. The Waste Movement reports the transport, may reference the notification, and accompanies the consignment. The environmental structures extend to ISO 14000. The Procurement Status is sent by a contracting party to an economic operator to describe the status of a procurement procedure, project or lot, and the Procurement Status Request asks for it.
Collections for someone else, which is the change to the invoice. Invoices, credit notes and debit notes gain 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, where that party is not the buyer.
Where the new documents sit in a transaction
Taken together, the additions cover the stages around the invoice: what was ordered, what was delivered, what work was done, the status of the invoice, and whether it has been paid.
The invoice has been able to reference the order, the despatch advice and the receipt advice since UBL 2.0 in 2006, and to reference them line by line since UBL 2.1 in 2013. UBL 2.5 adds references to the Delivery Note and the Work Report, and the invoice-specific status request and response.
- OrderAlready in UBL
Order, Order Response
The invoice has been able to point at the order since UBL 2.0 in 2006, and match it line by line since UBL 2.1 in 2013.
- DeliveryNew in 2.5
Delivery Note
Confirms the actual delivery of goods or services: items, quantities and shipment information. The invoice can reference it.
- Work performedNew in 2.5
Work Report
Reports work performed, from seller to buyer. The invoice can reference it.
- InvoiceExtended in 2.5
Invoice, Credit Note, Debit Note
Gain references to the Delivery Note and Work Report, lines for amounts collected on behalf of a third party, and a beneficiary party.
- StatusNew in 2.5
Invoice Status Request, Invoice Status Response
A request for the status of one or more previously issued invoices, and the response.
- PaymentNew in 2.5
Carried inside the Invoice Status Response
Amount paid, date paid and a transaction reference, carried in the response.
What 2.5 deprecates
UBL 2.5 introduces component deprecation. Five document types and a number of fields are flagged as deprecated.
Under the specification, a deprecated component remains valid and fully supported in the 2.5 schemas, and documents that use it remain conformant. Its use is discouraged, and 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 "endorsed" schemas that exclude deprecated content, which implementers can use to detect deprecated components in existing documents.
One deprecated field is the buyer reference on the Invoice, Credit Note and self-billed documents, replaced by a buyer assigned reference structure. In EN 16931 that field is BT-10, and in Germany it carries the Leitweg-ID, which the federal administration’s e-invoicing guidance requires on every e-invoice. Those invoices are built on UBL 2.1 profiles, where the field is not deprecated, and deprecation does not affect conformance in any case.
| What is deprecated | What OASIS says to use instead |
|---|---|
| Freight Invoice, a separate document type for freight | The ordinary Invoice |
| Attached Document, a wrapper for carrying attachments | A specialised document envelope, such as the OASIS XHE |
| Enquiry and Enquiry Response | Document Status Request and Document Status |
| Order Response Simple | Order Response without order lines |
| Copy indicator, the flag marking a document as a copy, on most document types | Nothing. OASIS records "no consensus of real use cases for this" |
| Buyer reference on the Invoice, Credit Note and self-billed documents | The new buyer assigned reference structure |
Four claims, and what the specification says
Four claims have circulated since the announcement. The right-hand column sets out what the specification and the OASIS announcement say on each point.
| The claim | What the standard says |
|---|---|
| "UBL now supports JSON" | UBL 2.5 is defined in XML. The OASIS announcement says the release "lays the foundation for JSON and other syntax bindings in future releases", and the specification treats JSON representations of the UBL models as non-normative alternatives to the XML schemas. |
| "Tax authorities will use delivery notes to check VAT returns" | The specification states that UBL does not provide documents for tax reporting purposes; it provides structures to support the information on which taxes are based. Where tax authorities collect data beyond the invoice, they do so under their own national rules. |
| "Invoices will now be matched line by line to orders and deliveries" | Invoices have referenced orders, despatch advices and receipt advices since UBL 2.0 in 2006, and line by line since UBL 2.1 in 2013. UBL 2.5 adds references to the new delivery notes and work reports. All of these references are optional in the standard; whether any is required is set by the rules that apply to a given business. |
| "Businesses need to upgrade to UBL 2.5" | 2.5 is backward compatible with every earlier 2.x version, and none of the mandates in this article names it. Obligations come from the law in the countries where a business trades. |
What current mandates name
Governments set e-invoicing obligations through their own instruments. The table sets out the position in four of them as at 2 September 2026, and which standard, network or version each one names. The Publications Office of the European Union works with the OASIS UBL Technical Committee and is quoted in the announcement of this release.
| Where | Where it stands | What it names |
|---|---|---|
| France | The reform came into force on 1 September 2026, as the Ministry of the Economy confirms. All businesses must now be able to receive e-invoices; large and intermediate-sized businesses must also issue them and transmit transaction and payment data. The DGFiP puts everyone else at 1 September 2027 at the latest. | A core set of three formats: UBL, CII and Factur-X. The DGFiP technical specifications of 30 April 2026 state that the UBL format supported by the public portal conforms to OASIS UBL 2.1. Approved platforms must also support at least four invoice statuses: deposited, rejected, refused and cashed, the last carrying the payment date and amount. See our guide to French approved platforms. |
| Belgium | The Federal Public Service Finance has required structured e-invoices between Belgian VAT-registered companies since 1 January 2026, sent via the Peppol network. As the European Commission notes on its Belgian country page, a PDF sent by email is no longer sufficient. | Peppol BIS Billing 3.0 over the Peppol network. That specification validates invoices against UBL 2.1. Belgium is also preparing a five-corner e-reporting model. |
| United Kingdom | The government’s consultation response of November 2025 confirmed that it will mandate e-invoicing for all VAT invoices from 2029, with an implementation roadmap to follow at Budget 2026, which HM Treasury has set for 28 October. Real-time reporting is not part of the 2029 mandate. | The consultation response left the standard open. HMRC named Peppol as the core interoperability network in its Tax update 2026, and the detail is due in the roadmap. We cover it in Peppol as the UK’s core network. |
| European Union | Under the EU’s VAT in the Digital Age package, Member States have been able to introduce mandatory e-invoicing under specific conditions since April 2025. Cross-border digital reporting requirements apply from 1 July 2030. | EN 16931, whose syntax bindings the Commission describes as covering UBL 2.1 and UN/CEFACT CII. Our explainer on what ViDA changes sets out the full calendar. |
None of these four regimes names UBL 2.5. Where a UBL version is specified, it is 2.1.
What applies to each role
UBL 2.5 imposes no obligation on any of the roles below. The table sets out what the release contains that touches each one, and where the obligations come from.
| Role | What UBL 2.5 contains that touches this role | Where the obligations come from |
|---|---|---|
| Business owners | Nothing that changes an obligation. The release is backward compatible, and none of the mandates in this article names it. | National law in the countries where the business trades. Our country mandate tracker lists the position by country. |
| Finance, accounting and AP/AR teams | A standard Invoice Status Request and Response, with a place in the response for the amount paid, the date paid and a transaction reference. | National rules. France requires four invoice statuses under its own regulations, including a cashed status carrying the payment date and amount. |
| Procurement teams | A Work Report and a Delivery Note, both of which the invoice can reference. | None of the regimes in this article requires either document. |
| In-house tax teams | No tax reporting documents. The specification states that UBL does not provide them. | National and EU law. None of the instruments in this article names UBL 2.5. |
| E-invoicing vendors and their marketing teams | Eight new document types and a deprecation mechanism, all backward compatible with earlier 2.x versions. | The mandates in this article name UBL 2.1, or a network and specification built on it. None requires UBL 2.5. |
Summary
UBL 2.5 adds eight document types, introduces component deprecation, and remains backward compatible with every UBL 2.x version. Documents issued under earlier versions remain valid.
The mandates cited in this article name EN 16931, Peppol BIS Billing 3.0 or a national specification. Where they specify a UBL version, it is 2.1. None names UBL 2.5.
Sources. OASIS, Universal Business Language Version 2.5, OASIS Standard of 12 August 2026, in particular Section 5 on component deprecation and Appendix C, the revision history; and the OASIS announcement of the standard’s approval, 26 August 2026. Document counts, release dates and the deprecation list are taken from Appendix C.
European Commission: the eInvoicing Building Block, for EN 16931 and its syntax bindings; the eInvoicing in Belgium country page; and the Taxation and Customs Union pages on VAT in the Digital Age.
France: the Ministry of the Economy on the e-invoicing reform; the DGFiP reform information sheet, for the four mandatory invoice statuses; and the DGFiP Dossier de spécifications externes de la facturation électronique, version 3.2 of 30 April 2026, for the UBL 2.1 requirement.
Belgium: Federal Public Service Finance, on e-invoicing obligations. Germany: the federal administration’s e-invoicing guidance, on the buyer reference and the Leitweg-ID. United Kingdom: the government response to the consultation Promoting electronic invoicing across UK businesses and the public sector, 26 November 2025; HMRC, Tax update 2026: simplification, modernisation and fairness; and HM Treasury on the date of Budget 2026.
As at 2 September 2026, none of the mandates cited in this article names UBL 2.5.
Explore e-Invoice.app
Real-time compliance data, peer discussions, and cross-functional tools for every stakeholder.
Compare Countries
Side-by-side comparison of mandates, timelines, and technical requirements.
Open Compare ModeFind the Right Vendor
Get matched with e-invoicing vendors for your countries and ERP.
Start vendor match