Moss Receipt Not Matching? Diagnose the Receipt Inbox

Trace delivery, document recognition, Moss card context, potential matches, and manual correction before sending the receipt again.

By ilios Galil · Founder, Expensent

Updated August 31, 2026

Last verified : August 31, 2026

Read this if…

Use this diagnostic when a forwarded card receipt remains unmatched, was linked to the wrong Moss transaction, or appears to be missing from the Receipt Inbox.

Related: Open the Moss email setup guide

TL;DR

Confirm the receipt went to the organization-specific receipts+ address, not the invoices+ address. The two inboxes perform different jobs.

Automatic receipt matching is for Moss card transactions. Check the card purchase, merchant, date, amount, document quality, and the Receipt Inbox suggestions.

Use Unlink and attach to a new transaction or manual matching when Moss already has the receipt. Do not resend an existing item unless delivery or recognition actually failed.

1. Identify delivery, recognition, or matching

Treat the workflow as three checkpoints. Delivery means the message reached the organization address. Recognition means Moss saved a usable receipt or converted supported body evidence. Matching means Moss associated that receipt with a Moss card transaction.

Verified Capterra reviews describe occasional receipt matching or categorization that needs manual correction, and another reviewer reports that connectivity can interrupt uploads. Those reports support a focused recovery guide. Moss's current help center defines the actual inbox and correction controls.

Observed state
Observed stateCheckpointNext action
Nothing in the Receipt InboxDestination, delivery, or recognitionCheck the receipts+ address, send history, and supported evidence.
Receipt present but unmatchedCard context or match confidenceReview potential matches or search all transactions.
Receipt attached to the wrong transactionIncorrect automatic or manual matchUse Unlink and attach to a new transaction.

2. Check the organization and destination type

Compare the exact destination in the sent message with the Receipts tab in the affected Moss organization. A supplier invoice sent to invoices+ belongs in the invoice workflow and will not behave like a card receipt. A receipt sent to another organization address will be reviewed in that organization.

Copy the current address from Moss instead of relying on a contact or rule saved earlier. If the destination is wrong, correct it before one controlled resend and update any recurring rule only after the new path succeeds.

3. Check document recognition and the Moss card purchase

Confirm the email contains a PDF, JPG, JPEG, or PNG within the Moss limit and, for an Expensent handoff, within the current 3 MB per-attachment limit. If the evidence exists only in the body, confirm the finance team enabled the Moss conversion setting and review the generated document.

Then confirm that the target purchase was made with a Moss card and that the transaction lacks a receipt. Compare merchant, date, amount, and available tax evidence. A receipt for a personal purchase, another card platform, or a supplier invoice awaiting payment needs a different path.

  • Confirm the exact receipts+ address and Moss organization.
  • Confirm the receipt file or body evidence was recognized.
  • Confirm the purchase used a Moss card.
  • Compare merchant, date, amount, and existing receipt state.
  • Check for a duplicate notification before sending another copy.

4. Use the Receipt Inbox correction controls

Open the unmatched receipt and review the suggested potential transactions. If one is correct, attach it. If none is correct, use Select other transaction and search the full list. When the receipt is attached to the wrong transaction, use Unlink and attach to a new transaction.

Delete only when the file itself should be removed. Moss distinguishes unlinking a relationship from deleting the receipt. Preserving the existing evidence while correcting the link keeps the activity easier to audit.

5. Retest one vendor pattern

After correcting the destination, evidence, or card context, test the next receipt from the same vendor. Confirm that it appears in the right organization and either auto-matches or produces a sensible suggestion.

Approve a recurring Expensent rule only after this result is predictable. Keep supplier invoices on their separate invoices+ route and preserve a review step for body-only receipts or vendor emails with several attachments.

6. Escalate with a complete inbox trace

If the receipt remains missing or cannot be corrected, collect the sender, exact Moss destination, organization, message timestamp, attachment name and size, card transaction, merchant, date, amount, and visible Receipt Inbox state. Include any duplicate or upload notification.

Expensent can show the source and approved send history. Moss must resolve document recognition, inbox retention, matching, and transaction-link problems inside its platform.

7. Sources checked

These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.

9. Frequently asked questions

Why is my Moss receipt in the inbox but not matched?

Check that the purchase used a Moss card, compare merchant, date and amount, then review the suggested matches or search all transactions manually.

How do I fix a Moss receipt attached to the wrong transaction?

Use Unlink and attach to a new transaction in the Receipt Inbox. This corrects the relationship without requiring another copy of the source.

Should I delete or unlink a Moss receipt?

Unlink when the file is valid but connected to the wrong transaction. Delete only when the receipt file itself should be permanently removed.

Can Expensent force Moss to match a receipt?

No. Expensent controls source discovery and approved delivery. Moss controls recognition, duplicate handling, matching, correction, and accounting export.

Correct the Moss inbox item before resending

Keep one source document and use the Moss match controls so the organization, transaction, and correction history remain clear.

Get Started
Guide slug: moss-receipt-not-matching