Does your Odoo version work for Verifactu? From 12 to 19

Last updated:

It depends on your version and edition. Odoo's official Verifactu module, Enterprise only, exists from version 17. On Community you can use the OCA module, which exists for Odoo 15, 16, 17 and 18; not yet for 19. If you run version 12 to 14 there is no official or community route and you will normally need to migrate.

Last reviewed: 2 November 2026. Legal dates in force: 1 January 2027 (corporate income tax payers) and 1 July 2027 (everyone else). The postponement to October 2028 was announced on 5 October 2026 and is pending publication; until it appears in the BOE the 2027 dates apply. More in deadlines and penalties.

Table by version and edition

Version Community Enterprise
12 to 14 No official or community route. Backport or third-party module (risky), or migrate. No official route. Same: backport, third-party or migrate.
15 OCA module l10n_es_verifactu_oca, 15.0 branch (under active development; test on a copy). The official module starts at 17. Options: migrate, third-party, or evaluate with your partner the OCA route (a Community module).
16 OCA module, 16.0 branch (PyPI publishes it as beta), with OSS, POS and IGIC variants. The official module starts at 17. Options: migrate to 17 or later, third-party, or evaluate with your partner the OCA route (a Community module).
17 OCA module, 17.0 branch (under active development; test on a copy). Official module l10n_es_edi_verifactu (and _pos for point of sale).
18 OCA module, 18.0 branch (under active development; test on a copy). Official module.
19 No OCA module on the 19.0 branch yet. Wait, third-party, or change edition. Official module.

Two caveats. First, an OCA branch existing does not mean it is as complete as another: the POS, OSS and IGIC variants exist only on 16.0, and the manifests do not declare a maturity status, so always test on a copy. Second, the official modules start in test mode and need a digital certificate configured. For more on each route, read the complete Verifactu on Odoo guide and the one on Odoo Community with OCA.

How to find out your version

Your version and edition appear in your contract or subscription and in the instance information provided by whoever administers your Odoo. If you are unsure, ask them: it is the first item in any inventory.

Adapt or migrate: criteria

Adapt if...

  • Your version has a clear route (official on Enterprise 17+, OCA on Community 15 to 18).
  • You have few customisations on invoices, journals and sequences.
  • Your platform works well and there is no other reason to migrate.
  • You want compliance with the least change and time.

Migrate if...

  • You are on 12 to 14, with no official or community solution.
  • You are on 19 Community and do not want to wait for an OCA module or switch to Enterprise.
  • You are on 15 or 16 Enterprise and want the official module, which requires 17 or later.
  • You carry custom developments that are hard to maintain and interfere with invoicing.
  • You already planned to migrate for other reasons (performance, features, support).

Middle cases

If you are on a version with an OCA route but with a lot of in-house code, run an inventory before deciding. Sometimes a clean migration pays off compared with keeping patches on a version that will keep ageing.

Three typical scenarios

These are generic examples to illustrate the reasoning; they describe no specific customer.

  1. Small business on Odoo 16 Community with few customisations. It has a direct route: the OCA module on 16.0, which also includes POS and IGIC if needed. The work is installing on a copy, testing with the AEAT environment and going live. Migrating would be optional.
  2. Company on Odoo 14 with a lot of in-house development. There is no module for its version. Adapting a backport on an old, customised version is risky. The sensible move is to plan a migration and treat Verifactu as one of its requirements.
  3. Company on Odoo 19 Community. There is no OCA module on 19.0 yet. It must weigh waiting for one to appear (no date guaranteed), a third-party module with the usual cautions, or moving to Enterprise, where the official one exists.

When to migrate

The legal calendar in force sets 1 January and 1 July 2027 depending on your case. The October 2028 announcement is not yet in the BOE. With that in mind:

  1. Do not bet everything on an unpublished postponement. Plan with the 2027 dates; if the postponement is confirmed, you gain room to test better.
  2. Start with the inventory. It commits you to nothing and tells you whether migrating is necessary.
  3. Migrate before adapting if the Verifactu module depends on a different version from yours. Doing both in the same window is usually worse than two well-separated phases.
  4. Leave time for testing: a period on the copy with the AEAT test environment before go-live.
  5. Avoid year-end closing as the switch date.

Questions for your partner before deciding

  • Exactly which version and edition do I have, and which fiscal and invoicing modules are installed?
  • Which customisations touch invoices, journals or sequences, and will they survive a migration?
  • Which route do you propose for my case, and why do you rule out the others?
  • How will it be tested, on which copy and against which environment?
  • Who will maintain the solution when Odoo or the rules change?
  • What is the realistic timeline, with margin ahead of the 2027 dates?
  1. Note version, edition and installed modules (invoicing, point of sale, fiscal localization).
  2. List customisations touching invoices, journals or sequences.
  3. Match against the table above to find your route.
  4. If migrating, plan it in phases and test on a copy.
  5. Test the Verifactu module against the AEAT test environment and review journals before activating.

A full checklist is in the main guide. Useful sources: the Odoo documentation on Spain and the OCA/l10n-spain repository.

Can we help?

If you are unsure whether to adapt or migrate, uKodeIT reviews your version, modules and invoicing and tells you which route makes most sense. See the service page, our implementations or contact us.

Frequently asked questions

Which Odoo version do I need for Verifactu?

Odoo's official Verifactu module (Enterprise only) is available from version 17, and also in 18 and 19. On Community the route is the OCA module, which exists for versions 15, 16, 17 and 18 (not yet for 19).

Can I use Verifactu on Odoo 16?

On Odoo 16 Community, yes, with the l10n_es_verifactu_oca module on the 16.0 branch (with OSS, POS and IGIC variants). On Odoo 16 Enterprise there is no official module (it starts at 17); the options are to migrate, use a third-party module, or evaluate with your partner the OCA route, which is a Community module.

Is there Verifactu support for Odoo 15 or earlier?

For Odoo 15 Community there is the OCA module on the 15.0 branch. For versions 12 to 14 there is no official or community route: the options are a backport or a third-party module, with maintenance risk, or migrating.

Is there a Verifactu module for Odoo 19 Community?

As of 2 November 2026 the OCA module does not exist yet on the 19.0 branch. Odoo 19 Enterprise has the official module. On Community the options are to wait, evaluate a third-party module or change edition.

Should I adapt my version or migrate?

Adapt if your version has a clear route (official or OCA) and few customisations complicating it. Migrate if you are on a version with no reasonable solution, carry a lot of custom development, or were going to migrate anyway.

How long does an Odoo migration take?

It depends on size, customisations and data; there is no universal figure. An upfront inventory lets you estimate it realistically. What matters is planning it with margin before the date that applies to you.

Related guides

← All guides