Best practice and case studies for Finance, Shared Services and Indirect Tax professionals. Automation tips and strategies in our webinars, articles, events.

UBL Gets Major Update After 13 Years

{{article.author.firstname}} {{article.author.lastname}}
Susie West
Sep 7, 2026
lightbulb

OASIS has officially published UBL 2.5, bringing a significant update to one of the standards sitting underneath global e-invoicing.¹

The interesting part is just how much has changed since the version many businesses know best.

UBL 2.1 was published in 2013.

Since then, e-invoicing has moved from predominantly B2G adoption in many markets towards large-scale B2B mandates, continuous transaction controls and increasingly connected digital trading environments.

UBL itself has continued to evolve through versions 2.2, 2.3 and 2.4. But UBL 2.1 remains particularly important to e-invoicing, including as the UBL syntax underlying Peppol BIS Billing 3.0.

UBL 2.5 expands the standard again.

**Among the changes:**¹

  • Eight new business document types, taking UBL from 93 to 101
  • New Invoice Status Request and Invoice Status Response documents
  • Improved invoice status tracking
  • Enhanced payment referencing
  • Support for collections on behalf of third parties
  • New support around waste transport management
  • A new deprecation mechanism allowing UBL to evolve without breaking existing implementations

For e-invoicing, the addition of dedicated invoice status documents is particularly interesting.

The Invoice Status Request allows a party to request the status of one or more previously issued invoices, while the Invoice Status Response provides information back on their status.²

The direction of travel is increasingly towards an invoice being part of a much wider digital transaction lifecycle — not simply a structured document sent from supplier to buyer.

Importantly, this does not mean Peppol or EN 16931 implementations suddenly move from UBL 2.1 to UBL 2.5.

In fact, OASIS technically classifies UBL 2.5 as a minor revision, precisely because it preserves backwards compatibility with earlier UBL 2.x versions.¹

So this is evolution rather than replacement.

Thirteen years after UBL 2.1, the underlying language of electronic business documents is evolving for a very different e-invoicing world.

Sources

  1. OASIS Open, Universal Business Language Version 2.5, 2026. OASIS UBL 2.5 specification
  2. OASIS Open, UBL 2.5 Invoice Status Request / Invoice Status Response. OASIS Invoice Status Request specification


This content is intended to share insights and practical considerations based on industry experience. It does not constitute legal, regulatory, or financial advice. Regulatory requirements vary by jurisdiction and circumstance, so any compliance-related matters should be reviewed and validated with your own professional advisors.