Austria e-Rechnung.gv.at Peppol Invoice
Peppol invoice to the Austrian federal government (e-Rechnung.gv.at)
A Peppol BIS Billing 3.0 invoice 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
e-Rechnung.gv.at receives invoices to the federal government over Peppol under one participant ID for all of them (9915:b) and finds the office the invoice is for from its order reference. It reads the order reference from the purchase order reference (BT-13) and the supplier number the federal government assigns from the seller identifier (BT-29), and runs its own checks on the invoice besides the Peppol ones.
Those checks run here with the portal's codes: the order reference and its form, the order position of each line (BT-132) when the reference is an order number, the supplier number, the seller's e-mail address, a delivery date or period, the payment means, the IBAN and Austrian VAT numbers.
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; whether the supplier number and buyer group exist is not looked up.
- The example is ours, with fictitious parties.
Files
14 files · 2.7 MB · Download all (.zip)-
maindoc/UBL-Invoice-2.1.xsd main
-
common/UBL-CommonAggregateComponents-2.1.xsd
-
common/UBL-CommonBasicComponents-2.1.xsd
-
common/UBL-CommonExtensionComponents-2.1.xsd
-
common/UBL-QualifiedDataTypes-2.1.xsd
-
common/UBL-UnqualifiedDataTypes-2.1.xsd
-
common/UBL-ExtensionContentDataType-2.1.xsd
-
common/CCTS_CCT_SchemaModule-2.1.xsd
-
common/UBL-CommonSignatureComponents-2.1.xsd
-
common/UBL-SignatureAggregateComponents-2.1.xsd
-
common/UBL-SignatureBasicComponents-2.1.xsd
-
common/UBL-xmldsig-core-schema-2.1.xsd
-
common/UBL-XAdESv132-2.1.xsd
-
common/UBL-XAdESv141-2.1.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Business rules
Schematron · run in this orderThe 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-invoice.xml · 6.7 KB · passes the schema and the rules
In CI and from code
The same schema by its name, at-erechnung-peppol-invoice, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema at-erechnung-peppol-invoice
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: at-erechnung-peppol-invoice
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document=@erechnung-bund-peppol-invoice.xml \
-F schema=at-erechnung-peppol-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