# A recurring template that emails its invoices needs someone to email

Saving a template with `send_automatically: true` and no recipient now answers `422 SIN_DESTINATARIO_RESOLUBLE`, and malformed recipient addresses are rejected.

Sep 17, 2026 · Breaking

A template set to email every invoice, with no address to send it to, was accepted. You found out months later, when the customer had never received an invoice. It is now rejected when you save it, on create and on every update.

Templates already stored are not touched. The check runs when a template is written.

## What breaks

- **`send_automatically: true` needs a recipient.** Either `email_configuration.recipients` carries at least one address, or the template's customer has an email. With neither, `POST`, `PUT` and `PATCH` answer `422 SIN_DESTINATARIO_RESOLUBLE`, where they used to answer `201`/`200`.
- **`email_configuration.recipients` and `cc` must be valid email addresses** (since 15 September). A malformed one answers `422 VALIDATION_ERROR`, on the three writes and when deriving a template from an invoice.

## Does this affect you?

- Grep your client for recurring-template writes that send `send_automatically: true`. If the body has no `email_configuration.recipients`, the call now depends on the customer having an email.

## Endpoints

- `POST|PUT|PATCH /v1/companies/{company_id}/recurring-invoices` — 422 SIN_DESTINATARIO_RESOLUBLE when auto-send has no recipient

## Where to go next

- [SIN_DESTINATARIO_RESOLUBLE](/errors/SIN_DESTINATARIO_RESOLUBLE)
- [Create a recurring invoice](/recurring-invoices/createCompanyRecurringInvoice)
- [Recurring invoices](/guides/recurring-invoices)

---

Full OpenAPI spec: https://docs.beel.es/api/openapi