A realistic source document followed by the actual Image to CSV document state or output artifact.
Bank Statement to CSV — Extract Image Transaction Rows — table image to CSV converter with a cell review grid — After
Bank Statement to CSV — Extract Image Transaction Rows — table image to CSV converter with a cell review grid — Before
Image to CSV

Bank Statement to CSV — Extract Image Transaction Rows

Upload a statement image with transaction headings and readable amounts

Read a bank statement image into CSV transaction records. Verify dates, debit and credit fields, references and decimal separators before any import.

  • Budget-app import preparation
  • Transaction comparison in a script

Upload your table image

Upload a statement image with transaction headings and readable amounts

All image formats (JPG, PNG, WEBP, HEIC, TIFF…)

Convert a bank statement image to CSV rows for a budget app

This bank statement to CSV page reads the transaction table from a photo, scan or screenshot of a statement page and turns it into comma-separated rows. You review the grid first, correct what was misread, and then save a .csv file for a budgeting app, a reconciliation sheet or a script. The tool reads the pixels on the page you choose. It does not log in to a bank or pull transactions by itself.

What a statement page looks like to the table reader

A statement page usually has a header block with the bank name, account holder and period, then the transaction table, then a footer with opening and closing balances. Lines outside the table arrive as single-cell rows above or below the transactions, and the first table row becomes the CSV header. A photo that catches a page break can show the column headings twice, and the second set arrives as an ordinary row, so delete it with the trash icon before you export.

Settle debit, credit and balance columns before you export

Banks print amounts in different ways: separate Debit and Credit columns, one signed Amount column, a CR or DR suffix, or negative numbers in parentheses. A CSV file carries no formatting, so decide which convention your destination expects and make the grid match it. The grid edits cells and rows but has no column controls, so merging two amount columns into one is a job for the spreadsheet or importer that opens the file.

Use the running balance to catch misread digits

Most statements print a balance after each transaction, which turns the table into its own checksum. Take the balance on one line, apply the next line's amount, and the result must equal the next printed balance. When it does not, a digit in the amount or the balance was misread, and the amber cells in the grid are the first place to look. Run this check down the whole page before you save, so one misread digit does not carry into every figure you calculate from it.

Load the file into a budget app without duplicates

Dates are the next trap. 04/05 means April 5 on a US statement and May 4 on many others, and the CSV keeps the text exactly as printed. Set the date format and decimal separator in the importer instead of editing every row. Two statements with overlapping periods can contain the same transaction, and the converter has no idea what your app already holds, so compare the first and last dates of each file with what you imported before.

  1. Open the CSV import in your budgeting app and choose the file.
  2. Match Date, Description and Amount to the columns in its preview.
  3. Set the date format and decimal separator to match the statement.
  4. Import a few rows first, then compare the totals with the statement page.

Before you save the statement CSV

A statement image is not yet a safe transaction import

Prepare transaction rows from a statement image for a budgeting or reconciliation import. Bank layouts differ, so verify the amount convention and adapt the reviewed CSV to the destination's date, currency and column requirements.

Budget-app import preparation

Review dates and amounts, then map the CSV to your app's template and check for transactions already imported elsewhere.

Transaction comparison in a script

Prepare a checked extract for your own matching logic, retaining references and making the debit-credit convention explicit.

Check transaction conventions before loading a budget app

  1. Capture complete statement rows and their debit, credit or amount headings.
  2. Check date order, minus signs, decimal separators and wrapped transaction descriptions.
  3. Export CSV, adapt it to the destination template and verify duplicates before importing.

Bank-feed expectations, date formats and duplicate transactions

Is this a direct bank feed or Open Banking connection?
No. Only the statement image you choose is processed. There is no live bank connection or automatic transaction synchronization.
Will the CSV match my budget app's bank-import format?
You may need to rename columns, format dates and convert separate debit-credit columns into signed amounts according to that app's documentation.
How can duplicate statement transactions be avoided?
Check overlapping statement periods and existing imports in your destination. OCR extraction does not know which transactions you have already recorded.
Does a successful CSV export mean the financial data is accurate?
No. Compare extracted transactions and balances with the original statement. File generation confirms an export, not the correctness of the financial record.
How do I turn separate debit and credit columns into one amount column?
Open the CSV in a spreadsheet and add a column that subtracts the debit from the credit, so withdrawals are negative and deposits positive. Then delete the two original columns or keep them for reference. Do this after the converter, because the grid corrects cells and rows but has no column controls.
Why do my statement dates import in the wrong order?
The CSV holds each date as the text printed on the statement, so a spreadsheet or app guesses its order from your regional settings. Choose the date format in the import dialog instead of editing the file, and check a row where the day is above 12 so a day and month swap is easy to see.
Can I put a multi-page statement into one CSV?
Each image is read on its own and gives one CSV. Convert the pages in order, then paste the transaction rows of later pages under the first file's header, deleting repeated headings and carried-forward balance lines. Batch mode, a Premium option, converts all pages at once but skips the review grid, so check those files yourself.
What happens to the account number printed on the page?
Anything printed outside the table becomes a single-cell row, so an account number or holder name can end up in the file. Delete those rows in the grid, or crop the image to the transaction table before you upload it, if the destination should not receive them.
Can I review the grid before I download the CSV?
Yes. The grid is a free preview, so you can read and correct the statement before any file is made. The .csv download is the export step: signed-out visitors are asked to sign in, signed-in accounts use their export allowance first, and then Premium or credits apply.
Why is a minus sign or parenthesis missing from some amounts?
Small marks such as minus signs, parentheses and decimal points are the first details to fade in a photo. Cells the reader doubted are shaded amber, but a clean-looking cell can still be wrong, so compare each sign with the statement and recheck any line whose result breaks the running balance.
Free to use · No signup required · Without watermarkUploads are encrypted in transitRemoved under our retention policy

Watch each transformation land

Every photo crosses the slash untouched and comes out the other side finished.