Troubleshoot a QBO file that will not import

Confirm the file and destination

Make sure you selected the downloaded .qbo file rather than the original .csv file. Then verify that the destination register is the right account type. A credit card file should not be directed to a checking register, and two different real-world accounts should not share the same import file.

• Reconvert with the intended account type.
• Use one account and one currency per file.
• Try a file containing a few known transactions.
• Record the exact import message before making changes.

Dates are rejected or unexpected

Return to the converter and check month/day/year versus day/month/year. Also verify that every transaction has a real calendar date and that the export does not contain headings or balance rows in the date column. Spreadsheet-formatted dates can display differently from their stored values; compare the CSV text with the statement.

If dates import but land in the wrong period, do not accept or categorize them. Remove the test records using the receiving product’s documented workflow, correct the mapping, and generate a new file.

Amounts are reversed

Expenses should be negative for checking and savings imports, while deposits should be positive. For a credit card, purchases are normally negative and payments or refunds positive in the transaction feed. If every amount is reversed, inspect the source sign convention and whether Debit and Credit were swapped.

Do not map a positive-only amount column if the transaction direction is stored in a separate Type column; the converter cannot infer money in versus money out from arbitrary text. Export a layout with signed amounts or separate debit and credit columns.

Duplicates appear

Stop before importing another file. Compare the date range with previous imports and review whether the same statement was converted twice from differently ordered or edited CSVs. A generated transaction ID is stable for identical input, but changes to row content can change it.

Resume with a date range that does not overlap the existing register. Reconcile the account after correcting duplicates so the register agrees with the bank statement.

The file is still rejected

Create a minimal test file with two or three posted transactions and no extra rows. If that imports, add data in small batches until the problematic record is isolated. If even the minimal file fails, preserve the exact error text and consult the support documentation for your QuickBooks product and version; available import paths and restrictions can differ.

Bank2QBO is independent software and is not affiliated with Intuit. It cannot inspect errors inside your QuickBooks account because conversion happens locally and no credentials are collected.

Use a controlled fault-isolation sequence

Do not change date order, account type, column mapping, and date range all at once. Begin with a fictional or non-production test containing one negative and one positive transaction. Confirm that the generated file uses the intended account type. Then add a third row from the problematic source.

If the two-row file works and failure returns after adding one real row, inspect that row for an invalid date, missing amount, embedded heading, or unusual text. If the two-row file fails, revisit the account and import workflow before changing transaction data. This sequence narrows the cause without repeatedly exposing a full statement to the receiving workflow.