What is checked
- The OASIS UBL 2.1 schema of the document: Invoice, CreditNote, DebitNote, Order, OrderResponse, OrderChange, OrderCancellation, DespatchAdvice, ReceiptAdvice, Catalogue, Quotation or ApplicationResponse. Elements in their order, required elements, data types and the UBL extension point, each error with its line and column; messages such as "This element is not expected" and "Missing child element(s)" have a page on what causes them.
- Business rules, when
cbc:CustomizationIDnames a profile in the catalog: EN 16931 and the specifications built on it (Peppol BIS Billing, XRechnung, SI-UBL, CIUS-RO, CIUS-PT, EHF, OIOUBL), the PINT specifications, and Peppol BIS 3.0 for orders, order responses, order changes and cancellations, despatch advice, catalogues and their responses, invoice responses and message level responses.
Each finding names its rule, its line and the element it points at; a rule's page says what it checks and how to fix it.
Which schema and which rules
All UBL 2.1 documents share one set of components, so the document element and its namespace (urn:oasis:names:specification:ubl:schema:xsd:Order-2) say which schema applies. The customization identifier says which rules: a Peppol order names urn:fdc:peppol.eu:poacc:trns:order:3, a Peppol invoice urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0. A document that names a profile the catalog does not have is checked against the plain schema. The schema catalog lists every UBL document type and profile; to check against one yourself, choose it in the validator.
When it fails
Fix the first schema error first: UBL elements come in a fixed order, so one element in the wrong place can make every one after it "not expected". The business rules run only once the schema check passes. To write a UBL invoice that passes, the e-invoice generator makes one in Peppol BIS or XRechnung and checks it before download; the e-invoice viewer lays a UBL invoice out as a PDF to read.
Questions
Is my document uploaded?
No. The XML is read and checked in your browser, with the same engine and rules as our API. Nothing is sent anywhere.
Which UBL versions are supported?
UBL 2.1, the version EN 16931 and Peppol use, for every document type above, and UBL 2.5 for invoices and credit notes. Later versions only add elements, so a document of UBL 2.2 to 2.4 that uses none of them passes the 2.1 schema; an invoice that does can be checked against UBL 2.5, chosen in the validator.
Can I check a UBL order?
Yes: drop it and it is checked against the UBL 2.1 Order schema, with the Peppol BIS Order rules when it names them. Order responses, changes, cancellations, despatch and receipt advice, catalogues and quotations work the same way.
Can I check many documents at once?
Yes: in the validator, drop a folder or a zip and each document is checked with the schema and rules it names. The API and CLI do the same in a build.
Can I use my own UBL schema or customization?
Yes: in the validator, add the XSD files yourself, or save them as a schema of your own with a Pro account and refer to it in the API.
Other tools
- XML formatter: Pretty-print or minify XML, keeping text, CDATA and comments as written.
- XML viewer: Read a document as a tree you can fold, search and copy XPaths from.
- XPath tester: Evaluate XPath 3.1 against a document and see each match with its line.
- XSD generator: Infer an XML Schema from sample documents, checked against them.
- XML from XSD: Generate a sample XML document from a schema, validated against it.
- XSLT transformer: Run XSLT 1.0, 2.0 or 3.0 on a document and see the result, the messages and the files it writes.
- XML diff: Compare two XML documents as trees: changed, added and removed elements, attributes and text.
- XML to JSON converter: Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
- JSON to XML converter: Convert JSON to XML: @keys become attributes, arrays repeated elements.
- XML to CSV converter: Turn a repeating element into CSV rows: invoice lines, products, records.
- XML to PDF converter: Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
- E-invoice viewer: Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
- ZUGFeRD validator: Check a ZUGFeRD or Factur-X PDF: the XML inside against its profile's rules, and the PDF around it.
- XRechnung validator: Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
- Peppol validator: Check a Peppol BIS Billing 3.0 or PINT invoice against the OpenPeppol rules before your access point sends it.
- P7M viewer: open a .p7m file: Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
- XRechnung examples to download: Example XRechnung and ZUGFeRD invoices to download, one for each common case.
- E-invoicing mandate in Germany: do I have to?: Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
- Factur-X examples: Example Factur-X invoices of every profile and of the French reform, as XML and as PDF.
- Leitweg-ID check: Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
- Peppol lookup: Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
- XML validator: check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.