Spanish Accounting and Tax Compliance in Odoo

With Binovo, the tax compliance of your Odoo is covered: we have our own in-house team that knows Spanish tax rules, both national and foral, develops and maintains them in Odoo, and anticipates changes from the tax authorities without relying on third parties. We implement Odoo Community and Enterprise for companies across Spain from Oiartzun (Gipuzkoa), and we share what we develop with the OCA and the community.

Information reviewed on 18 November 2026 using sources from the Spanish Tax Agency, the Canary Islands Tax Agency, the foral tax authorities of Gipuzkoa, Bizkaia, Álava and Navarre, and the BOE (Spain’s Official State Gazette).

In short

  • What your Odoo must comply with depends on where you pay tax: the Spanish Tax Agency (Verifactu, SII), the Basque tax authorities (TicketBAI, foral SII, LROE in Bizkaia) or the Foral Tax Authority of Navarre (foral SII and, in preparation, NaTicket). In the Canary Islands, IGIC replaces VAT.
  • B2B e-invoicing under the Crea y Crece Act and Facturae for public administrations are separate obligations that coexist in the same ERP. If you sell to consumers in other EU countries, you may have to apply their VAT and report it through the one-stop shop (OSS).
  • At Binovo, two team members are dedicated to regulatory monitoring, and our clients’ tax and accounting changes (SII, tax returns, invoicing systems) are developed and maintained by our own team, on a common Odoo base with the same patches for everyone.
  • We are the authors of the TicketBAI modules published in the OCA, and our Verifactu module for Odoo is public on GitHub.

What affects you depending on where you pay tax

Several tax authorities coexist in Spain. The same Odoo may need different configurations if your group has companies in several territories:

Where you pay tax Invoicing VAT books What’s coming
Spanish Tax Agency (common territory) Verifactu: mandatory from 1 January 2027 for Corporate Income Tax payers and from 1 July 2027 for everyone else (Royal Decree-Law 15/2025). A postponement to October 2028 has been announced, pending publication in the BOE SII for large companies (turnover above €6 million), VAT groups and companies registered in the REDEME: submission within four business days B2B e-invoicing
Canary Islands (Canary Islands Tax Agency) Verifactu, as in the rest of the common territory IGIC instead of VAT (general rate of 7%), with quarterly self-assessment on form 420 and the IGIC SII for those required to use it B2B e-invoicing
Gipuzkoa TicketBAI, mandatory for everyone since 1 June 2023 Foral SII for those required to use it. TicketBAI does not exempt you from the SII LiburuBAI: draft record books and VAT and personal income tax returns for self-employed individuals and professionals, based on TicketBAI data
Bizkaia TicketBAI within Batuz, mandatory for everyone since 1 January 2026 Batuz LROE record book, which includes the SII: data is submitted only once B2B invoicing, pending agreement with the Spanish Tax Agency
Álava TicketBAI, mandatory for everyone since 1 December 2022 Foral SII for those required to use it. There is no LROE in Álava B2B invoicing, pending agreement with the Spanish Tax Agency
Navarre Neither Verifactu nor TicketBAI for activity taxed in Navarre. NaTicket, in preparation with no dates yet Foral SII, in force since 2018 for those required to use it NaTicket and B2B invoicing, pending agreement with the Spanish Tax Agency

Throughout Spain, if you sell to a public administration, the invoice must be in Facturae format and submitted through FACe or the body’s own entry point: we explain this in Facturae and FACe in Odoo (in Spanish). B2B e-invoicing will be mandatory from 6 October 2027 for companies with an annual turnover above €8 million and from 6 October 2028 for everyone else; in the Basque Country and Navarre it will be implemented through agreements with the foral tax authorities, which are still pending.

If you sell to consumers in other EU countries: OSS

When a Spanish company makes distance sales to final consumers in other European Union countries, or provides them with certain services, and exceeds €10,000 a year across the EU as a whole, it must apply the VAT of the customer’s country. With the one-stop shop (OSS), everything is reported to the Spanish Tax Agency using form 369, without registering in each country. In Odoo, this means having the VAT rates of each country and fiscal positions that apply them depending on where the customer is located, and extracting from the accounting records the amounts required by the return.

What we cover in Odoo

Besides complying with each obligation, we take care of what makes it possible: a well-configured chart of accounts, taxes and fiscal positions, so that what Odoo sends to the tax authorities matches your accounting.

How we maintain the tax compliance of your Odoo

With Odoo, it is common to wait for the community to update the Spanish localization. The community does an enormous amount of work, but its timelines are those of a collaborative project, and regulations come with deadlines. That is why at Binovo we do it this way:

  • Regulatory monitoring. Two team members follow the accounting and tax changes published by the Spanish Tax Agency, the foral tax authorities and the BOE. We don’t do this only for Odoo: our TicketBAI and Verifactu API products, and what we develop for B2B e-invoicing, both in Odoo and in our API, depend on staying up to date.
  • In-house team. Our clients’ tax and accounting changes, from the SII to tax returns, are developed and maintained by our own team, without relying on third parties.
  • We evaluate before applying. If the OCA incorporates a new feature first, we review it before rolling it out to our clients. If time is short, we develop it ourselves.
  • A common base. We maintain a common Odoo base with the same patches for all clients: when a rule changes, the change reaches everyone.
  • A consultant as your point of contact, who knows your installation and lets you know what affects you. More in Odoo maintenance and support.
  • Community or Enterprise, no dogmas: we present both and you decide.

An example: VAT on food in 2023

