What Qonto data does Well pull into QuickBooks?

Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks into QuickBooks with the original Qonto record ID kept on the entry.

Will every Qonto record post to QuickBooks 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 QuickBooks email-in address and QuickBooks 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.

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

Well maintains a sync marker against Qonto so each window only pulls records strictly newer than the last successful sync; the Qonto record ID is then tracked into QuickBooks 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 QuickBooks entry rather than duplicating it.

Can I customise which Qonto fields are sent to QuickBooks?

The default mapping covers every Qonto field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.

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

When a record fails to post to QuickBooks (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.

How does Well authenticate with Qonto and QuickBooks?

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 QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. 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.

Qonto to QuickBooks

AvailableNative · QontoNative · QuickBooks

Connect Qonto to QuickBooks with Well

Pull Qonto debits and credits into Well, score each line against your open invoices and prior history, then forward the matched output to QuickBooks as a confirmable draft.

Connect both toolsView all integrations

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

QuickBooks

Target

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

Why this pair

Qonto runs on EU banking rails (SEPA, EUR) and QuickBooks Online accepts emailed PDFs at @qbodocs.

com to create bills or receipts. Connecting Qonto to QuickBooks through Well matches each Qonto transaction inside its own ledger with the supplier resolved and the source reference preserved, then forwards the matched document to QuickBooks' email-in. QuickBooks creates a bill or receipt; your team confirms in the For Review tab and reconciles against the matching invoice.

What Well does between Qonto and QuickBooks

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

Salesforce France

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

VendorSalesforce France
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 entitySalesforce France
Tax idFR81449666036
Domainsalesforce.com
Ledger account6238 · CRM

Confidence97%

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

Post

post as bills and receipts

Create a bill or receipt in QuickBooks

auto-posted

posted

TypeBill
VendorSalesforce France
Amount€1,284.00
Ledger6238 · CRM
Source docattached
Confidence97%

audit linkto QuickBooks

Action in QuickBooks

1 compatible with this trigger

Create a bill or receipt in QuickBooks

Reconcile Qonto transactions to QuickBooks 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 QuickBooks's email-in inbox with the receipt attached for your one-click confirmation.

Categorise unmatched debits by counterparty

When a Qonto debit has no matching invoice in Well, the counterparty is checked against your prior history and a category is proposed. Approve the proposal once for a new vendor and Well applies it to every subsequent Qonto debit from the same counterparty before forwarding to QuickBooks.

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

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 QuickBooks, so the FX delta is visible alongside the operational entry when you review the draft.

6 signals and actions across Qonto and QuickBooks

When a supplier invoice is uploaded to Qonto
Pulls from the Qonto banking API. Detects supplier invoices uploaded into the Qonto invoicing inbox. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
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. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Invoice
Resolve the vendor from the bill
Driven by Qonto bank transactions and supplier invoices. QuickBooks OCR resolves the vendor name from the document. You confirm or merge against an existing vendor on first sight.
Action·Company
Route the record to the For Review tab
Driven by Qonto bank transactions and supplier invoices. The created bill or receipt lands in the QuickBooks For Review tab so your team confirms the expense account and bank match before posting. Well never writes the ledger entry itself.
Action·Transaction
Create a bill or receipt in QuickBooks
Driven by Qonto bank transactions and supplier invoices. Well forwards the PDF to your @qbodocs.com address; QuickBooks creates a bill or receipt with vendor, date, and amount populated. QuickBooks picks the record type per document.
Action·Invoice
Attach the source document to the QuickBooks record
Driven by Qonto bank transactions and supplier invoices. The forwarded PDF is stored on the QuickBooks bill or receipt as the source.
Action·Document

Reference

Field mapping for Qonto → QuickBooks

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

Transaction fields

5 fields flow from Qonto into QuickBooks.

Qonto field	Label		QuickBooks field	Label
transaction.amount	Amount	→	Amount	Amount
transaction.currency	Currency	→	CurrencyRef	Currency
transaction.emitted_at	Booking date	→	TxnDate	Transaction date
transaction.label	Description	→	Memo	Memo
transaction.transaction_id	Transaction id	→	PrivateNote	Source id

Invoice fields

5 fields flow from Qonto into QuickBooks.

Qonto field	Label		QuickBooks field	Label
supplier_invoice.invoice_number	Invoice number	→	DocNumber	Doc number
supplier_invoice.issue_date	Issue date	→	TxnDate	Bill date
supplier_invoice.due_date	Due date	→	DueDate	Due date
supplier_invoice.total_amount.currency	Currency	→	CurrencyRef	Currency
supplier_invoice.attachment_id	Source PDF	→	PrivateNote	Source id

Connect Qonto and QuickBooks 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 QuickBooks For Review inbox. 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 QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online 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 QuickBooks Online.
- AuthConnect
- First syncup to an hour

How Qonto and QuickBooks 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 QuickBooks inbox
Well forwards the extracted document to your QuickBooks email-in address; QuickBooks reads bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks from it and you review and post. No write credential to QuickBooks 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 QuickBooks on Well

01What Qonto data does Well pull into QuickBooks?: Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks into QuickBooks with the original Qonto record ID kept on the entry.
02Will every Qonto record post to QuickBooks 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 QuickBooks email-in address and QuickBooks 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.
03How does Well prevent duplicates when posting Qonto records to QuickBooks?: Well maintains a sync marker against Qonto so each window only pulls records strictly newer than the last successful sync; the Qonto record ID is then tracked into QuickBooks 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 QuickBooks entry rather than duplicating it.
04Can I customise which Qonto fields are sent to QuickBooks?: The default mapping covers every Qonto field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.
05What happens if a Qonto record fails to post to QuickBooks?: When a record fails to post to QuickBooks (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.
06How does Well authenticate with Qonto and QuickBooks?: 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 QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. 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.