QuickBooks Online CSV format: 3-column and 4-column templates

Choose the format for your QuickBooks product

Start with the product and import screen you actually use. Intuit's current QuickBooks Online guidance accepts manual uploads in QBO, QFX, and CSV formats and describes CSV layouts with either three or four transaction columns. Its QuickBooks Desktop guidance describes Web Connect files with a .qbo extension. The shared brand name can make these options sound interchangeable, but each file still has to satisfy the checks used by the destination workflow.

If your QuickBooks Online transaction-upload screen accepts CSV, a normalized CSV is usually the clearest choice because you can inspect and map its columns. Use a .qbo file only when the destination explicitly accepts it and you understand that Web Connect-style files may be validated against product, financial-institution, or format details. Do not rename one extension to another: changing a filename does not convert the data structure.

Use a supported three- or four-column CSV

Intuit documents two common QuickBooks Online CSV structures. A three-column file contains Date, Description, and Amount. The Amount field carries the direction: money out is negative and money in is positive. A four-column file contains Date, Description, Credit, and Debit, with money in and money out separated into their own columns.

Choose one structure and use it consistently. Do not include a signed Amount column and separate Credit and Debit columns in the same import mapping. A normalized three-column file is usually the simplest portable result when your source already distinguishes positive deposits from negative withdrawals.

Format the values before upload

Use one header row followed only by transaction rows. Remove statement titles, repeated headings, opening or closing balance summaries, blank report notes, and total rows from a working copy. Keep the untouched bank export separately. QuickBooks Online asks you to map the source columns during upload, so a plain heading such as Date or Transaction date is acceptable as long as you map it deliberately.

Dates should use one consistent order throughout the file. Intuit's formatting guidance shows formats such as DD/MM/YYYY and MM/DD/YYYY; the correct interpretation still needs to match the source statement. Descriptions should identify the merchant or payee clearly. Amount cells should contain transaction values, not currency symbols mixed with commentary. A CSV must use commas as separators for the documented import workflow.

• Keep one account and one currency in each file.
• Use posted rather than pending transactions when possible.
• Check that spreadsheet software did not turn identifiers into scientific notation.
• Review descriptions containing commas to make sure they remain quoted as one field.
• Save the result as CSV, not an Excel workbook with an .xlsx extension.

Worked QuickBooks Online example

This fictional three-column example represents one expense, one customer receipt, and one bank fee. It is for understanding the layout only; do not import fictional activity into production books.

Date,Description,Amount
07/01/2026,Office Supplies,-42.60
07/02/2026,Customer Receipt,900.00
07/03/2026,Monthly Bank Fee,-9.00

Use Bank2QBO without choosing the wrong output

Bank2QBO can normalize a bank export into a clean three-column CSV for a QuickBooks Online upload workflow. Map the source date, description, and either a signed amount or separate debit and credit fields; then review the preview before downloading the QuickBooks CSV. This is a format-preparation step, not a connection to your QuickBooks company.

The QBO Web Connect output is an alternative for an import screen that explicitly accepts .qbo files, not a more advanced version of CSV. Web Connect-style validation can depend on product version, financial-institution information, and file details. A third-party generated .qbo file may be rejected even when its transaction rows are valid, so test a short date range and follow the exact error guidance for your QuickBooks product.

Import a controlled test, then reconcile

Before uploading, compare the transaction count, earliest and latest dates, one withdrawal, and one deposit with the original export. In QuickBooks Online, select the intended account and map each CSV column on the upload screen. If the sample preview reverses money in and money out, stop and correct the source or mapping rather than accepting the transactions.

Begin with a short, non-overlapping date range. After import, compare every test row with the bank record and reconcile the account to its statement. Imported bank data still needs review, categorization, and duplicate control. Keep a small import log with the account nickname, date range, row count, and completion date so the next upload begins after the last successful period.

• Never upload the same period repeatedly while troubleshooting.
• Do not assume a successful upload means every transaction was categorized correctly.
• Preserve the original bank export and the normalized file.
• Consult current Intuit documentation when menus or accepted formats differ from this guide.