Spendesk Receipt Not Attached: Trace the Payment Handoff
Check the destination, existing payment, file type and size, duplicate state, export status, direct upload, and forwarding rule.
Read this if…
Use this guide when a receipt was emailed or uploaded but is not attached to the expected Spendesk payment.
Related: Open the Spendesk setup guide
TL;DR
Confirm the receipt was sent to the company Marvin address and that the target payment exists and is still editable.
Use PDF for the documented Marvin email path. For direct upload, check PDF, JPG, or PNG, readability, live size validation, and duplicate detection.
Compare one direct email or upload with the normal rule. Do not resend repeatedly before checking the payment and export state.
In This Guide
1. Confirm the target payment and its state
Open the Spendesk payment and verify the merchant, amount, date, currency, owner, and status. The receipt needs a real payment context for matching.
If the payment has already been exported or validated, Spendesk may block new attachments or changes. Contact the finance team before creating another record or using a workaround.
2. Verify the Marvin destination and sent message
Copy the current receipt address from Payments and compare it with the sent message. Do not confuse it with the bills+ supplier invoice address.
Check that the receipt is attached and that the source email was actually sent. Preserve the message, destination, attachment, and timestamp for comparison with Spendesk.
3. Check the file and duplicate rules
Use a clear PDF for the documented Marvin email path. Direct upload guidance also accepts JPG and PNG. Spendesk help currently gives conflicting 1 MB and 10 MB maximums, so follow the live validation message and use a smaller clear test file.
Spendesk can reject a receipt already submitted for another payment or request. Search the account for the same document before sending it again.
| Observed problem | Likely cause | Next action |
|---|---|---|
| No sent message | The source rule did not run | Check Expensent history or the mailbox rule |
| Upload error | Format, size, or app path failed | Use PDF for Marvin email or a supported upload format, with the live validation limit |
| Duplicate warning | The same evidence already exists | Find the prior payment or request before resubmitting |
| Payment exported | The record is no longer editable | Ask finance to use the supported correction process |
| Direct upload works | The file and payment are valid | Inspect the email address and forwarding route |
4. Compare direct and rule-based submission
Try one supported file through the payment interface or a direct message to the copied Marvin address. If the direct path works, inspect the forwarding rule, source account, recipient, and attachment preservation.
If the app path fails, use desktop upload or email as the documented alternative while retaining the original evidence. Recent Google Play and App Store reviews reported PDF or image upload regressions, and Spendesk replied that it restored PDF upload and was improving the experience.
5. Attach once and verify the final payment
After correcting the cause, attach one copy and verify it appears on the intended payment. Confirm the image is readable and the payment is no longer marked as missing evidence.
Remove overlapping submission rules and keep the source trail. Repeated sends can trigger duplicate detection or attach the evidence to another payment candidate.
6. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
8. Frequently asked questions
Why did my emailed receipt not attach in Spendesk?
Check the company Marvin address, target payment, file format and live size validation, duplicate detection, payment export state, and the source rule history.
Can I attach a receipt after a payment was exported?
Spendesk says an exported payment can no longer accept or modify receipts. Contact the finance team for the supported correction path.
Why was my receipt marked duplicate?
Spendesk detected the same document on another payment or request. Find the prior attachment before deciding whether a correction is needed.
What file size does Spendesk allow?
Current official help pages conflict between 1 MB and 10 MB. Follow the live uploader and account guidance, and use a smaller legible test file.
What if direct upload works but email does not?
The payment and file are valid, so check the Marvin address, sent message, attachment preservation, and forwarding rule.
Trace the Spendesk receipt handoff
Keep the source message, company destination, and payment context visible before sending a corrected copy.
Get Started