QuickBooks Online Advanced Import Bank Transactions: Convert Bank CSV to QBO Files

Yes. QuickBooks Online Advanced accepts bank transactions two ways, through a connected bank feed or through a manual upload. Intuit's accepted formats for a transaction list are QBO, QFX, or CSV, with PDF and image statements handled separately through side by side review. The upload path is the standard one: All apps, then Accounting, then Bank transactions, then the Link account dropdown and Upload from file. Some accounts still see the older Transactions then Bank transactions route, and both lead to the same uploader.

No. Spreadsheet Sync is limited to a defined set of transaction types, and bank transactions are not among them. Intuit's own documentation lists the supported set as journal entries, invoice and bills, credit memo, vendor credit, expenses and sales receipts, estimates, and purchase orders. Bank feed activity is handled entirely through the Bank transactions screen, not through the spreadsheet add-in.

This is the single most expensive misunderstanding on Advanced, because Spreadsheet Sync is one of the features people upgrade for. It is genuinely useful for what it covers. You can pull a trial balance, a profit and loss, a balance sheet or an A/P aging summary into Excel, edit invoices and bills in bulk, and push them back. None of that touches the banking feed. If your goal is to get a year of checking account activity into the register, Spreadsheet Sync is the wrong door.

The published limit is up to 1,000 lines per upload, each line containing one transaction, with the file at 350 KB or less. Both figures come from Intuit's manual upload documentation and neither is tied to a plan. An account with three years of activity on a busy operating account will exceed 1,000 lines inside a single quarter, so the constraint arrives long before the volume feels large.

No. The 1,000 line and 350 KB limits are properties of the bank transactions uploader, not of the subscription tier, and Intuit publishes them without any plan qualifier. Moving from Plus to Advanced buys more users, fixed assets, custom roles, deeper reporting and the Excel add-in. It does not buy a larger bank import. If a sales conversation or a forum answer suggested that upgrading would fix a failing import, that is worth checking before the purchase order goes through.

Almost always the file, not the plan. Intuit requires the transaction list to arrive as 3 columns (Date, Description, Amount) or 4 columns (Date, Description, Credit, Debit), in English, under 350 KB, and at or below 1,000 lines. Bank exports rarely arrive that way. They carry running balances, check numbers, posting and transaction dates, category guesses, and reference columns the importer has no field for.

Intuit's own preparation notes cover several traps worth knowing: remove the word amount from Credit and Debit headers, leave cells that contain only a zero blank rather than filled, strip numbers out of the Description field, and split the date from the day of the week if your bank combines them into one cell. Each of those is a silent failure rather than a clear error message, which is why an import can appear to succeed and still be wrong.

Declare the format your file actually uses, and be careful which help article you follow. The Intuit CSV formatting article that surfaces most often in search is the global edition, and it recommends DD/MM/YYYY. In a US company file that is wrong, and the damage is subtle: only the 1st through the 12th of each month are ambiguous, so those dates mispost while everything from the 13th onward looks correct. A reconciliation that is off by a handful of transactions scattered across a year usually traces back to exactly this.

Two Excel behaviors compound it. Two digit years resolve as 00 to 29 meaning 2000 to 2029 and 30 to 99 meaning 1930 to 1999, and Windows Excel defaults to the 1900 date system while Mac historically used 1904, a four year and one day shift. Normalizing dates before the file reaches QuickBooks removes the whole class of problem, which is what the conversion step above does.

Not through a newly connected feed. A fresh bank connection commonly pulls only about 90 days, and that is a bank side limit rather than a QuickBooks setting, so Advanced does not extend it. Anything older has to come in as a file. Most US banks will export a longer window on request: Chase account activity reaches roughly 24 months, TD online banking shows about 18 to 24 months, and American Express covers recent activity plus the past six billing statements. Download the older range as CSV, convert it, and upload the periods in order.

1. Export the full range from the bank. Pull the entire period you need as CSV or Excel in one download if the bank allows it. It is easier to split a large export than to stitch twelve small ones together.

