verifactu_not_eligible
The invoice cannot be registered with AEAT right now: the company is not on VeriFactu mode, it has no active certificate, or the certificate is revoked or issued for a different tax id. When issuing or annulling, the same code with the subcode `signing_certificate_unavailable` means the company, with VeriFactu enabled in NO VERI*FACTU mode, has nothing to sign the record with (`error.param`: `certificate`, `representation` or `system_certificate`, depending on what is missing), and with other `error.param` values that a field of the invoice does not fit the alta record (read `error.param` and `error.message`).
| Code | Type | HTTP | Category |
|---|---|---|---|
verifactu_not_eligible | invalid_request_error | 422 | VeriFactu |
Cause
The invoice cannot be registered with AEAT right now: the company is not on VeriFactu mode, it has no active certificate, or the certificate is revoked or issued for a different tax id. When issuing or annulling, the same code with the subcode signing_certificate_unavailable means the company, with VeriFactu enabled in NO VERI*FACTU mode, has nothing to sign the record with (error.param: certificate, representation or system_certificate, depending on what is missing), and with other error.param values that a field of the invoice does not fit the alta record (read error.param and error.message).
What to do
Activate VeriFactu mode and upload a valid FNMT certificate matching the company tax id; records deferred for this reason are re-queued as soon as a valid certificate is in place. If it arrives with the subcode signing_certificate_unavailable, upload a current certificate and repeat the same call: the invoice stays as it was.