OAuth scope: client_invoice.write
Creates a single client invoice for the authenticated organization.
Price plans: this endpoint is available for all Qonto price plans.
Do note:
currency of the provided client. If the currency is not set for that client, you will receive a validation error on the /data/attributes/currency property.Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
The ID of the associated client. The client is validated against the business rules of the invoicing domain. In case of getting a validation error related to a field in the customer, you will need to issue a request to update the customer itself and then try to re-create the invoice itself. This is because a client can be used across different domains - client creation performs only minimal validations on the client and then it is up to each domain (for example, invoicing) to apply their own business rules on top of that client. More information can be found in the docs for creating a client.
"2022-03-01"
Payment deadline that is added by the initiator. The format should be YYYY-MM-DD
Currency for the total amount of the invoice. Currently, only value allowed is EUR. Trigram following ISO 4217
"EUR"
Payment method details for the invoice.
Optional ID of a previously uploaded file to attach to this invoice. The upload must have been created using the POST /v2/client_invoices/uploads endpoint.
"4d5418bb-bd0d-4df4-865c-c07afab8bb48"
DEPRECATED: This field is deprecated. Please use performance_start_date and performance_end_date instead.
The performance date represents when the job or service is expected to be completed by the client. Date the initiator has issued or shared the invoice as legally viable. The format should be YYYY-MM-DD
Start date of the performance period for the invoice. The format should be YYYY-MM-DD.
The performance period defines the date range during which the job or service is expected to be completed by the client. This field marks the beginning of that period and can be used together with performance_end_date to create a flexible date range instead of a single fixed date.
Validation rules:
performance_end_date is providedperformance_end_date when both are providedFallback behavior:
performance_date value as fallbackperformance_date field"2022-03-01"
End date of the performance period for the invoice. The format should be YYYY-MM-DD.
This field defines the end of the performance date range, allowing clients to complete the job or service anytime between performance_start_date and performance_end_date. When used together with performance_start_date, it creates a flexible time window rather than requiring completion on a specific date.
Validation rules:
performance_start_date becomes requiredperformance_start_date"2022-03-31"
Invoice's status. If not filled, unpaid will be automatically propertyd to the invoice.
draft, unpaid Invoice's number. Must be unique within the organization and is:
40"INV-2023-001"
Purchase order data added by the invoice’s initiator.
40Additional notes added by the invoice’s initiator.
525"This is an example."
"This is an example."
This collection of properties can be optionally used to temporarily override some of the organization's properties for this one invoice.
false, the invoice will not be sent to SdI.GET v2/client_invoices to retrieve its e-invoicing status under the property einvoicing_status.rate field with their IRPF.4 - 15"1.00"
Global discount applied to the entire invoice. This discount is applied to the sum of all items (after item-level discounts, if any).
Returns the client invoice created.