TicketBAI: what it is, who it applies to and how it works
TicketBAI is the system of the foral treasuries of Álava, Bizkaia and Gipuzkoa that requires invoices to be issued with guarantor software, which signs them, adds a TicketBAI code and a QR and sends the information to the foral treasury. It is in force in all three territories (in Bizkaia, as part of Batuz, together with the LROE) and replaces Verifactu there; being in the SII (Immediate Supply of Information) does not exempt you from it.
TicketBAI deadlines by territory
The roll-out is complete in all three territories.
| Who | Date | Status | Rule |
|---|---|---|---|
| TicketBAI in Gipuzkoa: foral taxpayers Phased by activity from 1 July 2022. | Since 1 Jun 2023 | In force | NF 3/2020 · DF 32/2020 |
| TicketBAI in Álava: foral taxpayers Phased from 1 April 2022; all other taxpayers since 1 December 2022. | Since 1 Dec 2022 | In force | NF 13/2021 y DF 48/2021 · FAQ 1.9 · calendario |
| Batuz in Bizkaia (TicketBAI and LROE): companies that are not SMEs | 1 Jan 2024 | In force | NF 8/2023 · Batuz |
| Batuz in Bizkaia (TicketBAI and LROE): SMEs, self-employed and everyone else In four windows: 1 Jul 2024, 1 Jan 2025, 1 Jul 2025 and 1 Jan 2026; roll-out complete. | Until 1 Jan 2026 | In force | NF 8/2023 · Batuz |
This is not advice: each taxpayer determines what applies to them with their adviser.
What TicketBAI is and how it works
TicketBAI (also shortened to TBAI) is the common system the three Basque foral treasuries use to control invoicing: each invoice is issued with guarantor software and sent to the foral treasury. In those territories it plays the role that Verifactu plays in common territory, with its own rules in each territory.
The TicketBAI invoice
A TicketBAI invoice carries the TicketBAI identification code and a QR. With them, the recipient can look it up on their foral treasury’s website: TicketBAI invoice lookup in Álava and TicketBAI invoice lookup in Gipuzkoa, and check your invoice in Bizkaia.
Guarantor software
Guarantor software (software garante) is invoicing software registered with the foral treasury because it meets the TicketBAI requirements. Each treasury publishes its list.
Signature, chaining and TicketBAI code
For every invoice, the guarantor software generates a TicketBAI file and signs it electronically. The file’s «HuellaTBAI» block chains it to the previous invoice through that invoice’s signature. The invoice carries the TicketBAI identifier (NIF, date, the first 13 characters of the signature and a check code) and the QR code. Unlike Verifactu, TicketBAI has no mode without submission: every file is sent to the foral treasury (Gipuzkoa, Álava, Bizkaia). Technical details are in the TicketBAI API documentation.
Who TicketBAI applies to under the foral rules
| Criterion | What the rules say |
|---|---|
| Taxpayers | Anyone carrying on an economic activity who pays Corporate Income Tax, Non-Resident Income Tax through a permanent establishment or Personal Income Tax (including income-attribution entities) to the foral treasury of Álava, Bizkaia or Gipuzkoa. |
| Exclusions | Each territory sets its own. Álava excludes, among others, people who were 60 or older on 31 December 2021 and met the conditions of Urgent Tax Regulatory Decree 9/2022 (FAQ 3.1); Bizkaia has no age-based exemption but does allow one, with conditions, for income of up to €2,000 a year (Batuz). |
| Territory | It is decided by the competent tax territory under the Economic Agreement (Concierto Económico), not just by where the head office is. |
| SII | Being in the SII does not exempt you from TicketBAI: none of the three territories provides for that exclusion. |
| Outside | Common territory, where Verifactu applies, and Navarre, which is preparing NaTicket, announced with no rule published. |
This is not advice: each taxpayer determines what applies to them with their adviser.
TicketBAI in each territory
TicketBAI requirements
What TicketBAI requires from invoicing software:
- Being guarantor software, registered with the foral treasury.
- Generating a TicketBAI file per invoice and signing it electronically.
- Chaining each invoice to the previous one through the hash.
- Printing the TicketBAI code and the QR on the invoice.
- Sending the information to the foral treasury. In Bizkaia, it goes to the Batuz LROE.
TicketBAI penalties
Each foral treasury sets its penalty regime in its own rules: Foral Rule 3/2020 in Gipuzkoa, article 118 of the Personal Income Tax Foral Rule and article 133 of the Corporate Income Tax Foral Rule in Bizkaia (Batuz) and Foral Rule 13/2021 in Álava.
TicketBAI regulations
| Rule | Territory | What it regulates | Link |
|---|---|---|---|
| Foral Rule 3/2020 | Gipuzkoa | TicketBAI obligation and penalty regime | NF 3/2020 |
| Foral Decree 32/2020 | Gipuzkoa | Implementing regulation and roll-out timetable | DF 32/2020 |
| Foral Rule 5/2020 and Foral Decree 82/2020 | Bizkaia | Batuz: TicketBAI and LROE | NF 5/2020 and DF 82/2020 |
| Foral Rule 8/2023 | Bizkaia | Definitive Batuz roll-out and timetable | NF 8/2023 |
| Foral Rule 13/2021 and Foral Decree 48/2021 | Álava | TicketBAI obligation and implementing regulation | DF 48/2021 (BOTHA) |
Free foral treasury apps vs an API
| Free foral app | TicketBAI API | |
|---|---|---|
| Which one | FakturAraba (Álava), Haz tu factura (Bizkaia) and FakturaBAI (Gipuzkoa) | TicketBAI API |
| Who it is for | People who invoice without their own software | In-house software and invoicing software vendors |
| Connection with your software | No: it is used on each treasury’s website, with electronic ID | Built into your software |
| Volume and several NIFs | Each invoice is typed into the app | Multi-NIF, with the NIF management API |
| Prior validation | Check with your foral treasury | Each invoice is validated before it is sent and any error comes back with a code |
| Submission to the treasury | From the app itself | Yes, automatically, to each NIF’s foral treasury |
| Cost | Free | From €14.99 a month per NIF active in production, excluding VAT: the same price as Verifactu. Pricing |
Each treasury’s TicketBAI site: Álava, Bizkaia (Batuz) and Gipuzkoa.
Comply with TicketBAI from your software, through an API
The TicketBAI API receives the invoice as JSON, returns the QR and the TicketBAI code and sends it to each NIF’s foral treasury. Verifacti is guarantor software in Álava, Bizkaia and Gipuzkoa, so your software does not need to register.
The free account includes a TicketBAI test environment, and NIF management is the same as for Verifactu.
Built for developers
Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.
Typical integration: one to three developer daysSpecialists in Spain
Common and foral territory: Verifactu, TicketBAI and SII with one provider.
TicketBAI guarantor software in Álava, Bizkaia and GipuzkoaProven reliability
Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.
AEAT social collaboratorTicketBAI, Verifactu, SII and e-invoicing
| Rule | Relation to TicketBAI |
|---|---|
| Verifactu | TicketBAI replaces Verifactu in Álava, Bizkaia and Gipuzkoa. Verifactu in the Basque Country. |
| SII | The SII does not exempt you from TicketBAI. |
| B2B e-invoicing | B2B e-invoicing adds to TicketBAI, in the Basque Country too. |
| NaTicket | Navarre has no TicketBAI: it is preparing NaTicket, announced with no rule published. |
Questions about TicketBAI
Is TicketBAI mandatory throughout Spain?
If I am in the SII, do I have to comply with TicketBAI?
Are TicketBAI and Verifactu the same thing?
What is TicketBAI guarantor software?
Does TicketBAI use an electronic signature?
Building TicketBAI into your software?
Try the TicketBAI API with the free account: it includes a TicketBAI test environment.