expense report rejected: duplicate detected across two reports
Resolves a cross-report duplicate rejection by finding the two reports, keeping the correct line, and resubmitting. Use when an expense report is rejected because a duplicate was detected across two reports. Not for duplicates within a single report.
TL;DR
Two different reports contain the same expense (same merchant, date, amount), usually because a report was copied as a template or a receipt was uploaded twice into different drafts. Open both reports, delete the duplicate line from the wrong one, and resubmit the corrected report. The rejection is the duplicate control working across the report boundary.
Error
expense report rejected: duplicate detected across two reportsSteps
- Open the rejection notice and identify both reports and the duplicated expense line. Expected: you have the two report IDs and the matching amount and date.
- Compare the two lines against the source receipt. Expected: both lines reference the same underlying transaction.
- Decide which report should keep the expense (usually the earlier or the already-approved one). Expected: one report is clearly the rightful owner.
- Delete the duplicate line from the other report. Expected: that report no longer contains the duplicated expense.
- Resubmit the corrected report. Expected: the duplicate rejection clears and the report routes for approval.
When to use
- A report is rejected for a duplicate spanning two reports.
- A copied report template carried old expense lines into a new report.
- The same receipt was filed in two different monthly reports.
When not to use
- The duplicate is within a single report (fix the one report).
- The two lines are genuinely different purchases that happen to match.
- The rejection is for policy reasons with no duplicate mention.
Tool compatibility
Applies across expense tools with cross-report duplicate detection (Expensify, Concur, Ramp, Brex; current 2026 releases).
Variant phrasings
"duplicate expense found in another report"
Alternate wording for the same cross-report match. Identify both reports and remove one copy.
copied report caused a duplicate rejection
Template copies inherit old lines. Delete the inherited lines before submitting.
same receipt in two monthly reports
The receipt was filed twice across periods. Keep it in the correct period's report.
Why it happens
Duplicate detection compares new submissions against the employee's history, not just the current report, because the classic double-claim is filing the same receipt in two different reports. Copying a report as a template is the most common accidental trigger: the copy inherits the original's lines, and both reports then contain the same expense. The rejection protects the company from paying twice; the fix is always removing one copy.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_5HmjJtTyii6Lj5KA1opgIg