Bank statements

How to import a IndusInd Bank statement into an expense tracker

Import an IndusInd Bank statement into an expense tracker with a first-time setup, a table of row checks, and a way to confirm totals match.

Editorial illustration for How to import a IndusInd Bank statement into an expense tracker

To import an IndusInd Bank statement, set up the account and your base currency in the tracker first, then upload the statement you downloaded from your own login and go through the preview line by line. Most problems show up in the preview as swapped dates, flipped debit and credit, or lines that are not transactions at all.

What do I set up before the first upload?

Two decisions are hard to undo, so make them first. Name the account clearly, for example IndusInd savings, because each transaction stays with its account. Then choose the base currency. In SpendixAI it must be chosen before importing and cannot be changed once transactions exist. Expenses can still be in their own currency later; totals use the rate saved with each transaction.

If you have a card statement from any provider, treat it as a separate account rather than mixing it with the bank account. Otherwise a card bill payment will look like spending twice.

How do I download the statement?

After you sign in the usual way, look for the statement, e-statement or transaction history area. Pick the account, set the date range and choose PDF, CSV or Excel. Menus change, so do not rely on a fixed route. If the bank only gives a password-protected PDF, follow the instructions the bank gives for opening it. We cannot promise every IndusInd layout reads perfectly, so assume nothing until the checks pass.

What should I look at in the preview?

Here is a made-up preview to show what trouble looks like. The rows are invented, not copied from any bank.

Preview rowPossible problemWhat to do
04/05/2026, UPI to a friend, ₹1,200 inDirection reversed, since you paid themFlip to an expense
04/05/2026 read as 5 AprilDay and month swappedCheck against a date you remember, then fix the range
Page 2 of 3, no amountPage footer read as a rowDelete it
Closing balance line with a figureBalance mistaken for a transactionDelete it

Is it a problem if one narration looks cryptic?

Not at all. Bank narrations are long and often contain reference codes and short merchant names. Import them as they are. You can rename the merchant or add an alias afterwards so that next month's lines match your rule without you touching them.

Can I import several months at once?

You can, but the first time do it one month at a time. A month is small enough to check by eye, and the balances chain from one to the next. Using the earlier made-up figures, the first month closes at ₹21,500. The next month should open at ₹21,500. If it has credits of ₹38,000 and debits of ₹33,200, it closes at 21,500 + 38,000 − 33,200 = ₹26,300.

If an opening balance does not equal the previous closing balance, a gap between the two files has hidden some transactions. Fix the gap before you add a third month on top of it.

How do I confirm nothing is missing?

Write down the opening balance, the closing balance and the totals the statement gives. Say the opening balance is ₹18,000, credits are ₹40,000 and the closing balance is ₹21,500. Debits must then be 18,000 + 40,000 − 21,500 = ₹36,500. If the preview debits total ₹36,500, you are fine. If they total ₹35,900, there is ₹600 of missing debits, perhaps one or two small payments from a page break.

When should I save?

  • The first and last dates match your range.
  • The account on screen is the right one.
  • Total debits and credits agree with the statement.
  • Anything uncertain is fixed or deleted.

SpendixAI shows rows for review before saving, flags possible duplicate imports, and keeps a history of each import with a status, so a rejected file is easy to find and try again.

SPENDIXAI JOURNAL

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

Explore your reports