CSV to QBO file requirements

CSV to QBO file requirements: prepare a CSV for QuickBooks.

A bank CSV is only a table, while a QBO file needs dates, signed transaction values, and an account-oriented structure. Prepare a clean source, review every row, and treat the generated QBO as a local beta candidate—not a guaranteed import.

Updated July 25, 2026 · Examples use fictional data.

Use the next step nowChoose a local CSV, TXT, or XLSX file, confirm the mapping, and generate a candidate QBO only after the preview looks right.
Open the CSV to QBO converter

Current input and output boundary

ItemCurrent BankFileKit behavior
Accepted source filesCSV, TXT, and XLSX. XLSX uses the first worksheet.
Source limitsOne file at a time, up to 20 MB and 50,000 source rows.
Generated resultA candidate .qbo Web Connect file for US English and USD testing.
Not accepted herePDF statements, QIF, IIF, QBW, QBX, images, bank logins, and complete company backups.

Minimum transaction fields

FieldWhat to provideWhat the tool does
DateA date consistent with the selected MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD convention.Blocks an invalid row; a numeric date that could mean two conventions requires explicit confirmation before export.
AmountOne signed Amount column, or separate Credit and Debit columns.Blocks a missing/invalid amount or a row with both Credit and Debit populated.
DescriptionReadable transaction text such as a merchant, payee, or memo.Shows a warning when empty; review it before creating the QBO candidate.

Map headings by meaning

Common headers such as Posted Date, Transaction Date, Details, Memo, Deposit, and Withdrawal can mean the same fields. Confirm the meaning before export—do not rely on a column position or a bank-specific label alone.

Fictional CSV example

Posting Date,Details,Deposit,Withdrawal
07/14/2026,Fictional Office Supply,,48.20
07/15/2026,Fictional Client Payment,425.00,

Prepare the table before conversion

  1. Export a transaction table from the source system, not a formatted statement report.
  2. Keep one transaction per row; remove titles, subtotals, and repeated header rows.
  3. Choose one date convention, explicitly confirm ambiguous numeric dates, and check several familiar transactions.
  4. Review possible-duplicate warnings; the tool never removes repeated rows automatically.
  5. Confirm the sign or Credit/Debit direction against a known purchase and deposit.
  6. Use invented values to reproduce a problem instead of sharing a real statement.

CSV to QuickBooks is not one universal workflow

QuickBooks Online can use a formatted bank CSV, while a .qbo file is a Web Connect format commonly used in QuickBooks Desktop workflows. BankFileKit has a local CSV formatter for the former and an unverified CSV-to-QBO beta for the latter. Choose the target workflow before converting.

Test the QBO candidate cautiously

Download does not establish compatibility. Keep a backup, test only in a blank QuickBooks Desktop company, then compare dates, transaction count, amounts, and descriptions. If the target rejects the file, record only a generic error category and use a fictional reproduction.

The source file stays local

The selected source is read, mapped, previewed, and exported in browser memory. BankFileKit does not upload the source file, the generated QBO, filenames, account details, or transaction data to its application server, analytics, or AI services.