Sage Expense Management Receipts Not Matching: A State-by-State Fix

Use this guide when the forwarded receipt produced a record in Sage Expense Management but did not attach to the expected card expense. The most common visible outcome is a new Incomplete expense under Expenses > Unreported. That outcome proves Magic Mail intake worked; it does not prove receipt matching should have succeeded.

If no expense or receipt record appeared at all, stop here. Recheck the user-specific Magic Mail address, owner, sending address, secondary-inbox setup, source evidence, and processing time. Amount, merchant, and card state cannot explain a document that never entered the product.

Open the new Incomplete expense and the expected corporate-card expense side by side. Preserve the source email. Record the amount, date, merchant, payment mode, expense type, current state, receipt image, and History events. This turns a vague “not matching” report into a specific comparison.

Do not immediately complete the new record, delete it, or send the receipt again. First decide whether the record is the valid start of a reimbursable expense, a Magic Mail exception that should attach to a card expense, or a duplicate caused by an earlier upload. Those paths have different corrections.

Recent accounting-community discussion about the Fyle-to-Sage transition includes user concern about lag and glitchy OCR. That is useful evidence that receipt-processing friction is a real search problem, but it does not prove a platform-wide incident. Diagnose the documented criteria and the actual History before assuming a product outage.

Sage Expense Management currently documents receipt matching for corporate-card expenses. The emailed or texted receipt-matching path does not apply to reimbursable, mileage, or per-diem expenses. A receipt for a personal-card purchase may need an expense created and completed for reimbursement rather than a corporate-card match.

Check payment mode instead of inferring it from the merchant or employee. A restaurant receipt can belong to a corporate card, personal card, or cash purchase. Magic Mail may create a new expense in the user's default payment mode when no match is found, so the new record's payment mode is not proof of how the purchase was actually paid.

The candidate corporate-card expense must be in Incomplete or Complete state for receipt matching. An expense already submitted, approved, processing, paid, closed, or linked in another incompatible state is outside the documented receipt-matching rule. Use the current Sage Expense Management correction flow appropriate to that state.

Ownership also matters. Magic Mail is user-specific. Confirm that the destination belongs to the cardholder or expected expense owner and that the corporate-card charge appears under that same user. A perfectly readable receipt sent to another employee's Magic Mail destination can create a valid expense without ever becoming eligible for the intended card match.

If the target is mileage, per diem, or reimbursable, stop trying to force a card association. Complete the appropriate expense type using the original receipt and the organization's policy. If the target is a corporate-card expense but is not Incomplete or Complete, capture its state and ask the admin which current correction path is allowed.

For an eligible corporate-card expense, Sage Expense Management documents four content and state checks: amount, date, merchant similarity, and a unique candidate. Evaluate all of them from the source receipt and the card record. Correcting only the most obvious mismatch can leave another blocker in place.

The amount normally must match exactly. Sage Expense Management documents an exception within 20 percent for food, lodging, or taxi categories. That tolerance is category-specific. It should not be generalized to software, supplies, fuel, or every travel purchase, and it does not eliminate the need to understand tips, deposits, currency conversion, or final settlement amounts.

The documented receipt date window is within one day of the card expense date. This is narrower than the separate five-day window Sage Expense Management uses when matching a newly imported card transaction to a manually created expense. A team note that says “Fyle uses five days” can therefore be true for one flow and wrong for emailed receipt matching.

Merchant text must reach at least 40 percent similarity. Processor prefixes, marketplace names, hotel property names, franchise locations, and abbreviated statement descriptors can lower similarity even when a person recognizes the purchase. Compare the extracted merchant with both the source receipt and the card transaction rather than editing one blindly.

Finally, only one candidate can win. When several Incomplete or Complete corporate-card expenses look plausible, Sage Expense Management says it creates a new expense instead of attaching the receipt. Treat that as an ambiguity safeguard and resolve ownership manually.

When no match is found, Sage Expense Management says Magic Mail creates a new expense in the user's default payment mode. That record appears under Expenses > Unreported and contains the fields the system could extract. It is an exception work item, not an error message by itself.

Open it and compare the receipt image or email evidence with the expected card charge. If the purchase was actually out of pocket, the new expense may be the correct record. Complete the required fields and follow the reimbursement workflow. If it was a corporate-card purchase, do not submit the new record until you understand why the existing card expense was ineligible or ambiguous.

Use History on both records. Sage Expense Management documents History as the place to see when a card transaction or receipt was linked or when expenses were merged. Time order can reveal whether the receipt arrived before the card transaction, whether a manual expense had already been edited, or whether a prior merge changed eligibility.

Avoid changing amount and date merely to trigger automation. Any correction must be supported by the source receipt and card data. If OCR captured the subtotal instead of the final total, correct it from the receipt. If the card amount includes a tip or currency conversion that the receipt does not show, retain the evidence and document the difference rather than making both records artificially identical.

Once the reason is clear, use the current Sage Expense Management UI to attach, unlink, merge, dismiss, or complete the right record as allowed. The exact available action depends on expense type, state, card linkage, and permissions. If the correct action is absent, preserve both records and escalate with their identifiers instead of deleting evidence.

