Platform

Standardize bank statement CSV exports for accounting import

Standardize bank statement CSVs: detect debit/credit, normalize dates, strip metadata rows.

🛡️ Your rows never leave your browser.
Why Onfyt: Auto-detects six common bank statement layouts (separate debit/credit, signed amount, amount+Dr/Cr) without manual schema configuration.

Interactive Sample Data

DateDescriptionDebitCreditBalance
15/01/2024MPESA TRANSFER FROM GRACE K4500.0025500.00
16/01/2024ATM WITHDRAWAL - CBD BRANCH2000.0023500.00

How this tool works

Bank statement CSV formats vary by institution and change between statement periods. Some banks use a single 'Amount' column with positive/negative values; others use separate Debit and Credit columns; others use a single Amount column with a separate Dr/Cr indicator. Date formats span DD/MM/YYYY, MM-DD-YYYY, '15 Jan 2024', and many others. This cleaner strips bank metadata rows, detects the debit/credit encoding pattern, normalises all dates to ISO 8601, and outputs a standardised 4-column format (date, description, amount, balance) that imports directly into QuickBooks, Xero, Wave, and FreshBooks. Bank statement exports often feature irregular debit and credit columns, signed numbers, missing balance fields, and cryptic payee descriptions containing store numbers and terminal codes. DataFix normalizes bank statements into standard accounting schemas: unifying debit and credit amounts into signed transaction values, cleaning payee names, and formatting dates to ISO-8601 for automated reconciliation in QuickBooks, Xero, or personal finance trackers. Financial statements often present split debit and credit columns, signed amounts, and messy transaction descriptions. Standardizing columns into signed transaction amounts and cleaning payee strings accelerates accounting audits. Bank statements often present separate credit and debit columns alongside cryptic payee text strings. Unifying transactions into single signed amounts and cleaning payee descriptions accelerates monthly bank reconciliation in accounting tools.

Things that usually go wrong

  • Every bank uses a different CSV format — the tool auto-detects the most common formats but may not recognise every bank.
  • Debit/credit amounts split across two columns are merged into a single signed 'amount' column.

Edge cases we tested

🧪 Bank using single Amount column with negative for debits

Detected automatically; no sign flipping applied.

🧪 Running balance column using comma separators ('25,500.00')

Commas stripped before balance stored as numeric.

🧪 Statement spanning multiple months with interim balance rows

Monthly balance rows detected by pattern ('Closing Balance:') and excluded.

Frequently Asked Questions

Which banks are supported?

Barclays, HSBC, NatWest, Chase, Bank of America, Standard Chartered, KCB, Equity Bank, and many more. The tool uses heuristics to handle unknown formats.

Are transaction categories added?

Not automatically — categories are bank-specific. Use Filter CSV Rows to manually segment by description.

Related tools

Platform

Shopify Customer Export Cleaner

Normalize Shopify customer exports: merge split address fields, clean phones, and strip internal metadata.

Open Tool →
Platform

Stripe CSV to JSON

Convert Stripe balance and payment CSV exports to clean JSON with amount conversion and metadata parsing.

Open Tool →
Platform

Google Contacts CSV Fixer

Fix Google Contacts CSV exports to import into Outlook, Apple Contacts, or CRM platforms.

Open Tool →