Import guide

QuickBooks Transaction CSV Import Checklist

Check Date, Description and Amount columns before importing bank transaction CSV files into QuickBooks.

Recommended first tool

Start with QuickBooks CSV Checker

Check bank transaction CSV files before importing into QuickBooks.

Open QuickBooks CSV Checker

What this guide covers

Confirm the required transaction columns
Normalize dates and amounts
Detect duplicate transactions
Reconcile before final upload

Confirm the required transaction columns

QuickBooks transaction imports usually start with Date, Description and Amount. If one of those columns is missing or named unexpectedly, the importer cannot map the file cleanly.

Check the header row first, then inspect the data values. A correct header with bad dates or currency-formatted amounts can still fail during import.

Normalize dates and amounts

Dates should use one format throughout the file. Mixing `2026-01-31`, `01/31/2026` and spreadsheet locale formats increases the risk of misread transactions. Choose the date format expected by your import mapping and normalize the column before upload.

Amounts should be plain numbers. Remove currency symbols, labels and text. Negative amounts and zero amounts may be valid refunds, fees or adjustments, but they should be reviewed before import.

Detect duplicate transactions

Duplicate transaction rows can create duplicate entries in accounts. A practical duplicate key is Date plus Description plus Amount, but you may need a bank-provided transaction ID when available.

Review duplicates before deleting. Recurring subscriptions and fees can look similar, so a repeated amount is not enough to prove a duplicate by itself.

Reconcile before final upload

Keep the original bank export, the reviewed issue report and the cleaned CSV. If totals do not match after import, those files make it easier to find removed rows, corrected dates or filtered adjustments.

Run the cleaned file through a generic CSV checker too. Blank descriptions, trailing spaces and copied footer rows can cause problems even when Date and Amount look valid.

Example QuickBooks preflight

Load the QuickBooks sample in QuickBooks CSV Checker. It should flag duplicate transaction keys, invalid dates and zero or negative amounts for review. Fix those rows, then run CSV Data Quality Checker on the cleaned file.

FAQ

Are negative QuickBooks amounts always errors?

No. They can represent refunds, chargebacks or adjustments. The checker flags them for review so they are not imported accidentally.

Can duplicate descriptions cause duplicate transactions?

Not by themselves. Use Date, Description and Amount together, or a transaction ID when available, to identify likely duplicates.

Related guides

Next workflow