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.
