Verifactu, TicketBAI and SII: differences and which applies to you

Verifactu, TicketBAI and the SII get mixed up constantly, but they are different obligations. Knowing which applies to you avoids trouble with the tax authority and unnecessary Odoo configuration.

Verifactu (state-wide)

It's the AEAT system to guarantee the integrity, retention and immutability of invoicing records. It applies in the common territory and requires your software to chain invoices (hash), include a QR code and, in Verifactu mode, submit records to the tax authority. More in our Verifactu in Odoo guide.

TicketBAI (Basque Country)

The regional version: it applies in Álava, Bizkaia and Gipuzkoa. It generates a signed, chained file per invoice, with a QR and a TBAI identifier, and submits it to the regional tax authority. Each province has its nuances (e.g. Batuz in Bizkaia). See TicketBAI in Odoo.

SII (immediate supply)

The SII isn't about invoice integrity, but about submitting VAT record books to the AEAT in near real time (usually within 4 days). It's mandatory for large companies, businesses in REDEME and VAT groups. Details in The SII in Odoo.

Which one applies to me?

• Invoicing in the common territory? → Verifactu.
• Tax domicile in the Basque Country? → TicketBAI (instead of Verifactu).
• Large company, REDEME or VAT group? → also SII.

They're not mutually exclusive: a company can be subject to the SII and Verifactu, for example.

How they coexist in Odoo

The good news: Odoo handles all of them at the account.move level with the Spanish localization and the relevant modules. The key is to enable only what applies to you, with the right certificate and configuration, and to test in staging before issuing for real.

Conclusion

Confusing these rules leads to over- (or under-) configuring and to rejections. If your case isn't clear, we run a diagnosis and set your Odoo to comply with exactly what applies to you. Let's talk.