This module allows you to export XAF audit files for the Dutch tax authorities (Belastingdienst).
The currently exported version is 3.2
An option allows to export the XAF audit files in a format that is accepted by Unit4.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Create and download XAF audit files (version 3.2) for the Dutch tax authorities directly from Odoo, with an optional Unit4-compatible format.
This module adds an "Auditfile export" screen under Accounting > Reporting. There you create an export record by choosing a company, a start date and an end date; the dates default to the current fiscal year and the name defaults to a combination of the company name and the year.
On the form you press "Generate auditfile". Odoo then builds an XML file containing the company details, customers and suppliers, the chart of accounts, VAT codes, monthly periods, opening balances and all posted journal entries for the chosen period. The result is stored as a downloadable attachment and the screen shows whether generation succeeded, plus the date it was generated. If generation fails, the error is posted in the record's chatter.
Business rules shown in the code: - The start date must be earlier than the end date, otherwise Odoo refuses to save. - Only posted journal entries are included; section and note lines are skipped. - The Unit4 option truncates the document reference to 35 characters so the file can be imported into Unit4. - The generated file is validated against the official XAF 3.2 schema.
Access is limited to accounting managers. The module works with account.move, account.move.line, account.account, account.journal, account.tax, res.partner and res.company.
Depends on
Menus it adds
Models and fields (9)
- xaf.auditfile.export · new modelname, unit4, date_end (End date), auditfile, company_id, date_start (Start date), auditfile_name (Auditfile filename), date_generated (Date generated), fiscalyear_name, auditfile_success
- ir.qweb.field.auditfile.string9 · new model
- ir.qweb.field.auditfile.string10 · new model
- ir.qweb.field.auditfile.string15 · new model
- ir.qweb.field.auditfile.string20 · new model
- ir.qweb.field.auditfile.string30 · new model
- ir.qweb.field.auditfile.string35 · new model
- ir.qweb.field.auditfile.string50 · new model
- ir.qweb.field.auditfile.string999 · new model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/l10n-netherlands.
terminal Installation and usage
OCA documentation · Odoo 18.0Installation
Source · Odoo 18.0In order to reduce the memory footprint of the validation step, you can install the xmllint tool, which is part of the libxml2 package:
sudo apt install libxml2-utils
Configuration
Source · Odoo 18.0The exporting feature is available to the users who have Billing Administrator or Accountant rights for accounting.
To configure the default start and end dates of the actual fiscal year, go to accounting/settings and change the Last Day of the year you want to export. Then in the form of the audit file export, by default the end-date will be set accordingly and the start date will be 12 months before the end date. Be aware that in case the OCA module account_fiscal_year is installed, then the calculus of the fiscal year dates is overridden, taking by default the date range defined for the actual fiscal year (check Settings/Date Ranges).
Usage
Source · Odoo 18.0To use this module, you need to:
- be sure that you have Billing Administrator or Accountant rights for accounting
- go to Invoicing/Reporting/Auditfile export
- create a new record, adjust values if the defaults are not appropriate
- click Generate auditfile
- click Download on the field Auditfile
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.