Bank statements

How to import a IDBI Bank statement into an expense tracker

How to import an IDBI Bank statement into an expense tracker: download it yourself, pick the account, review rows, then verify against the closing balance.

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

To import an IDBI Bank statement into an expense tracker, download your own statement from the bank in PDF, CSV or Excel, upload it against the right account, review every row before saving, and then confirm that the totals agree with the closing balance printed on the statement. The whole job takes a few minutes once you have done it a time or two.

Where do you get the statement from?

Sign in to your own net banking or mobile banking and look for the statement or e-statement section. Menu names change from time to time, so I will not quote them; search that area for a way to choose an account and a date range. Some branches will also issue a printed statement or passbook entries, but a file you download yourself is far easier to import.

Pick a format if you are given a choice. A CSV or Excel file keeps every row as its own line, which suits a tracker best. A PDF works too. Choose a start date and an end date that match whole months, such as the 1st to the last day, so that each month can be checked on its own.

How do you import it step by step?

  1. Open the import screen in your tracker and pick the IDBI Bank account (create it first if this is your first import).
  2. Upload the PDF, CSV or Excel file. You can usually add several files in one batch.
  3. Wait for the rows to appear, then review them. Look at dates, amounts and whether debits and credits are in the right direction.
  4. Fix or delete anything that looks wrong, then save.
  5. Open the import history and confirm the file shows a successful status.

In SpendixAI you pick the account before you import, each transaction keeps that account, and you review the rows before they are saved. If an import fails you get an Import failed notification, and the history shows a status for each file. I cannot promise that every IDBI Bank layout will read perfectly, because we have not seen all of them; that is exactly why the review step and the balance check exist.

What should you check before trusting the import?

CheckWhat to doRed flag
Row countCount the lines on the statement and the rows in the trackerA few rows missing at the top or bottom
Date formatLook at a day above 12, such as 25 AprilDates read as month first and swapped
Debit and creditSpot-check a salary credit and a large paymentEverything shown as spending
Closing balanceOpening balance plus credits minus debitsA different figure from the statement

Here is the balance check with made-up numbers. Opening balance ₹24,800. Credits in the month ₹55,000. Debits ₹47,350. Opening plus credits is 24,800 + 55,000 = ₹79,800, and minus debits gives ₹32,450. If the statement says ₹32,450, the import is complete.

What if you import the same month twice?

Overlapping date ranges are the usual cause of doubles. If you downloaded 1 to 15 April and then 10 to 30 April, the days 10 to 15 sit in both files. SpendixAI flags possible duplicate imports, but you should still glance at the history and avoid uploading the same period again. A neat habit is to download one month at a time and name each file with the month.

After the import: set it up for next month

The first import takes the longest because nothing has been categorised yet. Fix the categories on the larger merchants, add a rule for the ones that repeat, and next month most lines will fall into place without attention. Do the closing-balance check every time, even when the import looks perfect.

  • Download a whole month, not a part.
  • Pick the right account before uploading.
  • Review rows, then save.
  • Check the closing balance.
  • Note any merchant that needs a rule.
SPENDIXAI JOURNAL

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

Explore your reports