Choose your CSV
Export transactions from your bank as a CSV file. Nothing is uploaded.
Bank CSV → QuickBooks
Map your bank's columns, check dates and amounts, then download a normalized CSV or an optional QBO Web Connect file for a supported QuickBooks import workflow. Your financial data stays in your browser.
Free formatter
Map and review the transactions once, then choose the output that matches your QuickBooks product.
How it works
Export transactions from your bank as a CSV file. Nothing is uploaded.
Identify dates, amounts, descriptions, and optional transaction IDs.
CSV is the straightforward QuickBooks Online route. QBO is an alternative Web Connect format supported in some Online and Desktop workflows.
Choose the right output
The similar names cause understandable confusion. Your destination product—not the name of this website—determines which file to download.
| Your destination | Recommended output | Important limitation |
|---|---|---|
| QuickBooks Online | Normalized CSV for the simplest mapping workflow | Current Intuit guidance also lists QBO and QFX, but accepted options and validation can vary by workflow. |
| QuickBooks Desktop with Web Connect | QBO Web Connect file | Desktop may reject files whose financial-institution details are not recognized. Test a short date range first. |
| Unsure which QuickBooks product or workflow you use | Do not import yet | Read the format guide and confirm the destination account and supported file type first. |
See the QuickBooks Online CSV format guide, based on current Intuit support documentation, before choosing an output.
Is your export ready?
A usable bank CSV has one header row and enough information to determine the date, description, and direction of every transaction.
| CSV layout | Use it? | Mapping choice |
|---|---|---|
| Date, Description, Amount with negative withdrawals | Yes | Map the signed Amount column |
| Date, Description, Debit, Credit | Yes | Leave Amount unused; map Debit and Credit |
| All amounts positive with only a custom Type label | Not directly | Export another layout or prepare separate debit/credit columns |
| PDF statement or spreadsheet workbook | No | Download or save a real CSV first |
Unsure which columns you have? Compare your export with the fictional sample CSV layouts or read the column-mapping guide.
Fictional example
A source row such as 07/18/2026, Northside Office Supply, -48.25 stays a negative amount in normalized CSV and becomes a debit transaction in QBO output. A positive 1250.00 customer receipt remains positive or becomes a credit transaction. QBO output also includes the selected account type, currency, and a transaction identifier.
The converter does not categorize the office purchase, connect it to a vendor, or decide which ledger account to use. Those bookkeeping decisions remain in the receiving software and under your review.
Choose the correct QuickBooks format →More than a converter
Use original Bank2QBO resources before and after conversion so the workflow is reproducible rather than dependent on guesswork.
Detect delimiter, heading, date, amount, blank-description, debit-credit, repeated-heading, and total-row risks locally.
Inspect a CSV →Compare signed-amount and debit-credit layouts, use a three-column template, and record each import in a control log.
Open the library →See the parser test matrix, failure cases, authorship, source policy, limitations, and material change record.
Read the methodology →How privacy works
When you choose a CSV, browser code reads it on your device, builds the preview, and creates the downloadable CSV or QBO file. Bank2QBO does not operate a transaction-processing endpoint and does not receive the selected file, transaction descriptions, amounts, or account identifier.
Optional analytics requires your explicit choice, while advertising privacy choices use Google's consent system where required. Neither is given the contents of your selected or generated files. See the privacy policy for the precise data-handling explanation.
Common questions
No. Parsing and conversion happen locally in your browser. The file never leaves your device.
The mapper supports comma-delimited CSV files with numeric dates and either one US-style signed amount column (for example, 1,234.56) or separate Debit and Credit columns. It does not currently interpret semicolon-delimited files, localized decimal commas, or arbitrary transaction-type labels.
Confirm the account type, date order, signs, and statement dates. Import a small file first and keep your original CSV.
No. Bank2QBO creates a file for manual import and never receives your QuickBooks credentials. File acceptance is controlled by your QuickBooks product and its current import rules.
Conversion help
Clear, independent guidance for mapping, importing, and troubleshooting bank transactions.
QuickBooks Online format
Prepare a bank CSV for QuickBooks Online, choose the supported three- or four-column layout, and understand when a QBO Web Connect file is the wrong format.
Read guide →Conversion guide
Turn a bank CSV export into a QBO file with the correct dates, amounts, account type, and transaction IDs.
Read guide →Import workflow
A pre-import checklist for cleaner QuickBooks bank transaction uploads and fewer duplicate or misclassified entries.
Read guide →