Skip to main content
iVentureTeam
Odoo Upgrades

Odoo VeriFactu Guide: Spain Deadlines, Setup and Why to Upgrade

Odoo VeriFactu guide for Spain: 2027 legal dates, the announced October 2028 delay, setup in Odoo 17 to 20, and why old versions should upgrade, not patch.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 14, 202612 min read3 views
Odoo VeriFactu Guide: Spain Deadlines, Setup and Why to Upgrade cover

Spain's VeriFactu rules change how every invoice is recorded, chained and reported. If your company runs an older Odoo, our Odoo upgrade services can move you to a version where VeriFactu is built in and kept current by Odoo.

Related service: Odoo upgrade services — version upgrades with custom modules ported and tested.

This guide is for finance leads and IT managers at Spanish companies that run Odoo. For the B2B mandate side, see our guide to Odoo e-invoice formats compared covers from the format side.

What is VeriFactu and why does it matter for Odoo users?

VeriFactu is Spain's set of rules for invoicing software, and it applies to the system you use to issue invoices, including Odoo. It comes from Royal Decree 1007/2023 and the technical order HAC/1177/2024.

In plain terms, once an invoice is issued, it cannot be silently edited or deleted.

According to the AEAT's own guidance, the key technical rules are:

  • Chained records: each invoice record carries a hash built from the record before it.
  • QR code: every invoice, full or simplified, carries a QR code the customer can use to check it.
  • Event log: the system keeps a protected log of events, not only of invoices.
  • Corrections by new records: errors are fixed with an additional record or a corrective invoice, never by overwriting.

Odoo's Spain localization documentation says VeriFactu is mandatory for most taxpayers in Spain, except those who use SII or fall under a regional regime such as TicketBAI.

What are the current VeriFactu deadlines, and is there a 2028 delay?

The legal deadlines in force are 1 January 2027 for Corporate Income Tax payers and 1 July 2027 for everyone else; an October 2028 date has been announced but is not yet law. The dates have already moved twice, in April 2025 and December 2025, so check the BOE before planning around any date.

ItemDateStatus on 14 November 2026
Earlier deadlines (set by RD 254/2025)1 January 2026 and 1 July 2026Replaced in December 2025
Corporate Income Tax payersBefore 1 January 2027In force (Royal Decree-law 15/2025)
Self-employed and other taxpayersBefore 1 July 2027In force (Royal Decree-law 15/2025)
Announced new date for both groupsOctober 2028Announced 5 October 2026, not published in the BOE (unconfirmed)
Technical requirementsUnchangedMinistry says they will stay substantially equivalent

The consolidated text of RD 1007/2023 in the BOE, last updated 3 December 2025, and the AEAT's information note both still show the 2027 dates.

The Ministry's 5 October 2026 note forecasts a move to October 2028, to match the B2B e-invoicing timetable. It gave no exact day and named no legal instrument.

Our advice: plan for the 2027 dates until a new rule appears in the BOE. If the delay becomes law, you gain time to upgrade calmly, not a reason to stop.

How does VeriFactu relate to Spain e-invoicing in Odoo?

VeriFactu controls how your invoicing software records and reports invoices, while the B2B e-invoicing mandate controls how invoices are exchanged between companies. They are two different rules, and most Spanish companies will need both.

RuleWhat it coversKey dates
VeriFactu (RD 1007/2023)Invoicing software, record chaining, QR, reporting to the AEAT2027 in force; October 2028 announced
B2B e-invoicing (RD 238/2026, Order HAC/1028/2026)Structured e-invoices between businesses, invoice and payment status6 October 2027 for turnover over 8 million euros; 6 October 2028 for others
SIINear real-time VAT ledger reporting for larger companiesAlready mandatory; SII users are outside VeriFactu
TicketBAIBasque foral territoriesAlready mandatory there

Order HAC/1028/2026 came into force on 6 October 2026, which started the B2B clock. For Spain e-invoicing in Odoo, plan VeriFactu and e-invoice formats as one project.

Which Odoo versions support VeriFactu?

Odoo's official VeriFactu module exists in Odoo 17.0, 18.0, 19.0 and 20.0, but only versions 18.0 to 20.0 still get standard support and security updates. Odoo 16.0 and older have no official module at all.

Odoo versionOfficial VeriFactu moduleStandard support endsVerdict for Spain
14.0, 15.0, 16.0NoAlready endedUpgrade, or rely on community code
17.0YesSeptember 2026 (ended)Works, but no more security updates
18.0YesSeptember 2027 (planned)Fine for 2027, short runway
19.0YesSeptember 2028 (planned)Good for 2027 dates
20.0YesSeptember 2029 (planned)Longest runway, covers October 2028

The dates come from Odoo's standard and extended support table, which also says security updates are only provided during standard support.

Odoo SA has signed a declaración responsable, the self-declaration of compliance that producers must issue. The copy in the current documentation is dated 24 June 2025 and covers version "18+", while the 17.0 documentation carries one for "17.0+".

