Universal Business Language

From Wikipedia, the free encyclopedia

Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. UBL was developed by an OASIS Technical Committee with participation from a variety of industry data standards organizations. UBL is designed to plug directly into existing business, legal, auditing, and records management practices.[1] It is designed to eliminate the re-keying of data in existing fax- and paper-based business correspondence and provide an entry point into electronic commerce for small and medium-sized businesses.[2]

UBL is owned by OASIS and is currently available to all, with no royalty fees. The UBL library of business documents is a well-developed markup language with validators, authoring software, parsers and generators.[3] As of June 2021, the latest approved OASIS Standard is UBL Version 2.3,[4] which includes a total of 91 business document types. All UBL minor versions are fully backwards compatible back to UBL Version 2.0.

UBL traces its origins back to the EDI standards and other derived XML standards.[5][6]

Ontologies are used to describe markup languages for business workflows. UBL is only one option to map e-business processes into an OWL description.[7]



UBL 2.4 - https://docs.oasis-open.org/ubl/UBL-2.4.html (Published 17 October 2023)

UBL 2.3 - https://docs.oasis-open.org/ubl/UBL-2.3.html (Published 15 June 2021)

UBL 2.2 - https://docs.oasis-open.org/ubl/UBL-2.2.html (Published 9 July 2018)

UBL 2.1 - https://docs.oasis-open.org/ubl/UBL-2.1.html

UBL 2.1 as ISO/IEC 19845:2015 - http://standards.iso.org/ittf/PubliclyAvailableStandards/


UBL 2.0 - http://docs.oasis-open.org/ubl/os-UBL-2.0-update/

UBL 1.0 - http://docs.oasis-open.org/ubl/cd-UBL-1.0/

UBL 2.1 (ISO/IEC 19845:2015) and UBL 2.2[edit]

OASIS UBL Technical Committee and ISO/IEC 19845 Maintenance Agency[edit]

The OASIS Universal Business Language (UBL) Technical Committee[8] is responsible for the creation and maintenance of the OASIS Standard and has been designated the maintenance agency for ISO/IEC 19845. The maintenance governance procedures[9] describe how committee and non-committee members contribute to the development of the specification.

Business processes described and supported in UBL[edit]

Business process support originating with UBL 1.0 (2004)[edit]

Ordering, Fulfilment, Billing

Business process support added in UBL 2.0 (2006)[edit]

Catalogue, Quotation, Payment, Statement, Transport Services, Certificate of Origin

Business process support added in UBL 2.1 (2013)[edit]

eTendering, Vendor Managed Inventory, Intermodal Freight Management, Utility Billing, and Collaborative Planning, Forecasting, Replenishment and e-Invoice / e-Archive and e-Ledger in Turkey

Business process support added in UBL 2.2 (2018)[edit]

Weight Statement, Business Directory, eTendering

Standard document types defined by UBL[edit]

Document types originally defined in UBL 1.0 (2004)[edit]

Order, Order Response, Order Response Simple, Order Change, Order Cancellation, Despatch Advice [Advance Ship Notice], Receipt Advice, Invoice

Document types added in UBL 2.0 (2006)[edit]

Added document types for sourcing: Catalogue, Catalogue Deletion, Catalogue Item Specification Update, Catalogue Pricing Update, Catalogue Request, Quotation, Request for Quotation

Added document types for fulfillment: Bill of Lading, Certificate of Origin, Forwarding Instructions, Packing List, Transportation Status, Waybill

Added document types for billing: Credit Note, Debit Note, Freight Invoice, Reminder, Self Billed Credit Note, Self Billed Invoice

Added document types for payment: Remittance Advice, Statement

Added supplementary document types: Application Response, Attached Document

Document types added in UBL 2.1 (2013)[edit]

Added document types for eTendering: Awarded Notification, Call for Tenders, Contract Award Notice, Contract Notice, Guarantee Certificate, Tender, Tender Receipt, Tenderer Qualification, Tenderer Qualification Response, Unawarded Notification

Added document types for Collaborative planning, forecasting, and replenishment: Exception Criteria, Exception Notification, Forecast, Forecast Revision, Item Information Request, Prior Information Notice, Trade Item Location Profile

Added document types for Vendor Managed Inventory: Instruction for Returns, Inventory Report, Product Activity, Retail Event, Stock Availability Report

Added document types for Intermodal Freight Management: Goods Item Itinerary, Transport Execution Plan, Transport Execution Plan Request, Transport Progress Status, Transport Progress Status Request, Transport Service Description, Transport Service Description Request, Transportation Status, Transportation Status Request

Added document type for Utility billing: Utility Statement

