Last updated August 2026. To import bank transactions into QuickBooks Online, put them in a CSV file with either three columns (Date, Description, Amount) or four columns (Date, Description, Credit, Debit), then go to Transactions > Bank transactions, choose the account, and upload. QuickBooks also accepts QBO, QFX, and OFX files. It does not accept PDF or Excel workbooks, which is why a statement downloaded from your bank usually needs converting first.
Most of the difficulty here is not the upload. It is the twenty minutes before the upload, spent working out why a file that looks perfectly reasonable keeps getting refused. This walks through the format QuickBooks actually wants, the errors that come up most, and the two situations where importing is the wrong answer entirely.
How do I import bank transactions into QuickBooks Online?
Sign in and go to Transactions, then Bank transactions. Select Link account if the bank is not connected yet, or use the dropdown next to Update and choose File upload. Pick your CSV, tell QuickBooks which account the transactions belong to, then map your columns to its fields on the next screen. Review the list it shows you and confirm.
Two things to know before you start. QuickBooks remembers your column mapping for next time, so getting it right once saves work every month afterwards. And nothing posts to your books at upload: imported transactions land in the For review tab, where you categorize and accept them. Until you do that, they are not in your ledger and a bad import is easy to undo.
What file formats does QuickBooks Online accept?
Four, and the one people arrive with is usually not among them.
| Format | Accepted | When you would use it |
|---|---|---|
| CSV | Yes | The general purpose route. Any statement can be shaped into a CSV. |
| QBO | Yes | Web Connect files, offered as a download by some US banks. |
| QFX | Yes | Quicken's exchange format, offered by some banks alongside QBO. |
| OFX | Yes | The open standard the other two are built on. |
| No | Convert it to CSV first. This is what most statements arrive as. | |
| XLSX or XLS | No | Save the sheet as CSV from Excel before uploading. |
If your bank offers a QBO or QFX download, take it. Those formats carry the account and transaction identifiers QuickBooks uses to recognize duplicates, so they import more cleanly than a CSV you assembled yourself. CSV is the fallback, and it is a perfectly good one.
How do I format the CSV file for QuickBooks?
QuickBooks takes one of two layouts, and nothing else. Three columns puts every transaction in a single Amount column, with withdrawals written as negatives. Four columns keeps money in and money out separate, which is how most bank statements print and usually the easier one to produce.
| Layout | Columns | How withdrawals appear |
|---|---|---|
| Three column | Date, Description, Amount | Negative numbers in the Amount column |
| Four column | Date, Description, Credit, Debit | Positive numbers in their own Debit column |
Beyond the columns themselves, five rules decide whether the file goes through:
- No currency symbols or thousands separators. An amount has to read
1250.00, not$1,250.00. This is the single most common reason an upload fails. - One date format for the whole column. Pick one and keep it. Mixed formats in one file either get rejected or, worse, map to the wrong year silently.
- Ordinary header names. Date, Description, Amount, Credit, and Debit map without argument. Whatever shorthand the bank printed will not.
- Header on the first row. Delete the letterhead, the account summary block, the page footers, and any running balance column the statement carried.
- Watch the file size. QuickBooks caps how big an upload can be, so a full year of a busy account may need splitting into a few files. Intuit's help article carries the current limit and is worth checking there rather than on any third party page.
Why is QuickBooks not accepting my CSV file?
Work through these in order. In practice the first two account for the large majority of failures.
| Symptom | Cause | Fix |
|---|---|---|
| Upload rejected with no useful detail | Currency symbols or commas inside the amounts | Format the amount columns as plain numbers with two decimals and no symbol |
| Error about the number of columns | An extra column such as running balance or check number | Delete everything except the three or four columns allowed |
| Dates land in the wrong year | Mixed or ambiguous date formats down the column | Reformat the whole column at once, then confirm January and December both look right |
| Mapping screen shows blank fields | The header row is not the first row of the file | Remove the bank letterhead and summary rows above the headers |
| Every amount imports as a deposit | Debits lost their negative sign or their own column | Switch to the four column layout so credits and debits stay separate |
| File will not upload at all | Over the size limit | Split it by month or quarter and upload in date order |
If amounts look correct on screen but still fail, the values are probably text rather than numbers. Select the column and check whether Excel shows a sum in the status bar. If it does not, the cells are text and still carry whatever formatting came with them. Our guide to converting text to numbers in Excel covers the repair, and the same trick fixes a date column that refuses to sort chronologically.
What if my bank statement is only a PDF?
This is the usual situation for anything that is not the current month. Convert the statement to CSV, tidy it to the three or four columns above, and upload that. A PDF to Excel converter set up for QuickBooks pulls the transaction table off every page as one continuous list with debits and credits still in separate columns, which is most of the formatting work done for you. Scanned statements need a converter with OCR, because there is no text in the file to read otherwise.
Copying and pasting from the PDF is the approach people try first and it rarely survives contact with a real statement: everything lands in one column, the debit and credit split disappears, and page headers end up interleaved with transactions. Retyping works but introduces errors that only surface at reconciliation.
One variation worth knowing about. If your workflow specifically needs a Web Connect file rather than a CSV, for instance because you are on a QuickBooks Desktop version that expects one, you need a tool that writes the statement out as a QBO file instead. It is a different output format, not a different quality of conversion, and CSV is fine for QuickBooks Online.
How do I import bank transactions into QuickBooks Desktop?
Desktop uses Web Connect rather than the browser upload. Go to Banking, then Bank Feeds, then Import Web Connect File, and select your QBO file. Desktop does not take a plain CSV through that path, which is the main practical difference from QuickBooks Online and the reason Desktop users end up looking for a QBO converter rather than a CSV one.
Third party importer tools add CSV support to Desktop, and plenty of firms use them. If you are choosing between the two products for a client with years of PDF statements to load, QuickBooks Online's native CSV upload is the shorter path.
How far back can I import bank transactions?
There is no limit on the age of transactions in a file you upload yourself. You can import 2019 statements today. The limit people run into belongs to the live bank connection, which typically backfills only the last ninety days or so when you first link an account, with the exact window varying by bank.
That gap is why catch up bookkeeping almost always involves file uploads. Connect the account for the current month, then import the history from statements. Do it in date order and reconcile each month before moving to the next, because an error found in January takes five minutes and the same error found in December means unpicking eleven months of categorization.
How do I avoid duplicate transactions?
QuickBooks catches some duplicates on its own, but it is much better at it with QBO and QFX files, which carry unique transaction identifiers, than with a CSV that does not. When you are uploading CSVs, assume the responsibility is yours.
Two habits prevent nearly all of it. First, note the exact date range in each file and never let two files overlap, which is easy to do accidentally when a statement period runs from the fifteenth to the fifteenth. Second, check the last few transactions already in the For review tab before you upload the next file, and start the new file the day after the last one you accepted. If duplicates do slip through, exclude them from the For review tab rather than deleting them after they post, which is a much smaller job.
The short version
QuickBooks Online imports CSV, QBO, QFX, and OFX, never PDF or Excel. Shape the data as Date, Description, Amount, or Date, Description, Credit, Debit. Strip currency symbols and commas from the numbers, use one date format throughout, put the header on row one, and upload under Transactions and then Bank transactions. Use the live bank feed for the current month and file uploads for everything older than the connection reaches. And total the credits and debits against the statement before you upload, because catching a missing transaction in a spreadsheet takes seconds and catching it during a reconciliation takes an afternoon.
Once the transactions are in, the bank reconciliation walkthrough covers tying the imported month back to the statement, and the bank statement converter handles the PDFs that started all this.