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.
Forward extracted invoice PDFs directly to your Spendesk bills inbox to draft supplier invoice payment requests
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 |
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.
The forwarded PDF is stored on the Spendesk invoice as the source.
Spendesk's OCR resolves the supplier name from the PDF. You confirm the match before the payment request is approved.
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.
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.
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.
Spendesk has no inbound write path today, so Well keeps the reconciled record on the Well side for review rather than delivering it to Spendesk.
Ask in plain language. Well answers from your connected Spendesk connection, resolved against the rest of your stack.
Ask anything about your Spendesk connection
Ask about your Spendesk connection…
Authorize Well to access your document routing pipeline and locate your unique Spendesk bills email address.
Confirm the connection to establish the secure forwarding path for your extracted invoice PDFs.
Verify that test documents successfully arrive in your Spendesk bills inbox as drafted supplier invoice payment requests.
Well delivers documents to Spendesk via email forwarding and does not write directly to the Spendesk API.
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.
Read Spendesk records
Endpoints the Spendesk API token grants, scoped by your consent.
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.
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.
Store Spendesk passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Well forwards your extracted invoice PDFs to your unique Spendesk bills inbox email address. Well does not write directly to the Spendesk API.
No. Well only forwards the invoice PDF to your inbox. Spendesk drafts the supplier invoice payment request, leaving the final review and approval to you.
Spendesk uses its OCR technology to read the forwarded PDF and draft a supplier invoice payment request with the source document attached.
More in Spend management
Popular cross-category
Connect once. Every card transaction, expense report, cardholder reconciled in Well flows out to Spendesk with its source-graph link preserved. Disconnect any time.