Added supplementary document types: Document Status, Document Status Request

Document types added in UBL 2.2 (2018)[edit]

http://docs.oasis-open.org/ubl/UBL-2.2.html Added document types for eTendering: Enquiry, Enquiry Response, Expression Of Interest Request, Expression Of Interest Response, Qualification Application Request, Qualification Application Response, Tender Contract, Tender Status, Tender Status Request, Tender Withdrawal, Unsubscribe From Procedure Request, Unsubscribe From Procedure Response

Added document types for transportation: Weight Statement

Added document types for business directories and agreements: Business Card, Digital Agreement, Digital Capability

Document types added in UBL 2.3 (2021)[edit]

Added document types for transportation: Common Transportation Report, Export Customs Declaration, Goods Certificate, Goods Item Passport, Import Customs Declaration, Manifest, Proof Of Reexportation, Proof Of Reexportation Reminder, Proof Of Reexportation Request, Transit Customs Declaration.

UBL 2.1 as ISO/IEC 19845:2015[edit]

The OASIS UBL 2.1 specification has been approved as ISO/IEC 19845 as of 2015-12-15:

UBL 2.2[edit]

The OASIS UBL 2.2 specification has been approved as an OASIS Standard as of 2018-07-09.[10]

UBL 2.3[edit]

OASIS UBL Version 2.3 has been approved as an OASIS Standard as of 15 June 2021.[4]

Subsets and customizations of UBL[edit]

Danish subsets: OIOXML and OIOUBL[edit]

In December 2003 Denmark legislated[11] the mandatory use of a customization of UBL 0.7, using the OIOXML specification, for electronic invoicing for government procurement starting February 2005. In March 2010 Denmark legislated[12] the mandatory use of a customization of UBL 2.0, using the OIOUBL specification.

In 2011 the Danish government documented[13] savings of €500,000,000 having used UBL.

Northern European Subset - NESUBL[edit]

As part of the Northern European cooperation on e-commerce and e-procurement, representatives from Denmark, Sweden, Norway, Finland, UK and Iceland set up a working group for developing a Northern European subset of UBL 2.0 documents. The main focus of NES is to define the semantic use of UBL 2.0 as applied to specific business processes. To achieve this the UBL 2.0 standard is restricted on additional levels by using "profiles" that apply to defined business situations.[14] The use of individual elements is specifically described to avoid conflicting interpretation. Additionally each country has developed guidelines that describe the application of the NESUBL subset to domestic business practices. The goal is to enable companies and institutions to implement e-commerce by agreeing to a specific profile and thus eliminate the need for bilateral implementation. Additional countries have shown interest in joining the work. The NESUBL subset was published in March 2007.[15]

Since its publication, NESUBL subset has influenced government eProcurement initiatives across Europe, for example in Denmark, Sweden, Norway, Iceland, The Netherlands, Turkey. It is also the basis for an eProcurement initiative, ePrior, by the European Commission, Directorate General's of the European Commission, starting with the Directorate General for Information Technology (DIGIT).[16][17] It is also the basis of the syntax for business documents created by the CEN/BII (Business Interoperability Initiative).[18][19]

European-wide deployment of UBL in PEPPOL[edit]

PEPPOL adopts the work products of CEN/TC434 and CEN/TC440 that include UBL customizations and syntax serializations of different document types for European business processes. The goal of PEPPOL is to enable public procurement across borders within the EU.[20]

It was reported[21] that CEN/TC434 has unanimously agreed to endorse UBL as one of two syntaxes complying with the forthcoming European Norm on e-Invoicing and will be listed in a specific CEN Technical Specification.

These efforts support Directive 2014/55/EU on electronic invoicing in public procurement in Europe.

On March 3, 2017, this summary update of recent announcements was published, including references to Austria, Belgium, Denmark, Italy (Emilia-Romagna region), Netherlands, Norway, Sweden.

Spanish UBL version based in CCI[edit]

In Spain, UBL is being used primarily for electronic invoice encoding. The UBL Spanish Localization Committee has been actively developing UBL awareness and has created implementation guidelines to allow easy adoption of UBL based on previous work done by CCI.

UBL Turkish Customization - UBL-TR[edit]

The UBL Turkish Localization Subcommittee customized the UBL 2.0 to be used in eInvoice process in Turkey. See also the IBM Knowledge Center.

Czech UBL Customization - ISDOC[edit]

The SPIS consortium (currently named ICT unie) created an UBL 2.0 customization ISDOC to be used for e-Invoicing in the Czech Republic. The recently released ISDOC 6 supports e-Requests too.[22]

Peruvian UBL Customization - SUNAT[edit]

