Bank Statement Convertor

Fixing bank statement date format problems

Updated 2026-08-19

Date errors are the most dangerous kind of statement error because nothing looks broken. Every row is present, every amount is right, and the monthly totals are quietly wrong.

Day-first versus month-first

A UK or Australian statement dated 03/04 means the third of April. Opened in a US-configured spreadsheet, it becomes the fourth of March. Nothing warns you. Every date from the first to the twelfth of a month is ambiguous, so roughly forty percent of a typical statement can shift.

Statements that omit the year

Many Canadian and Australian statements print only the day and month inside the table, with the year appearing once in the header. Take the year from the statement period, and be careful with periods that cross a year boundary: a December statement running into January needs two different years in one file.

Getting it into Excel safely

Do not double-click a CSV and hope. Use Data then From Text/CSV, set the column type to Date and declare the source format explicitly. That single step prevents the silent swap.

How to tell it went wrong

Sort by date. If transactions from the same statement appear scattered across several months, or if a date exists that falls outside the statement period, the format was misread on import.

Convert a statement now

Drop a PDF bank statement in and get a clean CSV or Excel file back. Free, no signup, nothing stored.

Open the converter

Frequently asked questions

+Which format is safest?

ISO style, year then month then day. It sorts correctly as text and is unambiguous in every locale.

+Can I fix dates after a bad import?

Only reliably if you still have the source. Once ambiguous dates have been converted to real date values, the original intent is lost. Reimport rather than patch.

More guides