Indian receipt OCR

Receipts in India come in more shapes than a scanner can guess at: GST retail receipts with tax-inclusive totals and a printed GSTIN, e-receipts sent by email and WhatsApp, UPI payment confirmation pages, and flimsy thermal paper from petrol pumps and toll plazas. Dynamite Docs reads them all, phone photos and digital files, into merchant, date, amount, and GST rows you review and export. No template to build for a single shop.

Try this workflow free or view pricing.

Indian receipts change shape, the fields do not

Retail receipts are printed on thermal paper that fades and curls, and photographed with phones, so the OCR has to work on low-contrast, noisy images.
A GST retail receipt packs a lot into a small slip: merchant GSTIN, tax-inclusive total, a CGST and SGST line, and often a truncated description.
UPI payment confirmations are a different document entirely, merchant, amount, reference ID, and timestamp, and they usually arrive as screenshots.
Petrol, toll, and delivery receipts each have their own layout, and expenses only reconcile when the right amount lands against the right merchant and date.

How Dynamite Docs handles Indian receipts

01 — Snap or drop the receipt

Phone photos work as well as digital files. GST retail receipts, e-receipts, UPI screenshots, and thermal-paper slips are read by the vision model you choose; clean digital files parse deterministically.

02 — Receipt fields are inferred

Merchant, receipt number, date and time, GSTIN, tax-inclusive total, and the GST break are pulled from each layout on the spot. No templates to build per shop or fuel brand.

03 — Review the few low-confidence rows

Confidence scores flag the amount or the GSTIN when the image is rough. Corrections become patterns, so the same shop’s receipts extract cleanly next time.

04 — Export to expenses

Rows export to Excel, CSV, or JSON, or push to Google Sheets, ready for expense reports, reimbursement, and your ledger.

Document types this workflow handles

GST retail receipts — tax-inclusive totals and GSTIN printed
e-receipts by email / WhatsApp — digital files, parsed deterministically
UPI payment confirmations — screenshots read as images
Petrol, toll & delivery slips — thermal paper, phone photos

What gets extracted from an Indian receipt

Inferred per layout. A typical receipt run yields these fields, each confidence-scored:

Merchant — Reliance Fresh — Kothrud
Receipt / invoice no. — RCPT-00078142
Date & time — 2026-08-04 14:32
GSTIN (merchant) — 27AAACR1234F1Z8
Taxable value — ₹1,322.03
CGST — ₹79.32
SGST — ₹79.32
Total (incl. tax) — ₹1,480.67
Payment method — UPI ··2045
UPI reference ID — 405194423881

A realistic example

A mixed batch of retail receipts and UPI confirmations extracts to rows like these:

Merchant	Receipt no.	Date	GSTIN	Total	Payment
Reliance Fresh — Kothrud	RCPT-00078142	2026-08-04	27AAACR1234F1Z8	₹1,480.67	UPI ··2045
Indian Oil (bunk) — Karve Rd	—	2026-08-05	—	₹2,000.00	UPI ··3310
Swiggy Instamart	ODR-88120544	2026-08-06	27AAHCS7788K1ZM	₹412.50	UPI ··2045

One schema across every shape a receipt takes

The variety is the point. A GST retail receipt prints a tax-inclusive total and the merchant’s GSTIN, which makes it an input-credit document as well as an expense record. An e-receipt sent by email is clean text with a different layout per store. A UPI confirmation is a timestamped screen showing the merchant, the amount, and a reference ID. Petrol and toll slips are low-contrast thermal paper. Treating them all as “a receipt” is what Indian receipt OCR means: one schema across every shape the document takes.

Photos are the default input, not the edge case. Most receipts in India are captured with a phone before the paper is lost, which makes vision the core of the work. The model you choose reads the merchant, the amount, and the date from the image; clean e-receipts and PDFs parse deterministically for free. Both paths land in the same rows, so an expense report mixes paper and digital sources without a second thought.

The GSTIN is the field worth checking. On a retail receipt it is the merchant’s, and it ties the expense to an input-credit trail an auditor may want. Confidence scores flag it when the thermal print is rough, and the correction becomes a pattern the next receipt from the same merchant reuses. The total is usually worth a glance too, because a tax-inclusive slip hides the split between taxable value and tax, and that split matters once the receipt reaches your books.

Expense reconciliation is where the rows pay off. Each receipt’s amount has to land against the right merchant and the right date, and that match only works when the extracted data is exact. Batch a month of receipts, review the low-confidence handful, and export the clean rows for reimbursement or your ledger, instead of keying each slip by hand.

Why bring-your-own-AI matters for receipts

Receipts are the most personal documents you process, carrying places, times, and spending patterns, so who reads them is a privacy decision as much as a quality one. Bring your own key, lock sensitive batches to no-training providers, or run fully local with Ollama and keep the pixels on your own machine.

Photos are the default input, not the edge case, and the vision model you pick reads merchant, amount, and date from the image while clean e-receipts and PDFs parse deterministically for free. The volume argument is real: hundreds of receipts a month, each amount a small risk in the expense ledger.

The merchant and category corrections your team makes are remembered per shop, so the second batch from the same store extracts cleanly. The rows export to Excel, CSV, or JSON for reimbursement or your books, and they stay yours.

Questions, answered

Does it read phone photos of receipts?

Yes. Photos of thermal-paper slips, retail receipts, and UPI screenshots are read by the vision model you choose, alongside clean digital PDFs and e-receipts.

Does it extract the GSTIN printed on retail receipts?

Yes. The merchant’s GSTIN comes out as a confidence-scored field where one is printed, along with the taxable value, CGST, SGST, and the tax-inclusive total.

Can it handle UPI payment confirmations?

Yes. UPI payment pages and screenshots are read like any other receipt, with merchant, amount, timestamp, and the UPI reference ID extracted into the same rows.

Does it file input-credit claims or prepare returns?

No. Dynamite Docs extracts and structures the receipt data; input-credit decisions and return preparation remain with your CA or team, who review the confidence-scored rows before exporting.