Forward Qonto supplier invoices into Ramp

About Qonto and Ramp

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.

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

   • AuthOAuth 2.0
2. 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. 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 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.