How to Email Receipts and Supplier Invoices to Spendesk

For card-payment evidence, Spendesk provides a company-specific Marvin address with a receipts+ prefix. Users can find it in Payments and forward the receipt for matching to a payment.

For supplier invoices on Essentials, Growth, and Premium, Spendesk provides a separate company bills+ address in Inbox. The feature is not available on Starter. Each attached invoice creates a draft request.

Copy the company-specific receipt address from Payments. Spendesk specifically documents PDF for the Marvin email path; its broader upload guidance also accepts JPG and PNG. Use a clear PDF for the first email test.

Send one receipt per source document. Duplicate detection can reject a file already associated with another payment or request. If the payment has already been exported to the accounting system, Spendesk may no longer allow the receipt to be attached or changed.

Current Spendesk help pages conflict on the maximum receipt size: one page says 1 MB, while another updated page says 10 MB. Follow the current uploader and account guidance, compress carefully when necessary, and do not promise one fixed limit until Spendesk reconciles the documentation.

On Essentials, Growth, and Premium, copy the bills+ address from Spendesk Inbox. Spendesk says this feature is not available on Starter. A company user or supplier can email invoice attachments to that destination, and Spendesk creates one draft request per attachment.

If the sender is not a recognized Spendesk user, Spendesk checks the CC field for a user to assign. Unassigned invoices remain in the shared controller and Account Owner inbox. Requester permissions determine who can submit and assign requests.

Spendesk warns that emails with more than 10 invoices can cause OCR errors. Split large batches and review every draft rather than treating one successful delivery as proof that all attachments were processed.

Spendesk supports mobile capture, desktop upload, reply to a payment confirmation, and email forwarding. Choose the method that preserves the clearest document and the strongest link to the payment.

The mobile app can validate whether a photo resembles a financial document, but Spendesk says desktop and email uploads do not use the same automatic validity check. Finance still needs the purchase date, supplier details, item information, and tax evidence required by policy.

Connect the inbox where receipts or supplier invoices arrive, confirm that the account plan exposes the required destination, and send one controlled example. Verify the payment attachment or draft request before creating a rule.

Use separate rules for receipt and invoice destinations. A vendor can issue both card receipts and unpaid invoices, so sender alone may be too broad. Include subject, document context, or review whenever the intended Spendesk workflow varies.

For a receipt, verify that the evidence is attached to the correct payment and remains legible. For a supplier invoice, review the request owner, supplier, amount, due date, analytics, and approval path before submission.

Expensent controls the inbox discovery and email handoff. Spendesk controls receipt matching, invoice request assignment, duplicate detection, approval, export state, and accounting consequences.