Duplicates appear when the same transaction enters your records twice, usually because two statement files overlap by a few days or one file was uploaded again. Prevent them by importing non-overlapping date ranges, keeping a log of what you imported, and running a duplicate check after each import.
Where do duplicates come from?
- A statement from 1 to 31 March and another from 15 March to 15 April, which share two weeks
- The same file uploaded twice, after a slow upload made you doubt it worked
- A bank account and a UPI app history both imported, so the same payment appears in each
- A card bill payment, which shows as a debit in the bank account and a credit on the card
The last one is not a duplicate in the true sense, but a transfer between your own accounts. It still doubles your totals if you count both sides as spending.
How do you prevent overlaps?
- Write down the last date of each import for each account.
- Start the next statement the day after.
- When downloading, pick exact calendar-month dates rather than the last 30 days.
- Name files with the account and date range, for example savings-2026-03.
- Check import history before uploading again.
How do you find duplicates in a spreadsheet?
If date is in column A, description in B and amount in C, put this in D2 and fill down: =COUNTIFS($A$2:$A2, A2, $B$2:$B2, B2, $C$2:$C2, C2). A result of 2 or more means this row repeats an earlier one. Filter D for values above 1. It works in Excel and Google Sheets.
Not every repeat is a mistake. Two identical chai payments on the same day are real. Look at the pair before you delete anything.
A worked example with made-up numbers
| Date | Merchant | Amount | Count |
|---|---|---|---|
| 4 March | Electricity board | ₹2,340 | 1 |
| 4 March | Electricity board | ₹2,340 | 2 |
| 9 March | Tea stall | ₹30 | 1 |
| 9 March | Tea stall | ₹30 | 2 |
The electricity row is almost certainly an overlap, because a bill is rarely paid twice on the same day. The tea stall could be two real cups. If you remove the electricity duplicate, your month drops by ₹2,340, and your monthly total of, say, ₹38,640 becomes ₹36,300.
What if a real double charge happened?
Merchants do charge twice sometimes. If the same amount went to the same merchant within a day or two and you only meant to pay once, contact the merchant with both statement lines. Do not assume it is an import error.
What should you do after each import?
- Compare the number of rows saved with the number in the file.
- Check that the first and last dates match the period you meant to import.
- Run your duplicate check or report and look at each flagged pair.
- Compare the month's closing balance in your records with the bank's.
If the balance does not match, the gap tells you the size of what is missing or doubled, which is the best clue to what happened.
Keep a small import log, even a single line per upload: account, date range, date imported. When something looks wrong three months later, that line answers most of your questions in seconds.
What does SpendixAI do about this?
In SpendixAI you choose the account before importing, uploads are recorded in an import history with a status, and possible duplicate imports are flagged. A Possible duplicate charges report lists the same amount to the same merchant within two days, which helps separate import overlaps from real double charges. Rows are reviewed before saving, so you can look at a flagged pair before deciding.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

