Sign in Open validatorValidator
XSD+SCH AUSTRIAPRO (schema); checks after e-Rechnung.gv.at (Federal Ministry of Finance) · 6.1, e-Rechnung.gv.at error list of October 2026

Austria e-Rechnung.gv.at (ebInterface 6.1)

e-Rechnung.gv.at invoice to the Austrian federal government (ebInterface 6.1)

An ebInterface 6.1 invoice to the Austrian federal government, checked against the schema and the checks e-Rechnung.gv.at makes before it accepts it.

Validate with this schema Try it with the example

About

Suppliers of the Austrian federal government (the Bund) send their invoices through e-Rechnung.gv.at, which rejects one that fails the schema or one of its checks and names the error by a code such as AF-0010 or EBI61-0012.

After the schema, the portal's checks run here with its codes: the order reference (an order number of ten digits starting with 47, a buyer group like Z01, or a buyer group and a reference) and the order position on each line, the supplier number, the biller's e-mail address, a delivery date or period, line, tax and invoice totals, discounts (Skonto), the payment method, the IBAN and up to 999 lines.

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.
  • The checks are written by xmlvalid after the portal's published requirements, its error list and its own version of the ebInterface schema. Lookups in the federal accounting system (whether the supplier number and buyer group exist) and checks against the day of upload (an invoice date too old, a due date in the past) are not run, so a document gives the same result on any day.
  • Amounts may be a cent off, and a period may end on the day it starts.
  • The example is ours, with fictitious parties.

Files

1 file · 27.5 KB · Download all (.zip)

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-ebinterface-6.1.xml · 4.6 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, at-erechnung-ebinterface-6.1, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema at-erechnung-ebinterface-6.1
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: at-erechnung-ebinterface-6.1
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document=@erechnung-bund-ebinterface-6.1.xml \
  -F schema=at-erechnung-ebinterface-6.1

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