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.
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: trueneeds a recipient. Eitheremail_configuration.recipientscarries at least one address, or the template's customer has an email. With neither,POST,PUTandPATCHanswer422 SIN_DESTINATARIO_RESOLUBLE, where they used to answer201/200.email_configuration.recipientsandccmust be valid email addresses (since 15 September). A malformed one answers422 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 noemail_configuration.recipients, the call now depends on the customer having an email.
Endpoints
- POST|PUT|PATCH/v1/companies/{company_id}/recurring-invoices422 SIN_DESTINATARIO_RESOLUBLE when auto-send has no recipient
Where to go next
An OSS line keeps the destination country's VAT
Our OSS examples set `percentage: 0`, which drops the destination VAT from the breakdown. The API never required it. Check your `regime_key: "17"` lines.
Recurring templates say when they are failing, and which period they last invoiced
`is_failing` flags a template from its first failed run, and `last_generated_scheduled_date` gives the latest period it has already invoiced.