Templates
QuickBooks bank transaction CSV template
Use a simple Date, Description, and Amount CSV shape for bank statement transactions before importing or reviewing in QuickBooks.
Required columns
The first DocuRows QuickBooks preset focuses on the simplest bank transaction CSV shape. It is easy for users to inspect and easy to generate from many bank statement layouts.
- Date
- Description
- Amount
Amount signs
Money leaving the account should be negative. Money entering the account should be positive. This is easier to audit than a PDF layout with separate debit and credit columns.
Fields to avoid in the import file
Statement balance, account number, page number, opening balance, ending balance, and summary totals are useful context, but they should not become transaction rows.
When to use Excel first
If a user wants to inspect, sort, filter, or categorize transactions before import, opening the CSV in Excel or Google Sheets is a practical review step.
Template
Date,Description,Amount 04/02/2026,POS PURCHASE OFFICE DEPOT,-48.12 04/03/2026,ONLINE TRANSFER FROM CHECKING,850.00 04/05/2026,BANK SERVICE FEE,-15.00
The date format can be normalized during review. The important part is consistent rows and signed amounts.
FAQ
Should Description be split into merchant and memo?
Not for the first simple CSV. A single Description column is easier to review and usually enough for bank transaction import prep.
Should check numbers be a separate column?
Only if the downstream workflow requires it. The simpler first version can keep check numbers inside Description.
Can categories be added automatically?
Categories are a later workflow. The first priority is accurate dates, descriptions, and signed amounts.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.