Match the file format to how you're importing
QuickBooks accepts different file types depending on the path you take. QuickBooks Online supports CSV uploads for bank transactions, plus QBO (Web Connect) files. QuickBooks Desktop uses QBO files through Web Connect, and can import IIF for lists and some transactions. If you feed the wrong type into the wrong window, you get a generic upload failure.
If you have a CSV, use the manual upload option under the banking or transactions area. If you have a QBO file, use the Web Connect import path instead. Do not rename a CSV to .qbo or vice versa. Changing the extension does not change the file's internal structure, and QuickBooks will reject it or import garbage.
OFX and QFX files are close cousins of QBO. QuickBooks specifically expects the QBO variant, which includes an INTU.BID (bank ID) field. A plain OFX or QFX file from a source other than a supported bank may import in some tools but be refused by QuickBooks.
Fix CSV column and formatting problems
CSV is the most common source of errors because the layout is flexible. QuickBooks Online expects either a three-column format (date, description, amount) or a four-column format (date, description, credit, debit). During upload it asks you to map your columns. If mapping is wrong, amounts land in the wrong direction or the file is rejected.
Dates cause the most failures. QuickBooks reads the date format you select during import, so if your file uses DD/MM/YYYY but you leave it on MM/DD/YYYY, any day above 12 will error out or post to the wrong month. Pick the format that matches your actual data, and keep every row consistent.
Amounts must be plain numbers. Remove currency symbols, thousands separators that confuse the parser, and text like 'pending'. Use a minus sign or a separate debit column for money out. Delete blank rows, summary lines, running balances, and header rows above the real column titles. QuickBooks wants one clean header row followed by transaction rows only.
If the upload says the file is empty or has no valid transactions, open the CSV in a plain text editor. Look for stray characters, merged cells that shifted columns, or a file that was saved as something other than comma-separated values.
Handle duplicates and 'already imported' messages
QuickBooks tracks what it has imported. If you re-upload a file that overlaps a previous date range, it may flag transactions as duplicates or refuse the file entirely, saying the transactions already exist. This is a safeguard, not a bug.
To avoid overlap, note the date of your last successful import and start the next file the day after. If duplicates already landed in the For Review or banking feed, you can exclude or delete them there before they are added to the register. Once a transaction is matched and added to an account, removing it is more involved, so catch duplicates while they are still under review.
If a QBO file is rejected because QuickBooks says it was already imported, the file may carry the same date range or transaction IDs as a prior import. Trim the date range or use only new transactions to get a clean import.
Resolve QBO, Web Connect, and account-mapping errors
QBO files can fail with errors referencing the financial institution or a code like OL-301 or OL-393. These usually mean the bank ID inside the file, or the account it is trying to attach to, does not line up with what QuickBooks expects. Make sure you import the file into the correct account rather than letting QuickBooks guess.
A common Desktop issue is that Web Connect cannot associate the file with an account. When prompted, choose to create a new account or link to the existing one deliberately. If you link to the wrong account, transactions post to the wrong register and reconciling breaks.
If a file consistently fails and you cannot see anything wrong, convert your source statement into a clean, correctly formatted CSV and use the manual upload path. Rebuilding the file from the statement data often clears format-level errors that are impossible to diagnose from a vague message.
After any import, review the first and last few transactions before you add them. Confirm dates, signs, and amounts match the statement. It is far easier to fix a mapping mistake in the review stage than after everything is in the books.