QuickBooks Bank Upload Errors: 6 Common Fixes
A QuickBooks bank upload error usually falls into one of six categories: file already imported (duplicate detection), deposits showing as withdrawals (amount sign inverted in column mapping), fewer transactions than expected (header row counted as data, blank dates, or the 350 KB CSV size cap), unsupported format (PDF or Excel instead of CSV or QBO), generic import failure (malformed or oversized file), and transactions not appearing after upload (they land in For Review, not the register).
This page covers errors that appear during or after the upload. If your file is rejected before the column-mapping screen, the issue is usually file structure — see the QuickBooks CSV format requirements and error fixes.
Error-by-Error Fixes
1. “This file has already been imported”
QuickBooks detects duplicate uploads using transaction IDs in QBO files or by matching date, amount, and description in CSV files. This message means the upload worked the first time.
Fix: Go to Transactions → Bank transactions → For Review and check whether the transactions are already there. If you need to re-upload a corrected file for the same date range, you may need to exclude or delete the original transactions first.
2. Deposits showing as withdrawals (or vice versa)
This is an amount sign problem. QuickBooks expects debits as negative values and credits as positive, but many bank exports flip this convention. The column-mapping screen has an option to reverse the sign.
Fix: Return to the upload flow and look for the amount direction toggle on the mapping screen. For files with separate Credit and Debit columns, confirm each column is mapped to the correct field — swapping them causes the same symptom.
If the transactions are already in For Review with the wrong sign, exclude them, fix the file or mapping, and re-upload.
3. Fewer transactions imported than the file contains
Check the preview screen row count before clicking Import. If it is lower than expected, one of these is the likely cause:
- Header row: QuickBooks skipped the first row as a header but your file has two header rows, or the column-mapping picked the wrong row as the header.
- Blank or unrecognized dates: Rows with empty date cells or dates in an unexpected format are silently skipped.
- Date range overlap: Transactions that already exist in the account (matched by QuickBooks) may not appear in For Review.
- 350 KB file size cap: CSV uploads over 350 KB are truncated. Split the file into shorter date ranges and upload each separately.
Fix: Open the CSV in a spreadsheet, confirm all date cells are in a consistent format (MM/DD/YYYY or YYYY-MM-DD work reliably), remove extra header rows, and keep files under 350 KB.
4. “File format not supported”
QuickBooks Online's Upload from file flow accepts QBO (Web Connect), OFX, and CSV files. Common causes of this error:
- Uploading a PDF bank statement instead of an exported data file.
- Uploading an .xls or .xlsx Excel file instead of a saved-as-CSV.
- A QBO file with a corrupt or incomplete header — the
OFXHEADERblock must be intact.
Fix: Log in to your bank, navigate to the download or export section, and export in QBO, OFX, or CSV format. Do not open and re-save QBO files in Excel — this corrupts the format. If QuickBooks won't import the bank file even after re-exporting, open it in a plain text editor to confirm the format is intact before uploading again.
5. “We can't import your file right now”
This generic error usually means the file is malformed, oversized, or contains characters that break QuickBooks parsing.
Fix: Open the file in a plain text editor (not Excel). Look for unexpected characters, encoding issues (non-UTF-8 content), or a truncated file ending. If the file looks clean, reduce the date range to shrink file size and try again. Exporting a fresh copy directly from your bank often resolves the issue.
If your bank only provides PDF statements and no downloadable data file, a PDF converter is the alternative — see uploading transactions from PDF bank statements.
6. Transactions not showing up after upload
Uploaded transactions do not go directly into your register. They land in the For Review tab until you categorize and accept them.
Fix: Go to Transactions → Bank transactions, select the account, and click the For Review tab. Filter by the date range you uploaded. If the transactions are not there, the upload likely failed silently — repeat the upload and confirm the row count on the preview screen matches your file before clicking Import.
If transactions are present in For Review but not appearing in your register, you still need to accept them by clicking Add or matching them to existing transactions.
When the Source File Is the Problem
Many upload errors trace back to the exported file rather than QuickBooks itself. Banks export data in formats that are slightly inconsistent with what QuickBooks expects — extra columns, non-standard date formats, or mixed positive and negative values in a single Amount column.
If your bank only provides PDF statements and no direct CSV or QBO download, you cannot fix the source file — there is no source file to fix. In that case, a PDF-to-QBO converter reads the statement document and produces a QuickBooks Web Connect file directly, bypassing the column-mapping step and most of the errors above. See how Bank Parser converts PDF bank statements to QBO and why QBO files tend to import more cleanly than CSV files.
For catch-up bookkeeping projects where the client has years of PDF statements and the bank no longer provides direct downloads for that period, PDF conversion is often the only practical path to getting the data into QuickBooks without manual entry.
Frequently Asked Questions
Why does QuickBooks say “this file has already been imported”?
QuickBooks detects duplicate uploads using transaction IDs embedded in QBO files or by matching date-amount-description combinations in CSV files. If you see this message, the file was already uploaded successfully. Check the For Review tab or your register for those transactions before uploading again.
Why are my deposits showing as withdrawals in QuickBooks after upload?
This happens when the Amount column sign is inverted — debits are positive when QuickBooks expects them negative, or vice versa. Return to the column-mapping step and switch the amount direction. For CSV files with separate Credit and Debit columns, make sure each column is mapped to the correct field.
Why did QuickBooks import fewer transactions than my file contains?
The most common causes are: a header row counted as a data row, transactions whose dates fall outside the account's date range, rows with blank or unrecognized date formats, and the 350 KB per-file size limit for CSV uploads. Split large files into smaller date ranges and upload oldest first.
Why does QuickBooks say my file format is not supported?
QuickBooks Online accepts QBO (Web Connect), OFX, and CSV files from the Upload from file flow. Common causes: uploading a PDF instead of an exported file, a .xls or .xlsx Excel file instead of a CSV, or a QBO file with a corrupt header. Export the file from your bank in a supported format before uploading.
What does “We can't import your file right now” mean in QuickBooks?
This generic QuickBooks error usually means the file is malformed, too large, or contains characters that break parsing. Try opening the file in a text editor to check for unexpected characters, reduce the date range to make the file smaller, or export a fresh copy from your bank.
Why are uploaded transactions not showing up in QuickBooks after import?
Uploaded transactions land in the For Review tab, not directly in the register. Go to Transactions → Bank transactions → For Review and look for your date range. If nothing appears there either, the upload may have silently failed — repeat the upload and watch the row count on the preview screen.