Send a client invoice via e-invoice

OAuth scope: client_invoices.write

Sends the client invoice identified by the id path parameter via e-invoice.

Eligibility: The client on the invoice must be reachable on the e-invoicing network: e_invoicing_reachable on the client (from Retrieve a client or List clients) must be true. If it is false, do not call this endpoint, use Send a client invoice via email instead. The client invoice must also not already have been submitted for e-invoice. If a send was already requested, calling this endpoint again completes successfully and does not resubmit the invoice.

Processing: Relative to the e-invoicing network, delivery is asynchronous. A 204 means the request was accepted for processing, not that the invoice was fully delivered or issued on the network. The client invoice status does not change when you call this endpoint.

Track downstream steps on the invoice via einvoicing_lifecycle_events. The status_code values follow the platform’s lifecycle; a typical sequence is:

1. 200 — Submitted (deposited for e-invoicing)
2. 201 — Issued by the platform (released into the network)
3. 202 — Received from the platform (the receiving platform acknowledges receipt from the sender), when applicable

Side effects: A successful call records that an e-invoice send was requested and updates the invoice so downstream processing can submit it to the e-invoicing network. Delivery to your customer’s receiving platform—and how the buyer is notified there—then proceeds asynchronously, according to network and counterparty rules. The client invoice status is unchanged by this call; einvoicing_status and lifecycle entries can change as those steps run.

Observability: There is no separate lifecycle-only endpoint. Use Retrieve a client invoice (GET /v2/client_invoices/{id}): the client_invoice object includes einvoicing_lifecycle_events (each event has a lifecycle status_code—for example 201 for Issued by the platform when that milestone is recorded) and einvoicing_status. Client invoice webhooks support updated (and created) events; treat them as a signal to fetch the invoice again if you need the latest lifecycle list. The documented webhook payload includes einvoicing_status but not the full einvoicing_lifecycle_events array.

412 Precondition Failed is returned when the invoice cannot be sent via e-invoice—for example, invalid data, the recipient not being reachable on the e-invoicing network, or another unmet precondition.

Note: The e-invoicing flow is only available in the production environment. Sandbox does not support e-invoicing, as the underlying e-invoicing network operates exclusively in production. This is a platform-level constraint and cannot be worked around in sandbox.