Check AI receipt extraction with arithmetic and source lines
Verify quantity, price, discounts, tax and currency against the image before importing a total into records.
In brief
Receipt extraction can read the wrong line or decimal while still returning valid JSON. Reconcile the arithmetic and source position before using the amount as a record.
A small manual check can catch an error that a tidy table or schema validator cannot see.
Read labels before amounts
Distinguish item price, quantity, subtotal, tax, discount, paid and change. A prominent number may be tendered cash rather than the purchase total. Check whether the receipt states tax is included before adding a separate amount.
Use arithmetic as a cross-check
In this deliberately invented example, two items at 3 plus one at 4 give a subtotal of 10; a stated tax of 1 gives 11 if that tax is additional. This is an explanation of the check, not a real extracted receipt. A mismatch means investigate the line or condition, not overwrite the source total automatically.
Keep correction traceable
Record the verified value and the source line or page, with access controls appropriate for the receipt. Keep uncertain entries out of automatic posting. If the image is too blurred, request a clearer permitted copy rather than asking the model to infer missing digits.
Before you act
Receipts can contain personal details. Share only appropriate material, and do not treat automated extraction as financial verification or a certified accounting record.
What to do next
- Read the currency, decimal convention and relevant line labels from the source.
- Multiply quantity by unit price and reconcile discounts and tax.
- Compare the computed and printed total, marking unreadable fields for review rather than guessing.