Skip to main content
VeriFactu

VeriFactu technical errors: when the problem is in the AEAT systems

Some VERI*FACTU codes are not about your invoices but about the systems of the AEAT, the Spanish tax agency: a failure reading the certificate, checking powers of attorney or in its database. There is nothing to fix in the record. What matters is knowing which ones Odoo retries on its own and which ones you have to resend.

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

Two groups handled differently

The ten codes on this page start with «Error técnico», technical error, or «Error técnico de base de datos», database technical error, but the AEAT list splits them into two sections. And the module treats them according to their section:

CodeAEAT textWhat Odoo does
4108Error técnico al obtener el certificado.Failed, no automatic retry.
4110Error técnico al comprobar los apoderamientos.Failed, no automatic retry.
4111Error técnico al crear el trámite.Failed, no automatic retry.
4118Error técnico: la dirección no se corresponde con el fichero de entrada.Failed, no automatic retry.
4128Error técnico en la recuperación del valor del Gestor de Tablas.Failed, no automatic retry.
3500Error técnico de base de datos: error en la integridad de la información.Failed, no automatic retry.
3501Error técnico de base de datos.Failed, no automatic retry.
1129Error técnico al obtener el acuerdo de facturación.Automatic retry.
1256Error técnico al obtener el límite de la fecha de expedición.Automatic retry.
1288Error técnico en la validación de la fecha de expedición/operación.Automatic retry.
Card for the AEAT technical errors in VeriFactu
In red, the technical errors that reject the whole request; in amber, those that only reject one record and that the queue retries.

Why some are retried and others are not

The first seven are in the section that rejects the whole submission, and the AEAT returns them as a SOAP fault. The module treats that answer as final: it leaves the submission in Failed and does not repeat it, because repeating a fully rejected request usually gets the same answer. Here, though, the fault is the AEAT's, and after a while the very same submission may get through without changing anything.

The last three reject a single record. The queue retries those on its own, with waits from 2 minutes to 12 hours, until the sixth attempt. For a passing technical fault, that is exactly what is needed.

AEAT submission queue grouped by status
The queue grouped by status: Retrying holds what the queue will repeat on its own, and Failed what you have to resend yourself. Odoo 20 screenshot with demo data; the AEAT answers are simulated.

What to do

  1. With one of the first seven, wait a little and resend from AEAT Submission › AEAT Errors with Retry Selected. The submissions go back to the queue, which runs every 1 minute.
  2. With 1129, 1256 or 1288, let the queue work. If it reaches Dead Letter, resend it the same way.
  3. With 4118, which mentions the address, also check that the company's AEAT Endpoint URL field is empty, unless we gave you an address. When that field is empty, the module uses the standard address of each environment.

How do I find out if I am not watching the queue?

The module's daily compliance digest counts, per company, the pending submissions, the failed ones and those in Dead Letter. It goes out by email if a recipient is set up and, by default, only when a company is amber or red.

If a technical error keeps repeating for hours with all your submissions, write to comercial@flexigobe.com with the answer: the problem may not be a passing one. A technical error that persists across every company and every invoice is worth reporting, because nothing in your data will make it go away.

Keep reading

VeriFactu error 4134: «Servicio no activo», what happens to your invoices and how to resend themWhat VeriFactu error 4134 from the Spanish tax agency means, why it rejects the whole submission and how to resend your invoices from Odoo 17, 18, 19 and 20.VeriFactu errors with the submission format: unreadable XML, UTF-8 and empty requestsVeriFactu errors on the submission format (4103, 4119, 4135 to 4138, 1100, 1251): unreadable XML, UTF-8, GET or empty requests, and how Odoo sends each submission.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.
Checked in the module's source code (version 20.0) and the linked sources

Sources