The module is part of the standard Odoo addons under the LGPL-3 licence, so VeriFactu Odoo Community databases can use it too, as can Odoo Online.

Can you patch an old Odoo version for VeriFactu instead of upgrading?

You can, through the community OCA module, but you then own the risk of running compliance code on an old, unsupported core. For most companies this is a stopgap, not a plan.

The Odoo Community Association publishes l10n_es_verifactu_oca for Odoo 16.0, with branches back to 14.0. Its README marks it Beta and lists open items, such as error handling for AEAT outages.

It also does not cover changing or cancelling invoices already sent. That is workable, but it is not code Odoo SA maintains and declares.

The bigger issue is the core. Odoo 16.0 standard support ended in September 2025, so security fixes stopped. Our guide to unsupported Odoo version security risks explains what that means for an internet-facing ERP.

Ask your tax adviser one more question. Some Spanish advisers warn that a company altering its own invoicing code may count as a producer, facing the higher penalty. We have not seen the AEAT confirm this, so treat it as unconfirmed.

Upgrade or patch: how do you decide for VeriFactu?

Odoo VeriFactu: Patch old Odoo or upgrade?

Upgrade when you are on Odoo 16 or older, carry heavy custom code, or need the system to last past 2027; patch only as a short bridge with a firm upgrade date. The table compares the two paths.

FactorPatch old Odoo (OCA module)Upgrade to Odoo 19 or 20
Who maintains VeriFactu codeCommunity, Beta statusOdoo SA, with its declaración responsable
Security updates for the coreNone on 16.0 and olderYes, until 2028 or 2029
B2B e-invoicing readinessSeparate work laterSame platform, current formats
Custom codeStays, keeps ageingPorted once, cleaned up
Cost profileLower now, repeats each rule changeHigher once, then routine
Best fitShort bridge to an agreed upgradeMost Spanish companies

Use these five questions to decide:

  1. Version: are you on 16.0 or older, where no official module exists?
  2. Custom code: do custom modules touch invoices, taxes or the POS?
  3. Horizon: will this database still issue invoices in 2028?
  4. E-invoicing: do you have more than 8 million euros of turnover and face B2B e-invoicing from October 2027?
  5. Budget: can you fund one upgrade now rather than several patches over three years?

If three or more answers point to change, upgrade. Our guide on why growing businesses should upgrade their Odoo version covers the wider case.

How do you set up VeriFactu in Odoo 19 and 20?

Install the Spain VeriFactu module, enable it in Accounting settings, upload your certificate, and test on the AEAT test servers before you switch to production. Odoo's documentation sets out the steps.

  1. In Settings, check that your company's Country and Tax ID are correct.
  2. Install Spain VeriFactu (l10n_es_edi_verifactu), and the Point of Sale add-on (l10n_es_edi_verifactu_pos) if you sell over the counter.
  3. Go to Accounting, then Configuration, then Settings, tick Enable VeriFactu and open Manage certificates.
  4. Upload your certificate file and its password. At least one certificate is required.
  5. Keep Test Environment on while you test, then turn it off when you are ready to send official data.
  6. Confirm an invoice and click Send with the VeriFactu option. Odoo stores a VeriFactu document and prints a QR code on the PDF.

AEAT can impose waiting periods between submissions, so some documents are sent later by a scheduled action. Watch the VeriFactu tab in your first weeks live.

Plan journals early. A forum user asked whether one journal could skip VeriFactu while another sends; the answer was no, so use separate journals and exempt taxes.

What goes wrong when moving old Odoo databases to VeriFactu?

Most problems come from tax setup, custom code and old data, not from the VeriFactu module itself. Test with your real invoices, not demo data.

  • Tax mapping: VeriFactu records need the right tax types and exemption reasons, so old or custom taxes must be mapped.
  • Custom invoice code: modules that change invoice numbering, posting or PDF layouts can block the QR code or the send flow.
  • Module conflicts: one Odoo 18 user reported an error when issuing an invoice with the VeriFactu module, with no answer posted, which shows why a test database matters.
  • POS: each paid order creates its own VeriFactu document, so test receipts and refunds at the till.

Porting custom modules is usually the largest piece of work. Our Odoo custom module upgrade guide explains how to scope it.

How much does an Odoo Spain compliance upgrade cost?

The cost depends mostly on your starting version and how much custom code you carry, not on VeriFactu itself. The module is included in standard Odoo, so the work is the upgrade, the setup and the testing.

Our industry estimates in the Odoo upgrade cost guide: US$1,500 to US$3,000 for 19 to 20, US$3,000 to US$6,000 for 18 to 20, US$3,500 to US$10,000 for 17 to 20. Heavy customization can pass US$30,000.

Add time for VeriFactu configuration, tax mapping and AEAT test runs. For a quick number on your own database, try the Odoo migration cost calculator.

Which industries in Spain face the most VeriFactu work?

