Guide
Markdown exportE-Invoicing in Austria
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Austria.
What matters in practice
This Austria guide explains EBInterface, PEPPOL routing, EN 16931 alignment, and the identity and payment questions that most often determine whether an invoice gets through.
Common e-invoice formats
Use these points as the practical checks for this section.
- EBInterface (common in Austria)
- EN 16931 mappings
Routing & delivery
Common identifiers
Use these points as the practical checks for this section.
- VAT ID
- Company registration number
Mandate & scope
Austria commonly works with EBInterface in domestic processes while PEPPOL and EN 16931-aligned XML matter for broader exchange scenarios.
Country-specific operating notes for Austria
Use these points as the practical checks for this section.
- Austria has required structured e-invoices to federal agencies since January 2014; suppliers usually submit through e-Rechnung.gv.at, USP, web service, or PEPPOL routes.
- ebInterface is the Austrian XML standard, while PEPPOL BIS Billing 3.0 is also relevant for EN 16931 and cross-border delivery.
- Before sending, confirm the buyer reference, order data, and the exact ebInterface or PEPPOL version accepted by the receiving workflow.
Quick checklist
Use these points as the practical checks for this section.
- The recipient often determines whether EBInterface, PEPPOL, or another EN 16931-aligned syntax is acceptable.
- VAT ID and company registration data should be consistent with the supplier master record.
- Structured buyer references and payment instructions help avoid manual processing delays.
How to send (practical steps)
Follow this sequence as the practical checklist for this section.
- Confirm the accepted format and delivery channel with the recipient before generating the invoice.
- Map supplier and buyer identifiers exactly as stored in the trading-partner setup.
- Validate the file against the chosen syntax and the applicable business rules.
- Send through the agreed channel and archive the transmitted XML plus acknowledgement.
Validation & compliance
Use these points as the practical checks for this section.
- When using EBInterface, keep the business semantics aligned with EN 16931 data expectations.
- When using PEPPOL/UBL, validate code lists, VAT treatment, and totals before sending.
- Check buyer references and payment instructions for exact formatting.
Common pitfalls
Use these points as the practical checks for this section.
- Assuming a PDF attachment is sufficient when the recipient expects structured XML.
- Mixing EBInterface assumptions with PEPPOL-specific routing data.
- Leaving VAT ID or registration details inconsistent with master data.
Frequently asked questions
Which invoice format is most common in Austria?
EBInterface is common in domestic workflows, while PEPPOL or other EN 16931-aligned XML formats are used for broader exchange.
What should I verify before sending an Austrian invoice?
Check the accepted format, supplier and buyer identifiers, VAT data, and payment references before you submit.