xmlvalid
Sign in Open validator
XSD+SCH OpenPeppol · 3.0.21

Peppol BIS Billing 3.0 Invoice

A Peppol invoice checked the way an access point does: UBL 2.1 schema, EN 16931 rules and the Peppol BIS Billing 3.0 rules.

Validate with this schema Try it with the example

About

Peppol BIS Billing 3.0 is the invoice exchanged over the Peppol network in Europe. Access points reject a document that breaks a rule flagged fatal.

Three layers are checked in order: the UBL 2.1 Invoice schema, the EN 16931 rules and the Peppol rules: profile, endpoint and party identifiers (PEPPOL-EN16931-R001 and on) and the national rules of Denmark, Germany, Greece, Iceland, Italy, the Netherlands, Norway and Sweden.

E-invoicing in Belgium: the rules in short and how to check an invoice →

Good to know

  • Rules run only when the document matches the schema. Documents over 50 MB are checked against the schema only.
  • The rules and the example are published by OpenPeppol; the EN 16931 rules are reproduced by OpenPeppol with permission from CEN.

Files

14 files · 2.7 MB
  • maindoc/UBL-Invoice-2.1.xsd main
    58.8 KB View Download
  • common/UBL-CommonAggregateComponents-2.1.xsd
    2.3 MB View Download
  • common/UBL-CommonBasicComponents-2.1.xsd
    214.7 KB View Download
  • common/UBL-CommonExtensionComponents-2.1.xsd
    9.3 KB View Download
  • common/UBL-QualifiedDataTypes-2.1.xsd
    3.5 KB View Download
  • common/UBL-UnqualifiedDataTypes-2.1.xsd
    26.7 KB View Download
  • common/UBL-ExtensionContentDataType-2.1.xsd
    4.2 KB View Download
  • common/CCTS_CCT_SchemaModule-2.1.xsd
    44.2 KB View Download
  • common/UBL-CommonSignatureComponents-2.1.xsd
    5.4 KB View Download
  • common/UBL-SignatureAggregateComponents-2.1.xsd
    7.6 KB View Download
  • common/UBL-SignatureBasicComponents-2.1.xsd
    4.1 KB View Download
  • common/UBL-xmldsig-core-schema-2.1.xsd
    10.5 KB View Download
  • common/UBL-XAdESv132-2.1.xsd
    21.2 KB View Download
  • common/UBL-XAdESv141-2.1.xsd
    1.3 KB View Download

The validator loads all of these with their folder structure, so includes and imports resolve as published.

Business rules

Schematron · run in this order

The rules run after the schema check, only when the document matches the schema, and in your browser like the schema check (with SaxonJS by Saxonica). Each finding names its rule, such as BR-CO-15, and the line it points at; each rule has a page with what it checks.

Example document

base-example.xml · 9 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, peppol-bis-3-invoice, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema peppol-bis-3-invoice
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: peppol-bis-3-invoice
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document={{ $schema->example ?? 'document.xml' }} -F schema=peppol-bis-3-invoice

Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups