Bank statements

How to import a Bandhan Bank statement into an expense tracker

Import a Bandhan Bank statement into an expense tracker, from one month to a full April to March year, and check row counts and balances as you go.

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

To import a Bandhan Bank statement into an expense tracker, download your own statement for the period you want from net banking or the app, upload it as PDF, CSV or Excel against the right account, review the rows before saving, and check that the closing balance agrees. If you want a whole financial year, you can do it in one go or month by month.

Should you import a month or a whole year?

The Indian financial year runs from 1 April to 31 March, so a full-year import suits anyone preparing records for a CA. Monthly imports are easier to review. You may well do both: a year to start with, and a month at a time afterwards.

ApproachGood forWatch out for
Whole year in one fileCatching up, annual recordsA long review screen, and a longer PDF may parse less cleanly
Quarter at a timeA middle pathMake sure each file starts the day after the last ends
Month at a timeEveryday trackingTwelve imports a year, so set a reminder

Where do you download it?

Sign in to your own account, find the statement or e-statement section, and pick the dates. The wording and the layout of the menus change from time to time, so look for what the page offers instead of relying on a screenshot. Never give your net-banking details to a third party. If you cannot find the option, the bank's customer care can point you to it.

What are the steps?

  1. Create the account in the tracker, named after the bank and the account type.
  2. Select it before you upload.
  3. Upload the file, or several files in a batch.
  4. Review the rows. Sort by amount and look at the largest ones first, since a misread figure matters most there.
  5. Save and read the import history for each file's status.

How do you check a full-year import?

Add up the whole year and compare with the two balances. Say the account stood at ₹18,000 on 1 April, credits for the year were ₹7,20,000 and debits ₹6,95,500. Then 18,000 plus 7,20,000 is 7,38,000, minus 6,95,500 is ₹42,500. The statement's balance on 31 March should be ₹42,500, and the next year's opening balance on 1 April should be the same figure.

Also count rows. If the statement lists 412 transactions and the tracker holds 410, two rows were skipped. A count is a quick test, because it points straight to a gap.

What should you do with a failed or half-finished import?

Do not start again from scratch. Open the import history, see which file has the problem, and read the status. If one file failed, re-download that period, ideally in CSV or Excel, and try just that file. If the import saved but looks wrong, look at the first and last rows against the statement, then compare totals. Fix the cause before importing the next period, because errors multiply when later files build on a faulty one.

What about layouts we do not know?

We do not know every layout of Bandhan Bank statements, so treat the review step as the real safeguard. Common faults are swapped day and month, a narration split across two rows and header lines imported as transactions. If the PDF is messy, try CSV or Excel for the same dates. SpendixAI also sends an Import failed notification if a file cannot be read.

After the import

  • Note the last date imported and begin the next file the day after.
  • Create rules for the payees that repeat.
  • Check the Possible duplicate charges report if two files overlapped.
  • Keep the original files, named by period.
SPENDIXAI JOURNAL

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

Explore your reports