Tax authorities across Europe are moving away from manual, sample-based audits. In their place, a growing number of jurisdictions now require businesses to submit structured accounting and VAT data in a standardised format that can be checked automatically, at scale, and in far greater detail than a traditional audit allows.
That format is SAF-T. If your business holds VAT registrations in Europe, understanding what SAF-T requires, where it applies, and how to stay ready for it is becoming a non-negotiable part of your compliance picture.
SAF-T, short for Standard Audit File for Tax, is a standardised XML format that lets businesses hand accounting and VAT data to tax authorities in a single, machine-readable file. The OECD first published the framework in 2005, giving revenue services a consistent structure for reviewing records regardless of country or accounting system.
Portugal made SAF-T reporting mandatory in 2008, and the standard audit file for tax has since spread across the EU as authorities look for faster ways to close the VAT gap. Manual audits are slow and sample-based; a properly structured SAF-T VAT file lets a tax authority run automated checks across an entire dataset, flagging inconsistencies a human auditor might miss. For businesses, VAT compliance reporting is shifting from an on-request exercise into something built into everyday bookkeeping.
A SAF-T file is built around a small number of main data blocks, though the exact schema differs from country to country:
Not every country asks for all the blocks in every submission. Portugal’s monthly file is billing-focused, while a full SAF-T VAT file requested by Lithuania or Norway expects the complete set, including fixed assets and inventory. Because the standard reuses the same schema, master data set up for one country’s SAF-T compliance obligation can usually be adapted for another through re-mapping rather than built from scratch.
Requirements differ sharply by jurisdiction, both in filing frequency and scope:
Broadly, SAF-T jurisdictions fall into two categories. Continuous reporting countries, such as Poland, Portugal and, from 2026, Bulgaria, require businesses to generate and submit a file on a fixed schedule, usually monthly, whether the authority has asked or not. The file becomes a recurring compliance deliverable, like a VAT return.
Audit-triggered countries, including Norway, Austria and, for its full accounting file, Lithuania, take a different approach. Businesses must be able to produce a compliant file within a short window, often 10 to 30 days, if requested, typically during an audit. No file needs submitting otherwise, but the obligation to be ready never goes away.
This shapes how a business resources SAF-T compliance. Continuous reporting demands a repeatable monthly process, while audit-triggered reporting demands ERP data always stay clean and exportable, since errors found mid-audit are harder to fix quietly than errors caught before a routine filing.
SAF-T does not replace a business’s VAT return. In Poland the two are combined into a single JPK_VAT filing, but in most jurisdictions SAF-T sits alongside the periodic VAT return as a separate, more granular layer of digital tax reporting. Where a VAT return summarises output and input tax at a high level, a SAF-T file exposes the underlying transactions, invoice by invoice, so an authority can reconcile the return against the data behind it.
SAF-T is also converging with e-invoicing. Portugal’s ATCUD identifiers, Poland’s KSeF mandate, and Romania’s e-Factura system are all designed to feed the same transaction data a SAF-T file reports on. The EU’s VAT in the Digital Age (ViDA) reforms push this further, aiming towards standardised, near real-time reporting for intra-EU trade by 2030. Cross-border e-commerce sellers face a related layer of digital reporting, covered in our article on what is an IOSS number and why is it important. Treating SAF-T, e-invoicing and VAT returns as separate obligations, rather than views of the same data, tends to duplicate effort and open reconciliation gaps.
A handful of errors show up repeatedly across SAF-T compliance projects:
Most trace back to the same cause: SAF-T treated as an IT export task rather than a VAT compliance reporting obligation with its own data quality standard.
Before SAF-T becomes an urgent problem, work through three questions:
Where do you have exposure? List every jurisdiction where the business holds a VAT registration, not just where it has a physical presence, since SAF-T obligations are tied to registration, not establishment.
Is SAF-T mandatory, or audit-triggered, in each country? The answer changes whether the business needs a recurring monthly process or simply audit-ready data.
Is the ERP set up to produce a compliant file today? Test an export against the current schema for each relevant country, rather than assuming last year’s mapping still holds, since schemas and thresholds change often.
For businesses managing registrations across several EU countries, this ties into the broader picture addressed in our guide on global VAT compliance key requirements, since SAF-T is one part of a wider cross-border compliance obligation.
1. Do businesses need separate SAF-T files for each country they operate in?
Yes. Each tax authority sets its own schema version, field requirements and submission portal, so one global file won’t satisfy every jurisdiction. Portugal, Poland and Lithuania build on the same OECD base structure, making the data reusable, but the file still needs to be generated separately for each country with a VAT registration.
2. What happens if a SAF-T file contains errors or inconsistencies?
Consequences vary by country, but errors typically trigger an enquiry, a request for supporting documents, or a formal audit. Persistent inconsistencies between a SAF-T file and the VAT return can also lead to penalties in jurisdictions such as Poland and Romania. Corrections are usually possible, though repeated ones draw closer scrutiny.
3. Do foreign businesses need to comply with SAF-T requirements?
In most cases, yes. SAF-T obligations are generally tied to holding a VAT registration, regardless of physical presence. Lithuania, for example, requires non-resident VAT-registered businesses to submit monthly i.SAF invoice data, though the full on-request i.SAF-T file applies only to resident companies above a turnover threshold.
4. How long are businesses required to retain SAF-T files after submission?
Retention periods generally follow each country’s standard tax record-keeping rules rather than a separate SAF-T timeline, typically five to ten years. Portugal and Poland both expect records available throughout the statute of limitations for an audit, so retained files must stay in the originally submitted format, not just as source data.
5. Does SAF-T replace traditional tax audits?
No. SAF-T changes how an audit is carried out, not whether one happens. Instead of manually sampling paper or PDF invoices, an officer can run automated checks across a business’s full transaction history in the file. This makes audits faster and more data-driven, but authorities still open formal audits and can request documentation beyond the file.
Keeping pace with SAF-T reporting across multiple jurisdictions, each with its own schema, frequency and audit triggers, is a lot to manage alongside day-to-day VAT compliance. Our team tracks SAF-T obligations across the EU and beyond, so your business always knows what is mandatory, audit-triggered, and what your ERP needs to produce on time.
Get in touch with our team to review your SAF-T exposure before a filing deadline or an audit request catches you off guard.
SAF-T Reporting Explained: What Businesses Need to Submit for VAT Compliance Tax authorities across Europe are moving away from manual, sample-based audits. In their place, a growing number of jurisdictions now require businesses to submit structured accounting and VAT data in a standardised format that can be checked automatically, at scale, and in far greater […]
The DGFiP Has Spoken: France’s September e-Invoicing Deadline Stands. There has been speculation in recent weeks about whether France’s mandatory e-Invoicing deadline would be pushed back following a cyberattack on the DGFiP, France’s Public Finances Directorate. The French government has now responded directly, and the answer is unambiguous: no postponement. David Amiel, Minister for […]
How to Deregister for VAT and What to Consider First A drop in turnover, a change of business model, or the closure of a cross-border sales channel can all result in a company being registered for a tax it no longer needs to charge. Cancelling that registration is rarely as simple as writing to the […]
EDI vs E-Invoicing: What’s the Difference and Which Does Your Business Need? Both EDI and e-Invoicing move structured transactional data electronically between businesses. On the surface they look similar. In practice they serve different purposes, operate through different mechanisms, and carry very different compliance implications depending on where your business operates. Understanding the distinction is […]
Backdating VAT Registration: What Businesses Need to Know VAT registration has a deadline. Miss it, and the tax authority does not simply move the start date forward to when you applied. In most cases, it moves it back to when you should have registered in the first place. That gap between when you were liable […]
VAT IT and Helios: Every Invoice Verified, All Eligible VAT Recovered. When your business crosses borders, the tax rules, invoice formats, and compliance requirements change with every country you enter. Most expense platforms were not built to handle that. Managing it across multiple vendors is where things tend to go wrong. Helios and VAT […]
This webinar explains how US businesses can identify and recover foreign VAT, breaking down key concepts like reciprocity and showing where refund opportunities are often missed.
