A duplicate receipt is not a second expense — separate a request from an instruction

A no-code exercise: submit a fictional receipt twice, once as a photo and once as a PDF. Filename matching misses the duplicate. When evaluating OpenClaw, I would compare merchant, date, amount and reference, then leave ambiguous matches for review. Similar totals alone would not justify discarding a legitimate expense.

Present the sample as a customer request, then as an owner instruction. Discuss whether the source changes what the operator may do.

Which receipt field would you trust most for a duplicate check? What would that additional check change in your decision?

4 comments

A duplicate receipt is not a second expense — separate a request from an instruction