Store a receipt in your Soldo Library
Well forwards the receipt PDF to your personal @myfiles.soldo.com forwarding address; Soldo stores it in your Library and, with OCR on, matches it to the relevant card transaction.
Forward receipt PDFs directly to your Soldo email-in inbox to match documents with card transactions
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 @myfiles.soldo.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.
Soldo has no inbound write path today, so Well keeps the reconciled record on the Well side for review rather than delivering it to Soldo.
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…
Authorize Well to access your receipt pipeline and enter your dedicated @myfiles.soldo.com forwarding address in the connection settings.
Confirm the connection within the Well dashboard to establish the automated document forwarding path.
Verify that test receipts successfully arrive in your Soldo library and are ready for transaction matching.
Receipts are delivered solely via email forwarding, as direct API write capabilities are not supported for this destination.
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.
Well forwards your extracted receipt PDFs to your designated @myfiles.soldo.com email address. Soldo then stores these documents in your library.
No. Well does not have a direct API write channel to Soldo. All receipt delivery is handled via email forwarding to your Soldo inbox.
No. Well only delivers receipt documents to your Soldo library. It cannot create bills, invoices, or journal entries.
Well extracts and forwards receipts as PDF documents to ensure they are compatible with Soldo's library and OCR matching.
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.