UBL (Universal Business Language)
UBL (Universal Business Language) is an OASIS standard XML library of business document formats — order, catalogue, despatch advice, invoice, and related documents — built for electronic procurement and invoicing across supply chains. It's an ISO/IEC standard (19845) and is the document format underlying PEPPOL, the network most European public-sector and cross-border e-invoicing runs on. Where cXML and OCI are punchout-centric protocols built around North American procurement platforms, UBL is document-centric: it defines what a compliant order or invoice looks like, independent of how it's transmitted.
What UBL actually defines
UBL is a library of XML schemas for the documents a buyer and supplier exchange across a transaction: Catalogue, Order, Order Response, Despatch Advice, Invoice, Credit Note, and dozens more. OASIS first published it in 2004, aimed originally at small and mid-sized business e-commerce; it's since become the document standard most e-procurement and e-invoicing infrastructure builds on, particularly in Europe. UBL 2.1 was ratified as ISO/IEC 19845, and OASIS continues to extend it — recent versions add document types for waste transport, third-party collections, and expanded procurement status messaging.
Unlike EDI formats built around fixed-width or delimited segments, UBL documents are XML, with an explicit, machine-validatable schema for each document type.
UBL and PEPPOL
PEPPOL (Pan-European Public Procurement Online) is the network; UBL is the document format most PEPPOL message types are built on. A supplier sending an invoice through PEPPOL to a government buyer in a mandating country is, underneath the network routing, sending a UBL Invoice document that conforms to a PEPPOL-specific profile (a PEPPOL BIS).
That pairing has made UBL the default e-invoicing format across public procurement in much of the EU, plus adoption in Turkey, Peru, Colombia, and Panama. A supplier selling into any of those markets is likely to encounter a UBL-formatted requirement even without dealing with PEPPOL directly, since national e-invoicing mandates frequently specify UBL as the accepted schema.
UBL vs. cXML vs. OCI vs. EDI
These get grouped together as "procurement integration standards," but they solve different parts of the problem and come out of different regions:
| Standard | Primary use | Typical region |
|---|---|---|
| UBL | Document schema for orders, invoices, catalogues | Europe, LatAm public sector, PEPPOL |
| cXML | Punchout session and document exchange with procurement platforms (Ariba, Coupa) | North America |
| OCI | Punchout protocol native to SAP procurement | Global, SAP-centric |
| EDI / EDIFACT | Batch transaction exchange (POs, invoices, ASNs) over established EDI networks | Global, especially retail and logistics |
A distributor selling across regions doesn't get to pick one: a North American retail EDI trading partner, a SAP customer expecting an OCI punchout, and a European public-sector buyer on PEPPOL are three separate integration requirements on the same catalog.
Where it touches the catalog
The UBL Catalogue document type carries product identification, description, classification, and pricing — the same underlying data a PIM already manages, reshaped into UBL's schema. A supplier onboarding onto a PEPPOL-connected buyer or a country's e-invoicing mandate needs that product and pricing data mapped into UBL structures, which is a mapping exercise on top of clean source data rather than a reason to maintain a second copy of the catalog.
Frequently asked questions
Is UBL the same thing as PEPPOL?
No. PEPPOL is the network and the set of transport, addressing, and validation rules that route a document between trading partners. UBL is the XML document format most PEPPOL message types (invoices, orders, catalogues) are built on, typically constrained further by a PEPPOL-specific profile called a PEPPOL BIS. A UBL document can exist outside PEPPOL; PEPPOL messages are usually, but not exclusively, UBL.
Is UBL used in the United States?
Much less than in Europe. U.S. B2B procurement integration runs more often on cXML, OCI, or traditional EDI/EDIFACT, and the U.S. hasn't adopted a nationwide e-invoicing mandate the way many EU countries have. UBL still shows up for U.S. suppliers selling into UBL-mandating markets — much of the EU, plus Turkey, Peru, Colombia, and Panama.
How is UBL different from cXML?
cXML is built around punchout — a live session where a buyer's procurement system opens a supplier's catalog UI, and structured documents move as part of that interaction. UBL is document-centric rather than session-centric: it defines the schema for a catalogue, order, or invoice independent of the transport mechanism, which is why it pairs with a network like PEPPOL rather than defining a punchout flow of its own.
Who maintains the UBL standard?
OASIS (Organization for the Advancement of Structured Information Standards), the same body that maintains a range of other data-interchange standards. UBL 2.1 is also ratified as ISO/IEC 19845, giving it standing as both an OASIS and an ISO standard.