Integrations · Accounting

Connect Kolecto to Well

Sync Kolecto collection records, client status, and reminder activity into Well. Reconciled actions are prepared for write-back once Kolecto's write surface lands.

What Well writes to Kolecto

Well writes reconciled invoice, supplier, attachment to Kolecto after they clear your review queue, with the source-record link preserved. Use Kolecto as the destination for entries enriched across your other connected tools.

In WellTo Kolecto
Payable
Invoice
Vendor
Supplier
Source PDF
Attachment
Kolecto logo
Sync mode
incremental polling
Refresh
scheduled
Direction
Well → Kolecto

3 actions in Kolecto.

  • Create a supplier invoice in Kolecto

    Well forwards the PDF to your Kolecto collection address; Kolecto creates a supplier invoice with supplier, date, and amount pre-filled for your review.

    Action·Invoice
  • Attach the source document to the Kolecto record

    The forwarded PDF is stored on the Kolecto supplier invoice as the source.

    Action·Document
  • Resolve a Kolecto supplier from the invoice

    Kolecto's OCR resolves the supplier name from the PDF. You confirm or correct the match on first sight.

    Action·Company

What Well does with your Kolecto connection

Connect

Connect Kolecto over OAuth 2.0: you approve on Kolecto's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Kolecto is a delivery target, not a source, so Well pulls nothing in. Once a record clears review, Well's pipeline can create a supplier invoice in Kolecto.

Enrich

Before delivery Well reconciles and enriches each document, resolving the supplier invoice, attachment, and supplier so what reaches Kolecto arrives matched and carries its full audit trail.

Available

Well forwards the PDF to your Kolecto collection address; Kolecto creates a supplier invoice with supplier, date, and amount pre-filled for your review.

Questions Kolecto unlocks

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

Ask Well

Ask anything about your Kolecto connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Kolecto connection…

Connect Kolecto in three steps

  1. 01

    Authorise Kolecto via OAuth 2.0

    Open Well's Connections panel, find Kolecto, and click Connect. You're redirected to Kolecto's authorize screen, where you'll see the exact scopes Well requests. Approve, and you land back in Well with the connection live.

    • AuthOAuth 2.0
    • Accessread + write
  2. 02

    Map your entities

    Well reads collection record, client, and reminder from Kolecto on first connect and brings each record into your workspace using the canonical mappings defined in Well's data-views layer.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Use the data: ask questions in conversation, build records tables, and let agents post reconciled entries back to Kolecto once they clear your review queue. Kolecto records are live in your workspace immediately.

    • First syncstarts as soon as connect completes

OAuth handshake typically under a minute. Backfill of historical records runs in the background; you can use Well in conversation against incoming records while the backfill completes.

How Kolecto stays secure with Well

Well calls Kolecto's API with an OAuth 2.0 token scoped to collection record, client, and reminder. Kolecto's consent screen shows you the same list before you approve. Kolecto enforces scope server-side; authentication runs entirely through Kolecto's authorize screen so Well never sees your credentials. Tokens refresh automatically; rotation is one click away.

OAuth 2.0Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requests
  • Read Kolecto records

    Endpoints the Kolecto API token grants, scoped by your consent.

    granted
  • Resolve collection record, client, and reminder across your stack

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

    granted
  • Deliver documents to your Kolecto inbox

    Well forwards approved documents to your Kolecto email-in address; Kolecto drafts the record and you post it. No write credential to Kolecto is requested.

    granted
  • Store Kolecto passwords or session cookies

    Authentication runs through OAuth 2.0 tokens we never see.

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

Frequently asked questions about Kolecto and Well

Open Connections in Well, pick Kolecto, and click Connect. You're redirected to Kolecto's OAuth screen, you approve the scopes Well requests, and you land back in Well with the connection live. The whole flow runs under a minute and never requires you to handle client credentials.

Well brings in collection record, client, and reminder from Kolecto and reshapes each entity into your workspace: collection record becomes receivable; client becomes customer. Every record arrives with the source identifier preserved, so Kolecto stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well brings in Kolecto collection records, reminder cadences, and client-payment status, links each record to the matching customer in Well, and queues reconciled actions for write-back. Posting back to Kolecto ships when the write surface is enabled; queries about collection status work today.

Every workspace receivable built from Kolecto carries the source collection record identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Kolecto record; from Kolecto, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

Well polls Kolecto regularly for collection record, client, and reminder. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on Kolecto's side stays modest.

Open Connections > Kolecto in Well and click Disconnect. Well calls Kolecto's token revocation endpoint and stops calling Kolecto immediately on its side; provider-side propagation to Kolecto's admin panel varies by provider. The collection record, client, and reminder Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Once a reconciled record clears your review queue, Well forwards the extracted document to your Kolecto email-in address with the matched context attached: line items, ledger codes, vendor or customer references, and the source PDF. Kolecto's own capture reads it and drafts the entry; you review and post it, so Kolecto stays the system of record. Well holds no write credential to Kolecto and delivers only what you have approved (case-by-case or under a per-rule auto-forward threshold you set).

Kolecto logo

Ready to connect Kolecto?

Connect once. Every collection record, client, reminder reconciled in Well flows out to Kolecto with its source-graph link preserved. Disconnect any time.