All countries
Country Guide

πŸ‡¦πŸ‡Ή E-Invoicing in Austria

B2G MandatoryPeppol
Verification pending: 20 December 2025

Austria was an early B2G adopter (mandatory since 2014) with its own ebInterface national standard alongside Peppol. B2B e-invoicing is voluntary but widely adopted. A mandatory B2B mandate is expected under EU ViDA, likely between 2027 and 2028.

TL;DR

Austria requires (B2G) e-invoicing using ebinterface, peppol_bis formats. Connected to the Peppol network for cross-border exchange.

Last updated: January 2026

Quick Facts
Format
ebinterface, peppol_bis
Peppol
Connected
Compliance

Mandate Status

Phase
Status
Scope
B2G
Live (Jan 2014)
All federal government suppliers
B2B mandate
2027-2028
Expected under ViDA

Technical Specifications

Required CIUSebInterface 6.0 (national standard, EN 16931 aligned)
Routing identifierUID (VAT identification number)
PeppolYes β€” Peppol accepted alongside ebInterface
Accepted formatsebinterface, peppol_bis
Practical

Common Rejection Patterns

#1AT-R-004ERB (e-Rechnung Bund) compliance requiredFix guide
#2AT-01Austrian sellers should include UID numberFix guide
#3BR-AT-01Austrian UID number requiredFix guide
#4AT-R-002Austrian UID number format invalidFix guide
#5AT-R-003Austrian postal code formatFix guide
Invoice Navigator auto-remediates these at pipeline speed. See how β†’

Implementation Notes

ebInterface vs Peppol. Austria accepts both ebInterface 6.0 (national standard) and Peppol BIS Billing 3.0 for B2G. The ebInterface format is EN 16931 aligned but has Austrian-specific extensions. If you're building for multiple markets, Peppol BIS 3.0 is the safer choice. B2G invoices are submitted via the USP (Unternehmensserviceportal). Digital signatures are optional but recommended.

Stay Current

πŸ”” Austria Alerts

Explore

E-Invoicing in Austria: FAQ

Ship compliant Austria invoices

Validate, fix, and route Austria e-invoices through a single API. No XML editing required.

Get API Access