Why your bank statement CSV won't import

You have a CSV, you upload it, and the accounting software says the file is invalid or imports nothing. The cause is almost always one of a handful of formatting problems.

Start with the error, then the file

Read the message the software gives you, then open the CSV in a plain text editor, not only in a spreadsheet. A spreadsheet hides things such as stray quotes, odd delimiters and extra lines. The text view shows you exactly what the importer sees.

Common causes and fixes

Header and footer junk

Importers expect a header row followed by transactions. Title lines, account numbers, "Opening balance" rows or totals at the bottom can cause a rejection or a bogus row. Delete everything except the column headers and the transactions.

Date format

Most importers accept a specific set of formats and let you choose between day-first and month-first. A date such as 03/04/2026 is ambiguous. Unambiguous formats like 2026-04-03 avoid the problem, and you should check what your software accepts. Dates stored as text with leading spaces also fail.

Amount columns

Some tools want one signed Amount column; others want separate debit and credit columns. Supplying both a signed amount and debit/credit columns, or putting amounts in the wrong one, causes failures or doubled values. Remove currency symbols, thousands separators and parentheses. Use a minus sign for negatives and a full stop as the decimal mark unless your region says otherwise.

Commas inside descriptions

A description like ACME, INC must be wrapped in quotes or it splits into an extra column and shifts everything to its right. If a few rows look misaligned in the text editor, this is the likely reason.

Encoding and delimiters

Save as plain CSV (UTF-8). Some regional spreadsheet settings export semicolon-separated files, which an importer expecting commas reads as a single column.

Duplicates and overlap

If an import "works" but transactions are missing, the software may have skipped rows it considered duplicates of ones already in the account, or rows outside the date range you picked.

Check the numbers before you import

A file can import cleanly and still be wrong. Before uploading, confirm that opening balance plus the sum of transactions equals the closing balance on the statement. It is much easier to fix before the rows are in your books.

Where PennyTie fits

If your CSV started as a PDF statement, PennyTie can produce it in the first place: it converts a text-based statement PDF to CSV in your browser, runs the balance check, and flags rows that look off. That removes the header junk and sign problems at the source, though you may still need to rename columns to match your software.

Limits

PennyTie reads text PDFs only (no OCR) and does not write software-specific import formats; it gives you a CSV. Always review flagged rows and check the importer's current requirements in your software's help pages.

Try it: open PennyTie, drop a text-based statement PDF (or use the built-in fictional sample) and see whether the totals tie out. Free for statements up to 5 pages; nothing is uploaded.