Getting started

Duplicate Transactions in Your Expense App: Find and Remove Them

A forum-style answer on finding and removing duplicate transactions in an expense app when the same payment was typed by hand and also imported.

Editorial illustration for Duplicate Transactions in Your Expense App: Find and Remove Them

The question: "I entered a payment by hand and then imported my statement, and now the same expense appears twice, so my totals are too high. How do I find and remove duplicates?" Short answer: look for the same amount, the same merchant and a date within a day or two, keep the imported one, and delete the hand-typed copy.

How do duplicates sneak in?

Three common ways. You logged a payment on the day and later imported the statement that contains it. You uploaded the same statement twice, or two statements with overlapping dates. Or a card payment shows both as a purchase and, separately, through the wallet or UPI that funded it. In each case the app is doing what you asked; the record is the issue.

How do I find them? Steps

  1. Sort the month's transactions by amount, then by date.
  2. Scan for neighbouring rows with the same amount and merchant.
  3. Open each pair. Check the account, the date and any note.
  4. Decide which row is the source of truth. For anything on a statement, that is the imported row.
  5. Delete the other. Do not delete both.
  6. Recheck the month total against the statement total.

What does the cost of a duplicate look like?

Hypothetical: a restaurant bill of ₹1,250 entered by hand on the 12th and imported from the statement on the 13th. Your month shows ₹48,200 of spending, but the statement total is ₹46,950.

LineAmount (₹)
Month total shown in the app48,200
Duplicate restaurant entry1,250
Corrected total46,950

48,200 minus 1,250 is ₹46,950, which now matches the statement. One duplicate overstated the month by about 2.7 percent, and ten like it would make the month look ₹12,500 heavier.

What does SpendixAI do about duplicates?

During import review SpendixAI flags possible duplicate imports before anything is committed, so you can skip the row instead of cleaning up afterwards. There is also a "Possible duplicate charges" report, which lists the same amount to the same merchant within two days. If you delete something by mistake, deleted transactions go to a recycle bin for 30 days.

Which flagged rows are not duplicates?

  • Two identical chai payments of ₹40 on the same morning.
  • A monthly subscription and a one-off add-on for the same amount.
  • Two family members paying the same shop on the same day.
  • A purchase followed by a genuine second order.

What is the honest limit?

No tool can know for certain that two similar rows are one payment. The flag is a prompt, and your judgement settles it. Keeping a single source for each account, either imports or hand entries, avoids most of the work.

What if the duplicates are in an old import?

Open the import history first. If you uploaded the same file twice, undoing or removing that import may be cleaner than deleting rows one by one. Check what the import history shows for the file name and date range before acting.

For older months, compare each month total with the statement total. Only months that disagree need a row-level search, which saves a lot of time. Fix the largest differences first and leave tiny ones if they are only a few rupees. Write down which months you have verified, so you do not repeat the work next quarter, and note the total you matched each one to.

How to stop them returning

  • Pick one source per account: import or manual.
  • Check the date range before uploading a statement.
  • Review the flagged rows at every import.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports