Screenshot reconciliation
2026-09-26 ·
screenshots ⟕ internal log (no GPay CSV)
· last run 27-Sep 05:16
· source /var/lib/recon/data/inbox/Manual-Deposit-Agent_1.xlsx
What do these buckets mean? (click to expand)
This run compared 2 sources: customer payment screenshots
(OCR-extracted) and the staff internal log XLSX. No GPay CSV was
used this time. Every screenshot and every log entry lands in one bucket
based on whether a match was found on the other side. Matching is by
12-digit UPI UTR, with an amount + time fallback.
⬇ Export full report (Excel)
Detailed multi-sheet XLSX — summary plus every bucket, row by row.
Primary buckets
Matched ✓
MATCHED
16 entries
₹34,680.00
Screenshot proof and a logged deposit agree. Amount
verified against the internal log. No action needed.
Open
Money came but not logged 🚨
ORPHAN_IMG
0 entries
≈ ₹0.00
Customer sent a payment screenshot, but staff never
logged it. Owed to customer / needs logging. (Amount is OCR-estimated.)
Open
Logged but no screenshot 🚨
PHANTOM
112 entries
₹3,35,804.00
Staff logged a deposit, but no customer screenshot backs
it. Some customers simply don't send proof — verify the payment arrived.
Open
Flags — issues that can appear alongside any bucket
Duplicate UTR
2
Same 12-digit UPI ID appears in more than one row.
0 in the internal log (possible double-credit) ·
2 in screenshots (customer sent proof twice).
Open log dups
Needs human review
0
OCR couldn't extract every field cleanly (usually a
missing UTR or amount). Open and fill in the gaps inline — corrected
rows get picked up on the next reconciliation.
Open
Pipeline totals (2026-09-26)
Screenshots: 17 rows · ₹36,680.00
Internal log: 128 rows · ₹3,70,484.00
Run reconciliation