Most failed CSV imports come from the file's shape, not the app: a wrong date format, amounts stored as text, extra rows above the header, or a different delimiter. Open the file in a spreadsheet, compare it with what the importer expects, and fix one thing at a time. Examples below use dollars and made-up rows.
What did the error actually say?
Read the message before editing. "Invalid date", "unexpected column" and "file could not be read" point to different problems. Copy the exact wording, because it tells you whether to fix dates, columns or the file type itself.
Seven fixes in order of likelihood
- Remove junk above the header. Banks often put an account summary in the first rows. Delete everything above the line with Date, Description and Amount.
- Check the date format. 03/04/2026 can mean 3 April or 4 March. If the importer expects month first, convert to year-month-day, which is unambiguous.
- Fix amount text. Values such as $1,250.00 or (45.10) may import as text. Remove the dollar sign and commas, and turn brackets into a minus sign.
- Use one amount column or two, as the importer asks. Some want signed amounts, some want separate debit and credit columns.
- Save as plain CSV, not a spreadsheet file. Choose comma-separated and UTF-8 if offered.
- Strip special characters from descriptions, including stray quotes and line breaks inside a cell.
- Split large files by year if the importer has a row limit.
A before-and-after row
| Before (invented) | After |
|---|---|
| 03/04/2026 | 2026-04-03 |
| "$1,250.00" | 1250.00 |
| (45.10) | -45.10 |
| COFFEE SHOP, #22 | COFFEE SHOP 22 |
Test with only five rows first. If those import, add the rest. If they fail, the problem is in the structure, not the volume.
Why did it import but the totals are wrong?
A silent success can hide errors. Check three numbers: the row count, the sum of credits and the sum of debits against the bank statement. Suppose you imported 112 rows and the statement shows 115, with a missing amount of $320.40 across the three. Look for rows with blank dates or a negative zero, because importers often skip those without warning.
Could it be a duplicate problem?
If you imported overlapping date ranges, you may see double entries. Fix this by importing non-overlapping periods, or deleting the older duplicate batch before re-importing.
When the file is not the problem
Occasionally the app has a bug or a format it does not support. Try a different statement period, a different export option from your bank, or contact the app's support with the first five rows with all personal details removed. SpendixAI is built around India and rupees, so it will not help with a US account; the checklist above still applies to any importer.
How do you stop it happening next month?
Build a repeatable routine. After the first successful import, note which steps fixed the file and write them as a short checklist beside your template. Next month you will apply the same steps in a few minutes. If your bank offers more than one export option, such as one for a date range and one for all recent activity, use the same one every time so the layout stays consistent.
- Download the same export type each month.
- Apply the same clean-up steps in the same order.
- Import a small sample before the full file.
- Compare totals with the statement before closing the file.
Keep a template
- Save a cleaned sample file that imported successfully.
- Match future files to its column order.
- Keep the original download untouched.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

