Bank statement import problem

Check bank statement imports before reconciliation

Use transaction counts, totals, balances, and import previews to catch bank statement conversion errors before reconciling.

For Bookkeepers, accountants, and business owners reconciling bank imports · Last updated June 2, 2026

Why this happens

A converted file can import successfully but still be wrong. Missing rows, flipped signs, duplicate ranges, or wrong dates show up later during reconciliation.

Common signs

Opening and closing balances do not tie out
Imported totals differ from the statement
Duplicate rows appear after import
Reconciliation takes longer than manual entry

How bank-statements.co helps

Run statement-level checks before export: transaction count, debit total, credit total, and balance movement where available.

Transaction count checks
Opening and closing balance checks
Total debit/credit checks
Duplicate date-range warnings

Recommended workflow

  1. 1. Upload the original statement PDF.

    Use the source bank statement rather than a manually edited spreadsheet whenever possible.

  2. 2. Review extracted rows before import.

    Check dates, descriptions, debits, credits, and balances. Pay special attention to ambiguous dates and signed amounts.

  3. 3. Choose the destination export.

    Use QBO for QuickBooks where possible, Xero CSV for Xero, QIF for Quicken, or generic CSV/Excel for review and cleanup.

  4. 4. Import and reconcile.

    Import the converted file into your accounting system, then reconcile against the original statement.

Product roadmap fit

This problem maps directly to the product roadmap for destination presets, export-time date controls, preview warnings, reconciliation checks, bookkeeper batch workflows, and stronger security messaging.

Read about security | Bookkeeper workflow

Related pages

Fix this with a clean bank statement export

Upload a statement PDF and download an accounting-ready file in the format your workflow needs.