## TL;DR

Expensify matched two legitimate similar charges (same vendor, same amount, close dates). Open both expenses, confirm each has its own receipt, add a note distinguishing them, and submit; the reviewer clears the flag.

## Error

```text
duplicate receipts flagged incorrectly by expensify
```

## Steps

1. Open both flagged expenses and view their receipts. Expected: two separate receipts, not one receipt attached twice.
2. Confirm the charges are genuinely distinct: different dates, different times, or different items on similar totals. Expected: you can articulate the difference.
3. Add a comment on each expense noting the distinction (for example, "client lunch Tuesday" vs "team lunch Thursday"). Expected: the reviewer sees the explanation inline.
4. Submit both expenses. Expected: they route with the flag visible to the reviewer.
5. If one receipt was accidentally attached to both, remove it from the wrong expense and attach the correct one. Expected: each expense carries its own receipt.

## When to use

- Expensify flags legitimate repeat charges as duplicates.
- Each charge has its own receipt.

## When not to use

- The same charge was submitted twice (delete the duplicate).
- The flag comes from the accounting import, not Expensify (see the QuickBooks skill).

## Tool compatibility

- Expensify duplicate detection on web and mobile.

## Variant phrasings

### Possible duplicate: review required

Same flag, reviewer-facing wording.

### These expenses look like duplicates

The in-app prompt form of the same check.

## Why it happens

Duplicate matching keys on merchant, amount, and date proximity. Routine repeat purchases (daily transit, weekly team lunch) naturally collide on all three, so the matcher asks a human to confirm.

## Provenance

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