CSV to QBO troubleshooting
A source-file validation issue is different from a QuickBooks Web Connect rejection. Fix the local table first, then treat the generated QBO beta as a separate, cautious import test.
Updated July 24, 2026 · Examples use fictional data.
BankFileKit can report a source-file issue before download, such as an invalid date or amount. A later Web Connect error comes from the target QuickBooks workflow. Do not treat a changed file extension as a fix for either category.
| Visible issue | Likely source problem | Safe correction |
|---|---|---|
| Date missing or ambiguous | Mixed formats, an invalid value, or a heading row mapped as a transaction. | Choose one date convention and remove non-transaction rows. |
| Amount missing or invalid | Currency text, a blank cell, or a non-numeric value. | Use a clean signed Amount field or valid Credit/Debit fields. |
| Credit and Debit conflict | Both sides of a row contain a non-zero value. | Keep one side populated for each transaction. |
| Description empty warning | The mapped Description cell is blank. | Map a readable Details, Payee, Memo, or Description column and recheck the preview. |
| No usable transactions | The table contains only headers, notes, or invalid rows. | Export the actual transaction table rather than a statement summary. |
Bank exports use different words for the same concept. Check that the selected Date, Description, Amount, Credit, and Debit columns match a known fictional or non-sensitive example. A header named Balance is not a transaction Amount.
BankFileKit's CSV-to-QBO result is an unverified beta. A structurally generated file can still be rejected because of a QuickBooks release, account state, institution information, or Web Connect requirement. Back up first, test in a blank company, and follow Intuit's current Web Connect guidance rather than repeatedly importing into production books.
Date,Description,Amount 07/20/2026,Fictional Refund,24.00 07/21/2026,Fictional Software License,-79.00
The converter reads and generates the file in the browser. Analytics receives only allow-listed aggregate event fields—not filenames, source text, account information, transaction amounts, dates, or descriptions. If support needs context, send a generic error category and a fully invented example.
Stop and preserve the original export if transactions are missing, duplicated, reversed, or connected to a live QuickBooks account. A converter cannot make bookkeeping or reconciliation decisions, and a browser download is not proof of an accurate import.