Why do my bank CSV dates fail to import?

Accounting software fails on the first unreadable date. Bank CSVs often use a format that doesn't match, or mix formats within the file.

What date format does Xero need for CSV imports?

Xero UK expects DD/MM/YYYY. StatementFlow reformats every row to the required format automatically.

Guides / Bank CSV dates won't import into Xero or QuickBooks

CSV import fix

Bank CSV dates won't import into Xero or QuickBooks

Xero and QuickBooks read a CSV row by row and stop at the first date they can't parse. Bank exports often mix or use an ambiguous date format, so the import fails partway — or silently imports the wrong dates.

Why it happens

Different banks export dates differently — DD/MM/YYYY, YYYY-MM-DD, D MMM YYYY, even mixed within one file. Xero expects UK dates as DD/MM/YYYY; US QuickBooks expects MM/DD/YYYY. When the file doesn't match, 03/04/2026 might import as 4 March instead of 3 April, or fail outright.

The manual fix

Manually you'd reformat the entire date column in Excel to a single, correct format — being careful Excel doesn't 'helpfully' re-interpret dates or turn them into serial numbers, which is its own well-known trap.

The faster way

StatementFlow reformats every date to exactly what your accounting software expects — UK DD/MM/YYYY for Xero, or the QuickBooks format for your org — in one pass, so no row fails and no date flips month and day. Pick the preset, drop the file, done.

Fix it in one click

Drop your CSV, pick your bank and accounting software, download a file that imports first time. Free to start, client-side, nothing uploaded.

Get started free →