How to Email Receipts and Supplier Invoices to Moss

Open the Moss Document Inbox and choose the tab that matches the job. The Receipts tab shows the organization-specific receipt address for evidence that should attach to Moss card transactions. The Invoices tab shows a different organization-specific address for supplier invoices that need the invoice workflow.

The address formats include the organization name, but the live value is authoritative. Copy it from the current account. Do not convert a receipts+ address into an invoices+ address by editing the text, because naming and organization details can change.

Moss documents PDF, JPG, JPEG, and PNG in the Receipt Inbox, with a maximum of 20 MB per file and up to twenty files in a drag-and-drop batch. Expensent currently supports PDF, JPG, and PNG attachments up to 3 MB each, so an Expensent handoff must fit the narrower limit.

Use the original legible document when possible. A card receipt should show the merchant, date, amount, and tax evidence needed to identify the purchase. A supplier invoice should show the supplier, invoice number, amount, currency, payment details, and due date that the finance team must verify.

Moss can optionally convert a receipt found only in the email body into a PDF. The finance team controls that setting, and Moss warns that a generated document is not guaranteed to satisfy tax requirements. Treat the generated file as reviewable evidence, not automatic proof of tax compliance.

Email forwarding is useful when the document already arrives in a mailbox. Receipt Finder is a separate Gmail or Microsoft 365 connection for a supported merchant list and searches after a Moss card transaction occurs. Moss says it checks for up to seven days before marking the receipt missing.

Bulk upload fits a local document backlog. Send to Moss lets a phone user share a receipt from another app. Direct web or mobile attachment fits a known card transaction, and TravelPerk is a separate direct integration. The right method depends on where the evidence starts and whether the target card transaction is already known.

Moss processes a receipt from the inbox and attempts to match it with a Moss card transaction that lacks evidence. A successful result appears as auto-matched. If confidence is lower, the Receipt Inbox can show potential matches or let the user search all transactions and attach the receipt manually.

Moss also documents duplicate handling and a correction path. A detected duplicate can be removed from the inbox with an email notification. An incorrect match can be unlinked and attached to another transaction. These controls are reasons to inspect the existing inbox item before sending the source again.

Connect the mailbox where receipts and supplier invoices arrive. Expensent can find current and historical documents, show the source and available files, and send selected evidence to the exact Moss destination configured for the organization.

Expensent creates a new message with an Expensent subject and summary body. Selected attachments are added to it, and body-only evidence appears below the summary. Moss controls whether it recognizes the attachment or the body-derived evidence, so test one representative vendor message before approving a rule.

For a card receipt, confirm the transaction, cardholder, merchant, date, amount, tax, accounting attributes, and receipt status. For a supplier invoice, confirm supplier, invoice number, due date, amount, payment data, approval path, and duplicate state.

Expensent owns source discovery, review, and the approved email handoff. Moss owns recognition, matching, invoice handling, controls, payment, and accounting export. Keep the source message until the downstream record is complete.