CORRECTIVE_TOTAL_ALREADY_EXISTS

When it happens

The original invoice already has a TOTAL corrective, which replaces it whole, so it admits no other. The message names it.

How to fix it

Nothing is left to correct on that invoice: the TOTAL corrective already replaced it whole.

Retry

Do not retry. The outcome is final: sending the same request again gets the same answer.

Returned by

The operations where this code is most likely. The list is not exhaustive.

• POST /v1/companies/{company_id}/invoices/{invoice_id}/corrective

Example response

When this error occurs, the API answers 422 Unprocessable Content with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/CORRECTIVE_TOTAL_ALREADY_EXISTS",
  "title": "CORRECTIVE_TOTAL_ALREADY_EXISTS",
  "detail": "This invoice already has a full corrective invoice (‹corrective›): it does not admit another one.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CORRECTIVE_TOTAL_ALREADY_EXISTS",
    "message": "This invoice already has a full corrective invoice (‹corrective›): it does not admit another one.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Placeholders are filled in at runtime:

• ‹corrective› — the number of the existing TOTAL corrective.

Other errors in this category

Keep exploring