Bizkaia TicketBAI Setup for New Companies: Batuz, LROE-240, and the First Invoice

A Bizkaia TicketBAI setup for new companies is not complete merely because the company has been incorporated and obtained an NIF. Before issuing the first final invoice, the business needs a workable chain connecting its tax identity, electronic credentials, authorized users, registered invoicing software, and LROE-240 records.

Disclaimer: This guide provides general compliance and document-preparation information, not tax or legal advice. Confirm your company’s tax jurisdiction, transaction treatment, and current filing obligations with Hacienda Foral de Bizkaia or a qualified tax adviser.

Key takeaways

• Confirm Bizkaia jurisdiction first. A Bilbao address alone does not settle every cross-territory case. The tax domicile, actual place of management, and the company’s operations may all matter.
• Do not issue the first final invoice until the complete chain works. Check the company data, certificate, software registration, TicketBAI output, and LROE-240 result—not only the customer-facing PDF.
• An adviser’s electronic authority does not unlock every invoicing tool. Bizkaia’s free Haz tu factura application only issues invoices in the user’s own name, so an adviser invoicing for clients needs a different registered-software arrangement.
• Certified translation is secondary but sometimes decisive. It may be needed for foreign powers, director appointments, or parent-company records used to establish authority. It is not a blanket requirement for every foreign supplier invoice entered in LROE.

Who this guide is for

This guide is for newly formed companies operating under the provincial tax rules of Bizkaia, particularly S.L. and S.A. companies, foreign-owned subsidiaries, and Spanish branches that have obtained or are applying for a Bizkaia NIF but have not issued their first final invoice.

It is written for foreign founders, directors, finance employees, and local tax advisers working with Spanish or Basque records alongside English, French, German, Portuguese, Chinese, or other foreign-language corporate documents. These language combinations are examples relevant to international teams, not an official ranking of language demand in Bizkaia.

The usual file combines Modelo 036 data, an incorporation deed, the administrator’s appointment, an electronic certificate, representation records, software configuration, customer and VAT master data, and the first TicketBAI invoice with its LROE-240 status. The guide is especially useful when the company exists legally but the founder, employee, gestoría, and software provider have not agreed who will issue, sign, transmit, correct, and retain invoices.

If you are still completing incorporation, NIF, notarial, or commercial-register steps, start with the more general Bilbao foreign-founder S.L. registration guide. This page begins at the point where the company must make its invoicing system operational.

Why the first invoice is a Bizkaia-specific compliance event

Batuz is Bizkaia’s integrated tax-control framework rather than a generic Spanish invoicing label. Its practical components include TicketBAI-compliant invoicing, the electronic Libro Registro de Operaciones Económicas, and tax-return assistance based on the recorded data. Legal entities and non-resident permanent establishments use LROE model 240, while individuals and certain entities without legal personality use model 140. The official LROE portal explains this division and provides access to the two applications.

Bizkaia’s phased implementation timetable reached its final listed cohort on 1 January 2026. A newly active company should therefore not assume that incorporation creates a separate grace period. Check the company’s taxpayer type, principal activity, and any transaction-specific exemption against the current Batuz implementation schedule before the first invoice is finalized.

This is also why TicketBAI should not be treated as another name for Spain’s national Veri*Factu or B2B e-invoicing arrangements. A company subject to Bizkaia rules must configure the Bizkaia workflow that actually applies to it, even if its software also advertises compliance with national systems.

Bizkaia TicketBAI setup for new companies: the practical sequence

1. Confirm the tax identity that will appear everywhere

Reconcile the company’s NIF, registered legal name, tax address, activity start date, and IAE activity with its Modelo 036 and incorporation records. The exact legal name should then be copied consistently into the certificate request, invoicing software, customer-facing invoice, and LROE configuration.

A trading name should not silently replace the registered entity name. Foreign directors should also resolve inconsistent spacing, accents, surname order, or transliteration before those differences spread across certificates and powers of attorney.

2. Decide who will perform each action

Create a short responsibility matrix before buying software:

First-invoice responsibility matrix

Action	Possible operator	Question to settle
Issue the invoice	Director, employee, or external adviser	Whose certificate signs the TicketBAI record?
Transmit or review LROE entries	Company or registered representative	Does the operator have the necessary electronic representation?
Correct an error	Finance team or adviser	Who approves cancellation or a rectifying invoice?
Retain evidence	Company, adviser, or both	Who keeps the PDF, electronic records, receipts, and error logs?

Bizkaia distinguishes legal representation, voluntary representation, enabled professional representation, and internal company authorization. The official electronic representation guidance explains how representatives and company employees are registered and accept authority. Legal and ordinary voluntary powers generally have maximum validity periods of five years, while enabled voluntary representation may run for up to seven years.

