Vai al contenuto
Torna al blog
AustriaPubblicato il 15 luglio 20267 min di lettura

Austria e-invoicing: what ebInterface 6.1 actually requires

ebInterface 6.1 is Austria’s national invoice format — proprietary XML, not UBL. Why you may not need it for B2G, the two output modes, and the three things that surprise implementers.

Austria is the country where the national e-invoice format is optional for the government and hard to avoid in business. That is the opposite of what most people assume, and it changes whether you need ebInterface at all.

What ebInterface is

ebInterface is Austria’s own invoice vocabulary. Its root element is <Invoice>, in the namespace http://www.ebinterface.at/schema/6p1/, and it has its own element names throughout — Biller, InvoiceRecipient, ListLineItem, TaxItem. It is not UBL and it is not CII.

Since version 5.0 it is aligned with EN 16931 — but in semantics, not in syntax. The concepts map; the XML does not. You cannot re-label a UBL invoice into ebInterface, which is exactly why it needs its own mapping rather than a tweak to an existing one.

The surprise: you may not need it for B2G

If your reason for looking at ebInterface is invoicing the Austrian federal government, pause. Peppol BIS 3.0 is an accepted alternative for federal invoicing — and if you already produce Peppol BIS 3.0 for anywhere else in Europe, you may simply be done.

The real reason ebInterface matters is the B2B install base. Austrian ERPs, accounting packages and trading partners have exchanged ebInterface for years, and plenty of them still expect it. That is an install-base story, not a compliance story — and it is a much better reason to support it than a mandate that does not exist.

Two modes — and mixing them up is the classic mistake

ebInterface has a generic form and a stricter federal-government (“Bund”) profile. The Bund profile adds an order reference, and when that order number is a 10-digit numeric federal one, every single invoice line needs its own order position number.

The failure mode is applying Bund rules to a private customer, or quietly forgetting them for a ministry. Both are silent: the document still looks fine. That is why we expose them as two separate output profiles rather than one profile with a flag — you have to say which one you mean.

Three things that surprise implementers

  • There is no B2C shape. The VAT identification number is mandatory on both parties — the biller and the recipient. If you invoice consumers, ebInterface is not the format for that document, and no amount of mapping will change it.
  • “Below-the-line” is not an extension mechanism. Despite the name, BelowTheLineItem carries non-tax-relevant amounts that still move the payable total: late-payment interest, third-party services, balance carry-overs. It is explicitly not for tax-exempt entries — those are ordinary line-level tax categories. (The real extension point is a separate Extension/Custom element.)
  • There is no Schematron. Unlike Peppol or XRechnung, ebInterface ships no machine-readable rule file. The XSD is the only automated gate; the rest of the specification is prose. Structurally valid is not the same as compliant.

Transport: there isn’t any

There is no SdI, no ANAF, no clearance step. ebInterface is exchanged however you and your trading partner agree — email, a portal upload, whatever the relationship already uses. That means there is nothing to integrate against, and nothing that can reject you asynchronously three days later. For once, the document is the whole job.

Where MyInvoice fits

Send the data you already export — CSV, Excel, UBL, CII, EDIFACT — and get back an ebInterface 6.1 document validated against the official XSD:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=ebinterface"

Invoicing the federal government? Switch to profile=ebinterface-bund and the order-reference and line-position rules are enforced for you — and never applied to anyone else.

Generate an Austrian invoice in your browser

Because ebInterface has no Schematron, treat the XSD as a floor rather than a ceiling — confirm the prose rules against the current specification before you go live.

Read the API docs