If your food total looks twice as big as the month felt, you have probably logged the same spends two ways: once by hand in the canteen queue and once when you imported the bank statement. Sort the month by amount, look for pairs with the same figure on the same or next day, keep the one that carries the statement detail, and delete the hand entry.
This is the most common mess for someone living on pocket money, because students tend to do both things. You tap a quick entry for the ₹85 chai-and-samosa so you do not forget it, and at month end you upload the statement from the account your parents top up. Now the same ₹85 exists twice.
Why students get doubles more than most people
A salaried person usually picks one method. A student mixes: cash from the hostel gate shop, UPI to a friend for the shared auto, a card swipe for books. The cash never appears in a statement, so hand entry is genuinely needed for it. The trouble starts when you also hand-enter things that will later arrive in the statement anyway.
- Hand entry for a UPI spend, then a statement import that contains the same UPI debit.
- Uploading the same month's statement twice because the first upload looked stuck.
- Uploading a statement that overlaps the previous one, for example 1 to 15 and then 10 to 30.
- A friend pays the café bill on their phone and you log your share, then your statement shows a separate debit for what you sent them.
How do I spot duplicates by hand?
Do this once a month, before you read any totals.
- Sort all transactions by amount, highest first, then by date.
- Scan for the same amount on the same day or the day after. Real repeats exist (two ₹30 bus tickets), so look at the merchant text too.
- Where one row says "chai" and the other carries a long UPI reference, that is the pair: the long one came from the bank.
- Keep the bank row, because it matches your statement. Delete the typed one.
- Re-check the category total. It should drop by exactly the amount you removed.
A worked example with pocket money
Say your parents send ₹7,000 a month. You hand-enter eleven canteen spends of ₹60 each. Later you import the statement, and nine of those eleven also appear as UPI debits of ₹60. The other two were paid in cash and never reach the statement.
| Step | Rows | Amount |
|---|---|---|
| Typed canteen entries (11 x ₹60) | 11 | ₹660 |
| Statement debits for the same canteen (9 x ₹60) | 9 | ₹540 |
| What Food now shows for the canteen (660 + 540) | 20 | ₹1,200 |
| Delete the 9 typed rows that match the statement (9 x ₹60) | -9 | -₹540 |
| Correct canteen total (9 statement rows + 2 cash rows) | 11 | ₹660 |
The honest figure is ₹660, which is also what you would quote if a parent asked where the money went. Left alone, the app would have told you ₹1,200, nearly double.
Can the app catch this before it happens?
SpendixAI flags possible duplicate imports and lets you review rows before anything is saved, so an overlapping upload can be caught at that screen instead of after your totals are wrong. It also has a "Possible duplicate charges" report that lists the same amount to the same merchant within two days. Treat that report as a list of suspects, not a verdict: two ₹30 bus tickets in one day are legitimate.
A tidy-up routine for the semester
- Pick one import day each month and note it, so statement dates never overlap.
- After each import, open the review list and look at the flagged rows first.
- Keep receipts for big items such as books or a laptop bag attached to the statement row, not to a second typed entry.
- If a hostel fee or tuition payment goes through a parent's account, record it once and note whose account it left.
- Before showing a month's spending to a parent, run the amount-sort check one last time.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