The counterintuitive point is that representation and invoice signing are related but separate. A gestoría may be authorized to submit tax information without automatically being able to use every invoicing interface in the company’s name.

3. Obtain the appropriate electronic credential

The right credential depends on the operating model. A director acting for the company may use an entity-representative certificate. An authorized employee may access permitted company procedures with an accepted personal identification method after the company creates and the employee accepts the authorization. Some automated systems use a device certificate, with additional registration and configuration requirements.

Do not choose a certificate solely because it permits login. Confirm that it supports the intended TicketBAI signature architecture and the LROE action being performed. Build renewal dates and authority-expiry dates into the compliance calendar so a certificate does not fail on the day a customer expects an invoice.

4. Choose a registered software workflow

Commercial claims such as “Spanish-compliant invoicing” are insufficient. Search the official Registro de Software Garante TicketBAI for the product and developer. Match the registered product name to the edition or module being sold to the company.

Ask the provider to demonstrate five things:

1. How the company and certificate are linked.
2. How invoice series and sequential numbering are controlled.
3. How the TicketBAI record and QR are generated.
4. How the LROE-240 submission or synchronization is checked.
5. How errors, cancellations, rectifying invoices, and exports are handled.

Bizkaia permits more than one compliant software arrangement, and a company may use separate tools for TicketBAI invoices and other LROE chapters. That flexibility is useful, but it creates an ownership problem unless one person is responsible for reconciliation.

5. Understand the free-tool limitation before assigning work

The Diputación Foral de Bizkaia offers Haz tu factura, a free application that creates invoices containing the TicketBAI identifier and QR. Invoices produced through it are recorded automatically in the user’s LROE. However, the official Haz tu factura page states that it only issues invoices in the user’s own name; it cannot be used to issue an invoice on behalf of a third party.

For a founder-managed company with simple invoicing, the free application may be enough. If an external adviser will issue invoices for several client companies, the adviser needs an appropriate registered-software and certificate arrangement. Do not wait until the first billing date to discover this distinction.

6. Configure the first-invoice data

Before generating anything final, check:

• Registered name, NIF, and tax address;
• Invoice series, numbering, and date controls;
• Customer identification, including foreign customer fields;
• Description of goods or services;
• VAT rate, exemption, or reverse-charge treatment confirmed by a tax adviser;
• Currency, totals, payment terms, and bank details;
• Certificate selected for signing;
• Responsibility for reviewing the resulting LROE-240 entry.

A pro forma invoice may be used while commercial terms are being agreed, but it should be clearly marked as non-final and should not be presented as the completed TicketBAI invoice. Once the taxable transaction requires a final invoice, issue it through the compliant workflow.

7. Run a go/no-go acceptance check

Use a controlled first transaction or an approved test environment where available. The company should be able to answer “yes” to every item below before treating the setup as live:

• Can the intended operator sign in with the correct identity?
• Does the software display the correct entity and NIF?
• Is the precise product listed in the official software register?
• Does the final invoice contain the expected TicketBAI identifier and QR?
• Can the team confirm the corresponding LROE-240 status?
• Is there a named owner for warnings or rejected annotations?
• Can the company retrieve its final invoice and supporting audit record?
• Does the team know when to cancel and when to issue a rectifying invoice?

Generating an attractive PDF is not the same as completing this acceptance check. The company must inspect the tax-side result and preserve evidence of what happened.

What must go into LROE-240 after the first invoice?

LROE-240 covers more than issued TicketBAI invoices. A legal entity may also need to record received invoices, expenses, and other operations with tax significance. TicketBAI data generated through a compatible workflow may enter the relevant issued-invoice chapter automatically, but that does not remove the need to maintain received-invoice and other applicable chapters.

Deadlines depend on the taxpayer and operation. Do not turn a general quarterly bookkeeping habit into a universal legal deadline. Configure the calendar with the company’s adviser, ensure entries are made before the relevant VAT return where required, and check the current LROE instructions whenever the taxpayer changes to monthly reporting or another special regime.

When foreign documents and certified translation matter

Translation is usually a supporting part of this setup, not the invoicing system itself. A foreign supplier invoice does not automatically require a certified translation merely because its data must be reflected in LROE. Keep the original, enter the required tax data accurately, and be prepared to provide a translation if Hacienda later requests one as evidence.

Translation becomes more important when a foreign document establishes who may act for the company. Examples include a foreign parent-company extract, board resolution, administrator appointment, or power of attorney. The receiving authority may require authentication, a Spanish translation, or a Spanish traducción jurada, depending on the document and procedure.

