Ticket Bai Spain’s New Invoicing and Tax Compliance System

The three regional tax authorities and the Basque government have embarked on a shared project to fight tax fraud through the implementation of TICKET BAI. This Project revolves around a set of new technical and legal obligations that will directly impact how businesses create invoices.

This initiative intends to establish more control and visibility into companies’ turnover and business activities, particularly those in the B2C sector.

What is Ticket BAI?

TicketBAI also called TBAI is the new invoice reporting model created and shared by the three Basque provincial councils (Álava, Vizcaya y Guipúzcoa) and the Basque Government.

According to the Basque Government’s Department of Economy and Taxation the TBAI’s main goal is to “guarantee the declaration of all sales operations conducted by persons or entities that perform economic activities”. Despite it being a common project Ticket BAI is adapted to each provincial council’s laws, meaning that its implementation differs depending on the provincial council tax payers must report too.

Generally, as of the compliance deadline all sales must generate a file with tax information which must be submitted to the corresponding provincial council’s tax authority. Each sale must also generate an invoice with the TBAI code and TBAI QR code based on the reported file. The invoice must also include enough information so that final clients can cross reference the invoice to ensure them of its correct issuance.

Who is Impacted by Ticket BAI?

All physical and legal persons who perform economic activities in one of the three provincial councils comprising the Basque government who are subject to the IPRF or corporate tax.

What Operations Should be Generated Under the Ticket BAI Standards?

TicketBAI affects all invoices, whether they are simple or full invoices, electronic or paper, as well as receipts issued when there is no obligation to do so.

When Will Ticket BAI Compliance Become Mandatory?

Ticket BAI is in different stages of development in each provincial council. Guipúzcoa and Vizcaya have already published technical requisites and implementation timelines. Álava has published its implementation date and will publish the regulation in 2021.

Álava

Has communicated  that it will incorporate itself to the TicketBAI system gradually. The initiative will be implemented by groups as of 2022.

• January 1st: voluntary use.
• April 1st: consultancies.
• July 1st: professional activities and pharmacies.
• December 1st: the rest of the taxpayers.

Guipúzcoa

The Provincial Treasury of Gipuzkoa started a voluntary period in 2021. In 2022 and 2023, a mandatory adhesion calendar by sector will begin:

• June 1, 2022: tax management professionals.
• August 1, 2022: professional activities.
• October 1, 2022: companies in the retail trade, hotel and lodging sector.
• March 1, 2023: construction, real estate development, transportation and recreational, cultural and personal services.
• May 1, 2023: manufacturing, wholesale trade, telecommunications, financial services and artists.

Vizcaya

The Vizcaya provincial tax agency has decided to implement the Ticket BAI on a voluntary basis as of January 1st 2022 and on a mandatory basis as of January 1st 2024. 

In Vizcaya the Ticket BAI system is part of the BATUZ project which includes other more expansive measures to curb tax fraud and to improve taxpayer compliance.

BATUZ, Tax Audit strategy

The BATUZ project is composed of three initiatives:

• TICKET BAI invoicing system.
• Economic Operations Registry Books (LROE).
• Generation of VAT, Corporate and income tax drafts.

Economic Operations Registry Books (LROE) 

The Economic Operations Registry Books – LROE are a tax declaration mechanism intended to reduce tax fraud related to companies’ economic operations.

As of January 2024, the declaration of LROEs must be conducted electronically and through the new TicketBAI invoicing system.

How Does Ticket BAI Work?

The Ticket BAI system creates a digital chain with issued invoices which are electronically signed. This method of declarations guarantees authenticity, integrity, and the non-repudiation of digital registries by impeding the deletion or manipulation of electronic invoices once they have been issued through a point of sale system (POS), personal computer, advanced vending machine, advanced scale, tablet or mobile phone.

Every time a sales operation is conducted an XML-TBAI file must be generated, signed and sent to the corresponding provincial council’s tax authority. The company must generate an invoice with the TicketBAI ID, the TBAI QR and sufficient information for the final client to prove that the invoice is correct.

One must consider the technical requisites and time limits for the issuance of information to each provincial tax authority.

Álava

Currently there has been no publication of the technical requirements. However, the provincial council’s website has stated that the TBAI files will be sent to Alava’s provincial council’s tax authority at the moment the invoice is created, meaning that the reporting will be online and in real time.

Guipúzcoa

The provincial council’s tax authority demands that the XML TicketBAI file must be sent to the administration as soon as the e-invoice is generated.

Vicaya

In Vizcaya’s provincial council’s tax authority the TBAI XML will not have to be sent issuers will be obligated to store it an send it through the Economic Operations Registry Books (LROE).

TBAI File

Format

Archivo XML

Information it must include 

• Invoice information (parties, number, date, breakdown, description)
• Electronic Signature
• TBAI Identifier: a code used to identify the invoice in the sytem and ensures the relation between an invoice and the TBAI file. It is 39 characters long.
• TBAI QR Code: bi-dimensional code that gives the recipient fiscal information   associated to the invoice in question.

Printed Format

The print format of the invoices must include the TBAI QR code with access to the QR reading web application and the TBAI identifier.

How will TICKET BAI affect the electronic invoice?

In order to be valid, electronic invoices must contain the TicketBAI ID. This ID can be in one of two standard formats: EDIFACT or FACTURA-e. If the invoice is in EDIFACT format, it must contain the FTX segment and TXD qualifier at the header level. If the invoice is in FACTURA-e format, it must contain the legal literals within the XML structure.

Compliance Requirements for the new Ticket BAI system

It will be necessary to have an invoicing software that is capable of performing the following functions:

• Generate the XML TBAI file following each provincial council’s technical specifications.
• It should be able to electronically sign the XML TBAI files.
• It will have to automatically send the files to the provincial council through the established communications systems.
• The invoices generated by the system for the final client must include a QR code (QR TBAI).

EDIWIN warranted TickeBAI software

EDICOM’s platform has been registered in the Ticket BAI warranted software list.

Meaning that it complies with the functional and technical specifications of each of the provincial councils (Guipuzcoa , Vizcaya and Álava) for the generation, issuance and delivery of the TBAIs and LROEs.

TicketBAI becomes yet another electronic invoicing and tax reporting solution that EDICOM offers in Spain. Adding itself to the SII and B2G FACE electronic invoice.

EDICOM coordinates GOVEIN2019 project (Action No: 2019-EU-IA-0046)

*The contents of this publication belong solely to EDICOM GROUP and do not necessarily reflect the opinion of the European Union.