Expensify SmartScan Troubleshooting

Stuck on “SmartScanning”? Forwarded receipts not showing up? Wrong amounts or duplicate expenses? A diagnostic walkthrough for the parts of the Expensify receipt flow that most often break in practice.

By ilios Galil · Founder, Expensent

Published April 1, 2026 · Updated June 17, 2026

Skip manual forwarding when you can. Many SmartScan failures happen before Expensify sees the receipt — Gmail auto-forwarding can change sender attribution, unverified senders may not route to your account, or portal-only emails arrive without attachments. Expensent connects to your inbox via OAuth and helps you review and forward receipt emails to Expensify from a linked address.

Expensify integration details·When to avoid the forwarding chain

In This Guide

1. How SmartScan troubleshooting works
2. Diagnostic flowchart: which failure is yours?
3. Category A — Receipt never arrived
4. Category B — Arrived but scan stalled or produced an unreadable result
5. Category C — Wrong data extracted
6. Category D — Duplicates and workflow blockers
7. Category E — The forwarding-chain problem
8. When to stop troubleshooting and switch approach
9. Frequently Asked Questions

1. How SmartScan troubleshooting actually works

Most SmartScan troubleshooting advice fails because it treats the whole receipt flow as one black box. In practice, the failures cluster into a few simpler stages: the receipt never arrived, the receipt arrived but processing stalled, processing finished with bad extraction, or the expense ended up duplicated or blocked later in the workflow.

Expensify's public help is clearest about inputs and outcomes: use clear receipt images or PDFs, make sure the sender is a linked contact method, and avoid assuming a precise processing window. That is enough to build a reliable troubleshooting flow without inventing extra precision about the internal pipeline.

Why does this matter for troubleshooting? Because each stage fails differently and has a different fix. If you separate arrival, processing, extraction, and downstream workflow issues, the right next step gets much easier to spot.

Key implication:when someone says “SmartScan is broken”, the first job is to figure out whereit broke. That's what Section 2 does.

2. Diagnostic flowchart: which category is your failure?

Run through these four questions in order. The first one you answer “no” to points you at the right category below.

1.Does the receipt appear in Expensify at all (any state, including “Checking” or an empty expense)? No → jump to Category A.
2.Did the receipt finish processing with usable data? No → jump to Category B.
3.Is the extracted amount, date, and merchant correct? No → jump to Category C.
4.Are you dealing with duplicates, a blocked report, or a receipt that landed in the wrong workflow state? Yes → check Category D.

If the receipt is being forwarded from Gmail or Outlook and you keep landing in Category A even after fixing the obvious stuff, skip ahead to Category E — the forwarding chain itself is probably the problem.

3. Category A — Receipt did not appear in Expensify

Symptom: you forwarded or emailed a receipt to receipts@expensify.com and nothing shows up in Expensify at all — no expense, no processing state, no “Checking” placeholder. Treat this as an upstream delivery or sender-matching issue before troubleshooting SmartScan itself.

Sending address not verified as a secondary login

Cause: Expensify associates emailed receipts with the primary login or a verified contact method. Unverified senders may not route to your account.

Fix: Settings → Account → Profile → Contact Methods. Add the address, then complete the Magic Code verification from that inbox. See the full email receipts to Expensify setup walkthrough.

Typo in the destination address

Cause: Sent to receipt@expensify.com (singular), receipts@expensifiy.com, or a similar typo. Correct the address before troubleshooting SmartScan itself.

Fix: The correct address is exactly receipts@expensify.com. Save it as a contact to eliminate repeat typos.

Gmail or Outlook flagged Expensify's bounce as spam

Cause: When something goes wrong, an error or notification email may not be obvious in your inbox. Spam/junk search can still be a useful diagnostic, but do not rely on it as the only signal.

Fix: Search your spam/junk folder for from:expensify.com. If you find Expensify messages there, adjust your mail rules so future notices are easier to spot.

Attachment type not supported

Cause: Expensify handles common receipt images and PDFs best in this flow. Its email guidance lists additional accepted formats, but HEIC and WEBP files, encrypted PDFs, or attachments that were repackaged by a forwarding chain are riskier inputs.

