The AED's electronic audit file should be prepared before the request arrives, not after. What the FAIA contains, who must be able to produce it, and how Odoo exports it cleanly.

In short. The FAIA (Fichier d'Audit Informatisé de l'AED) is Luxembourg's version of the OECD SAF-T standard: an XML file gathering your complete accounting, which the Administration de l'enregistrement, des domaines et de la TVA can request during an audit. Businesses keeping computerised accounts under the standard chart of accounts must be able to produce it on demand. Odoo, properly configured for Luxembourg, generates the FAIA export natively. The real question is not whether you can click "export", but whether the file that comes out is clean.

The request usually arrives with a letter from the AED announcing a VAT audit, and a deadline to hand over the file. That is a bad moment to discover that your software cannot produce a FAIA, or that the generated file is riddled with inconsistencies. Here is how the file works, and how to make sure Odoo will deliver a flawless export when the day comes.

What is the FAIA?

The FAIA is an electronic audit file in XML format, based on the OECD's international SAF-T (Standard Audit File for Tax) standard. It contains all accounting data for a financial year: chart of accounts, journal entries, customers, suppliers, taxes and invoices. The AED requests it during VAT audits to analyse the books automatically instead of leafing through binders.

For the administration, the appeal is obvious: a structured file can be screened in minutes, cross-checks and consistency tests included. For you, it changes the nature of the audit: anomalies no longer drown in paper. A misused account, a wrongly coded VAT rate or a gap in invoice numbering shows up immediately.

Who must be able to produce a FAIA file?

The scope covers Luxembourg businesses that keep their accounts electronically and follow the standard chart of accounts, the PCN 2020. In practice, if your company files annual accounts with the RCS and runs its bookkeeping in software, you are in scope. The obligation is not to transmit the file every year: it is to be able to produce it when the AED asks, within the deadline it sets (situation as of July 2026).

This is where many businesses discover they are exposed. A generic foreign package, not localised for Luxembourg, keeps perfectly honest books that simply cannot be exported in the expected format. Fixing compliance in a hurry, under an audit deadline, always costs more than a setup done calmly in advance.

What the AED sees in your file

The FAIA lays your accounting bare: the chart of accounts and its conformity with the PCN 2020, the full journal with dates and references, customer and supplier records with their VAT numbers, the tax codes applied line by line, and the detail of invoices issued and received.

In other words, the quality of your FAIA is exactly the quality of your day-to-day bookkeeping. A file that is technically valid but substantively shaky (suspense accounts never cleared, VAT coded by hand as you go, duplicate partners) attracts precisely the questions an audit is designed to ask. The best preparation for a VAT audit is not the export, it is the bookkeeping.

Generating the FAIA export from Odoo

With Odoo's Luxembourg localisation, the FAIA export is one of the native accounting reports: you select the requested year or period, and Odoo assembles the XML file from posted entries. No third-party module, no Excel rework. It is one of Odoo's concrete arguments for a Luxembourg company, alongside the preloaded PCN 2020 and eCDF filings, a foundation we cover in our guide to setting up Luxembourg accounting in Odoo.

The condition, once again, is the initial configuration. An Odoo installed "by default", without the Luxembourg localisation enabled from the start, will produce an incomplete or non-compliant file. Three things to lock down: the chart of accounts must be the Luxembourg one (not a generic plan renumbered), taxes must use the native Luxembourg VAT codes, and partner records must carry exact VAT numbers. If any of these three foundations is missing, the FAIA export will reveal it, at the worst possible moment.

The classic pitfalls, seen from the field

On the files we take over, the same causes keep coming back. Entries left in draft for months, which do not appear in the export even though the invoices exist. Custom taxes created in a hurry to "save time", which break the mapping to the expected codes. Migrations from an old package where history was imported as one global entry, unreadable for an auditor. None of these problems is serious if caught early; all of them become serious under an audit deadline.

A simple habit: generate a test FAIA once a year, at closing, and have it reviewed. It takes little time and turns a possible audit into a formality. This is typically part of our ongoing accounting engagements: the audit file is not a crisis topic, it is a by-product of well-kept books.

Frequently asked questions

Does the FAIA have to be filed every year?

No. The FAIA is not a periodic return: it is produced at the AED's request, typically during a VAT audit. The obligation is the ability to generate it within the deadline the administration sets.

What is the difference between FAIA and eCDF?

eCDF is the platform for periodic filings (VAT returns, annual accounts). The FAIA is a one-off audit file exposing the full detail of the books. Both rest on the same foundation: accounts kept under the PCN 2020.

Does Odoo generate the FAIA natively?

Yes. Odoo's Luxembourg localisation includes the FAIA export among its accounting reports, provided the books were set up with the native Luxembourg chart of accounts and taxes.

My current software cannot produce a FAIA. What now?

Do not wait for an audit. Either your vendor offers a Luxembourg compliance extension, or you should consider migrating to a localised tool, ideally planned at year-end closing rather than under the deadline of an AED letter.

Why Advena?

  • Odoo and Luxembourg compliance under one roof: the FAIA is not an isolated technical topic, it mirrors your bookkeeping. We handle both sides.
  • Audit-minded configuration: PCN 2020, native taxes, reliable partner data, so the export is clean the first time.
  • A test FAIA at closing: included in our ongoing engagements, so an actual audit is a formality.
  • Clear fixed prices: the cost is known before we start, with no hourly billing.

Read next: Setting up Luxembourg accounting in Odoo: PCN, FAIA and eCDF · Odoo in Luxembourg: is it the right ERP for your SME?

Want to know whether your Odoo would produce a clean FAIA today? We can check it with you.

Book a free assessment