XSD+SCH OpenPeppol · 3.0.2

Peppol BIS Self-Billing 3.0 Credit Note

Peppol BIS Self-Billing 3.0 credit note (self-billed credit note)

A Peppol self-billed credit note, issued by the buyer in the seller's name, checked against the UBL 2.1 schema, the EN 16931 rules and the Peppol BIS Self-Billing 3.0 rules.

About

The self-billed credit note of Peppol BIS Self-Billing 3.0 (type code 261), sent by the buyer to the seller, with the same rule layers as the self-billed invoice. A self-billed invoice with negative amounts may correct one too.

Its specification identifier (CustomizationID) is urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:selfbilling:3.0.

E-invoicing in Norway: 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 the CEN 1.3.16 release OpenPeppol ships with it.

Files

14 files · 2.7 MB · Download all (.zip)
  • maindoc/UBL-CreditNote-2.1.xsd main
    56.3 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

SB-base-creditnote-correction.xml · 9.2 KB · passes the schema and the rules

In CI and from code

The same schema by its name, peppol-bis-sb-credit-note, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema peppol-bis-sb-credit-note
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: peppol-bis-sb-credit-note
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document=@SB-base-creditnote-correction.xml \
  -F schema=peppol-bis-sb-credit-note

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