xmlvalid
Sign in Open validator
XSD+SCH OpenPeppol · 3.1

Peppol Invoice Response

The buyer tells the seller what happened to a Peppol invoice: received, accepted, rejected, paid.

Validate with this schema Try it with the example

About

Invoice Response reports the processing status of an invoice, with clarification codes for a rejection. Two layers are checked: the UBL 2.1 Application Response schema and the Peppol rules.

Good to know

  • Rules run only when the document matches the schema.
  • The rules and the example are published by OpenPeppol in the BIS upgrade-3 package.

Files

14 files · 2.7 MB
  • maindoc/UBL-ApplicationResponse-2.1.xsd main
    21.2 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

InvoiceResponse_Example.xml · 2.5 KB · passes the schema and the rules

View Open in validator

In CI and from code

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

npx @xmlvalid/cli validate "**/*.xml" --schema peppol-invoice-response
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: peppol-invoice-response
    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-invoice-response

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