Updated: 18 November 2026
LiburuBAI is a project of the Provincial Council of Gipuzkoa that will allow the Provincial Tax Authority to automatically prepare, using the invoicing data it already receives through TicketBAI, a draft of the record books and of certain VAT and personal income tax (IRPF) returns for self-employed business owners and professionals. The project has been tendered and is under way, but there are still no go-live dates, it is not known whether it will be voluntary or mandatory, and there are no technical specifications for software vendors. In this article we separate what is known from what is not, explain how it differs from TicketBAI and Batuz, and outline what you should review now.
- What LiburuBAI is
- What we know and what we don’t
- LiburuBAI, TicketBAI and Batuz
- Who will be affected
- What you should review now
- What we are doing at Binovo
- Frequently asked questions
What LiburuBAI is
The official name of the project is “LiburuBAI, Record books of economic activities for individuals”. According to the Provincial Council of Gipuzkoa, it involves exploiting and analysing, with a big data platform, the invoicing data that arrives in real time through TicketBAI. Using this data, the Provincial Tax Authority will be able to automatically prepare a draft of the record books already required by law and of certain VAT and IRPF returns.
The Council presents it as a service to help taxpayers, with three goals: simplifying compliance with tax obligations, reducing internal accounting and tax management costs, and providing greater certainty about accounting data.
It is a fundamental change. Until now, the Gipuzkoa Tax Authority itself explains in its TicketBAI FAQ that submitting TicketBAI files does not make it possible to prepare VAT or IRPF drafts. LiburuBAI is the project that will take that step.
What we know and what we don’t
| What we know | What we still don’t know |
|---|---|
| It was tendered by IZFE, the IT company of the Provincial Council of Gipuzkoa, in May 2025 (file 2025KOES0001). | When it will be available to taxpayers. |
| The contract is listed as awarded and in progress. | Whether its use will be voluntary or mandatory. |
| It is co-financed by the ERDF Basque Country 2021-2027 programme. | Whether invoicing software will have to send or query anything new, and under what specifications. |
| It is fed by TicketBAI data and is aimed at self-employed business owners and professionals. | Which specific VAT and IRPF returns the draft will include. |
When the Council publishes anything new, we will update this article with the date and the source.
LiburuBAI, TicketBAI and Batuz
- TicketBAI is the invoicing obligation in Gipuzkoa: each invoice is signed, chained, carries a QR code and is sent to the Provincial Tax Authority. In Gipuzkoa it has been mandatory for everyone since 1 June 2023. LiburuBAI does not replace it: it builds on it.
- Batuz is the Bizkaia model. In addition to TicketBAI, it includes the register of economic transactions (LROE), which the taxpayer submits themselves, and the Bizkaia Provincial Tax Authority uses that information to prepare draft returns.
- LiburuBAI goes in a similar direction to Batuz, but with a different approach according to what has been published so far: the draft would be prepared by the Gipuzkoa Provincial Tax Authority from the TicketBAI data it already receives, without the taxpayer having to submit a separate book.
If you want the details of TicketBAI and Batuz in Odoo, you can find them in TicketBAI and Batuz in Odoo.
Who will be affected
According to the Council, the project is aimed at self-employed business owners and professionals in Gipuzkoa, that is, freelancers and professionals who pay IRPF on their economic activity. Companies do not appear in the official description of the project.
Even so, it is relevant to any software or services company that invoices with TicketBAI in Gipuzkoa: if the draft is generated from that data, the quality of what is submitted becomes even more important.
What you should review now
There is no need to wait for the specifications to get started. What you can do today:
- Make sure what you send through TicketBAI matches your accounting. Corrective invoices, cancellations, VAT rates, descriptions of transactions and customer data: any inconsistencies will carry over into the draft.
- Keep your invoicing in a single system. If you invoice from several programs, check that all of them send data to TicketBAI correctly and consistently.
- Make sure your software provider is following the project. Ask whether they have LiburuBAI in their roadmap and how they will notify you when there are updates.
- Make sure your tax advisor has it on the radar. The draft will be an aid, but responsibility for the returns remains with the taxpayer.
What we are doing at Binovo
At Binovo, we have been monitoring LiburuBAI from a regulatory standpoint since it was tendered. Two people on our team follow the accounting and tax changes from the Spanish Tax Agency, the provincial tax authorities and the BOE (Spain’s Official State Gazette), because our Odoo customers depend on this, as do our TicketBAI and API Verifactu products.
Our plan for LiburuBAI:
- For Odoo: we will develop it and roll it out to all our customers through our common codebase, with advance notice from their consultant.
- For other ERPs: we will also add it to our Binovo TicketBAI and Verifactu API (in Spanish), so that companies that do not use Odoo can connect with the Gipuzkoa Provincial Tax Authority and comply with LiburuBAI.
- Without getting ahead of what has not been published: once official specifications are available, we will develop, test and deploy. Until then, we are reviewing the quality of our customers’ TicketBAI data with them.
It is the same process we follow with TicketBAI, Batuz, Verifactu and B2B e-invoicing. We explain it in more detail in Spanish accounting and tax compliance in Odoo. If your company invoices in Gipuzkoa, you may also be interested in Odoo in Gipuzkoa.
Tell us how you invoice today and we will tell you what to review.
Frequently asked questions
What is LiburuBAI?
It is a project of the Provincial Council of Gipuzkoa that will allow the Provincial Tax Authority to automatically prepare, from the invoicing data received through TicketBAI, a draft of the record books and of certain VAT and IRPF returns for self-employed business owners and professionals.
Is LiburuBAI mandatory?
As of 18 November 2026, the Council has not published whether it will be voluntary or mandatory, nor any go-live dates.
Does it replace TicketBAI?
No. TicketBAI remains the invoicing obligation in Gipuzkoa. LiburuBAI builds on TicketBAI data to prepare books and draft returns.
Is it the same as Batuz in Bizkaia?
It is not the same, although it goes in a similar direction. In Bizkaia, Batuz includes the LROE record book, which the taxpayer submits themselves. In Gipuzkoa, based on what has been published so far, the draft would be prepared by the Provincial Tax Authority from TicketBAI data.
Do I have to change my invoicing software?
Today there are no published technical specifications for software. What is advisable is to check that what your program sends through TicketBAI is complete and matches your accounting.
What is Binovo doing about LiburuBAI?
We are monitoring it from a regulatory standpoint. We will develop it for Odoo and for our TicketBAI and Verifactu API, so that companies with other ERPs can also comply, and we will roll it out to our customers once the specifications are published.
Sources
- Provincial Council of Gipuzkoa. Tender launched for the project “LiburuBai, Record books of economic activities for individuals” (27 May 2025; accessed 18 November 2026).
- Euskadi.eus, public procurement. File 2025KOES0001: LiburuBAI (accessed 18 November 2026).
- Provincial Council of Gipuzkoa. TicketBAI frequently asked questions (accessed 18 November 2026).
- Provincial Council of Bizkaia. Batuz frequently asked questions (accessed 18 November 2026).
This article is general information and does not replace tax advice.
Transparency: this article was prepared with the help of artificial intelligence based on the sources cited and was reviewed and validated by the Binovo team before publication.
