Skip to content

Validate a UBL invoice

Check a UBL invoice against the rules that apply to it, such as EN 16931 or Peppol BIS, with each finding explained. Free within the daily limit.

No file to hand? Try a sample invoice

In short

Check an invoice against its applicable EN 16931 and national rule set. Read each finding and guidance on what to correct. Free, 10 a day without an account.

What the check covers

Klarbon checks the XML against the official schema and the business rules of the rule set for its format and version, listed below, and checks a PDF for PDF/A-3 conformance and the invoice metadata Factur-X and ZUGFeRD require. It does not verify digital signatures, and a pass does not show that the tax treatment is right or that the recipient or a platform will accept the file.

Rule sets and versions

Klarbon chooses the rule set from what the file declares. The French CIUS runs only when you ask for it on a French seller's invoice.

Specification Version Covers
EN 16931 1.3.17 UBL
XRechnung 3.0.2 UBL
Peppol BIS Billing 3.0 2026.5 UBL
NLCIUS (SI-UBL) 2.0.3.13 UBL
French EN 16931 CIUS 1.4.0-04 UBL
RO_CIUS and RO e-Factura 1.0.9 UBL

Klarbon's UBL validator checks a UBL 2.1 invoice or credit note against the EN 16931 business rules for UBL. When the file declares Peppol BIS Billing 3.0, XRechnung or the Dutch NLCIUS, it runs that rule set as well and shows both results side by side. Returned findings include rule codes and guidance where available. Free for ten checks a day, fifty with a free account.

What does the validator check?

A UBL invoice is an XML file in the OASIS Universal Business Language (OASIS UBL 2.1). Its cbc:CustomizationID says which rules it follows, and Klarbon picks the rule sets from it:

The file declares Rule sets applied
EN 16931 only EN 16931 1.3.17 for UBL (CEN/TC 434 artefacts)
Peppol BIS Billing 3.0 Peppol BIS Billing 3.0 rules (OpenPeppol), and EN 16931 for UBL
XRechnung 3.0 XRechnung 3.0.2 rules for invoices, and EN 16931 for UBL; UBL credit notes are not supported yet
NLCIUS SI-UBL 2.0 rules for invoices, and EN 16931 for UBL; UBL credit notes are not supported yet
UBL.BE not checked; the UBL.BE rule set is not available in Klarbon

The report names each rule set and its version. Checking UBL is live: the official EN 16931 examples pass, and an official example with a wrong total is caught as BR-CO-16. Checking a Peppol BIS file is still in beta. More in what is UBL.

Why do validators disagree?

Because they run different rules, or different releases of them. NLCIUS requires the seller's Chamber of Commerce number with its scheme (BR-NL-1) and XRechnung a buyer reference (BR-DE-15), neither of which EN 16931 requires. A file can therefore pass one validator and fail another. Klarbon shows each rule set's result in one table and says in one sentence why two of them differ.

How do I validate a UBL file?

  1. Upload the XML file. On a phone, pick it from Files, Mail or your downloads.
  2. Read the report. Returned findings show the rule code and severity, with a business term, source location and correction guidance where available.
  3. Correct and check again in your invoicing software, or check any e-invoice if you are not sure the file is UBL.

Which errors are common?

Missing required fields such as the buyer reference or an electronic address, totals or a VAT breakdown that do not add up, and code values that are not on the allowed lists, such as a unit or VAT category. A UBL file that opens in a viewer can still break these rules, so open and check are separate steps.

Does Klarbon print, send or keep the file?

It prints: turn the UBL invoice into a PDF for a readable copy, though the XML stays the invoice, and convert the e-invoice to another format if the recipient wants CII or XRechnung. It does not send: Klarbon is not a Peppol access point. And it does not keep: the check runs on Klarbon's servers in memory and the file is deleted after the request (what happens to my files). Checks are free, ten a day without an account and fifty with one (prices). The Belgian e-invoicing guide covers the UBL.BE and Peppol side.

Frequently asked questions

How do I validate a UBL invoice?

Upload the XML file to Klarbon's UBL validator. It checks the invoice against the EN 16931 business rules for UBL, or against the Peppol BIS Billing, XRechnung or NLCIUS rules when the file declares one of those, and reports returned findings with guidance where available.

Which UBL version does the validator support?

UBL 2.1, the syntax EN 16931 binds to. Plain EN 16931 and Peppol BIS Invoice and CreditNote documents are checked. XRechnung and NLCIUS UBL credit notes are not supported checking targets yet. A file in a later UBL version is not automatically an accepted invoice profile.

Is a UBL file that opens also valid?

Not necessarily. Opening shows what the file contains, even when rules are broken. Only a check tells you whether the business rules are met.

Does the validator check Belgian UBL.BE rules?

No. Klarbon does not run the UBL.BE rule set. A Belgian invoice sent over Peppol follows Peppol BIS Billing 3.0, which the validator does check.

Does a valid result mean the invoice will be accepted?

No. A pass means the selected technical rules were met. It does not confirm the tax treatment, the amounts or a recipient's own extra requirements.

Sources

Updated 16 November 2026