What Qonto data does Well pull into Pennylane?

Well polls the Qonto API on a fixed cadence and pulls your organization, its bank accounts and balances, transactions, and supplier invoices with 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 hourly, which fits Qonto's rate-limit envelope and keeps the downstream match window inside the same business day. The hourly pull respects Qonto's rate limits and feeds Pennylane once per window with the batch's confidence outcomes already resolved.

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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Pennylane is encrypted at rest and handled in line with GDPR.

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

Qonto is two separate authorisations, not one.

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

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 ledger lines.

01Featured

Close books in days

Transactions arrive already matched to invoices, so month-end takes days instead of weeks.

No more CSV round-trips

Remove the export, clean, re-import loop between Qonto and Pennylane for good.

Accountant-ready entries

Hand over clean journal entries with the source document attached to each line.

Single audit trail

Trace every booked entry back to the Qonto transaction and the invoice that backs it.

10 signals and actions across Qonto and Pennylane

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
Business account balance updated
Pulls from the Qonto banking API. Well monitors changes in your Qonto business accounts to keep balances synchronized. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Account
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. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
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. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
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
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

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

24 agent skills run on Qonto and Pennylane.

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 Pennylane 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 Pennylane 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 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. 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 Pennylane on Well

01What Qonto data does Well pull into Pennylane?: Well polls the Qonto API on a fixed cadence and pulls your organization, its bank accounts and balances, transactions, and supplier invoices with 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 hourly, which fits Qonto's rate-limit envelope and keeps the downstream match window inside the same business day. The hourly pull respects Qonto's rate limits and feeds Pennylane once per window with the batch's confidence outcomes already resolved.
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'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 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 in transit under TLS 1.3. Anything Well holds between Qonto and Pennylane is encrypted at rest and handled in line with GDPR.