B2B e-invoicing will require your Odoo to issue and receive invoices in a structured electronic format and, in addition, to report whether you reject them and when you pay them. This is the obligation under Spain’s Crea y Crece Act, and it is not the same as Verifactu or TicketBAI. At Binovo we are developing an e-invoicing module for Odoo that will be publicly available on our GitHub.
Information reviewed on 2 November 2026 using sources from the Spanish Tax Agency and the BOE (Spain’s Official State Gazette).
| Date | Who | What they must do |
|---|---|---|
| 6 October 2027 | Companies and self-employed professionals with a volume of operations above €8 million | Issue and receive e-invoices and report the status of invoices and payments |
| 6 October 2028 | All other companies and self-employed professionals | Issue and receive. Legal entities must also report the status |
| 6 October 2029 | Individuals and entities under the income attribution regime | Report the status; voluntary until that date |
The Spanish Tax Agency’s public solution must be available before 6 August 2027. We explain this in more detail in the B2B e-invoicing timeline and in the payment statuses.
| Your situation | Does it affect you? |
|---|---|
| You invoice companies or professionals established in Spain | Yes |
| You only invoice private individuals | Not for those invoices |
| You issue simplified invoices | Generally excluded |
| You file taxes in the Basque Country or Navarre | Pending agreements with the regional tax authorities (haciendas forales), not published as of 2 November 2026. See Odoo in the Basque Country and Odoo in Navarre |
If you have a specific question about your company, consult your tax advisor.
| Verifactu | B2B e-invoicing | |
|---|---|---|
| What it looks at | How your software generates invoices | How the invoice reaches your customer |
| Which invoices | Those issued by your software, including to private individuals | Those sent to companies and professionals |
| When you receive | Nothing | You must be able to receive them and report rejections and payments |
Complying with one does not mean complying with the other. You can find the full comparison table (in Spanish) on apiverifactu.es, and what it means for your Odoo in Verifactu in Odoo.
| Task | What the regulation requires | What to review now |
|---|---|---|
| Issue | Invoice in a structured format, using the European EN 16931 model | Customer tax data, invoice series, and custom templates or developments |
| Send | Through the Spanish Tax Agency’s public solution or a private platform, which sends a copy to the public solution | Which channel suits your customers and your volume |
| Receive | Supplier invoices will also arrive in electronic format | How they are currently entered into accounting and who validates them |
| Report | Communicate the rejection and the date of full payment, within a maximum of four calendar days of payment | That payments are recorded in Odoo promptly |
As with our Verifactu module, we will publish the e-invoicing module on Binovo’s GitHub. It is currently in development and there is no date yet. We will let you know here as soon as it is available.
Installing a module is not the same as being compliant: you need to check that it covers your use cases, configure it, test it and maintain it. Anyone who installs it on an Odoo instance that does not depend on Binovo is responsible for that installation.
The module is included in your maintenance plan. We will prepare it with you: we review your Odoo, your custom developments and how you invoice, and tell you what to do and when. You do not need to do anything yet; if the 2027 deadline affects you or you want to get ahead, write to us.
We publish the module so the community can use it, but we do not install it on an Odoo that has another partner. It is the same policy as with TicketBAI and Verifactu: for us to serve you, your Odoo has to be part of our system.
If you want to keep your current software, we are developing the B2B e-invoicing API (in Spanish), built on the same technology as API Verifactu.
It depends on the version, how it is configured and any custom developments it has. Binovo is developing an e-invoicing module for Odoo, which will be public on its GitHub. In the meantime, it is advisable to review your data and processes.
From 6 October 2027 for those with a volume of operations above €8 million, and from 6 October 2028 for everyone else. Individuals and entities under the income attribution regime have until 6 October 2029 to report the status of invoices.
No. Verifactu and TicketBAI look at how your software generates invoices. B2B e-invoicing regulates how you send them to another company and requires you to report their status. They are separate obligations.
The foral territories are governed by whatever is agreed with their regional tax authorities. As of 2 November 2026, we have not found those agreements published.
Yes, once it is ready it will be public on Binovo’s GitHub, like the Verifactu one. It is currently in development and there is no confirmed date. Anyone who installs it on an Odoo instance that does not depend on Binovo is responsible for that installation. We do not install it on an Odoo that has another partner.
If you are already a Binovo customer with a maintenance plan, the module is included. Otherwise, we determine it in a conversation with you, because needs differ even within the same sector and a general figure would create false expectations.
Binovo is developing a B2B e-invoicing API, built on the same technology as API Verifactu, to connect other software and online stores.
Tell us which version of Odoo you use and how you invoice, and we’ll tell you where to start.
