Convert a Bank Statement to CSV

Create a portable CSV with one record for each posted transaction and stable columns covering descriptions, dates, balances, credits, debits, review notes, categories, and confidence.

Choose CSV for portable row data when formulas, workbook styling, and multiple sheets are unnecessary.

bank-statement-transactions.csv
posted_on,bank_text,outflow,inflow,running_balance,review_status
2026-10-02,"Sample payroll",,2620.00,4112.40,check
2026-10-04,"Sample rent",1450.00,,2662.40,check
Illustrative structure, not uploaded data.
Source entries from a bank statement transformed into fields in a structured CSV file
Receive transactions in a CSV fileThe output centers on portable source entries, mapped fields, reconciliation issues, and the CSV download.

Private automated processing: This temporary CSV review is unavailable to search engines and expires in 30 minutes. Before import, check delimiters, dates, signs, amounts, and empty values. Review current limits and pricing.

When CSV is the right output

CSV suits database loading, scripts, bookkeeping staging, and tools that need rows rather than workbook formatting. It carries plain tabular values without formulas, multiple sheets, styling, or a built-in summary page.

The format does not dictate how receiving software handles dates, decimals, delimiters, encoding, or blanks. Verify mapping settings; an upload success message does not prove that fields landed correctly.

Field contract before import

One record
A single posted transaction from the statement, excluding page totals and duplicate headers.
Blank value
Leave it empty when the statement omits the value; do not substitute zero.
Original text
Preserve the quoted source wording before normalizing merchants or assigning categories.
Confidence
The extraction's review indicator for that field or transaction row.

Preserving transaction meaning

Quote and encode source descriptions consistently so punctuation and non-English characters neither split records nor become corrupted. Keep debit separate from credit and retain blank balances when the statement prints none.

Specify the date format and identify source currency wherever multiple currencies could be mistaken. An ambiguous day and month cannot acquire a year without period evidence.

Validate the receiving system

Load a small sample before the full dataset and compare its opening, middle, and final records with both CSV and statement. Verify row count, field mapping, directions, decimals, leading zeros, long references, and embedded line breaks.

After complete loading, recalculate controls within the destination. Retain the source CSV and a mapping record so the import can be reproduced without hidden settings.

Import acceptance test

  • Confirm encoding, delimiter, and date format
  • Validate a small import sample before loading everything
  • Compare source and destination control totals
  • Preserve the CSV and field-mapping record

Example CSV import check

Imagine a quoted CSV description reading "MARKET, CENTRAL". Software that ignores quotes divides it into two fields and shifts every following value; testing five rows exposes this mapping failure before full loading.

Once delimiter and quoting rules are corrected, compare row count, debit and credit controls, and the opening and closing records across systems. File size and upload status are not reconciliation evidence.

Guidance for CSV mapping and reconciliation

Match Bank Statements to Bookkeeping

Bank records and books view one account through separate systems. A defensible match uses the same cutoff, linked evidence, and a schedule for genuine timing differences.

Bank Statement Reconciliation Guide

The purpose of reconciliation is to account for every difference at one cutoff. Removing difficult entries merely creates agreement without evidence.

Review extraction before importing rows

Learn how the transaction entries and their uncertainty are retained before the receiving system applies its field rules.

Review the methodology