SUNAT, the national customs and tax administration for Peru, supports[23] a customization of UBL 2.0. Plans have been announced[24] by SUNAT to migrate to UBL 2.1

Belgian UBL Customization - e-fff[edit]

In December 2011 the Belgian government specified[25] a customization of UBL to maximize the interoperability of the electronic invoice between Belgian actors.

Swedish UBL Customization - Svefaktura[edit]

SFTI, the joint project of the Swedish Association of Local Authorities and Regions (SKL), Financial Management Authority (ESV) and the government contracting authority specified Svefaktura, a UBL customization.

As of November 1, 2018 it will be mandatory[26] for Swedish electrical authorities to use PEPPOL.

Colombian UBL Customization - DIAN[edit]

DIAN, the Colombian national tax and customs directorate, implements [27] UBL 2 as the XML document format for electronic invoicing.

Norwegian UBL Customization - EHF[edit]

Difi, the Norwegian agency for Public Management and eGovernment, has chosen[28] to use CEN BII as a base for the EHF formats and the Universal Business Language (UBL) as a foundation for the implemented syntax.

Dutch UBL Customization - UBL-OHNL and Simplerinvoicing[edit]

UBL-OHNL is a Dutch government-specific customization for submitting documents via Digipoort.

Simplerinvoicing is a community of e-invoicing, ERP and accounting software providers making e-invoicing in UBL available for everyone. It includes access to the PEPPOL network for secure and reliable transfer.

In response to the European Directive 2014/55/EU the Dutch government has mandated[29] XML Invoicing for all contracts signed after January 1, 2017, using the UBL-OHNL customization via Digipoort or the Simplerinvoicing customization via PEPPOL.

Australia and New Zealand use of UBL[edit]

As part of a national initiative to increase the proportion of businesses participating in the Australian digital economy the Digital Business Council endorsed [30] an Interoperability Framework in 2016. The initial version of the framework includes a set of policies, standards and guidelines to promote the economy-wide adoption of eInvoicing. A subset of UBL 2.1 for the invoice and business response document was included in this initial release. The subset was initially based on a working draft of the European Committee for Standardization's work under the CEN/TC 434 - Electronic Invoicing project

In 2017 OASIS established a localisation subcommittee to promote the harmonised use of UBL and to support the broader market adoption across Australia. The subcommittee facilitates an open dialogue for information sharing and collaboration, under the auspices of OASIS transparent governance and operating procedures.

Further guidance and support is facilitated by third parties such as

  • DCAF Online - a contemporary and transparent approach to businesses having visibility of the digital standards and frameworks their service providers support. Recognised service providers are listed and resources are available to support the economy-wide adoption of digital procurement.

In February 2019 "the two countries’ intention to jointly adopt the Pan-European Public Procurement Online (PEPPOL) interoperability framework for trans-Tasman e-invoicing" was announced[31] by the Prime Ministers of New Zealand and Australia.

Italian use of UBL[edit]

The future of e-invoicing in Italy will facilitate the correct implementation of the national Technical Rules for Interoperability between e-Procurement platforms (Circolare 3 AgID) and the automation of the end-to-end procurement process, based on PEPPOL or, where a PEPPOL specification is not available, by implementing a CEN BII profile using the OASIS UBL 2.1 syntax.[32] In the long term, likely by 2022, the objective is to migrate to a single global standard, UBL, still supporting the other mandatory syntax with translations, and phasing out the national format.

Singaporean use of UBL[edit]

Singapore has established the first PEPPOL Authority outside of Europe[33] with the Info-communications Media Development Authority (IMDA) to help businesses in Singapore to benefit from digitalisation and better position themselves to plug into the international marketplace.

United States and Canadian use of UBL[edit]

On October 4, 2018, the Business Payments Coalition e-Invoicing Subcommittee,[34] an open technical committee consisting of US, Canadian, and Mexican interests in electronic invoicing and facilitated by the US Federal Reserve Bank of Minneapolis, released[35] its first review of the semantic model of an invoice, expressed using the business objects of OASIS UBL 2.2.

National adoptions[edit]

  • on February 17, 2017, Canada formally adopted UBL 2.1 as Canadian national standard CAN/CSA-ISO/IEC 19845:16[36] (paid content identical to free content from OASIS download web site cited above)

Corporate support of UBL[edit]

  • MSC Belgium documented[37] their adoption of UBL 2.1 for sales invoices as of March 15, 2016
  • EDF France documented[38] their adoption of UBL 2.0 for orders as of March 23, 2010
  • IBM documents[39] their support of PEPPOL UBL for e-Invoicing

Industry support of UBL[edit]

