OASIS Universal Business Language (UBL) TC

Hi UBL Technical Committee,

As some of you might know, we at Google have been adopting the UBL 2.4 standard for some time and have recently published our UBL 2.4 implementation on the Google Developer site. You can view it here: https://developers.google.com/invoice-vendor-interface

For our implementation, we are focusing on a specific use case: exchanging information with our vendors so they can deliver it to various countries' tax administration e-invoicing portals and return processed responses back to us (workflow overview). While our implementation is tailored to meet this specific use case, I believe it might still be beneficial to share it with the community.

Here are a few points about the implementation:

• We utilize three UBL schemas: Invoice, CreditNote and ApplicationResponse. ApplicationResponse is crucial for receiving responses from vendors after e-invoice processing.
• We aimed to stay as close to the UBL 2.4 spec as possible, with only a few minor edge cases (e.g., added wrappers for invoice batch uploads).
• Code Lists: wherever possible, we used industry standards such as BIS 3.0 but also added a few specific ones necessary for our scenarios.

Additionally, since the website is hosted on Google's developer platform, it includes automatic machine translations into multiple languages.

In the future, we plan to continue advancing our implementation while staying aligned with UBL updates, and we welcome any feedback or recommendations you might have. Please feel free to send them to me directly at mnarinsky@google.com

Best,
Misha Narinsky

Google Invoicing and Regulatory Billing Product Lead