Templates
Balance check for bank statement CSV
Use a simple balance-check workflow to verify bank statement CSV rows before importing them into QuickBooks, Xero, or a spreadsheet process.
What a balance check is actually for
The point of a balance check is not to recreate a full reconciliation inside the import file. It is to catch obvious extraction problems before the data touches QuickBooks, Xero, or a shared spreadsheet. PDF-origin files can look tidy while still hiding dropped rows, wrong signs, or summary lines that should never become transactions.
- Upstream input: statement PDF, scan, or extracted CSV
- Review output: validated transaction CSV plus notes about anything uncertain
- Downstream job: import prep, reconciliation support, or accountant handoff
What to compare against the statement
Start with the original statement or a readable scan beside the CSV. Compare the visible transaction count, the opening and ending balance context, and any obvious high-value or end-of-month transactions. If the statement uses debit and credit columns, normalize those mentally into signed amounts while reviewing.
- Row count against visible transaction lines
- Opening balance and ending balance context
- Large deposits, transfers, fees, or reversals
- Dates near page breaks or month boundaries
What usually fails a balance check
The most common failures are boring: balance-forward rows treated as transactions, deposits imported as negatives, wrapped descriptions split into multiple rows, check-image captions copied into the CSV, and one or two missing rows at a page break. These mistakes matter because they often survive until reconciliation, where they become harder to trace.
Trust and workflow boundaries
This review workflow works even when account numbers are redacted, as long as the transaction table and balance context remain visible. No bank login is required. Review before import still applies, and DocuRows should not be framed here as native `.qbo`, `.ofx`, or `.qfx` export unless that support actually exists.
Balance-check review list
- Row count
- Does the CSV have the same number of visible transactions as the statement?
- Signs
- Are withdrawals negative and deposits positive?
- Non-transactions
- Were balance lines, summaries, and headers excluded?
- Boundary rows
- Do first/last transactions of the month match the statement?
A balance check is a review gate before import, not a claim that the file can skip human validation.
FAQ
Do I need running balance in the CSV to do a balance check?
Not necessarily. Running balance can help, but a useful first pass can still compare row count, signs, first and last transactions, and any large items against the statement.
Can I do this with redacted statements?
Yes. Redacted files are fine as long as the transaction rows and balance context you need for review remain visible.
Does a balance check replace reconciliation inside QuickBooks?
No. It is a pre-import validation step that helps catch extraction errors before they become reconciliation problems later.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.