Duplicates appear because the same transaction entered the app twice: you uploaded overlapping statements, imported the same file again, or entered by hand something that a statement later brought in. To remove them, sort by date and amount, confirm each pair against your bank statement, and delete only the extra copy.
Why do duplicates happen in the first place?
- Two statements that cover overlapping days, such as one ending 31 March and the next starting 28 March.
- The same file uploaded twice after an error message.
- A cash or UPI entry typed in by hand and then imported from the statement.
- A bank that lists a pending and a settled version of one card payment.
- A transfer between your own accounts recorded once on each side.
The last one is not a true duplicate at all, and deleting it would break your balances. Treat it as a different problem.
How can I tell a duplicate from two real payments?
The same amount to the same merchant on the same day does not prove a duplicate. Two chai-stall payments of ₹20 or two ₹399 renewals for different family members are real. Open your bank statement for the date and count the lines. If the statement shows one line and your app shows two, the second is a duplicate. If the statement shows two, keep both.
What is a safe step-by-step cleanup?
- Filter your transactions to the month with the issue.
- Sort by merchant, then date, then amount, so repeats sit next to each other.
- Compare each suspect pair with the statement, line by line.
- Delete only the extra copy and keep the one with the receipt or notes attached.
- Recheck the month total against the statement total.
- If the app has a recycle bin, confirm the deleted rows landed there in case you were wrong.
A worked example with made-up numbers
Say the app shows March spending of ₹41,880 but your bank statement says ₹39,880. The gap is ₹2,000. Sort by amount and you find two rows of ₹1,200 and two of ₹800 to the same merchants on the same dates, and the statement shows one of each. Removing the extra ₹1,200 and ₹800 takes off exactly ₹2,000, and the totals agree at ₹39,880. A gap that does not equal any combination of rows suggests a different cause, such as a missing credit or a wrong sign.
What does SpendixAI do about duplicates?
SpendixAI flags possible duplicate imports and includes a Possible duplicate charges report, which lists the same amount to the same merchant within two days. Treat both as prompts to check, not verdicts, since a flagged pair can still be two real payments. Deleted transactions go to a recycle bin for 30 days, so a wrong deletion can be recovered.
How do I stop it happening again?
Import statements in date order, one account at a time. Write down the last date you imported for each account, and start the next file from the day after, or accept the overlap and untick rows you already have. If you add cash by hand, do not also import the same payment from a UPI statement; choose one route per type of spend.
What about duplicates inside a single statement?
Sometimes the bank itself lists a payment twice, once as authorised and once as settled, or a failed payment and its reversal appear as two lines. These are not import errors. The reversal normally has the opposite sign, so the pair nets to zero. Keep both, or remove both, but never one of them. If you are unsure, check the reference number on the statement line: genuine repeat payments usually carry different references.
Quick checklist
- Month total matches the statement.
- Each deleted row was checked against a statement line.
- Own-account transfers left alone.
- Last imported date noted for every account.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

