Do you validate against the UBL XSD?

We check well-formedness, root element, namespaces and data types of all EN 16931 fields, plus the business rules. Element order is not checked as strictly as a schema validator would.

Which encoding is supported?

UTF-8 is recommended. Files with a byte-order mark are handled automatically.

Can I download the report?

Yes, export the full report as JSON or print it as PDF.

UBL 2.1 invoice validator

Paste or upload any UBL 2.1 Invoice or CreditNote. We detect the profile (Peppol, XRechnung, EN 16931), check well-formedness with exact line and column, and apply all business rules.

Standard: OASIS UBL 2.1 (ISO/IEC 19845)
Documents: Invoice, CreditNote
Profiles detected: Peppol BIS 3.0, XRechnung, EN 16931
Max file size: 5 MB

Rules

Drop your e-invoice here

UBL 2.1 · Peppol BIS 3.0 · XRechnung · Factur-X / ZUGFeRD (XML or PDF)

Processed in memory and never stored. PDFs are unpacked in your browser.

What this validator checks for UBL 2.1

XML well-formedness with line and column
Root element and namespace detection
Data types for dates and amounts
EN 16931 business and calculation rules
Peppol rules when a Peppol CustomizationID is present

Common UBL mistakes

The most frequent problems we see are TaxInclusiveAmount not equal to TaxExclusiveAmount plus VAT (BR-CO-15), VAT computed per line instead of per rate group (BR-CO-17), missing schemeID attributes on EndpointID (BR-62/BR-63), and dates with time components.