Free · No account · Browser-only
Import bank statements into QuickBooks Desktop and Online with a reviewable QBO file. Mapping and conversion happen in your browser; your CSV is never uploaded.
CSV → QBO workbench
Your bank data never leaves this browser.
Who this is for
Bank exports are designed for reading, while QuickBooks bank feeds expect a structured import file. CSV2QBO closes that format gap without hiding the decisions. You choose the date, description, amount, debit, credit, memo, and optional transaction ID columns; the workbench shows what will be exported before it creates the QBO file.
Turn a checking, savings, or credit-card export into a file you can review before bringing historical transactions into QuickBooks. The workflow stays focused on the statement in front of you: no account creation, subscription choice, or bookkeeping dashboard to configure.
Use explicit column mapping and a transaction preview when a client sends a CSV instead of a Web Connect file. Deterministic transaction IDs help the same ordered source data produce consistent identifiers, while genuine repeated rows remain separate transactions.
Convert transaction exports from an internal system, payment report, or unfamiliar bank layout when the file still contains parseable dates, descriptions, and amounts. Header suggestions accelerate common cases; every suggested field remains editable.
Three deliberate steps
The whole conversion remains visible in one workbench. Nothing is sent to a server, and nothing is downloaded until required fields validate.
Choose or drop a CSV export. Browser JavaScript reads the file locally, removes a byte-order mark when present, detects comma, semicolon, or Tab separation, and keeps quoted commas and line breaks together. The original statement is not posted to csv2qbo.com.
Confirm the date, description, amount, debit, credit, memo, and transaction ID fields. Select MDY, DMY, or YMD, then inspect normalized amounts and row-level issues. Missing fields, zero amounts, invalid dates, and conflicting debit and credit values block the download.
The converter writes an OFX 1.02 Web Connect document with bank-account metadata, statement dates, signed amounts, descriptions, and deterministic FITIDs. It encodes the result for the legacy format and downloads a .qbo file to your device.
Private by architecture
The converter has no upload endpoint. The Worker serves the application; your file is read and transformed by JavaScript on your device.
The format gap
CSV is a flexible table, not a banking interchange contract. A header such as Amount does not tell software which date convention you used, whether debits are negative, which account receives the data, or how repeat imports should be identified. QBO wraps normalized transactions in an OFX Web Connect structure that QuickBooks can treat as bank-feed data.
A CSV can use almost any header names, delimiter, date notation, sign convention, and optional columns. That flexibility is convenient for exports but leaves critical meaning implicit.
Mapping states exactly which source field means date, description, signed amount, debit, credit, memo, or transaction ID. Ambiguous dates are controlled by one explicit date-order setting.
Values are converted into consistent dates and integer cents before output. Invalid or contradictory rows appear as issues instead of being silently coerced into financial data.
The output adds statement and account metadata, transaction types, signed amounts, names, memos, and stable FITIDs inside an OFX 1.02 Web Connect document saved with a .qbo extension.
The converter does not categorize transactions, reconcile accounts, connect to your bank, or promise that every institution-specific import will succeed. Its job is narrower: make the transformation visible, validate what it can, and produce one inspectable QBO file.
Supported CSV structures
Banks use different names and punctuation, but most transaction exports reduce to a few structural patterns. The parser detects comma, semicolon, and Tab delimiters, preserves quoted fields and embedded line breaks, and presents every source column for mapping. That is more honest and more useful than claiming a fixed number of supported banks.
| Layout | Expected columns | Date handling | What the converter handles |
|---|---|---|---|
| Single signed amount | Date, Description, Amount; optional Memo and transaction ID | MDY, DMY, or YMD selected explicitly | Positive and negative values, currency symbols, parentheses, trailing minus signs, decimal commas, and thousands separators |
| Separate debit and credit | Date, Description, Debit, Credit; optional Memo and transaction ID | MDY, DMY, or YMD selected explicitly | Debit becomes negative and credit positive. A row containing values on both sides is blocked for review instead of guessed. |
| European-style export | Quoted fields separated by semicolon or Tab, with the same required transaction fields | DMY and YMD are available alongside MDY | Decimal commas and grouped values are normalized after you confirm the date format and field mapping. |
| Unfamiliar column names | Any parseable header row containing date, description, and amount information | The selected date order applies consistently to every row | Choose columns manually when a bank uses unfamiliar names. Export remains disabled until required mappings and row values validate. |
What this is not: a private catalog of bank templates. CSV2QBO currently suggests common English accounting headers and gives you manual controls for everything else. Compatibility depends on the structure of the export, not the logo printed on the statement.
Compatibility, plainly stated
QuickBooks Desktop and QuickBooks Online do not expose the same bank-transaction import workflow. This converter produces one format only: a Web Connect QBO file. The notes below explain where that file belongs and where QuickBooks already gives you other choices.
For the Bank Feeds Web Connect workflow, QuickBooks Desktop imports files with a .qbo extension. A CSV may be useful for other QuickBooks data tasks, but it is not the Web Connect bank-feed file used by this workflow.
QuickBooks Online can manually upload CSV, TXT, QBO, and OFX files. You do not need to convert every CSV first. CSV2QBO is useful when you want to inspect mapping outside QuickBooks, normalize signs and dates, or keep a reusable QBO artifact.
Before you import
No. Parsing, mapping and QBO generation happen inside your browser. The selected file is never sent to csv2qbo.com.
The first release supports CSV and plain-text exports. Save Excel files as CSV before using the converter.
Choose the format used in your file before export. Ambiguous dates are never silently guessed.
Each transaction receives a deterministic FITID. Re-exporting the same ordered data produces the same IDs, while genuine duplicate rows remain unique.
No. CSV2QBO generates and validates an OFX 1.02 Web Connect structure, but banks and QuickBooks editions can apply institution-specific rules. Back up your books, review the preview, and test the import before relying on it for production bookkeeping.
It reads quoted CSV data with comma, semicolon, or Tab delimiters. It can map either one signed Amount column or separate Debit and Credit columns. Common English header names are suggested automatically; unfamiliar headers can be selected manually.
The parser supports MDY, DMY, and YMD date orders plus common decimal and thousands-separator styles. Automatic header suggestions are English-focused, so a file with non-English column names usually needs manual mapping before export.
CSV2QBO accepts one local file up to 5 MB and 50,000 data rows. Those are converter limits, not promises about QuickBooks. QuickBooks Desktop or Online may impose lower or different limits, so check its current guidance before a large import.
This release exports QBO only. QFX is another OFX-based format, while IIF is a separate QuickBooks import format with a different structure and workflow. CSV2QBO does not generate QFX, IIF, PDF, or Excel files.
First confirm the selected date order, signs, account type, bank ID, account ID, and institution ID. Make sure you are using the correct QuickBooks import path and that the institution supports manual Web Connect. Keep a backup and consult Intuit's current import guidance for product-specific errors.
CSV2QBO is an independent utility and is not affiliated with, endorsed by, or sponsored by Intuit Inc. QuickBooks is a trademark of Intuit Inc.
Ready when your statement is
Open your bank export in the workbench above, confirm the mapping, inspect the dates and signs, then download the QBO file. The conversion is free, requires no signup, and keeps the source statement on your device.
Before importing financial data, keep a backup and review the destination account in QuickBooks.
