← All guides · Formats & conversion
What is a UBL 2.1 invoice and when do you need one?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
A UBL 2.1 invoice is an invoice written in Universal Business Language XML: every field — parties, lines, VAT breakdown, totals — sits in a named XML element that accounting systems import directly. It is the syntax EN 16931 uses here and the format Peppol BIS invoices are sent in. If your client asks for an e-invoice, a UBL file is very likely what they mean.
What is UBL 2.1?
UBL (Universal Business Language) 2.1 is an ISO-standard XML vocabulary for business documents. A UBL invoice document carries the EN 16931 core invoice data in elements such as cbc:ID for the invoice number and cac:InvoiceLine for each line. EInvoice Translator generates UBL 2.1 XML for every converted invoice and embeds the identical XML in its Factur-X PDF output.
Why XML, when a PDF looks identical?
A PDF shows an invoice to a person; a UBL file explains it to a machine. When your client receives UBL, their accounting software reads the seller, the VAT identifiers, each line's amount and VAT category, and the payable total directly from named elements — no scanning, no OCR, no retyping. That is why mandate countries require structured invoices: the receiving side can book, check and pay without manual handling.
The difference shows up in errors. A mistyped total on a PDF is a query three weeks later. In UBL, the totals sit in explicit elements and the receiving system compares them against the lines immediately; if they disagree, the file is rejected the same day, with the rule named. Structured data moves the argument to the moment of sending, when it is cheap to fix.
Anatomy of a UBL invoice
A UBL invoice opens with its identity: the invoice number (cbc:ID), issue date, type code (380 for an invoice, 381 for a credit note) and currency. Then come the two parties — supplier and customer — each with name, postal address and VAT identifier. Delivery and payment details follow, including the due date and payment means where supplied.
The heart of the document is the tax section and the lines. cac:TaxTotal holds the tax amount and the breakdown per category and rate — taxable amount and tax for each. cac:LegalMonetaryTotal states the line extension total, tax-exclusive amount, tax-inclusive amount and payable amount. Each cac:InvoiceLine carries its own id, quantity, line extension amount, item name and price, plus its VAT category and rate. Nothing is implied: if a figure matters, it has an element.
UBL and EN 16931: model and syntax
EN 16931 is the European invoice model — the business terms and rules. UBL 2.1 is a syntax that can express that model, and the EN 16931 UBL binding defines exactly how each business term maps to a UBL element. The same model also underpins Peppol BIS Billing 3.0, the profile used to send invoices over the Peppol network, which adds its own stricter rules on top of the EN 16931 core.
That layering is why converting once is enough. An invoice validated against the EN 16931 core rules and written as UBL 2.1 is the file your client imports, the file embedded in your Factur-X PDF, and the file you upload when you send through your own Peppol account. The product keeps those three identical — the PDF's embedded XML is byte-for-byte the XML you can download separately.
How a UBL file is validated
Validation happens on two levels. The data level checks the EN 16931 business rules: required fields present, codes from the allowed lists, VAT category and rate agreement, and the BR-CO totals arithmetic. The file level parses the generated XML back and re-runs the checks on what is actually in the document, so a generation fault cannot slip through as a file that says something different from what you entered.
Serious receiving systems do the same, and national platforms add their own layer — Italy's SdI and Poland's KSeF check their own formats and rules. Passing EN 16931 validation does not convert your UBL into FatturaPA or a KSeF invoice; those are separate national formats. What it does guarantee is that the invoice data itself is complete and consistent, which is the precondition for every channel.
Creating a UBL invoice from an ordinary one
You do not write XML by hand. You enter the invoice you already have — number, dates, seller, buyer, lines with VAT categories and rates — and the converter computes totals, validates the data, and generates the UBL file. Failures come back as named rules against named fields, and the exception workspace walks you through correcting them instead of starting again.
The free tier here converts one invoice completely: UBL 2.1 XML plus the Factur-X PDF, with the acceptance checker telling you whether your client's country requires the structured file for that invoice date. Pro adds bulk conversion of up to 200 invoices per job for firms converting a whole billing run, and exports to Xero, QuickBooks and CSV formats alongside the XML.
Sending a UBL invoice
Delivery is separate from creation. Many clients accept the XML or the Factur-X PDF by email or portal upload. For Peppol, this product's model is guided sending: you download the validated UBL file, then send it free from your own Qvalia Connect Free account, under your own Peppol ID — the step-by-step guide is built into the converter's Peppol section. The send and its confirmation live in your Qvalia account; nothing is transmitted from here.
Whichever channel you use, keep the XML file itself in your records, not just the PDF. The XML is the invoice your client's system booked; if a figure is ever queried, the structured file is the unambiguous reference — and in mandate countries it, not the printout, is the legally operative document.
Before you send a UBL invoice: 5 checks
- Open the XML and confirm the invoice number, issue date, type code and currency elements match your invoice.
- Confirm both parties carry their VAT identifiers where the sale is cross-border B2B.
- Check the tax breakdown: one subtotal per VAT category and rate, matching your lines.
- Verify the payable amount equals line total minus allowances plus charges plus tax minus prepaid.
- Download and keep both files — the UBL XML and the Factur-X PDF — with your invoice records.
Worked example: one line, mapped to UBL
A translator invoices a French publisher: invoice 2026-031, one line, 'Manuscript translation, 12,000 words', quantity 1 at EUR 1,080.00, VAT category AE at 0% because the supply is cross-border B2B reverse charge, and the publisher's French VAT identifier is recorded. In the UBL file, the line becomes a cac:InvoiceLine with a line extension amount of EUR 1,080.00, the tax total shows EUR 0.00 with a subtotal for category AE over a taxable EUR 1,080.00, and the payable amount is EUR 1,080.00.
Nothing about the numbers changed — structured invoicing does not reprice your work. What changed is that every figure now sits in the element the publisher's system expects, so the invoice is booked on receipt instead of being printed, read and retyped by an accounts assistant.
Frequently asked questions
Is UBL the same as Peppol?
No. UBL is the document format; Peppol is the network that delivers documents between access points. Peppol BIS invoices are written in UBL 2.1 with additional Peppol rules.
Can my client open a UBL file?
Their accounting system imports it. For a human reader, send the Factur-X PDF as well — it shows the same invoice and embeds the identical XML.
Does Excel or my invoicing app export UBL?
Some do, many do not — and an export is only useful if the data passes EN 16931 validation. Converting here validates first, then generates, then re-checks the file.
What is the difference between UBL and CII?
They are the two syntax families EN 16931 allows. This product generates UBL 2.1; Factur-X/ZUGFeRD in Germany uses the CII tradition inside a PDF — here the embedded XML is the UBL invoice, byte-identical to the download.
How do I get a UBL invoice for free?
Convert one invoice on the home page: enter the invoice, validate, and download the UBL 2.1 XML and Factur-X PDF at no cost.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- What is EN 16931 and why does your invoice need to follow it?
- What is a Factur-X invoice? The PDF with the invoice inside it
- Peppol BIS Billing 3.0 explained: the profile your Peppol invoice must fit
- XRechnung vs ZUGFeRD: Germany's two e-invoice formats compared
- How to convert a PDF invoice to XML (UBL) that validates