Austria — Peppol BIS · federal B2G mandate
Peppol BIS B2G mandate live since 2014 · No B2B mandate yet — regulator: Bundesministerium für Finanzen (BMF). Facts last refreshed: 2026-05-05.
POST /v1/documents/send.
TL;DR
- Austria adopted Peppol BIS 3.0 natively for federal B2G in 2014 — no national wrapper, no separate hub.
- No domestic B2B mandate as of 2026; Austria has signalled alignment with the EU ViDA framework (target 2030–2032).
- Public-sector recipients are routed through e-Rechnung.gv.at (ER>B portal) — Flowie resolves the Peppol ID for you.
- Flowie is a registered Peppol Access Point (
9915:flowiefor AT) — or routed through a specialized local partner where in-country presence is required.
Deadlines
| Date | Who | What |
|---|---|---|
| 2014-01-01 | Federal contracting authorities | B2G e-invoicing mandatory (BGBl. I Nr. 32/2014). |
| ≥ 2030 | All B2B taxable supplies (expected) | Aligned with EU ViDA — not yet legislated; planning baseline only. |
Background
Austria was one of the earliest Peppol adopters in the EU, going live with federal B2G in January 2014 via the e-Rechnung.gv.at portal (also called ER>B). The portal is operated by the Bundesministerium für Finanzen and acts as a Peppol-aware ingress for every federal contracting authority. Suppliers either upload directly through the portal or — much more commonly via Flowie — send a Peppol BIS 3.0 invoice that the recipient AP routes to the federal node automatically.
B2B remains voluntary. The Austrian government has stated it will follow the EU ViDA timeline rather than introduce a national mandate ahead of the EU framework, so the first realistic B2B deadline is post-2030.
Format profile
- Peppol BIS 3.0 (UBL or CII), no national CIUS for federal B2G beyond standard EN 16931.
- Some federal authorities additionally accept ebInterface 4.x / 5.x (legacy XML) — Flowie auto-converts when the recipient declares ebInterface in its SMP record.
- The
BuyerReferenceon B2G must be the contracting authority's Auftragsreferenz (order reference); without it, ER>B rejects.
Required fields
-
buyerReferencestringrequired for B2G
Auftragsreferenz issued by the federal authority. Without it, e-Rechnung.gv.at rejects synchronously.
-
seller.vatNumberstringrequired
Format
ATU12345678. Validated against UID-Bestätigungsverfahren.
Public sector (B2G)
| Hub | Peppol identifier scheme | Lookup |
|---|---|---|
| e-Rechnung.gv.at (ER>B) | 9915:AT-GOV-<authority-id> | https://www.erb.gv.at |
Federal authorities are listed in the ER>B directory. Land (state) and municipal authorities adopt at their own pace; about half are Peppol-reachable in 2026.
B2B reporting / clearance
No central B2B reporting hub — pure transmission only.
Error codes
Generic Peppol BIS schematron error codes apply (BR-*, EN16931-*); no country-specific overlays.
Testing in sandbox
| What you want to test | How |
|---|---|
| Federal B2G happy path | Sender VAT ATU00000001, recipient 9915:AT-GOV-TEST in sandbox. |
| Missing Auftragsreferenz | Send to a B2G recipient without buyerReference → AT-specific rejection echoed back. |
FAQ
Do I need to register on e-Rechnung.gv.at to send to a federal authority?
No, not when sending via Peppol — Flowie's AP delivers to the federal endpoint behind ER>B. You only register if you upload manually through the portal.
Can I use ebInterface instead of Peppol BIS?
Yes, and Flowie can render ebInterface 5.0 from the same JSON payload. But Peppol BIS is the strategic format and what every new authority accepts.
References
Primary sources (government / regulator / standards body):
- EU Commission · eInvoicing in Austria — Pan-EU reference factsheet.
- OpenPeppol · Austria profile — Authoritative Peppol facts.
- BMF · Austrian Ministry of Finance — Tax authority owning e-invoicing policy.
- USP · e-Rechnung an die Verwaltung — Official B2G submission portal guide.
- e-Rechnung.gv.at — Federal e-invoicing platform.
Industry analyses (vendor trackers — useful for cross-referencing):
- EDICOM · Austria e-invoicing analysis — Industry tracker — formats and timelines.