What Qonto data does Well pull into Melio?

Well polls the Qonto API on a fixed cadence and pulls supplier invoices and 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.

Will every Qonto record post to Melio automatically?

Not always. At the next fifteen-minute polling window, 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.

What 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.

How 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.

What happens if I disconnect Qonto or Melio?

Disconnecting Qonto stops the flow at the source. Well calls the Qonto OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. 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.

How does Well authenticate with Qonto and Melio?

Qonto runs a manual OAuth 2.0 flow that you approve inside Qonto; Well receives a refresh token scoped to the resources it needs to read. 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Melio hosts outside the EU; Well processes records per the storage region configured for your workspace.

Qonto to Melio

AvailableNative · QontoNative · Melio

Connect Qonto to Melio with Well

A Qonto debit links to the matching context inside Well the moment it clears; the bill arrives in Melio reflecting the real state, including manual transfers reconciled retroactively.

Connect both toolsView all integrations

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

Melio

Target

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

Why this pair

Connect Qonto to Melio through Well so records flow without manual rework.

What Well does between Qonto and Melio

One-way: Qonto into Well into Melio
Sync mode: Polling every 15 minutes
Up to 4 syncs/hour

Trigger from Qonto

2 events · pick one

Well engine·recipe·When a supplier invoice is uploaded to Qonto

Source

from upload · 15-min poll

Vercel Sarl

via Qonto

Supplier invoice

When a supplier invoice is uploaded to Qonto

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from Qonto

6 fields read

VendorVercel Sarl
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entityVercel Sarl
Tax idFR67898212340
Domainvercel.com
Ledger account6156 · Hosting

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

schedule as bills

Create a bill in your Melio inbox

auto-posted

posted

TypeBill
VendorVercel Sarl
Amount€1,284.00
Ledger6156 · Hosting
Source docattached
Confidence97%

audit linkto Melio

Action in Melio

1 compatible with this trigger

Create a bill in your Melio inbox

Match Qonto debits to Melio scheduled payments.

01Featured

Match debits to bills you have in flight

Each Qonto debit is checked against your bill records inside Well on payee, amount, scheduled date, and currency. Above the auto-link threshold the bank line is linked inside Well; AP sees the link in the document Well forwards to Melio, with the receipt attached for the next vendor audit.

Flag unauthorised vendor payments

If a Qonto debit appears for a vendor not on your approved list inside Well, the match is stopped and the workspace owner is paged. The debit sits on a review queue with the proposed new vendor alongside; once confirmed, Well treats the next debit from the same counterparty consistently before forwarding to Melio.

Close the loop on returned payments

When a Qonto payment is returned (insufficient funds, account closure, fraud claim), Well flags the reversal inside its own ledger, reopens the bill for rescheduling, and routes a notification to the AP owner so the reschedule decision in Melio has the original reason in context.

Surface duplicate payments before the second debit

If a bill flips to scheduled twice in error, Well watches the next Qonto debit window for a second payment to the same vendor with the same amount and surfaces the conflict before AP confirms the second action in Melio.

6 signals and actions across Qonto and Melio

When a supplier invoice is uploaded to Qonto
Pulls from the Qonto banking API. Detects supplier invoices uploaded into the Qonto invoicing inbox.
Trigger·Invoice
When a Qonto supplier invoice is updated
Pulls from the Qonto banking API. Picks up any update to a Qonto supplier invoice the next time Well checks for updates.
Trigger·Invoice
Attach the bill PDF to the Melio record
Driven by Qonto bank transactions and supplier invoices. The forwarded PDF is stored on the bill in your Melio inbox.
Action·Document
Resolve a Melio vendor from the bill
Driven by Qonto bank transactions and supplier invoices. Melio's OCR resolves the vendor name from the PDF; banking details for the payment route are set up separately.
Action·Company
Park the Melio bill in the Bills Inbox for payment scheduling
Driven by Qonto bank transactions and supplier invoices. The created bill waits in your Melio Bills Inbox until you pick a pay date, choose a funding source (bank transfer or card), and set how the vendor gets paid (ACH deposit or mailed check). Well never sets a pay date, chooses funding, or sends the payment.
Action·Invoice
Create a bill in your Melio inbox
Driven by Qonto bank transactions and supplier invoices. Well forwards the PDF to your @invoicesmelio.com address; Melio's Smart Bill Capture lifts the vendor, amount, and due date into a Bills Inbox entry that waits for you to schedule a payment date and funding method.
Action·Invoice

Reference

Field mapping for Qonto → Melio

9 fields across 2 record types, open to see the full table.

Transaction fields

5 fields flow from Qonto into Melio.

Qonto field	Label		Melio field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.emitted_at	Booking date	→	scheduled_for	Payment date
transaction.label	Description	→	reference	Reference
transaction.transaction_id	Transaction id	→	payment_id	Payment id

Invoice fields

4 fields flow from Qonto into Melio.

Qonto field	Label		Melio field	Label
supplier_invoice.invoice_number	Invoice number	→	bill_number	Bill number
supplier_invoice.due_date	Due date	→	due_date	Due date
supplier_invoice.total_amount.currency	Currency	→	currency	Currency
supplier_invoice.attachment_id	Source PDF	→	bill_id	Bill id

Connect Qonto and Melio in three steps.

1
Connect Qonto
Click Connect with Qonto; you approve the connection inside Qonto and authorise read access to supplier invoices and their attachments. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
2
Map your accounts
Well discovers Qonto's supplier invoices and 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
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

How Qonto and Melio stay secure with Well

Well calls Qonto with an OAuth 2.0 token scoped to read-only access. Qonto's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

OAuth 2.0EU residency optionGDPR-aligned

Scopes Well requests

Read Qonto records
Scoped to supplier invoices and their attachments. No access to anything else in your Qonto account.
granted
Deliver documents to your Melio inbox
Well forwards the extracted document to your Melio email-in address; Melio reads bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture from it and you review and post. No write credential to Melio is requested.
granted
Modify or delete Qonto records
Not granted. Qonto is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Qonto’s admin panel.

Frequently asked questions about Qonto and Melio on Well

01What Qonto data does Well pull into Melio?: Well polls the Qonto API on a fixed cadence and pulls supplier invoices and 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. At the next fifteen-minute polling window, 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 calls the Qonto OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. 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 runs a manual OAuth 2.0 flow that you approve inside Qonto; Well receives a refresh token scoped to the resources it needs to read. 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Melio hosts outside the EU; Well processes records per the storage region configured for your workspace.