What Mercury data does Well pull into Qonto?

Mercury streams transactions, wires, ACH transfers, card payments, and counterparty records to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Qonto as supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices, with the Mercury event ID preserved on the entry for audit.

Will every Mercury record post to Qonto automatically?

Not always. Within seconds of Mercury firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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.

How does Well match Mercury records to entries in Qonto?

Well scores every candidate match between Mercury records and existing Qonto entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Qonto updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

Does Well handle multi-currency records between Mercury and Qonto?

Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Qonto ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Qonto entry carries the unchanged Mercury amount and the conversion is owned by the Qonto accounting policy.

How does Well prevent duplicates when posting Mercury records to Qonto?

Mercury sends each event with a stable resource ID that Well tracks against the Qonto ledger. Webhook replays (which Mercury can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Qonto entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

How does Well authenticate with Mercury and Qonto?

Mercury'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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Mercury hosts outside the EU; Well processes records per the storage region configured for your workspace.

Mercury to Qonto

AvailableNative · MercuryNative · Qonto

Connect Mercury to Qonto with Well

Treasury teams running Mercury and Qonto in parallel see one reconciliation state, not two: matched flags mirror between accounts and FX deltas land on their own ledger line.

Connect both toolsView all integrations

Mercury

Source

The Mercury integration connects your startup banking to Well via MCP, pulling transactions, balances, and counterparty data into your workspace.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

Mercury runs on US banking rails in USD and Qonto runs on EU rails in EUR.

The two sides sit on opposite ends of a cross-border money flow. Connecting Mercury to Qonto through Well matches Mercury outbound wires to Qonto inbound transfers with the FX rate stamped on the booking date, the counterparty resolved on both sides, and the original payment reference preserved on the audit trail.

What Well does between Mercury and Qonto

One-way: Mercury into Well into Qonto
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Mercury

6 events · pick one

Well engine·recipe·When a new transaction posts on your Mercury account

Source

from bank line · live webhook

Mailchimp Intl.

via Mercury

Transaction

When a new transaction posts on your Mercury account

INV-1024 · 22 Apr 2026$1,284.00

Extract

5 fields read from Mercury

5 fields read

CounterpartyMailchimp Intl.
Booking date22 Apr 2026
Amount$1,284.00
CurrencyUSD
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyMailchimp Intl.
Tax idIE3404552KH
Ledger account6238 · Email mktg
Match1 candidate invoice

Confidence97%

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

Post

reconcile as supplier invoices

Push a supplier invoice PDF to Qonto

auto-posted

posted

TypeSupplier invoice
VendorMailchimp Intl.
Amount$1,284.00
Ledger6238 · Email mktg
Source docattached
Confidence97%

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

Cross-reconcile Mercury and Qonto statements.

01Featured

Mirror reconciliation flags across accounts

When a transaction reconciles cleanly in Mercury, Well mirrors the matched flag and supporting documents onto the related Qonto record. Treasury teams running two accounts in parallel see the same reconciliation state without re-running the match per account.

Detect inter-account transfers

Outbound debits from Mercury that match inbound credits in Qonto on amount, date, and counterparty are recognised as inter-account transfers and tagged accordingly. The transfer never accidentally reads as revenue on one side or expense on the other in the downstream accounting feed.

Track FX between two-currency accounts

When Mercury debits one currency and Qonto credits another, Well snaps the FX rate at the timestamp of the transfer, tags the FX gain or loss on the Qonto ledger line, and keeps both the source and destination amounts on the matching pair so audit can recompute the conversion from primary data.

Surface unsettled inbound deposits

Deposits sitting unconfirmed in Qonto for longer than the expected settlement window are checked against Mercury outbound payments. Matches flip the Qonto record to settled; mismatches surface in a review queue with the candidate Mercury debit alongside so treasury can chase the right counterparty.

9 signals and actions across Mercury and Qonto

When a new transaction posts on your Mercury account
Pulls from the Mercury transactions API. Triggers on every debit or credit posting in a Mercury account. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a wire transfer is sent from Mercury
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When an ACH payment clears in Mercury
Pulls from the Mercury transactions API. Picks up cleared ACH credits and debits with the company id reference. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Mercury account's payment details are read
Pulls from the Mercury transactions API. Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Payment method
When a Mercury card charge posts
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a check is deposited to Mercury
Pulls from the Mercury transactions API. Tracks check deposits with the payer, amount, and clearing date. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Mercury account is read
Pulls from the Mercury transactions API. Pulls each Mercury account the workspace holds with its balance, currency, and routing details. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Account
When a wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
Push a supplier invoice PDF to Qonto
Driven by Mercury transaction events. Well POSTs the supplier invoice PDF to Qonto's /v2/supplier_invoices/bulk endpoint via OAuth so the invoice appears under your Qonto supplier invoices.
Action·Document

Reference

Field mapping for Mercury → Qonto

5 fields across 1 record type, open to see the full table.

Transaction fields

5 fields flow from Mercury into Qonto.

Mercury field	Label		Qonto field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.posted_at	Posted date	→	emitted_at	Booking date
transaction.bank_description	Description	→	label	Label
transaction.id	Transaction id	→	transaction_id	Transaction id

Connect Mercury and Qonto in three steps.

1
Connect Mercury
Click Connect with Mercury; Mercury's MCP server handles authorisation through Dynamic Client Registration. Mercury's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthConnect
2
Map your accounts
Well discovers Mercury's transactions, wires, ACH transfers, card payments, and counterparty records and the the Qonto supplier-invoices section. Inter-account transfers and FX deltas are matched across both statements; treasury sees one reconciliation state instead of two competing accounts.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Qonto
Click Connect with Qonto; you approve the connection inside Qonto and authorise the supplier_invoice.write scope so Well can POST PDFs to /v2/supplier_invoices. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
- First sync~30 min

How Mercury and Qonto stay secure with Well

Well connects to Mercury through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Mercury secret; the server refreshes its own tokens on each session. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-aligned

Scopes Well requestsmcp.mercury.com/mcp

Read Mercury records
Scoped to transactions, wires, ACH transfers, card payments, and related records. No access to anything else in your Mercury account.
granted
Post approved records to Qonto
Over Qonto's API, scoped to supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices you have approved (case-by-case or via a per-rule auto-post threshold).
granted
Modify or delete Mercury records
Not granted. Mercury 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 Mercury’s admin panel.

Frequently asked questions about Mercury and Qonto on Well

01What Mercury data does Well pull into Qonto?: Mercury streams transactions, wires, ACH transfers, card payments, and counterparty records to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Qonto as supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices, with the Mercury event ID preserved on the entry for audit.
02Will every Mercury record post to Qonto automatically?: Not always. Within seconds of Mercury firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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.
03How does Well match Mercury records to entries in Qonto?: Well scores every candidate match between Mercury records and existing Qonto entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Qonto updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04Does Well handle multi-currency records between Mercury and Qonto?: Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Qonto ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Qonto entry carries the unchanged Mercury amount and the conversion is owned by the Qonto accounting policy.
05How does Well prevent duplicates when posting Mercury records to Qonto?: Mercury sends each event with a stable resource ID that Well tracks against the Qonto ledger. Webhook replays (which Mercury can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Qonto entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
06How does Well authenticate with Mercury and Qonto?: Mercury'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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Mercury hosts outside the EU; Well processes records per the storage region configured for your workspace.