Skip to main content

Overview of the TicketBAI Integration

Vetera provides an integration with the TicketBAI system used in the Spanish market. TicketBAI is an invoice reporting system developed by...

Vetera provides an integration with the TicketBAI system used in the Spanish market.

TicketBAI is an invoice reporting system developed by the Basque administration. The Provincial Treasury controls the billing of all businesses, and the Spanish Tax Administration (STA) requires all companies based in the Basque Country to communicate their invoices and receipts through the TicketBAI system to ensure a direct connection with the autonomous public administrations. The purpose of the system is to eliminate tax evasion and fraud.

When using the TicketBAI integration with Vetera, invoices generated by Vetera are reported to the Spanish Tax Administration and QR codes are shown on valid invoices.

Requirements for Invoice Prefixes

The following invoice types must have different prefixes in Vetera:

  • Regular invoices

  • Credit notes

  • Simplified invoices (invoices without a client)

  • Simplified credit notes (credit notes without a client)

Invoice Process with the TicketBAI Integration

1. User finalises an invoice in Vetera.

When a user creates a draft consultation or counter sale invoice in Vetera and finalises it, Vetera pre-finalises the invoice and sends it to TicketBAI. When an invoice is in the pre-finalised state in Vetera, users cannot edit the invoice in any way.

2. TicketBAI validates the invoice data.

TicketBAI validates the following invoice data:

  • Invoice parties (seller/sender and buyer/receiver). The receiver may be missing in certain cases, for example, from a simplified invoice. Name, address, and fiscal identification number (NIF in Spain) are required.

  • Invoice number and date

  • Invoice rows (unit price, quantity, discount, and the amount including VAT)

  • Tax breakdown

  • Description (can be anything, for example, "consultation" or "counter sale")

  • Flag to identify the invoice type, for example, if it is a simplified invoice. The one to be used depends on the business and the legal matter.

    • 01 "Regimen general"

    • 02 "Exportation"

    • 51 "Equivalence surcharge"

3. VeteraCloud finalises the invoice and TicketBAI reports the invoice to STA.

If the invoice data is valid:

  1. TBAI reports the invoice to STA.

  2. Vetera finalises the invoice and generates a QR code.

If the invoice data is not valid:

  1. Vetera shows an error message on the invoice page.

  2. User edits the invoice and finalises the invoice again.

  3. TicketBAI validates the invoice data again.

Did this answer your question?