Bring Square sales records into Qonto supplier invoices

About Square and Qonto

Square

Source

The Square connection reads your Square account through the Square MCP server using OAuth.

Qonto

Target

Qonto is two separate authorisations, not one.

1. 1

   Connect Square

   Click Connect with Square; Square's MCP server registers a Well client automatically. Square'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 Square's card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments and the the Qonto supplier-invoices section. Payouts are anchored to the matching bank deposit with the fee split into its own ledger line, so reconciliation shows gross revenue and processor fees separately.

   • Auto-post above85% confidence
   • Overridemanual anytime
3. 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

01What Square data does Well pull into Qonto?

Square streams card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Qonto as supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices, with the Square event ID preserved on the entry for audit.

02How often does Square data sync to Qonto?

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

03How does Well match Square records to entries in Qonto?

Well scores every candidate match between Square 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 Square data when I first connect to Qonto?

Square exposes the last two 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 Square record IDs and updates existing Qonto entries instead of duplicating them.

05Does Well handle multi-currency records between Square and Qonto?

Square carries the original transaction currency on every record and Qonto natively ledgers in multiple currencies. Well preserves the original amount, applies your Qonto chart-of-accounts conversion rules at posting time, and Well writes both the source and converted amounts onto the record it posts to Qonto, so the entry keeps both sides of the trade.

06How does Well authenticate with Square and Qonto?

Square'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 Square and Qonto is encrypted at rest and handled in line with GDPR.