[1] It is designed to streamline information exchange through standardization, facilitating seamless connections between small, medium-sized, and large organization, thereby eliminating the re-keying of data and providing a comprehensive framework for electronic commerce.
UBL now defines a syntax-neutral information model that can be restricted or extended to meet the requirements of particular industries, sectors, and communities, thus providing interoperability between systems and vendors when used as a generic interchange format.
Ordering, Fulfilment, Billing Catalogue, Quotation, Payment, Statement, Transport Services, Certificate of Origin eTendering, Vendor Managed Inventory, Intermodal Freight Management, Utility Billing, and Collaborative Planning, Forecasting, Replenishment and e-Invoice / e-Archive and e-Ledger in Turkey Weight Statement, Business Directory, eTendering Order, Order Response, Order Response Simple, Order Change, Order Cancellation, Despatch Advice [Advance Ship Notice], Receipt Advice, Invoice 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 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 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 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.
[4] In December 2003 Denmark legislated[12] the mandatory use of a customization of UBL 0.7, using the OIOXML specification, for electronic invoicing for government procurement starting February 2005.
[16] Since its publication, NESUBL subset has influenced government eProcurement initiatives across Europe, for example in Denmark, Sweden, Norway, Iceland, The Netherlands, Turkey.
[19][20] 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.
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.
DIAN, the Colombian national tax and customs directorate, implements [28] UBL 2 as the XML document format for electronic invoicing.
The Norwegian Agency for Public and Financial Management (DFØ) has chosen[29] to use Peppol BIS Billing 3.0 and UBL for implementation of national format for invoicing.
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 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[34] by the Prime Ministers of New Zealand and Australia.
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.
[35] 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.