Scanning receipts
Known issue: receipt scanning is currently failing on some devices with a generic “Couldn’t read that image” error. A diagnostic build is rolling out. See Known issues for status, and use manual entry in the meantime.
Receipt scanning creates an expense from a photo of a receipt.
The flow
- Tap ＋ → Expense → Scan a receipt.
- Choose the camera or import from your photo library. Camera use is optional by design — every flow has a no-camera path, and manual entry always works.
- Text recognition runs on the device and Varuno proposes the transaction details.
- A review screen shows everything it extracted; all fields are editable. Nothing is saved until you confirm.
The receipt image is a working copy for the import and is deleted afterwards. Recognition runs entirely on the phone — the image and its text are never uploaded.
Troubleshooting
- “Couldn’t read that image… (TYPE)” — newer builds include the error type in parentheses. Retry with the camera in good light, or fall back to manual entry. If you report the bug, include the exact TYPE shown, whether you used camera or photo import, and your device model. By design the app only surfaces the error type — never the image or its content — so that is all support needs.
- Blurry or crumpled receipts extract poorly. Flatten the receipt and fill the frame.
About the camera permission
iOS asks for camera access the first time you scan with the camera (“scan paper receipts into transactions”). If you decline, photo import and manual entry still work. The photo-library permission mentions bank-notification screenshots — that refers to a manual “import a screenshot” flow you start yourself; Varuno never reads your photos or notifications in the background.