Invoicing software in Basque
Cairos is translated into Basque: 7,871 of the program's 7,912 sentences, and the invoices you issue. But there is something you need to know before reading on, and we would rather say it up here than in the small print.
If you invoice from Álava, Bizkaia or Gipuzkoa, this is not for you yet
Your invoicing obligation is not VeriFactu: it is TicketBAI, and it has bound you since 2022-2024 depending on the territory. Cairos does not issue TicketBAI: it does not generate the file, does not sign it, does not chain it, does not print the TBAI identifier and is not entered on the register of guarantor software of any of the three provincial councils. The program being in Basque does not change that, and we do not want you finding out after signing up. We set it out in full on the TicketBAI page.
For anyone who speaks Basque and invoices in the common territory
And there are more of them than it seems: anyone who lives and invoices outside the three foral territories, and anyone in Navarre, where neither TicketBAI nor VeriFactu is compulsory today.
- The program in Basque: menus, screens, warnings and help, at 99%
- Invoices, quotes and delivery notes in Basque, if your company chooses it
- VeriFactu included, for anyone taxed in the common territory
- And what is not: your clients' portal is still in Spanish
Almost no invoicing software is in Basque
And it is one of the few things there is no debate about: the big ones are in Spanish and, at most, in English.
| Interface | Invoices | Help | |
|---|---|---|---|
| Cairos | Yes | Yes | In Spanish |
| Large general-purpose software | Spanish and English | Spanish | In Spanish |
| International software | English and several | It depends | In English |
Checked against what their own websites advertise. If any of them has added it since, write to us and we will correct it: we would rather put it right than let the table age badly.
How much is translated into Basque, counted
With the four rows side by side, so that you can see where Basque stands against the others and exactly what it is missing.
| Language | Strings translated | What is missing |
|---|---|---|
| Catalan | 7,912 of 7,912 | Nothing. |
| Galician | 7,912 of 7,912 | Nothing. |
| English | 7,912 of 7,912 | Nothing. |
| Basque | 7,871 of 7,912 | 41 strings: terms the Administration does not translate, plus the odd paragraph on cooperative taxation. |
Counted on 4 September 2026 against the program's catalogue, not against this website. Every new ERP screen goes in first in Spanish and is translated afterwards, so the figure is counted again at each review.
An ERP made here, and in Basque for that reason
Translating a management program does not show up on any spreadsheet: it is thousands of sentences, the error messages, the help text on every field and the documents that go out to your client. For a company that runs its product from abroad, the Basque market is a small line in a report, and that line does not win the argument. For us it is not a line: it is where we live.
We do not decide this in another time zone
Cairos is nobody's subsidiary and no fund's product. We make it here, we maintain it here and we decide here what gets translated. That is why Basque came in before things that would sell more.
Properly translated, not run through a machine
Sentence by sentence, with the tax terminology reviewed. And what does not exist in Basque — terms the Administration itself does not translate — stays in Spanish deliberately, rather than our inventing a word that then fails to match the form.
And it costs no more
It is in every plan, including the free one. Charging for someone's language would strike us as mean, and making it an add-on would treat it as a feature rather than what it is.
What is translated and what is not
What gets used is translated: the menus, the screens, the buttons, the error messages, the warnings and the help text on every field. That is 7,871 sentences counted one by one, not a layer on top. And so is what leaves the program: the PDF of the invoice, the quote and the delivery note is generated in the language your company chooses, not in the language of whoever pressed the button.
What is not translated, and deliberately so: the names of the AEAT tax forms — the 303 is the 303 in any language — the codes of the official files, and the terms the Administration itself does not translate. Changing them would mean inventing a nomenclature that then fails to match what the form asks for.
And what is not translated yet, which is a different matter: on the printed invoice, the column headings — «Concepto», «Cant.», «Precio», «IVA», «Importe» — and the total written out in words are still in Spanish. So is the portal where your client looks up their invoices: the documents they download from there come out in your company's language, but the screen around them is in Spanish. We say it here and not in the small print because these are the three things your client sees.
And one more thing, particular to Basque: there are still 41 sentences in Spanish out of the program's 7,912. Most of them are terms deliberately left alone — «remesa», «capital social», «suplidos», «órgano gestor» — because we could not find a settled form on the Haciendas Forales' own sites and we would rather not invent tax terminology. An invented term on an invoice is worse than one in Spanish that everybody recognises. The rest are help paragraphs on cooperative taxation and investment income, and those are in the queue.