## TL;DR

Concur matches the new receipt against previously submitted ones by amount, date, and merchant fingerprint, and the match means one of the two lines is a re-submission. Open the exception detail to see which report and expense line it matches, then delete the duplicate line (or the duplicate report) and resubmit. Two genuinely different receipts with the same amount and date need a comment explaining the difference to clear the audit flag.

## Error

```text
Concur: report contains a duplicate of a previously submitted receipt
```

## Steps

1. Open the flagged report and click the exception to see the matched receipt details. Expected: the exception names the prior report ID, expense date, and amount it matched against.
2. Open that prior report and confirm the receipt really is the same transaction. Expected: the prior line shows the same merchant, date, and amount, confirming a true duplicate.
3. If it is a duplicate, delete the duplicate line from the current report (or withdraw the older report if that one was the mistake). Expected: the exception clears or drops to a warning.
4. Resubmit the report. Expected: the report moves to the next approval step with no duplicate exception.
5. If the two receipts are genuinely different purchases (same amount, same day), add an expense comment describing the difference and attach any secondary proof. Expected: the approver can clear the audit exception manually.

## When to use

- A Concur report throws a duplicate-receipt exception on submit.
- An audit exception points at a receipt from a prior submitted report.
- A receipt was uploaded twice (mobile app and email forwarding both captured it).

## When not to use

- The duplicate is across two different employees' reports (that is an approval-routing issue, not a duplicate line).
- The flag is on amounts that merely look similar but belong to different merchants.
- The report is rejected for policy reasons with no duplicate mention.

## Tool compatibility

SAP Concur Expense (Standard and Professional, current 2026 releases). Applies to web report editing and the mobile app upload flow.

### Variant phrasings

### "duplicate receipt detected" warning on upload

The mobile app flags the receipt at capture time against recent submissions. Check whether it is the same expense before discarding one copy.

### concur exception "previously submitted" on a hotel folio

Hotel folios split into room charges and incidentals often re-trigger the match when one half is submitted twice. Compare line-item totals, not the folio grand total.

### duplicate flagged after forwarding the same email twice

The receipts@ inbox captured the same email twice. Delete one attachment from the expense, keeping the one with the cleaner scan.

## Why it happens

Concur keeps a fingerprint of every submitted receipt: merchant, date, amount, and image hash. Re-uploading a receipt (phone scan plus email forward, or copying a report as a template) creates a second expense with an identical fingerprint, and the duplicate-detection audit rule fires on submission. The rule is conservative on purpose: expensing the same receipt twice is one of the most common accidental fraud patterns, so the system would rather flag two identical-looking legitimate receipts than miss a double claim.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GXqCQcgLo-nPlzA-t0fedA