Troubleshooting
Bank statement summary vs transaction rows
Learn why statement summaries, balances, and totals should not be treated like transaction rows when converting bank statements to CSV.
What counts as a transaction row
A real transaction row usually includes a date, a description, and a money movement amount. Some statements also show running balance, debit, or credit columns, but the row still represents one event on the account.
What belongs to the statement summary instead
Opening balance, ending balance, total deposits, total withdrawals, interest summaries, monthly service fees in a summary block, and page-level captions are not interchangeable with transaction rows. They may help validate the file, but they should not automatically become import lines.
- Opening and ending balances
- Total deposits or total withdrawals
- Statement-period summary boxes
- Check-image captions and footer text
Why this causes bad CSVs
When summaries are treated like transactions, users see duplicate totals, strange 0-row outputs, or import files that do not reconcile. The review step should compare visible account activity against the output and remove summary-only content before the CSV is used downstream.
How to use summaries safely
Summary values are still useful during review. They help users spot missing pages, wrong signs, and row-count mismatches. Original PDFs work best, readable scans can still work, no bank login is required, and redacted files are fine if transaction rows stay visible.
Summary block versus import rows
- Summary-only content
- Beginning balance, ending balance, total deposits, total withdrawals.
- Import-ready rows
- Date, Description, Amount for each real transaction.
- Review rule
- Use summary values to validate totals, not as extra transactions.
Review before import. Balance checks are useful, but summary lines should not be uploaded as bank activity.
FAQ
Should a running balance be imported into QuickBooks?
Usually no for a simple transaction CSV. Balance is useful for review and reconciliation, not as a default import field.
Why does my CSV have extra total lines?
The statement likely contains summary boxes, balance rows, or fee summaries that need to be excluded from the transaction-only output.
Can I still use scanned statements for this workflow?
Yes, if the page is readable. Scans just need more review because summaries and wrapped rows are easier to misread.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.