Index
Who this article is for: It applies to clubs operating in the Basque Country (Álava, Bizkaia and Gipuzkoa).
What is this integration?
The TicketBAI integration lets you comply with the mandatory electronic invoicing system of the Basque Country. Each time an invoice is issued, Golfmanager signs it electronically and sends it to the corresponding foral tax authority through the intermediary service KubiBAI. The invoice is left with its signature and its QR code.
TicketBAI is the invoicing regulation of the foral tax authorities of Álava, Bizkaia and Gipuzkoa. KubiBAI is the service that acts as an intermediary between Golfmanager and the tax authority to sign and send the invoices.
What problem does it solve?
Comply with the TicketBAI regulation automatically, with no manual steps.
Signs and sends each invoice to the tax authority at the moment of issuing it.
Adds the signature and the QR to the invoice (visible in the PDF).
Maintains the mandatory chaining of the invoices.
Which systems does it connect and in which direction does the data travel?
It connects Golfmanager with KubiBAI and, through it, with the foral tax authority. The flow, step by step, is:
Golfmanager, when creating an invoice, sends the information to KubiBAI.
KubiBAI signs the invoice and forwards it to TicketBAI (the Basque tax authority).
KubiBAI returns that signature to Golfmanager.
Golfmanager includes that signature as a QR code on the invoice.
For tickets or simplified invoices, the QR is added automatically when the payment is taken at the POS. That QR serves as the unique identifier of the ticket before the Basque tax authority.
What information is exchanged?
Information | Direction | Purpose |
Invoice data (sender, recipient, lines, taxes) | Golfmanager → KubiBAI → tax authority | Sign and declare the invoice |
Signature and QR code | Tax authority → KubiBAI → Golfmanager | Store the signed invoice and show the QR |
Prerequisites (before enabling the integration)
Operate in the Basque Country and be subject to TicketBAI.
Have the KubiBAI service contracted and its keys.
Have the TicketBAI module installed, together with the invoicing module.
Know your territory (Álava, Bizkaia or Gipuzkoa) and the company's tax data.
That the company's tax ID (CIF) matches exactly the one registered in KubiBAI (same upper/lowercase, 9 characters without a hyphen).
Invoicing management permissions to configure it.
How to set it up (step by step)
The configuration has three blocks: the company data, the invoicing settings and the KubiBAI keys.
Step 1 — Company data
Settings Menu > Invoicing > Companies > TicketBAI section
Go to Settings Menu > Invoicing > Companies and open your company.
Check that the CIF is correct and matches the one in KubiBAI.
In the TicketBAI section, if the sender is a natural person or self-employed, enable "Sender is individual" (for legal entities leave it disabled).
If you are a natural person, fill in Name, Last Name 1 and Last Name 2.
If you also operate in Bizkaia, enable "Is Bizkaia" and enter the Activity epigraph TicketBAI (for golf courses it is usually
196710).Save the changes.
Step 2 — Invoicing settings
In Settings Menu > Invoicing > Settings > Invoices section, in the Company field, select your company.
Enable "Void simplified invoices when issuing a full invoice".
In Settings Menu > Invoicing > Invoice series, in the Company field, also select your company.
Save the changes.
Step 3 — KubiBAI keys and territory
In the TicketBAI configuration, enable the service and leave production mode disabled to start with tests.
Enter the KubiBAI keys (test and production) provided to you.
Indicate your territory: 01 = Álava, 02 = Bizkaia, 03 = Gipuzkoa.
Validate that invoices are signed and, when everything works, enable production mode.
⚠️ Recommendation: start in test mode with the test keys, check that invoices are signed, and enable production mode only when everything works. The keys are stored encrypted.
The configuration fields in detail
Below is an explanation of the fields involved in TicketBAI.
1) Sender is individual
• Field name: Sender is individual (Companies > TicketBAI)
• Description: Indicates whether the issuer is a natural person/self-employed rather than a company.
• Impact on the system: It changes the tax data sent (name and surnames instead of company name).
• Usage example: you enable it if the club invoices as a self-employed person.
What happens when it is used: the name and surname fields appear to be filled in.
System behavior: by default it is disabled (legal entity).
2) Is Bizkaia
• Field name: Is Bizkaia (Companies > TicketBAI, for a natural person)
• Description: Marks that the natural person operates in Bizkaia, a territory that requires additional data.
• Impact on the system: It enables the activity epigraph that is mandatory in Bizkaia.
• Usage example: you enable it if you are self-employed in Bizkaia.
What happens when it is used: the extra data Bizkaia requires is requested.
System behavior: it only applies to natural persons in that territory.
3) Name / Last Name 1 / Last Name 2
• Field name: Name, Last Name 1, Last Name 2 (natural person)
• Description: The issuer's personal data when they are a natural person.
• Impact on the system: They are sent to the tax authority as the issuer's identification.
• Usage example: you fill them in if you enabled "Sender is individual".
What happens when it is used: the invoice comes out with the correct name and surnames.
System behavior: they are only mandatory for natural persons.
4) Activity epigraph TicketBAI
• Field name: Activity epigraph TicketBAI
• Description: The economic activity code required for natural persons in Bizkaia (for golf courses it is usually 196710).
• Impact on the system: It accompanies the invoice as a mandatory tax datum in that case.
• Usage example: you enter 196710 if your tax advisor tells you so.
What happens when it is used: the invoice includes the activity epigraph.
System behavior: it is only required for a natural person in Bizkaia.
5) Company tax ID (CIF)
• Field name: CIF (in Companies and in General Settings > Center)
• Description: The issuer's tax identifier. It must match exactly the one registered in KubiBAI.
• Impact on the system: If it does not match (upper/lowercase, length), the tax authority/KubiBAI rejects the submission.
• Usage example: you check that the CIF has 9 characters, without a hyphen, the same as in KubiBAI.
What happens when it is used: the invoice is signed under the correct issuer.
System behavior: a mismatch causes errors like "id_card must match the KubiBAI control panel".
6) Company (in Invoices and in Invoice series)
• Field name: Company
• Description: Associates the invoicing and the invoice series with the company configured for TicketBAI.
• Impact on the system: It ensures invoices are issued under the correct issuer and with the TicketBAI data.
• Usage example: you select your company in Settings > Invoices and in Invoice series.
What happens when it is used: the invoices you issue are linked to that company and signed.
System behavior: if missing, invoices may not be sent correctly to TicketBAI.
7) Void simplified invoices when issuing a full invoice
• Field name: Void simplified invoices when issuing a full invoice (Settings > Invoices)
• Description: When a full invoice is later issued for a ticket (simplified invoice), it automatically voids the simplified one.
• Impact on the system: It avoids declaring the same amount twice to the tax authority.
• Usage example: you enable it so that, when converting a ticket into an invoice, the simplified one is voided on its own.
What happens when it is used: the voiding of the simplified invoice and the new full invoice are generated.
System behavior: it keeps tax consistency between ticket and invoice.
8) Enabled service / Production mode
• Field name: Enabled service and Production mode (TicketBAI configuration)
• Description: They activate the integration and switch between the test and real environments.
• Impact on the system: In test mode nothing is really declared to the tax authority; in production it is.
• Usage example: you start in test and enable production once validated.
What happens when it is used: in production, each invoice is really signed and declared.
System behavior: it uses the test or production keys depending on the mode.
9) KubiBAI keys
• Field name: KubiBAI keys (test and production; a User key and a Client key for each)
• Description: The credentials that let Golfmanager communicate with KubiBAI.
• Impact on the system: Without them, invoices cannot be signed or sent.
• Usage example: you copy them from the KubiBAI sign-up; they are stored encrypted.
What happens when it is used: they authenticate each submission to KubiBAI.
System behavior: the test or production ones are used depending on the mode.
10) Territory
• Field name: Territory ID
• Description: The foral tax authority you belong to: 01 Álava, 02 Bizkaia, 03 Gipuzkoa.
• Impact on the system: It directs the declaration to the correct tax authority and adjusts the requirements.
• Usage example: you select your club's territory.
What happens when it is used: invoices are declared in the corresponding province.
System behavior: a wrong territory causes submission errors.
ℹ️ Note: the exact names and location of some settings (keys, territory, mode) may vary depending on your version. Your implementation team and KubiBAI provide the specific values.
How it is used day to day
Once configured, you do not have to do anything special: when issuing an invoice, Golfmanager signs it and sends it to the tax authority automatically, and the invoice is left with its signature and QR (visible in the PDF).
Regular invoices: they require the customer's data and are signed.
Simplified invoices (tickets): they do not require the customer's data and are also signed (the QR is added when the payment is taken at the POS).
Internal, summary or proforma documents: they are excluded from TicketBAI.
The system also handles exemptions, withholdings (IRPF) and foreign recipients with their specific data.
⚠️ If KubiBAI does not return the signature at the moment of issuing, Golfmanager will not let you keep invoicing and will show an error notification (in the bell icon, top right). You must resolve that invoice before continuing.
Statuses, transactions and actions
Status on Ticketbai (column in the Invoices list):
Signed OK (green): the invoice was signed and sent correctly.
Pending (red): it was sent but is not yet signed (it must be resolved).
Not sent (red): it is a type that is not signed (for example, proforma or global invoice).
Ticketbai tab (in each invoice's detail): it shows the transaction information (whether it was correct or the error, with its number to identify the cause).
Send a "Pending" invoice:
Review the error in the Notifications (bell icon).
Go to the Invoices list and select the pending invoice.
Click Actions > Send to Ticketbai.
If it changes to Signed OK (green), it is validated. If it stays Pending, you must void it and create it again.
Voiding an invoice: the delete option is disabled. Use Void so the system generates a corrective invoice, which is registered automatically in KubiBAI.
Key concepts
Concept | What it is |
Signature | The electronic signature that gives the invoice validity before the tax authority |
QR code | The QR printed on the invoice, required by TicketBAI |
Chaining | Invoices must be signed in order; each links to the previous one |
Foral territory | Álava (01), Bizkaia (02) or Gipuzkoa (03) |
KubiBAI | The intermediary that signs and sends the invoices to the tax authority |
Limitations to keep in mind
Invoices are signed in order (chaining): if the previous invoice was not signed correctly, the next one cannot be signed until it is resolved.
If KubiBAI does not return the signature, you will not be able to keep invoicing until the pending invoice is resolved.
Invoices cannot be deleted: they are voided via a corrective invoice.
It depends on KubiBAI and the tax authority: if the service is unavailable, the signature may not complete at that moment.
Some documents are excluded (internal, summary, proforma).
It is specific to the Basque Country and its TicketBAI regulation.
Frequently asked questions
What is KubiBAI and why does it appear?
It is the intermediary service that signs your invoices and sends them to the foral tax authority. Golfmanager communicates with KubiBAI and KubiBAI with the tax authority.
Do I have to do anything when issuing each invoice?
No. When the invoice is issued it is signed and sent automatically and is left with its signature and QR. You will only need to step in if an invoice stays "Pending".
What do the "Signed OK", "Pending" and "Not sent" statuses mean?
Signed OK = correct; Pending = sent but not signed (it must be resolved); Not sent = it is a type that is not signed (proforma or global).
An invoice stayed in "Pending". What do I do?
Review the error in the Notifications (bell), go to the Invoices list, select the invoice and click Actions > Send to Ticketbai. If it stays Pending, void it and create it again.
Can I delete an invoice?
No. Deletion is disabled. Use Void: the system generates a corrective invoice that is registered in KubiBAI.
I get the error "tax_id_number must be 9 characters / Invalid ID card number".
Check in Customers that the Identification type and the tax ID (DNI) are correct and have 9 characters.
I get "The sender id card number must be 9 characters".
Check in General Settings > Center that the CIF is the same as in KubiBAI, with 9 characters and without a hyphen.
I get "The id_card of the sender must match the ID Card of the KubiBAI control panel".
Check in Companies that the CIF matches exactly the one in KubiBAI, including upper and lowercase.
Does the QR appear on the printed invoice?
Yes. Once signed, the invoice (and the simplified ticket) comes out with its QR and its signature, as TicketBAI requires.
What happens if the tax authority or KubiBAI are down?
The process is asynchronous: KubiBAI can keep returning to Golfmanager the signature it generates. If the signature does not arrive at the moment of issuing, Golfmanager warns you and does not let you keep invoicing until it is resolved.
I am a natural person/self-employed, does anything change?
Yes. You must enable "Sender is individual" and fill in name and surnames; in Bizkaia, also check "Is Bizkaia" and enter the epigraph (e.g. 196710).
Who do I contact for KubiBAI matters?
KubiBAI support (see "Contact and help"). For the configuration in Golfmanager, our support through the blue bubble.
Recommended best practices
Test first in test mode and validate that invoices are signed before enabling production.
Set up the territory correctly and the company data (CIF identical to the one in KubiBAI).
Resolve an unsigned invoice as soon as possible so as not to block the chaining or the invoicing.
Check that the QR and the signature appear on the invoices.
To correct, use Void (corrective invoice), never try to delete.
Contact and help
For the configuration in Golfmanager or the status of an invoice, write to us through the blue bubble in your management software.
For the service sign-up, the keys and KubiBAI control panel matters, contact KubiBAI support:
Contact person: Aingeru Escudero
Phone: +34 623 06 87 79
Email: soporte@kubibai.com