How often does Ramp data sync to Qonto?

Ramp pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Qonto within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Ramp record post to Qonto automatically?

Not always. Within seconds of Ramp 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 Ramp records to entries in Qonto?

Well scores every candidate match between Ramp 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.

What happens to historical Ramp data when I first connect to Qonto?

Ramp 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 Qonto ledger, and re-running the backfill is safe because Well tracks the Ramp record IDs and updates existing Qonto entries instead of duplicating them.

What happens if I disconnect Ramp or Qonto?

Disconnecting Ramp stops the flow at the source. Well asks the Ramp MCP server to revoke the access token; Ramp returns confirmation and stops streaming events the moment it is acknowledged. Anything Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 Ramp and Qonto?

Ramp'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 in transit under TLS 1.3. Anything Well holds between Ramp and Qonto is encrypted at rest and handled in line with GDPR.

Ramp to Qonto

AvailableNative · RampNative · Qonto

Connect Ramp to Qonto with Well

Mirror Ramp reconciliation rules onto Qonto for the second leg of every inter-account flow, with the FX gain or loss landing on its own ledger line.

Connect both toolsView all integrations

Ramp

Source

The Ramp integration connects your corporate card and expense management platform to Well.

Qonto

Target

Qonto is two separate authorisations, not one.

Why this pair

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

What Well does between Ramp and Qonto

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

Trigger from Ramp

4 events · pick one

Well engine·recipe·When a Ramp card is swiped

Source

from card · live webhook

Vercel Sarl

via Ramp

Card

When a Ramp card is swiped

INV-1024 · 22 Apr 2026€1,284.00

Extract

5 fields read from Ramp

5 fields read

CounterpartyVercel Sarl
Booking date22 Apr 2026
Amount€1,284.00
CurrencyEUR
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyVercel Sarl
Tax idFR67898212340
Ledger account6156 · Hosting
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
VendorVercel Sarl
Amount€1,284.00
Ledger6156 · Hosting
Source docattached
Confidence97%

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

Cross-reconcile Ramp and Qonto statements.

01Featured

Mirror reconciliation flags across accounts

When a transaction reconciles cleanly in Ramp, 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 Ramp 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 Ramp 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 Ramp outbound payments. Matches flip the Qonto record to settled; mismatches surface in a review queue with the candidate Ramp debit alongside so treasury can chase the right counterparty.

7 signals and actions across Ramp and Qonto

When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Ramp vendor record appears in your account
Well discovers new Ramp vendors via the read-only ETL load and mirrors them as company records. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
When a Ramp transaction trips a spend policy
Pulls the policy_violations field on the transaction so non-compliant lines surface for review. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Ramp card account is read
Pulls each Ramp card account the workspace holds with its limit and the cards bound to it. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Account
When a Ramp transaction is coded by a Ramp rule
Picks up Ramp transactions that arrive with an automated coding rule already applied. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
Push a supplier invoice PDF to Qonto
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 Ramp → Qonto

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

Transaction fields

3 fields flow from Ramp into Qonto.

Ramp field	Label		Qonto field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency_code	Currency	→	currency	Currency
transaction.id	Transaction id	→	transaction_id	Transaction id

Invoice fields

4 fields flow from Ramp into Qonto.

Ramp field	Label		Qonto field	Label
bill.invoice_number	Invoice number	→	invoice_number	Invoice number
bill.invoice_date	Issue date	→	issue_date	Issue date
bill.due_date	Due date	→	due_date	Due date
bill.currency_code	Currency	→	currency	Currency

Connect Ramp and Qonto in three steps.

1
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Ramp's card transactions, approved bills, reimbursements, vendor records, and policy events 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; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

24 agent skills run on Ramp and Qonto.

Each one answers a question from the data this pair brings in. The required ones return nothing until a source like it is connected.

Needs a source like these

Runway

Know exactly how many months and days of cash you have left.

Cash position

Know exactly how much cash you have, and which accounts it came from.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Receivables aging

See who owes you money, and how long they've been sitting on it.

Bills due

See exactly what's coming due, in what order, and how much cash it adds up to.

Rank clients by LTV

Find out who your best customers really are, ranked by what they've actually paid.

Company profile

Everything you know about one company, in one view.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Missing receipts

Find the bills with no paperwork attached, before an auditor does.

Draft invoice

Turn a sentence into a real invoice in Well, PDF attached, no template hunting.

Burn rate

Know what you actually spend each month, averaged over real months.

Recurring revenue

Know what you can count on earning each month, averaged over real months.

Cash forecast

See where your cash lands if nothing new comes in.

Cash movement

See the bridge from last month's balance to this one.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close to the point of approval.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Answers better with these connected

FX exposure

See how much of your cash and receivables sit outside your home currency.

Invoice fetching agents

See exactly which agents would run, before any of them does.

Convert currencies

Turn mixed currencies into one number you can actually audit.

Connects and checks them

Check your connections

See what is connected, what is syncing, and what is missing.

Connect your bank

Get the bank feed in, and confirm it is really live.

Browse all skills

How Ramp and Qonto stay secure with Well

Well connects to Ramp through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Ramp secret; the server refreshes its own tokens on each session. Anything Well holds between Ramp and Qonto is encrypted at rest and handled in line with GDPR.

MCP server authEncrypted at restGDPR compliant

Scopes Well requestsramp-mcp-remote.ramp.com/mcp

Read Ramp records
Scoped to card transactions, approved bills, reimbursements, vendor records, and related records. No access to anything else in your Ramp 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 Ramp records
Not granted. Ramp is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Not granted. A session resolves only to the workspaces your account belongs to, and Well checks that membership before it returns any record.
refused

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

Frequently asked questions about Ramp and Qonto on Well

01How often does Ramp data sync to Qonto?: Ramp pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Qonto within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02Will every Ramp record post to Qonto automatically?: Not always. Within seconds of Ramp 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 Ramp records to entries in Qonto?: Well scores every candidate match between Ramp 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.
04What happens to historical Ramp data when I first connect to Qonto?: Ramp 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 Qonto ledger, and re-running the backfill is safe because Well tracks the Ramp record IDs and updates existing Qonto entries instead of duplicating them.
05What happens if I disconnect Ramp or Qonto?: Disconnecting Ramp stops the flow at the source. Well asks the Ramp MCP server to revoke the access token; Ramp returns confirmation and stops streaming events the moment it is acknowledged. Anything Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 Ramp and Qonto?: Ramp'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 in transit under TLS 1.3. Anything Well holds between Ramp and Qonto is encrypted at rest and handled in line with GDPR.