Start with a transaction table, not a PDF
Use a CSV, TXT, or XLSX export that contains individual transactions. A PDF statement, image, or printed report is not supported by the converter and should not be renamed to look like a CSV.
Bank statement CSV to QBO
Bank statement CSV to QBO: prepare a local beta file.
If a bank or card portal gives you a transaction CSV, you can prepare it for BankFileKit's local CSV-to-QBO beta. A statement export is not automatically a valid QBO file, so the source table and a fictional test both matter.
Updated July 24, 2026 · Examples use fictional data.
Use the next step nowChoose a local statement CSV, review the mapping, and create a candidate file without uploading the source.
Prepare a CSV to QBO candidate Check the source before conversion
| Check | Why it matters |
|---|---|
| One transaction per row | Statement headings, subtotals, and balance rows are not transactions and should be removed. |
| Dates use one convention | A value such as 03/04/2026 can mean two different days until the source convention is selected. |
| Amounts have a clear direction | Use a signed Amount or one populated Credit/Debit side per row. Verify a known purchase and deposit. |
| Description text is readable | The QBO candidate uses this text for the transaction name, so blank or private detail should be reviewed first. |
A statement CSV and a QBO file are different
A CSV keeps visible rows and columns. A QBO file is a structured Web Connect file. The beta writer must map the CSV rows into that structure, which is why a correct-looking spreadsheet still needs a preview and a target-product test.
Fictional bank-statement example
Date,Description,Amount 07/18/2026,Fictional Stationery Store,-31.40 07/19/2026,Fictional Service Invoice,680.00
Local preparation workflow
- Download a transaction CSV or export a clean spreadsheet table.
- Keep the original copy outside the converter.
- Choose the file locally and confirm Date, Description, and Amount or Credit/Debit columns.
- Review warnings, row count, and amount direction before download.
- Create a candidate QBO only after the preview matches the intended source period.
Use a blank-company test for the candidate QBO
BankFileKit has not verified its generated QBO output in real QuickBooks Desktop. Keep a backup, use a blank test company, and compare transaction count, dates, signs, and readable descriptions after any attempted import. Do not repeatedly import the same period into a live account.
What not to assume
- A bank name or CSV column label does not establish QBO compatibility.
- A successful file download does not establish successful QuickBooks import.
- BankFileKit does not connect to a bank, validate a login, or certify a bank-specific workflow.
- Unsupported files—including PDF, QIF, IIF, QBW, and QBX—cannot be converted by changing their extension.
Keep statement data on your device
The source file and generated output stay in browser memory. Do not send a real statement to support. If a conversion problem needs review, create a small, fully fictional CSV that has the same table shape.
Sources checked July 24, 2026: Intuit CSV formatting guidance; Intuit Web Connect troubleshooting.