## TL;DR

A single misread digit (7 as 1) drops the receipt total below the card charge or below a flag threshold, so the agent waves through an expense it should have questioned. Add a verification step: compare the OCR total against the card transaction amount, and flag any receipt where they differ beyond tolerance for human review. OCR is a guess; the card charge is ground truth.

## Error

```text
agent's ocr misread a 7 as a 1 on the receipt total  -  under-flagged
```

## Steps

1. Confirm the misread: open the receipt image and compare the printed total to the OCR value the agent used. Expected: the digit error is visible on the image.
2. Add a cross-check in the agent: compare the OCR total to the card transaction amount for the same expense. Expected: the agent computes the difference.
3. Flag for human review whenever the difference exceeds a small tolerance (e.g. a few percent or a fixed small amount). Expected: mismatched totals route to a reviewer instead of auto-passing.
4. Log the misread pattern (which digits, which receipt styles) to tune OCR preprocessing. Expected: the log shows where the OCR is weak.
5. Re-run the agent over the affected period with the cross-check enabled. Expected: previously under-flagged expenses surface for review.

## When to use

- OCR misreads a receipt total and the agent under-flags the expense.
- Receipt totals and card charges disagree with no flag raised.
- Tuning an audit agent's OCR verification.

## When not to use

- The merchant name is misread but the total is right (a different field).
- The card charge itself is wrong (a billing dispute, not OCR).
- The agent over-flags on tiny OCR differences (tune the tolerance instead).

## Tool compatibility

Applies to custom audit agents using OCR (Tesseract, cloud vision APIs, or expense-tool OCR; current 2026 releases).

### Variant phrasings

### ocr digit confusion on receipt totals

7/1, 6/8, and 3/5 are the classic confusions. Cross-check against the card charge.

### agent approved an expense with a wrong total

The OCR value was wrong and nothing verified it. Add the card-charge comparison.

### receipt total vs card charge mismatch unflagged

The verification step is missing. Flag on difference beyond tolerance.

## Why it happens

OCR confuses similar digit shapes, especially on faded thermal print and low-resolution photos. An agent that trusts the OCR total as fact inherits the error silently, and a 7-to-1 misread specifically shrinks the total, which biases the agent toward under-flagging. The card transaction amount is an independent, authoritative number for the same purchase, which makes it the ideal cross-check.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Fb6Q_KktabWCbc4zl0Md1Q