QBO vs IIF: Which QuickBooks Import File Do You Need?

Last updated July 2026.

If you are converting a PDF bank statement, the converter will ask which file you want out: QBO or IIF. The wrong pick means a failed import or transactions in the wrong place. Here is the plain-English difference and how to choose, whether you run QuickBooks Online or Desktop.

What is a QBO file?

A QBO file is a QuickBooks Web Connect file built on the OFX banking standard. QuickBooks treats it exactly like a download from your bank. The transactions land in the Banking or Bank Feeds center, where you review them, apply categories and rules, match them to anything already recorded, and then accept them into the register. Nothing posts until you approve it. QBO files work in both QuickBooks Online and QuickBooks Desktop, though Desktop expects the file to be no more than three years old.

What is an IIF file?

An IIF file (Intuit Interchange Format) is a tab-delimited text format that QuickBooks Desktop reads directly. IIF imports are fully offline and post straight into the register without a review-and-match step. That makes them fast, but less forgiving: the account names, and for some entries the vendor or customer names, have to match what is already in your QuickBooks file exactly, or the import fails or creates duplicates. IIF is a Desktop format. QuickBooks Online does not import IIF files.

QBO vs IIF vs CSV at a glance

Which one should you choose?

Choose QBO if you use QuickBooks Online

QuickBooks Online does not read IIF, so QBO (or CSV) is your import format. QBO is the better of the two because it routes through the For review screen, where you set categories, apply bank rules, and catch any misread line before it hits your books. Convert your statement to a QBO file with our PDF bank statement to QuickBooks converter or the PDF to QBO converter, then upload it under Bank transactions.

Choose QBO on Desktop when you want a bank-feed workflow

On QuickBooks Desktop, import a QBO file through Banking, then Bank Feeds, then Import Web Connect File. You still get the match-and-accept step, which keeps the register clean and avoids duplicates. Keep the file recent, since Desktop rejects Web Connect files older than three years.

Choose IIF on Desktop when you want transactions posted directly

If you are loading historical entries, journal-style data, or lists into QuickBooks Desktop and you want them in the register immediately with no matching, IIF is the tool. Just line up your account names first. Our PDF to IIF converter and the QuickBooks Desktop IIF import guide walk through it.

How do I create a QBO or IIF file from a PDF?

Your bank gives you a PDF, not a QBO or IIF file, so you convert it. Upload the PDF statement to a converter, check that the dates, descriptions, and amounts match the statement, then export the format you need. The tool at the top of this page produces both QBO and IIF from the same PDF, so you can match the file to wherever it is going.

If your data is already in a spreadsheet rather than a PDF, you do not need a PDF step at all. A CSV to QBO converter turns an exported CSV into a Web Connect file, and for any statement format that is not strictly PDF, a general bank statement to QuickBooks converter covers the broader set of inputs.

Moving from QuickBooks Desktop to Online?

This is where the QBO vs IIF question trips people up most. Years of Desktop data often live in IIF files or IIF exports, but QuickBooks Online cannot read any of them. The routes that do work, and the one most people waste an afternoon on, are set out in our guide to importing IIF files into QuickBooks Online. When you migrate, you have two realistic paths for transaction history. You can use Intuit's built-in migration tool for the company file as a whole, or, for individual accounts and date ranges that did not carry over, convert the source statements to QBO files and import those into the new Online company. Either way, budget time to recreate your chart of accounts and bank rules in Online, because those do not move through a QBO file. The transactions come across in the QBO; the categorization logic you rebuild once on the Online side.

A note on the three-year QBO rule

QuickBooks Desktop rejects a Web Connect (QBO) file if the transactions are dated more than three years in the past. That rarely matters for current bookkeeping, but it bites during deep historical catch-up. If you hit the error on Desktop, an IIF file is the workaround, since IIF has no date restriction and posts straight to the register. On QuickBooks Online there is no equivalent three-year cutoff for uploaded files, so older QBO files import normally.

Frequently asked questions

Can I import an IIF file into QuickBooks Online?

No. IIF is a QuickBooks Desktop format, and QuickBooks Online does not import it. For Online, convert your data to a QBO (Web Connect) file or a properly formatted CSV instead. If you are moving from Desktop to Online, plan to re-export your transactions as QBO or CSV rather than reusing IIF files.

Is a QBO file the same as an OFX file?

