How it works The integration follows three steps:
- Your user creates an invoice in your tool, exported in one of the supported structured formats: Factur-X (recommended), UBL 2.1, or CII.
- You import the invoice to Qonto via
POST /v2/client_invoices/bulk. This registers the invoice and returns aclient_invoice_id. - You send the invoice via Qonto’s PA using that
client_invoice_id. Qonto routes it through the e-invoicing network to the recipient’s platform.
Coming soon: webhooks so you can be notified of supplier and client invoices’ lifecycle events
Account setup Each of your users needs a “Qonto PA” account (free, €0/month) to be registered as a PA user. This lightweight onboarding can be triggered programmatically - see Create a registration for the full flow, including the PA-specific account configuration.
Key endpoints
- Create a registration - trigger a workflow to guide the user through the necessary steps to register an organization with Qonto
- Import a client invoice -
POST /v2/client_invoices/bulkto import an externally generated invoice (Factur-X, UBL, or CII) and obtain aclient_invoice_id - Send via e-invoicing -
POST /v2/client_invoices/{id}/send_by_einvoiceto route the invoice through Qonto’s PA - Retrieve a client invoice - fetch the current status and metadata
- Retrieve a supplier invoice - access incoming invoices received through the PA on behalf of your users
client_invoice.write
A note on AFNOR XP Z12-013 Qonto’s API does not currently follow the AFNOR XP Z12-013 standard. The endpoints listed above cover the same e-invoicing use cases — see E-invoicing via API for details.