RECURRING_STATE_TRANSITION_INVALID

When it happens

The recurring invoice cannot move from its current status to the one you asked for; for example, a COMPLETED recurrence cannot become ACTIVE again. error.details.current_status and error.details.target_status carry both.

How to fix it

Fetch the recurring invoice and check its status. To bill again after a recurrence completed, create a new one.

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.

• PUT /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/status

Example response

When this error occurs, the API answers 400 Bad Request with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/RECURRING_STATE_TRANSITION_INVALID",
  "title": "RECURRING_STATE_TRANSITION_INVALID",
  "detail": "Cannot move from ‹from› to ‹to›",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "RECURRING_STATE_TRANSITION_INVALID",
    "message": "Cannot move from ‹from› to ‹to›",
    "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:

• ‹from› — the current status.
• ‹to› — the status you asked for.

Other errors in this category

Keep exploring