What Is SAF-T Tax? Countries, Filing, and Penalties

SAF-T tax reporting is the Standard Audit File for Tax, an OECD-designed electronic format that lets tax authorities pull a company’s accounting data directly out of its software in a structured XML file. More than a dozen countries now require it in some form, each with its own version of the schema, its own filing rhythm, and its own penalty scale. If your company operates in one of them, SAF-T is a compliance obligation with real financial consequences attached to getting the details wrong.1Organisation for Economic Co-operation and Development. Guidance on Tax Compliance for Business and Accounting Software

What Goes Into a SAF-T File

Every SAF-T file is an XML document, meaning the data sits inside labeled tags that any tax authority’s software can read regardless of what accounting system produced it.2Organisation for Economic Co-operation and Development. Guidance for the Standard Audit File – Tax, Version 2.0 The OECD’s version 2.0 schema splits the file into four parts: a header with company and period information, master files holding standing data like the chart of accounts and customer, supplier, product, tax rate, stock, and fixed asset records, the general ledger entries covering every journal posting for the period, and source documents such as sales invoices, purchase invoices, payments, and goods movements.

The general ledger is the backbone. Each entry needs a transaction date, unique ID, posting date, debit and credit amounts, and a link back to the source document, in an unbroken sequence. Accounts receivable and payable sit in the master files section as customer and supplier records that must reconcile with the ledger entries referencing them. Fixed assets, inventory, and stock movements may or may not be required in every filing depending on the country, but your system should be able to produce them on demand.3Organisation for Economic Co-operation and Development. Guidance for the Standard Audit File – Tax, Version 2.0

That four-part skeleton stays constant across countries. What changes is which elements are mandatory and how granular the data has to be. Romania requires over 390 mandatory data elements. Norway’s implementation focuses on master files, general ledger transactions, and company information.4The Norwegian Tax Administration. SAF-T Financial A company filing in both countries needs two different mapping configurations for the same underlying accounting data.

How Filing Works

Before you submit, most countries expect you to run the file through a government-provided or government-approved validation tool. It checks that every required tag is present, dates use the right format, debits and credits balance, and entry numbers run sequentially. If the file fails, you get an error report pointing to the specific lines.

A validated file is uploaded through a national tax portal or transmitted via an API that connects your accounting system directly to the tax authority. Norway uses the Altinn portal. Portugal and Romania run their own dedicated platforms. A successful upload produces a digital receipt. Keep it. If a filing dispute arises later, that receipt is your proof. When a submission fails, the fix-and-resubmit usually has to happen before the original deadline, because extensions are rare and generally require a formal request.

How Often You File

Filing frequency depends entirely on the country. Portugal requires monthly reporting of sales and purchase data plus an annual accounting file. Poland’s JPK VAT register is a monthly obligation for every VAT-registered company. Norway and Austria go the other way: no periodic filing, but you have to produce a valid SAF-T file on demand when tax authorities ask, typically during an audit. Lithuania uses a hybrid model where some taxpayers file monthly and others only on request.

On-demand does not mean low-stakes. If the tax authority requests your file and your software can’t generate a compliant export, you face penalties and a scramble to produce the data under time pressure.

Which Countries Require SAF-T

Countries with active SAF-T requirements include Portugal, Poland, Norway, Romania, France, Luxembourg, Lithuania, Austria, and Angola. Bulgaria is phasing in its own version starting in 2026. All of them trace back to the OECD template, but the local rules diverge enough that a multinational company treats each jurisdiction as a separate compliance project.

Portugal

Portugal was one of the earliest adopters, starting in 2008 under Portaria No. 321-A/2007. It covers two streams: a monthly invoicing file with sales and purchase data (mandatory since January 2020) and an annual accounting file with ledger and chart-of-accounts information. The mandatory qualified electronic signature requirement for the accounting file has been postponed again.5KPMG. Portugal: Postponed Mandatory Use of Qualified Electronic Signature (QES) and SAF-T Accounting File Requirements Failure to submit can trigger penalties up to €5,000, with additional fines for accounting record delays exceeding 90 days.

Poland

Poland’s version is called JPK (Jednolity Plik Kontrolny) and is among the most comprehensive in Europe. The JPK VAT register, currently on version JPK_V7M(3), rolls record-keeping and the monthly VAT declaration into one file. JPK CIT extends the obligation into corporate income tax records, including fixed assets and economic events affecting financial results. Non-compliance triggers penal and fiscal sanctions, and when the resulting tax shortfall exceeds PLN 10,000, the violation is classified as a crime rather than a misdemeanor.

Norway

