← All posts

When a receipt scan gets one price wrong

A price read as RM7.30 instead of RM7.80 can change a shared bill. See how SplitYours checks uncertain readings and presents a suggested correction for review.

Case study · By Nexstrive Services · · 3 min read · Updated

A receipt price of RM7.80 is scanned as RM7.30. The amount looks plausible, but the error changes the item subtotal and can affect each person’s share of the bill.

Correcting every line manually reduces the value of scanning. Accepting the first reading without checking can carry the error into the final split.

SplitYours uses the receipt’s other amounts to check uncertain prices and suggest a correction. The person adding the bill reviews any changed line before accepting it.

Check the reading against the receipt

This illustrative example uses synthetic recognition input to demonstrate the current parser. It is not a customer receipt or a test of recognition accuracy from a photograph.

Item Printed price Initial reading
Noodles RM7.80 RM7.30
Rice set RM12.20 RM12.20
Shared side RM10.00 RM10.00
Item subtotal RM30.00 RM29.50

The receipt shows RM30.00 of items, RM3.00 service charge, RM1.80 service tax and a final total of RM34.80. The scanned items are 50 sen short of the printed subtotal.

The engine checks the item amounts as well as the receipt summary. Reproducing the final total from the printed subtotal alone would leave the incorrect item price unresolved.

Present a supported correction

In this example, the recogniser also supplies RM7.80 as a possible reading of the same price. The engine checks that alternative against the receipt and selects it as the suggested correction.

The corrected calculation is:

Component Amount
Item subtotal RM30.00
Service charge, 10% of items RM3.00
Service tax, 6% of items RM1.80
Calculated and printed total RM34.80

For Malaysian food-and-beverage services, service charge is excluded from the service-tax base. Royal Malaysian Customs confirms this in its Food & Beverage guidance, version 7, FAQ 8.

Where another OCR reading is unavailable, the engine can sometimes suggest an estimated price from sufficiently reliable receipt amounts. An estimate remains marked for confirmation against the photo.

Review the changed line in SplitYours

We checked both versions of this example against the current parser. It recovered RM7.80 from an alternative reading and, in the separate estimation scenario, from the receipt balance. Both results kept the changed line unverified.

The user can inspect the suggested price, compare it with the photo and confirm or edit it before adding the items to the bill. This provides a specific correction to review and reduces the need to re-enter an uncertain price from the beginning.

Matching totals provide evidence of arithmetic consistency. They cannot establish that every item name is correct or that separate errors have not cancelled each other out. The user retains control of the reviewed bill.

Extend document checks to business workflows

The same approach could be adapted to expense claims, supplier invoices or delivery records. For example, an expense system could compare a scanned receipt with the claimed amount. An invoice workflow could check extracted lines against a purchase order and flag differences for review.

Those applications need rules suited to the document, business and jurisdiction. SplitYours demonstrates how document evidence can support a suggested correction while keeping the reviewer involved.