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
- Capture complete statement rows and their debit, credit or amount headings.
- Check date order, minus signs, decimal separators and wrapped transaction descriptions.
- 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.




























