Why duplicates happen

The most common sources of duplicate entries in Stareceipt are:

Photo + email overlap — you capture a paper receipt with your camera and the same transaction also arrives as an email receipt.
Double submission — two team members photograph the same receipt at a shared dinner.
Re-upload after editing — a receipt is deleted and re-uploaded from a photo library.
Email forwarding — the same email invoice is processed twice because it was forwarded manually and also caught by an automatic forwarding rule.

How detection works

Receipt groups likely duplicates within the same ledger. Current clients expose duplicate fingerprints, duplicate markers, and duplicate candidate lists; matching may combine receipt content similarity with overlapping fields such as merchant, amount, date, and tax.

Where flags appear

Duplicate signals appear in the following places:

Receipt detail and receipt lists — receipts can carry duplicate markers or links to related items.
Web Duplicates page — the Web app exposes a dedicated Duplicates page for unresolved groups.
Mobile duplicate-management flows — mobile clients can surface duplicate groups and let you choose which receipts to keep.

Resolving a flag

Current clients focus on two resolution patterns:

Dismiss a false positive

Keep both receipts and mark the pair as non-duplicate. This records a duplicate exception so the same pair does not keep surfacing as an unresolved warning.

Use this when two receipts look similar but are genuinely different transactions.

Keep one and delete extras

Choose the receipt you want to keep and delete the extra receipt or receipts from the duplicate-management UI.

Use this when multiple receipts represent the same real transaction and you want to preserve only one surviving record.

Review before deciding

Open the related receipts side by side before you dismiss the warning or delete anything.

False positives

If Stareceipt is flagging entries that are genuinely different, the most common cause is a merchant that charges the same round amount on a regular basis (e.g. a weekly subscription or a fixed-price parking garage).

Use the false-positive dismissal flow so both receipts remain visible without continuing to appear as an unresolved duplicate pair.

Duplicate detection across ledgers

Duplicate detection is typically scoped per ledger so that unrelated projects and entities do not interfere with each other's matching results.