What Columns Does QuickBooks Need for a CSV Import? The Exact Format

QuickBooks Online reads a bank CSV in one of two shapes. Three columns: Date, Description, Amount, with money out written as a negative number. Or four columns: Date, Description, Credit, Debit, with both amounts written positive and the column itself deciding the direction. Dates have to be consistent across the whole file, amounts have to be plain numbers with no dollar signs and no thousands commas, and the file has to stay under Intuit's 350 KB upload size. Everything else your bank puts in the export (running balance, category, card number, memo, status) has to come out before you upload.

What columns does QuickBooks need for a CSV import?

Three at minimum: Date, Description, and Amount. QuickBooks Online also accepts a four column layout that splits the money into separate Credit and Debit columns instead of one signed Amount. Those are the two documented layouts. Use one header row, plain header words, and make sure every row underneath carries a real date.

The three column format

Date, Description, Amount. Purchases, checks, and withdrawals are negative. Deposits, refunds, and payments received are positive. This is the layout I reach for whenever the source file already gives me a single signed amount column, which covers most credit card downloads and most checking activity exports. It also has the fewest failure modes, because there's no chance of a withdrawal landing in the wrong money column.

The four column format

Date, Description, Credit, Debit. Both money columns hold positive numbers and only one of them is filled on any given row. Two details trip people up here. The headers have to read exactly Credit and Debit, not Credit Amount and Debit Amount. And any cell that would hold a zero should be left blank instead, since a zero sitting on both sides of a row muddies the direction of the transaction.

Does QuickBooks Online accept a CSV with five columns?

Intuit documents the three and four column layouts only. The upload flow does include a mapping step where you tell QuickBooks which column holds the date, the description, and the amount, and a file with one extra column sometimes goes through. Extra columns are also the most common cause of the "some info may be missing from your file" error, so trimming down first is the reliable move.

What date format does QuickBooks need in a CSV?

MM/DD/YYYY is the safest choice for a US file. QuickBooks Online also accepts MM-DD-YYYY, YYYY-MM-DD, and DD/MM/YYYY, but every row has to use the same one. Excel is the usual culprit here: it will display a date one way while storing it another, so set the entire column to a single format before saving.

How many transactions can you upload in one CSV?

Intuit's published cap is 350 KB per CSV file, which typically works out to somewhere around a thousand rows depending on how long the descriptions run. A full year of an active operating account will usually exceed it. Split the export by month or by quarter, then upload the pieces oldest first so the running balance in QuickBooks stays sensible.

Why bank exports almost never match the format

Banks build their downloads for their own screens and for personal finance software, not for the QuickBooks upload wizard. So you get a posted date and a transaction date, a merchant category the bank guessed at, a status column, a truncated card number, sometimes a running balance, and occasionally no header row at all. Wells Fargo's comma delimited download is the clearest example: it arrives with no header row, so you have to add one before QuickBooks will look at it. None of that is broken. It just has to be reduced to the three or four columns QuickBooks reads.

If you work across several issuers, it pays to keep a cheat sheet of exactly what each one hands you, which is what the credit card CSV export columns reference is for. The layouts change rarely, but they do change, and a mapping template built on last year's column order will silently put the wrong field in the wrong place.

How to map an issuer file into the QuickBooks shape

The work is mechanical once you know the target. Same five steps every time:

• Delete every column QuickBooks doesn't read: category, type, status, card number, memo, balance, and the second date column.
• Rename the headers to exactly Date, Description, Amount, or Date, Description, Credit, Debit.
• Fix the sign. On a card file where purchases are positive, multiply the amount column by negative one and paste the result back as values.
• Clean the numbers. Strip dollar signs, strip thousands commas, format the column as Number rather than Currency or Accounting, and delete parentheses used for negatives.
• Sort by date ascending, delete trailing blank rows, and save as CSV UTF-8.

For card accounts specifically, watch the direction convention before you upload. In QuickBooks a credit card account is a liability, so a purchase increases the balance owed and a payment reduces it. Getting that backwards is the reason a freshly imported card register reconciles to the exact opposite of the statement. The step by step for card files lives on the import credit card transactions into QuickBooks page, and the issuer specific quirks are covered on pages like convert a Chase credit card statement to Excel.

Common QuickBooks CSV import errors and what fixes them

• "Some info may be missing from your file." Usually extra columns, a blank required cell, or empty rows at the bottom of the sheet. Trim to three or four columns and delete everything below the last transaction.
• Dates come in wrong or the file is rejected. Mixed date formats in one column. Reformat the whole column to MM/DD/YYYY and re-save.
• Amounts import as zero or as text. Currency symbols, thousands separators, or numbers stored as text. Clean the column and set it to Number.
• Everything imports with the sign reversed. The issuer wrote purchases positive. Multiply by negative one, or move to the four column layout and let the column carry the direction.
• The file is too large. Split by month or quarter to stay under 350 KB per upload.
• Strange characters in descriptions. Re-save the file as CSV UTF-8 rather than the default encoding.

What if you only have PDF statements?

Plenty of accounts give you no usable download at all: closed accounts, accounts where online history has aged out, or client statements that arrive as email attachments. In that case the PDF is the source of record, and the job is to turn it into the same three or four columns. A PDF bank statement to Excel converter does that directly, and a QuickBooks bank statement converter can output the file already shaped for the upload wizard. If you'd rather skip the CSV step entirely, the QBO file format imports as a bank feed style file and carries transaction IDs, which cuts down on duplicates.

One more thing worth sorting out before you import rather than after: coding. A clean CSV still lands in the For Review queue with no accounts assigned, and if you're processing hundreds of card charges a month it's usually cheaper to categorize every card charge automatically at the source than to click through them in the banking tab. Either way, the import format stays the same.

The short version

Three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit). Consistent dates, ideally MM/DD/YYYY. Plain numbers with no symbols or commas. One header row, no blank rows, under 350 KB, saved as CSV UTF-8. Every bank export needs trimming to get there, and the only part that really requires thought is the sign convention, because that's the one mistake that imports cleanly and reconciles wrong.