Reconcile Ramp spend against Qonto supplier invoices

About Ramp and Qonto

Ramp

Source

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

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

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

   • AuthOAuth 2.0
   • First sync~30 min

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