Create a supplier invoice in your Spendesk Inbox
Well forwards the PDF to your dedicated Spendesk bills+ address; Spendesk OCR creates a supplier invoice payment request with invoice number, issue date, and total pre-filled.
Action·Invoice
Integrations · Spend managementConnect Spendesk to Well
Connect Spendesk so its invoice, supplier, and attachment become queryable in conversation and through your agents.
What Well writes to Spendesk
Well writes reconciled invoice, supplier, attachment to Spendesk after they clear your review queue, with the source-record link preserved. Use Spendesk as the destination for entries enriched across your other connected tools.
| In Well | To Spendesk | Relation | |
|---|---|---|---|
Payable | Invoice | Creates as | |
Vendor | Supplier | Resolves to | |
Source PDF | Attachment | Attaches as |
- Sync mode
- incremental polling
- Refresh
- scheduled
- Direction
- Well → Spendesk
3 actions in Spendesk.
Attach the source document to the Spendesk record
The forwarded PDF is stored on the Spendesk invoice as the source.
Action·DocumentResolve a Spendesk supplier from the invoice
Spendesk's OCR resolves the supplier name from the PDF. You confirm the match before the payment request is approved.
Action·Company
What Well does with your Spendesk connection
Connect
Connect Spendesk over OAuth 2.0: you approve on Spendesk's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Spendesk 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 your Spendesk Inbox.
Enrich
Before delivery Well reconciles and enriches each document, resolving the supplier invoice, attachment, and supplier so what reaches Spendesk arrives matched and carries its full audit trail.
Available
Well forwards the PDF to your dedicated Spendesk bills+ address; Spendesk OCR creates a supplier invoice payment request with invoice number, issue date, and total pre-filled.
Questions Spendesk unlocks
Ask in plain language. Well answers from your connected Spendesk connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Spendesk connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Spendesk connection…
Connect Spendesk in three steps
- 01
Authorise Spendesk via OAuth 2.0
Open Well's Connections panel, find Spendesk, and click Connect. You're redirected to Spendesk'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
- 02
Map your entities
Well reads card transaction, expense report, and cardholder from Spendesk on first connect and brings each record into your workspace using the canonical mappings defined in Well's data-views layer.
- Mappingpreconfigured by Well
- 03
Use the data
Use the data: ask questions in conversation, build records tables, and let agents post reconciled entries back to Spendesk once they clear your review queue. Spendesk 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 Spendesk stays secure with Well
Well calls Spendesk's API with an OAuth 2.0 token scoped to card transaction, expense report, and cardholder. Spendesk's consent screen shows you the same list before you approve. Spendesk enforces scope server-side; authentication runs entirely through Spendesk'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 policyScopes Well requests
- granted
Read Spendesk records
Endpoints the Spendesk API token grants, scoped by your consent.
- granted
Resolve card transaction, expense report, and cardholder across your stack
Match identifiers in Spendesk against the same entities your other connected tools expose, so each record carries cross-tool context.
- granted
Deliver documents to your Spendesk inbox
Well forwards approved documents to your Spendesk email-in address; Spendesk drafts the record and you post it. No write credential to Spendesk is requested.
- refused
Store Spendesk passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Disconnect any time from Well settings or Spendesk’s admin panel.
Frequently asked questions about Spendesk and Well
Open Connections in Well, pick Spendesk, and click Connect. You're redirected to Spendesk'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, expense report, and cardholder from Spendesk and reshapes each entity into your workspace: card transaction becomes expense; expense report becomes reimbursement. Every record arrives with the source identifier preserved, so Spendesk stays the source of truth while Well lets you query the data alongside the rest of your stack.
Once Spendesk 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 Spendesk source, so you can always trace a workspace record back to the original.
Well watches for updates to card transactions and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right expense. Edits flow in incrementally; nothing is duplicated, and the Spendesk source identifier is retained on every revision.
Well polls Spendesk regularly for card transaction, expense report, and cardholder. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on Spendesk's side stays modest.
Open Connections > Spendesk in Well and click Disconnect. Well calls Spendesk's token revocation endpoint and stops calling Spendesk immediately on its side; provider-side propagation to Spendesk's admin panel varies by provider. The card transaction, expense report, and cardholder 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 Spendesk email-in address with the matched context attached: line items, ledger codes, vendor or customer references, and the source PDF. Spendesk's own capture reads it and drafts the entry; you review and post it, so Spendesk stays the system of record. Well holds no write credential to Spendesk and delivers only what you have approved (case-by-case or under a per-rule auto-forward threshold you set).
Pairs well with Spendesk
More in Spend management
Popular cross-category
Ready to connect Spendesk?
Connect once. Every card transaction, expense report, cardholder reconciled in Well flows out to Spendesk with its source-graph link preserved. Disconnect any time.