QuickBooks: expense already exists - duplicate skipped on import
Handles QuickBooks' duplicate-skipped import message by verifying whether the skipped expense is a true duplicate or a missing entry. Use when a QuickBooks import reports expenses skipped as duplicates. Not for import format errors or bank-feed disconnects.
TL;DR
QuickBooks skipped the row because it matched an existing expense on date, amount, and payee, which usually means the expense is already booked and nothing is wrong. Open the existing transaction to confirm it matches, then either accept the skip or, if the import row is actually a distinct charge, tweak the memo so it no longer matches and re-import. The message is informational, not an error, when the match is real.
Error
QuickBooks: expense already exists - duplicate skipped on importSteps
- Note which rows the import report marked as skipped duplicates. Expected: the report lists the skipped rows with dates and amounts.
- Search QuickBooks for a transaction with the same date, amount, and payee. Expected: you find the existing transaction that triggered the match.
- Compare the existing transaction against the source receipt. Expected: identical merchant, date, and amount confirms a true duplicate.
- If it is a true duplicate, accept the skip and reconcile the import. Expected: the import completes with no missing expenses.
- If it is a distinct charge that happened to match, edit the memo or reference number to make it unique and re-import that row. Expected: the row imports as a new transaction.
When to use
- A QuickBooks import log shows "duplicate skipped" rows.
- Re-importing a file after a partial import flags most rows as duplicates.
- Bank feed and manual imports overlap on the same expenses.
When not to use
- The import fails with a format or column-mapping error.
- The bank feed itself is disconnected.
- The skipped row never appears in QuickBooks at all (a matching bug, not a duplicate).
Tool compatibility
QuickBooks Online (current 2026 releases). Applies to CSV/Excel imports and third-party expense syncs.
Variant phrasings
quickbooks "possible duplicate" on manual entry
The same matcher fires when you key in an expense by hand. Verify against the suggested match before saving.
re-import flagged everything as duplicate in quickbooks
A second import of the same file matches every row from the first import. This is expected; review the first import instead of re-importing.
bank feed duplicate after csv import in quickbooks
The bank feed later downloads the same charges you imported by CSV. Exclude the feed copies from the feed to avoid double-booking.
Why it happens
QuickBooks deduplicates imports on date, amount, and payee to prevent double-booking the same expense. Re-importing a file, or importing a file whose charges also arrive via the bank feed, triggers the matcher. The message is protective: it is telling you the row already exists. It only becomes a problem when the matcher is wrong and a genuinely distinct charge gets skipped, which is why the fix is verification first, re-import second.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_asxcPbfhIpwOnIGSqdqa-Q