Short answer: is Odoo ready for Verifactu?
Yes, natively. Odoo S.A. ships the «Spain - Veri*Factu» module (technical name l10n_es_edi_verifactu) in the Odoo Community repository, under LGPL-3, in versions 17, 18 and 19. There is also a point-of-sale module (l10n_es_edi_verifactu_pos). So you do not need Enterprise to comply, and you do not need to buy a third-party connector.
There is also the community route: the OCA maintains l10n_es_verifactu_oca (AGPL-3) in the l10n-spain repository, for versions 16, 17 and 18. It is the usual choice if your Odoo runs the OCA Spanish localisation instead of the official one, or if you are still on Odoo 16.
Verifactu in Odoo is not a paid Enterprise extra: the official module ships in Community, under a free licence, since Odoo 17.
Which module each Odoo version uses
| Odoo version | Official module (Odoo S.A.) | OCA module | Our recommendation |
|---|---|---|---|
| Odoo 19 | l10n_es_edi_verifactu (LGPL-3) | — | The official one |
| Odoo 18 | l10n_es_edi_verifactu (LGPL-3) | l10n_es_verifactu_oca (AGPL-3) | The official one, unless you already run the OCA localisation |
| Odoo 17 | l10n_es_edi_verifactu (LGPL-3) | l10n_es_verifactu_oca (AGPL-3) | The official one, and plan an upgrade |
| Odoo 16 | Does not exist | l10n_es_verifactu_oca (AGPL-3) | The OCA one or, better, migrate |
| Odoo 15 or older | Does not exist | Does not exist | Migrate before 2027 |
On Odoo 15 or older there is no module to install: the conversation is no longer Verifactu, it is migration. Start early, because migrating an ERP with years of data does not happen in a month.
Community or Enterprise: what changes for Verifactu
For the obligation itself, nothing: the same official module generates the chained invoicing records, each invoice's hash and the QR code, and sends them to the tax agency in both Community and Enterprise. What changes is everything around the invoice. Enterprise brings Odoo S.A.'s full accounting and is billed per user; Community covers the essentials of invoicing and accounting.
That is why we built Community Plus: Odoo Community with full Spanish accounting (PGC, forms 303 and 390), Verifactu and SII installed and verified as standard, payroll and time tracking, with €0 in licences. For many Catalan SMEs it is the cheapest way to comply without falling short.
How to set up Verifactu in Odoo, step by step
1. Check the version and localisation
The official module needs Odoo 17 or later, with the Spanish localisation (l10n_es) installed and the PGC chart of accounts applied to the company. If you run several companies in one Odoo, each one is configured separately.
2. Install the Spain - Veri*Factu module
Install «Spain - Veri*Factu» from Apps and, if you invoice in a shop or in hospitality, the point-of-sale one too. Once installed, the Accounting settings show the checkbox to enable Veri*Factu for the company.
3. Upload the company's electronic certificate
Submissions to the tax agency are signed with a certificate: the company's legal representative certificate or a seal certificate. It is uploaded to Odoo as a .p12 or .pfx file with its password. If the certificate expires, submissions stop: note the date.
4. Test first in the tax agency's test environment
The module has a test-environment switch. With it on, Odoo sends records to the tax agency's test environment rather than production. There you issue normal, corrective and simplified invoices and cancellations, and check that every one is accepted without errors.
5. Review journals, series and taxes
Each sales journal is an invoicing series. Before going live, check that series do not overlap, that taxes carry the right VAT regime key and that EU and foreign customers have the correct tax ID. This is the step that prevents the most errors later.
6. Go live before your deadline
Switch the test environment off and from then on every validated invoice generates its chained record, prints the QR code and is sent to the tax agency. Odoo batches the submissions and shows each invoice's record status, so you can see at a glance if any was rejected.
The Catalan case: AEAT, not ATC
A question we hear a lot in Catalonia: does this go to the Catalan Tax Agency (ATC)? No. Verifactu implements a state regulation (Royal Decree 1007/2023) and records go to the Spanish Tax Agency (AEAT). Catalonia is common territory for this regulation, so it applies in full, just as in Madrid or Valencia. The only territorial exceptions are the Basque Country and Navarre, which have their own regional rules.
What is local is the work: many Catalan SMEs invoice in Catalan, have an outside accountant who also logs into Odoo, and have run for years on software that will not make it to 2027. A well-done implementation solves all three at once: template language, accountant access and migration of the old data.
Deadlines: which date applies to you
| Taxpayer type | Deadline | Source |
|---|---|---|
| Company (Corporate Income Tax) | 1 January 2027 | RD 1007/2023, fourth final provision |
| Self-employed or professional (IRPF) | 1 July 2027 | RD 1007/2023, art. 3.1 |
| Company already filing through SII | This regulation does not apply | RD 1007/2023, art. 3.3 |
If you already file VAT through SII, the regulation excludes you: Odoo also has an official SII module (l10n_es_edi_sii) and you stay on it. Otherwise your own date is the one that matters, and the sensible plan is to finish testing several months ahead.
What Verifactu in Odoo costs
The module is free in every edition. What costs money is the work: configuring the company, certificate, series and taxes, testing with the tax agency and training whoever invoices. In Community Plus and Agentic that work is included as standard. In Community and Enterprise we do it inside the implementation project, and if you already run Odoo, we quote it as a fixed project.