Send an e-invoice
Issues a maventa_einvoice draft and transmits it over the e-invoice network: allocates the invoice number, stores the invoice, books the sale when LAC keeps the ledger, and queues the Finvoice send. For a partner-profile draft, the tenant’s Maventa connection is only the material-handler transport: the partner stays the Finvoice seller and payment beneficiary, receives a bookkeeping PDF copy, and the invoice has no tenant ledger effect. The e-invoice network is the only buyer-delivery channel LAC transmits on. A partner-profile send also emails its seller a bookkeeping copy. Drafts on any other channel are refused with 409; pdf_download drafts are issued through POST /invoices/{invoice_id}/finalize instead. Requires a write-scoped key.
Authorizations
Portal API key minted in portal Settings → API access. Scope read or write; pinned to one company. Send as Authorization: Bearer lac_sk_....
Path Parameters
Body
Optional company selector for write requests.
Target company. Optional for API keys.
Response
Updated invoice.
One sales invoice, sales draft, or purchase invoice. Amounts are integer cents; interior fields beyond the stable ones vary by status.
invoice, credit_note Live allocated payment amount in integer cents.
Amount still outstanding in integer cents.
True only when this issued Maventa invoice has one queued intent, no provider attempt or id, no payment or earlier correction, and an active original journal. The write route repeats these checks under the outbound and journal locks.
Customer-facing seller name captured for this invoice.
Registered legal seller name captured for this invoice.
Seller Business ID captured for this invoice.
Payment account captured for this invoice.
Partner seller profile id; empty for the tenant's own sale.
False for a partner sale. Such an invoice is excluded from this company's journal, VAT facts, receivables, aging, and overdue controls.
Delivery state of the partner's bookkeeping PDF copy.
not_required, no_contact_email, pending, sending, sent, failed, ambiguous Latest partner-copy delivery error.
Whether the exact issued PDF is registered as retained evidence.
Canonical evidence-document id for the issued PDF.
SHA-256 of the exact bytes returned by the PDF endpoint.
^[0-9a-f]{64}$Size of the retained PDF in bytes.
Where this draft stands with its approver, for a company whose invoice_approval_policy is required. Meaningful only while the row is a draft; an issued invoice carries an empty value because approval no longer applies to it. Changing a draft resets this to none: the approval was for the invoice as written.
none, awaiting, approved, rejected Who asked for approval.
Stable identity of the current approval request.
^[0-9a-f]{32}$Which approver approved it or sent it back.
Why an approver did not approve it.
Who created the draft; this person cannot decide it.
Material sales invoice revision that approve or return must echo.
^[0-9a-f]{64}$Material revision that was returned. A new request needs a different current revision.
^[0-9a-f]{64}$Current commercial/source review revision of a purchase invoice; accounting-only coding is excluded.
verify, approve, returned, approved, ready_for_payment, payment_in_progress, paid, source_unavailable, payment_details_missing Whether this person may perform the next purchase review action.
Whether a retained supplier-invoice source document is available; explicit receipt/supporting attachments do not qualify.
An invoicing counterparty (the customer you invoice), with e-invoice routing and per-party defaults. Rates in basis points (25.5% = 2550).