Textile Clothing and Footwear industry - eBiz-TCF[edit]

  • eBIZ is a UBL customization available for the Textile Clothing and Footwear industry.

The e-Freight Framework[edit]

  • a joint effort to create "One Common Framework for Information and Communication Systems in Transport and Logistics" from FREIGHTWISE, e‐Freight, INTEGRITY, Smart‐CM, SMARTFREIGHT, EURIDICE, RISING, DiSCwise, iCargo, COMCIS, eMAR and other projects, developing a reference model and logistics information exchange "document" that are now part of UBL 2.1 - ISO/IEC 19845[40]

Danish Industry[edit]

  • ClearView Trade offers a portal for customers to obtain export documents using UBL[41]

Products supporting UBL[edit]

  • Akretion has created open source UBL modules for open source Odoo[42] (formerly OpenERP) and has produced a demonstration video in OGG Video format
  • Crane Softwrights Ltd. offers a subset schema preparation service
  • go2UBL offers a service of converting PDF documents into UBL documents
  • the backbone document format for the Tradeshift platform is UBL[43]
  • UBLReady is an online validation service for UBL documents and for certifying the readiness of organizations[44] according to the UBL Ready configuration[45]
  • xa-elegans is a web application that accepts and runs rules over UBL documents as part of the Internet of Rules
  • Centiga is a cloud-based accounting software that utilises UBL to offer free invoicing services. The software is integrated with the majority for Norwegian banks, which means that one can control the economy as a whole in one place.
  • bBiller is a real world Ethereum Blockchain DAO for Double Entry Book-keeping and accounting using the International standard OASIS UBL Universal Business Language.
  • Semine is a Norwegian AI platform provider that provides automated double entry accounting for business documents received in the UBL format. The platform can be integrated with any ERP solutions using their open API.
  • Charlie-India is a tech startup providing a white-label e-invoicing platform; users of the services built on the platform can exchange invoice data in the OASIS UBL format.
  • Conta Conta is a web-based invoicing platform that utilizes UBL to deliver cost-free invoicing services within the Australian market.

Tools for working with UBL documents and models[edit]

UBL Vocabulary Development[edit]

The OASIS UBL Naming and Design Rules Version 3.0 documents how the UBL Technical Committee applies the OASIS Business Document Naming and Design Rules Version 1.0 specification for defining a business document creating XSD schemas on the basis of business objects described using the UN/CEFACT Core Component Technical Specification 2.01.

The committee has published a reference[46] for one to create one's own UBL subset schema by starting from the same resources used by the committee to publish the UBL distribution.

