XSD+SCH OpenPeppol; checks after e-Rechnung.gv.at (Federal Ministry of Finance) · Peppol BIS Billing 3.0.21, e-Rechnung.gv.at error list of October 2026

Austria e-Rechnung.gv.at Peppol Credit Note

Peppol credit note to the Austrian federal government (e-Rechnung.gv.at)

A Peppol BIS Billing 3.0 credit note to the Austrian federal government, checked against UBL 2.1, the EN 16931 and Peppol rules and what e-Rechnung.gv.at requires on top.

About

A credit note to the federal government needs the same order reference, supplier number and e-mail address as an invoice; it needs no payment means.

E-invoicing in Austria: 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 e-Rechnung.gv.at checks are written by xmlvalid after the portal's published requirements and its error list.
  • The example is ours, with fictitious parties.

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

erechnung-bund-peppol-credit-note.xml · 4.7 KB · passes the schema and the rules

In CI and from code

The same schema by its name, at-erechnung-peppol-credit-note, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema at-erechnung-peppol-credit-note
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: at-erechnung-peppol-credit-note
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document=@erechnung-bund-peppol-credit-note.xml \
  -F schema=at-erechnung-peppol-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