Getting started

Duplicate transactions after a statement import: causes and fixes

Why statement imports create duplicate transactions, how to tell a real double charge from an overlap, and how to clean up and prevent repeats.

Editorial illustration for Duplicate transactions after a statement import: causes and fixes

Duplicates after a statement import almost always come from importing the same period twice, usually through overlapping date ranges or the same statement in two file formats. Real double charges exist too, but they are rarer, and you can tell them apart by checking the dates and the reference on each line.

Why did the same transactions appear twice?

  • You imported a statement for 1 to 31 October and later one for 15 October to 15 November. Everything from 15 to 31 October is now there twice.
  • You downloaded the same month as PDF and as CSV and imported both.
  • A first upload failed halfway, you retried, and the partial rows were already saved.
  • Two accounts overlap: a card statement and a bank statement both show the card bill payment, one as a card credit and one as a bank debit.
  • A statement and a hand-typed entry for the same purchase, such as a cash-style note you added from memory, now both exist.

How do I tell an overlap from a genuine repeat?

An overlap duplicates the whole run of lines: same date, same text, same amount, same order. A genuine repeat is usually a single pair. Two ₹40 chai payments at the same stall on the same day are two real purchases. Look for a reference number or time in the narration. Identical lines with identical references are import duplicates; identical lines with different references are probably real.

PatternLikely causeWhat to do
Dozens of pairs across one date rangeOverlapping importsDelete one copy of the overlapping range
Every line twice, same accountSame file imported twiceDelete the second batch
One pair, different referencesTwo real purchasesKeep both
Card payment appears as spending and as a bank debitAccount overlapMark the bank-side line as a transfer
One pair, one typed and one importedManual entry plus statementKeep the imported line, delete the typed one

What is the cleanest way to remove them?

  1. Do not delete anything yet. Sort the month by amount, then date, so pairs sit together.
  2. Work out the expected total from the statement's opening and closing balances.
  3. Say your sheet shows debits of ₹84,300, but the statement says ₹71,800. The gap is ₹12,500, so the duplicates should add up to exactly that.
  4. Remove one copy of each pair until the gap closes. If you remove pairs worth ₹13,000, you deleted a real transaction; add it back.
  5. Re-run the total against the statement balances.

How does SpendixAI handle this?

SpendixAI keeps an import history with a status for each upload, flags possible duplicate imports, and has a Possible duplicate charges report that lists the same amount to the same merchant within two days. That report is for spotting real double charges as well as import repeats. Deleted transactions sit in a recycle bin for 30 days, so a wrong delete can be reversed. Flags are prompts to look, not verdicts, so you still decide which copy goes.

How do I prevent it next month?

  • Import by calendar month, with no overlap, and note the last date you loaded.
  • Pick one format per statement and delete the other file.
  • Choose the account before uploading, so lines from different accounts are not mixed.
  • Do not re-add by hand anything you know is on its way in a statement.
  • After each import, compare the total with the statement and write the result in a note.

If you believe a merchant genuinely charged you twice, keep both statement lines and the receipt, and raise it with the merchant or your bank. Check your own statement and card terms for how disputes work.

SPENDIXAI JOURNAL

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

Explore your reports