Will every Qonto record post to Bill.com 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 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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Bill.com is encrypted at rest and handled in line with GDPR.

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

Qonto is two separate authorisations, not one.

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

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

Forward a supplier invoice with its PDF

Well reads the supplier invoice and its attachment from Qonto and forwards the document to Bill.com'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 Bill.com.

Collapse duplicate suppliers

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

Keep the source invoice attached

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

9 signals and actions across Qonto and Bill.com

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
Business account balance updated
Pulls from the Qonto banking API. Well monitors changes in your Qonto business accounts to keep balances synchronized.
Trigger·Account
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
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 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
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; 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 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

24 agent skills run on Qonto and Bill.com.

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 Bill.com 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 Bill.com 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 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. 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 Bill.com on Well

01Will every Qonto record post to Bill.com 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 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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Bill.com is encrypted at rest and handled in line with GDPR.