Several similar card charges can block automatic matching. Common examples include repeated rides, identical subscription amounts across departments, two restaurant checks on the same day, or a temporary card authorization followed by a final charge. Because Sage Expense Management refuses to choose among multiple candidates, a separate Incomplete expense is an expected protective result.

List every eligible candidate with owner, card, amount, date, merchant, and state. Compare the original email recipient, order number, last four digits when available, location, project, and timestamp. Do not select a transaction only because it has the same total. The receipt is financial evidence and must belong to the right charge.

Sage Expense Management separately flags potential duplicate expenses and provides merge controls. Current help says two expenses can be merged when eligibility rules allow it, with the linked or more advanced record typically retained. The user chooses which conflicting field values and receipt to keep. Treat this as a data-loss-sensitive action because one duplicate record and potentially one receipt are removed from the surviving view.

The product's help articles are not perfectly aligned about undo behavior: one says a merge cannot be undone, while another describes an unmerge or unlink process that may not restore every attachment or detail. Use the current account UI and support guidance before merging. Preserve the source email and export or screenshot the critical record details first.

Do not merge two expenses that represent an authorization and a final charge until the card feed has settled and the organization understands how its bank presents them. Likewise, do not merge a reimbursable expense with a corporate-card expense merely because the merchant and amount match. Payment ownership is part of the accounting record.

A receipt can also attach to the wrong expense or produce incorrect extracted fields. Start with History, the original receipt email, and the card transaction. Record what was linked automatically and when. Do not overwrite the record before capturing the evidence that explains the current state.

For wrong extraction, compare final total rather than subtotal, confirm tax and tip, verify currency, and check whether a refund or credit appears on the same document. Long itemized receipts, low-resolution images, folded paper, or merchant logos far from the total can all make human review more important. Correct only what the document supports.

For a wrong match, compare all eligible candidates and confirm the cardholder. Use the current unlink or remove-card-details action when available, then associate the receipt through the product's supported workflow. Do not send the same email again, because the original receipt already exists and a second intake can create another expense.

If the receipt was routed through Expensent, its delivery record helps confirm which source mailbox sent which message to which destination. That evidence can narrow the issue to downstream extraction or matching. It cannot prove that Sage Expense Management selected the correct candidate, and Expensent cannot modify the downstream History.

Community reports of OCR friction are a reason to make this review path easy to find, not a basis for claiming that every mismatch is OCR. If amount, date, merchant, state, and candidate count all satisfy the current documented rules, collect the full record and contact Sage Expense Management support. Product behavior can depend on account configuration and changes not visible in public help.

After resolving the case, classify the cause. Intake causes include a wrong user destination, unrecognized sender, missing receipt evidence, or a broad filter. Matching causes include an ineligible expense type or state, amount or date difference, merchant similarity, and multiple candidates. Review causes include incorrect OCR, required fields, policy, or ownership.

Fix the narrowest upstream rule. A sender-plus-subject pattern for a recurring SaaS invoice is safer than a keyword filter for every message containing “invoice.” A dedicated business travel profile is safer than sending personal and business rides to the same Magic Mail address. A shared finance inbox needs explicit mapping to the correct user destination.

Keep the source email until the expense is reviewed and added to the correct report. For historical catch-up, send smaller batches and check Unreported after each vendor pattern. Old receipts may already have been uploaded, reimbursed, refunded, or attached through another channel.

Avoid parallel capture paths for the same source. If a vendor sends directly to Magic Mail, employees should not also forward the same email or upload the attachment through Slack. If a Gmail filter handles the pattern, an Expensent rule for the same message can duplicate delivery. Record which system owns each recurring route.

Measure the workflow by exceptions, not by sent count. Track how many routed messages created new Incomplete expenses, matched correctly, produced duplicates, or required field corrections. High sent volume with unresolved Unreported items is not automation success.

Escalate when the receipt exists, the target is an eligible Incomplete or Complete corporate-card expense, the documented amount, one-day date, and merchant criteria appear satisfied, and no competing candidate explains the result. Also escalate a wrong automatic attachment when the correct candidate is clear and the current UI does not offer a safe correction.

Include the Sage Expense Management user, organization, Magic Mail owner, sending address, sent timestamp, source email subject, receipt file or body evidence, new Incomplete expense identifier, expected card expense identifier, payment mode, state, amount, date, merchant text, and History events. Redact unrelated personal or card information before sharing outside approved support channels.

State whether the receipt came through Magic Mail, Gmail or Outlook add-in, mobile, web, text, Slack, direct merchant delivery, or Expensent. The intake channel helps support reproduce identity and processing behavior. Include any confirmation or rejection message and whether another submission already existed.

Describe the expected result in one sentence: for example, “The emailed hotel receipt created a separate Incomplete expense even though one eligible corporate-card expense has the same amount, a date within one day, and a closely matching merchant.” Avoid saying only “OCR is broken” or “Magic Mail failed” when the record shows intake succeeded.

Until support resolves the case, preserve the source email and both expense records. Do not merge, delete, or repeatedly resend merely to clear the queue. A visible exception with complete evidence is safer than a clean-looking report whose receipt is attached to the wrong transaction.