Universal Business Language
{{short description|Business document open library}}
Universal Business Language (UBL), ISO/IEC 19845, is an open library of standard electronic business documents and information models for supply chain, procurement, and transportation such as purchase orders, invoices, transport logistics and waybills. Originally 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.[http://www.simpleubl.com/products/universal-business-language-implementation-library/ UBL 2.0 implementation library] Retrieved on 2009-12-21. 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.{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl | title=UBL official homepage | access-date=2007-03-31}}
UBL is owned by OASIS and is available to all, with no royalty fees. The UBL semantic library is a well-developed information and data model with validators, authoring software, parsers and generators.Article by Tim Bray: [http://www.tbray.org/ongoing/When/200x/2006/01/08/No-New-XML-Languages "Don’t Invent XML Languages"] Retrieved on 2007-05-29. As of June 2021, the latest approved OASIS Standard is UBL Version 2.3,[http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html "Universal Business Language Version 2.3"] which includes a total of 91 business document types. All UBL minor versions are fully backwards compatible back to UBL Version 2.0.
Originally tracing it origins back to the EDI standards and other derived XML standards,{{cite web | url=http://www.unimaze.com/support/resources/on-ubl | title=On UBL (an overview) | access-date=2008-02-09}}{{Cite web|url=http://ubl.xml.org/wiki/history-of-ubl|title=History of UBL {{!}} UBL XML.org|website=ubl.xml.org|access-date=2017-01-11}} UBL has evolved to include a broader range of syntaxes such as JSON, thereby enhancing global harmonization and interoperability. 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.{{Cite web |title=OASIS Technical Committee {{!}} Charter |url=https://www.oasis-open.org/committees/ubl/charter.php |access-date=2024-04-24 |website=www.oasis-open.org}}
Ontologies are used to describe markup languages for business workflows. UBL is only one option to map e-business processes into an OWL description.{{cite conference |title=Mapping of core components based e-business standards into ontology |author=Magdalenic, Ivan and Vrdoljak, Boris and Schatten, Markus |conference=Research Conference on Metadata and Semantic Research |pages=95–106 |year=2010 |publisher=Springer |doi=10.1007/978-3-642-16552-8_10}}
Downloads
= Current =
UBL 2.4 - https://docs.oasis-open.org/ubl/UBL-2.4.html (Published 20 June 2024)
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/
= Historical =
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
= OASIS UBL Technical Committee and ISO/IEC 19845 Maintenance Agency =
The OASIS Universal Business Language (UBL) Technical Committee{{Cite web|url=https://www.oasis-open.org/committees/ubl|title=OASIS Universal Business Language (UBL) Technical Committee}} 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{{Cite web|url=http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/UBL-Governance-v1.0.html|title=UBL Maintenance Governance Procedures Version 1.0|website=docs.oasis-open.org|access-date=2017-11-08}} describe how committee and non-committee members contribute to the development of the specification.
= Business processes described and supported in UBL =
== Business process support originating with UBL 1.0 (2004) ==
Ordering, Fulfilment, Billing
== Business process support added in UBL 2.0 (2006) ==
Catalogue, Quotation, Payment, Statement, Transport Services, Certificate of Origin
== Business process support added in UBL 2.1 (2013) ==
{{Not a typo|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) ==
{{Update|date=October 2020}}
Weight Statement, Business Directory, {{Not a typo|eTendering}}
= Standard document types defined by UBL =
== Document types originally defined in UBL 1.0 (2004) ==
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) ==
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) ==
Added document types for {{Not a typo|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) ==
{{Update|date=October 2020}}
http://docs.oasis-open.org/ubl/UBL-2.2.html
Added document types for {{Not a typo|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) ==
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.
== Document types added in UBL 2.4 (2024) ==
Added document types: Business Information, Purchase Receipt
= UBL 2.1 as ISO/IEC 19845:2015 =
The OASIS UBL 2.1 specification has been approved as ISO/IEC 19845 as of 2015-12-15:
- http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66370
= UBL 2.2 =
The OASIS UBL 2.2 specification has been approved as an OASIS Standard as of 2018-07-09.{{Cite web|url=http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html|title=Universal Business Language Version 2.2}}
= UBL 2.3 =
Subsets and customizations of UBL
= Danish subsets: OIOXML and OIOUBL =
In December 2003 Denmark legislated{{Cite web|url=http://www.oio.dk/XML/standardisering/eHandel/materialer/OIOXMLeInvoice|title=Danish statute for OIOXML eInvoice|website=www.oio.dk|access-date=2016-09-29}} 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{{Cite web|url=http://oioubl.info/documents/en/OIOUBLStatute.pdf|title=Executive Order on Information in, and Transport of, OIOUBL Electronic Invoices for Electronic Settlement with Public Authorities}} the mandatory use of a customization of UBL 2.0, using the [http://oioubl.info/classes/en/index.html OIOUBL] specification.
In 2011 the Danish government documented{{Cite web|url=https://www.oasis-open.org/committees/download.php/36397|title=E-Invoicing in Denmark}} savings of €500,000,000 having used UBL.
= Northern European Subset - NESUBL =
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.{{cite web | url=http://www.unimaze.com/support/resources/on-nesubl | title=On NESUBL (an overview)| date=5 August 2020}} 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.{{cite web | url=http://www.nesubl.eu | title=NES official homepage | access-date=2007-03-31 |archive-url = https://web.archive.org/web/20070320000433/http://www.nesubl.eu/ |archive-date = 2007-03-20}}
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, {{Not a typo|ePrior}}, by the European Commission, Directorate General's of the European Commission, starting with the Directorate General for Information Technology (DIGIT).{{cite web | url=http://www.epractice.eu/cases/ePRIOR | title=IDABC e-Invoicing and e-Ordering project for public procurement, by Pieter Breyne | access-date=2010-04-03}}{{cite web|url=http://www.epractice.eu/en/library/288906|title=Analysis of Business Requirements for e-Invoicing in a Public Procurement Context : Final Study|last=Breyne|first=Pieter|author2=Philip Van Langenhove |author3=Joao Frade |author4=Maarten Daniëls |date=31 March 2009|publisher=European Commission|access-date=5 January 2012}} It is also the basis of the syntax for business documents created by the CEN/BII (Business Interoperability Initiative).{{cite web|url=http://spec.cenbii.eu/|title=The CEN / BII workshop results|access-date=2010-04-03}}{{cite web|url=http://www.cen.eu/cen/Sectors/Sectors/ISSS/Activity/Pages/Ws_BII.aspx|title=The CEN / BII official homepage|access-date=2010-04-03}}
= European-wide deployment of UBL in PEPPOL =
PEPPOL adopts the work products of [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C CEN/TC434] and [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1976650&cs=175E298F320429229DD35C9E22F4E8F76 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.{{cite web | url=http://peppol.eu/ | title=PEPPOL, Pan European Public Procurement Online | access-date=2010-04-03}}
It was reported{{Cite web|url=https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Agreement+on+syntaxes+complying+with+the+forthcoming+European+standard+%28EN%29+on+Electronic+Invoicing|title=2017-01-26: Agreement on syntaxes complying with the forthcoming European standard (EN) on Electronic Invoicing - CEF Digital - CEF Digital|website=ec.europa.eu|access-date=2016-11-07}} 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 [http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32014L0055&rid=1 Directive 2014/55/EU] on electronic invoicing in public procurement in Europe.
On March 3, 2017, this [http://eeiplatform.com/18297/peppol-implementations-european-union-continues-rise/ 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 =
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 - [http://www.efatura.gov.tr/anasayfa.html UBL-TR] =
The [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl-trlsc UBL Turkish Localization Subcommittee] customized the UBL 2.0 to be used in {{Not a typo|eInvoice}} process in Turkey. [https://www.ibm.com/support/knowledgecenter/en/temp_sterlingb2bcloud/einvoicing/SCN_eINV_Turkey_Definitions.htm See also the IBM Knowledge Center.]
= Czech UBL Customization - ISDOC =
The SPIS consortium (currently named [http://www.ictu.cz/ ICT unie]) created an UBL 2.0 customization [http://www.isdoc.cz/ ISDOC] to be used for e-Invoicing in the Czech Republic. The recently released ISDOC 6 supports e-Requests too.[http://www.systemonline.cz/zpravy/isdoc-6-novy-format-elektronicke-fakturace-zlepsi-transparentnost-verejnych-zakazek-z.htm ISDOC 6: Nový formát elektronické fakturace má zlepšit transparentnost veřejných zakázek]
= Peruvian UBL Customization - SUNAT =
[http://www.sunat.gob.pe/ SUNAT], the national customs and tax administration for Peru, supports{{Cite web|url=http://www.edicomgroup.com/en_US/news/4081|title=E-invoicing in Peru|access-date=2016-09-29}} a customization of UBL 2.0. Plans have been announced{{Cite web|url=https://translate.google.com/translate?hl=en&sl=es&u=http://www.sunat.gob.pe/legislacion/superin/2016/anexo-067-2016.pdf&prev=search|title=Google Translate|website=translate.google.com|access-date=2016-09-29}} by SUNAT to migrate to UBL 2.1
= Belgian UBL Customization - e-fff =
In December 2011 the Belgian government specified{{Cite web|url=http://www.e-fff.be/NL/doc03.php|title=e-fff|website=www.e-fff.be|access-date=2016-09-29}} a customization of UBL to maximize the interoperability of the electronic invoice between Belgian actors.
= Swedish UBL Customization - Svefaktura =
[http://www.sfti.se/standarder/bestallningsprocesssftisvehandel/svefaktura.1882.html SFTI], the joint project of the Swedish Association of Local Authorities and Regions (SKL), Financial Management Authority (ESV) and the government contracting authority specified [http://www.sfti.se/standarder/bestallningsprocesssftisvehandel/svefaktura.1882.html Svefaktura], a UBL customization.
As of November 1, 2018 it will be mandatory{{Cite web|url=http://www.esv.se/contentassets/5cb651dd8cbf4425bc50f0d4c37c8db8/esv-cirkular-2015-3.pdf|title=Ekonomistyrningsverkets cirkulärserie över föreskrifter och allmänna råd|access-date=2017-03-17}} for Swedish electrical authorities to use PEPPOL.
= Colombian UBL Customization - DIAN =
[http://www.dian.gov.co/ DIAN], the Colombian national tax and customs directorate, implements {{Cite web|url=http://www.dian.gov.co/contenidos/otros/fac_electronica.html|title=Dirección de Impuestos y Aduanas Nacionales de Colombia|website=www.dian.gov.co|access-date=2016-10-27}} UBL 2 as the XML document format for electronic invoicing.
= Norwegian UBL Customization - EHF =
[http://www.dfo.no/ The Norwegian Agency for Public and Financial Management (DFØ)] has chosen{{Cite web|url=https://anskaffelser.dev/postaward/g3/spec/current/billing-3.0/norway/|title=EHF Billing 3.0|website=anskaffelser.dev|access-date=2024-04-17}} to use Peppol BIS Billing 3.0 and UBL for implementation of national format for invoicing. Additional specifications{{Cite web|url=https://anskaffelser.dev/postaward/g3/spec/|title=Anskaffelser.dev, EHF Post-Award G3 specifications|website=anskaffelser.dev|access-date=2024-04-17}} using UBL as syntax based upon Peppol BIS are also used in the Norwegian market.
DFØ follows the direction once set out by Norwegian Agency for Public Management and eGovernment (Difi){{Cite web|url=https://anskaffelser.dev/postaward/g2/spec/current/invoice-and-creditnote/2.0/en/#_background_and_objective|title=EHF Invoice and Credit Note 2.0, Background and Objective|website=anskaffelse.dev|access-date=2024-04-17}} in using UBL and results from CEN BII (restarted as CEN TC434) as basis for national implementation of post-award document exchange.
= Dutch UBL Customization - UBL-OHNL and Simplerinvoicing =
UBL-OHNL is a Dutch government-specific customization for submitting documents via Digipoort.
[http://www.simplerinvoicing.org/en/ 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 [http://www.peppol.eu PEPPOL] network for secure and reliable transfer.
In response to the European [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055 Directive 2014/55/EU] the Dutch government has mandated{{Cite web|url=http://eeiplatform.com/17338/mandatory-xml-e-invoicing-towards-dutch-central-agencies-as-from-1-january-2017/|title=Mandatory XML e-invoicing towards Dutch central agencies as from 1 January 2017 - E-invoicing Platform|website=eeiplatform.com|access-date=2016-12-01}} 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 =
As part of a national initiative to increase the proportion of businesses participating in the Australian digital economy the [http://digitalbusinesscouncil.com.au/ Digital Business Council] endorsed {{Cite web|url=http://www.itnews.com.au/news/australia-now-has-a-national-standard-for-e-invoicing-431943|title=Australia now has a national standard for e-invoicing|website=iTnews|access-date=2016-09-28}} 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 {{Not a typo|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 [https://standards.cen.eu/index.html European Committee for Standardization's] work under the [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C CEN/TC 434 - Electronic Invoicing project]
In 2017 OASIS established a [https://www.oasis-open.org/committees/sc_home.php?wg_abbrev=ubl-australia 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
- [https://dcafonline.com/ DCAF Online] - a contemporary and transparent approach to businesses having visibility of the digital standards and frameworks their service providers support. [https://dcafonline.com/procurement-providers.html Recognised service providers] are listed and [https://dcafonline.com/procurement-resources.html 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{{Cite web|url=http://www.beehive.govt.nz/release/joint-statement-prime-ministers-rt-hon-jacinda-ardern-and-hon-scott-morrison-mp-auckland-22|title=Joint Statement by Prime Ministers the Rt Hon Jacinda Ardern and the Hon Scott Morrison MP Auckland, 22 February 2019|website=The Beehive|language=en|access-date=2019-02-22}} by the Prime Ministers of New Zealand and Australia.
= Italian use of UBL =
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.{{Cite web|url=https://ec.europa.eu/docsroom/documents/25521/attachments/1/translations/en/renditions/native|title=Study on the practical application and implementation of the European e-Invoicing standard}} 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 =
Singapore has established the first PEPPOL Authority outside of Europe{{Cite news|url=https://peppol.eu/singapore-first-peppol-authority-outside-europe/|title=Singapore first PEPPOL Authority outside Europe - Peppol|last=Works|first=Strøm|date=2018-05-22|work=Peppol|access-date=2018-09-25|language=en-US}} 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 =
On October 4, 2018, the Business Payments Coalition e-Invoicing Subcommittee,{{Cite news|url=https://fedpaymentsimprovement.org/payments-efficiency/b2b-payments/electronic-invoicing/|title=Electronic Invoicing -|work=FedPayments Improvement|access-date=2018-10-17|language=en-US}} 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{{Cite web|url=https://bpceinvcttee.page.link/shareddrive|title=BPC semantic models - Google Drive|website=bpceinvcttee.page.link|language=en|access-date=2018-10-17}} its first review of the semantic model of an invoice, expressed using the business objects of OASIS UBL 2.2.
National adoptions
- on February 17, 2017, Canada formally adopted UBL 2.1 as Canadian national standard CAN/CSA-ISO/IEC 19845:16{{Cite web|url=https://store.csagroup.org/ccrz__ProductDetails?cartID=&sku=2704106&viewState=DetailView |title=CAN/CSA-ISO/IEC 19845:16|website=ShopCSA|language=en|access-date=2017-02-18}} (paid content identical to free content from [https://www.lionobytes.com/demo OASIS] download web site cited above)
Corporate support of UBL
- MSC Belgium documented{{Cite web|url=https://www.msc.com/bel/notices/2016-february/msc-belgium-presents-e-invoicing|title=MSC Belgium presents e-invoicing {{!}} MSC|website=www.msc.com|access-date=2016-09-29}} their adoption of UBL 2.1 for sales invoices as of March 15, 2016
- EDF France documented{{Cite web|url=https://entreprises.edf.com/fichiers/fckeditor/Commun/Entreprises/pdf/Guide%20technique%20facture%20EDF%20en%20XML%20V1.2.pdf|title=Guide technique Traduction des factures EDF en XML Version 1.2}} their adoption of UBL 2.0 for orders as of March 23, 2010
- IBM documents{{Cite web|url=http://www-05.ibm.com/support/operations/ca/en/e-invoicing.html|title=IBM Electronic Invoicing - Canada|date=2017-02-01|website=www-05.ibm.com|language=en-CA|access-date=2017-03-17}} their support of PEPPOL UBL for e-Invoicing
Industry support of UBL
= Textile Clothing and Footwear industry - eBiz-TCF =
- [http://www.moda-ml.org/moda-ml/imple/pgcl.asp?p=256&lingua=en eBIZ] is a UBL customization available for the Textile Clothing and Footwear industry.
= The e-Freight Framework =
- 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, {{Not a typo|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{{Cite web|url=https://www.eimpactproject.eu/the-e-freight-framework|title=The e-Freight Framework - e-Impact|website=www.eimpactproject.eu|language=en-US|access-date=2017-11-07}}
= Danish Industry =
- ClearView Trade offers a portal for customers to obtain export documents using UBL{{Cite web|url=http://clearviewtrade.com/#referencer|title=CLEARVIEW TRADE - ClearView Trade|website=clearviewtrade.com|language=da-DK|access-date=2017-11-10}}
Products supporting UBL
- Akretion has created open source UBL modules for open source Odoo{{Cite web|url=http://www.akretion.com/blog/akretion-adds-support-for-ubl-based-electronic-orders-in-odoo|title=Akretion {{!}} Akretion adds support for UBL-based electronic orders in Odoo|website=www.akretion.com|language=en|access-date=2017-11-15}} (formerly OpenERP) and has produced a [http://public.akretion.com/odoo_electronic_orders_ubl.ogv demonstration video in OGG Video format]
- Crane Softwrights Ltd. offers a [http://www.CraneSoftwrights.com/links/services-wiki.htm subset schema preparation service]
- [http://www.go2ubl.nl go2UBL] offers a service of converting PDF documents into UBL documents
- the backbone document format for the [http://www.Tradeshift.com Tradeshift] platform is UBL{{Cite web|url=https://blog.tradeshift.com/the-hidden-oasis-a-universal-business-language/|title=The hidden OASIS: a Universal Business Language - Tradeshift Blog|date=2013-05-21|language=en-US|access-date=2016-10-02}}
- [http://www.ublready.nl UBLReady] is an online validation service for UBL documents and for certifying the readiness of organizations{{Cite web|url=http://ublready.com/ubl-ready-participants/|title=UBL Ready participants, taking the next step in e-invoicing: UBL e-invoicing {{!}} UBL Ready {{!}} E-invoicing|website=ublready.com|language=en-GB|access-date=2017-03-10}} according to the UBL Ready configuration{{Cite web|url=http://ublready.com/get-started-guide/|title=Get Started Guide to become UBL Ready in five easy steps {{!}} UBL Ready {{!}} E-invoicing|website=ublready.com|language=en-GB|access-date=2017-03-10}}
- [https://github.com/Xalgorithms/xa-elegans xa-elegans] is a web application that accepts and runs rules over UBL documents as part of the [https://InternetOfRules.org/ Internet of Rules]
- [http://www.centiga.no 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.
- [http://bBiller.com bBiller] is a real world Ethereum Blockchain DAO for Double Entry Book-keeping and accounting using the International standard OASIS UBL Universal Business Language.
- [http://www.semine.com 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.
- [http://www.charlie-india.com 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.
- [http://www.conta.com 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
- Crane Softwrights Ltd.'s [http://www.cranesoftwrights.com/resources/ubl/#ods2obdgc ods2obdgc] and [http://www.cranesoftwrights.com/resources/ubl/#gc2obdndr gc2obdndr] tools are used by the UBL committee to create UBL document schemas from a spreadsheet expression of business objects described using the UN/CEFACT Core Component Technical Specification 2.01
- [http://www.srdc.com.tr/eDoCreator iSURF eDoCreator 1.0] allows creation and customization of UBL document schemas.
- [https://github.com/phax/ph-ubl ph-ubl] Open Source Java library for reading and writing UBL 2.0, 2.1, 2.2 and UBL-TR documents. Licensed under the Apache 2.0 License
- [http://ubllarsen.codeplex.com/ UBL Larsen] C# .NET 4.0 library for reading and writing UBL 2.0 documents.
- [https://www.kyktir.info Kyktir] universal file viewer with an UBL viewer included.
UBL Vocabulary Development
The [http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/UBL-NDR-v3.0.html OASIS UBL Naming and Design Rules Version 3.0] documents how the UBL Technical Committee applies the [http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/Business-Document-NDR-v1.0.html 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{{Cite web|url=https://docs.google.com/document/d/1RSvewwdS-lp4sl-gYHI5gjNxrgXXqCc5wuA6UI5hhWA/view|title=UBL spreadsheet editing instructions|access-date=2016-09-28}} 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{{Cite web|url=https://www.oasis-open.org/news/announcements/ubl-2-1-json-alternate-representation-v1-0-and-business-document-naming-and-desig|title=#UBL 2.1 JSON Alternate Representation v1.0 and Business Document Naming and Design Rules start public review - ends April 1st {{!}} OASIS|website=www.oasis-open.org|date=31 January 2017|language=en|access-date=2017-02-01}} the first public review of the OASIS Business Document Naming and Design Rules Version 1.1{{Cite web|url=http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html|title=Business Document Naming and Design Rules Version 1.1|website=docs.oasis-open.org|access-date=2017-02-01}} proposed OASIS Standard with new rules for creating JSON validation artefacts for JSON documents, complete with the OASIS Committee Note{{Cite web|url=http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/UBL-2.1-JSON-v1.0.html|title=UBL 2.1 JSON Alternative Representation Version 1.0|website=docs.oasis-open.org|access-date=2017-02-20}} 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.