Templates

Bank statement CSV column mapping

Map bank statement fields into Date, Description, Amount or Credit and Debit columns before QuickBooks cleanup and import.

Audience: Bookkeepers and cleanup operators who already have rows but need the columns shaped correctly before import.
Updated: 2026-07-11
Reading time: 5 min read

The two useful target shapes

The simplest target is Date, Description, and signed Amount. Some downstream tools prefer Date, Description, Credit, and Debit. Pick one target and normalize the rows consistently before import.

How source statement fields usually map

Statement rows often start with a date, a narrative description, an amount or debit/credit pair, and sometimes a running balance. The balance is useful for review, but it should not automatically become an import column unless the downstream tool explicitly expects it.

Date -> transaction date
Description -> merchant, memo, or counterparty text
Debit/Credit -> one signed Amount or separate Credit and Debit fields
Balance -> optional review column only

Common mapping mistakes

The most expensive mistakes are flipped signs, balance rows treated as transactions, multi-line descriptions split into extra rows, and summary sections mixed into the dataset. These problems are why review before import belongs on every statement workflow page.

Trust and file-quality guidance

Original PDFs work best, but readable scans and photos can still be tested. No bank login is required, and redacted files are fine if the transaction rows remain visible.

Mapping example

Source columns: Posted Date | Details | Debit | Credit | Balance
Target CSV: Date,Description,Amount
2026-04-02,ACH PAYMENT ACME SUPPLY,-128.44
2026-04-03,CLIENT DEPOSIT,2400.00
2026-04-04,MONTHLY SERVICE FEE,-12.00

Review before import. Running balance can help validate totals, but it is usually not part of the final QuickBooks-style CSV.

FAQ

Should I keep a Balance column in the final import file?

Usually no for a basic QuickBooks-style CSV. Balance is useful during review, not as a default import field.

When should I use Credit and Debit instead of Amount?

Use separate Credit and Debit columns when the downstream import flow specifically expects them. Otherwise, one signed Amount column is simpler to validate.

Can I upload redacted statements for mapping tests?

Yes. Redacted files are fine if the transaction rows, dates, and amounts are still readable.

Turn a statement file into reviewable rows

Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.

Review the columns