Universal Business Language (UBL) is an open standard developed by OASIS (Organization for the Advancement of Structured Information Standards) for the structured electronic exchange of business documents, with UBL 2.1, published in 2013, remaining widely implemented today.
Its scope extends far beyond e-invoicing, covering a broad range of business documents and processes, from procurement and ordering to delivery, invoicing and payment.
A short while ago, OASIS officially published UBL 2.5 [↗︎], a major new release that updates existing documents and introduces new ones to address evolving business and regulatory requirements.
These changes will also have implications for e-invoicing, although how and when UBL 2.5 will be incorporated into existing standards, networks and national frameworks has yet to be defined.
Why was a new UBL version needed?
UBL 2.5 is not simply an update of the UBL format but, as Kenneth Bengtsson, Chair of the OASIS UBL Technical Committee, stated in a recent press release about the new version [↗︎]: “UBL 2.5 is our most significant release since UBL 2.1.”
Since UBL 2.1 was published in 2013, the way businesses exchange information has evolved considerably. Global trade, logistics, supply chains and digital commerce have become increasingly interconnected and complex, while new regulatory and operational requirements have emerged across both the private and public sectors.
UBL 2.5 has therefore been developed to better reflect these real-world requirements. According to OASIS, the new version notably expands support for e-commerce, retail transactions, global trade and logistics, as well as circular economy and waste-management requirements.
The objective is not to redesign UBL, but to extend a standard already widely implemented around the world to support new business processes and more complex operational scenarios, while maintaining backward compatibility with existing UBL 2.x implementations.
What actually changes with UBL 2.5?
UBL 2.5 introduces changes across the broader UBL business-document framework. Existing documents have been updated and eight entirely new document types have been introduced, bringing the UBL library to 101 business documents:
- Delivery Note
- Invoice Status Request
- Invoice Status Response
- Work Report
- Procurement Status
- Procurement Status Request
- Waste Movement
- Waste Notification
They illustrate the broader scope of the new version, covering areas ranging from procurement and delivery to invoice lifecycle management and environmental compliance.
But UBL 2.5 is not only about adding new documents: existing documents, including Invoice and Credit Note, have also evolved. New fields have been introduced, existing structures have been refined and some cardinalities have been changed, allowing the standard to represent additional or more complex business scenarios.
What will UBL 2.5 change specifically for e-invoicing?
For electronic invoicing, these changes arrive at a particularly important time, as B2B e-invoicing mandates are rapidly expanding worldwide and the ViDA directive is around the corner.
Today, UBL 2.1 remains one of the main technical foundations of structured e-invoicing. It is notably the syntax used by the Peppol network (Peppol BIS Billing 3.0), and together with UN/CEFACT CII, one of the two standardized syntaxes used to implement EN 16931 in Europe.
However, UBL 2.1 was established more than a decade ago, at a time when many of the major structured e-invoicing initiatives, particularly in Europe, were still predominantly focused on B2G (Business-to-Government) and public procurement transactions.
Since then, the landscape has changed considerably, with structured e-invoicing progressively expanding into large-scale B2B exchanges, involving a much greater diversity of organizations, business activities, commercial models and operational requirements.
To support these business needs, an invoice should not be considered only as a tax and compliance document, but also as a business document integrated into an end-to-end commercial process, from procurement and delivery to payment and lifecycle management.
UBL 2.5 clearly supports this evolution by enriching the Invoice and Credit Note structures to address more complex business scenarios. It notably introduces additional purchase and delivery references, new parties such as the Beneficiary Party and Collected For Party, and enhanced support for payment and collection scenarios.
But supporting an end-to-end invoicing process does not stop with the invoice itself. Once an invoice has been issued, businesses also need to exchange information about its processing and status throughout its lifecycle.
UBL 2.5 addresses this need with the introduction of new Invoice Status Request and Invoice Status Response documents.
These new documents also raise an interesting question: could UBL 2.5 eventually provide a more standardized way of managing invoice lifecycle messages, which are currently implemented differently by Peppol and by some national e-invoicing frameworks, such as France, notably through UN/CEFACT CDAR lifecycle messages?
When will changes regarding e-invoicing formats be enacted?
The publication of UBL 2.5 does not mean that e-invoicing mandates will immediately migrate from UBL 2.1 to UBL 2.5.
For the time being, existing specifications remain applicable, and Peppol BIS Billing 3.0, for example, continues to use UBL 2.1. Any transition to UBL 2.5 is expected to be progressive and will depend on future updates of the underlying standards and specifications, including EN 16931, Peppol specifications and national e-invoicing frameworks.
Some changes may nevertheless emerge progressively, including in the near term, notably through national extensions.