“Certified translation” is therefore a bridge term for international founders. It is not automatically identical to a Spanish sworn translation signed and sealed by an appropriately authorized translator. The Ministry’s sworn-translation and Ministry directory page explains the official status of sworn translators and interpreters. Confirm the required format before ordering, and avoid assuming that notarization, apostille, and translation perform the same function. For the general distinction, use CertOf’s concise guide to certified versus notarized translation.

For a useful authority-document translation packet, provide:

• Every page of the source document, including seals and apostille pages;
• The spelling of company and director names used in Spanish records;
• The intended recipient and procedure;
• Any deadline for the certificate or representation setup;
• Instructions about digital delivery, signed originals, and revisions.

CertOf can help translate and format corporate records, powers, and supporting documents, but it is not a gestoría, tax adviser, TicketBAI software provider, or representative before Hacienda. You can review who signs a CertOf certification and how CertOf measures translation quality and consistency before deciding whether the receiving authority instead requires a Spanish sworn translator.

Local service and software ecosystem

Compare providers by role and verifiable capability, not broad marketing claims or generic star ratings. Prices and implementation times vary with language, certificate status, transaction volume, and integrations.

Private providers

Private providers relevant to first-invoice preparation in Bizkaia

Provider or provider type	Public local signal	Useful for	Boundary to verify
LinguaVox	Publishes an address at Máximo García Garrido 12, 1 D, 48980 Santurtzi, and telephone 944 936 508	Professional, legal, and sworn translations delivered across Bizkaia	Confirm the actual signing translator, authorized language pair, delivery format, and whether the recipient requires a sworn translation
MAEC-listed sworn translator	Individual professional status and authorized language pair should be checked through the Ministry’s official resource	Foreign public or corporate documents for which a Spanish authority specifically requires traducción jurada	Verify the signer rather than relying only on an agency name
Registered TicketBAI software provider	Product and developer should appear in the Bizkaia official register	Invoice generation, signing, QR creation, and LROE transmission	Confirm the purchased edition, representation support, error monitoring, and data export
Bizkaia tax asesoría or gestoría	Local tax practice and valid electronic authority can be verified directly	Modelo 036, VAT treatment, representation, and LROE reconciliation	It may not provide software, issue invoices through Haz tu factura, or translate foreign authority documents
CertOf online document translation	Remote intake rather than a Bizkaia office	Certified translations, layout reconstruction, revisions, and multilingual corporate supporting records	Not a substitute for a Spanish sworn translator, tax adviser, or electronic representative when those roles are required

Official and free assistance

Official Bizkaia assistance channels

Resource	Contact	Use it for
Hacienda Foral de Bizkaia fiscal information	946 125 500; Monday–Friday, 08:30–19:00	Taxpayer classification, LROE questions, appointments, and tax-treatment questions
Technical assistance	946 083 566; Monday–Friday, 08:30–14:00	Electronic applications, connectivity, certificates, and software-related technical incidents
Bizkaia electronic office and representation register	Online through the Sede Electrónica	Representation, authorizations, cases, notices, and electronic submissions
TEAF de Bizkaia	Provincial economic-administrative tribunal	Challenging an appealable tax act; it is not a software help desk

The official Hacienda assistance page publishes current telephone hours, appointment access, and the province-wide office network. In-person attention is provided preferentially by appointment. Because this guide covers Bizkaia as a province, a company should use the nearest listed office rather than assuming every issue must be taken to Bilbao.

Wait time, cost, and scheduling reality

There is no useful single “TicketBAI setup time.” A company with settled tax data, an active certificate, and simple invoices may require only software configuration and testing. A foreign-owned company may wait longer if its administrator appointment, power of attorney, or company extract must first be authenticated or translated.

The official Haz tu factura application is free, but it may not fit a multi-user, high-volume, or adviser-operated workflow. Commercial cost can include the software subscription, implementation, certificate work, adviser time, data migration, and translation. Obtain an itemized proposal rather than comparing only the monthly software fee.

Avoid scheduling the first customer invoice for the same day as certificate activation or representation acceptance. Build time for identity matching, software testing, and correction. Neither CertOf nor a software seller should promise a government processing time they do not control.

Local user signals and recurring failure points

Two types of public evidence point to the same practical lesson. First, Bizkaia’s official guidance repeatedly addresses representation, the use of multiple software products, and the distinction between generating an invoice and transmitting LROE data. Second, local radio reporting on business and implementation experiences has described relatively straightforward adaptation for some simple, low-volume operations while recognizing greater difficulty where workflows are more complex. These are operational signals, not official service guarantees.

The most useful recurring problems are:

