beel_create_invoice

es.beel/mcp · Verify this server

Creates an invoice for this company. The issuer data comes from the company in the path, and the document is created as a draft unless you ask for it to be issued. - **Issuing:** `options.issue_directly` numbers and issues the invoice in the same call. Submission to the AEAT is asynchronous, so `verifactu.submission_status` comes back as `PENDING`: a 2xx means the invoice was accepted for submission, not that the AEAT has registered it. - **Document type:** `type` chooses the document. A `PROFORMA` is non-fiscal — it is born `ACTIVE`, numbered `PRO-...` from its own non-fiscal series, and ignores `issue_directly`. - **Related:** to copy an existing invoice into a new draft, use `POST …/invoices/derivations`, which carries neither `type`, nor `recipient`, nor `lines`. Endpoint: POST /v1/companies/{company_id}/invoices ⚠️ Fiscal guardrails — read before calling: - How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types) - How a line states its price, and which field combinations are rejected. (resource: beel://guardrails/invoice-lines) - What regime_key means, where it lives, and which combinations are rejected. (resource: beel://guardrails/regime-keys) - Why a name that does not match the census makes an invoice unsubmittable. (resource: beel://guardrails/nif-validation) - Why an issued invoice may never reach AEAT, and how to tell before issuing. (resource: beel://guardrails/verifactu-gates) - How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering) For the exhaustive rules and worked examples, call beel_docs_search.