beel_create_recurring_invoice_derivation
Creates a recurring invoice template from an existing invoice, copying its lines, recipient, series, and payment data so you only define the recurrence schedule.
Instructions
Creates a recurring invoice template of this company taking its lines, recipient, series and payment data from an existing invoice, so only the recurrence has to be described.
from_invoice_id: the source invoice. It must belong to the company in the path, and one you cannot reach is reported the same way as one that does not exist. It is not modified by this call.Recurrence:
name,day_of_monthandstart_dateare required;end_dateandfrequencyare optional. The cadence is not taken from the source invoice — a one-off invoice has none to copy — so it is described here like any other recurrence field: every 1 (MONTHLY), 3 (QUARTERLY) or 12 (YEARLY) months,MONTHLYwhen omitted. It governs the step from the first invoice onwards, not where that first one lands.VeriFactu: not inherited from the source invoice. Each generated invoice is registered with AEAT, or not, according to the company's regime when it is issued.
BeeL API endpoint: POST /v1/companies/{company_id}/recurring-invoices/derivations (reference: https://docs.beel.es)
⚠️ Read before calling:
Fiscal rules, domains simplified, taxes: beel_rules_list with domain, or resource beel://guardrails/.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"company_id": "<company_id>",
"body": "<body>"
},
"name": "beel_create_recurring_invoice_derivation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| company_id | Yes | Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed. | |
| idempotency_key | No | Optional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created. |