Convert IIF to QBO: Two QuickBooks Formats, Two Jobs

To convert IIF to QBO, pull the bank lines out of the IIF file, put them in a spreadsheet and write them as a QBO file. The two formats do different jobs. IIF posts finished entries into QuickBooks Desktop's books, while QBO delivers bank transactions for you to review and accept.

IIF and QBO: what does each QuickBooks file import?

An IIF file imports complete accounting entries into QuickBooks Desktop, while a QBO file imports bank transactions that wait for your approval. They look like cousins but do different work, which is why converting between them is more than renaming.

IIF stands for Intuit Interchange Format. It is a tab-delimited text file that can describe lists such as accounts, customers and vendors, and also full transactions. Each transaction lists its own accounts, with debits and credits already decided.

QBO is the Web Connect file. It lists only what the bank saw: a date, an amount, a payee and a unique ID. You, or a bank rule, decide the account afterwards.

The last row gets its own section below. For the background on the QBO side, see what a QBO file is and how QuickBooks reads it.

Which one did you actually receive?

Check the extension and then the contents. An IIF file opened in a text editor starts with header rows that begin with an exclamation mark, such as !TRNS, !SPL and !ENDTRNS. A QBO file starts with a block of header lines and then angle-bracket tags like STMTTRN. Different shapes make them easy to tell apart.

A deposit in both formats

The example below shows one deposit twice. Values are examples only.

IIF, with tabs between fields:

!TRNS	TRNSTYPE	DATE	ACCNT	AMOUNT	NAME
!SPL	TRNSTYPE	DATE	ACCNT	AMOUNT	NAME
!ENDTRNS
TRNS	DEPOSIT	03/14/2026	Checking	2400.00	Customer payment
SPL	DEPOSIT	03/14/2026	Sales Income	-2400.00	Customer payment
ENDTRNS

QBO, as one transaction inside the file:

<STMTTRN>
<TRNTYPE>CREDIT
<DTPOSTED>20260314
<TRNAMT>2400.00
<FITID>20260314-0001
<NAME>Customer payment
</STMTTRN>

Notice what is missing on the QBO side: the Sales Income account. The IIF names both halves of the entry. The QBO names only the bank side and leaves the other half to you.

Why IIF files work only in QuickBooks Desktop

IIF files work only in QuickBooks Desktop because the import is a Desktop feature, and QuickBooks Online has no IIF import. If your company file lives online, an IIF file cannot be loaded there, whatever its contents.

This is the point where many people get stuck. A bookkeeper sends an IIF, the client has QuickBooks Online, and nothing opens. Check your version in the software's own help, since Intuit's products change over time, but Desktop is where IIF has always lived.

What to do if you use QuickBooks Online

Pick the route by what the IIF holds:

• Bank transactions. Extract them and make a CSV or QBO to upload. The next section shows how.
• Lists, such as customers or accounts. Online has its own import tools for lists, mostly spreadsheet based. Move the list into a spreadsheet and use those.
• A full set of historical entries. This is a bigger migration, and you should ask your accountant or Intuit support rather than force it through a bank upload.

What to do if you use Desktop

Desktop can open IIF directly through the File menu, and it can open QBO through Web Connect. For bank lines, the second is usually safer, and the reason is the subject of a later section. The Desktop steps for the QBO path are in how to import bank transactions into QuickBooks Desktop. The first Web Connect import asks which bank account to link the file to, and linking the Web Connect file to a Desktop bank account covers that choice.

How do you pull bank transactions out of an IIF file into QBO?

You pull bank transactions out of an IIF file by opening it as a table, keeping only the lines that touch the bank account, and writing those as a CSV or a QBO file. The work is selecting rows and signing amounts correctly.

Follow these steps:

1. Open the IIF in a spreadsheet. It is tab delimited, so Excel or Sheets will split it into columns. Make a copy first.
2. Keep the TRNS rows for the bank account. Each entry has a TRNS row, which is the main line, and one or more SPL rows, which are the other sides. If your bank account appears on the TRNS row, keep that row. If it appears on an SPL row, keep that one.
3. Check the signs. In IIF, a deposit is positive on the bank line and negative on the other line. Keep the bank line's sign: money in positive, money out negative.
4. Build the columns. Date, description (the NAME or MEMO) and amount. Convert dates to one format.
5. Add unique IDs. QBO needs a unique ID per transaction. Without one, QuickBooks can treat repeated amounts as duplicates.
6. Convert. A CSV can go straight into QuickBooks Online. For Desktop, or for a no-mapping upload, convert the CSV to QBO. What a good converter checks is in the CSV to QBO converter checklist.

Splits and transfers

An IIF entry with several SPL rows is a split. The bank only saw the total, so write one QBO line for the bank amount and drop the split detail. If you need the detail later, categorize it in QuickBooks after import.

Transfers between your own accounts appear in IIF as one entry touching two bank accounts. Convert each account's side to its own file, or the second account will lack its line.

Going the other way

To convert QBO to IIF, which some readers search for, you reverse the work: extract the QBO transactions to a table, pick the account for each line, and write the TRNS, SPL and ENDTRNS rows. The tab spacing is exact, so test a few lines first. Another route is simply to import the QBO and let QuickBooks create the entries.

Reading the dates and amounts in an IIF before you convert

Two columns cause most conversion errors. IIF dates are usually written as month, day and year with slashes, so 03/04/2026 means March 4 in a US file, yet a spreadsheet set to a day-first region will read it as April 3. Fix the regional setting, or split the date into three pieces with a formula, before you rewrite it as year, month and day.

Amounts need the same care. IIF stores the bank side and the other side with opposite signs, so a spreadsheet total of every row in the file comes to zero. If your total is not zero, a row was lost when you opened the file. Fix that first, then filter down to the bank account lines and total again, and compare that figure with the bank's activity for the period.

What goes wrong when IIF posts straight to the books?

IIF posts straight to the books, so a bad row becomes a real transaction with no review step. A wrong date, a doubled amount or a missing account lands in your ledger at once, and fixing it means finding and voiding the entries.

QBO behaves differently. The file only fills a queue. You look at each line, match it to an existing entry or categorize it, and reject what you do not want. That pause is the safety net.

The common IIF problems are:

• Duplicates. Importing the same IIF twice creates every entry twice. QBO has a unique ID per line to prevent this.
• Accounts that do not exist. If the IIF names an account not in the chart of accounts, behaviour depends on the version, and you may get a new account you never meant to create.
• Date format surprises. A month and day swapped looks valid for any day up to the twelfth.
• Hidden formatting. A stray space or an extra column shifts every field after it.

A safer habit

Back up the company file before any IIF import. Run the import on a copy of the file first, check totals against the bank, and only then repeat it on the real file. The same care applies to a three-row test of any converter.

When is an IIF file still the better pick?

An IIF file is the better pick when you are moving accounting structure, not bank lines: a chart of accounts, customer and vendor lists, or a batch of journal-style entries that need accounts already assigned. QBO cannot carry any of that.

Bank files are the wrong tool for those jobs because QBO knows only the bank side of a transaction. An IIF is right when:

• you must set many accounts or list entries up the same way every time;
• the transactions are not bank-related, such as adjusting entries;
• you are on Desktop, and you trust the file and have a backup.

For ordinary bank statements, QBO is better in nearly every case, because of the review step and the duplicate protection.

Starting from a PDF statement

Many people reach IIF only because their bank gave them a PDF. If that is you, skip IIF. SimpleBankConvert turns a PDF statement into a CSV or QBO file, and a QBO file brings the transactions into Desktop or a CSV into Online without a posting format in between. It is opening to early users, so join the list on the get started page. If your real task is reading a Quicken download in a spreadsheet, converting QFX to CSV is the closest guide.