How often does Pennylane data sync to Qonto?

Pennylane pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Qonto within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Pennylane record post to Qonto automatically?

Not always. Within seconds of Pennylane firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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 match Pennylane records to entries in Qonto?

Well scores every candidate match between Pennylane records and existing Qonto entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Qonto updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

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

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

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

When a record fails to post to Qonto (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 Pennylane record. Nothing silently drops.

How does Well authenticate with Pennylane and Qonto?

Pennylane'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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted at rest and in transit under TLS 1.3. Both Pennylane and Qonto host their data in the EU, so both ends of the integration sit within EU jurisdiction.

Pennylane to Qonto

AvailableNative · PennylaneNative · Qonto

Connect Pennylane to Qonto with Well

Move Pennylane invoices and contacts through Well and into Qonto as supplier invoices, with the audit trail kept on every record.

Connect both toolsView all integrations

Pennylane

Source

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

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

Connect Pennylane to Qonto through Well so records flow without manual rework.

What Well does between Pennylane and Qonto

One-way: Pennylane into Well into Qonto
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Pennylane

5 events · pick one

Well engine·recipe·When a Pennylane customer invoice is read

Source

from payment · live webhook

Aldercroft Trading

via Pennylane

Invoice

When a Pennylane customer invoice is read

INV-1284 · 22 Apr 2026€1,284.00

Extract

5 fields read from Pennylane

5 fields read

CustomerAldercroft Trading
Invoice numberINV-1284
Issue date22 Apr 2026
Total€1,284.00
CurrencyEUR

Enrich

against your historical record graph

4 fields added

Customer recordAldercroft Trading
Domainaldercroft.co.uk
Tax idGB987604123
Sales journalVE · 2026

Confidence97%

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

Post

reconcile as supplier invoices

Push a supplier invoice PDF to Qonto

auto-posted

posted

TypeSupplier invoice
VendorAldercroft Trading
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

9 signals and actions across Pennylane and Qonto

When a Pennylane supplier invoice is read
Pulls Pennylane supplier invoices with the supplier, amount, due date, and VAT. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Pennylane credit note is read
Captures Pennylane credit notes with the linked invoice, totals, and VAT so refunds reconcile correctly. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Pennylane transaction is read
Captures the bank transactions Pennylane holds with amount, date, and counterparty. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Transaction
When a Pennylane bank account is read
Pulls the bank accounts linked in Pennylane with currency and holder detail. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Account
When a Pennylane invoice attachment is read
Picks up the source PDF attached to a Pennylane invoice as a document. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Document
When a Pennylane customer invoice is read
Pulls Pennylane customer invoices with line items, customer, totals, and VAT. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When a Pennylane payment is read
Reads the payment recorded against a Pennylane invoice with method and amount. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Payment method
When a Pennylane customer is read
Pulls Pennylane company customers with name, registration number, and billing detail. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
Push a supplier invoice PDF to Qonto
Well POSTs the supplier invoice PDF to Qonto's /v2/supplier_invoices/bulk endpoint via OAuth so the invoice appears under your Qonto supplier invoices.
Action·Document

Reference

Field mapping for Pennylane → Qonto

14 fields across 3 record types, open to see the full table.

Invoice fields

6 fields flow from Pennylane into Qonto.

Pennylane field	Label		Qonto field	Label
invoice.amount.total	Total amount	→	total_amount	Total
invoice.currency	Currency	→	currency	Currency
invoice.date.issue_date	Invoice date	→	issue_date	Issue date
invoice.deadline.due_date	Due date	→	due_date	Due date
invoice.invoice_number	Reference	→	invoice_number	Invoice number
invoice.vat_amount.tax	VAT	→	tax_amount	Tax

Transaction fields

5 fields flow from Pennylane into Qonto.

Pennylane field	Label		Qonto field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.date.created	Execution date	→	emitted_at	Booking date
transaction.label.description	Label	→	label	Label
transaction.id	Transaction id	→	transaction_id	Transaction id

Company fields

3 fields flow from Pennylane into Qonto.

Pennylane field	Label		Qonto field	Label
customer.name	Customer name	→	supplier_name	Supplier
customer.website	Website	→	supplier_website	Website
customer.vat_number.tax_id	VAT number	→	supplier_tax_id	Tax id

Connect Pennylane and Qonto in three steps.

1
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane'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 Pennylane's supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server and the the Qonto supplier-invoices section. Match candidates are scored on counterparty, amount, date, and reference; above 85% confidence the link posts automatically, below it the candidate set queues for sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Qonto
Click Connect with Qonto; you approve the connection inside Qonto and authorise the supplier_invoice.write scope so Well can POST PDFs to /v2/supplier_invoices. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
- First sync~30 min

How Pennylane and Qonto stay secure with Well

Well connects to Pennylane through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Pennylane secret; the server refreshes its own tokens on each session. Both providers host in the EU, so both ends of the integration sit within EU jurisdiction.

MCP server authEU residency on both sidesGDPR-aligned

Scopes Well requestswellapp.ai/v1/mcps/pennylane/mcp

Read Pennylane records
Scoped to supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server. No access to anything else in your Pennylane account.
granted
Post approved records to Qonto
Over Qonto's API, scoped to supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices you have approved (case-by-case or via a per-rule auto-post threshold).
granted
Modify or delete Pennylane records
Not granted. Pennylane 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 Pennylane’s admin panel.

Frequently asked questions about Pennylane and Qonto on Well

01How often does Pennylane data sync to Qonto?: Pennylane pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Qonto within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02Will every Pennylane record post to Qonto automatically?: Not always. Within seconds of Pennylane firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well posts the record directly to Qonto over the connected API and verifies the response before marking it done. 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 match Pennylane records to entries in Qonto?: Well scores every candidate match between Pennylane records and existing Qonto entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Qonto updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04What happens to historical Pennylane data when I first connect to Qonto?: Pennylane exposes seven years of accounting history 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 Qonto ledger, and re-running the backfill is safe because Well tracks the Pennylane record IDs and updates existing Qonto entries instead of duplicating them.
05What happens if a Pennylane record fails to post to Qonto?: When a record fails to post to Qonto (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 Pennylane record. Nothing silently drops.
06How does Well authenticate with Pennylane and Qonto?: Pennylane'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, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted at rest and in transit under TLS 1.3. Both Pennylane and Qonto host their data in the EU, so both ends of the integration sit within EU jurisdiction.