Bank statement import problem

Fix debit, credit, and signed amount errors before import

Avoid flipped debit and credit columns when converting bank statement PDFs to CSV, QBO, OFX, QIF, or Excel.

For Bookkeepers reconciling imported bank statement transactions · Last updated June 2, 2026

Why this happens

Bank statements vary: some use debit/credit columns, some use withdrawals/deposits, and others use one signed amount column. Mapping mistakes break reconciliation.

Common signs

Deposits appear as expenses
Withdrawals appear as income
Credit card payments have the wrong sign
Totals do not match the original statement

How bank-statements.co helps

Preview transaction direction before export and use destination presets that reshape amounts correctly for each accounting system.

Debit/credit validation
Signed amount conversion
Total debit and credit checks
Accounting software presets

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.