Since the Spanish Tax Agency (AEAT) published the draft law regulating the Veri*factu system, many companies and developers have worked to adapt their electronic invoicing systems to the new obligations. In the Odoo ecosystem, the Spanish Odoo Association (AEOdoo) has played a key role in ensuring that the ERP meets all the technical and legal requirements of the model.
What is Veri*factu?
Veri*factu is the new tax control system that requires invoicing programs to guarantee the integrity, preservation, accessibility, legibility and inalterability of records. Its goal is to prevent invoice manipulation and ensure that every commercial transaction can be validated by the Tax Agency.
In practice, all invoicing programs must:
Generate an invoicing record with a digital fingerprint (hash).
Electronically sign each record.
Allow the automatic and voluntary submission of records to the AEAT.
Comply with the technical formats and XML schemas defined by the administration.
The role of AEOdoo in Veri*factu compliance in Odoo
The Spanish Odoo community, led by AEOdoo and the Odoo Community Association (OCA), has developed the module l10n_es_verifactu_oca, currently available on Odoo Apps. This module is the basis for adapting Odoo to compliance with Veri*factu and represents an important step forward in Spanish tax localization.
In the most recent versions —Odoo 17, 18 and 19—, Veri*factu compliance is already natively built into the system standard, developed directly by the official Odoo team. For earlier versions, the OCA and AEOdoo continue to be the main drivers of the adaptation and maintenance of the modules needed to ensure regulatory compliance.
Among its most notable contributions:
Modular structure: integrates the logic of Veri*factu with the standard invoicing modules of Odoo, guaranteeing a clear and maintainable architecture.
Signing and chaining of records: each invoice is cryptographically linked to the previous one by hash, ensuring traceability and preventing alterations.
Generation of the Veri*factu XML: the fields and structures required by the AEAT have been implemented, following the official schema.
Preparation for sending to the AEAT: although automatic sending is not yet mandatory, the module already provides the structure needed for its future activation.
Open collaboration: development has been carried out publicly and collaboratively, allowing companies, partners and developers to take part in testing and validation.
What does this mean for companies that use Odoo?
For Spanish companies that operate with Odoo, these adaptations represent a key step toward 2025 regulatory compliance. Implementing a system compatible with Veri*factu will not be optional, and having a specialized partner will be essential to ensure a smooth transition.
Veri*factu is not just a legal obligation, it is an opportunity for your company to digitalize and secure its invoicing processes efficiently. At Birtum, we accompany companies at every step of the Odoo implementation, ensuring they comply with the regulation and optimize their operations.
Don’t wait for the deadline to arrive, contact us today and find out how to prepare your Odoo to comply with Veri*factu without complications.
