Finance
QuickBooks Bank Transactions CSV import requirements
Import bank transactions into QuickBooks Online with proper date and amount formatting. Below are the 4 columns the import expects, including 2 required fields, the formats each one accepts, and the errors that most often cause a failed import.
Validate my QuickBooks Bank Transactions CSV freeQuickBooks Bank Transactions CSV columns
Header names are matched automatically — the “also accepted” names are mapped to the correct QuickBooks Bank Transactions field. Dates should use the MM/DD/YYYY format.
| Column | Required | Type & rules | Also accepted headers |
|---|---|---|---|
| Date | Yes | Date, format MM/DD/YYYY | date, Transaction Date, transaction_date, Datum, Posted Date |
| Description | No | Text, max 4,000 characters | description, Memo, memo, Narrative, Details |
| Amount | Yes | Number | amount, Total, total, Value, value |
| Check No. | No | Text | check_no, Check Number, Cheque No, Reference, Ref |
Common QuickBooks Bank Transactions import errors
- Column headers that don’t match QuickBooks Bank Transactions field names (for example "Transaction Date" instead of "Date").
- Missing or empty required columns: Date, Amount.
- Dates in the wrong format, for example DD/MM/YYYY where the importer expects another order.
- Numbers with currency symbols, thousands separators, or European decimal commas.
- Values longer than the field’s maximum length, which the importer truncates or rejects.
- Hidden problems: wrong file encoding, a byte-order mark, extra blank rows, and leading or trailing whitespace.
How to check your file before importing
- Open the free validator and upload your CSV, TSV or Excel file — nothing leaves your browser.
- Choose QuickBooks Bank Transactions and confirm the suggested column mapping.
- Review the four-layer report: structure, formats, content and cross-field rules.
- Apply one-click repairs, then download the clean file and import it.