TicketBAI
TicketBAI compliance for invoicing to the Basque regional tax authorities: electronic signature on every invoice, chained records, QR code and submission to the relevant administration.
Bizkaia, Gipuzkoa and Araba share the rule but not the detail: each province has its own timetable, submission format and quirks. The system applies the ones for your territory without anyone having to keep track of which version applies.
And if your company also invoices in common territory, TicketBAI coexists with Verifactu and SII in the same installation: each invoice follows the system that applies to it depending on where it is taxed, with no second program and no deciding by hand what goes to each authority.
What it requires
What software must do to comply with TicketBAI
TicketBAI is the requirement the Basque regional tax authorities place on invoicing software. As with every rule of this kind, what is regulated is not the company issuing invoices but the program used to issue them, and it comes down to four specific obligations:
- One file per invoice containing its tax data, electronically signed.
- Chaining: each file carries the fingerprint of the previous one, so deleting or altering one breaks the chain and shows from outside.
- TBAI code and QR on the invoice, letting the recipient check that it has been declared.
- Submission to the regional tax authority for the territory where tax is paid.
None of these is something you switch on or forget to switch on: they live in the invoicing engine, and every area of the platform issues through that same engine.
The three provinces
Bizkaia, Gipuzkoa and Araba share the rule, not the detail
This is the most common misunderstanding: TicketBAI is presented as a single obligation, but each provincial authority has rolled it out with its own timetable, submission format and specifics. Software that complies in one territory does not automatically comply in the other two.
The system applies the rules of the territory you are registered in and keeps the specifications current as they change, which in practice is what stops a technical obligation from becoming an internal project every time the administration publishes a new version.
If you operate in more than one province, they coexist in the same installation and each invoice follows the one that applies to it.
Alongside common territory
Invoicing inside and outside the Basque Country with one program
Many companies operating in the Basque Country also invoice in common territory, where two different systems coexist: TicketBAI for the provincial side and Verifactu (or SII, where it applies) for the rest.
Both regimes are handled in the same installation and each invoice follows the one that applies depending on where the transaction is taxed. No second program, no exporting between them, and nobody deciding by hand what goes to which authority, which is exactly where the errors that later need correcting come from.
From each invoice record you can see which system applied, whether the record was submitted, when, and what the relevant authority replied.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
What does TicketBAI require of invoicing software?
Four things: a signed file for every invoice, chaining of those files through the previous one's fingerprint, the TBAI code and QR printed on the invoice, and submission to the relevant provincial tax authority. All of it lives in the invoicing engine, not in an add-on somebody could forget to switch on.
Is it the same for Bizkaia, Gipuzkoa and Araba?
They share the rule but not the detail: each province has its own timetable, submission format and specifics. The system applies those of the territory you are registered in and keeps the specifications current as they change.
Can I also invoice in common territory?
Yes. TicketBAI coexists with Verifactu and SII in the same installation, and each invoice follows the system that applies depending on where the transaction is taxed, with no second program and no deciding by hand what goes to each authority.
How do I know an invoice was submitted correctly?
From each invoice record you can see which system applied, whether the record was submitted, when, and what the authority replied. If a submission fails it is flagged for retry rather than going unnoticed.
Accounting and finance
Invoices post themselves, AEAT tax forms are built from real data and the bank reconciles almost on its own. With Verifactu, TicketBAI and SII solved.
Verifactu
Compliance with the Spanish tax authority's Verifactu regulation: every invoice generates a signed invoicing record chained to the previous one, with its QR code and, if you choose that mode, immediate submission to the tax authority.
View moduleSII (AEAT)
Immediate Supply of Information on VAT: the record books of issued and received invoices are reported to the Spanish tax authority within the legal deadline, with no manual work.
View moduleBank Reconciliation
Connect to your banks, download transactions without anyone exporting a file, and reconcile them automatically against receipts, payments and accounting entries.
View moduleReceivables and Payables
Every instrument and due date in one place: what is left to collect, what to pay, when each falls due and what state it is in.
View moduleSEPA Remittances
Direct debit collection orders and credit transfer payment orders, generated from outstanding due dates and ready to upload to your bank.
View module