Sage Expense Management Receipts Not Matching: A State-by-State Fix
Start after Magic Mail creates a record. Check corporate-card eligibility, state, amount, date, merchant similarity, competing candidates, OCR, duplicates, and History.
Read this if…
Read this only after a receipt or expense record appears in Sage Expense Management. If nothing was created, return to the setup guide and troubleshoot Magic Mail intake first.
Related: Open the Sage Magic Mail setup guide
TL;DR
A new Incomplete expense means Magic Mail intake worked but Sage Expense Management did not find one eligible unique corporate-card match.
Check the target type and state first, then exact or category-tolerated amount, one-day date window, at least 40% merchant similarity, and competing candidates.
Do not resend an existing receipt. Use the source email and History to resolve the current record without creating another expense.
In This Guide
- 1. Confirm that Magic Mail intake worked
- 2. Confirm that the target can receive a match
- 3. Compare the documented matching criteria
- 4. Use the new Incomplete expense
- 5. Resolve competing charges carefully
- 6. Correct the record from the source receipt
- 7. Sources checked
- 8. Related reading
- 9. Frequently asked questions
1. Confirm that Magic Mail intake worked
Use this guide when a receipt created a record in Sage Expense Management but did not attach to the expected card expense. A new Incomplete expense under Expenses > Unreported means intake succeeded.
If nothing appeared, check the user-specific Magic Mail address, owner, sending mailbox, and source evidence before investigating matching.
First diagnostic split
Nothing created means intake troubleshooting. A new Incomplete expense means intake succeeded but Sage Expense Management did not find one eligible match.
2. Confirm that the target can receive a match
Sage Expense Management documents this receipt-matching path for corporate-card expenses in Incomplete or Complete state. Reimbursable, mileage, and per-diem expenses follow their own workflows.
Confirm the payment mode, expense state, cardholder, and Magic Mail owner. A receipt sent to another user's destination cannot match the intended card expense.
3. Compare the documented matching criteria
The amount normally must match exactly, with a documented tolerance within 20 percent for food, lodging, or taxi. The receipt and card dates must be within one day.
Merchant text must reach at least 40 percent similarity. Processor names, franchise locations, and abbreviated card descriptors can affect that comparison.
Only one eligible candidate can win. When several expenses are plausible, Sage Expense Management creates a new expense instead of attaching the receipt to one of them.
| Matching check | Documented requirement | What to inspect | Safe next action |
|---|---|---|---|
| Expense type and state | Corporate-card expense; Incomplete or Complete | Payment mode, owner, current state, existing card link | Use the correct reimbursement or admin path when the target is ineligible |
| Amount | Exact, or within 20% only for food, lodging, or taxi | Tip, tax, deposit, refund, currency, settlement total | Correct extraction from the original evidence; do not invent a total |
| Date | Within one day for receipt matching | Receipt date, local time, card date, posting timing | Keep the receipt-matching window separate from the five-day merge flow |
| Merchant | At least 40% similarity | Extracted merchant, receipt brand, processor, card descriptor | Correct demonstrably wrong extraction and preserve the original source |
| Candidate count | One eligible match | Same-value charges, repeated trips, duplicate expenses | Resolve the ambiguity instead of resending the receipt |
4. Use the new Incomplete expense
When no match is found, Magic Mail creates a new expense in the user's default payment mode. Compare it with the expected charge and check History on both records.
If it was an out-of-pocket purchase, complete the reimbursement record. If it belongs to a corporate card, use the current attach, unlink, or merge action available for the expense state instead of sending another copy.
5. Resolve competing charges carefully
Compare every candidate using owner, card, amount, date, merchant, order reference, location, and timestamp. The same total alone is not enough to establish the right charge.
Use merge controls only when the records truly represent one expense and the current account supports the correction. Preserve the source email before a merge or unlink action.
Ambiguity is safer than a wrong attachment
A new Incomplete expense keeps the receipt visible. Resolve the owner and candidate transaction before using merge or delete controls.
6. Correct the record from the source receipt
For a wrong match or extracted value, compare History, the original receipt email, and the card transaction. Correct only the amount, date, merchant, tax, tip, or currency values the source supports.
If Expensent routed the receipt, its delivery record can confirm the source email and destination. Sage Expense Management remains responsible for extraction, matching, and downstream corrections.
7. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
- Sage Expense Management Help: Receipt matching and merging
- Sage Expense Management Help: Magic Mail
- Sage Expense Management Help: Merge duplicate expenses
- Sage Expense Management Help: Fix incorrectly merged expenses
- Sage Expense Management Help: Understanding My Expenses
- Accounting community discussion: Sage Expense Management
9. Frequently asked questions
Why did Magic Mail create a new expense instead of matching my card charge?
Sage Expense Management creates a new expense when no eligible unique match is found. Common reasons include a non-corporate-card target, an ineligible expense state, amount or date differences, weak merchant similarity, or several possible matching expenses.
Which expenses can receive an emailed receipt match?
Current Sage Expense Management help says receipt matching applies to corporate-card expenses in Incomplete or Complete state. It does not use this matching path for reimbursable, mileage, or per-diem expenses.
How close do the receipt and card amounts need to be?
The documented rule is an exact amount match, with a tolerance within 20 percent for food, lodging, or taxi categories. Do not assume the tolerance applies to every category or use it to explain a foreign-currency or tip discrepancy without reviewing the original receipt.
What date window does Sage Expense Management use?
For receipt matching, Sage Expense Management currently documents dates within one day. A separate auto-merge flow for manual expenses and card transactions uses a five-day window; the two rules should not be confused.
What happens when several card expenses could match?
Sage Expense Management says it will not attach the receipt to any candidate when multiple possible matches exist. It creates a new expense instead so a person can resolve the ambiguity.
Should I forward the receipt again?
Not when an expense or receipt record already exists. A second send can create another Incomplete expense and make the exception harder to resolve. Review the existing record, candidate card expense, History, and duplicate controls first.
Can Expensent fix Sage Expense Management matching?
Expensent finds and routes the source email and preserves the sending record. Sage Expense Management continues with extraction, card matching, expense state, History, duplicate handling, reporting, approval, and accounting sync.
Recover the source email behind the expense
Expensent preserves the source email and routing destination, giving you the evidence needed to correct the existing Sage Expense Management record.
Get Started