Bank statements

Import a year of bank statements without duplicate rows

Plan date windows for your salary account and card, then catch stray repeats in review, to avoid duplicate transactions when importing bank statements.

Editorial illustration for Import a year of bank statements without duplicate rows

Duplicates appear when two files cover the same dates. The cleanest way to avoid duplicate transactions when importing bank statements is to decide the date windows first, download one file per account per window, and only then upload. The import review should catch the odd stray row, not hundreds of them.

Why a year of statements doubles up

A salaried person in a metro usually has a salary account, one or two credit cards, and maybe a second savings account that receives a bonus or a reimbursement. Each of those can be downloaded by month, by quarter, by financial year or as 'last six months'. People tend to download a little at a time over several evenings, and the windows quietly overlap.

Credit cards add a twist. A card statement often runs from the middle of one month to the middle of the next, so a card file labelled 'March' may start on 15 February. If you then also download 'February' by cycle, the two files share two weeks of rows.

Plan the windows before you download anything

  1. Write down every account you want covered: salary account, each card, any wallet.
  2. For each one, pick a start date and an end date for the full year, for example 1 April to 31 March if you think in financial years.
  3. Cut that range into windows that touch but never overlap, such as 1 April to 30 September and 1 October to 31 March.
  4. Download only those windows. Name each file with the account, start date and end date.
  5. Tick the file off your list once it is imported, so you never upload it twice.

A worked example with real arithmetic

Say you download three files for the salary account. File A covers 1 January to 30 June and has 310 rows. File B covers 1 April to 30 September and has 290 rows. File C covers 1 October to 31 December and has 140 rows. April to June appears in both A and B, and say that overlap is 150 rows.

StepRows
Import A, B and C as they are310 + 290 + 140 = 740
Rows that are really the same transaction150
True number of transactions740 - 150 = 590
Cleaner plan: A, then B re-downloaded as 1 July to 30 September (140 rows), then C310 + 140 + 140 = 590

Same final count, but the cleaner plan never creates the 150 extra rows in the first place. Always do this subtraction before you trust a year of data.

Which repeated rows are real?

Not every repeat is a duplicate. Two cab rides of ₹240 to and from the office on one day are two genuine trips. A monthly EMI of ₹14,500 repeats every month because that is what an EMI does. A true duplicate is the same date, the same amount and the same narration or reference appearing twice because the same file, or an overlapping one, went in twice.

When you are unsure, look at the reference number in the narration. Two different payments almost never share one. If your statement does not show a reference, compare the running balance column instead: a real second payment changes the balance again.

What the import review does for you

In SpendixAI you pick the account before importing, so every row keeps the right account, and you review the rows before they are saved. Possible duplicate imports are flagged in that review, and the import history shows the status of each upload. There is also a Possible duplicate charges report that lists the same amount to the same merchant within two days, which is useful for spotting genuine double charges, not just double imports. Treat the flags as prompts to look, since you know which repeats are real.

If duplicates are already saved

  • Sort the month by amount and look for pairs with identical dates.
  • Delete the extra copy, not both.
  • Deleted transactions go to a recycle bin for 30 days, so a wrong delete can be undone.
  • Compare each month's saved row count with the row count on the bank's own statement.

Before you press upload

  • Do the windows touch without overlapping?
  • Is the right account selected for this file?
  • Have you read the review list rather than approving it all?
  • Did you note the file as done?
SPENDIXAI JOURNAL

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

Explore your reports