Store a receipt in your Soldo Library
Well forwards the receipt PDF to your personal @mysoldo.com forwarding address; Soldo stores it in your Library and, with OCR on, matches it to the relevant card transaction.
Connect Soldo so its receipt become queryable in conversation and through your agents.
Well writes reconciled receipt to Soldo after they clear your review queue, with the source-record link preserved. Use Soldo as the destination for entries enriched across your other connected tools.
| In Well | To Soldo | Relation | |
|---|---|---|---|
Source PDF | Receipt | Delivers as |
Well forwards the receipt PDF to your personal @mysoldo.com forwarding address; Soldo stores it in your Library and, with OCR on, matches it to the relevant card transaction.
Connect Soldo over OAuth 2.0: you approve on Soldo's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Soldo is a delivery target, not a source, so Well pulls nothing in. Once a record clears review, Well's pipeline can store a receipt in your Soldo Library.
Before delivery Well reconciles and enriches each document, resolving the receipt so what reaches Soldo arrives matched and carries its full audit trail.
Well forwards the receipt PDF to your personal @mysoldo.com forwarding address; Soldo stores it in your Library and, with OCR on, matches it to the relevant card transaction.
Ask in plain language. Well answers from your connected Soldo connection, resolved against the rest of your stack.
Ask anything about your Soldo connection
Ask about your Soldo connection…
Open Well's Connections panel, find Soldo, and click Connect. You're redirected to Soldo's authorize screen, where you'll see the exact scopes Well requests. Approve, and you land back in Well with the connection live.
Well reads card transaction, cardholder, and receipt from Soldo on first connect and brings each record into your workspace using the canonical mappings defined in Well's data-views layer.
Use the data: ask questions in conversation, build records tables, and let agents post reconciled entries back to Soldo once they clear your review queue. Soldo records are live in your workspace immediately.
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.
Well calls Soldo's API with an OAuth 2.0 token scoped to card transaction, cardholder, and receipt. Soldo's consent screen shows you the same list before you approve. Soldo enforces scope server-side; authentication runs entirely through Soldo's authorize screen so Well never sees your credentials. Tokens refresh automatically; rotation is one click away.
Read Soldo records
Endpoints the Soldo API token grants, scoped by your consent.
Resolve card transaction, cardholder, and receipt across your stack
Match identifiers in Soldo against the same entities your other connected tools expose, so each record carries cross-tool context.
Deliver documents to your Soldo inbox
Well forwards approved documents to your Soldo email-in address; Soldo drafts the record and you post it. No write credential to Soldo is requested.
Store Soldo passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Open Connections in Well, pick Soldo, and click Connect. You're redirected to Soldo'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 card transaction, cardholder, and receipt from Soldo and reshapes each entity into your workspace: card transaction becomes expense; cardholder becomes team member. Every record arrives with the source identifier preserved, so Soldo stays the source of truth while Well lets you query the data alongside the rest of your stack.
Once Soldo is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Soldo source, so you can always trace a workspace record back to the original.
Every workspace expense built from Soldo carries the source card transaction identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Soldo record; from Soldo, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well polls Soldo regularly for card transaction, cardholder, and receipt. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on Soldo's side stays modest.
Open Connections > Soldo in Well and click Disconnect. Well calls Soldo's token revocation endpoint and stops calling Soldo immediately on its side; provider-side propagation to Soldo's admin panel varies by provider. The card transaction, cardholder, and receipt 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 Soldo email-in address with the matched context attached: line items, ledger codes, vendor or customer references, and the source PDF. Soldo's own capture reads it and drafts the entry; you review and post it, so Soldo stays the system of record. Well holds no write credential to Soldo and delivers only what you have approved (case-by-case or under a per-rule auto-forward threshold you set).
More in Spend management
Popular cross-category
Connect once. Every card transaction, cardholder, receipt reconciled in Well flows out to Soldo with its source-graph link preserved. Disconnect any time.