• The company bought software before deciding who would sign and issue invoices.
• The adviser had tax representation, but the selected invoicing tool did not support third-party issuance.
• The PDF looked correct, but nobody was assigned to inspect the LROE result.
• The company confused a pro forma document with the final TicketBAI invoice.
• A foreign authority document used a different company or director name from the Spanish tax record.

Use these signals to improve the acceptance checklist. Do not convert them into unsupported claims about average rejection rates, average setup costs, or which local office is fastest.

Local numbers that affect the workflow

• 1 January 2026: the final date shown in Bizkaia’s phased Batuz implementation table. This is why a new company should verify current coverage rather than rely on an old transition article.
• Models 140 and 240: the distinction prevents a legal entity from following instructions written for an individual business operator.
• Five or seven years: maximum representation periods vary by representation type, so authority expiry belongs in the compliance calendar.
• Twelve Hacienda service offices: the published province-wide network means assistance is not limited to Bilbao, although complex technical issues may still be handled centrally or online.

Verification, fraud prevention, and complaints

Three verification checks reduce the risk of paying the wrong provider or following a misleading notice:

1. Check invoicing software in the official register, including the exact developer and product name.
2. For a sworn translation, verify the actual translator and authorized language pair—not just the agency’s marketing page.
3. Check tax notices and case status inside Bizkaia’s electronic office before acting on an unexpected payment request or email.

Route problems according to their nature. Use technical support for connection or validation incidents, fiscal information for classification questions, the software provider for product defects, and the provider’s contractual complaint process for a private-service dispute.

If Hacienda issues a formal assessment or penalty, read the notice immediately. The official TEAF guidance states that an economic-administrative claim generally must be filed within one month of notification of the challenged act. Follow the remedy and deadline stated in the notice; a service complaint or technical-support request does not preserve an appeal deadline.

Frequently asked questions

Does a new Bizkaia company need TicketBAI for its first invoice?

If the company is subject to Bizkaia tax rules and falls within compulsory Batuz coverage, it should prepare to use the compliant system from its first final invoice. Confirm unusual entity types, exempt operations, and cross-territory cases before invoicing.

What is the difference between Batuz, TicketBAI, and LROE-240?

Batuz is the wider Bizkaia framework. TicketBAI governs the compliant invoicing record and invoice identifiers. LROE-240 is the electronic economic-operations book used by legal entities and non-resident permanent establishments.

Can my gestoría use Haz tu factura for my company?

Not to issue invoices on behalf of the company as a third party. The official tool only invoices in the user’s own name. An adviser-operated workflow requires suitable registered software, signing credentials, and representation for the relevant LROE actions.

Can we send a pro forma invoice before the system is ready?

A clearly identified non-final pro forma may be used for commercial discussion, but it should not be presented as the final TicketBAI invoice. Once the transaction requires a final invoice, issue it through the compliant workflow.

What should we do if LROE-240 does not accept the first invoice?

Preserve the rejection message or error code, check the company and invoice data, and determine whether the issue belongs to the software provider, certificate configuration, or Bizkaia’s technical channel. Do not simply delete the audit trail or issue an unrelated replacement. Confirm whether correction, cancellation, or a rectifying invoice is appropriate.

Where can we get official TicketBAI help in Bizkaia?

Use Hacienda’s fiscal-information line at 946 125 500 for taxpayer and tax-treatment questions. Use the technical line at 946 083 566 for electronic applications, certificates, connectivity, and software-related incidents. Check the official assistance page before calling because hours can change.

Do foreign supplier invoices need certified translation before LROE entry?

Not automatically. Record the required tax data and retain the original. Translation may become necessary if Hacienda requests understandable evidence or if the company needs the document for another Spanish legal or administrative procedure.

Does a foreign power of attorney always require traducción jurada?

No single answer covers every recipient. Ask the authority, certificate issuer, notary, or adviser whether authentication and a sworn Spanish translation are required. Translate apostille and seal pages when they form part of the document being relied upon.

What should we retain after the first invoice?

Keep the final customer copy, the TicketBAI-related electronic record available from the chosen system, LROE acceptance or error evidence, the underlying contract or order, and a record of any cancellation or rectifying invoice.

Prepare foreign corporate documents without delaying the setup

If a foreign board resolution, company extract, administrator appointment, or power of attorney is blocking the certificate or representation stage, CertOf can prepare a complete, consistently formatted translation set and support revisions. Review the practical differences between electronic, editable, and paper translation formats, or upload and order a certified translation online.

Where an original signed copy is requested, check the available hard-copy delivery options. Always confirm first whether the Bizkaia or Spanish recipient requires a MAEC-authorized traducción jurada. CertOf provides document translation and preparation support; it does not issue TicketBAI invoices, register electronic powers, submit LROE records, or act as your tax representative.