Home › Guides › QuickBooks Online Bank Upload Errors: A File Checklist
QuickBooks Online Bank Upload Errors: A File Checklist
For a rejected QuickBooks Online bank upload, check the file type, size, transaction count, CSV columns, date format and amount mapping before retrying. Intuit documents a 350 KB file limit and up to 1,000 transaction lines per upload. Test only after checking whether an earlier attempt already imported any lines.
Updated November 6, 2026
Make sure this is the Online workflow
This checklist is for QuickBooks Online → Bank transactions → Upload from file. If you are using QuickBooks Desktop and see “QuickBooks found an error. We can't read the file”, follow the separate Web Connect guide below. Desktop's financial-institution validation is not a CSV column-mapping problem.
Diagnose the stage where the upload stops
| Stage | Inspect first | Next action |
|---|---|---|
| File cannot be selected or read | Actual file extension and export type | Download a supported transaction file; renaming PDF to CSV does not convert it |
| Size or line-limit warning | Bytes and number of transaction rows | Split into smaller non-overlapping periods |
| Column mapping fails | Three-column or four-column layout and a single header row | Prepare a clean transaction-only copy |
| Preview dates are wrong | Actual date strings versus selected format | Normalise dates and select the matching convention |
| Money in/out is reversed | Signed Amount or separate-column mapping | Check a known payment and deposit before proceeding |
| Nothing new appears | Selected account, selected rows and prior imports | Inspect existing data rather than repeatedly uploading |
1. Check the file rather than its name
A CSV must contain comma-separated transaction data, not a PDF, HTML sign-in page or Excel workbook with a new extension. Intuit's transaction-list instructions suggest QBO and also describe CSV and other bank export formats. When possible, download the correct export directly from the bank. If your bank supplies only a PDF for the period you need, extract the transactions into a real import format.
2. Reduce the file safely
Intuit specifies files in English of 350 KB or less and up to 1,000 transaction lines per upload. Work by statement month or another clearly recorded date range. Keep a batch log with account, start date, end date and imported row count. Do not split by randomly removing rows or copy an opening balance row into every batch.
3. Clean the CSV structure
Use Date, Description, Amount, or Date, Description, Credit, Debit. Remove title lines, summary totals and repeated page headers. Leave unused amount cells blank; Intuit asks you to remove zero-only amount cells and the word “amount” from Credit/Debit headings. Preserve a separate original copy for audit evidence.
Keep numeric amounts as plain decimals. In a three-column bank file, a payment is negative and a deposit positive. Do not use a global “remove punctuation” replacement: it can destroy decimal points and minus signs. Correct problematic text fields separately from numeric fields.
4. Verify the preview before confirming
Choose the actual bank or credit card account. Map the appropriate number of amount columns, then choose the date convention. Check the earliest row, latest row, one payment and one receipt. If a previous attempt reached the confirmation screen, inspect the account's imported lines before retrying the full month.
5. Decide whether to change format or contact support
In Online, a clean three-column CSV is an alternative when a QBO file is refused. This is not a guarantee that every file or account configuration will import. If a clean, small file still fails, record the exact error message, file type, account type and step where it occurs, and contact Intuit through its official support channels. Do not include private statement details in a public community post.
After a successful upload, match or categorise the imported lines and reconcile the account. A file accepted by QuickBooks can still contain a missing transaction, an incorrect date or the wrong sign.
From a PDF to reviewed transaction data
If the source is a PDF, review it in CSVLedger and export QBO or QuickBooks CSV. Check the output before uploading it to your books.
Open the converter → · Plans and limits · How balance checks work
Conversion runs in your browser; statement files are not uploaded to CSVLedger. A balance check helps identify extraction issues, but does not replace review or accounting reconciliation.
Frequently asked questions
Can I rename a PDF to CSV?
No. Changing the filename does not extract transaction data or create a valid CSV.
Will a CSV fix every QBO file error?
No. A properly formatted CSV is an alternative in QuickBooks Online, but account settings, invalid data or other problems may still need attention.
Does this checklist apply to QuickBooks Desktop?
No. Desktop Web Connect uses QBO files and has separate version, sign-in and financial-institution requirements.
Related guides
- QuickBooks Online CSV Format: 3 Columns vs 4 Columns
- Fix QuickBooks CSV Date Format Errors Before Importing
- Fix “QuickBooks Can’t Read the File” in Desktop Web Connect
Sources and scope
Based on official help documentation reviewed through search results on November 6, 2026. Menus, regional availability and product requirements can change; use the current official instructions if your screen differs. Examples are fictional. These instructions are documentation-based, not a claim of a completed live import test.