Xero bank CSV date format not recognised: what I check

Xero rejects a bank CSV and the message is usually some version of "we could not recognise the date format". The file looks fine in Excel. That is often the problem.

I see this most with UK exports. The bank writes dates one way. Excel helpfully "fixes" them. Xero expects another. Then you spend half an hour staring at cells that look identical.

Why UK dates break imports

Day and month swap depending on locale. A date like 03/04/2026 can mean March or April. If Excel has already converted the column to a serial date, what you export is not what the bank gave you.

Do not trust Excel as the middle step

Open the CSV in a plain text editor first. Check the raw date strings. If you need a spreadsheet, import as text so it does not auto-convert. Save out carefully. Better still, convert with a tool that does not reinterpret dates.

Run a five-row test

Before you clean the whole statement, take five rows: a payment, a deposit, and a couple of odd ones. Import that sample into Xero. Confirm the dates and signs land correctly. Then do the full file.

What "valid statement data" usually means

• Consistent date order across every row
• Amounts without currency symbols stuck to them
• Clear money in versus money out, or a signed amount column
• No duplicate header rows halfway down the file

A quicker path when you are stuck

I built CSVReady for this exact faff. You upload a bank or payment CSV, check the mappings, and get a file shaped for Xero, QuickBooks Online, or FreeAgent. You can try five rows free with no account and no bank login.

Try CSVReady: five rows free →

If your export is especially awkward, send a note through the CSVReady contact form and leave the real statement data out of the message.