Resolve OCR corrections and pump discrepancies
Some odometer and pump readings need a person: the AI could not confirm them, or the driver's and the merchant's pump readings disagree. Decide them from the Review Queue so the right reading reaches the vehicle and the order.
Before you start#
- Role: Tenant Admin or Tenant Supervisor, the roles that can review OCR submissions.
- Where: Review Queue in the web portal sidebar, then OCR Corrections or Pump Discrepancies.
- How you hear about it: you get a notification when a reading is sent for review or a pump discrepancy is raised.
- What each tab contains and why items arrive there is on Review queue; how the AI check works is on Odometer and pump photo readings.
Steps#
Correct a reading#
- Open OCR Corrections. Each row shows Image, Driver, Context, OCR Value and Captured; click Review on the reading. Context says what was read: an odometer, a pump reading, or a document field.
- Compare the Source Image with the OCR Value and the LLM Value. Read the LLM Reasoning, and for an odometer the Rejected Candidates the AI ruled out.
- For a pump photo, check the Pump Breakdown: litres, unit price and total, marked cross-check OK or liters × price ≠ total.
- For an odometer the driver typed, check User vs LLM reconciliation. Its badge says why the reading is here: Escalated — user and LLM values diverge or Escalated — LLM reading unavailable. When both values are shown, compare the User value with the LLM value: they were sent for review because they are further apart than the Tolerance used, in km. Divergence is that gap as a share of the larger reading, not in km.
- Under Submit Correction, enter the right reading in Corrected value and click Commit Correction. You return to the list with OCR correction committed.
There is no separate accept button: to accept a reading, enter it in Corrected value. For an odometer the driver typed, that is the User value.
Resolve a pump discrepancy#
- Open Pump Discrepancies. Each row shows the order, driver, store, both photos, Driver (L), Merchant (L), Delta (L) and when it was Flagged.
- Click Review on the discrepancy. Compare the Driver Reading and Merchant Reading photos, the Delta and the Tolerance used.
- Under Resolution, choose one:
- Confirm Driver Reading and confirm Confirm driver reading as accurate?;
- Confirm Merchant Reading and confirm Confirm merchant reading as accurate?;
- Dismiss (tolerable variance), then type a Reason for dismissal and click Dismiss.
- You return to the list with Discrepancy resolved.
What happens next#
- Corrected odometer: becomes the vehicle's verified odometer reading, which feeds maintenance and resets the distance the GPS-based refuel limit counts. The order keeps the odometer the driver entered. A corrected reading far ahead of the vehicle's estimated odometer is held for odometer review instead of being applied; see Review flagged odometer readings.
- Corrected document field: updates that field among the document's extracted fields.
- Corrected pump reading: is recorded as that side's pump reading on the order. It does not change the order's quantity or amount.
- Pump discrepancy decision: is recorded on the discrepancy with your name and the time, with the chosen reading marked accurate and the other inaccurate, or with your dismissal reason. The order's quantity and amount do not change.
- Each correction is recorded in the audit log with the original and corrected values.
Rules and limits#
- Decisions are final. A committed correction or a resolved discrepancy leaves the queue and cannot be changed from it. A discrepancy can come back if new readings are paired for the same refuel and still disagree; a pending one leaves the queue by itself if a new pair agrees within tolerance.
- First decision wins. If someone else decided the item first, yours is refused: you return to the list with a message that the item is no longer pending, and it stays as they left it.
- Odometer rules still apply. A corrected odometer that is not a number, or that the odometer rules refuse, is not saved.
- Your company only. You see only your company's items.
If something goes wrong#
| Message | Cause | Fix |
|---|---|---|
| Corrected value is required. | Corrected value was empty | Enter the reading |
| Failed to apply OCR correction to downstream entity. | The value is not a number, or the odometer rules refuse it (for example lower than the current reading) | Check the photo and enter a valid reading |
| This submission is already resolved (status: …). | You opened a reading someone already decided | Nothing to do |
| A message that the item is no longer pending | Someone decided it while you were working on it | Nothing to do; check their decision in the list |
| Dismiss reason is required. | Reason for dismissal was empty | Enter why the difference is acceptable |