Fix:Setting iPhone Camera to Most Compatible (Settings → Camera → Formats → Most Compatible) can avoid HEIC uploads. Or open and re-export the file as JPG/PNG before sending, or resend the original PDF if the vendor provided one.

4. Category B — Arrived but SmartScan stalled or produced an unreadable result

Symptom: the receipt is visible in Expensify, but it's stuck in a status like “SmartScanning” for too long, never produced useful fields, or is blocking your report from submitting with a “waiting for SmartScan to finish” warning.

“Checking” vs “SmartScanning” are different states. A receipt that remains in an upload/checking state should be treated as an arrival or connectivity problem first. “SmartScanning” means Expensify has an item to process, but it is still worth checking receipt quality and contacting Concierge if it does not complete.

Stuck on SmartScanning

Cause: Expensify positions SmartScan as quick, but processing can vary. Receipt quality, file format, connectivity, and account matching are better troubleshooting signals than an exact wait time.

Fix: Review the receipt, sender, and file type first. If the same expense still does not complete, contact Concierge with the report or expense details.

Failed scan or unreadable receipt

Cause: The image quality was too poor, the crop missed part of the receipt, or the attachment was in a format Expensify did not parse cleanly.

Fix:Replace the attachment with a cleaner image or the original PDF. For future receipts, re-photograph flat-on, in daylight, and avoid screen-of-screen captures entirely — a downloaded PDF from the vendor portal works far better than a phone photo of the same email on a monitor.

Email signature image confusing OCR

Cause: When you forward an email, some clients convert your HTML signature (with logo) into an attached image. SmartScan sees two attachments and can route to the wrong one, or can combine them into a single garbled receipt.

Fix: Strip your signature before forwarding, or download the original invoice PDF from the vendor and attach just that to a fresh email.

Report blocked: “waiting for SmartScan to finish”

Cause:Expensify won't let you submit a report while any expense on it is still SmartScanning, because the receipt data is not ready for review yet.

Fix: Either wait for SmartScan to finish, or detach the offending expense from the report if your policy allows it, submit without it, and add it back later once the scan completes.

5. Category C — SmartScan extracted the wrong data

Symptom: SmartScan finished, the expense has values, but the amount, date, merchant, or currency is wrong. The usual fix is the same — edit it manually — but understanding why it got it wrong helps you choose better receipts going forward.

Amount picked up the tip line, not the total

Common on US restaurant receipts where the printed total includes a blank tip row and a “grand total” row. OCR sometimes grabs the larger number from whichever line happens to be cleanest. Fix in-place on the expense.

Date = statement date instead of transaction date

Credit card statements, subscription receipts, and “thanks for your purchase” confirmations often show two dates. SmartScan's vendor parsers usually pick correctly for big-name vendors, but for the long tail you get whichever date OCR read first.

Merchant = parent company, not the DBA

SmartScan returns “YUM Brands” instead of “Taco Bell”, or “Darden” instead of “Olive Garden.” Fine for reporting, annoying for categorisation. Edit manually, and accept that next month's receipt from the same vendor may still say the parent company — treat your correction as a fix for the current expense.

Currency mis-detection on international invoices

€, £, and $ are easy to confuse when the currency symbol is tiny or printed in a decorative font. SmartScan tends to default to your account currency on ambiguous receipts, which means a €100 EU invoice can land in your reports as $100 USD. Always double-check currency on foreign vendors.

Treat your edits as a fix for the current expense. Expensify does not clearly document any personal training loop from your corrections. If a vendor is consistently messy, build the expectation that you'll keep reviewing those receipts.

6. Category D — Duplicates and workflow blockers

Symptom: the receipt is in Expensify, but the workflow is still not clean. You might see a duplicate expense, a report blocked while a receipt is still processing, or a receipt that landed separately from the card transaction you expected it to match.

The most common cause is that the same receipt arrived twice: once from a manual forward and once from a vendor resend, or once as a receipt and once as a card transaction that never merged. Another common cause is that the receipt is still processing, so Expensify temporarily holds the report open until the scan completes.

