Turn bank transaction data into QuickBooks-ready QBO files. Import into QuickBooks Online or Desktop in two clicks — free, no signup, no desktop software to buy.
You have transactions in a CSV — exported from your bank, a payment platform, or converted from a PDF — and QuickBooks won't take it. This is the most common bank-feed frustration in QuickBooks:
Our converter produces valid QBO (Web Connect) files that import cleanly into both QuickBooks Online and Desktop.
When you import CSV to QBO, the converter needs to know which CSV columns correspond to which QBO transaction fields. Our converter auto-detects common column names, but understanding the mapping helps you prepare a clean CSV that converts without errors.
| CSV Column Name(s) | QBO Field | Format Required | Notes |
|---|---|---|---|
| Date, Posting Date, Transaction Date, Value Date | DTPOSTED | MM/DD/YYYY or DD/MM/YYYY or YYYY-MM-DD | Must be a real calendar date |
| Description, Memo, Payee, Narrative, Particulars | MEMO | Plain text | Special characters (&, <, >) are escaped automatically |
| Amount (single column) — or separate Debit + Credit columns | TRNAMT | Negative = debit (money out), Positive = credit (money in) | Do not include currency symbols — strip £, $, € before uploading |
| CSV Column Name(s) | QBO Field | Purpose |
|---|---|---|
| Balance, Running Balance, Closing Balance | Not in OFX standard — stripped | Can be used internally to validate amounts but not exported to QBO |
| Reference, Cheque No, Check Number, Ref No | CHECKNUM | Appears in QuickBooks as the check/reference number field |
| Type, Transaction Type, Txn Type | TRNTYPE (DEBIT/CREDIT/OTHER) | Overrides the sign-based auto-detection of transaction type |
This is the ideal column layout for a CSV you want to import to QBO. Copy this format when preparing data from a spreadsheet:
Many bank CSVs — especially from UK and Australian banks — use two amount columns instead of one signed amount. Our converter handles this automatically:
Every major US bank exports CSV activity slightly differently. Here is exactly what each bank's download looks like and how our converter maps it to QBO.
Chase exports from the Activity > Download Account Activity page as CSV with these columns:
How we map it: Posting Date → DTPOSTED, Description → MEMO, Amount → TRNAMT (Chase already uses signed amounts — negative for debits), Type column → TRNTYPE, Check or Slip # → CHECKNUM. The Details and Balance columns are informational and not written to QBO.
Bank of America downloads from Accounts > Download > CSV format:
How we map it: Date → DTPOSTED, Description → MEMO, Amount → TRNAMT (signed). Running Bal. is stripped. Clean 4-column format — one of the easiest to convert to QBO.
Wells Fargo exports from Account Activity > Download Account Activity as a headerless CSV:
How we map it: Column 1 → Date, Column 2 → Description, Column 3 → Amount (signed), Column 4 → empty/check number, Column 5 → Balance (stripped). The lack of headers is handled automatically — Wells Fargo's format is detected by column count and positional structure.
Capital One (checking, savings, and credit cards) exports from the Download Transactions button:
How we map it: Transaction Date → DTPOSTED (YYYY-MM-DD format auto-detected), Description → MEMO, Debit → negative TRNAMT, Credit → positive TRNAMT. Card No. and Category columns are stripped. The separate Debit/Credit columns are combined into a single signed amount in the QBO output.
Citibank downloads from Account Details > Download in CSV format:
How we map it: Date → DTPOSTED, Description → MEMO, Debit/Credit columns → combined signed TRNAMT. Status column is stripped. Citibank uses a Debit column with negative values (already signed) which we handle correctly.
These are the errors people hit most when trying to convert CSV to QBO or import QBO into QuickBooks — and how to fix each one.
| Error | Cause | Fix |
|---|---|---|
| Invalid file format in QuickBooks import | The QBO file has a corrupted header, wrong bank ID, or was opened and re-saved in a text editor that changed the encoding | Re-download the QBO from our converter without opening it. Import the original downloaded file directly. Do not open QBO files in Excel or Notepad before importing. |
| 0 transactions imported — import appears to succeed but nothing appears | All transactions in the QBO file are duplicates of ones already imported. QuickBooks filters them silently via FITID matching. | Check your existing bank feed for the same date range. If you need to force re-import, use a fresh date range or contact QuickBooks to clear the FITID cache for the account. |
| Date out of range or transactions assigned to wrong year | Your CSV uses DD/MM/YYYY but the converter interpreted it as MM/DD/YYYY (or vice versa). Ambiguous dates like 04/05/2025 can be read either way. | Reformat the Date column in your CSV to YYYY-MM-DD (ISO 8601) before uploading — this format is unambiguous and always parsed correctly. |
| Amount sign reversed — debits show as credits in QuickBooks | Your CSV uses positive values for debits (some banks do this, especially UK banks). The converter assumed negative = debit. | Add a Type or Debit/Credit column to clarify direction, or invert the Amount column values in a spreadsheet before uploading (multiply Amount by -1). |
| Special characters in description — description appears garbled in QuickBooks | The CSV contains characters like &, <, >, or " that weren't escaped in the QBO XML output. | Our converter escapes these automatically. If you see garbled text, the CSV may have non-UTF-8 encoding. Open the CSV in a text editor, save as UTF-8, then re-upload. |
| Account not found or wrong account type during import | QuickBooks prompts you to link to an account during QBO import. If the account type in the QBO (checking vs credit card) doesn't match the QuickBooks account, it may warn or skip. | During the QuickBooks import wizard, select the correct existing account. If prompted about account type mismatch, create a new account matching the QBO type, then merge it with your existing one. |
| Currency symbol in Amount column — conversion fails | Your CSV has values like $1,234.56 or £450.00 in the Amount column. The converter can't parse these as numbers. | Strip currency symbols and thousand separators before uploading. In Excel: select the Amount column, Format Cells → Number → set decimal places to 2, no symbol. Or use Find & Replace to remove $ and ,. |
| Blank rows at top or between transactions | Some bank CSVs include summary rows, header blocks, or blank separator rows mixed in with transaction data. | Open the CSV in Excel, delete non-transaction rows (title rows, summary totals, blank lines), leave only the header row and data rows, then save and re-upload. |
QuickBooks Online has two ways to get bank transactions in manually: its built-in CSV uploader, and the QBO (Web Connect) file import. They are not equivalent. Here's the full comparison:
| Feature | QuickBooks CSV Import | QBO File Import |
|---|---|---|
| QuickBooks Online | ✅ Supported | ✅ Supported |
| QuickBooks Desktop | ❌ Not supported for bank feeds | ✅ Full support (Web Connect) |
| Column format required | Rigid 3-4 columns (Date, Description, Amount) — extras cause failure | Any bank format — our converter normalises it |
| Date formats accepted | MM/DD/YYYY only in QBO Online CSV wizard | Any date format — converter normalises to OFX standard |
| Duplicate prevention | None — re-importing the same CSV creates duplicates | FITID-based — QuickBooks skips already-imported transactions |
| Transaction type field | Not available — type inferred from amount sign only | TRNTYPE field (DEBIT/CREDIT/INT/DIV/FEE) supported |
| Real bank CSV compatibility | Low — extra columns, regional dates, and balance columns all cause errors | High — our converter handles all major bank formats |
| What to use | Only if you have a perfectly clean 3-column CSV and are using QuickBooks Online | Recommended for all cases — especially for QuickBooks Desktop or any real bank export |
The verdict: Always convert to QBO. The QuickBooks CSV importer is a convenience feature for simple use cases. For real bank exports with extra columns, different date formats, or when importing into QuickBooks Desktop, QBO import is the only reliable path.
QuickBooks Desktop is particularly popular in Canada, and Canadian banks export CSV files with slightly different column structures than their US counterparts. Here's how to import CSV to QuickBooks Desktop for the major Canadian banks.
TD Bank exports from EasyWeb > Account Details > Download Transactions as CSV:
TD uses separate Withdrawals/Deposits columns (no negative sign). Our converter combines them into a signed TRNAMT for the QBO file. After downloading the QBO, import via File > Utilities > Import > Web Connect Files in QuickBooks Desktop.
RBC exports from My Accounts > Download Transactions:
RBC splits description across Description 1 and Description 2 columns — our converter concatenates them for the MEMO field. The CAD$ column is used as TRNAMT (already signed). USD$ is stripped.
Scotiabank exports from the Account Details > Download section with a header block followed by transaction data:
Scotiabank includes account summary rows before the transaction data — open the CSV in Excel, delete everything above the header row, then upload. Our converter handles the Funds Out / Funds In column structure automatically.
BMO exports from Online Banking > Account Activity > Download:
BMO uses YYYYMMDD date format (no separators) — our converter parses this automatically. Transaction Type column (DEBIT/CREDIT) is used to verify amount sign. First Bank Card column is stripped.
Note: QuickBooks Desktop Canada supports CAD accounts natively. The QBO file our converter produces uses standard Web Connect format which QuickBooks Desktop Canada accepts without modification.
Tip: If you don't see the "Upload from file" option, your QuickBooks Online plan may not support manual uploads. QuickBooks Simple Start restricts this feature — it's available on Essentials and above.
QuickBooks Desktop versions supported: QuickBooks Pro, Premier, Enterprise (all years from 2015 onwards), and QuickBooks Desktop for Mac. The Web Connect import feature is available in all versions.
Most CSVs are themselves exported or converted from a bank statement. If you have the original statement PDF, convert it directly to QBO — one step instead of two, and with a critical advantage: balance verification. PDFs carry the running balance, so every extracted amount can be mathematically checked. A CSV has no balance context — errors in it pass through silently. Going PDF → QBO catches what CSV → QBO can't.
Bank statement PDF from any bank — digital or scanned
Transactions extracted and balance-checked automatically
Import into QuickBooks via Banking → Upload from file
| Format | QuickBooks Online | QuickBooks Desktop | Notes |
|---|---|---|---|
| QBO (Web Connect) | ✅ Full support | ✅ Full support | The reliable path for bank transactions |
| CSV | ⚠️ Limited (3-4 column only) | ❌ Not for bank feeds | Strict format, frequent import failures |
| OFX | ❌ | ❌ | Needs conversion to QBO for QuickBooks |
| QFX | ❌ | ❌ | Quicken's format — not QuickBooks |
| Excel | ⚠️ Via CSV export | ❌ | Convert to QBO for direct import |
Searches for CSV-to-QBO conversion mostly surface paid desktop utilities ($40–60 licenses) that require installation and per-machine activation. For converting bank statements, that's unnecessary: our converter runs in the browser, costs nothing, requires no signup, and adds balance verification that desktop CSV converters structurally cannot do.