Use a simple capture routine to reduce blur, glare, shadows, and missing receipt edges.
Published by the AI Expense Editorial Team. AI Expense is developed and published by EmuInbox.
Problem: Use a simple capture routine to reduce blur, glare, shadows, and missing receipt edges.
Case notes for mobile users scanning receipts in changing light
The useful outcome in this case is to improve the source image before recognition begins. Start from the source document and record only what another person can verify. A complete-looking row is not useful when its merchant, date, amount or context cannot be traced back to evidence.
What arrives
The process begins when you place the receipt under even light and switch off direct flash when it creates glare. Before recognition, decide whether the file represents one transaction, several documents or an incomplete source.
What requires judgment
Next, hold the phone parallel to the page instead of shooting from an angle. The most relevant warning sign is trying to sharpen an unreadable photo later. Keep that issue visible instead of allowing automation to turn uncertainty into an apparently final value.
What must survive handoff
Then tap to focus on the smallest printed text before taking the photo, followed by retake the image when totals or tax lines are not legible at normal zoom. The finished record should prove that small text is readable, all four corners are visible, there is no bright reflection over the amount.
A blur diagnosis that takes less time than correcting bad OCR
A fuel receipt photographed inside a parked car may look acceptable as a thumbnail while the litres, unit price and tax line are unreadable at full size. Before running recognition again, identify whether the problem is motion blur, missed focus, glare or perspective. Each cause has a different fix, and repeated processing of the same weak image cannot recreate characters that the camera never captured.
Evidence that makes this example defensible
Evidence
What it proves
Motion blur
Letter edges smear in one direction; brace the phone and retake the image with more light.
Focus failure
The dashboard or table is sharp but the receipt text is soft; tap the smallest print before capture.
Glare or shadow
A bright or dark patch crosses the total; move the light source rather than applying extreme contrast later.
Questions to test the finished record
Are the smallest relevant characters readable at normal zoom?
Do all four receipt edges remain visible?
Can the retake be compared with the first image before replacing it?
Scenario-specific FAQ
Can sharpening repair every blurry receipt?
No. Sharpening may improve edges, but it cannot reliably recover text that was never resolved.
Is flash always a bad choice?
No, but direct flash should be avoided when glossy thermal paper reflects it over important fields.
Article-specific walkthrough: How to Fix Blurry Receipt Scans Before OCR
Use this sequence as a dry run for mobile users scanning receipts in changing light:
Opening condition: Place the receipt under even light and switch off direct flash when it creates glare.
First evidence test: Verify that small text is readable; specifically investigate trying to sharpen an unreadable photo later.
Mid-workflow decision: Hold the phone parallel to the page instead of shooting from an angle. Then tap to focus on the smallest printed text before taking the photo without changing the original source.
Exit condition: Retake the image when totals or tax lines are not legible at normal zoom. Completion requires that all four corners are visible and there is no bright reflection over the amount.
This walkthrough is intentionally tied to “improve the source image before recognition begins.” If the workflow produces a polished record but cannot demonstrate those conditions, it has solved a different problem from the one described in this article.
Record review matrix
Review test
Failure pattern
Response
Small text is readable.
Trying to sharpen an unreadable photo later.
Place the receipt under even light and switch off direct flash when it creates glare.
All four corners are visible.
Covering the receipt with a hand shadow.
Hold the phone parallel to the page instead of shooting from an angle.
There is no bright reflection over the amount.
Capturing only the total and not the merchant.
Tap to focus on the smallest printed text before taking the photo.
Two questions before completion
Could someone who did not capture the document explain why the accepted fields are correct?
Could that person retrieve the source after the record has been exported?
Retrieval and handoff test for this topic
Before completion, ask a second person to find the record without using its filename. Give that person only clues that belong to this article: the document type, an approximate date or amount, and the context implied by “improve the source image before recognition begins.” The result should expose the original source, reviewed fields and current status together.
Then test the next handoff. The receiver should be able to see why “small text is readable” was accepted and whether “trying to sharpen an unreadable photo later” remains unresolved. If either answer depends on the uploader remembering what happened, add the missing context before export.
Relevant AI Expense path
Open the related product workflow for capture, source review, search and export. Professional treatment of the record remains outside the app.