Amending an invoicing record in Verifactu: example

An amendment (subsanación) is done with /verifactu/modify and the rechazo_previo field (N, X or S), and only for changes with no tax effect.

FieldValue
APIVerifactu API
Invoice type or key/verifactu/modify · rechazo_previo
Endpoint/verifactu/create · /verifactu/modify
When to use itChanges with no tax effect to a record already sent.

What changes in this case

The Verifactu API contains the endpoint /verifactu/modify which corresponds to the operation that the administration calls “amendment” of an invoicing record.

The cases in which this endpoint can be used are very limited, so it should be considered an extraordinary operation. It is very rare to find yourself in a situation where you need to (or can) perform this operation. Despite what the name might suggest, this has nothing to do with corrective invoices.

This endpoint can only be used to amend invoicing records in those cases where the amendment has no fiscal impact, which greatly limits its use.

Below we include the three examples in which this endpoint can be used, controlled by the field rechazo_previo, which make it clear that this is not something that will be done on a regular basis.

JSON requests

Amendment of an accepted record

Suppose we send the following invoicing record, which we will call Record A, and it has been correctly accepted by the Tax Agency:

Descripcion inicial
{
  "serie": "Ejemplos",
  "numero": "1",
  "fecha_expedicion": "19-11-2026",
  "tipo_factura": "F1",
  "nif": "A15022510",
  "nombre": "Nombre destinatario",
  "descripcion": "Descripcion inicial",
  "lineas": [
    {
      "base_imponible": "200",
      "tipo_impositivo": "21",
      "cuota_repercutida": "42"
    }
  ],
  "importe_total": "242"
}

If we now wanted to modify, for example, the amount, we would need to issue a corrective invoice, as explained in other examples. However, if we wanted to change the descripcion field of the invoice, then a new invoicing record can be sent to the endpoint /verifactu/modify setting the field rechazo_previo=N since the original invoicing record was not rejected. Therefore, the JSON for the amendment record, which we will call Record B, would be as follows:

Descripcion modificada
{
  "rechazo_previo": "N",
  "serie": "Ejemplos",
  "numero": "1",
  "fecha_expedicion": "19-11-2026",
  "tipo_factura": "F1",
  "nif": "A15022510",
  "nombre": "Nombre destinatario",
  "descripcion": "Descripcion modificada",
  "lineas": [
    {
      "base_imponible": "200",
      "tipo_impositivo": "21",
      "cuota_repercutida": "42"
    }
  ],
  "importe_total": "242"
}

Amendment of a rejected record

Suppose now that the initial invoice from the previous paragraph (Record A) had been rejected by the AEAT because the certificate used to send it was not valid. In that case, the invoicing record would be rejected and a new amendment record would need to be generated by setting the field rechazo_previo=X.

Descripcion inicial
{
  "rechazo_previo": "X",
  "serie": "Ejemplos",
  "numero": "1",
  "fecha_expedicion": "19-11-2026",
  "tipo_factura": "F1",
  "nif": "A15022510",
  "nombre": "Nombre destinatario",
  "descripcion": "Descripcion inicial",
  "lineas": [
    {
      "base_imponible": "200",
      "tipo_impositivo": "21",
      "cuota_repercutida": "42"
    }
  ],
  "importe_total": "242"
}

Amendment of a rejected amendment record

Suppose now that the initial invoice from the previous paragraph (Record A) had been accepted correctly and, instead, the subsequent amendment record (Record B) had been rejected. In that case, we should generate and send a new amendment record, setting the field rechazo_previo=S.

Descripcion modificada
{
  "rechazo_previo": "S",
  "serie": "Ejemplos",
  "numero": "1",
  "fecha_expedicion": "19-11-2026",
  "tipo_factura": "F1",
  "nif": "A15022510",
  "nombre": "Nombre destinatario",
  "descripcion": "Descripcion modificada",
  "lineas": [
    {
      "base_imponible": "200",
      "tipo_impositivo": "21",
      "cuota_repercutida": "42"
    }
  ],
  "importe_total": "242"
}

As can be seen, due to the limitation that amendments must have no fiscal impact, the amendment endpoint /verifactu/modify has very few use cases.

Try this case in the test environment

Create your free account, copy the request and send it with the test API key of your test NIF.

Test environment and test NIF includedRead the documentation