When QuickBooks Online reports no transactions found in a file, it opened the file but couldn't pick out any rows it recognises as transactions. Check four things in order: the header row and column mapping, the date cells, how the file was saved, and whether the amount column holds numbers. Fix the first fault, then upload again.
Why does QuickBooks Online find no transactions in a full file?
QuickBooks Online finds no transactions in a full file when none of its rows pass the upload's reading rules. The file is not empty to you; it just doesn't look like a list of transactions to QuickBooks. Usually one problem affects every row at once, such as a missing date column or a header in the wrong place.
Intuit's guide to manually uploading transactions sets out what a transaction row needs. A CSV must have either three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit). Dates must use one format throughout, the file must be in English, and it must be 350 KB or less with no more than 1,000 lines.
A row that breaks any of those rules is not a transaction to the upload. When the rule broken is one that every row shares, the count of readable rows drops to zero.
Work through the checklist below in order. Each step takes a minute and clears the most likely cause before the next:
- Open the file in a plain text editor and confirm it has rows of data, not just headings.
- Check that the first line is the header and that the data starts on line two.
- Check that every date uses the same format, with no weekday in the cell.
- Check that the file was saved as a real CSV, in Windows CSV format on a Mac.
- Check that the amount, credit or debit cells hold plain numbers.
- If all of that passes, check that the bank export covers the dates you meant.
Header rows and mapping when QuickBooks finds no transactions
The header row is the first line of a CSV, holding the column names. QuickBooks uses it on the mapping screen, where you match each column in the file to a field. If the header sits lower down, or the columns are matched wrongly, QuickBooks reads the data in the wrong place and finds nothing usable.
Bank exports often put several lines above the real header: the account name, the statement period, an opening balance. QuickBooks treats the first line as headings, so that block pushes everything out of line. Delete every row above the column names, so the header is line one.
On the mapping screen, Intuit's article on common errors when importing bank transactions from a CSV gives the fix for wrong mapping: delete the columns you don't need, keep Date, Description and Amount, and rename the CSV's columns to match the QuickBooks titles. A file with eleven columns from a bank export gives the mapping screen eleven chances to go wrong. Three gives it almost none.
Here is a broken example, as it might arrive from a bank. The values are made up:
Account: Business Checking ...4417
Statement period: 03/01/2026 - 03/31/2026
Transaction Date,Post Date,Type,Description,Withdrawals,Deposits,Balance,Check No
Sat 03/14/2026,03/16/2026,DEBIT,HARDWARE STORE,$42.18,,"$9,318.27",
And the same file fixed:
Date,Description,Amount
03/16/2026,HARDWARE STORE,-42.18
The fixed version drops the two lines above the header, keeps one date column, moves to a single amount with money out negative, and strips the dollar sign. Every fix there removes one way for the upload to miss the row.
Could date cells hide every transaction from the upload?
Yes. A date cell hides its row when QuickBooks can't read it in the format you chose on the mapping screen. Intuit's guide asks for one date format across the file. When the format in the cells doesn't match the one you picked, every row fails the same way, and the upload can report it found nothing at all.
Three date faults affect a whole file at once:
- A weekday in the cell. Exports such as
Sat 03/14/2026add the day name. Intuit's guide to formatting CSV files for bank transactions says you need to remove the day of the week. - Dates stored as text in a mixed format. Some rows read
03/14/2026and others2026-03-14. Pick one, and convert the rest. - A format that doesn't match the mapping choice. A file written month first, mapped as day first, fails on any day over 12.
Intuit's common-errors article suggests setting the date column to Short Date in the spreadsheet so every cell takes the same form. After saving, open the CSV in a text editor and read three or four dates to confirm they look alike.
Which date column to keep matters too. Many exports carry both a transaction date and a posting date. Keep one. The posting date usually matches the bank statement and the balance, which makes reconciliation easier later.
File encoding, Mac exports and the "no transactions" upload
File encoding is the way a computer stores the letters in a text file. A CSV can look perfect in a spreadsheet and still be saved in a form the upload doesn't expect. Intuit's formatting guide gives one firm rule here: Mac users must save the file in Windows CSV format.
In Excel for Mac, the save dialog offers several CSV options. Choose the one labelled Windows Comma Separated. In Numbers, export to CSV and check the advanced options before saving. On any computer, a file saved as .xlsx or .numbers and renamed to .csv is still a spreadsheet inside. The upload won't find rows in it.
Two other signs of a saving problem:
- Everything in one column. Opened in a spreadsheet, the file shows each row as one long cell. The separator may be a semicolon or a tab instead of a comma, which happens when a computer is set to a region that uses commas for decimals.
- Odd characters at the start. A few symbols before the first header can come from the way the file was written. Retyping the header line in a plain text editor and saving again often clears it.
Intuit's common-errors article also suggests copying the CSV's contents into a blank spreadsheet to reveal hidden problems, then saving that copy as a fresh CSV. That resets formats and encoding in one move.
Desktop users have their own version of a file that won't go through. When a Web Connect import hangs rather than failing, the guide to QuickBooks Desktop freezing during a Web Connect import is the place to look.
An empty or one-sided amount column in the upload file
An amount column with nothing QuickBooks can read gives it dates without money, and a row without an amount is not a transaction. This happens when every amount carries a currency symbol or text, when the money sits in a column you didn't map, or when a four-column file has only one side filled in.
Intuit's common-errors article covers the first and last cases. For amounts with currency symbols or commas, open Format Cells on the amount column and change it from Currency to General. For a file with separate debit and credit columns where every row is money out, add one extra line with a positive amount, then untick it on the final review list before you confirm.
Intuit's formatting guide adds two small rules for a four-column file. The headers should read only "Credit" and "Debit," without the word "amount." And any zero in those columns should go, leaving the cell blank.
If the upload starts and then never finishes, that is a different problem from finding no transactions. The guide to a bank upload stuck in QuickBooks Online covers browser checks and splitting a file that is too big.
When the bank export really has no transactions in it
Sometimes the message is simply right. A bank export can contain headings and a balance but no transaction rows, because the period you chose had no posted activity or because the download came from the wrong account. Rebuilding that file by hand is wasted effort. Go back to the bank and download again.
Before you edit anything, count the rows under the header. If there are none, look at the export settings:
- The dates. A range that ends before the first transaction, or starts in the future, returns nothing.
- The account. Banks with several accounts on one login sometimes default to the first one in the list.
- Pending items. Transactions that haven't posted yet are often left out of exports until they do.
- The reach. Online downloads usually cover a limited history, so a range from two years ago may come back empty.
Choosing a QBO download instead of CSV sidesteps the header, date and amount problems above, because a QBO file needs no column mapping. The walk-through on how to download a QBO file from Chase shows a typical download screen, including the date range to pick. Most banks lay out the same choices in a similar way.
When the bank has stopped offering downloads for the months you need, a PDF statement is often what remains. SimpleBankConvert is being built to turn a PDF statement into a CSV or QBO file laid out the way QuickBooks Online expects. It has not opened yet; the get started page holds a place for you.