# Peppol validator

Source: https://xmlvalid.com/peppol-validator

> Check a Peppol invoice before your access point sends it, or find out why it was rejected: drop the UBL file and the validator reads its specification identifier, picks the Peppol BIS or PINT profile it names, and checks it against the UBL 2.1 schema, the EN 16931 rules and OpenPeppol's rules, with the national rules of the seller's country. Everything runs in your browser

## What is checked

- **The UBL 2.1 schema**: elements in their order, required elements, data types and code list forms.
- **The EN 16931 rules** (1.3.16, the release Peppol BIS ships with): totals that add up ([BR-CO-15](https://xmlvalid.com/rules/BR-CO-15)), the VAT breakdown per category, required business terms.
- **OpenPeppol's rules** (Peppol BIS Billing 3.0.21): the 64 PEPPOL-EN16931 rules, such as the seller's and buyer's electronic addresses ([PEPPOL-EN16931-R020](https://xmlvalid.com/rules/PEPPOL-EN16931-R020), [R010](https://xmlvalid.com/rules/PEPPOL-EN16931-R010)) and the code lists Peppol allows.
- **National rules** for sellers in Germany, Denmark, Greece, Iceland, Italy, the Netherlands, Norway and Sweden, which Peppol BIS carries: organisation numbers, VAT number forms, payment means.

Each finding names its rule, its line and, for a business rule, the element it points at; a rule's page says what it checks and how to fix it.

## Which Peppol profile

The validator reads the specification identifier (BT-24, `cbc:CustomizationID`) and picks the profile: Peppol BIS Billing 3.0 invoices and credit notes, Self-Billing 3.0, the PINT specifications of the UAE, Singapore (InvoiceNow), Japan, Australia and New Zealand, and Malaysia, and the national profiles built on Peppol BIS: XRechnung, SI-UBL 2.0 (NLCIUS) and EHF Billing, which is Peppol BIS with the Norwegian rules. Orders, despatch advice, catalogues and the other Peppol post-award documents are in the catalog too: choose their schema in the validator.

## Rejected by the access point

An access point checks every document against the same rules before it sends it, and rejects one with a fatal finding. Fix the first errors first: the business rules run only once the schema check passes, and later findings often follow from earlier ones. A receiver that is not in Peppol, or does not take the document type, is a different problem: the [Peppol lookup](https://xmlvalid.com/tools/peppol-lookup) shows whether a company is registered and what it receives. To write an invoice that passes, the [e-invoice generator](https://xmlvalid.com/e-invoice-generator) makes a Peppol BIS invoice and checks it before download.

## Questions

### Is my invoice uploaded?

No. The UBL file is read and checked in your browser, with the same engine and rules as our API. Nothing is sent anywhere.

### Is this the official Peppol validator?

No: OpenPeppol publishes the Schematron rules and this page runs them. They are compared every week with Saxon-HE for Java on OpenPeppol's own test documents, so the findings are the ones an access point running the published rules gets.

### Why does my invoice pass here but the access point rejects it?

An access point may run an older or newer release of the rules, or checks of its own such as the receiver's registration. Compare the rule set versions the result names with the ones your provider uses.

### Can I check many invoices at once?

Yes: in the validator, drop a folder or a zip and each document is checked with the profile it names. The API and CLI do the same in a build.

### Does it check PINT invoices too?

Yes: PINT invoices of the UAE, Singapore, Japan, Australia and New Zealand, and Malaysia are checked against OpenPeppol's shared PINT rules and the jurisdiction's own.

  ### Other tools

- [XML formatter](https://xmlvalid.com/tools/xml-formatter): Pretty-print or minify XML, keeping text, CDATA and comments as written.
- [XML viewer](https://xmlvalid.com/tools/xml-viewer): Read a document as a tree you can fold, search and copy XPaths from.
- [XPath tester](https://xmlvalid.com/tools/xpath-tester): Evaluate XPath 3.1 against a document and see each match with its line.
- [XSD generator](https://xmlvalid.com/tools/xsd-generator): Infer an XML Schema from sample documents, checked against them.
- [XML from XSD](https://xmlvalid.com/tools/xsd-to-xml): Generate a sample XML document from a schema, validated against it.
- [XSLT transformer](https://xmlvalid.com/tools/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](https://xmlvalid.com/tools/xml-diff): Compare two XML documents as trees: changed, added and removed elements, attributes and text.
- [XML to JSON converter](https://xmlvalid.com/tools/xml-to-json): Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
- [JSON to XML converter](https://xmlvalid.com/tools/json-to-xml): Convert JSON to XML: @keys become attributes, arrays repeated elements.
- [XML to CSV converter](https://xmlvalid.com/tools/xml-to-csv): Turn a repeating element into CSV rows: invoice lines, products, records.
- [XML to PDF converter](https://xmlvalid.com/tools/xml-to-pdf): Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
- [E-invoice viewer](https://xmlvalid.com/tools/e-invoice-viewer): Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
- [ZUGFeRD validator](https://xmlvalid.com/zugferd-validator): Check a ZUGFeRD or Factur-X PDF: the XML inside against its profile's rules, and the PDF around it.
- [XRechnung validator](https://xmlvalid.com/xrechnung-validator): Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
- [UBL validator](https://xmlvalid.com/ubl-validator): Check a UBL invoice, order or any other UBL 2.1 document against its OASIS schema, and the business rules of the profile it names.
- [P7M viewer: open a .p7m file](https://xmlvalid.com/tools/p7m-viewer): Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
- [XRechnung examples to download](https://xmlvalid.com/tools/xrechnung-examples): Example XRechnung and ZUGFeRD invoices to download, one for each common case.
- [E-invoicing mandate in Germany: do I have to?](https://xmlvalid.com/tools/e-invoicing-mandate): Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
- [Factur-X examples](https://xmlvalid.com/tools/factur-x-examples): Example Factur-X invoices of every profile and of the French reform, as XML and as PDF.
- [Leitweg-ID check](https://xmlvalid.com/tools/leitweg-id): Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
- [Peppol lookup](https://xmlvalid.com/tools/peppol-lookup): Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
- [XML validator](https://xmlvalid.com/validate): check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.
