Bank statements

Bank CSV import failed: causes and fixes you can try yourself

Why a bank CSV import fails and how to fix it: header rows, date and amount formats, encoding, split debit and credit columns, with a worked example in rupees.

Editorial illustration for Bank CSV import failed: causes and fixes you can try yourself

A bank CSV import usually fails because the file does not look like a clean table: extra lines above the column headers, dates in an unexpected format, amounts with commas stored as text, or the file saved in the wrong encoding. Open the file in a spreadsheet, fix the first few rows, and import again.

What should you check first?

  1. Open the CSV in Excel or Google Sheets and look at the first ten lines. Is there a bank name, an account number or a summary above the header row?
  2. Is there one header row, with one column per field: date, description, debit, credit, balance?
  3. Scroll to the bottom. Is there a totals line or a disclaimer after the last transaction?
  4. Are dates in one consistent format all the way down?
  5. Are there blank lines in the middle?

What are the common causes?

  • Preamble lines above the headers, which push the real table down
  • Dates as text, or mixing formats such as 03/04/2026 and 3 Apr 2026
  • Amounts with commas or currency symbols, so 1,25,000.00 is read as text
  • Debit and credit in two columns, with blanks or dashes instead of zeros
  • A comma inside a description that breaks the columns, when the file is not properly quoted
  • Special characters displayed as strange symbols, which points to an encoding problem

How do you fix the file step by step?

  1. Make a copy of the original and work on the copy.
  2. Delete the lines above the header row and below the last transaction.
  3. Make the date column consistent. If dates are text, convert them, for example =DATE(RIGHT(A2,4), MID(A2,4,2), LEFT(A2,2)) for text in the form 03/04/2026 read as day, month, year.
  4. Strip commas from amounts: =VALUE(SUBSTITUTE(C2, ",", "")). Fill down and paste values back.
  5. Replace dashes in debit or credit columns with 0 or empty cells.
  6. Save as CSV with UTF-8 encoding if your spreadsheet offers the choice.

A worked example with made-up rows

BeforeProblemAfter
Statement for Savings A/cExtra line above headersRow deleted
03/04/2026Text date, day first3 April 2026
1,25,000.00Indian commas, text125000
-Dash in credit column0

After the clean-up a salary credit of 1,25,000 imports as a number, and a month with 40 rows totalling ₹96,500 in debits and ₹1,25,000 in credits leaves a net of ₹28,500 (125,000 minus 96,500). Check that kind of total against the closing balance change on your statement, to see that nothing dropped out.

What if the file still fails?

Try downloading the same statement as Excel or PDF if your bank offers them, or a shorter date range, which tells you whether one bad row is the cause. If the bank offers several CSV layouts, pick the one with the fewest summary lines. Do not use any tool or workaround that asks for your net-banking login.

What should you write down once it works?

Note the steps that fixed the file: which rows you deleted, which formula you used, which encoding you saved with. Next month's file will have the same quirks, so the same fixes will work. Keep a cleaned template with the formulas already in place, and paste each new month's data into it. Ten minutes spent on this once saves the annoyance of failed imports every month after.

How does SpendixAI report failures?

SpendixAI accepts statements as PDF, CSV or Excel, shows rows for review before saving, keeps an import history with a status, and sends an Import failed notification. Any layout may not parse perfectly, so check the preview against your statement. Pick the account before importing so the rows land in the right place.

SPENDIXAI JOURNAL

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

Explore your reports