Expensify SmartScan Troubleshooting
Stuck on “SmartScanning” forever? Forwarded receipts vanishing? 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 April 22, 2026
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 expect SmartScan to take anywhere from a few minutes to a few hours. 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.
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 never arrived at 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. The receipt didn't reach Expensify's servers, so nothing in the SmartScan flow has a chance to run.
Sending address not verified as a secondary login
Cause: Expensify only accepts receipts from the primary login or a verifiedsecondary login. Unverified senders are silently dropped — no error, no bounce.
Fix: Settings → Account → Profile → Contact Methods → Add a secondary login. 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. These silently bounce or go nowhere.
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, Expensify often replies with an error email. If Gmail or Outlook files that reply into Spam, you never see it and assume nothing happened.
Fix: Search your spam/junk folder for from:expensify.com. Whitelist the domain so future bounces land in your inbox.
Attachment type not supported
Cause: Expensify works best with clear receipt images or PDFs. HEIC and WEBP files, encrypted PDFs, or attachments that were repackaged by a forwarding chain can all cause the receipt to vanish before it is usable.
Fix:Setting iPhone Camera to Most Compatible (Settings → Camera → Formats → Most Compatible) sidesteps any HEIC edge case in Expensify's email path. 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.
Stuck on SmartScanning for hours
Cause:Expensify publishes that SmartScan takes “a few minutes to a few hours” depending on receipt quality and backlog volume. During month-end, tax season, and major holidays the human review queue balloons and multi-hour waits are normal.
Fix:Wait. If you're past 24 hours on the same expense, ping Concierge with the report ID so they can manually force it through the pipeline.
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 — that's by design, to avoid approving a report whose totals are about to change.
Fix: Either wait for SmartScan to finish, or detach the offending expense from the report, 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 fix is always 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.
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 most troubleshooting articles never mention. If you've verified your secondary login, confirmed the file format, waited out the SmartScan queue, and the forwarded receipt from Gmail or Outlook stillfails — the problem isn't on Expensify's side. It's the forwarding chain.
When Gmail or Outlook auto-forward a message, they don't just relay it untouched. They rewrite the envelope. 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 every receipt, every time.
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 only fixes are: (a) stop using auto-forward and manually forward each receipt from the native Gmail/Outlook UI, or (b) bypass the forwarding chain completely 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 the last hour clicking through Concierge threads, re-verifying your secondary login, reshooting receipts, and watching the same ones vanish 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 vanish between your Gmail/Outlook auto-forward rule and Expensify, the problem is structural. The forwarding chain itself is rewriting headers you can't control, and no amount of configuration inside Expensify will fix a header that gets rewritten before Expensify ever sees it. Expensent doesn't fix SmartScan's OCR misreads or plan quotas — it only removes the forwarding-chain variable. But for most people stuck at this point, that's the entire problem.
At that point you have two realistic options. One: manually forward every receipt from the native Gmail or Outlook UI — works, but puts the burden back on you to remember every receipt, every month. Two: skip the forwarding chain entirely.
How Expensent bypasses the forwarding chain
- 1.Connect your inbox via OAuth — Gmail, Google Workspace, Outlook, Microsoft 365, or IMAP. No password shared, no Gmail filters to configure, 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 never miss a receipt in Expensify.
9. Frequently Asked Questions
Why is my Expensify SmartScan taking so long?
What usually causes a failed or unreadable SmartScan?
Why don't my forwarded Gmail receipts show up in Expensify?
Can I retry a failed SmartScan?
What makes SmartScan more accurate?
Why did SmartScan extract the wrong amount?
How do I add a secondary email so my receipts show up?
Does editing a SmartScanned expense teach it to do better next time?
What file types does receipts@expensify.com accept?
Why does my receipt say "Checking" and never start scanning?
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.
Also see: pricing · how Expensent works