Austria VAT Compliance for Non-EU Companies: Which Filings Are Due When (VAT Return / Recapitulative Statement / Intrastat) — and the Pitfalls to Watch

Summary

For non-EU busi­ness­es oper­at­ing in Aus­tria, VAT com­pli­ance is rarely about a sin­gle “VAT rate ques­tion.” It is about a recur­ring fil­ing cycle: Aus­tri­an VAT returns, the reca­pit­u­la­tive state­ment (EC Sales List) and — for intra-EU move­ments of goods — Intra­stat. Most issues come from incon­sis­tent data sources (ERP vs. freight for­warder vs. 3PL/warehouse) and from tim­ing dif­fer­ences between ship­ment, invoic­ing and cus­toms. Heinz Kobled­er – Tax Advi­sors, your Tax Advis­er in Aus­tria, sup­ports non-EU com­pa­nies as fis­cal rep­re­sen­ta­tive with reli­able fil­ing process­es, rec­on­cil­i­a­tions and audit-ready doc­u­men­ta­tion.

1. Why Austria compliance is harder for non-EU businesses than it looks

Non-EU com­pa­nies often rely on mul­ti­ple oper­a­tional par­ties: mar­ket­places, Aus­tri­an or EU ful­fil­ment cen­tres, car­ri­ers, cus­toms bro­kers and local cus­tomers. Com­pli­ance, how­ev­er, is dri­ven by the actu­al move­ment of goods and how it is doc­u­ment­ed — not by the com­mer­cial con­tract alone.

Com­mon com­plex­i­ty dri­vers:

• Mul­ti­ple flows (import into Aus­tria, trans­fers, EU dis­patch­es, returns)
• Tim­ing gaps between ship­ment, arrival, clear­ance, invoic­ing and cred­it notes
• Con­flict­ing “truths” across ERP, 3PL reports and trans­port doc­u­men­ta­tion
• Spe­cial cas­es such as call-off stock/consignment struc­tures or tri­an­gu­lar flows

That is why a local Tax Advis­er in Aus­tria typ­i­cal­ly focus­es first on process design and data qual­i­ty, not on last-minute fil­ing.

2. Austrian VAT return (UVA): the backbone of ongoing VAT

The Aus­tri­an VAT return is the recur­ring state­ment that con­sol­i­dates Aus­tri­an out­put VAT and input VAT. For non-EU busi­ness­es, it often becomes the monthly/quarterly “hub” where import VAT, local tax­able sup­plies and deductible VAT all meet.

What you typically report and reconcile:

• Tax­able domes­tic sup­plies in Aus­tria
• Aus­tri­an input VAT (e.g., local sup­pli­ers, ware­hous­ing, ful­fil­ment fees)
• Import VAT (where deductible and prop­er­ly evi­denced)
• Cor­rec­tions (returns, rebates, cred­it notes) in the cor­rect peri­od

Typical pitfalls (VAT return):

1. Wrong peri­od selec­tion (invoice date vs. tax point / move­ment date).
2. Input VAT claimed with­out robust doc­u­men­ta­tion.
3. Dou­ble count­ing (import VAT record­ed twice via dif­fer­ent sources).
4. Incor­rect ERP tax cod­ing (domes­tic vs. EU vs. third-coun­try flows).

A struc­tured month­ly close with rec­on­cil­i­a­tions is usu­al­ly the fastest way to reduce audit and penal­ty risk.

3. Recapitulative statement (EC Sales List / “ZM”): small form, big consequences

The reca­pit­u­la­tive state­ment reports intra-EU sup­plies of goods and cer­tain cross-bor­der B2B ser­vices. Non-EU busi­ness­es need it as soon as goods are dis­patched from Aus­tria to cus­tomers in oth­er EU Mem­ber States (or cer­tain ser­vices are reportable).

Pitfalls (recap statement):

1. Cus­tomer VAT ID issues (invalid, wrong coun­try, not val­i­dat­ed).
2. Mis­align­ment with invoic­es and VAT returns (ship­ment in Decem­ber, invoice in Jan­u­ary).
3. Spe­cial codes/transactions missed (e.g., call-off stock report­ing).
4. Cor­rec­tions han­dled incon­sis­tent­ly and too late.

A reli­able process con­nects cus­tomer VAT ID val­i­da­tion, ship­ment data and peri­od log­ic — the same “data spine” used for the VAT return.

4. Intrastat: “just statistics” that can become a major operational burden

Intra­stat is a sta­tis­ti­cal report­ing oblig­a­tion for intra-EU move­ments of goods. Many com­pa­nies under­es­ti­mate it until they dis­cov­er that the ERP does not con­tain every­thing required (com­mod­i­ty codes, net mass, sta­tis­ti­cal val­ue, etc.), and the miss­ing pieces sit with the freight for­warder or 3PL.

Pitfalls (Intrastat):

1. Move­ment date vs. account­ing date con­fu­sion.
2. Incoterms and respon­si­bil­i­ty: who is the report­ing par­ty and who has the data?
3. Returns and replace­ments mis­han­dled.
4. Mis­match­es with the reca­pit­u­la­tive state­ment (dif­fer­ent val­u­a­tion log­ic).

5. A practical January 2026 “deadline snapshot”

To illus­trate how tight the month­ly rhythm can be, the fol­low­ing were high­light­ed as due in Jan­u­ary 2026:

• Intra­stat for Decem­ber 2025: 16 Jan­u­ary 2026
• Reca­pit­u­la­tive state­ment for Decem­ber 2025: 31 Jan­u­ary 2026

When dead­lines stack up like this, com­pa­nies suc­ceed by automat­ing data extrac­tion ear­ly and rec­on­cil­ing before sub­mis­sion.

6. Best practices: how non-EU companies avoid most mistakes

1. One dataset, three out­puts
   Define one mas­ter trans­ac­tion record per movement/sale (date, coun­try, val­ue, cus­tomer VAT ID, incoterm, ware­house, trans­port ref­er­ence). Feed VAT return, recap state­ment and Intra­stat from the same core.
2. Month­ly three-way rec­on­cil­i­a­tion
   ERP ↔ 3PL (pick/pack/ship) ↔ carrier/customs evi­dence. Resolve deltas before fil­ing.
3. Evi­dence and archiv­ing by design
   Stan­dard­ise trans­port proof, import doc­u­men­ta­tion and invoice require­ments; enforce VAT ID val­i­da­tion.
4. Clear own­er­ship and dead­lines
   Who deliv­ers which file by which date? Who reviews? Who sub­mits? Who archives?

This is where Heinz Kobled­er – Tax Advi­sors sup­ports you end-to-end: as your Tax Advis­er in Aus­tria and fis­cal rep­re­sen­ta­tive, we design the com­pli­ance set­up, run recur­ring fil­ings and build audit-ready process­es — so Aus­tria becomes a scal­able mar­ket, not a recur­ring com­pli­ance risk.

Dis­claimer: This arti­cle pro­vides gen­er­al infor­ma­tion and is not a sub­sti­tute for indi­vid­ual advice.