record_not_rejected
Only an alta record that AEAT accepted (or accepted with errors) or rejected can be subsanado. This record is in another state — pending remission, submitted with no answer yet or in technical error — which the retry covers, not the subsanación.
| Code | Type | HTTP | Category |
|---|---|---|---|
record_not_rejected | invalid_request_error | 422 | VeriFactu |
Cause
Only an alta record that AEAT accepted (or accepted with errors) or rejected can be subsanado. This record is in another state — pending remission, submitted with no answer yet or in technical error — which the retry covers, not the subsanación.
What to do
If the failure was technical, retry the transmission (POST /v1/companies/{company}/verifactu/records/{id}/retry, or retry-blocked if it is blocked) and wait for AEAT's answer; only then, if data has to be corrected, subsanar. can_subsanar on the record tells you when it is admitted.