Skip to main content
Best Practices

Standard Audit Files for Tax and the Trend of Digital Tax Auditing

What Is SAF-T? Standard Audit Files for Tax and Digital Tax Auditing Explained

A complete guide to the Standard Audit File for Tax: what it is, who created it, what it contains, and which countries require it.

Last reviewed: June 2026

Quick answer: SAF-T (Standard Audit File for Tax) is a standardised, XML-based file format created by the OECD in 2005 that lets businesses send accounting and tax data to tax authorities electronically. It standardises audit data so tax authorities can run faster, more accurate digital audits, while reducing the compliance burden on businesses. SAF-T is now mandatory in several European countries, including Portugal, Poland, Norway, and Romania.

What is SAF-T?

SAF-T, short for Standard Audit File for Tax, is a standardised electronic format used to exchange tax-related accounting data between businesses and tax authorities. Rather than supplying records in inconsistent, system-specific layouts, an organisation produces a single structured file that any compliant tax administration can read in the same way. The goal is to simplify the auditing process, strengthen tax compliance, and improve transparency across the tax system.

A SAF-T file presents financial information in a unified structure, drawing together transactional records such as invoices and receipts with data from accounts, general ledger entries, and tax reporting. Because the format is consistent, it enables more efficient audits and supports the broader effectiveness of tax administration. In practice, SAF-T is one of the clearest examples of how tax authorities are moving from manual, paper-based reviews toward fully digital tax auditing.

Who created SAF-T, and when?

SAF-T was created by the Organisation for Economic Co-operation and Development (OECD). The OECD published the first version of the schema, version 1.0, in May 2005, defining what a SAF-T file should contain and how the data should be formatted and structured. The original schema centred on the general ledger, invoice and payment details, and customer and supplier master files.

A revised version 2.0 followed in April 2010, extending the schema to cover inventory and fixed assets so it could handle more complex financial reporting. Version 2.0 is not fully backward-compatible with version 1.0, which is one reason national implementations differ: some countries adopted the earlier version while others built on the later one. The OECD defines the standard itself, but each tax administration decides the exact data it captures and how and when files must be submitted.

What does a SAF-T file contain?

A typical SAF-T file brings together the core financial and tax information a tax authority needs to verify compliance. While the precise contents vary by country and schema version, most files include the following:

  • Taxpayer information – the identification number and core business details of the organisation.
  • General ledger accounts – details of the accounts maintained and the entries posted to them.
  • Invoices and credit notes – transactional data including VAT information and payment details.
  • Customer and supplier information – master data on the business partners involved in transactions.
  • Tax details – applicable tax categories, rates, and amounts.

From version 2.0 onward, the schema also accommodates inventory and fixed-asset records, and some national variants extend further into areas such as accounts receivable and payable or payroll data.

What format is a SAF-T file?

SAF-T files are structured in XML (Extensible Markup Language). XML allows standardised data representation and integrates readily with accounting and enterprise resource planning (ERP) systems. Its flexibility is part of why the standard has spread so widely: the same underlying approach can be adapted to the differing requirements of individual jurisdictions and businesses without abandoning a common, machine-readable foundation.

Which countries require SAF-T?

Although SAF-T provides a common international starting point, individual countries tailor it to their own regulatory frameworks, so requirements and submission rules differ. Adoption has been concentrated in Europe, with Portugal acting as the early pioneer. The table below summarises how some of the main adopters apply the standard.

CountryIn use sinceHow it works
Portugal 2008 First country to adopt SAF-T; monthly SAF-T (PT) files are mandatory for invoices and ledgers.
Poland 2016 Introduced as JPK and mandatory from 2018; since 2020 the JPK_V7 file combines the VAT return and transaction-level data.
Norway 2020 Mandatory since 1 January 2020, but files are generally required only on request.
Romania 2022 SAF-T (RO), known as D406, is mandatory, with standard monthly, annual asset, and on-request stock reports.
Austria On request SAF-T files are requested during audits rather than submitted periodically.
Lithuania, Luxembourg Adopted Both have implemented national SAF-T schemas reflecting local tax rules.
France Audit-based Uses the FEC audit file, related to but not identical to the OECD SAF-T standard.