Because of the war in Ukraine, Royal Decree-Law 20/2022 was published in the BOE on 28 December 2022 and reduced VAT on several food products with effect from 1 January 2023: from 4% to 0% and from 10% to 5%. There were barely a few days, with the year-end in between. Our team did not wait for the community and updated all our clients on time.

Our commitment: no Binovo client is left without their regulatory update.

How we follow an upcoming change: LiburuBAI in Gipuzkoa

Tax compliance is the most sensitive part of running a company, which is why we don’t wait for a change to become mandatory before we start working on it. LiburuBAI is the project we are currently monitoring, and this is our process:

  1. Detect. In May 2025, the Provincial Council of Gipuzkoa (Diputación Foral), through its IT company IZFE, put out to tender the project “LiburuBAI, Record books of economic activities for individuals”, co-financed by the ERDF Basque Country 2021-2027 programme. Our regulatory monitoring team added it to the list of changes under follow-up.
  2. Understand what it is and who it affects. According to the Provincial Council, LiburuBAI will make use of the invoicing data that arrives in real time through TicketBAI so that the foral tax authority can automatically prepare a draft of the mandatory record books and of some VAT and personal income tax returns for self-employed individuals and professionals. It is a step in line with what Bizkaia does with Batuz and the LROE.
  3. Separate what is known from what is not. The Provincial Council has not yet published whether it will be voluntary or mandatory, nor launch dates, nor technical specifications for software providers. We don’t tell our clients anything that has not been published.
  4. Decide the scope. We will develop it for Odoo and also for our Binovo TicketBAI and Verifactu API (in Spanish), so that companies with other ERPs can connect to the foral tax authority and comply with LiburuBAI.
  5. Prepare what can already be done. Since the draft will be generated from TicketBAI data, we check that the invoicing our clients submit is complete and consistent with their accounting.
  6. Develop, test and deploy. Once the specifications are published, we develop it, test it and roll it out to all clients through our common base, with notice from their consultant.

It is the same process we follow with TicketBAI, Batuz, Verifactu and B2B e-invoicing.

To provide you with this service, your Odoo must be part of our system: we do not install tax modules for clients who work with another partner, nor do we provide a service solely to install a module.

What we share with the community

Having our own team doesn’t mean being closed off. We develop first for our clients and share afterwards:

  • TicketBAI: we are the authors of the modules published in the OCA l10n-spain repository, under the AGPL-3 licence, including the Bizkaia LROE module, which we co-authored with Digital5.
  • Verifactu: our module for Odoo and the verifactu-xmlgen tool are public on GitHub.
  • B2B e-invoicing: the module we are developing will also be public.

If you download and install them in your Odoo or in your clients’ Odoo, whoever installs them becomes responsible for that invoicing system. Binovo is responsible for the installations it controls.

How much it costs

The cost is determined in a consultation or conversation with you. Needs differ even within the same sector, and giving a general figure would create false expectations. The main factors are where your companies pay tax, whether you already have Odoo, custom developments, the channels you invoice through, and any data that needs to be migrated.

Frequently asked questions

Is Odoo suitable for Spanish accounting and tax compliance?

Yes, provided it is properly configured and adapted to where each company pays tax: chart of accounts, taxes, invoicing system (Verifactu, TicketBAI or whichever applies) and VAT books. It needs to be reviewed in every installation.

Who maintains the Spanish localization of Odoo?

The OCA (Odoo Community Association) maintains many modules of the Spanish localization, and Odoo S.A. maintains its own. At Binovo, our team also develops and maintains the tax and accounting changes for our clients and shares its work with the community.

My company pays tax under a foral tax authority. Is Odoo suitable?

Yes. We implement Odoo with TicketBAI in Gipuzkoa, Bizkaia (with Batuz and the LROE) and Álava, and we follow NaTicket in Navarre. We have clients in production in all three Basque foral tax authorities.

Are Verifactu, TicketBAI and B2B electronic invoicing the same thing?

No. Verifactu comes from the Spanish Tax Agency and TicketBAI from the Basque tax authorities: one or the other applies depending on where the company pays tax. B2B electronic invoicing is a separate obligation that is added on top of either of the two.

Is Odoo suitable if I pay tax in the Canary Islands under the IGIC?

Yes. The IGIC replaces VAT, with its own rates, form 420 and its own SII; in Odoo its taxes and fiscal positions are configured, and invoicing continues with Verifactu, as in the rest of the common tax territory.

I sell to consumers in other EU countries. Which VAT do I apply?

If you exceed €10,000 a year in this type of sales across the EU as a whole, you apply the VAT of the customer’s country, which you declare to the Spanish Tax Agency through the One-Stop Shop (OSS). In Odoo this is configured with each country’s rates and automatic fiscal positions.

What is LiburuBAI and how does it affect my Odoo?

LiburuBAI is a project of the Provincial Council of Gipuzkoa (Diputación Foral de Gipuzkoa) under which the foral tax authority automatically prepares, from TicketBAI data, a draft of the record books and of some VAT and personal income tax returns for business owners and professionals. No dates or specifications have been published yet. At Binovo we are monitoring it and will develop it for Odoo and for our TicketBAI and Verifactu API.

Does it work in Odoo Community and Enterprise?

Yes. We present both editions and you decide; in both we review and maintain the tax side.

How much does it cost?

We determine it in a conversation with you, because it depends on where you pay tax, whether you already have Odoo, your custom developments and how you invoice.

Shall we talk about the tax setup of your Odoo?

Tell us where your companies pay tax and how you invoice today, and we’ll work out what you need.

Let’s talk about your case 943 569 206

Official sources

Odoo is a trademark of Odoo S.A. Binovo is an independent company. This page is for information purposes only and does not replace tax advice.