2. Convert to QBO, split by period. Upload the export here and convert it. Keep each resulting file inside the 350 KB and 1,000 line ceilings, which for most operating accounts means monthly or quarterly files.

3. Upload oldest first. Go to Bank transactions, choose the account, and upload from file. Working forward in time keeps the running balance readable while you review.

4. Reconcile period by period. Do not wait until all twelve months are in. Reconciling each period as it lands means a discrepancy points at one month rather than a year.

For a transaction list, Intuit accepts QBO, QFX, or CSV. Statements can also be uploaded as PDF or an image such as JPG, PNG or HEIC for side by side review. QBO is the Web Connect format, so a QBO file lands in the bank feed review queue as though the bank had delivered it. That matters more than it sounds: the file already declares which field is the date, which is the description and which is the amount, so there is no mapping step to get wrong.

It gives QuickBooks something to work with, which a CSV does not. Every OFX and QBO transaction carries a FITID, an identifier that is unique within the account and never reused. QuickBooks skips FITIDs it has already seen, and it remembers them even after you delete the transaction. A CSV has no transaction identifier at all, so re-uploading an overlapping month creates a second copy of every row.

On this site, unique transaction IDs are part of the Plus plan. If your work involves reimporting corrected periods, or several people touching the same company file, that is the feature that stops a cleanup from becoming a bigger cleanup.

Not in the sense people usually mean. Advanced does have batch tools, including batch invoicing and batch reclassification, and those are real time savers for work already in the ledger. Bank feed activity is different. It arrives through the banking screen and is accepted, matched or excluded there. There is no batch entry screen that takes a spreadsheet of bank rows and posts them to the register, which is why the file upload path is the one that matters.

Because bank transactions cannot be uploaded into a subaccount in QuickBooks Online. This applies to every plan including Advanced. The workaround is straightforward: import to the parent account, then reclassify the transactions to the subaccount once they are in. Advanced makes the second half of that easier than lower tiers do, since batch reclassification is available.

If it holds more than 1,000 transactions or weighs more than 350 KB, yes. The question is who does the splitting. Doing it by hand in Excel means cutting rows at a boundary you choose, saving each piece, and hoping no header row or trailing blank slipped through, repeated for every account and every period. Converting instead produces files already shaped for the uploader, with the date and amount handling settled at the same time.

There is a reconciliation benefit too. When a converted file is built per period, the totals for that period are checked against the source before you export, so a missing row shows up before it becomes a reconciliation difference three months later.

Yes, for what it is scoped to. Reporting is the strongest case: trial balance, profit and loss, balance sheet, statement of cash flows and A/P aging pulled into Excel on demand, with the formatting you actually want. Bulk edits to invoices and bills are the second. It is available on QuickBooks Online Advanced, QuickBooks Online Accountant and Intuit Enterprise Suite, and on Advanced and Accountant it works with Excel specifically. Just do not plan a bank import around it.

Every conversion adds up the transactions it parsed and checks that total against the source file before you export, so a dropped or doubled row surfaces at conversion time rather than at reconciliation. The output is a valid OFX 1.02 file with Web Connect headers, not a renamed spreadsheet, which is why QuickBooks Online and Desktop both accept it as a standard bank feed file.

Signs are worth a second of attention on credit card accounts, because the meaning flips: on a card, a purchase is negative and a payment positive, the opposite of a checking account. If a reconciliation ends up out by exactly twice a transaction, that is the signature of a sign flip. Out by an amount that divides evenly by nine usually means transposed digits.

Compare it to the hour rather than the license. A controller splitting a year of exports across four accounts by hand, redoing the column mapping on each upload and then chasing the periods that misposted, is spending a working day or more per company file. You can convert three files without an account to see whether the output loads cleanly into your Advanced company before deciding anything.

Starter suits a single company file with steady monthly volume. Plus adds multi-currency, conversion history and the unique transaction IDs that stop reimports from duplicating. Pro adds unlimited conversions and API access, which is the tier that makes sense when the imports are part of a repeatable month end rather than a one off catch-up.