Businesses with many simplified invoices, several journals or heavy custom invoicing face the most work. The table shows where effort usually goes.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
Retail and eCommerceHigh volume of tickets and refundsVeriFactu for Point of Sale, QR on receiptsTest tills, refunds and invoice requests
Restaurants and hospitalitySimplified invoices at the POSPOS add-on with automatic sendingSet up journals and receipt layouts
Wholesale and distributionMany customers, credit notes and exempt salesCorrective invoices and exempt taxesMap taxes and exemption reasons
ManufacturingCustom invoicing linked to orders and projectsStandard invoice flow after upgradePort custom code, test end to end
Real estate and rentalsTaxed and untaxed series side by sideSeparate journals and exempt taxesDesign journals with your tax adviser

How iVentureTeam helps with Odoo VeriFactu compliance

Upgrading for VeriFactu? Price it first

We take old Odoo databases to a supported version and set up VeriFactu so your invoices are compliant from the first day live. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Version check: we confirm what your version supports and whether patching or upgrading fits.
  • Upgrade and porting: we upgrade the database and port custom code through our Odoo migration services.
  • VeriFactu setup: module install, certificates, journals, taxes and POS.
  • AEAT test runs: real invoices sent to the test servers before you switch to production.
  • Rebuild or migrate: for very old versions, we help you choose, using our guide to Odoo migration vs reimplementation.

Odoo upgrade case study: EvoLogics

A German subsea technology company jumped three Odoo Enterprise versions with its custom workflows intact. It is not a Spanish VeriFactu project, but it shows how we handle the old-version, heavy-custom-code upgrade that most VeriFactu projects need.

EvoLogics ran Odoo 12 Enterprise with significant custom business-flow code. It was cut off from current security patches, and a straight database upgrade would have broken that code.

We audited every custom module, then migrated the database and ported the custom code to Odoo 15 Enterprise in parallel, with end-to-end testing before go-live.

The project took 12 weeks, with less than a day of cutover downtime. Read the EvoLogics Odoo 12 to 15 migration case study.

The bottom line on Odoo VeriFactu

If you run Odoo 16 or older in Spain, upgrade rather than patch; if you run 17 or 18, plan your next upgrade now. The 2027 dates are still the law, and any October 2028 delay is not yet confirmed.

Odoo 20 is the only version whose planned standard support covers an October 2028 start, so it is the safest target for most Spanish companies.

Ready to make your Odoo VeriFactu compliant?

Book a VeriFactu review

Get a clear upgrade plan before the 2027 deadlines arrive. Request an Odoo VeriFactu readiness review, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Does Odoo support VeriFactu?

+

Yes. Odoo has an official Spain VeriFactu module in versions 17.0, 18.0, 19.0 and 20.0, plus an add-on for Point of Sale. It sends records to the AEAT and prints a QR code on invoices and receipts.

When is VeriFactu mandatory?

+

Under the law in force, Corporate Income Tax payers must comply before 1 January 2027 and other taxpayers before 1 July 2027. The Ministry of Finance has announced a move to October 2028, but it is not yet published in the BOE.

Has VeriFactu been postponed to 2028?

+

Not yet in law. On 5 October 2026 the Ministry of Finance announced a plan to move the dates to October 2028. Until a rule appears in the BOE, the 2027 dates still apply, so keep planning for them.

Does VeriFactu work in Odoo Community?

+

Yes. The Spain VeriFactu module is part of the standard Odoo addons under the LGPL-3 licence, so Community databases on 17.0 or later can install it. Older Community versions need the OCA module instead.

Is there a VeriFactu module for Odoo 16?

+

Not from Odoo SA. The community OCA module l10n_es_verifactu_oca has a 16.0 branch, marked Beta. Odoo 16.0 standard support ended in September 2025, so an upgrade is usually the safer choice.

Who is exempt from VeriFactu?

+

Odoo's documentation says companies that use the SII system and those under a regional regime such as TicketBAI in the Basque Country are outside VeriFactu. Check your own case with your tax adviser.

What are the penalties for non-compliant invoicing software?

+

The AEAT lists 50,000 euros per financial year for holding a non-compliant invoicing system. Producers that sell non-compliant systems face 150,000 euros per financial year.

Is VeriFactu the same as Spain's B2B e-invoicing mandate?

+

No. VeriFactu covers how your software records and reports invoices. B2B e-invoicing covers exchanging structured invoices, from 6 October 2027 for turnover over 8 million euros and 6 October 2028 for others.

Should I upgrade to Odoo 19 or Odoo 20 for VeriFactu?

+

Both include VeriFactu. Odoo 19 standard support is planned to September 2028 and Odoo 20 to September 2029, so Odoo 20 gives the longest runway, especially if the October 2028 date is confirmed.

Free Odoo upgrade plan

Planning an Odoo upgrade?

Tell us your version, edition and custom modules. We check what breaks, what it costs to fix and the safest path, before any work begins.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.