Browse guides

Reviewing OCR suggestions

What OCR gets right, what to double-check, and why nothing posts automatically.

What OCR actually does

When you upload a receipt, Verluma Entry reads the document and suggests values for vendor, date, subtotal, tax, and total. That's the entire job: turning a photo into a set of starting values you can accept, correct, or ignore. It doesn't classify the transaction, decide a tax treatment, or touch anything in your books.

What's worth double-checking

  • Totals with handwriting or a faded thermal print — the most common source of a misread digit.
  • Tax split on receipts with multiple tax lines (GST and PST shown separately, for example) — confirm which line landed where.
  • Vendor name on a receipt with a franchise or holding-company name printed differently from the storefront.
  • Date on receipts using a day/month order that's easy to misread the other way.

Correcting a field

Every suggested field is editable in place — click into it and type the correct value. There's no separate “reject and start over” step; you're always looking at the same form OCR pre-filled, just with the ability to change anything before you confirm it.

TipIf OCR gets a field wrong often for a particular vendor (a receipt format it consistently struggles with), it's usually faster to just re-type that one field each time than to expect the suggestion to improve — it's reading the document fresh every time, not learning your vendors.

Why nothing posts automatically

A misread total or the wrong tax treatment in your books is a real problem — for filing, for your accountant, and for you. Requiring a person to confirm every transaction, every time, is a deliberate design choice, not a missing feature. See the review workflow guide for the checkpoint that comes after entry.