When businesses send invoices, the information must be clear and accurate. This becomes even more important when companies use different accounting systems or work with customers in other countries.
The UBL format helps solve this problem. It gives businesses a standard way to create and exchange electronic documents.
But what is UBL format, and why is it important for e-invoicing? Here is a simple guide to how it works, its benefits, and where it is used.
What is UBL Format?
UBL stands for Universal Business Language. It is an international standard developed by OASIS for exchanging business documents electronically.
UBL uses XML to organize information in a structured format that computers can read.
For example, an ordinary invoice may show the customer’s name, invoice date, products, taxes, and total amount. A UBL invoice contains the same information, but each detail is placed in a specific XML element.
This means accounting systems can read invoice data without someone entering everything manually.
UBL is not only used for invoices. It also supports purchase orders, credit notes, and other business documents.
How Does a UBL e-Invoice Work?
A UBL e-invoice works by turning invoice information into structured XML data.
Imagine a company in Belgium selling products to a customer in the Netherlands.
The seller creates an invoice using accounting software. The software generates a UBL XML file containing the buyer’s details, products, prices, and taxes.
The file is then sent through a supported e-invoicing network or platform.
The buyer’s accounting system receives the file and reads the information automatically.
The result is a faster process with less manual work. Both companies can use different software, provided their systems support the same required standards.
Benefits of Using the UBL Format
Businesses choose UBL for several reasons.
- Less manual data entry: Invoice information can move directly between accounting systems.
- Fewer mistakes: Structured fields reduce the need to copy information by hand.
- Faster processing: Businesses can receive and process invoices more quickly.
- Better compatibility: Different software systems can exchange documents using common standards.
- Improved tax compliance: UBL supports structured data checks, although meeting local tax rules still requires the correct invoice profile.
- Easier international trade: Companies can share invoice information across borders more efficiently.
For businesses handling hundreds of invoices every month, these benefits can make a real difference.
UBL Versions: From UBL 2.0 to UBL 2.5
UBL has changed over time as business needs have developed.
UBL 2.0 was released in 2006. It provided a common structure for many business documents.
UBL 2.1 followed in 2013 and became widely used for electronic invoicing.
Later versions, including UBL 2.2, 2.3, and 2.4, added more document types and improvements.
UBL 2.5 became an OASIS Standard in August 2026, continuing the development of the format.
However, a newer version is not automatically the version businesses should use.
For example, Peppol BIS Billing 3.0 still uses UBL 2.1 for its standard invoice syntax. Businesses must follow the version required by their country or receiving network.
Key Elements of a UBL Invoice
A UBL format invoice contains several important sections. Each section helps accounting software understand the document.
- Header: Includes the invoice number, issue date, invoice type code, and currency.
- Supplier and Customer Parties: Contains the seller’s and buyer’s business details, addresses, and relevant identification numbers.
- Payment Means and Terms: Explains how the customer should pay, including payment method, bank details where applicable, and payment conditions.
- Tax Total and Tax Breakdown: Shows tax amounts, categories, and rates where required.
- Legal Monetary Total: Contains invoice totals, such as the amount before tax, tax-inclusive amount, and amount payable.
- Invoice Lines: Lists the goods or services, quantities, unit prices, and line amounts.
These elements help systems process invoices consistently.
UBL Invoice Example
Here is a small example of how invoice information appears in UBL XML.
<cbc:ID>INV-2026-001</cbc:ID>
<cbc:IssueDate>2026-10-22</cbc:IssueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
This example shows an invoice number, issue date, invoice type, and currency.
A complete UBL invoice also includes the required XML namespaces, supplier and customer details, totals, invoice lines, and other mandatory elements.
How to Create a UBL Invoice? (Step-by-Step)
Creating a UBL invoice usually involves accounting software or an e-invoicing provider.
Step 1: Identify the UBL Profile or CIUS Required by Your Country
First, check the rules that apply to your business.
Some countries require a specific UBL profile or a Core Invoice Usage Specification (CIUS), which adds rules to a general invoicing standard.
Step 2: Map Your ERP Invoice Data to UBL Elements
Connect the information in your ERP or accounting system to the correct UBL fields.
For example, the invoice date must appear in the correct date element.
Step 3: Generate the UBL XML File
Use software to create the invoice as an XML document.
The system should follow the required UBL version and document structure.
Step 4: Validate the File Against Schema and Business Rules
Before sending the invoice, check that the XML structure is correct and all required information is included.
A valid XML file is not necessarily a compliant invoice. Business rules must also be checked.
Step 5: Transmit via Peppol or the Tax Authority Platform
Send the invoice through the required network, service provider, or government platform.
The correct method depends on the country and transaction.
Step 6: Archive the Invoice in Line With Retention Rules
Store the electronic invoice and related records for the period required by local law.
UBL vs UN/CEFACT CII: Key Differences
UBL and UN/CEFACT Cross Industry Invoice (CII) are two structured e-invoicing formats.
Both can support electronic invoicing, but they use different XML structures.
| Feature | UBL | UN/CEFACT CII |
| Full name | Universal Business Language | Cross Industry Invoice |
| Standards organization | OASIS | UN/CEFACT |
| Data format | XML | XML |
| Main purpose | Business document exchange | Invoice data exchange |
| EN 16931 support | Yes | Yes |
| Common use | Peppol and national systems | Selected European invoicing systems |
Neither format is automatically better. The right choice depends on the requirements of the receiving system.
UBL and EN 16931
EN 16931 is the European standard for electronic invoicing.
It defines the information an electronic invoice should contain, such as seller details, buyer details, taxes, and payment amounts.
UBL is one of the XML syntaxes used to represent that information.
In simple terms, EN 16931 explains what invoice information is needed, while UBL provides a structured way to write it.
This relationship is important for businesses working with e-invoicing in Europe.
UBL and Peppol BIS Billing 3.0
Peppol is a network and framework that allows businesses and public organizations to exchange electronic documents.
Peppol BIS Billing 3.0 defines rules for electronic invoices and credit notes based on EN 16931.
UBL 2.1 is the main invoice syntax used by this specification. Supported implementations may also accept CII.
A company cannot simply send any UBL XML file through Peppol. The document must meet the relevant Peppol business rules and validation requirements.
Which Countries Use UBL for e-Invoicing?
UBL is used in many parts of the world, but local requirements are not always the same.
Europe (Belgium, Netherlands, Denmark, Norway, Croatia)
These countries use UBL-based formats in different electronic invoicing systems, including Peppol-supported exchanges.
However, requirements vary by country, transaction type, and sector.
Germany: XRechnung UBL Syntax
Germany’s XRechnung standard supports UBL and CII syntaxes.
Businesses sending invoices to public authorities must follow the applicable XRechnung rules.
Türkiye: UBL-TR
Türkiye uses UBL-TR, a local adaptation of UBL developed for its electronic invoicing system.
UBL-TR includes requirements specific to Turkish tax regulations and e-Fatura processes.
Saudi Arabia: ZATCA
Saudi Arabia uses a UBL 2.1-based XML structure under its ZATCA e-invoicing framework.
Invoices must also meet Saudi-specific technical, security, and tax requirements.
Malaysia, Singapore, Australia and New Zealand
These countries use UBL-based standards in their electronic invoicing systems.
Malaysia uses UBL-based structures through MyInvois, while Singapore, Australia, and New Zealand support Peppol-based invoice exchange.
Businesses should always check local requirements before creating invoices.
FAQs About UBL Format
Is UBL the same as XML?
No. XML is a general language for organizing data. UBL is a business document standard that uses XML.
Is UBL mandatory for e-invoicing in the EU?
Not everywhere. UBL is a supported syntax under EN 16931, but some systems also accept CII. National rules determine what businesses must use.
Can a PDF invoice be converted to UBL?
Yes. Software can extract information from a PDF and generate a UBL XML file. However, the converted document must still be checked for missing data and compliance.
How do I open or view a UBL file?
A UBL file can be opened in a text editor because it contains XML. For a more readable invoice, use a UBL viewer or compatible accounting software.
What is the difference between UBL and UBL-TR?
UBL is an international business document standard. UBL-TR is Türkiye’s local version, with additional rules and fields required for Turkish electronic invoicing.