What Qonto data does Well pull into Xero?

Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes draft bills via email-in, with contact, dates, totals, line items, and tax type extracted by Hubdoc into Xero with the original Qonto record ID kept on the entry.

How often does Qonto data sync to Xero?

Well polls the Qonto API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Xero write happens at the end of the window, never mid-sync.

How does Well match Qonto records to entries in Xero?

Qonto transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.

What happens to historical Qonto data when I first connect to Xero?

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

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

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

How does Well authenticate with Qonto and Xero?

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

Qonto to Xero

AvailableNative · QontoNative · Xero

Connect Qonto to Xero with Well

Stop reconciling by hand: Qonto bank lines reach Xero as drafts with the counterparty resolved and the receipt attached. You confirm and post in seconds.

Connect both toolsView all integrations

Qonto

Source

The Qonto connection works on supplier invoices in both directions.

Xero

Target

The Xero integration connects Well to your accounting platform for bidirectional data flow.

Why this pair

Qonto runs on EU banking rails in EUR and Xero closes books in GBP, AUD, NZD, or EUR depending on entity.

Connecting Qonto to Xero through Well matches each Qonto transaction inside its own ledger with cost-centre and FX context attached and the original Qonto reference preserved, then forwards the matched document to Xero's email-in. Hubdoc creates the draft bill; your team confirms tracking category and tax type in Xero.

What Well does between Qonto and Xero

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

Atlassian B.V.

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

VendorAtlassian B.V.
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 entityAtlassian B.V.
Tax idNL824921788B01
Domainatlassian.com
Ledger account6064 · SaaS

Confidence97%

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

Post

post as draft bills

Create a draft bill in Xero

auto-posted

posted

TypeBill
VendorAtlassian B.V.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Xero

Action in Xero

1 compatible with this trigger

Create a draft bill in Xero

Reconcile Qonto transactions to Xero 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 Xero's email-in address, so the original PDF lands with the invoice.

Resolve the supplier against Xero contacts

Well matches the supplier on a Qonto invoice against the contacts already in Xero and carries the resolved company onto the forwarded document.

Collapse duplicate suppliers

Supplier names that resolve to one company are treated as the same business inside Well before the forward, so Xero keeps one clean contact.

Keep the accountant's ledger untouched

Well forwards resolved invoices to Xero's email-in and never posts journal entries through its API, so the ledger stays your accountant's.

6 signals and actions across Qonto and Xero

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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Invoice
Attach the file to the Xero record
Driven by Qonto bank transactions and supplier invoices. Hubdoc stores the original PDF on the draft bill as the source attachment.
Action·Document
Pre-fill the Xero tax rate from the document
Driven by Qonto bank transactions and supplier invoices. Hubdoc extracts the tax type and applies it on the draft bill. You confirm before posting.
Action·Invoice
Create a draft bill in Xero
Driven by Qonto bank transactions and supplier invoices. Well forwards the PDF to your Xero email-in address; Xero creates a draft bill via Hubdoc with contact, dates, totals, line items, and tax type pre-filled. You review and post.
Action·Invoice
Resolve a Xero contact from the document
Driven by Qonto bank transactions and supplier invoices. Hubdoc reads the contact name and trading address off the PDF to match the vendor. You confirm or merge on first sight.
Action·Company

Reference

Field mapping for Qonto → Xero

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

Transaction fields

5 fields flow from Qonto into Xero.

Qonto field	Label		Xero field	Label
transaction.amount	Amount	→	Total	Amount
transaction.currency	Currency	→	CurrencyCode	Currency
transaction.emitted_at	Booking date	→	Date	Transaction date
transaction.label	Description	→	Reference	Reference
transaction.transaction_id	Transaction id	→	BankTransactionID	Bank line id

Invoice fields

5 fields flow from Qonto into Xero.

Qonto field	Label		Xero field	Label
supplier_invoice.invoice_number	Invoice number	→	InvoiceNumber	Invoice number
supplier_invoice.issue_date	Issue date	→	Date	Bill date
supplier_invoice.due_date	Due date	→	DueDate	Due date
supplier_invoice.total_amount.currency	Currency	→	CurrencyCode	Currency
supplier_invoice.attachment_id	Source PDF	→	Reference	Reference

Connect Qonto and Xero 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.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Qonto's supplier invoices and their attachments and the the Xero draft bills queue populated by Hubdoc. 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 Xero
Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Qonto and Xero 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 Xero inbox
Well forwards the extracted document to your Xero email-in address; Xero reads draft bills via email-in, with contact, dates, totals, and related records from it and you review and post. No write credential to Xero 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 Xero on Well

01What Qonto data does Well pull into Xero?: Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes draft bills via email-in, with contact, dates, totals, line items, and tax type extracted by Hubdoc into Xero with the original Qonto record ID kept on the entry.
02How often does Qonto data sync to Xero?: Well polls the Qonto API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Xero write happens at the end of the window, never mid-sync.
03How does Well match Qonto records to entries in Xero?: Qonto transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.
04What happens to historical Qonto data when I first connect to Xero?: 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 Xero ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Xero entries instead of duplicating them.
05How does Well prevent duplicates when posting Qonto records to Xero?: 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 Xero 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 Xero entry rather than duplicating it.
06How does Well authenticate with Qonto and Xero?: 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 Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Qonto hosts in the EU and Xero hosts outside the EU; Well processes records per the storage region configured for your workspace.