Norway requires SAF-T Financial for all businesses with bookkeeping obligations that use electronic accounting systems.4The Norwegian Tax Administration. SAF-T Financial Small businesses with annual turnover below NOK 5 million that don’t keep electronic records are exempt, as are enterprises with fewer than 600 vouchers per year using spreadsheets. Since January 2025, submissions must use version 1.30 of the format. Filing is on demand: no periodic deadline, but when Skatteetaten asks, you deliver. A failure carries a fixed NOK 13,450 penalty, doubling to NOK 26,900 for a repeat within twelve months.

Romania

Romania’s D406 declaration rolled out in phases: large taxpayers since January 2022, medium since January 2023, small since January 2025. The schema is dense, with more than 390 mandatory data elements covering inventory, asset movements, and standard accounting records. Missing the deadline runs RON 1,000 to RON 5,000. Filing an incorrect or incomplete file runs RON 500 to RON 1,500. New filers get a graduated grace period, starting at six months for the first monthly statement and shrinking to two months by the fifth.

France

France doesn’t use the SAF-T name but requires a functionally similar file called the FEC (Fichier des Ecritures Comptables). The FEC uses a flat text format with tab or pipe delimiters rather than XML, and it must contain exactly 18 mandatory columns covering journal entries, account codes, descriptions, and currency amounts. The submission trigger is what sets it apart: the FEC has to be handed to the auditor on the first day of a tax inspection, with no grace period. Under Article L74 of the Livre des Procédures Fiscales, a non-compliant FEC brings a penalty of €5,000 per audited fiscal year or a 10% surcharge on reassessed tax, whichever is higher.

Luxembourg, Lithuania, and Austria

Luxembourg requires a SAF-T file known as FAIA for VAT-registered entities that use the national standard chart of accounts, file periodic VAT returns, record more than 500 transactions a year, and have turnover above €112,000. Filing is on demand. Austria adopted SAF-T in 2009 and also uses an on-demand model, producing the file when the Federal Ministry of Finance requests it during an audit. Lithuania phased in its requirement between 2016 and 2020, applying it to VAT-registered resident companies with annual turnover above €300,000, again on demand.

Penalties for Non-Compliance

Every country sets its own penalty framework, and the numbers vary not just between jurisdictions but between offense types inside the same jurisdiction.

  • Portugal: up to €5,000 for failure to submit, plus additional penalties for accounting delays over 90 days.
  • Poland: penal and fiscal sanctions scaling with the tax shortfall; shortfalls above PLN 10,000 are treated as criminal offenses.
  • Norway: NOK 13,450 per failure, doubling to NOK 26,900 for a repeat within twelve months.
  • Romania: RON 1,000 to RON 5,000 for missing the deadline; RON 500 to RON 1,500 for an incorrect or incomplete filing.
  • France: €5,000 per audited fiscal year or a 10% surcharge on reassessed tax, whichever is greater.

Direct fines aren’t the whole picture. A pattern of non-compliance can trigger a full audit, and in several countries the tax authority can impose estimated assessments when a company fails to provide the requested data. The exposure from an estimated assessment almost always exceeds what the actual data would have shown.

Where Implementation Actually Breaks

The hard part of SAF-T isn’t the rulebook. It’s getting your accounting system to produce a clean file. Problems cluster in a few predictable places.

Data mapping is where most projects stall. Your ERP stores data in whatever structure the vendor designed, and that structure rarely lines up with a SAF-T schema out of the box. Field names differ. Date formats differ. Decimal separators differ; France requires commas rather than periods. Account numbering may not match the country’s required taxonomy. Each mismatch needs a custom mapping rule, and a large organization with legacy systems can carry hundreds of them.

Multi-country operations compound the problem. Operating in Portugal, Poland, and Romania means three separate mapping configurations off the same underlying accounting data. A schema version change in one country can break the extraction there without affecting the others, so someone has to track regulatory updates in every jurisdiction you file in.

Data quality issues that stay invisible in daily operations surface the moment you try to export a SAF-T file. Gaps in transaction numbering, unreconciled entries, missing customer or supplier master records, and duplicate entries all cause validation failures. Companies that treat SAF-T preparation as a year-end task tend to spend the run-up to the deadline fixing months of accumulated errors. Building SAF-T validation into the monthly close is what catches problems while they’re still small.

Software readiness is the last piece. Not every accounting package includes a SAF-T export module, and the ones that do don’t always keep pace with schema version changes. Some companies use third-party middleware between their accounting system and the required output. Others rely on their ERP vendor’s updates. Either way, testing the export against the government’s validation tool well before the filing date is the only reliable way to avoid finding out on submission day.