Conversion · Convert

Bank Statement CSV to Excel: How to Open, Clean, and Format It

Import the file deliberately, protect each column's data type, and save a real Excel workbook without changing the source transactions.

Import the CSV instead of double-clicking it

To convert a bank statement CSV to Excel safely, open a blank workbook and choose Data > Get Data > From File > From Text/CSV. Select the CSV, confirm the preview has the right columns, then choose Transform Data when Excel's automatic types might alter dates, amounts, or identifiers. After checking the data, choose Close & Load and save the workbook as XLSX.

Double-clicking can be fine for a simple file, but it gives you less control over character encoding, delimiters, and type detection. The import preview is the moment to catch every row landing in one column, accented merchant names becoming garbled, an identifier losing its leading zeros, or a date such as 03/04/2026 being interpreted with the wrong regional convention.

Recommended Power Query type for a four-column bank-statement CSV
FieldSource exampleImport typeReason
Date2026-08-03Date using the source localeEnables chronological sorting
DescriptionCoffee, Market StreetTextPreserves merchant wording and punctuation
Amount-8.75Decimal numberEnables totals and numeric filters
Reference001247TextKeeps leading zeros; it is an identifier, not a quantity

Check encoding, delimiter, and quoted descriptions

Choose UTF-8 as the file origin when the source uses it. Microsoft notes that a UTF-8 CSV with a byte-order mark can open normally in Excel; otherwise, importing from Data > Get Data > From File > From Text/CSV lets you select the encoding explicitly. UTF-8 protects accented merchant names, em dashes, and other characters that older encodings can display incorrectly.

Confirm that comma is the delimiter for a conventional CSV. A description containing a comma must be surrounded by quotation marks in the underlying file so it stays in one cell. Do not split a quoted merchant description into extra columns merely because punctuation appears inside it.

Synthetic CSV sample showing a quoted comma and leading-zero references
Raw CSV lineWhat Excel should produce
2026-08-03,"Coffee, Market Street",-8.75,001247Four cells; the complete description remains one cell
2026-08-05,"ACH deposit — Client payment",2450.00,001248Four cells; the em dash remains readable and the amount is positive

Protect dates and leading zeros before loading

Set account fragments, check numbers, confirmation numbers, and transaction references to Text before loading. Microsoft documents that Excel can remove leading zeros or display long numbers in scientific notation when it treats them as numeric values. Text is the correct data type for an identifier because you do not calculate with it.

For dates, use Change Type > Using Locale in Power Query when the file's convention differs from your computer's regional settings. Choose the data type Date and the locale that matches the source file. ISO dates such as 2026-08-03 are less ambiguous than 08/03/2026, but you should still check the earliest and latest transaction after loading and avoid two-digit years.

  • Keep a copy of the untouched CSV before making transformations.
  • Treat identifiers as Text even when every character is a digit.
  • Confirm dates around the first 12 days of a month, where month/day reversal can look valid.
  • Check statements that cross December and January for the correct year on every row.

Make signed amounts true numbers

Import Amount as a Decimal Number without a currency symbol stored inside the value. Apply Currency or Accounting formatting after the data is loaded. A signed-amount ledger is simple to analyze: money out is negative and money in is positive. That lets =SUM(Transactions[Amount]) calculate the net activity when the table is named Transactions.

If the CSV has separate Debit and Credit columns, do not guess the sign from a merchant name. Preserve both source columns or create Amount with a documented rule that matches the file's definitions. Credit-card statements can use words such as debit and credit differently from checking accounts, so the statement or export documentation—not a generic label—should determine the sign convention.

Common import symptoms and the safest correction
SymptomLikely causeFix before analysis
SUM returns 0 or ignores rowsAmounts were imported as textChange the source column to Decimal Number and inspect conversion errors
001247 becomes 1247Reference was treated as a numberRe-import the original CSV with Reference set to Text
03/04/2026 changes meaningSource and workbook locales differConvert Date using the source locale
A merchant name spans two columnsWrong delimiter or quotation handlingChoose the correct delimiter and preserve quoted fields

Clean the range without deleting evidence

Remove a blank row or repeated header only after confirming it is not a transaction. Trim accidental leading and trailing spaces if needed, but preserve the complete source Description in its own column. If you want a standardized merchant or Category field, add it to the right rather than replacing the original wording.

Do not delete an apparent duplicate just because its date, description, and amount match another row. Repeated transactions can be legitimate. Compare reference values, source order, and the bank statement before removing anything, and record deliberate exclusions on a separate Notes or Review sheet.

Load an Excel table and save as XLSX

Choose Close & Load, select a cell in the loaded range, and confirm it is formatted as a table with headers. Name it Transactions, freeze the header row, widen or wrap the Description column, and apply a date display and monetary format. Excel tables add reliable filters and keep complete rows together when you sort.

Save the finished file as an Excel Workbook (.xlsx). CSV cannot preserve cell formatting, formulas, table filters, column widths, multiple sheets, or explicit Excel data types. If you are starting with a PDF and formatting matters, StatementMint can produce XLSX directly with Date, Description, and signed Amount, avoiding the CSV import step. Review any automated result against the source PDF before relying on it.

Run a five-minute quality check

Compare the spreadsheet row count with the source, then check the first and last transaction, the largest positive and negative amounts, same-day repeated rows, and the statement-period boundaries. Sort only after checking the original order, and clear every filter before counting rows.

A matching net total is useful but does not prove that the ledger is complete: a missing positive and negative amount can cancel each other. Keep the original CSV and issued statement until the workbook has been reviewed, and use the workbook for analysis rather than as a replacement for the issued record.

PRACTICAL CHECKLIST

Before you call it done

  • Import with Data > From Text/CSV
  • Confirm UTF-8 encoding and the correct delimiter
  • Set identifiers and references to Text
  • Convert dates using the source locale
  • Keep signed amounts as decimal numbers
  • Preserve the original description and transaction order
  • Load the range as a named Excel table
  • Save as XLSX and compare the result with the source

Frequently asked questions

How do I convert a bank statement CSV to Excel?+

In a blank workbook, choose Data > Get Data > From File > From Text/CSV. Confirm the encoding and delimiter, choose Transform Data, set dates, amounts, and identifiers to the correct types, then choose Close & Load and save the workbook as XLSX.

Why does Excel remove zeros from my bank reference numbers?+

Excel is treating the reference as a number. Re-import the original CSV and set that column to Text before loading. Adding zeros after they have been removed is unsafe unless the source tells you the exact length.

Why are bank statement amounts stored as text in Excel?+

Currency symbols, unexpected separators, or a source locale that differs from Excel can prevent numeric conversion. Import with Power Query, choose Decimal Number using the correct locale, and inspect errors before applying currency formatting.

Should I keep a bank statement as CSV or XLSX?+

Keep the original CSV as an untouched portable source. Use XLSX for reviewed work because it can preserve table filters, data types, formulas, widths, formatting, and additional notes or analysis sheets.

Sources and further reading

We prioritize regulators, public agencies, and first-party product documentation. Sources support the general guidance above; StatementMint’s workflow recommendations are our own.

  1. Opening CSV UTF-8 files correctly in ExcelMicrosoft Support
  2. Keeping leading zeros and large numbersMicrosoft Support
  3. Set a locale or region for data in Power QueryMicrosoft Support
  4. Create and format tablesMicrosoft Support

Educational information only—not financial, accounting, tax, or legal advice. Institution terms and your facts control.