Bring Pennylane invoices into Qonto

About Pennylane and Qonto

Pennylane

Source

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

Qonto

Target

Qonto is two separate authorisations, not one.

1. 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. 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. 3

   Connect Qonto

   Click Connect with Qonto; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.

   • AuthOAuth 2.0
   • First sync~30 min

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