Duplicate receipts: how to avoid double-counting an expense or a reimbursement

Short answer: a duplicate receipt isn't just clutter — it inflates your totals, can get you reimbursed twice for the same purchase, and quietly throws off anything you export for an accountant. Resiboo checks every new scan against your existing receipts and flags a likely repeat instead of silently filing it as a second, separate expense.

How a receipt gets duplicated

It happens more often than it sounds like it should:

• Scanning it twice by accident — retaking a photo because the first one looked blurry, without realizing the first scan already saved.
• Reimbursement double-dipping — you scan a client dinner for your own records, then scan it again weeks later while building an expense report, forgetting it's already in the app.
• Shared purchases — splitting a bill with a roommate or a travel companion, and both of you scan the same physical receipt into your own copy of the app.
• Rescanning after a correction — retaking a photo to fix a bad crop instead of using the receipt's own Rescan option, which creates a genuinely new entry instead of updating the existing one.

None of these are careless, exactly — they're just the natural result of receipts moving between your hands, a shared table, and a phone camera more than once.

How the check works

Once a scanned receipt has both a merchant and a total — the two fields Rung 0 extraction reads on every capture, no AI setup required — Resiboo compares it against your existing receipts for a same-day match on total, currency, and a normalized version of the merchant name (so "SM Supermarket" and "SM SUPERMARKET #042" still match). If it finds one, the new receipt gets flagged as a possible duplicate of the original.

This is deliberately narrow. It doesn't try to catch a duplicate from a different day, or two genuinely separate purchases at the same store on the same day that happen to cost the same — same-day, same total, same merchant is the bar, chosen to avoid false positives on days you legitimately visit a merchant twice.

What you see, and what it doesn't do

A flagged receipt shows a dismissible banner on its detail screen — "Possible duplicate — matches this merchant, on the same date, for the same amount" — naming the merchant, date, and amount it matched — with two actions, Not a duplicate (dismisses the flag for good) and View original (jumps straight to the receipt it matched, so you can compare before deciding).

Importantly, this is a soft flag, not a block. A possible duplicate saves normally either way — nothing is silently rejected or held back — and it surfaces in the Receipts tab's Needs attention filter alongside unconfirmed and low-confidence scans, so it's a list you check on your own schedule rather than a popup you have to resolve immediately mid-scan.

Where this actually saves money, not just clutter

• Reimbursements. If you're exporting receipts for a client or an employer, a duplicate that slips through means claiming the same expense twice — the kind of thing that's awkward to walk back once it's been paid.
• Freelance and business filings. A duplicated expense inflates what you report as spent, which matters if you're tracking deductible business expenses and want the total to be defensible, not just plausible.
• Household budgeting. Two entries for the same grocery run makes a normal month look like an unusually expensive one — the kind of noise that erodes trust in your own spending totals.
• A shop's end-of-day total. A busy counter means retaking a blurry photo sometimes — the same check catches it there too, so a retake doesn't quietly double-count a sale in your daily payment log.

What to do when the banner shows up

1. Check View original first. Nine times out of ten, one glance at the date, total, and photo confirms it's the same purchase.
2. If it genuinely is a repeat, delete the newer one rather than leaving both — a dismissed flag stops the nagging but doesn't merge the two records for you.
3. If it's a coincidence — same store, same amount, different purchase — tap Not a duplicate and move on; Resiboo won't re-flag that same pair again.

What it doesn't catch

The check only runs same-day, and only once a receipt has a merchant and a total — a manually entered receipt with no total yet, or a duplicate scanned a week apart, won't trigger it. It's a safety net for the most common accident, not a full reconciliation engine.

Resiboo checks every scan against your existing receipts automatically, on-device, and surfaces anything that looks like a repeat in Needs attention — so a double scan gets caught before it becomes a double reimbursement.