Bank statement guide
Fix Bank Statement CSV Import Errors
Troubleshoot common bank statement CSV import errors before loading transactions into Excel, Xero, QuickBooks, Sage, or bookkeeping workflows.
Last reviewed: 2026-05-13
Open the converterStart with the header row
Import tools usually expect clear date, description, debit, credit, and balance columns. Remove duplicated page headers and blank rows created by multi-page PDF extraction.
Check dates and amounts
Mixed date formats, currency symbols, commas in numbers, and reversed debit or credit signs are common causes of rejected imports.
- Normalize dates before import.
- Keep debit and credit columns consistent.
- Compare totals with the original PDF.
Re-export from a reviewed source
Use the South African bank statement converter to review extracted rows before export, then keep the original PDF next to the cleaned CSV.
Related bank statement pages
Frequently asked questions
What causes most CSV import errors?+
Date formats, amount signs, duplicated headers, blank rows, and missing descriptions cause many bank statement import errors.
Can Accounter prepare CSVs for accounting tools?+
Accounter exports reviewable CSV rows for spreadsheet and accounting import preparation, not a direct accounting integration claim.
Should I keep the original bank PDF?+
Yes. Keep the original PDF for review, audit support, and resolving ambiguous extracted rows.