How to Import a Bank Statement into Excel Without Breaking Dates

Choose the import route by file type

To import a bank statement into Excel without changing its dates, first identify whether you have a PDF, CSV, or XLSX. Convert PDF transactions into rows, import CSV with explicit date settings, or open an XLSX and check its date values. In every case, compare a few dates with the issued statement before sorting or calculating.

This guide focuses on date failures. The related CSV-to-Excel guide covers the broader import and cleanup workflow, while the Excel conversion guide explains how to turn a PDF into transaction rows.

Recognize a wrong date before trying to format it

The text 04/05/2026 can mean April 5 or May 4. Both are valid dates, so an incorrect import can produce no error message. A date such as 19/05/2026 helps establish day-first order, but confirm the pattern against the statement rather than guessing from one row.

Keep the original date text in a separate column or untouched source file. Changing a wrongly interpreted date to an MM/DD/YYYY display does not recover its original meaning. Reimport the original text with the correct interpretation.

Use the source locale when importing CSV

In Excel versions with Power Query text import, select Data > From Text/CSV and choose Transform Data. Inspect Applied Steps for an automatic Changed Type step. If it already interpreted the dates incorrectly, remove or revise that step so you can work from the original text.

Select the date column, choose Change Type > Using Locale, and set the type to Date with a locale matching the source convention. Microsoft explains that locale controls how text is interpreted as dates and numbers. English (United States) commonly fits month/day/year; English (United Kingdom) commonly fits day/month/year.

Check both an ambiguous day below 13 and a day above 12 before loading. Do not discard conversion errors to make the query finish. If the source mixes date conventions, separate the documented formats and convert each group explicitly.

Repair text dates without overwriting neighboring data

If dates remain text in a worksheet, work on a copy. In desktop Excel's Text to Columns workflow, select only the date column, keep each date as one field, and choose Date with the matching MDY, DMY, or YMD order in the final step. Set an empty destination and inspect the preview before finishing.

Microsoft also documents DATEVALUE for converting recognized text dates to date serial values. Its interpretation depends on date settings, so it is unsuitable as a blind fix for ambiguous day/month strings. Preserve the source column until you have checked the converted results.

Formatting cells as Date changes how numeric values display; it does not necessarily convert text into dates. Likewise, a long number displayed under General may already be a date serial. Inspect the value and compare it with the source before applying a conversion twice.

Keep the correct year and the correct date field

A statement covering December and January needs two calendar years. If the rows omit a year, use the statement period and the printed chronology to determine it. Never fill the whole column with the year in the filename or the year you happen to be importing.

Some card statements print transaction and posting dates. Decide which date your workflow requires, preserve both if available in your working records, and do not replace one with the other merely to make a cutoff test pass. The related transaction-date guide explains that distinction.

For review, sort the whole table by date and inspect the earliest and latest records. Check apparent outliers against the PDF: a purchase date can precede the posting period, so an outlier is a reason to investigate rather than automatically delete a row.

Verify amounts and dates together

A successful date import can still leave Amount as text or reverse a debit. Keep signed amounts numeric and compare one purchase and one credit with the source. Decimal and thousands separators must follow the source convention, just as dates do.

Use the checks below on a working copy. A numeric-date check confirms the storage type only; it cannot tell whether May 4 was mistakenly stored as April 5. Source comparison remains necessary.

Use formatted XLSX when the PDF is your starting point

StatementMint exports Date, Description, and signed Amount to CSV and formatted Excel. Its XLSX stores dates as date values displayed in MM/DD/YYYY format and amounts as numbers. That avoids the separate CSV date-parsing step, though extracted dates still need comparison with the PDF.

Convert the pages available under your allowance, download Excel, and check an ambiguous date, the year, and any row at the statement cutoff. Keep the source PDF and your reviewed working copy available for the accounting task. The export does not decide which date your accounting policy requires.

Frequently asked questions