Skip to main content
VeriFactu

VeriFactu errors on the invoicing software: who made the program you invoice with

Every VERI*FACTU record states which program generated it: who produces it, what it is called, its version and the installation it runs on. The AEAT, the Spanish tax agency, checks that this data is complete and well formed, and it has eleven codes for the SistemaInformatico block. With our module, you do not fill in any of this yourself.

FlexigoTech · Editor in charge: Víctor Gómez · Updated 4 November 2026

Key facts

Module
VeriFactu
Versions
Odoo 17, 18, 19 and 20
Checked
in the module's source code, version 20.0 · against the sources linked at the end
Reading time
3 min

What the AEAT checks

The AEAT validation document asks this of the SistemaInformatico block:

  • The producer of the program is identified with a Spanish tax ID or with IDOtro, one of the two and never both. Never with type 07.
  • IdSistemaInformatico always has two positions, and each one is a capital letter, other than Ñ, or a digit.
  • NombreSistemaInformatico, TipoUsoPosibleSoloVerifactu and TipoUsoPosibleMultiOT are mandatory and must have content.
Card for the VeriFactu invoicing software codes
The eleven codes of the SistemaInformatico block, in amber: they reject the invoice record.

The eleven codes

CodeWhat fails
1176The producer's tax ID.
1177IdSistemaInformatico.
1179Generic error of the block.
1212TipoUsoPosibleSoloVerifactu, which only accepts N or S.
1213TipoUsoPosibleMultiOT, which only accepts N or S.
1220NombreSistemaInformatico.
1221The producer's IDType.
1223Both a tax ID and IDOtro, or neither.
1226IndicadorMultiplesOT, which only accepts N or S.
1241Error técnico al obtener el SistemaInformatico., a technical error on the AEAT side.
1242No existe el sistema informático., the invoicing software does not exist.

What our module sends

The module puts this data in every record, without you having to configure it or being able to change it from the menus:

Software name
Flexigo Verifactu.
Identifier
FV, two capital letters.
Producer
The producer's tax ID, stored in the system parameter verifactu.sif_producer_nif.
Version
The installed version of the module.
Installation number
A SHA-256 computed from the database and the company, different for each installation.
Possible uses
TipoUsoPosibleSoloVerifactu set to N, because the module also supports the No VERI*FACTU mode, and TipoUsoPosibleMultiOT set to S.

With those values the format codes should not happen. What could trigger them is a manual change to the system parameters: if someone edits verifactu.sif_producer_nif or the producer name, the block no longer adds up.

The version that travels

The version field carries the version of the module installed at each moment. When you update the module, the records generated from then on go out with the new version, and earlier ones keep theirs. In Audit Trail › Responsible Declarations you can see the system's declarations, each one with the module version it belongs to and its status.

VeriFactu responsible declarations in Odoo
The system's responsible declarations inside Odoo, with their version and status. Odoo 20 screenshot with demo data.

What to do

  1. Do not touch the system parameters starting with verifactu.sif. If someone changed them, put back their value and write to us: the records that went out with the changed value have already been sent and need to be reviewed one by one.
  2. 1241 is a technical error on the AEAT side: the queue retries on its own, with waits from 2 minutes to 12 hours, until the sixth attempt.
  3. 1242 says the AEAT cannot find the invoicing software. Send us the answer at comercial@flexigobe.com so we can review it.

The codes on this page, with the AEAT's text

Each code with its literal text, in Spanish, as the AEAT's error list gives it:

CodeAEAT text (Spanish)
1176El valor de campo NIF del bloque SistemaInformatico es incorrecto.
1177El valor de campo IdSistemaInformatico del bloque SistemaInformatico es incorrecto.
1179Error en el bloque de SistemaInformatico.
1212El campo TipoUsoPosibleSoloVerifactu solo acepta valores N o S.
1213El campo TipoUsoPosibleMultiOT solo acepta valores N o S.
1220El valor del campo NombreSistemaInformatico es incorrecto.
1221El valor del campo IDType del sistema informático es incorrecto.
1223En el bloque SistemaInformatico si se cumplimenta NIF, no deberá existir la agrupación IDOtro y viceversa, pero es obligatorio que se cumplimente uno de los dos.
1226El campo IndicadorMultiplesOT solo acepta valores N o S.
1241Error técnico al obtener el SistemaInformatico.
1242No existe el sistema informático.

Why does each installation have a different number?

Because the AEAT tells apart each installation of the same program. A new Odoo database is a new installation for the module, with its own number and its own chain of records.

Keep reading

VeriFactu chaining errors: the previous record, the hashes and their lengthsVeriFactu chaining errors (1174, 1175, 1180, 1269, 1291, 2002, 2003, 2008 and the length codes): what the AEAT checks and how Odoo chains each invoicing record.VeriFactu error 2007: the AEAT already had your invoices and receives another «first record»VeriFactu error 2007: the AEAT already has invoices from your tax ID made with the same system and gets another first record. Why, in Odoo 17 to 20.VeriFactu technical errors: when the problem is in the AEAT systemsVeriFactu technical errors on the AEAT side (4108, 4110, 4111, 4118, 4128, 3500, 3501, 1129, 1256, 1288): which ones Odoo retries on its own and which ones you resend.
Checked in the module's source code (version 20.0) and the linked sources

Sources