By contrast, the United Kingdom did not adopt SAF-T, choosing its Making Tax Digital (MTD) initiative and a focus on digital VAT submissions instead.

How is SAF-T submitted?

Across the countries that have adopted SAF-T, three broad submission models have emerged. In the first, data is provided only at the request of the tax authority, typically ahead of an inspection or audit. In the second, files are submitted periodically alongside the regular VAT return. In the third, a single combined filing merges the VAT return with transaction-level detail, as Poland does with its JPK_V7 file. The model in force determines how often a business must generate compliant files and how deeply SAF-T is embedded in its day-to-day reporting.

What are the benefits of SAF-T?

For tax authorities, SAF-T enables faster, more consistent audits because data arrives in a predictable, machine-readable structure rather than dozens of bespoke formats. For businesses, the standardisation streamlines the way accounting data is fetched and organised, improves the quality and accessibility of archived records, and simplifies compliance for multinational groups operating across several jurisdictions. The shared objectives of the standard – facilitating compliance, reducing the cost and complexity of audits, improving data accuracy, and providing a clear and consistent format – benefit both sides of the relationship.

What are the challenges of implementing SAF-T?

Adopting SAF-T is rarely without difficulty. The most immediate challenge is cost: meeting the standard often calls for significant upfront investment in accounting software, staff training, and process changes, and organisations must confirm that their systems can genuinely produce compliant files.

Data quality is a second, ongoing concern. Reliable SAF-T outputs depend on accurate, well-organised accounting records, and shortcomings can create complications during an audit that may lead to penalties or wider compliance issues. Because countries periodically revise their regulations and schemas, organisations must also monitor change closely, treating compliance as a continuing obligation rather than a one-off project.

Integration is the third challenge. Embedding SAF-T functionality within existing ERP or accounting systems can be technically demanding, particularly for organisations that rely on legacy infrastructure, and specialist expertise is often required to deliver a smooth and dependable transition.

SAF-T and the future of digital tax auditing

Standard Audit Files for Tax represent a significant step forward in how tax data is collected, exchanged, and audited. By advancing standardisation and transparency, the framework improves the relationship between businesses and tax authorities, strengthens compliance, and reduces the costs traditionally associated with audits. The implementation hurdles are real, but they are generally outweighed by the longer-term benefits of a more efficient and effective approach to tax administration. As tax authorities worldwide continue to embrace digital transformation, SAF-T is poised to become a foundational component of the global tax landscape.

Frequently asked questions

Is SAF-T mandatory?

It depends on the country. SAF-T is mandatory in jurisdictions such as Portugal, Poland, Norway, and Romania, though the timing and frequency of submission differ. In some countries files must be submitted periodically; in others they are required only when a tax authority requests them during an audit.

What is the difference between SAF-T version 1.0 and version 2.0?

Version 1.0, published by the OECD in 2005, focused on the general ledger, invoices, payments, and customer and supplier master files. Version 2.0, released in 2010, added inventory and fixed-asset data to support more complex reporting. The two versions are not fully backward-compatible, which is why national implementations vary.

Does the United Kingdom use SAF-T?

No. The UK chose a different path with its Making Tax Digital (MTD) initiative, which emphasises digital VAT submissions rather than a comprehensive standard audit file.

What systems generate SAF-T files?

SAF-T files are produced by accounting and enterprise resource planning (ERP) software. Because the format is XML-based, compliant systems can export the required data in a standardised structure, though legacy systems may need additional configuration or middleware.

Is SAF-T the same as e-invoicing?

No. E-invoicing concerns the real-time or near-real-time exchange of individual invoices, while SAF-T is a broader audit file covering ledgers, master data, and tax details. The two are related parts of the wider move toward digital tax reporting but serve different purposes.

Key takeaways

  • Definition: SAF-T is a standardised, XML-based file for sending accounting and tax data to tax authorities.
  • Origin: Created by the OECD, with version 1.0 in 2005 and version 2.0 in 2010.
  • Adoption: Mainly European; Portugal led in 2008, followed by Poland, Norway, Romania, and others.
  • Purpose: Faster, more accurate digital audits and lower compliance costs.
  • Challenges: Upfront cost, data quality, and integration with existing or legacy systems.
Richard Cornelisse
Richard Cornelisse

Tax Function Effectiveness expert