QuickBooks Bank Statement Import Template: CSV Columns and Examples

Download the three-column CSV template

The most straightforward QuickBooks bank statement import template has three columns: Date, Description, and Amount. Current US QuickBooks documentation also accepts a four-column alternative, but the signed-Amount layout is easier to prepare when your source already represents money out as negative and money in as positive.

Download the synthetic CSV below, replace its example rows with reviewed transactions, and keep the header row intact. This is an independent StatementMint template based on Intuit's published bank-transaction format—not an Intuit file, a direct integration, or a guarantee that QuickBooks will accept unreviewed data.

Download the QuickBooks CSV template

Use exactly three fields in the destination file

QuickBooks maps the first row as field headings and each later line as one transaction. Keep the destination file narrow. Date identifies when the transaction occurred, Description carries the bank text used during review and matching, and Amount carries one numeric signed value. Statement balances, page numbers, account numbers, running balances, categories, and summary totals do not belong in this three-column import file.

Headers should be plain text with no leading or trailing spaces. Current Intuit guidance identifies Date, Description, and Amount as the required three-column fields. QuickBooks still asks you to map the uploaded columns, so verify the mapping rather than assuming that matching header names make it automatic.

Copy the example rows, then replace them

The downloadable file uses synthetic transactions and Intuit's currently recommended day/month/year date order. When you upload it, select the matching date format in QuickBooks. If your prepared source uses a different consistent date representation, create a destination copy and convert the dates there; do not repeatedly rewrite the reviewed source file.

Deposits and refunds are positive in the three-column example, while purchases and fees are negative. Keep the amount as a plain decimal number. A comma inside 2,450.00 would act as a field delimiter unless the CSV writer quotes it, and a dollar sign can cause a numeric field to be interpreted as text.

Know when the four-column layout is different

QuickBooks also documents a four-column layout with Date, Description, Credit, and Debit. That file has no signed Amount column: each transaction value appears in one of the two amount columns and the other cell stays blank. The headers should read Credit and Debit—not Credit amount and Debit amount—under Intuit's current formatting guidance.

Do not combine both layouts in one CSV, and do not guess how a source bank's debit and credit labels correspond to the QuickBooks screen. Those terms can be confusing across checking accounts and credit-card liabilities. Use the mapping preview for the selected account and confirm a known purchase plus a known deposit or payment before proceeding. When the source already has one reliable signed amount, the three-column layout avoids that extra transformation.

Prepare a destination copy from StatementMint

StatementMint's standard CSV already contains Date, Description, and signed Amount. It does not add QuickBooks categories, chart-of-accounts fields, tax codes, or journal entries. Convert the issued PDF, compare the transaction rows with the source statement, and preserve that reviewed export unchanged.

Duplicate the reviewed CSV for QuickBooks. If necessary, change only the date representation in the copy so every row matches the format you select during mapping. Keep descriptions attached to their transactions and retain numeric amounts. Then remove any non-transaction notes you added during review before saving the destination copy as CSV.

• Source PDF: authority for transaction completeness and wording.
• Reviewed StatementMint CSV: stable Date, Description, and signed Amount source.
• QuickBooks destination copy: only the formatting changes required by the current importer.
• QuickBooks review queue: matching and categorization happen after upload.

Run the import-error checklist before uploading

Current Intuit guidance says transaction-list files must be in English, no larger than 350 KB, and limited to 1,000 lines per upload. Those product limits can change, so check the current manual-upload page before processing a large history. Use smaller, non-overlapping date ranges when the file exceeds a limit.

Intuit's current troubleshooting pages also call out incorrect field mapping, currency formatting, inconsistent dates, zeros in unused amount cells, and problematic text as potential causes of rejection. Diagnose the specific failing row in a destination copy. Do not broadly strip legitimate merchant text or numbers from the reviewed source, because that can make matching and later audit work harder.

Test a small batch before the full period

Upload a short, representative destination file first when you are establishing a new workflow. Include at least one money-in row, one money-out row, a long description, and dates from the actual period. In QuickBooks Online, open Bank transactions, choose Upload from file, select the intended account, map the three columns, and inspect the transaction-selection screen before confirming.

After upload, match transactions that correspond to records already in the books and categorize only genuinely new records. Compare the accepted row count with the file, then reconcile the account to the statement ending date and balance. A successful file upload proves that the CSV was readable; reconciliation is what checks whether the account and statement agree for the period.

Keep the template separate from the accounting decision

A CSV template transports transaction facts; it does not decide the correct expense account, payee, tax treatment, class, or customer. Those choices require the business records and QuickBooks setup. Avoid placing guessed categories in a bank-transaction template simply because the merchant name looks familiar.

The safest handoff is a reviewed transaction file, a recorded account and statement period, a controlled upload preview, and a completed reconciliation. If QuickBooks changes its required fields or limits, the clean source CSV remains reusable because only the destination copy needs to change.

Frequently asked questions