What Qonto data does Well pull into Freshbooks?

Well polls the Qonto API on a fixed cadence and pulls your organization, its bank accounts and balances, transactions, and supplier invoices with 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. On the next hourly pull from Qonto, 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 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 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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Freshbooks is encrypted at rest and handled in line with GDPR.

Qonto to Freshbooks

AvailableNative · QontoNative · Freshbooks

Forward Qonto supplier invoices into Freshbooks

Reconcile Qonto transactions and 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

Qonto is two separate authorisations, not one.

Freshbooks

Target

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

Why this pair

Supplier invoices arrive in Qonto as a PDF and a line, and getting them into Freshbooks usually means a person downloading and re-keying each one.

Well reads the supplier invoices and their attachments from Qonto, resolves the supplier behind each invoice, and forwards the document to your Freshbooks email-in address with the supplier already matched. The invoice that lands carries a verified supplier and its original PDF, so your team is not re-typing the same vendor or chasing a missing attachment.

What Well does between Qonto and Freshbooks

One-way: Qonto into Well into Freshbooks
Sync mode: Polling every 60 minutes
Up to 24 syncs/day

Trigger from Qonto

3 events · pick one

Well engine·recipe·When a supplier invoice is uploaded to Qonto

Source

from upload · hourly 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

2 compatible with this trigger

Create a bill in FreshBooks (Select plan)Create an expense in FreshBooks

Reconcile Qonto transactions to Freshbooks ledger lines.

01Featured

Forward a supplier invoice with its PDF

Well reads the supplier invoice and its attachment from Qonto and forwards the document to Freshbooks's email-in address, so the original PDF lands with the invoice.

Resolve the supplier before it arrives

Well matches the supplier on a Qonto invoice against your prior history and carries the resolved company onto the document forwarded to Freshbooks.

Collapse duplicate suppliers

Two supplier names that resolve to one company are treated as the same business inside Well before the forward, so Freshbooks does not accumulate near-duplicates.

Keep the source invoice attached

The Qonto supplier invoice Well read stays linked to the document sent to Freshbooks, so the audit trail traces each bill back to the invoice it came from.

9 signals and actions across Qonto and Freshbooks

Business account balance updated
Pulls from the Qonto banking API. Well monitors changes in your Qonto business accounts to keep balances synchronized.
Trigger·Account
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
New transaction posted to Qonto account
Pulls from the Qonto banking API. Well pulls transaction details directly from your Qonto ledger when a new entry is posted.
Trigger·Transaction
New bank account connected in Qonto
Pulls from the Qonto banking API. When a new business account appears on your Qonto organization, Well starts tracking its activity in your workspace.
Trigger·Account
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; 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
Map your accounts
Well discovers Qonto's your organization, its bank accounts and balances, transactions, and supplier invoices with 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

24 agent skills run on Qonto and Freshbooks.

Each one answers a question from the data this pair brings in. The required ones return nothing until a source like it is connected.

Needs a source like these

Runway

Know exactly how many months and days of cash you have left.

Cash position

Know exactly how much cash you have, and which accounts it came from.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Receivables aging

See who owes you money, and how long they've been sitting on it.

Bills due

See exactly what's coming due, in what order, and how much cash it adds up to.

Rank clients by LTV

Find out who your best customers really are, ranked by what they've actually paid.

Company profile

Everything you know about one company, in one view.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Missing receipts

Find the bills with no paperwork attached, before an auditor does.

Draft invoice

Turn a sentence into a real invoice in Well, PDF attached, no template hunting.

Burn rate

Know what you actually spend each month, averaged over real months.

Recurring revenue

Know what you can count on earning each month, averaged over real months.

Cash forecast

See where your cash lands if nothing new comes in.

Cash movement

See the bridge from last month's balance to this one.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close to the point of approval.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Answers better with these connected

FX exposure

See how much of your cash and receivables sit outside your home currency.

Invoice fetching agents

See exactly which agents would run, before any of them does.

Convert currencies

Turn mixed currencies into one number you can actually audit.

Connects and checks them

Check your connections

See what is connected, what is syncing, and what is missing.

Connect your bank

Get the bank feed in, and confirm it is really live.

Browse all skills

How Qonto and Freshbooks stay secure with Well

Well connects to Qonto through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Qonto secret; the server refreshes its own tokens on each session. Anything Well holds between Qonto and Freshbooks is encrypted at rest and handled in line with GDPR.

MCP server authEncrypted at restGDPR compliant

Scopes Well requestswellapp.ai/v1/mcps/qonto/mcp

Read Qonto records
Scoped to your organization, its bank accounts and balances, transactions, and supplier invoices with 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. Well never edits or deletes an existing Qonto record; the one write it holds files a new document into Qonto.
refused
Read other workspaces' data
Not granted. A session resolves only to the workspaces your account belongs to, and Well checks that membership before it returns any record.
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 your organization, its bank accounts and balances, transactions, and supplier invoices with 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. On the next hourly pull from Qonto, 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 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 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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Freshbooks is encrypted at rest and handled in line with GDPR.

Connect Qonto and Freshbooks

Link both tools to Well so each Qonto supplier invoice reaches Freshbooks with its supplier resolved and its PDF attached.

Try Well free

Read-only scopes on Qonto
AES-256 at rest, TLS 1.3 in transit
GDPR compliant
Revocable Freshbooks access in one click

Other ways to connect Qonto or Freshbooks through Well.

Browse all

Qonto

See the Qonto connector

Freshbooks

See the Freshbooks connector

Stripe → Qonto

Reconcile Stripe payouts against Qonto bank deposits. Well d…

PayPal → Qonto

Match PayPal payouts to the Qonto bank deposit that received…

Square → Freshbooks

Reconcile Square sales, refunds, and customer activity insid…

iBanFirst

See the iBanFirst connector

Mercury

See the Mercury connector

Kolecto

See the Kolecto connector

Last reviewed: 2026-05-26