They are closely related. A QBO file is QuickBooks Web Connect data built on the OFX standard, with a few QuickBooks-specific tags. In practice you import a QBO file into QuickBooks, while plain OFX is used more broadly by other accounting tools. A good converter outputs the QBO flavor QuickBooks expects.

Why does my IIF import fail?

The usual cause is a name mismatch. IIF posts directly into the register, so the account, vendor, or customer names in the file must match your QuickBooks lists exactly, including spelling and spacing. Create any missing accounts first, line up the names, and re-import. QBO avoids this because it matches during the Bank Feeds review.

Which is more accurate, QBO or IIF?

Accuracy depends on the conversion, not the format. Both carry the same dates and amounts. The practical difference is that QBO lets you review every transaction before it posts, so errors are easier to catch, while IIF posts immediately. If you want a safety net, choose QBO and check the For review screen.

How do I open a QBO file?

You open a QBO file inside QuickBooks rather than by double-clicking it. In QuickBooks Desktop, go to File, then Utilities, then Import, then Web Connect Files, and pick the file. In QuickBooks Online, upload it under Bank transactions. QuickBooks then routes the transactions to the review screen for the account you select.

A QBO file is plain text underneath, so if you just want to look at what is in it, right-click and open it with Notepad or TextEdit. You will see OFX-style tags wrapped around each transaction: date, amount, description, and a transaction ID. That is useful for spot-checking a converted file before you import, but do not edit it by hand unless you know the format, because a single broken tag will make QuickBooks reject the whole file. If you want the full click path with screenshots, our guide on how to import a QBO file into QuickBooks covers both Online and Desktop.

Can I convert an IIF file to a QBO file?

Not directly. Intuit does not provide a tool that turns an IIF file into a QBO (Web Connect) file, and the two formats carry different kinds of data, so there is no clean one-to-one mapping. The workable route is to open the IIF in a spreadsheet, pull the date, description, and amount columns, and build a QBO from that.

This comes up constantly during Desktop to Online migrations, where years of payroll journals or vendor bills sit in IIF exports that QuickBooks Online will not touch. Keep in mind what gets lost: IIF can hold lists, items, and multi-line journal entries, while a QBO file is a bank statement feed. Invoices, bills, and payroll splits do not survive the trip in any meaningful way. If all you need is bank and credit card history, the simpler path is to skip the IIF entirely and convert the original PDF statements straight to QBO.

How do I open and edit an IIF file in Excel?

Open Excel, choose File then Open, switch the file type filter to All Files so the .iif shows up, then select it. Excel runs the Text Import Wizard because IIF is tab-delimited. Click through it, edit only the data rows, then save as Tab Delimited Text and rename the extension back to .iif.

Two things break IIF files more than anything else. First, editing the header rows: the lines starting with !TRNS, !SPL, and !ENDTRNS are keywords QuickBooks reads to understand the structure, so leave them alone. Second, letting Excel save in its own format. If you save as .xlsx or .csv, QuickBooks will not read it. Save as tab-delimited text, and when Excel nags you again on close, choose Don't Save. It also helps to back up your company file before importing, since an IIF import cannot be undone with a single click.

Does importing an IIF file create duplicate transactions?

It can, and QuickBooks will not stop you. IIF files carry no unique transaction ID, so if you import the same file twice, or import two files whose date ranges overlap, QuickBooks Desktop posts every line again without any warning. QBO files avoid this because Web Connect data includes an ID QuickBooks tracks per account.

That single difference is the strongest practical argument for QBO over IIF when you are loading bank or credit card activity. With a QBO file, a re-import of overlapping dates usually gets filtered out. With IIF, the only protections are your own: check the last posted date in the register before you import, keep your date ranges tight and non-overlapping, and take a backup first so you can restore if a batch goes in wrong. Cleaning up afterward means deleting entries one at a time or restoring that backup. If you are pulling statements for a Desktop file, converting them with our PDF bank statement to QuickBooks Desktop converter lets you output QBO and keep the duplicate protection.

Ready to pick a tool? Compare the converters that produce both formats in our best PDF to QBO converter roundup, or read how to import a PDF bank statement into QuickBooks Online step by step. Cost is usually the deciding factor once the formats match, so it is worth reading the DocuClipper pricing page-metered model against the flat ProperSoft pricing subscription before you commit a backlog to either one.