Importing a Standard Chartered India statement in more than one batch makes the date ranges overlap, and overlapping rows become duplicates. Choose the right account before every upload, keep a note of the last date imported, and let the tool's duplicate check and import history show what was already saved. Always compare the final count with the statement.
Why do overlaps happen?
Statement periods rarely line up with the calendar. You download 1 to 20 October on the 21st, then another on 5 November covering 15 October to 4 November, because it was the default range. Rows from 15 to 20 October are now in both files. If the tracker saves both blindly, those six days of spending are doubled. we do not describe the bank's own screens, so check the date range options on yours.
A worked example with made-up counts
| Import | Date range | Rows |
|---|---|---|
| First upload | 1 to 20 October | 38 |
| Second upload | 15 October to 4 November | 31 |
| Rows in both uploads | 15 to 20 October | 11 |
The second file has 31 rows, of which 11 were already saved, so only 31 − 11 = 20 are new. After the second import you should have 38 + 20 = 58 saved rows, not 69. If you see 69, the overlap was saved twice. SpendixAI flags possible duplicate imports and keeps an import history with status, so you can see which batch added what, but you still look at the flagged rows and decide.
How do you import safely?
- Pick the account first. A salary account and a credit card are different accounts, and each row keeps the account you choose.
- Upload one statement per account in a batch; batch uploads are supported, but mixing accounts in one batch makes review harder.
- Look at the import history for status before you start another one.
- On the review screen, scan for flagged duplicates and untick or delete them.
- After saving, compare the row count and the date span with your notes.
What about a card and a bank account together?
If you import both your bank account and your card, the card bill payment appears twice: as a debit on the bank statement and as a payment on the card statement. Keep the card purchases as the spending and mark the bank's card bill payment as a transfer. Otherwise a ₹25,000 card bill appears as ₹25,000 of spending in both places.
What if a duplicate got through?
- Filter the transactions for that account and date range.
- Sort by amount and look for pairs with the same merchant and date.
- Delete the second copy. Deleted transactions go to a recycle bin for 30 days in SpendixAI, so a wrong deletion can be recovered.
- Genuine repeat charges also exist, such as two identical coffee payments, so check before deleting.
How do you cross-check the final result?
After the second import, pick three dates inside the overlap and find each transaction on the original statement. Each should appear once in the tracker. Then sum the date range in the tracker and compare it with the statement's total for the same dates. If the two figures agree to the rupee, the overlap was handled correctly. If they differ, look first for a flagged duplicate you skipped and then for a row that was removed by mistake.
Before the next upload
- Download a range that starts the day after your last import.
- Confirm the account selected.
- Read the review screen.
- Reconcile the closing balance after saving.
We cannot promise that every statement layout is read perfectly, which is another reason to review. If a file will not import, try CSV or Excel instead of PDF, or ask the bank through its official channel for a fresh copy.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

