Home › Blog › QuickBooks › QuickBooks Online CSV format explained: 3-column and 4-column layouts
The exact QuickBooks Online CSV format explained, including the 3-column and 4-column layouts, date and amount rules, and mapping checks before upload.
By StatementVerified Editorial · November 5, 2026 · 7 min read · Filed under QuickBooks
QuickBooks Online accepts bank activity by CSV upload, but it accepts it on strict terms. The file must follow one of two layouts, the columns must contain exactly what the importer expects, and the first row must be headers the mapping screen can recognize. Most failed uploads are not mysterious. They are layout violations: an extra column, a running balance included out of helpfulness, amounts split the wrong way, or a file that mixes conventions halfway down. Understanding the two layouts precisely turns the import from trial and error into a routine preparation step.
This guide explains the 3-column and 4-column layouts, when to choose each one, the exact rules for dates, descriptions, and amounts in both, and the pre upload checks that catch the errors the importer either rejects outright or, more dangerously, accepts silently in the wrong direction. If you convert statements for import, build the file to this specification from the start rather than cleaning a generic spreadsheet into compliance at upload time.
The 3-column layout carries Date, Description, and Amount in that order, with one header row at the top and one transaction per row below it. The Amount column is signed: money into the account is positive and money out is negative for a bank account. That single signed column is what makes the layout compact and also what makes sign discipline essential. Every row must carry its sign explicitly. An unsigned amount will be read as positive, so an expense entered without its minus sign will import as income, and the upload itself will appear to succeed beautifully while the books absorb the error.
Choose the 3-column layout when your source provides a single amount per transaction, which is the common case for converted bank statements. Keep the file to exactly those three columns. Do not add a balance column, a check number column, or a category column hoping the importer will ignore them. Extra columns confuse the mapping screen and can shift assignments. If you need check numbers or categories for your own review, keep them in a separate workpaper copy and export a clean three column file for upload. The importer rewards minimalism: the closer the file is to the bare specification, the fewer decisions the mapping screen asks you to make.
The 4-column layout carries Date, Description, Credit, and Debit. Each transaction uses only one of the two money columns: a deposit fills Credit and leaves Debit empty, and a payment fills Debit and leaves Credit empty. That word empty is the rule people break most often. The unused cell must be truly blank, not zero. A zero in the unused cell, and especially zeroes in both money columns on some rows, can cause the importer to reject the row or misread the direction, because the file is telling the system the transaction is simultaneously a movement and not a movement. When you build this layout from a spreadsheet, audit it specifically for zeroes hiding in supposedly blank cells.
Choose the 4-column layout when your source naturally separates debits and credits, as many bank exports and some statement layouts do, and when the team reviewing the import finds two columns easier to proofread than signs. It is also the safer layout for handing a file to a client to review, because direction is visual rather than symbolic. Neither layout is more correct than the other. Consistency within the file is what matters. Never deliver a hybrid where some rows use a signed amount column and others use split columns, and never change layouts mid file at a page or month boundary during catch up work.
Dates must be in a single consistent format the importer can parse, written as plain dates without weekday names, time stamps, or text such as the word pending attached to them. Every row in the file should use the same format, because mixed formats invite silent misreading, especially where day and month can swap. Descriptions should be the full statement description, trimmed of line breaks and stray leading characters, but not shortened so aggressively that two different payees become indistinguishable. The importer does not categorize from description alone, yet your later review and rule matching depend on descriptions carrying the real payee information the statement provided.
Amounts must be plain numbers. Remove currency symbols, thousands separators are a nuanced point covered in depth in our amounts guide, accounting parentheses, and trailing minus signs before upload, and express direction only through the layout convention you chose: sign in the 3-column file, column choice in the 4-column file. A value like a fee shown in parentheses on the statement means money out, and in a 3-column file it becomes a negative plain number. Build a habit of summing your finished file and comparing the net total and the in and out subtotals to the statement totals before upload. That one comparison catches most direction errors while they are still free to fix.
At upload, QuickBooks Online shows a mapping screen where you confirm which file column is the date, which is the description, and which carries the amount or the credit and debit pair. Read it as a verification step rather than clicking through it. Confirm the date format selection matches the format actually in your file, because telling the importer the wrong format can swap day and month on every ambiguous row without any error message. Preview the first rows the screen displays and check that a known deposit appears as money in and a known fee appears as money out. That ten second preview has saved more imports than any other habit in this guide.
Also confirm you are importing into the correct bank account, especially in files with multiple accounts where a wrong destination import is tedious to reverse. Note the date range and row count the importer reports and compare them to your workpaper. If the count differs, stop. A short count means rows were skipped, often header or malformed rows, and proceeding would import a partial month that reconciles to nothing. Correct the file, reupload, and only proceed when the importer view of the file matches your verified view of the file exactly, in count, range, and direction.
The cleanest workflow produces the QuickBooks file directly from the verified conversion, rather than hand editing a generic spreadsheet. Start from a conversion that already ties to the statement balances, then shape a copy into the chosen layout: keep date, description, and amount, strip every other column, normalize the date format across all rows, and apply the sign or split column rule uniformly. Then run three final checks. First, no zeroes sit in blank money cells and no amount cell is empty. Second, no cell contains a symbol, letter, or parenthesis. Third, the file totals match the statement totals for money in, money out, and net movement.
Keep the verified source file, the shaped import file, and a note of the layout used together in the client workpapers. Months later, when a transaction is questioned, that trio lets you trace it from statement line to import row to register entry without ambiguity. It also makes catch up work dramatically faster, because a year of statements shaped by one consistent specification imports with one consistent mapping, instead of twelve slightly different files each demanding its own negotiation with the importer. Consistency is the real time saver in QuickBooks imports, far more than any single upload trick.
Use whichever matches your source and your review preference, applied consistently. The 3-column signed layout suits most converted statements. The 4-column split layout suits sources that already separate debits and credits. Both import correctly when their rules are followed exactly.
No. Upload only the layout columns: three or four. A balance column confuses mapping and can shift column assignments. Keep balances in your separate verification workpaper, where the running balance check belongs, and upload a clean minimal file.
Direction errors usually come from unsigned amounts in a 3-column file, zeroes in both money columns in a 4-column file, or a reversed mapping choice at upload. Preview a known deposit and a known fee on the mapping screen before importing, and compare file totals to statement totals.
QuickBooks · November 2, 2026
How QuickBooks Desktop imports bank data with QBO Web Connect files, why plain CSV does not work for banking, and how to prepare a clean import file.
QuickBooks · November 5, 2026
A post import checklist for QuickBooks before you reconcile the month, covering counts, duplicates, direction, transfers, and the closing balance proof.
QuickBooks · November 2, 2026
Fix QuickBooks Online amount import errors caused by currency symbols, commas, zeroes in cells, parentheses, and sign conventions, before you upload.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.