Skip to main content
VeriFactu

VeriFactu errors 4105, 4117, 4123 and 4124: when your tax adviser submits for you

If your tax adviser («asesoría») is the one sending the records to the AEAT, the Spanish tax agency, each submission carries a Representante block in its header with the adviser's tax ID and name. The AEAT checks both against its census. These four codes are the rejections of that block, and since it sits in the header, any of them brings down the whole request.

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

The four codes

CodeWhat the AEAT says, in SpanishData that fails
4105Error en la cabecera: el valor del campo NIF del bloque Representante no está identificado.The adviser's tax ID
4117Error en la cabecera: el campo NIF del bloque Representante tiene un formato incorrecto.The format of that tax ID
4123Error en la cabecera: el valor del campo NIF del bloque Representante no está identificado en el censo de la AEAT.The census
4124Error en la cabecera: el valor del campo Nombre del bloque Representante no está identificado en el censo de la AEAT.The adviser's name

The AEAT validation document sums it up in one line: the tax ID of the obliged party's representative or adviser has to be identified at the AEAT. All four sit in the section of the list that rejects the whole submission.

Card for the VeriFactu Representante codes
The four codes of the Representante block, in red: being in the header, they reject the entire request.

When Odoo sends a Representante

The module only adds the Representante block if the company has the Asesoría NIF field filled in. If it is empty, the header carries only the party obliged to issue, and these codes cannot appear. When it is filled in, the block is built like this:

  • Tax ID: the Asesoría NIF value, without spaces, in capitals and without the ES prefix if it has one.
  • Name: the Asesoría Name value. If that field is empty, the module puts the tax ID itself as the name.

That last detail explains many 4124 answers. The AEAT compares the name with the one it holds in its census for that tax ID, and a tax ID used as a name matches none. Filling Asesoría Name with the adviser's exact legal name solves it.

The certificate counts too

To connect to the AEAT, the module uses the company's active certificate in Odoo. If the adviser submits, that certificate has to allow them to submit on your behalf, and the AEAT checks it before anything else: with no certificate, its service redirects to the error page erro4033, and if it does not recognise it, to erro4011. Who may hold the certificate is explained in error 4112.

VeriFactu certificates in Odoo, one active and one inactive
The company's list of certificates: only one is active, and that is the one presented to the AEAT. Odoo 20 screenshot with test certificates.

How to fix it

  1. Check Asesoría NIF and Asesoría Name on the company. The name exactly as it appears in the AEAT census.
  2. Check that the active certificate is the one that should be presenting these records.
  3. Resend from AEAT Submission › AEAT Errors with Retry Selected. The header is rebuilt on every submission from the company data at that moment, so the resend already goes out corrected.

What if the adviser stops submitting for us?

Empty Asesoría NIF and Asesoría Name. From the next submission the header will go without a Representante, and the company will need its own active certificate.

These rejections leave submissions in Failed and they are not retried on their own: until you resend them, they do not go out. If the code persists after fixing the data, write to comercial@flexigobe.com.

Keep reading

VeriFactu error 4112: the certificate you connect with cannot submit those invoicesVeriFactu error 4112: the certificate holder is not the obliged party, a social collaborator, an attorney or a successor. How to check it in Odoo 17, 18, 19 and 20.VeriFactu errors with your company tax ID: 4104, 4107, 4109, 4115, 4116 and the IDEmisorFactura familyVeriFactu errors on the issuer tax ID (4104, 4107, 4109, 4115, 4116, 1108, 1215…): what the AEAT checks, which Odoo field it comes from and how to resend the submission.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