Fix: review duplicates by amount/date/merchant, merge or delete the extra expense where appropriate, and wait out in-flight scans before submitting the report. If duplicates keep happening from forwarding rules, simplify the intake path so the same receipt is not being pushed into Expensify more than once.

7. Category E — The forwarding-chain problem (the real root cause most guides miss)

Here's the one many troubleshooting articles underplay. If you've verified your secondary login, confirmed the file format, waited out the SmartScan queue, and the forwarded receipt from Gmail or Outlook still fails, the problem may be the forwarding chain rather than SmartScan itself.

When Gmail or Outlook auto-forward a message, they don't just relay it untouched. They can change message headers or envelope details that sender-matching systems rely on. Specifically:

What Gmail/Outlook auto-forward does to your receipt email

Auto-forwarded mail can still look like it came from the original sender — the forwarded email may arrive at Expensify still looking like it came from the vendor, not from your linked email. Expensify routes receipts by matching the sender to a verified login or contact method, so a message that still looks like “billing@somevendor.com” can miss your account.
Forwarding rules can repackage attachments or email content — attachments and inline content can arrive in a different shape than the original email, which increases the odds of missing or incomplete receipt data.
Manual forward actually works — usually — clicking Forward in Gmail composes a new message from your own address, which is what Expensify needs. The catch is usability: you have to remember each receipt.

The tell: the exact same receiptworks when you manually forward it from your phone's Gmail app (which sometimes preserves more headers), but fails from a Gmail auto-forward rule. Or: a vendor receipt works when you email it fresh from a web portal, but the same receipt forwarded from your Outlook rule lands in limbo. That's the forwarding chain doing surgery on the envelope.

The practical fixes are: (a) stop using auto-forward and manually forward each receipt from the native Gmail/Outlook UI, or (b) avoid relying on the forwarding chain by using a tool that connects to your inbox directly and helps you send receipts through a cleaner review workflow. That's what we cover next.

8. When to stop troubleshooting and switch approach

If you've spent a long session clicking through Concierge threads, re-verifying your secondary login, reshooting receipts, and watching the same ones fail again — take a breath. You're not doing anything wrong.

Honest framing: if you've worked through Categories A, B, C, and D, and receipts still fail between your Gmail/Outlook auto-forward rule and Expensify, the problem is often structural. The forwarding chain can change headers you don't control, and configuration inside Expensify may not fix a sender-matching problem introduced before the receipt arrives. Expensent doesn't fix SmartScan's OCR misreads or Expensify-side policy/workspace settings — it only removes the forwarding-chain variable. But for many people stuck at this point, that may be the entire problem.

At that point you have two realistic options. One: manually forward each receipt from the native Gmail or Outlook UI — works, but puts the burden back on you to remember each receipt. Two: avoid relying on the forwarding chain entirely.

How Expensent avoids relying on the forwarding chain

1.Connect your inbox — OAuth where supported for Gmail, Google Workspace, Outlook, and Microsoft 365, or supported IMAP using provider-specific connection settings. No Gmail filters to configure and no auto-forward rules to verify.
2.Review the invoices and receipt emails Expensent identifies — statuses help separate the ones ready to forward, the ones that need a portal download, and the ones that need a second look.
3.One-click forward to receipts@expensify.com — or create a rule from an existing invoice so the next one like it is auto-forwarded when it arrives. No more remembering.
4.Rules handle future similar emails after you approve them — you do not have to keep maintaining brittle keyword filters or remembering every monthly invoice by hand.

Why this fixes Category E specifically

Because Expensent removes the need to rely on Gmail auto-forward rules as the main intake path. You review invoices and receipt emails it identifies, forward the right ones, and let approved rules handle future similar emails. Make sure you've verified the sending address as a contact method in Expensify first — that is still a one-time Expensify-side step.

Want the full setup walkthrough? Read the Expensent → Expensify setup guide, or see the Expensify integration page for the feature breakdown. Related reading: Gmail to Expensify workflow and prevent missing receipts in Expensify.

Get Started

9. Frequently Asked Questions

