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

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

Does Well handle multi-currency records between Qonto and Bill.com?

Qonto carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.

How does Well prevent duplicates when posting Qonto records to Bill.com?

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 Bill.com 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 Bill.com entry rather than duplicating it.

Can I customise which Qonto fields are sent to Bill.com?

The default mapping connects each Qonto record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.

How does Well authenticate with Qonto and Bill.com?

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

Qonto to Bill.com

AvailableNative · QontoNative · Bill.com

Connect Qonto to Bill.com with Well

Every Qonto outbound transfer links to its bill inside Well on amount, vendor, and date; resulting bills reach Bill.com with the audit trail attached.

Connect both toolsView all integrations

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

Bill.com

Target

The Bill.

Why this pair

Qonto runs French SMB banking with native supplier-invoice upload; Bill.

com runs US-style AP with approval workflows and scheduled payments. Connecting Qonto to Bill. com through Well surfaces each Qonto supplier invoice and forwards the PDF to Bill. com's email-in. Bill. com creates the bill for your approval workflow; your team reconciles against the Qonto outflow once the payment lands. Qonto polls every fifteen minutes for new supplier invoices.

What Well does between Qonto and Bill.com

One-way: Qonto into Well into Bill.com
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

Mailchimp Intl.

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

VendorMailchimp Intl.
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 entityMailchimp Intl.
Tax idIE3404552KH
Domainmailchimp.com
Ledger account6238 · Email mktg

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorMailchimp Intl.
Amount€1,284.00
Ledger6238 · Email mktg
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

Match Qonto debits to Bill.com scheduled payments.

01Featured

Match debits to bills you have in flight

Each Qonto debit is checked against your bill records inside Well on payee, amount, scheduled date, and currency. Above the auto-link threshold the bank line is linked inside Well; AP sees the link in the document Well forwards to Bill.com, with the receipt attached for the next vendor audit.

Flag unauthorised vendor payments

If a Qonto debit appears for a vendor not on your approved list inside Well, the match is stopped and the workspace owner is paged. The debit sits on a review queue with the proposed new vendor alongside; once confirmed, Well treats the next debit from the same counterparty consistently before forwarding to Bill.com.

Close the loop on returned payments

When a Qonto payment is returned (insufficient funds, account closure, fraud claim), Well flags the reversal inside its own ledger, reopens the bill for rescheduling, and routes a notification to the AP owner so the reschedule decision in Bill.com has the original reason in context.

Surface duplicate payments before the second debit

If a bill flips to scheduled twice in error, Well watches the next Qonto debit window for a second payment to the same vendor with the same amount and surfaces the conflict before AP confirms the second action in Bill.com.

6 signals and actions across Qonto and Bill.com

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
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
Attach the source PDF to the Bill.com bill
Driven by Qonto bank transactions and supplier invoices. The forwarded PDF is the bill record itself in Bill.com's inbox.
Action·Document
Route the bill through Bill.com's multi-step approval policy
Driven by Qonto bank transactions and supplier invoices. The created bill enters your Bill.com approval policy and is routed to the assigned approver roles in sequence; each approver reviews the coding and signs off before the bill is cleared for AP. Well never approves the bill, picks a funding account, or releases payment.
Action·Invoice
Create a bill in Bill.com inbox
Driven by Qonto bank transactions and supplier invoices. Well forwards the PDF to your Bill.com inbox; Bill.com's IVA reads the vendor, invoice number, amount, and due date into a new bill and drops it straight into your AP approval policy.
Action·Invoice
Resolve a Bill.com vendor from the bill
Driven by Qonto bank transactions and supplier invoices. Bill.com's IVA OCR resolves the vendor name from the document. You complete the vendor setup (banking, tax) separately.
Action·Company

Reference

Field mapping for Qonto → Bill.com

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

Transaction fields

5 fields flow from Qonto into Bill.com.

Qonto field	Label		Bill.com field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.emitted_at	Booking date	→	process_date	Process date
transaction.label	Description	→	memo	Memo
transaction.transaction_id	Transaction id	→	payment_id	Payment id

Invoice fields

5 fields flow from Qonto into Bill.com.

Qonto field	Label		Bill.com field	Label
supplier_invoice.invoice_number	Invoice number	→	invoice_number	Invoice number
supplier_invoice.issue_date	Issue date	→	invoice_date	Invoice date
supplier_invoice.due_date	Due date	→	due_date	Due date
supplier_invoice.total_amount.currency	Currency	→	currency	Currency
supplier_invoice.attachment_id	Source PDF	→	external_id	External id

Connect Qonto and Bill.com 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 Bill.com inbox awaiting approval. The first batch of bank lines flows into the review queue alongside candidate scheduled payments; once you confirm the rule, Qonto debits auto-link above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Bill.com
In Bill.com, open Settings > Developer > API keys and create a key paired with your developer ID. Paste the key into Well; Bill.com's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
- AuthConnect
- First sync~10 min

How Qonto and Bill.com 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 Bill.com inbox
Well forwards the extracted document to your Bill.com email-in address; Bill.com reads bills via email-in inbox, with vendor, invoice number, amount, and related records from it and you review and post. No write credential to Bill.com 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 Bill.com on Well

01Will every Qonto record post to Bill.com 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 Bill.com email-in address and Bill.com 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.
02What happens to historical Qonto data when I first connect to Bill.com?: 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 Bill.com ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Bill.com entries instead of duplicating them.
03Does Well handle multi-currency records between Qonto and Bill.com?: Qonto carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.
04How does Well prevent duplicates when posting Qonto records to Bill.com?: 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 Bill.com 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 Bill.com entry rather than duplicating it.
05Can I customise which Qonto fields are sent to Bill.com?: The default mapping connects each Qonto record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.
06How does Well authenticate with Qonto and Bill.com?: 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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Bill.com hosts outside the EU; Well processes records per the storage region configured for your workspace.