Forward Qonto supplier invoices into Ramp

About Qonto and Ramp

Qonto

Source

Qonto is two separate authorisations, not one.

Ramp

Target

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

1. 1

   Connect Qonto

   Click Connect with Qonto; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto'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 Qonto's your organization, its bank accounts and balances, transactions, and supplier invoices with 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. 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

01How often does Qonto data sync to Ramp?

Well polls the Qonto API hourly, which fits Qonto's rate-limit envelope and keeps the downstream match window inside the same business day. The hourly pull respects Qonto's rate limits and feeds Ramp once per window with the batch's confidence outcomes already resolved.

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 asks the Qonto MCP server to revoke the access token; Qonto returns confirmation and stops streaming events the moment it is acknowledged. 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'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, 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 in transit under TLS 1.3. Anything Well holds between Qonto and Ramp is encrypted at rest and handled in line with GDPR.