What QuickBooks data does Well pull into Qonto?

Well polls the QuickBooks API on a fixed cadence and pulls bills, customers, and tax codes polled hourly from QuickBooks Online. Well resolves and scores each counterparty, then writes supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices into Qonto with the original QuickBooks record ID kept on the entry.

Will every QuickBooks record post to Qonto automatically?

Not always. On the next hourly pull from QuickBooks, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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.

How does Well match QuickBooks records to entries in Qonto?

Well scores every candidate match between QuickBooks 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.

How does Well prevent duplicates when posting QuickBooks records to Qonto?

Well maintains a sync marker against QuickBooks so each window only pulls records strictly newer than the last successful sync; the QuickBooks record ID is then tracked into Qonto for second-line dedup. If the same record appears twice through a manual re-import or a sync marker rewind, Well recognises the ID and updates the existing Qonto entry rather than duplicating it.

What happens if I disconnect QuickBooks or Qonto?

Disconnecting QuickBooks stops the flow at the source. Well calls the QuickBooks OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 QuickBooks and Qonto?

QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and QuickBooks hosts outside the EU; Well processes records per the storage region configured for your workspace.

QuickBooks to Qonto

AvailableNative · QuickBooksNative · Qonto

Connect QuickBooks to Qonto with Well

Move QuickBooks bills and customers through Well and into Qonto as supplier invoices, with the audit trail kept on every record.

Connect both toolsView all integrations

QuickBooks

Source

The QuickBooks connection delivers documents into QuickBooks Online through its @qbodocs.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

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

What Well does between QuickBooks and Qonto

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

Trigger from QuickBooks

5 events · pick one

Well engine·recipe·When a QuickBooks bill is read

Source

from upload · hourly poll

Algolia SAS

via QuickBooks

Bill

When a QuickBooks bill is read

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from QuickBooks

6 fields read

VendorAlgolia SAS
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 entityAlgolia SAS
Tax idFR75814107155
Domainalgolia.com
Ledger account6156 · Search infra

Confidence97%

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

Post

reconcile as supplier invoices

Push a supplier invoice PDF to Qonto

auto-posted

posted

TypeSupplier invoice
VendorAlgolia SAS
Amount€1,284.00
Ledger6156 · Search infra
Source docattached
Confidence97%

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

9 signals and actions across QuickBooks and Qonto

When a QuickBooks customer is read
Reads QuickBooks customer and vendor records with name, billing address, and tax registration to match against your companies. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
When a QuickBooks credit memo is read
Captures QuickBooks credit memos with customer, totals, and tax so refunds reconcile against the original invoice. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a QuickBooks sales invoice is read
Captures QuickBooks sales invoices with customer, amount, currency, and reference for reconciliation. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a QuickBooks bill is read
Pulls QuickBooks bills with vendor, due date, line items, totals, and tax code on the hourly poll. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a QuickBooks payment is read
Reads the payment recorded against a QuickBooks invoice or bill with method and amount. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Payment method
When a QuickBooks attachment is read
Picks up the source document attached to a QuickBooks bill or invoice. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Document
When a QuickBooks purchase order is read
Pulls QuickBooks purchase orders with vendor, line items, and totals to match against the arriving bill. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a QuickBooks account is read
Pulls bank-type accounts from the QuickBooks chart of accounts with currency and account number. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Account
Push a supplier invoice PDF to Qonto
Well POSTs the supplier invoice PDF to Qonto's /v2/supplier_invoices/bulk endpoint via OAuth so the invoice appears under your Qonto supplier invoices.
Action·Document

Reference

Field mapping for QuickBooks → Qonto

14 fields across 3 record types, open to see the full table.

Invoice fields

6 fields flow from QuickBooks into Qonto.

QuickBooks field	Label		Qonto field	Label
Bill.TotalAmt.total	Total	→	total_amount	Total
Bill.CurrencyRef.currency	Currency	→	currency	Currency
Bill.TxnDate.date	Bill date	→	issue_date	Issue date
Bill.DueDate.due_date	Due date	→	due_date	Due date
Bill.DocNumber.invoice_number	Doc number	→	invoice_number	Invoice number
Bill.TxnTaxDetail.tax	Tax	→	tax_amount	Tax

Transaction fields

5 fields flow from QuickBooks into Qonto.

QuickBooks field	Label		Qonto field	Label
Purchase.TotalAmt.amount	Amount	→	amount	Amount
Purchase.CurrencyRef.currency	Currency	→	currency	Currency
Purchase.TxnDate.created	Transaction date	→	emitted_at	Booking date
Purchase.PrivateNote.description	Memo	→	label	Label
Purchase.Id.id	Purchase id	→	transaction_id	Transaction id

Company fields

3 fields flow from QuickBooks into Qonto.

QuickBooks field	Label		Qonto field	Label
Vendor.DisplayName.name	Display name	→	supplier_name	Supplier
Vendor.WebAddr.website	Website	→	supplier_website	Website
Vendor.TaxIdentifier.tax_id	Tax id	→	supplier_tax_id	Tax id

Connect QuickBooks and Qonto in three steps.

1
Connect QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read access to bills, customers, and tax codes polled hourly from QuickBooks Online. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthConnect
2
Map your accounts
Well discovers QuickBooks's bills, customers, and tax codes polled hourly from QuickBooks Online and the the Qonto supplier-invoices section. Match candidates are scored on counterparty, amount, date, and reference; above 85% confidence the link posts automatically, below it the candidate set queues for sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Qonto
Click Connect with Qonto; you approve the connection inside Qonto and authorise the supplier_invoice.write scope so Well can POST PDFs to /v2/supplier_invoices. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
- First sync~30 min

How QuickBooks and Qonto stay secure with Well

Well calls QuickBooks with an OAuth 2.0 token scoped to read-only access. QuickBooks'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 QuickBooks records
Scoped to bills, customers, and tax codes polled hourly from QuickBooks Online. No access to anything else in your QuickBooks account.
granted
Post approved records to Qonto
Over Qonto's API, scoped to supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices you have approved (case-by-case or via a per-rule auto-post threshold).
granted
Modify or delete QuickBooks records
Not granted. QuickBooks 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 QuickBooks’s admin panel.

Frequently asked questions about QuickBooks and Qonto on Well

01What QuickBooks data does Well pull into Qonto?: Well polls the QuickBooks API on a fixed cadence and pulls bills, customers, and tax codes polled hourly from QuickBooks Online. Well resolves and scores each counterparty, then writes supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices into Qonto with the original QuickBooks record ID kept on the entry.
02Will every QuickBooks record post to Qonto automatically?: Not always. On the next hourly pull from QuickBooks, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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.
03How does Well match QuickBooks records to entries in Qonto?: Well scores every candidate match between QuickBooks 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.
04How does Well prevent duplicates when posting QuickBooks records to Qonto?: Well maintains a sync marker against QuickBooks so each window only pulls records strictly newer than the last successful sync; the QuickBooks record ID is then tracked into Qonto for second-line dedup. If the same record appears twice through a manual re-import or a sync marker rewind, Well recognises the ID and updates the existing Qonto entry rather than duplicating it.
05What happens if I disconnect QuickBooks or Qonto?: Disconnecting QuickBooks stops the flow at the source. Well calls the QuickBooks OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything Well already wrote to Qonto before the disconnect stays in Qonto; the connection only stops further writes. 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 QuickBooks and Qonto?: QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and QuickBooks hosts outside the EU; Well processes records per the storage region configured for your workspace.