How often does Qonto data sync to Ramp?

Well polls the Qonto API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Ramp write happens at the end of the window, never mid-sync.

How does Well match Qonto records to entries in Ramp?

Well scores every candidate match between Qonto records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp 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 Qonto data when I first connect to Ramp?

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

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

Qonto carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

What happens if I disconnect Qonto or Ramp?

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 Ramp is Ramp'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 Ramp?

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 Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Ramp hosts outside the EU; Well processes records per the storage region configured for your workspace.

Qonto to Ramp

AvailableNative · QontoNative · Ramp

Connect Qonto to Ramp with Well

Mirror Qonto reconciliation rules onto Ramp 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

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

Ramp

Target

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

Why this pair

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

What Well does between Qonto and Ramp

One-way: Qonto into Well into Ramp
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

Linear Orbit Inc.

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

VendorLinear Orbit Inc.
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 entityLinear Orbit Inc.
Tax idEU826112334
Domainlinear.app
Ledger account6064 · SaaS

Confidence97%

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

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorLinear Orbit Inc.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

Cross-reconcile Qonto and Ramp statements.

01Featured

Mirror reconciliation flags across accounts

When a transaction reconciles cleanly in Qonto, Well mirrors the matched flag and supporting documents onto the related Ramp 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 Qonto that match inbound credits in Ramp 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 Qonto debits one currency and Ramp credits another, Well snaps the FX rate at the timestamp of the transfer, tags the FX gain or loss on the Ramp 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 Ramp for longer than the expected settlement window are checked against Qonto outbound payments. Matches flip the Ramp record to settled; mismatches surface in a review queue with the candidate Qonto debit alongside so treasury can chase the right counterparty.

6 signals and actions across Qonto and Ramp

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
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
Create a draft bill in Ramp Bill Pay
Driven by Qonto bank transactions and supplier invoices. Well forwards the PDF to your company's @ap.ramp.com address; Ramp OCR creates a draft bill with invoice number, vendor, payment details, and line items pre-filled.
Action·Invoice
Attach the source document to the Ramp bill
Driven by Qonto bank transactions and supplier invoices. The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document
Resolve a Ramp vendor from the bill
Driven by Qonto bank transactions and supplier invoices. Ramp's OCR resolves the vendor name from the document. You confirm or merge against an existing Ramp vendor.
Action·Company
Create a draft vendor credit in Ramp Bill Pay
Driven by Qonto bank transactions and supplier invoices. When the forwarded PDF is a vendor credit memo rather than an invoice, Ramp OCR creates a draft vendor credit (a separate record from the bill) with the vendor and credit amount pre-filled for your review.
Action·Invoice

Reference

Field mapping for Qonto → Ramp

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

Transaction fields

5 fields flow from Qonto into Ramp.

Qonto field	Label		Ramp field	Label
transaction.amount	Amount	→	transaction.amount	Transaction amount
transaction.currency	Currency	→	transaction.currency_code	Currency
transaction.emitted_at	Booking date	→	transaction.user_transaction_time	Transaction time
transaction.label	Description	→	transaction.merchant_name	Merchant
transaction.transaction_id	Transaction id	→	transaction.id	Ramp transaction id

Invoice fields

3 fields flow from Qonto into Ramp.

Qonto field	Label		Ramp field	Label
supplier_invoice.invoice_number	Invoice number	→	matched_record.reference	Reference
supplier_invoice.total_amount.currency	Currency	→	matched_record.currency	Currency
supplier_invoice.attachment_id	Source PDF	→	matched_record.id	Source id

Connect Qonto and Ramp 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 Ramp Bill Pay drafts queue awaiting approval. 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 Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Qonto and Ramp 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 Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp 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 Ramp on Well

01How often does Qonto data sync to Ramp?: Well polls the Qonto API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Ramp write happens at the end of the window, never mid-sync.
02How does Well match Qonto records to entries in Ramp?: Well scores every candidate match between Qonto records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03What happens to historical Qonto data when I first connect to Ramp?: 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 Ramp ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Ramp entries instead of duplicating them.
04Does Well handle multi-currency records between Qonto and Ramp?: Qonto carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
05What happens if I disconnect Qonto or Ramp?: 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 Ramp is Ramp'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 Ramp?: 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 Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Ramp hosts outside the EU; Well processes records per the storage region configured for your workspace.