Qonto

Qonto exposes a wide range of financial objects: transactions, SEPA transfers, bank accounts, client invoices, supplier invoices, expense requests, cards, memberships, and labels. This integration covers the three objects that most directly reflect individual member activity within a finance team: SEPA transfers for payment operations, supplier invoices for accounts payable throughput, and client invoices for accounts receivable output, supplemented by a transaction-level governance indicator. Six KPIs were retained, selected against three criteria: ability to attribute the action to an identified member, resistance to gaming, and balance between leading and lagging indicators.

Payment operations: reading transfer activity through paired indicators

Two KPIs cover SEPA transfer initiation. Transfers Initiated measures the number of payment orders a member has submitted. Transfers Amount measures the total financial value of those orders. These two indicators are intentionally paired and should never be read in isolation.

The reason for pairing is structural: a member who fragments a single supplier payment into twenty micro-transfers will score high on count while the amount remains constant. Conversely, a member handling a single large treasury transfer will show a low count and a high amount. Neither pattern is inherently correct; what matters is whether the count-to-amount ratio is consistent over time and coherent with the member's role. A significant divergence between the two indicators is the signal worth investigating — it either reveals a change in payment practices or a change in the volume of work the member is carrying.

Accounts payable: supplier invoice throughput

Two KPIs cover supplier invoices. Supplier Invoices Processed measures the number of supplier invoices a member has handled. Supplier Invoices Amount measures the cumulative value of those invoices.

Supplier invoices are among the most attributable indicators in Qonto: each invoice requires an actual supplier document, which makes artificial inflation operationally costly and therefore rare. This low gaming risk is what justifies retaining both the count and the amount as independent KPIs rather than forcing a single composite measure. The count reflects processing rhythm — how consistently a member clears the queue of incoming invoices. The amount reflects the financial weight of the workload, which is not always correlated with count when the invoice mix includes both small operational expenses and large capital commitments. Reading both indicators together allows a finance manager to distinguish between high-frequency, low-value processing and lower-frequency, high-value processing, two profiles that carry different risk implications for cash flow management.

Accounts receivable and governance

Client invoice finalization

Client Invoices Finalized counts invoices that have moved out of draft status — that is, invoices marked as either unpaid or paid, meaning they have been formally issued to a client. This KPI tracks the billing cadence of members responsible for revenue-side documentation. A sustained drop in Client Invoices Finalized is an early signal of a slowdown in the revenue pipeline, since unbilled revenue cannot be collected. It does not measure the quality of invoicing or payment outcomes — only the activity of transforming completed work into formal billing requests.

Attribution for this KPI relies on a metadata field rather than a hard membership reference, which makes it less structurally reliable than the transfer and supplier invoice indicators. It should be interpreted with that caveat in mind, and anomalies in the data should be cross-checked against internal billing records before drawing management conclusions.

Expense governance

Attachment Compliance Rate measures the proportion of transactions for which a member has submitted the required receipt or supporting document. This indicator occupies a distinct position in the integration: it does not measure output or financial volume but adherence to an internal process. Its value lies in the fact that it is directly actionable by the member — uploading a receipt is a unilateral act requiring no approval — and that non-compliance creates downstream friction for accountants and auditors.

The pairing of Attachment Compliance Rate with the transfer and transaction indicators serves a coherence check function: a member with high Transfers Initiated and low Attachment Compliance Rate is creating payment activity without the corresponding audit trail, which is the pattern most likely to trigger regulatory or internal control issues. Read together, these indicators distinguish between members who execute at volume and those who execute with process discipline — a distinction that is invisible when only output volume is tracked.

Scope and limits of the integration

Qonto records financial operations to the extent that they pass through the platform. Payments made outside Qonto — via bank wire, check, or a separate card provider — remain invisible to this integration. The KPIs therefore reflect the share of financial activity that the organization routes through Qonto, not total financial operations. In organizations where Qonto is the sole business account, this limitation is negligible; in organizations using multiple banking providers, the indicators should be interpreted as partial views.

Attribution of transfers and supplier invoices relies on the member's Qonto membership identifier, which is resolved to a Human Bridge user email at OAuth connection time. This mechanism works correctly when every member has authenticated their Qonto account through the platform's connection flow. Members who have not yet connected produce no attributed data, which means the integration's coverage is directly proportional to the adoption rate within the finance team. The reliability of these KPIs therefore depends on two disciplines simultaneously: the financial rigor with which members operate in Qonto, and the organizational discipline with which the integration is rolled out to all relevant team members.