Why is my Expensify SmartScan taking so long?

Expensify positions SmartScan as a quick way to read receipts, but processing can vary by receipt quality and account state. If a receipt remains stuck, check whether it actually arrived, confirm the sender/contact method, replace blurry or unsupported inputs with a clearer image or original PDF, and contact Concierge with the report or expense details if it still does not complete.

What usually causes a failed or unreadable SmartScan?

The most common causes are a blurry or dark photo, a screenshot instead of the original receipt, a tightly cropped image, a receipt that includes extra images or signatures, or an attachment format Expensify does not handle well. If the receipt exists in Expensify but the scan is incomplete, replace it with a clearer image or the original PDF and edit the current expense manually if needed.

Why don't my forwarded Gmail receipts show up in Expensify?

This is usually one of two things. First, the sending address must match a primary or verified contact method on your Expensify account, or the receipt may not route to your account. Second, Gmail auto-forwarding and Workspace routing can preserve original sender attribution or otherwise change the message path, so test the exact route before relying on it. Manually clicking Forward in Gmail sends from your own address, which Expensify can match when that address is linked, but you still have to remember each receipt. Expensent avoids relying on Gmail's forwarding-address verification flow by connecting to your inbox and letting you review and send the right receipt emails.

Can I retry a failed SmartScan?

If the receipt is already in Expensify but the scan is bad, the safest path is to replace it with a cleaner image or the original PDF and then correct the expense manually if needed. For receipts still stuck in SmartScanning, wait first; Expensify treats them as still in progress. If a receipt is still stuck after a long delay, contact Concierge with the report or expense details.

What makes SmartScan more accurate?

Use the original vendor PDF when you have it, or a clear flat-on receipt photo with good lighting and tight cropping. Avoid screenshots, forwarded chains with extra signature images, encrypted PDFs, and attachments that were heavily reformatted in transit. Clean input quality matters more than any setting inside Expensify.

Why did SmartScan extract the wrong amount?

Common causes: SmartScan read the tip line instead of the total (on restaurant receipts), pulled the statement date instead of the transaction date, picked up the parent company name instead of the DBA (e.g., "YUM Brands" instead of "Taco Bell"), or mis-detected the currency on multi-currency invoices. Also: if your receipt image includes an email signature or a second receipt in the same frame, OCR can cross-contaminate the fields. Fix: edit the expense directly — amount, date, merchant, and category are all editable. Treat your correction as a fix for the current expense rather than something that will automatically clean up the next one.

How do I add a secondary email so my receipts show up?

On the Expensify website, go to Settings → Account → Profile → Contact Methods and add the email address you plan to forward receipts from. Expensify sends a Magic Code to that inbox; complete that verification before relying on the address for receipt forwarding. Expensify says contact methods are managed on the website, not the mobile app, and you can add multiple contact methods when you forward from both personal and work inboxes.

Does editing a SmartScanned expense teach it to do better next time?

Assume your edits fix the current expense, not the next one. Expensify does not clearly document any per-user training loop from your manual corrections, so if a vendor's receipts are consistently messy you should expect to keep reviewing them.

What file types does receipts@expensify.com accept?

Use clear receipt images or PDFs and keep them small and simple. PDF, JPG, and PNG are the safest simple formats for receipt forwarding, while Expensify's email guidance lists additional accepted attachment formats. Avoid encrypted PDFs, HEIC or WEBP attachments, and files that were wrapped or reformatted by a forwarding chain before they reached Expensify.

Why does my receipt say "Checking" and never start scanning?

"Checking" and "SmartScanning" can point to different parts of the flow. Treat a receipt that remains in an upload/checking state as an arrival or connectivity problem first: reopen the app, check your internet connection, confirm the sender/contact method, and try re-adding a clear supported file if needed. If it is visible in Expensify but still will not process, contact Concierge with the expense or report details.

Done fighting SmartScan?

Connect your inbox, review invoices and receipt emailsExpensent identifies, decide what gets forwarded, and let the rules you approve handle the rest as new invoices arrive. No brittle auto-forward rules to maintain, and much less hunting for the one receipt that vanished.