QBO Duplicate Finder & Cleanup Checker

The usual causes are importing the same statement or bank feed range twice, manual entries that overlap the bank feed, and re-imported QBO files whose transaction IDs changed. Files converted with Convert Statement carry content-derived IDs, so re-importing the same statement is recognized safely instead of duplicated.

No — and that's deliberate. Near-duplicates can be genuine repeats (two identical coffee purchases in a week), so every flagged group needs your judgment. Pro users can download a cleaned QBO with the exact duplicates removed and every transaction ID regenerated; review it, then import it into QuickBooks.

It starts at 100 and subtracts 10 per error (structural problems, balance breaks), 5 per duplicate instance, and 2 per warning. A score of 90+ is a clean file; anything under 70 deserves a cleanup pass before month-end.

Often, yes. The most common causes of a stuck reconciliation difference are duplicate transactions and old uncleared items — both are flagged here, including uncleared entries older than 90 days (from CSV exports with a cleared/status column). If the file carries running balances, the tool also verifies the balance chain.

The most common cause is overlap: you import a bank statement file for dates the live bank feed already pulled in, so every transaction lands twice. Connector apps re-syncing old data and staff entering expenses manually are close seconds. This checker flags the doubled rows by transaction ID, date, and amount — exclude one set in QuickBooks (never both), and next time import only the dates your feed doesn't cover.

No. Your file is processed in memory to build the report and is not stored afterwards. We never sell or share your financial data.