DDocuRows
New file

QuickBooks CSV format

QuickBooks CSV import format for bank transactions

For users who have transaction rows but need the columns, mapping, and cleanup checked before uploading a CSV to QuickBooks.

1

Choose the 3-column or 4-column CSV shape.

2

Clean mapping, dates, amounts, and extra columns.

3

Review the QuickBooks-ready CSV before import.

The two QuickBooks CSV shapes

QuickBooks supports a 3-column bank transaction CSV with Date, Description, and Amount, and a 4-column layout with Date, Description, Credit, and Debit. DocuRows currently exports the simple Date, Description, and Amount CSV, not a native .qbo file.

Clean the file before upload

Remove extra columns, map each CSV field to the matching QuickBooks field, and keep dates and amounts in a format your import screen accepts. Strip currency symbols, commas in amount values, and spreadsheet formatting that can travel with copied rows.

Why PDF conversion often fails

Generic PDF-to-Excel conversion can mix transaction rows with logos, statement summaries, balances, headers, footers, and page text. The import file should be one row per real transaction with readable descriptions.

Review before importing

Review row count, date order, amount signs, totals, and any ignored rows before import. For historical cleanup, import one statement or smaller date ranges at a time so duplicate checks are easier.

Related workflows

QuickBooks CSV import formatQuickBooks bank transactions CSVDate Description Amount CSVCredit Debit CSV QuickBooks

QuickBooks CSV format FAQ

Should I use Amount or Credit/Debit columns?

The simple format uses one signed Amount column. The 4-column format separates Credit and Debit. Choose the option that matches your QuickBooks upload flow.

Should withdrawals be negative?

For the 3-column Amount format, money out should be negative and deposits should be positive.

Can QuickBooks import a PDF directly?

QuickBooks bank transaction upload needs a supported transaction file format. A statement PDF generally needs to become structured rows before import.

Why did my CSV import fail?

Common causes include wrong mapping, extra columns, date formatting issues, currency symbols, commas in amounts, and rows from PDF-to-Excel noise that are not real transactions.

Can DocuRows create a native QBO file?

Not yet. The current product exports QuickBooks-ready CSV rows, not native .qbo files.