Convert a PDF Bank Statement into QuickBooks IIF Entries

IIF is not QBO

It is easy to confuse the two QuickBooks import formats, but they work differently. A QBO is a Web Connect file that flows through the bank-feed screen, where you match and add transactions. An IIF, the Intuit Interchange Format, is a tab-delimited text file that imports straight into the company file with no matching step, and it is QuickBooks Desktop only, QuickBooks Online does not take IIF. So IIF suits a Desktop user who wants to load a statement's transactions as posted entries rather than review them through a feed.

TRNS, SPL, and ENDTRNS

IIF transactions use a three-line pattern under header rows that begin with exclamation marks: !TRNS, !SPL, and !ENDTRNS. For each transaction, a TRNS line opens the block with the account, date, and signed amount; at least one SPL line follows with the offsetting account and the opposite sign; and an ENDTRNS line closes it. This is double-entry baked into the format, the money hits the bank account on the TRNS line and lands in another account on the SPL. A converted statement is built into exactly this TRNS, SPL, ENDTRNS structure.

The offset account and categorizing later

A bank statement lists a date, an amount, and a description, but not which expense or income account each transaction belongs to. IIF's double-entry rule still needs an account on the SPL line, so the conversion posts the offset to a single holding account, and you recategorize the splits inside QuickBooks afterward. That keeps the file valid and importable while leaving the accounting judgment, which category each charge really belongs to, where it belongs, with you in QuickBooks rather than guessed in the file.

Importing, and backing up first

You import an IIF through File, Utilities, Import, IIF Files in QuickBooks Desktop. Because IIF writes directly into the company file with no bank-feed review and no simple undo, it is worth backing up the company file before you import, so a mistaken account or a wrong sign can be rolled back cleanly. A converted file that is accurate going in reduces that risk, but the backup is cheap insurance for any direct IIF import.

Accuracy and privacy

Since an IIF posts straight into the books, the dates, amounts, and signs have to be right, and every transaction is reviewable in the converter before export. The output is a tab-delimited IIF ready for Desktop's import. Because the statement holds real account activity, the file is processed to build the IIF and then deleted automatically, with nothing kept on a server afterward.

Frequently Asked Questions