# QBO Files: What They Are and How QuickBooks Reads Them - Author: SimpleBankConvert (https://simplebankconvert.com) - Published: 2026-10-16 - Category: Import file formats - Canonical: https://simplebankconvert.com/blog/qbo-files-explained > What QBO files are, what's inside one, how QuickBooks Online and Desktop read them, and why a QBO file needs no column mapping the way a CSV does. QBO files are plain-text bank transaction files that QuickBooks reads directly. Each one lists dates, amounts and payees in labelled tags, plus a line that names the bank and account type. Because every value already has a label, QuickBooks needs no column mapping, which is why a QBO file imports faster than a spreadsheet. ## What's inside a QBO file? A QBO file is a text file with three parts: a short header, a block that identifies the bank and account, and a list of transactions. Every value sits between tags written in angle brackets, so software can read it without guessing which column means what. You can open one in Notepad or any text editor and read it. Nothing is hidden or encrypted. The example below is a tiny file with made-up values. Real files are longer, and many banks print the tags on one long line, but the order is the same. ``` OFXHEADER:100 DATA:OFXSGML VERSION:102 SECURITY:NONE ENCODING:USASCII CHARSET:1252 COMPRESSION:NONE OLDFILEUID:NONE NEWFILEUID:NONE 0INFO 20260331120000 ENG Example Bank99999 99999 1 0INFO USD 999999999000123456CHECKING 20260301 20260331 DEBIT20260314-412.8020260314001FLOUR SUPPLY COCard purchase CREDIT202603162500.0020260316001CUSTOMER PAYMENTDeposit 9318.2720260331 ``` ### The header The first lines, down to the blank line, are the header. They tell the reader which format version and character set follow. QuickBooks does not care about your data here. It checks that the file looks like the format it expects, then moves on. ### The account block Inside the tags near the top, the file names the bank and the account: - **ORG and FID** are the institution's name and its ID number. - **INTU.BID** is a bank ID that Intuit assigns to an institution. It is the line QuickBooks is fussiest about, covered in its own section below. - **CURDEF** is the currency, such as USD. - **BANKID, ACCTID and ACCTTYPE** are the routing number, the account number and the kind of account, such as CHECKING or SAVINGS. ### The transactions Each transaction is one STMTTRN entry. Five tags do most of the work: - **TRNTYPE** is a label such as DEBIT or CREDIT. - **DTPOSTED** is the posting date, written year, month, day with no separators. 20260314 means March 14, 2026. - **TRNAMT** is the amount. Money out is negative and money in is positive. - **FITID** is the transaction's unique ID. QuickBooks uses it to spot a transaction it has already seen, so a second import of the same file does not create duplicates. - **NAME and MEMO** hold the payee and any extra text. The last tag, LEDGERBAL, gives the balance on a stated date. QuickBooks can use it to compare against your register. Every tag in that list has one fixed meaning, and that is the whole point of the format. When you import a CSV, you tell QuickBooks which column is the date and which is the amount. A QBO file already says so. ## QBO files and Web Connect: the same thing? QBO files and Web Connect are two names for the same thing. QBO is the file extension. Web Connect is the name Intuit gives to the act of downloading that file from your bank's website and opening it in QuickBooks. Banks use the words loosely. One bank's download page says "Download for QuickBooks (Web Connect)" and saves a file ending in .qbo. Another says "QuickBooks" and saves the same kind of file. Both mean the same format. Two neighbours are easy to confuse with it: - **QFX** is the same structure aimed at Quicken, a different Intuit product. The two files look nearly identical inside. - **OFX** is the open standard that both are built on. Intuit's own variations on it, such as the INTU.BID line, are what turn a generic OFX file into a QBO file. If you read about "Intuit OFX", this is the layer being described. The way QFX, OFX and QBO differ is a topic on its own, covered in [QFX to QBO: why QuickBooks rejects a Quicken file and how a converter fixes it](/blog/qfx-to-qbo-converter#qfx-ofx-and-qbo-how-close-are-these-three-formats). The word "converter" also needs a plain definition here. A QBO file converter is a tool that takes data in another form, such as a CSV or a PDF statement, and writes it out as a QBO file with the tags above. It does not change what your transactions say. It changes the wrapping around them. ## The bank ID line that makes QBO files picky The bank ID line is the INTU.BID tag in the account block. It holds a number that identifies a financial institution in Intuit's list. When the number is missing or unknown to it, QuickBooks can refuse the file, even when every transaction in it is correct. The reason is that Web Connect was built for files that banks produce. QuickBooks matches the file to a known institution so it can link future downloads to the right account. A file made by a person or a small tool has no such institution behind it, so it has to carry an ID that QuickBooks accepts. Several things go wrong around this line, and they produce different symptoms: 1. **The line is missing.** The file looks complete, but QuickBooks reports a problem with the bank. [Intuit's guide to fixing Web Connect import errors in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-connectivity/fix-web-connect-import-errors/L8o5eQjO4_US_en_US) lists one such message: "QuickBooks is unable to verify the Financial Institution information for this download." 2. **The number is not on QuickBooks' list.** Same symptom, harder to spot, because the line is present. 3. **The account type does not match.** A file marked CHECKING that you try to link to a credit card account may be refused or may land in the wrong place. 4. **The file was edited in a word processor.** Smart quotes, a changed line ending or a saved .txt extension can break an otherwise good file. Edit QBO files only in a plain text editor. Because the cause is so often this one line, a QBO file made for QuickBooks should be generated with a valid bank ID from the start. Fixing a rejected file usually means changing that line, not the transactions. [The header change at the heart of a QFX to QBO conversion](/blog/qfx-to-qbo-converter#the-intu-bid-header-a-qfx-to-qbo-converter-changes) shows one such edit in detail. When you run into this error, check these in order: the file ends in .qbo, the INTU.BID line exists, the account type matches the QuickBooks account, and the file opens in a plain text editor with the tags intact. ## Opening QBO files in Online versus Desktop QuickBooks Online and QuickBooks Desktop both take QBO files, but they open them in different places and treat the account link differently. Online takes the file through the Upload from file screen under Bank transactions. Desktop opens it as a Web Connect import and asks which bank account to link it to. ### QuickBooks Online In Online, you go to Bank transactions, choose Upload from file, pick the file and select which QuickBooks account the transactions belong to. The transactions then appear for review, where you match, add or exclude each one. Online also takes CSV files through this same screen, but a CSV adds a column-matching step that a QBO file skips. ### QuickBooks Desktop In Desktop, you open the file as a Web Connect import. Desktop asks whether to link the file to an existing bank account or create a new one. The first time, the link is the important decision. Later downloads from the same bank reuse it. The Intuit guide above says a .qbo file is the only type Web Connect can read, so a QFX or OFX download will not do. ### Differences worth knowing - **Matching to existing accounts.** Online asks you to pick the account each time you upload. Desktop remembers the link once you set it. - **Duplicates.** Both versions use the FITID value to avoid re-importing a transaction they have already seen, so keep the FITID stable if you re-create a file. - **Bank ID strictness.** Desktop's Web Connect import has its own error for institution details it cannot verify, so test a home-made file there first. SimpleBankConvert's homepage says its files are designed for the QuickBooks Online bank file upload, and that QBO is also the file type Desktop opens, though the Desktop steps differ. It is in early access, so check [the product page](/) for what is open today. ## When a QBO file is the wrong choice A QBO file is the wrong choice when you need to see or edit the transactions first, when the destination is Xero, or when the data has no bank behind it that QuickBooks can link. In these cases a CSV is the better file. A CSV wins in three common situations: - **You want to check the numbers before importing.** A spreadsheet shows every row at a glance. A QBO file needs a text editor and some patience. - **You are importing into Xero.** Xero's statement import has its own CSV layout, and a CSV in that layout is the simplest file to get right there. - **You have to fix the data by hand.** Deleting a duplicate row or correcting a date is easy in a spreadsheet and fiddly in a tag file. A QBO file wins when the data is already clean and you want the quickest import with no mapping step, or when you use QuickBooks Desktop. Moving between the two is routine. To turn a spreadsheet into a QBO file, read [the five things to test in a CSV to QBO converter](/blog/csv-to-qbo-converter#csv-to-qbo-converter-checklist-five-things-to-test). To go the other way and read a QBO file in Excel, see [how to open a QBO file as a CSV in a spreadsheet](/blog/qbo-to-csv). If your starting point is a PDF statement, [converting a PDF statement to a QBO file](/blog/convert-pdf-to-qbo) covers that route. For printing or sharing a QBO file with someone who does not use QuickBooks, [turning QBO transactions into a printable report](/blog/qbo-to-pdf#turning-qbo-transactions-into-a-printable-report) explains the steps, and why the result is not a bank statement. SimpleBankConvert outputs both QBO and CSV from a PDF statement, so you can choose the file that suits the job. If you want to be told when accounts open, use [Get started](/get-started).