Bank statements

Students: import your statements without a pile of duplicates

Small UPI payments, wallet top-ups and one account with pocket money: how a student can avoid duplicate transactions when importing bank statements.

Editorial illustration for Students: import your statements without a pile of duplicates

Students rarely have a year of tidy statements, so the usual advice about annual files does not fit. To avoid duplicate transactions when importing bank statements, import in short, clearly dated chunks, keep your wallet and bank separate, and expect many repeated small amounts that are completely genuine.

Your statements look repetitive for a good reason

A student's account is mostly tiny UPI payments: tea at ₹20, auto fare at ₹60, mess extra at ₹45. In one day you can pay the same canteen the same amount twice. Any check that flags 'same amount, same merchant, within two days' will light up constantly. Most of those flags are just your life.

Start from the date the account became useful

If your account opened in August, there is no point downloading January to December. Find the first month with real activity and download from there to today in one go, or in two clean chunks. Say the account opened on 10 August and today is 14 November. One file from 10 August to 14 November is better than three overlapping 'last month' downloads.

Wallet top-ups are the real source of doubles

Suppose you top up a wallet with ₹500 from your bank. Your bank statement shows ₹500 going out. The wallet statement shows ₹500 coming in. If you import both, you will see two rows of ₹500 and may think one is a duplicate. They are the two sides of one move of your own money.

SourceWhat you seeHow to treat it
Bank statement₹500 debit to walletMoney moved, not spent
Wallet statement₹500 creditThe other side of the same move
Wallet statement₹60 debit to a juice stallReal spending

Pick the account before importing, so each row stays with its own account, and decide up front that the top-up is a transfer, not a purchase. That decision is yours; the app will not know your intent.

A simple monthly routine

  1. On the last day of the month, download the statement from the first day of the month to today.
  2. Import it into the right account.
  3. Read the review list. Approve repeats you recognise, delete ones you do not.
  4. Check one total: debits in the app should match the debits on the statement.

SpendixAI flags possible duplicate imports during that review, and the import history shows which uploads succeeded. If an upload fails you get an Import failed notification, so you know to try again rather than assume it worked.

What if the same file went in twice?

  • Look at the import history and find the two uploads of the same file.
  • Delete the rows from the second one.
  • Deleted rows stay in a recycle bin for 30 days, which gives you time to undo a mistake.
  • Next time, rename each file with its date range before you upload.

What if I only have PDFs from a few different months?

That is common. Say you saved September in October, then October and November together in December. Check the first and last date printed on each file before uploading. If the second file starts on 1 October and the first ended on 30 September, they sit cleanly side by side. If the second file begins on 25 September, five days overlap, and you should expect about five days of repeated rows. Write the real start and end of each file on a sticky note or in the file name, then import in date order, oldest first.

  • Oldest file first, newest last.
  • One account per upload.
  • A glance at the last row of one file and the first row of the next.

Before you upload

  • Is this the account you are importing into?
  • Did you start at the first day that mattered?
  • Are any two files overlapping by even one day?
  • Is a wallet top-up marked as a transfer rather than spending?
SPENDIXAI JOURNAL

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

Explore your reports