Reliably reading handwritten bills from a local shop in India is the hard part for any OCR tool. Short answer: not reliably. Handwriting varies too much, and the cost of one wrong digit is a wrong entry in your books, so the safer habit is to photograph the bill, type three fields yourself and let the payment record do the heavy lifting.
Why does handwriting break scanning?
Printed receipts have uniform characters in fixed positions. A kirana or hardware bill written on a carbon pad has none of that: digits run together, a 1 looks like a 7, a 4 looks like a 9, and the total is often underlined or circled over the figures. Carbon copies fade, and the pad's printed lines cut through numbers. Software can guess, but a guess that looks confident is the dangerous kind.
What should you do instead? Five steps
- Pay by UPI or card where you can. The payment shows in your bank statement with the exact amount, which is a typed record you did not have to read from paper.
- Photograph the bill the same minute, flat and in good light, with the total in frame.
- Type three fields yourself: shop name, date and the total you actually paid.
- Add the items only if you will need them later, such as for a warranty, and add them as a short note.
- Match the total against the statement line when it posts and fix any difference.
Worked example: one kirana bill
Say the pad bill reads atta 5 kg 240, dal 2 kg 310, oil 1 litre 165 and a circled total of 715. Add the lines yourself: 240 + 310 + 165 = 715. It matches, so you enter ₹715 for groceries on the day of purchase. Now say the shopkeeper had written 175 for the oil, with a total of 715. The lines now add to 725, not 715, so one of them is wrong. That is exactly the moment where a person catches an error that scanning would have passed straight through.
| Check | What you look at | If it fails |
|---|---|---|
| Lines add up | Sum of the written line amounts | Ask the shop, or enter the circled total and add a note |
| Total matches payment | UPI or card amount | Trust the payment, note the difference |
| Date is plausible | Written date against your day | Use the day you paid |
| Photo is legible | Total and shop name visible | Retake it before leaving |
Is there anything OCR is good for?
Printed, high-contrast text. A supermarket slip with aligned columns is a very different job from a pad bill, and even then the totals deserve a quick check. Treat any scan result as a draft that you confirm, never as a final entry.
What if the shopkeeper writes in a regional language?
Then the odds get worse, not better. Numerals may be written in a script the software was never tuned for, and abbreviations such as kg, ltr or pcs vary from shop to shop. You do not need to read the item names at all. Keep the photo for the names, and type only what your records need: the shop, the date and the amount you paid. If you must remember what a line meant, add a word in your own language to the note, because you will understand it later and a scanner may not.
- Shop name as you know it, not as it is printed.
- Amount paid, which you confirmed from the payment.
- One word for the kind of purchase, such as grocery or repair.
Where does an expense tracker fit in?
SpendixAI does not claim to read handwriting. You can import a bank or card statement, so the UPI payment becomes a row, and you add cash purchases by hand, one or several at once. A receipt photo can be kept with its transaction, and rows from an import are shown for review before they are saved.
One honest limit
If a shop gives only an unsigned, undated slip and you paid cash, nothing in software can fix the missing evidence. Write the amount, the shop and the date in your log that day, while you still remember it clearly.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


