Getting started

Why does my statement import show duplicate transactions?

Statement import showing duplicate transactions usually means one file went in twice or two overlap. Learn to tell that from a real repeat purchase.

Editorial illustration for Why does my statement import show duplicate transactions?

A statement import that shows duplicate transactions almost always has one of three causes: the same file was uploaded twice, two files cover overlapping dates, or you genuinely paid the same merchant the same amount more than once. The first two are mistakes you can undo. The third is real spending and should stay.

The three usual causes

  • The same file uploaded twice, often because the first attempt seemed slow or you were not sure it had worked.
  • Two statements whose dates overlap, such as a download for 1 to 31 January and another for 15 January to 10 February.
  • A real repeat: two chai payments of the same amount to the same stall, or a recharge you did twice because the first one looked stuck.

Each cause leaves a different fingerprint, and you can read it from the rows themselves before deciding what to delete.

A worked scenario with overlapping dates

Say you downloaded a savings account statement for 1 to 31 January and it has 46 rows. Later you downloaded another for 15 January to 10 February. Of the rows in the January file, 21 fall on or after 15 January. The second file therefore holds those same 21 rows plus 18 new ones from 1 to 10 February, so 39 rows in all.

Upload both and you will see 46 + 39 = 85 rows. The true number of different transactions is 46 + 18 = 64, which means 21 rows are copies. The giveaway is that the copies all sit in one block: every date from 15 to 31 January appears twice, with identical amounts and identical narration.

What you seeLikely causeWhat to do
Whole month appears twice, same orderSame file uploaded twiceRemove the second set
Only a block of days appears twiceOverlapping date rangesRemove the copies from the later file
One or two pairs, different days or different reference numbersReal repeat purchasesKeep both
Pair on the same day, same narration, same referenceBank posted a charge and a reversal, or a retryCheck the statement before deleting

How do I tell a flagged duplicate from a real repeat?

SpendixAI flags possible duplicate imports, and it also has a Possible duplicate charges report that lists the same amount to the same merchant within two days. Treat both as prompts to look, not as verdicts. The software cannot know whether you really bought two coffees.

Open your own statement and compare the two entries. A genuine repeat usually has its own reference number or a different time, because the bank recorded two separate payments. A copy created by an overlap is identical in every column, including the reference, and it came from a different file.

Should I delete the copies or the originals?

Keep whichever rows you have already categorised or attached receipts to, and remove the others. Deleted transactions go to a recycle bin for 30 days, so a wrong delete can be brought back within that window.

What if the duplicates are everywhere?

If almost every row appears twice, the same file probably went through twice. Look at the import history, which lists each upload, and you should see two entries with the same file name and similar sizes. Clear the second import's rows rather than going through them one by one.

How to stop it happening again

  1. Download statements for clean, non-overlapping periods, such as one full calendar month each.
  2. Note in a small list which months you have already imported.
  3. Check the import history before uploading, so you do not repeat a file.
  4. Review the rows before saving, looking at the first and last dates of each file.

If a duplicate has already slipped into your totals, remember that every month it touches is overstated by that amount, so fix it before you look at budgets or reports.

SPENDIXAI JOURNAL

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

Explore your reports