beel_delete_invoice_schedule
Removes an invoice schedule, returning it to a plain draft; repeat calls are idempotent and return 204 even if no schedule exists.
Instructions
Removes the scheduling of an invoice, returning it to a plain draft. Idempotent: an invoice
that is not scheduled answers 204 all the same. Unlike the PUT, it does not require the
scheduled_invoices feature.
BeeL API endpoint: DELETE /v1/companies/{company_id}/invoices/{invoice_id}/schedule (reference: https://docs.beel.es)
⚠️ Read before calling:
Fiscal rules, domains lifecycle, void, corrective: beel_rules_list with domain, or resource beel://guardrails/.
The status names, the proforma lifecycle, and which tool performs each operation. (resource: beel://guardrails/invoice-state-machine)
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>",
"invoice_id": "<invoice_id>"
},
"name": "beel_delete_invoice_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| invoice_id | Yes | Invoice ID |