What Qonto data does Well pull into Pennylane?

Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR into Pennylane with the original Qonto record ID kept on the entry.

How often does Qonto data sync to Pennylane?

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 Pennylane write happens at the end of the window, never mid-sync.

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

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

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

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

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

When a record fails to post to Pennylane (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 Pennylane?

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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Both Qonto and Pennylane host their data in the EU, so both ends of the integration sit within EU jurisdiction.

Qonto to Pennylane

AvailableNative · QontoNative · Pennylane

Connect Qonto to Pennylane with Well

Stop reconciling by hand: Qonto bank lines reach Pennylane 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.

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

Why this pair

Qonto and Pennylane are both built for the French SMB stack, but they sit on opposite ends of the workflow.

Qonto sits on the bank line, Pennylane on the journal. Connecting them through Well means every Qonto transaction is matched inside Well against your existing invoices, counterparties, and prior categorisation history. The matched documents are then forwarded to Pennylane's supplier or customer email-in address so Pennylane creates the invoice with VAT, date, and amount pre-filled. No CSV exports, no double-keyed entries, no broken VAT splits.

What Well does between Qonto and Pennylane

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

Notion Labs Inc.

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

VendorNotion Labs Inc.
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 entityNotion Labs Inc.
Tax idEU826053662
Domainnotion.so
Ledger account6064 · SaaS

Confidence97%

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

Post

post as supplier and customer invoices

Create a supplier invoice in Pennylane

auto-posted

posted

TypeSupplier invoice
VendorNotion Labs Inc.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

Reconcile Qonto transactions to Pennylane entries with EU residency intact.

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 Pennylane's email-in inbox with the receipt attached for your one-click confirmation.

Reconcile deposits to expected receivables

Qonto deposits are checked against your open sales invoices inside Well. The match runs on amount and date proximity inside the same customer, so a partial payment or an aggregated weekly deposit still resolves to the right invoices before the matched document reaches Pennylane.

Split card statement lines into per-employee context

Aggregated Qonto card statement lines from corporate cards are decomposed inside Well into per-employee, per-merchant documents. Each per-employee document is forwarded to Pennylane separately, so expense ownership stays attached to the underlying transaction in the target ledger.

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

7 signals and actions across Qonto and Pennylane

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 Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
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 Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
Create a supplier invoice in Pennylane
Driven by Qonto bank transactions and supplier invoices. Well forwards the extracted PDF to Pennylane's supplier inbox; Pennylane creates the supplier invoice with amount, VAT, and date pre-filled.
Action·Invoice
Resolve a Pennylane customer from the invoice
Driven by Qonto bank transactions and supplier invoices. Pennylane reads the customer name off the outbound invoice for collections. You confirm on first sight.
Action·Company
Resolve a Pennylane supplier from the document
Driven by Qonto bank transactions and supplier invoices. Pennylane's OCR resolves the supplier name from the PDF. You confirm or correct the match on first sight.
Action·Company
Create a customer invoice in Pennylane
Driven by Qonto bank transactions and supplier invoices. Well forwards the document to Pennylane's collections address; Pennylane creates the customer invoice with the same OCR pre-fill.
Action·Invoice
Attach the source document to the Pennylane record
Driven by Qonto bank transactions and supplier invoices. The PDF Well forwards is stored as the source attachment on whichever invoice Pennylane creates from it.
Action·Document

Reference

Field mapping for Qonto → Pennylane

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

Transaction fields

5 fields flow from Qonto into Pennylane.

Qonto field	Label		Pennylane field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.emitted_at	Booking date	→	date	Execution date
transaction.label	Description	→	label	Label
transaction.transaction_id	Transaction id	→	external_reference	Source id

Invoice fields

5 fields flow from Qonto into Pennylane.

Qonto field	Label		Pennylane field	Label
supplier_invoice.invoice_number	Invoice number	→	label	Reference
supplier_invoice.issue_date	Issue date	→	date	Invoice date
supplier_invoice.due_date	Due date	→	deadline	Due date
supplier_invoice.total_amount.currency	Currency	→	currency	Currency
supplier_invoice.attachment_id	Source PDF	→	external_reference	Source id

Connect Qonto and Pennylane 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 Pennylane Purchases tab and the customer-invoice collections list. 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 Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane'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 Pennylane 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. Both providers host in the EU, so both ends of the integration sit within EU jurisdiction.

OAuth 2.0EU residency on both sidesGDPR-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 Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane 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 Pennylane on Well

01What Qonto data does Well pull into Pennylane?: Well polls the Qonto API on a fixed cadence and pulls supplier invoices and their attachments. Well resolves and scores each counterparty, then writes supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR into Pennylane with the original Qonto record ID kept on the entry.
02How often does Qonto data sync to Pennylane?: 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 Pennylane write happens at the end of the window, never mid-sync.
03What happens to historical Qonto data when I first connect to Pennylane?: 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 Pennylane ledger, and re-running the backfill is safe because Well tracks the Qonto record IDs and updates existing Pennylane entries instead of duplicating them.
04How does Well prevent duplicates when posting Qonto records to Pennylane?: 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 Pennylane 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 Pennylane entry rather than duplicating it.
05What happens if a Qonto record fails to post to Pennylane?: When a record fails to post to Pennylane (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 Pennylane?: 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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Both Qonto and Pennylane host their data in the EU, so both ends of the integration sit within EU jurisdiction.