How to import a .qbo file into QuickBooks Online

A .qbo file is the quickest way to get a month of bank or card transactions into QuickBooks Online when the bank feed cannot do it: no column mapping, no date-format question, and a transaction ID on every row so a second upload does not double anything. This guide covers one job only, taking a .qbo you already have and getting it accepted. The facts were checked against Intuit's help pages in September 2026; screen labels drift between regions, so a nearby name is normally the same screen.

What a .qbo file is

Underneath, a .qbo is an OFX file: a sign-on block, an account block and one STMTTRN record per transaction with a posting date, a signed amount, a payee and a FITID. What makes it a .qbo rather than a plain .ofx is an INTU.BID element in the sign-on block, Intuit's number for the institution that produced the file. QuickBooks Online reads the account block to work out which account the file describes, and it reads the FITID on each row to decide whether it has seen that transaction before.

Both QuickBooks products accept the format. Desktop brings it in through Bank Feeds as a Web Connect file and checks the institution id against Intuit's directory; QuickBooks Online takes it through the manual upload on a bank account and is less strict about the id, though it still refuses a file whose structure is wrong. Because the file names the account and carries its own ids, there is no mapping step at all: you pick the QuickBooks account the file belongs to and the transactions land in For Review.

Where the file comes from

Most US banks, and a fair number elsewhere, have a QuickBooks or Web Connect option on the download menu. It usually sits on the account activity page rather than with the statements, and it covers a limited window, somewhere between the last 90 days and the last two years depending on the bank. For a recent month that download is the file to use.

When the bank offers nothing, when the month you need is older than the window, or when all you were given is the statement PDF, the file has to be produced from the statement instead. Bank statement to QuickBooks reads the PDF, confirms that the printed opening balance plus deposits minus withdrawals lands on the printed closing balance, and writes the .qbo with the INTU.BID QuickBooks wants and a FITID derived from each row. A CSV from the bank can go the same way through the free CSV to QBO tool, which runs in your browser and does not upload anything. Either way, open the result in the QBO checker before you try QuickBooks with it; a structural fault found there costs a minute, the same fault found by QuickBooks costs a failed import and a vague message.

Uploading the file, step by step

1. In QuickBooks Online, open Transactions (some regions label the menu Accounting) and choose Bank transactions.
2. If the account already has a tile at the top of the page, select it. Then open the Link account dropdown and pick Upload from file. An account that has never been connected shows Upload from file directly, or a link offering to upload transactions manually.
3. Drag the .qbo onto the upload area or browse to it. The same screen accepts .qfx and .ofx files, so a Quicken download from the bank can go in here too.
4. Choose the QuickBooks account the transactions belong to. If the account is new, create it from this screen rather than afterwards, and make it a bank account for a current or savings file and a credit card account for a card file.
5. Continue. There is no column step for a .qbo, so QuickBooks goes straight to importing and reports how many transactions it brought in.
6. Open the For Review tab for that account. Nothing has reached the books yet; the next section is where that happens.

If the bank's file and a converted file both exist for the same month, import one of them, not both. Their FITIDs will differ, so QuickBooks would treat the second file as new transactions.

What happens in For Review

For Review is a holding area. Each line can be matched to a transaction you already recorded (a bill payment, a cheque, a transfer), added as a new transaction with the payee and category you set, or excluded so it never posts. Bank rules apply here as well: a payee string that matches a rule arrives pre-coded, which is worth setting up before you bring in a long run of history.

Duplicate detection works on the FITID. QuickBooks records every id it has added for an account, and a later upload containing an id it already holds is skipped without comment. That is what makes overlapping files safe when they come from the same source, and it is also why a deleted transaction does not come back when you re-import the same file: the id is still remembered. To restore one, enter it by hand or change its FITID in the file first.

Before accepting anything, check two numbers. The statement says how many debits and credits it holds; the For Review count for that period should agree. Then total the imported money in and money out against the statement summary. A difference means a row is missing, doubled or has the wrong sign, and it is far easier to find now than after the month is reconciled. The reconciliation guide covers tracking down the row.

What each error means

• "We can't read the file you sent." The file is not valid OFX underneath, or the header is damaged: a missing header line, a tag QuickBooks does not know, a date not written as YYYYMMDD, an amount carrying a currency symbol, or a raw ampersand inside a payee name. Run the file through the QBO checker, which lists each problem with a line number, then fix the file or ask the bank for a fresh download.
• The file wants to create a new account. The account number in the file does not match the one QuickBooks has on record for the account you chose. Pick the existing account when QuickBooks asks instead of letting it create another one; a second account for the same bank is the most common way books end up with a phantom balance.
• "This file has already been imported." Every FITID in the file is one QuickBooks has already added. If the transactions are genuinely there, nothing is wrong. If you deleted them and want them back, the ids need to change or the transactions need to be typed in.
• Deposits arrive as payments, or the other way round. The sign on TRNAMT is reversed. QuickBooks uses the sign, not the TRNTYPE label, and money out must be negative. For a card file, purchases are negative and payments positive, and the file must use the credit card message set or QuickBooks will insist on a bank account.
• A file that imports but lands in the wrong account was linked to that account by an earlier upload. Upload again and choose the right account when asked.

File size and splitting

Intuit's published limit for manual uploads, 350 KB and at most 1,000 lines per file, is stated in its help article on CSV uploads. The sources checked for this guide do not publish a separate size limit for .qbo files. Rather than lean on that silence, keep one statement per .qbo and import in date order, oldest first, reconciling each period before moving to the next. A year of statements converted together comes back as a zip of monthly .qbo files for exactly that reason.

Keeping to one statement per file also makes the count and total checks above trivial, because the statement summary and the For Review list cover the same dates. If a single period is unusually long, several hundred rows on a busy card account for instance, it still goes in as one file; split only when QuickBooks itself refuses the upload.

QuickBooks Desktop

Desktop takes the same .qbo through Banking, Bank Feeds, Import Web Connect File, and the transactions arrive in the Bank Feeds Center rather than For Review. The QuickBooks Desktop import guide covers Express and Classic mode, the OL error codes and the account-linking rules, none of which apply to QuickBooks Online.