TicketBAI · Basque Country

Comply with your provincial tax authority without fighting your software

Cofactu signs with XAdES-BES, submits to Araba, Bizkaia or Gipuzkoa based on your territory, and generates the verification QR on every invoice. No installs, no data lock-out.

Start with TicketBAI for free Cofactu vs Anfix
XAdES-BES Provincial spec v1.2 No data lock-out
3

provincial tax authorities: Araba, Bizkaia and Gipuzkoa, sandbox + production

v1.2

common TicketBAI spec, XAdES-BES signature with your certificate

5×

retries with exponential backoff if the provincial tax authority goes down

QR

provincial verification code on every printed invoice

What Cofactu covers today

3 pillars for the 3 provincial territories

Implementation compliant with the TBAI v1.2 spec common to Araba, Bizkaia and Gipuzkoa.

Araba · Bizkaia · Gipuzkoa

Automatic submission to your provincial tax authority

When you issue an invoice, Cofactu signs it with XAdES-BES and sends it to the TBAI endpoint of the province you have configured. No installs, no re-signing, no extra buttons.

  • Sandbox + production endpoints supported for all 3 provincial tax authorities.
  • XAdES-BES electronic signature with your FNMT/Camerfirma/IZENPE certificate.
  • TBAI identifier auto-generated with CRC8 per the v1.2 spec.
  • Chained via SignatureValueFirmaFacturaAnterior — no invoice skipped.
Provincial spec v1.2

Verification QR on every invoice

Every printed invoice carries the TBAI QR with the province's URL (batuz.eus, ticketbai.araba.eus, tbai.egoitza.gipuzkoa.eus). Your customer can verify it from their phone without going through us.

  • Province-specific QR URL per current regulations.
  • PDF with QR generated instantly once the tax authority accepts it.
  • Mandatory TBAI logo on the printed invoice.
  • Full traceability: TBAI identifier ↔ invoice ↔ signed XML in R2.
Exponential backoff

Retries + proactive monitoring

If the provincial tax authority is down or returns a technical error, Cofactu retries up to 5 times with exponential backoff. If it rejects for a real reason (unauthorized NIF, duplicate invoice), you get an email with the error code and how to fix it.

  • Automatic retry queue — invoices aren't lost if the network fails.
  • Proactive email when the tax authority rejects, with a readable error code.
  • Catalog of provincial errors documented (in progress after the first pilots).
  • Audit log for every attempt — no surprises on inspection day.
Roadmap

What's live and what's coming

Honesty about scope: what already works, what's in development, and what we've deliberately left for later.

TicketBAI Araba (Álava)

Live

TBAI v1.2 submission to the Diputación Foral de Álava endpoint. Sandbox + production.

TicketBAI Bizkaia (Batuz)

Live

TBAI v1.2 submission to the Diputación Foral de Bizkaia Batuz endpoint. Sandbox + production.

TicketBAI Gipuzkoa

Live

TBAI v1.2 submission to the Diputación Foral de Gipuzkoa endpoint. Sandbox + production.

BATUZ LROE 240 (Bizkaia)

Q3 2026

Monthly Modelo 240 Libro Registro de Operaciones Económicas — an extra layer Bizkaia requires on top of TBAI. In development, arriving Q3 2026.

Hacienda Foral de Navarra

Q4 2026

Navarra's own tax authority system (doesn't use TBAI). On the roadmap for Q4 2026 — contact support if you're in Navarra to help us prioritize.

Coming from Anfix?

Your invoices don't get lost — even if the provincial tax authority goes down

Anfix is the long-standing competitor in the Basque Country, but it carries an iOS app broken since iOS 17 and documented cases of data lock-out when a contract expires. Cofactu retries on its own and your data leaves with you.

5 retries

backoff 30s → 1m → 2m → 4m → 8m if the provincial tax authority goes down

0 losses

invoice marked 'pending' and resumed once the authority is back

Free export

your data in CSV/JSON whenever you want — no lock-out

See the full Cofactu vs Anfix comparison Try free for 30 days →
Frequently asked questions

What people ask before migrating

Do I need a specific TBAI certificate, or does my FNMT one work?

Your existing FNMT representative or company certificate for Hacienda works fine. Camerfirma and IZENPE certificates work too. You upload it once in Settings → Certificate and it's reused for TBAI.

Do I need to request a TBAI license from my provincial tax authority?

Yes — each provincial tax authority assigns a license code to the software you'll use. When you sign up with Cofactu, we help you submit the request (an online form at each diputación). Once you have it, you enter it in Settings → Compliance.

Does Cofactu cover Bizkaia's BATUZ Modelo 240?

Not yet. Modelo 240 is the monthly Libro Registro that Bizkaia requires in addition to TBAI registration. It's in development, estimated to arrive Q3 2026. In the meantime, individual TBAI submission per invoice already works, and for Modelo 240 you'd need to use the provincial tool or an add-on.

I'm in Navarra — can I use Cofactu?

For general invoicing, yes, but automatic submission to the Hacienda Foral de Navarra (which has its own system, different from Basque TBAI) is on the roadmap for Q4 2026. If you're in Navarra and reach out, we'll notify you when it's ready and prioritize based on demand.

What if I sell to customers outside the Basque Country?

TicketBAI applies by the issuer's NIF, not the customer's — if your company is taxed in a provincial territory, all invoices you issue (regardless of where the customer is) must go through TBAI. Cofactu handles this automatically.

What happens if the provincial tax authority is down when I issue an invoice?

Cofactu automatically retries up to 5 times with exponential backoff (30s → 1min → 2min → 4min → 8min). If it's still down after 5 attempts, we mark the invoice as 'pending' and resume as soon as the authority is back. Your invoice is never lost.

Start with TicketBAI today

30-day free trial, no card required. Configure territory + license + certificate once and everything else is automatic.

Create a free account See pricing