QontoIntegrations · Business banking

Connect Qonto to Well

Read your Qonto organisation, bank accounts, balances, transactions, and supplier invoices with their PDF attachments into Well over OAuth, and file approved supplier-invoice PDFs back to Qonto. It is the one connector Well writes to directly through a provider API.

What flows between Well and Qonto

Well writes reconciled bank transaction, bank account, balance back to Qonto after they clear your review queue, with the source-record link preserved. Use Qonto as the destination for entries enriched across your other connected tools.

From QontoIn Well
Bank transaction
Invoice
Bank account
Workspace account
Balance
Cash position
Supplier invoice
Workspace invoice
Approved invoice PDF
Qonto supplier invoice
Qonto
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Qonto ⇄ Well

6 triggers and actions in Qonto.

  • When a supplier invoice is uploaded to Qonto

    Detects supplier invoices uploaded into the Qonto invoicing inbox.

    Trigger·Invoice
  • When a Qonto supplier invoice is updated

    Picks up any update to a Qonto supplier invoice the next time Well checks for updates.

    Trigger·Invoice
  • New transaction posted to Qonto account

    Well pulls transaction details directly from your Qonto account when a new entry is posted.

    Trigger·Transaction
  • Business account balance updated

    Well monitors changes in your Qonto business accounts to keep balances synchronized.

    Trigger·Account
  • New bank account connected in Qonto

    When a new business account appears on your Qonto organization, Well starts tracking its activity in your workspace.

    Trigger·Account
  • 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

What Well does with your Qonto connection

Connect

Connect Qonto over OAuth (MCP DCR via Well): Well registers a client through Qonto's OAuth Dynamic Client Registration and you approve on Qonto's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings bank transaction, bank account, and balance in from Qonto through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Qonto entity into invoice, workspace account, and cash position, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Qonto lands as invoice, workspace account, and cash position you can search, chart, and automate, and approved records flow back to Qonto once they clear your review queue.

Questions Qonto unlocks

Ask in plain language. Well answers from your connected Qonto connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Qonto connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Qonto connection…

40 agent skills run on Qonto.

Each one answers a question from live Qonto data. The required ones return nothing until a source like it is connected.

Needs a source like Qonto

Runway

Know how many months of cash you have at your current burn, with both sides of the division shown.

Cash position

Know how much cash you hold right now, with the accounts counted and the ones left out both stated.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Rank clients by LTV

Find out what each customer is worth over its whole life, ranked from the most valuable down.

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 draft invoice in Well, in your customer's design, PDF attached.

Burn rate

Know what you spend in an average month over a window you can see, with the months that carried no spend counted.

Recurring revenue

Know what you can count on earning each month, averaged over real months.

Cash forecast

See the settled month-end cash series and where the line goes from the last complete month.

Cash flow bridge

See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.

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 from open to sent to your accounting tool.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Board pack

The board numbers in one pass, each with its scope and its window stated.

Subscription spend

See which suppliers you pay on a schedule, what each costs a month, and how that spend moved.

Prefill Form 1120

Get page 1 of your 1120 back as a PDF with your own book figures already in the boxes, and a list of every box left for your preparer.

Prefill Form 1099-NEC

Get one 1099-NEC per contractor back as a PDF with your own posted figures already in box 1, and the list of payees you cannot file for yet.

Unposted and blocked

See what in a month has not reached the ledger, and which pile each item sits in.

VAT radar

See the net VAT your posted ledger shows for a quarter and which invoices to fix first.

Connect Qonto in three steps

  1. 01

    Authorise Qonto over OAuth

    Select Qonto in Well's Connections panel and complete the OAuth authorisation. You approve the offline_access, organization.read, supplier_invoice.read, and client_invoices.read scopes on Qonto's screen; no key is pasted into Well. Filing approved PDFs back is a separate Qonto connector with its own approval and its own supplier_invoice.write grant.

    • AuthOAuth 2.0: DCR to read, authorisation code to write
    • Read scopesoffline_access, organization.read, supplier_invoice.read, client_invoices.read
    • Write scopesupplier_invoice.write, on a separate approval
    • Coversorganization.read: bank accounts, balances, transactions
    • WritePOST supplier invoice from PDF, on the separate write connector
  2. 02

    Map your entities

    Well reads your Qonto organisation, bank accounts, balances, transactions, and supplier invoices with their PDF attachments into the workspace as structured records. organization.read covers the account and transaction side, including each account's payment details; the supplier-invoice scope covers the invoices and their documents.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Once a supplier-invoice PDF clears review, Well files it back to Qonto under the separate write connector's own grant, through the bulk supplier-invoice endpoint, and Qonto creates the invoice. That push is the only write Well makes: it cannot mark a transaction, move money, or touch cards. Qonto stays the system of record.

    • First syncstarts as soon as connect completes

