Peppol Validator

A Peppol validator checks whether a UBL XML invoice complies with Peppol BIS Billing 3.0 and EN16931 business rules. It runs schematron-based checks for schema issues, missing fields, invalid identifiers, and rule violations.

An electronic invoice (e-invoice) is a structured digital document exchanged directly between seller and buyer systems, not a PDF or scanned image. In Europe, e-invoices follow the EN16931 standard and are typically encoded as UBL 2.1 XML. They can be validated, processed, and booked automatically without manual data e

Upload your UBL XML invoice above and run validation against EN16931 and Peppol BIS schematron rules. Errors and warnings are shown inline with rule references. For CII / Factur-X invoices, use our Factur-X validator.

UBL (Universal Business Language) 2.1 is the OASIS XML standard that defines the data format for invoices and credit notes. Peppol BIS Billing 3.0 is a profile built on top of UBL 2.1 that restricts and extends it with specific business rules for the Peppol network. EN16931 sits in between as the European semantic stan

Common causes include missing mandatory fields (like seller/buyer identifiers or tax breakdowns), incorrect InvoiceTypeCode (BT-3), scheme ID mismatches on electronic addresses (PEPPOL-EN16931-R004), empty XML elements (PEPPOL-EN16931-R008), and calculation mismatches on line or document totals (BR-CO rules).

Yes. Upload a UBL CreditNote XML file and it will be validated against the same Peppol BIS 3.0 and EN16931 rules. Peppol supports two approaches: a dedicated CreditNote document (code 381, positive amounts) or a negative Invoice (code 380, negative amounts). Both are valid.