QuickBooks: "Some info may be missing from your file"
The full message is "Some info may be missing from your file. Double-check that your file is complete and try uploading again." It is QuickBooks' catch-all for a CSV it could not parse, and it never tells you which row or column was the problem. Below is what actually causes it, in the order worth checking.
🔒 In a hurry? Drop your CSV into the converter — it fixes every item on this list automatically, in your browser, without uploading your transactions anywhere.
The eight usual causes
1. The file is bigger than 350 KB
This is the single most common cause and the least obvious, because the message says nothing about size. QuickBooks Online rejects bank CSV uploads over 350 KB. A year of transactions from a busy current account passes that easily. Split the export into shorter date ranges — quarter by quarter, or month by month — and upload them one at a time.
2. Blank rows, or a preamble above the headers
Most banks put something before the actual data: an account number, an address block, a "Statement period" line, or simply an empty row. QuickBooks expects the header row to be the first row. Delete everything above it, and delete any blank rows inside or below the data.
3. Currency symbols and thousands separators in the amount
Amounts must be plain numbers. £1,234.56, $1,234.56 and 1 234,56 all break the parse. In Excel, select the amount column, right-click, choose Format Cells and change it from Currency to General. Watch for trailing minus signs (120.00-), parentheses for negatives ((120.00)) and CR/DR suffixes — all are common in bank exports and none of them are valid here.
4. Mixed or ambiguous date formats
Every date in the column has to be in the same format, and it has to match the format you pick at the mapping step. The trap is a column where some rows are text and some are real dates, which happens constantly after opening a bank CSV in Excel and saving it again. Select the date column and set the Number dropdown to Short Date. If your data could read either way — 03/04/2026 is 3 April or March 4 depending on who exported it — decide which it is before you upload, because QuickBooks will not ask twice.
5. Special characters in the description
Accented letters, em-dashes, curly quotes and stray control characters in the bank description can stop the import. They usually arrive via a non-UTF-8 export. Find and replace them, or re-save the file as UTF-8 CSV.
6. Zeroes where the cell should be empty
In a four-column file, a row should have a number in either the credit column or the debit column, not 0 in the other one. Clear those cells rather than filling them with zero.
7. A debit/credit file with only money going out
This one is genuinely strange, and it is documented by Intuit. If you use the four-column debit/credit layout and the period contains only outgoing transactions, the upload fails. The official workaround is to add one dummy row with a positive amount, then untick it on the final review screen before you confirm.
8. You are uploading to a subaccount
QuickBooks Online will not import a CSV directly into a subaccount. Either connect that account to the bank feed, or enter the transactions in the parent account.
What the file has to look like
QuickBooks accepts two shapes. Three columns:
Date,Description,Amount
01/04/2026,DIRECT DEBIT ACME LTD,-82.40
02/04/2026,SALARY,2150.00Or four columns, splitting the money in and money out:
Date,Description,Credit,Debit
01/04/2026,DIRECT DEBIT ACME LTD,,82.40
02/04/2026,SALARY,2150.00,Use exactly Amount, Credit and Debit as the money headers — not "Amount (GBP)" or "Debit amount". Delete every column you do not need; extra columns are a frequent cause of a bad mapping. On a Mac, save as Windows CSV, not the default Mac CSV.
A credit card export often has its signs the other way round from what you expect, because a payment reduces what you owe. Check the first few rows after import rather than assuming.
If it still will not go in, convert to QBO instead
When a CSV keeps failing for no visible reason, the standard fix is to stop fighting the CSV and hand QuickBooks a .QBO Web Connect file instead. QBO is a structured format with explicit fields, so there is nothing left for QuickBooks to guess at or misparse.
QBOKit reads the file in your browser, works out the columns, normalises the dates and amounts, strips what QuickBooks chokes on, and gives you back a .QBO, .OFX, .QIF or a cleaned-up CSV. Your transactions are never uploaded to us.