The OAuth handshake completes in about a minute. Accounts, transactions, and supplier invoices read on connect; approved invoice PDFs file back as they clear your queue. Qonto developer docs.

How Qonto stays secure with Well

Qonto authorises over OAuth, so Well holds no Qonto API key. The connection you approve carries the offline_access, organization.read, supplier_invoice.read, and client_invoices.read scopes. organization.read is what authorises the account side, so Well reads your organisation, bank accounts, balances, and transactions alongside your supplier and client invoices and their PDF attachments. Filing an approved supplier-invoice PDF back to Qonto is a separate connector with its own approval and its own grant; neither can mark a transaction, initiate a transfer, or touch cards.

OAuth (MCP DCR via Well)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsapi.wellapp.ai/v1/mcps/qonto/mcp
  • Read Qonto records

    Resources the Qonto MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve bank transaction, bank account, balance, and supplier invoice across your stack

    Match identifiers in Qonto against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Post approved records to Qonto

    Over Qonto's API, only records you've approved (case-by-case or via a per-rule auto-post threshold).

    granted
  • Store Qonto passwords or session cookies

    Authentication runs through OAuth (MCP DCR via Well) tokens we never see.

    refused
Disconnect any time from Well settings or Qonto’s admin panel.

Frequently asked questions about Qonto and Well

How do I connect Qonto, and what does Well ask for?

Choose Qonto in Well's Connections panel and authorise over OAuth, which you approve on Qonto's own screen. The connection carries the offline_access, organization.read, supplier_invoice.read, and client_invoices.read scopes. organization.read is the one that covers your organisation, bank accounts, balances, and transactions; supplier_invoice.read and client_invoices.read cover reading your supplier and client invoices. Filing approved PDFs back to Qonto is a separate connector with its own approval. Well holds no Qonto API key.

What does Well actually read from Qonto?

Well reads your Qonto organisation, your bank accounts and their balances, your transactions, and your supplier invoices with their PDF attachments. Records land in the workspace structured, with the source document attached where Qonto holds one. organization.read is what authorises the account and transaction side, so the feed is your Qonto activity, not the supplier invoices alone. Well can read all of it and change none of it.

Qonto is the one connector Well writes back to over an API. How does that work?

After a supplier-invoice PDF clears your review, Well files the document to Qonto through its bulk supplier-invoice endpoint, and Qonto creates the supplier invoice from it. This is a genuine OAuth API write, not an email-in handoff, which makes Qonto the only direct write target in the cohort. Filing that approved PDF is the whole write: Well cannot mark a Qonto transaction, attach a document to one, initiate a transfer, or touch cards.

Will Well match my Qonto transactions against my invoices?

Yes. Well reads your Qonto transactions and matches them against your invoices automatically, in both directions. Confident matches are linked without you doing anything; borderline ones are queued for your review. Bank rows with no invoice behind them, such as fees, salaries, and internal transfers, stay unmatched, which is what they should be. The matching lives in Well; nothing is written back to the transaction in Qonto.

How fresh is the Qonto data Well holds?

Well reads from Qonto in the background and folds new and updated records into the workspace as it picks them up, with the first connect bringing in your existing accounts, transactions, and supplier invoices. You can query what has already arrived while the rest fills in. Qonto stays the system of record; Well keeps a queryable copy and files approved invoice PDFs back.

If I disconnect Qonto, what unwinds?

Disconnect Qonto in Well and the OAuth token is dropped, so Well stops reading your accounts, transactions, and supplier invoices, and can no longer file anything back. Because the only write is a supplier-invoice PDF you approved, there is nothing else to reverse. Records Well already mirrored stay in your workspace, and the supplier invoices created in Qonto remain in Qonto.

Qonto

Ready to connect Qonto?

Connect once. Every bank transaction, bank account, balance from Qonto becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.