What Qonto data does Well pull into Freshbooks?

Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated into Freshbooks with the original Qonto record ID kept on the entry.

Will every Qonto record post to Freshbooks automatically?

Not always. At the next fifteen-minute polling window, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Freshbooks email-in address and Freshbooks drafts the record from it for you to confirm. 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.

What happens to historical Qonto data when I first connect to Freshbooks?

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

What happens if a Qonto record fails to post to Freshbooks?

When a record fails to post to Freshbooks (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Qonto record. Nothing silently drops.

What happens if I disconnect Qonto or Freshbooks?

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

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

Qonto to Freshbooks

AvailableNative · QontoNative · Freshbooks

Connect Qonto to Freshbooks with Well

Reconcile Qonto supplier invoices against your open invoices inside Well, then forward the matched documents to Freshbooks's email-in inbox for one-click review.

Connect both toolsView all integrations

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

Freshbooks

Target

The FreshBooks connection delivers extracted documents into FreshBooks through its email-in address.

Why this pair

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

What Well does between Qonto and Freshbooks

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

Figma 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

VendorFigma 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 entityFigma Inc.
Tax idEU826145320
Domainfigma.com
Ledger account6064 · SaaS

Confidence97%

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

Post

post as expenses and bills

Create a bill in FreshBooks (Select plan)

auto-posted

posted

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

audit linkto Freshbooks

Action in Freshbooks

1 compatible with this trigger

Create a bill in FreshBooks (Select plan)

Reconcile Qonto transactions to Freshbooks ledger lines.

01Featured

Reconcile transactions to existing invoices

Every Qonto debit is scored against your open invoices inside Well on counterparty, amount, scheduled date, and currency. Above the auto-link threshold the bank line is linked to the right invoice; the matched document is then forwarded to Freshbooks's email-in inbox with the receipt attached for your one-click confirmation.

Reconcile deposits to expected receivables

Qonto deposits are checked against your open sales invoices inside Well. The match runs on amount and date proximity inside the same customer, so a partial payment or an aggregated weekly deposit still resolves to the right invoices before the matched document reaches Freshbooks.

Pull statement balance for month-end close

At month-end Well snapshots the Qonto statement balance and surfaces every reconciling item in one queue inside Well. Outstanding cheques, in-transit deposits, and timing differences land on their own bucket so the controller clears the diff before forwarding matched documents to Freshbooks.

Capture FX impact on cross-border transfers

Cross-currency Qonto transfers carry the source and converted amounts; Well records the FX rate at the timestamp of settlement and includes it in the document forwarded to Freshbooks, so the FX delta is visible alongside the operational entry when you review the draft.

6 signals and actions across Qonto and Freshbooks

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
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
Create an expense in FreshBooks
Driven by Qonto bank transactions and supplier invoices. Well forwards the receipt PDF to your FreshBooks email-in address; FreshBooks creates an expense with merchant, total, and tax populated.
Action·Transaction
Resolve a FreshBooks merchant from the receipt
Driven by Qonto bank transactions and supplier invoices. FreshBooks reads the merchant name off the forwarded receipt and matches it on the expense (or bill). You confirm or correct the merchant on first sight.
Action·Company
Attach the receipt to the FreshBooks record
Driven by Qonto bank transactions and supplier invoices. The forwarded PDF is stored on the expense or bill as the source.
Action·Document
Create a bill in FreshBooks (Select plan)
Driven by Qonto bank transactions and supplier invoices. On the FreshBooks Select plan, the same email-in feature also creates a bill (with line items) instead of an expense.
Action·Invoice

Reference

Field mapping for Qonto → Freshbooks

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

Transaction fields

5 fields flow from Qonto into Freshbooks.

Qonto field	Label		Freshbooks field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency_code	Currency
transaction.emitted_at	Booking date	→	date	Transaction date
transaction.label	Description	→	note	Description
transaction.transaction_id	Transaction id	→	external_id	External id

Invoice fields

5 fields flow from Qonto into Freshbooks.

Qonto field	Label		Freshbooks field	Label
supplier_invoice.invoice_number	Invoice number	→	invoice_number	Invoice number
supplier_invoice.issue_date	Issue date	→	create_date	Issue date
supplier_invoice.due_date	Due date	→	due_date	Due date
supplier_invoice.total_amount.currency	Currency	→	currency_code	Currency
supplier_invoice.attachment_id	Source PDF	→	external_id	External id

Connect Qonto and Freshbooks 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 FreshBooks expense or bill queue. Counterparty proximity, amount, date, and reference drive the match score; lines above 85% post automatically and the rest queue for a one-click sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Freshbooks
Click Connect with FreshBooks; FreshBooks asks for the account to authorise and returns a refresh token and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your FreshBooks.
- AuthConnect
- First syncup to an hour

How Qonto and Freshbooks 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 Freshbooks inbox
Well forwards the extracted document to your Freshbooks email-in address; Freshbooks reads expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated from it and you review and post. No write credential to Freshbooks 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 Freshbooks on Well

01What Qonto data does Well pull into Freshbooks?: Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated into Freshbooks with the original Qonto record ID kept on the entry.
02Will every Qonto record post to Freshbooks automatically?: Not always. At the next fifteen-minute polling window, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Freshbooks email-in address and Freshbooks drafts the record from it for you to confirm. 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.
03What happens to historical Qonto data when I first connect to Freshbooks?: 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 Freshbooks ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Freshbooks entries instead of duplicating them.
04What happens if a Qonto record fails to post to Freshbooks?: When a record fails to post to Freshbooks (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Qonto record. Nothing silently drops.
05What happens if I disconnect Qonto or Freshbooks?: 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 Freshbooks is Freshbooks'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 Freshbooks?: 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 Freshbooks email-in address once it clears the matching threshold; Freshbooks creates the draft record from it and you confirm and post it. Well holds no write credential to Freshbooks. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Freshbooks hosts outside the EU; Well processes records per the storage region configured for your workspace.