UBL 2.5: e-invoicing is moving beyond the invoice
Sep 08, 2026
If you work with e-invoicing, you may have come across the abbreviation UBL. If not, now is a good time to get acquainted — because the standard behind much of Europe’s structured invoicing just had its biggest update in over a decade.
Universal Business Language (UBL) is an international open standard for structuring electronic business documents so different software systems can exchange and process them automatically. It covers far more than invoices: orders, delivery documents, credit notes and many other documents used in everyday trade.
UBL matters most in e-invoicing. UBL 2.1, published back in 2013, is still widely used today and is one of the technical foundations of European structured e-invoicing — Peppol BIS Billing 3.0, for example, currently runs on UBL 2.1.
On 26 August 2026, OASIS approved UBL 2.5, which its Technical Committee Chair Kenneth Bengtsson called the most significant UBL release since version 2.1. It adds eight new document types and expands the standard to reflect how digital business has changed over the past decade.
For e-invoicing, one shift stands out: the invoice is becoming just one part of a larger electronic conversation between buyer and seller.
What has changed since UBL 2.1?
A lot has happened since 2013.
Structured e-invoicing has moved well beyond its early focus on B2G and public procurement. B2B mandates are spreading across Europe and globally, Peppol has expanded, and near-real-time tax reporting is becoming the norm. At the same time, companies expect far more automation from their processes.
Simply getting an invoice from the supplier’s ERP into the buyer’s ERP is no longer the end goal. Businesses increasingly want structured information across the whole process: what was ordered, what was delivered, whether the invoice was accepted, whether there’s a dispute, and whether it has been paid.
This fits a wider trend: e-invoicing is gradually becoming part of a broader digital trade ecosystem connecting procurement, logistics, invoicing, compliance and payments.
What is new in UBL 2.5?
UBL 2.5 adds eight new business document types, taking the library from 93 to 101 documents:
- Delivery Note
- Invoice Status Request
- Invoice Status Response
- Work Report
- Procurement Status
- Procurement Status Request
- Waste Movement
- Waste Notification
Existing documents have also been expanded. Invoice and Credit Note structures now support additional purchase and delivery references, new parties such as the Beneficiary Party and Collected For Party, and more sophisticated payment and third-party collection scenarios.
Two further points signal where UBL is heading: the release adds support for ISO 14000 environmental standards, and lays the groundwork for JSON and other syntax bindings in future versions. Crucially, UBL 2.5 keeps backward compatibility with all existing UBL 2.x implementations — the standard evolves without forcing anyone to rebuild working integrations.
The new documents span very different areas, from procurement and logistics to environmental reporting. But for anyone following e-invoicing, Invoice Status Request and Invoice Status Response deserve particular attention.
Knowing what happened after the invoice arrived
Traditionally, electronic invoicing has focused on delivery. The seller sends an invoice; the invoice reaches the buyer; ideally both sides get confirmation it arrived. In simplified form:
Invoice sent → Invoice received
From a business perspective, that leaves the important questions unanswered. Was the invoice accepted? Rejected because of incorrect data? Approved? Disputed? Paid?
UBL 2.5 introduces standard document structures for requesting and communicating invoice status, supporting a much richer exchange across the whole lifecycle:
Sent → Received → Accepted / Rejected → Processed → Paid
It may sound like a small technical addition. In practice, it reflects a real change in thinking about what “digital” means for an invoice.
Regulation is moving in the same direction
UBL isn’t evolving in isolation. Regulators are increasingly interested in what happens to an invoice after it is issued.
France’s new B2B e-invoicing system, whose first mandatory phase went live on 1 September 2026, includes an invoice-lifecycle concept, using status messages to communicate events during processing.
Spain goes further still. Under Royal Decree 238/2026, invoice recipients must report the status of each invoice — commercial acceptance or rejection, and full payment, including the relevant dates — within four calendar days. The stated aim is end-to-end visibility across the invoicing lifecycle, and a tool against late payment.
These national systems use different technical approaches, so this does not mean UBL 2.5 has become the standard for lifecycle reporting in France or Spain. The point is the direction of travel: regulation, business needs and now the underlying document standards are all moving toward more structured communication about the whole transaction.
From document exchange to business-process exchange
This matters because the biggest gains from electronic data exchange rarely come from swapping one document format for another.
Replacing a PDF invoice with an XML invoice is useful — it removes manual data entry and enables automated processing. But the real value appears when documents are connected: an electronic order leads to an electronic delivery note; the delivery is matched to an invoice; the invoice is validated automatically against order and receipt; its status flows back to the supplier; payment information closes the loop.
At that point we are no longer just exchanging documents. We are digitising the business process between companies.
For companies already using EDI, this is hardly new — orders, order responses, despatch advices, receiving advices and invoices have formed connected document flows for years. What’s notable is that the wider e-invoicing world is now moving in the same direction.
Does UBL 2.5 mean Peppol will change immediately?
No.
The publication of UBL 2.5 does not mean existing systems will suddenly migrate off UBL 2.1. Peppol BIS Billing 3.0 continues to use UBL 2.1. Any future adoption of UBL 2.5 will depend on updates to specifications such as Peppol BIS, EN 16931 and national frameworks, and is expected to be progressive rather than immediate. Some changes may still appear sooner through national extensions.
So businesses don’t need to start rebuilding integrations because UBL 2.5 has arrived. But ERP providers, e-invoicing operators and anyone designing new automated processes should be paying attention now.
The invoice is becoming part of a larger data flow
The most important message from UBL 2.5 isn’t about version numbers or XML structures — it’s about where digital business is heading.
An invoice used to count as “successfully digital” once it could travel automatically from one system to another. Increasingly, companies need their systems to keep communicating after that point. The invoice has become one event in a longer, structured process connecting purchase, delivery, invoicing, approval, compliance and payment.
UBL 2.5 reflects that shift. Adoption will take time, but the direction is clear: the future of e-invoicing isn’t simply better electronic invoices — it’s better business-process automation between companies.
“For most of our customers, the hard part was never sending the invoice — it was knowing what happened to it afterwards. UBL 2.5 finally treats invoice status as structured data, not a phone call or a chase-up email. That’s the direction we’ve been building toward for years on the EDI side, and it’s good to see e-invoicing catch up.” — Hele Hammer, CEO, Telema
Need help navigating international e-invoicing requirements?
Telema helps companies exchange compliant e-invoices across different countries, networks and ERP systems — without having to manage every format and local requirement in-house. As standards like UBL 2.5 evolve, we track the changes so our customers don’t have to.