Forward Qonto supplier invoices into Melio

About Qonto and Melio

Qonto

Source

Qonto is two separate authorisations, not one.

Melio

Target

The Melio connection delivers extracted bills into Melio through its Pay Bills email address.

1. 1

   Connect Qonto

   Click Connect with Qonto; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.

   • AuthOAuth 2.0
2. 2

   Map your accounts

   Well discovers Qonto's your organization, its bank accounts and balances, transactions, and supplier invoices with their attachments and the the Melio Bills Inbox awaiting payment scheduling. The first batch of bank lines flows into the review queue alongside candidate scheduled payments; once you confirm the rule, Qonto debits auto-link above 85% confidence.

   • Auto-post above85% confidence
   • Overridemanual anytime
3. 3

   Connect Melio

   In Melio, open Settings > Integrations and generate an API token with payment-write scope. Paste the key into Well; Melio's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.

   • AuthConnect
   • First sync~10 min

01What Qonto data does Well pull into Melio?

Well polls the Qonto API on a fixed cadence and pulls your organization, its bank accounts and balances, transactions, and supplier invoices with their attachments. Well resolves and scores each counterparty, then writes bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture into Melio with the original Qonto record ID kept on the entry.

02Will every Qonto record post to Melio automatically?

Not always. On the next hourly pull from Qonto, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Melio email-in address and Melio drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

03What happens to historical Qonto data when I first connect to Melio?

Qonto exposes the last three years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Melio ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Melio entries instead of duplicating them.

04How does Well prevent duplicates when posting Qonto records to Melio?

Well maintains a sync marker against Qonto so each window only pulls records strictly newer than the last successful sync; the Qonto record ID is then tracked into Melio for second-line dedup. If the same record appears twice through a manual re-import or a sync marker rewind, Well recognises the ID and updates the existing Melio entry rather than duplicating it.

05What happens if I disconnect Qonto or Melio?

Disconnecting Qonto stops the flow at the source. Well asks the Qonto MCP server to revoke the access token; Qonto returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Melio is Melio's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

06How does Well authenticate with Qonto and Melio?

Qonto's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Qonto and Melio is encrypted at rest and handled in line with GDPR.