The committee announced[47] the first public review of the OASIS Business Document Naming and Design Rules Version 1.1[48] proposed OASIS Standard with new rules for creating JSON validation artefacts for JSON documents, complete with the OASIS Committee Note[49] of all UBL 2.1 document types as JSON schemas and all UBL 2.1 example documents as JSON documents, beginning February 1, 2017 and closing April 1, 2017.


  1. ^ UBL 2.0 implementation library Retrieved on 2009-12-21.
  2. ^ "UBL official homepage". Retrieved 2007-03-31.
  3. ^ Article by Tim Bray: "Don’t Invent XML Languages" Retrieved on 2007-05-29.
  4. ^ a b "Universal Business Language Version 2.3"
  5. ^ "On UBL (an overview)". Retrieved 2008-02-09.
  6. ^ "History of UBL | UBL XML.org". ubl.xml.org. Retrieved 2017-01-11.
  7. ^ Magdalenic, Ivan and Vrdoljak, Boris and Schatten, Markus (2010). Mapping of core components based e-business standards into ontology. Research Conference on Metadata and Semantic Research. Springer. pp. 95–106. doi:10.1007/978-3-642-16552-8_10.{{cite conference}}: CS1 maint: multiple names: authors list (link)
  8. ^ "OASIS Universal Business Language (UBL) Technical Committee".
  9. ^ "UBL Maintenance Governance Procedures Version 1.0". docs.oasis-open.org. Retrieved 2017-11-08.
  10. ^ "Universal Business Language Version 2.2".
  11. ^ "Danish statute for OIOXML eInvoice". www.oio.dk. Retrieved 2016-09-29.
  12. ^ "Executive Order on Information in, and Transport of, OIOUBL Electronic Invoices for Electronic Settlement with Public Authorities" (PDF).
  13. ^ "E-Invoicing in Denmark".
  14. ^ "On NESUBL (an overview)". 5 August 2020.
  15. ^ "NES official homepage". Archived from the original on 2007-03-20. Retrieved 2007-03-31.
  16. ^ "IDABC e-Invoicing and e-Ordering project for public procurement, by Pieter Breyne". Retrieved 2010-04-03.
  17. ^ Breyne, Pieter; Philip Van Langenhove; Joao Frade; Maarten Daniëls (31 March 2009). "Analysis of Business Requirements for e-Invoicing in a Public Procurement Context : Final Study". European Commission. Retrieved 5 January 2012.
  18. ^ "The CEN / BII workshop results". Retrieved 2010-04-03.
  19. ^ "The CEN / BII official homepage". Retrieved 2010-04-03.
  20. ^ "PEPPOL, Pan European Public Procurement Online". Retrieved 2010-04-03.
  21. ^ "2017-01-26: Agreement on syntaxes complying with the forthcoming European standard (EN) on Electronic Invoicing - CEF Digital - CEF Digital". ec.europa.eu. Retrieved 2016-11-07.
  22. ^ ISDOC 6: Nový formát elektronické fakturace má zlepšit transparentnost veřejných zakázek
  23. ^ "E-invoicing in Peru". Retrieved 2016-09-29.
  24. ^ "Google Translate". translate.google.com. Retrieved 2016-09-29.
  25. ^ "e-fff". www.e-fff.be. Retrieved 2016-09-29.
  26. ^ "Ekonomistyrningsverkets cirkulärserie över föreskrifter och allmänna råd" (PDF). Retrieved 2017-03-17.
  27. ^ "Dirección de Impuestos y Aduanas Nacionales de Colombia". www.dian.gov.co. Retrieved 2016-10-27.
  28. ^ eGovernment, Agency of Public Management and. "EHF Invoice and Creditnote". vefa.difi.no. Retrieved 2016-12-01.
  29. ^ "Mandatory XML e-invoicing towards Dutch central agencies as from 1 January 2017 - E-invoicing Platform". eeiplatform.com. Retrieved 2016-12-01.
  30. ^ "Australia now has a national standard for e-invoicing". iTnews. Retrieved 2016-09-28.
  31. ^ "Joint Statement by Prime Ministers the Rt Hon Jacinda Ardern and the Hon Scott Morrison MP Auckland, 22 February 2019". The Beehive. Retrieved 2019-02-22.
  32. ^ "Study on the practical application and implementation of the European e-Invoicing standard".
  33. ^ Works, Strøm (2018-05-22). "Singapore first PEPPOL Authority outside Europe - Peppol". Peppol. Retrieved 2018-09-25.
  34. ^ "Electronic Invoicing -". FedPayments Improvement. Retrieved 2018-10-17.
  35. ^ "BPC semantic models - Google Drive". bpceinvcttee.page.link. Retrieved 2018-10-17.
  36. ^ "CAN/CSA-ISO/IEC 19845:16". ShopCSA. Retrieved 2017-02-18.
  37. ^ "MSC Belgium presents e-invoicing | MSC". www.msc.com. Retrieved 2016-09-29.
  38. ^ "Guide technique Traduction des factures EDF en XML Version 1.2" (PDF).
  39. ^ "IBM Electronic Invoicing - Canada". www-05.ibm.com. 2017-02-01. Retrieved 2017-03-17.
  40. ^ "The e-Freight Framework - e-Impact". www.eimpactproject.eu. Retrieved 2017-11-07.
  41. ^ "CLEARVIEW TRADE - ClearView Trade". clearviewtrade.com (in Danish). Retrieved 2017-11-10.
  42. ^ "Akretion | Akretion adds support for UBL-based electronic orders in Odoo". www.akretion.com. Retrieved 2017-11-15.
  43. ^ "The hidden OASIS: a Universal Business Language - Tradeshift Blog". 2013-05-21. Retrieved 2016-10-02.
  44. ^ "UBL Ready participants, taking the next step in e-invoicing: UBL e-invoicing | UBL Ready | E-invoicing". ublready.com. Retrieved 2017-03-10.
  45. ^ "Get Started Guide to become UBL Ready in five easy steps | UBL Ready | E-invoicing". ublready.com. Retrieved 2017-03-10.
  46. ^ a b "UBL spreadsheet editing instructions". Retrieved 2016-09-28.
  47. ^ "#UBL 2.1 JSON Alternate Representation v1.0 and Business Document Naming and Design Rules start public review - ends April 1st | OASIS". www.oasis-open.org. 31 January 2017. Retrieved 2017-02-01.
  48. ^ "Business Document Naming and Design Rules Version 1.1". docs.oasis-open.org. Retrieved 2017-02-01.
  49. ^ "UBL 2.1 JSON Alternative Representation Version 1.0". docs.oasis-open.org. Retrieved 2017-02-20.