Hundreds of duplicates after importing twelve months of statements are avoidable, and the question is how. Duplicates usually come from overlapping date ranges or the same file loaded twice. Import one account at a time, keep each file's date range clearly separate, log what you loaded, and check the balance after each file.
Where the duplicates come from
- Statements downloaded as rolling windows, such as the last 33 days, which overlap the previous one by a few days.
- The same file uploaded twice after an error message that was not really an error.
- A monthly statement and a yearly statement for the same account both loaded.
- Two accounts imported into one account by mistake, so a transfer shows up on both sides.
Say each overlap contains 14 rows. With 12 files there are 11 boundaries, so 11 x 14 = 154 duplicates. That is the "hundreds" people complain about.
A safer import routine
- Decide the exact period, for example 1 April to 31 March, and download statements that start and end on the month boundaries.
- Keep a small log: file name, account, first date, last date, row count and status.
- Import oldest first, one account at a time, and pick the right account before every upload.
- After each file, compare the closing balance with the statement.
- If a file shows a date range that overlaps the previous one, trim the overlap before importing.
- Only start the next file when the current one is saved or discarded.
A log can be as simple as this, kept in a notes file:
| File | Account | First date | Last date | Rows | Status |
|---|---|---|---|---|---|
| April statement | Salary account | 1 Apr | 30 Apr | 131 | Saved |
| May statement | Salary account | 1 May | 31 May | 148 | Saved |
| June statement | Salary account | 1 Jun | 30 Jun | 127 | Next |
What if you are working in a sheet?
Put all rows on one tab and add a helper column that numbers repeated rows. If the date is in A, the amount in B and the description in C, in D2 use:
=COUNTIFS($A$2:A2,A2,$B$2:B2,B2,$C$2:C2,C2)
The first time a combination appears the result is 1. Filter for 2 or more to review the repeats. Do not delete them blindly: two ₹150 chai payments to the same stall on the same day are real. A repeat is only suspicious when the whole block repeats, which you can tell by looking at which file each row came from.
What can software do about duplicates?
SpendixAI keeps an import history with a status for each file, flags possible duplicate imports, and has a Possible duplicate charges report that lists the same amount to the same merchant within two days. That second report finds genuine double charges rather than overlapping files, so it is a different safety net. You still review the rows before saving.
Can you clean up after the fact?
Yes, but it takes patience. Sort by date and amount, identify the overlap windows, and delete one copy of each repeated row, keeping a note of what you removed. Look for a recycle bin: SpendixAI keeps deleted transactions for 30 days, which leaves room to undo a mistake. Then check the monthly totals against the statements.
An honest limit
No tool can tell for sure whether two identical rows are a duplicate or a real repeat purchase. The statement balance is the referee: if the totals match without the second copy, it was a duplicate; if they only match with it, keep it.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

