TicketBAI vs Veri*Factu: which one applies to your bar?

Search for "Spanish invoicing law" and you'll find two names that sound interchangeable: TicketBAI and Veri*Factu. They're not the same thing, they don't apply in the same places, and a POS that complies with one does not automatically comply with the other. Here's how to tell which one is your problem.

The one-sentence answer

Where your business is tax-domiciled decides everything: if you pay your business taxes to one of the three Basque foral haciendas (Álava, Bizkaia, Gipuzkoa), TicketBAI is your regime; if you pay to the state AEAT — which means the rest of Spain, including all the hospitality coasts and islands — your regime is Veri*Factu.

It's about your tax domicile, not where your customers come from or what language your menu is in.

TicketBAI, briefly

TicketBAI (often "TBAI") is the anti-fraud system of the Basque Country, created by the three foral tax authorities. Every invoice or ticket is generated as a signed, chained XML file and reported to the relevant foral hacienda — in Bizkaia it's embedded in the wider Batuz system. Receipts carry a TBAI identifier and QR code. Rollout happened earlier than the state system, in phases by province and taxpayer type, starting back in 2022.

If this is your territory, you need software specifically certified as a software garante for your province. Ask any vendor for their TicketBAI certification for Álava, Bizkaia or Gipuzkoa specifically — they are separate registrations.

Navarra is its own case: a foral territory with its own hacienda, not covered by TicketBAI. If you're domiciled there, ask your gestor what currently applies — don't assume either regime.

Veri*Factu, briefly

Veri*Factu is the state-wide equivalent under RD 1007/2023, applying to everyone who pays the AEAT: companies since 1 January 2026, autónomos from 1 July 2026. Your POS either submits every billing record to the AEAT in real time (Veri*Factu mode) or keeps cryptographically chained records ready for inspection. Receipts carry an AEAT-verifiable QR code.

The differences that matter when buying a POS

Authority: TicketBAI reports to a foral hacienda; Veri*Factu to the state AEAT. Different APIs, different certifications, different QR codes.
Maturity: TicketBAI has been live for years; Veri*Factu's deadlines are landing now, which is why so many older tills are suddenly being replaced.
Portability: if you move your tax domicile between territories — say, opening a second venue in Bilbao from an Alicante base — your fiscal software requirements change with it. Multi-territory groups should ask vendors hard questions about both.

Where brasio stands — honestly

brasio is built for the Veri*Factu regime: every ticket is submitted to the AEAT in real time and receipts carry the AEAT QR, with the deadlines and mechanics covered here. We do not currently support TicketBAI — if your bar is tax-domiciled in the Basque Country, brasio isn't the right till for you today, and we'd rather tell you that in the second paragraph than after a sales call.

For the rest of Spain — the peninsula's common territory, the Balearics and the Canaries — this is exactly what we do, every day, automatically.

Domiciled outside the foral territories and need VeriFactu sorted before July? Start a free 14-day trial — no card required.*