PDF to IIF Converter for QuickBooks Desktop

What is an IIF file?

IIF stands for Intuit Interchange Format. It is a plain tab-delimited text file that QuickBooks Desktop reads to import lists and transactions: customers, vendors, accounts, and the bank or credit card activity you want in a register. Each section starts with a header row that names the columns, then one data row per record. Because it is just tab-separated text, you can open an IIF file in a spreadsheet to inspect it, but QuickBooks Desktop is what turns it into posted transactions.

A PDF statement is not an IIF file. A PDF is a fixed image of a page, and QuickBooks has no way to map its rows and columns into the fields a register needs. That is the whole reason an import from a raw PDF fails. Converting the PDF to IIF does the mapping for you: it reads each visible row on the statement and writes it into the exact tab-delimited columns QuickBooks Desktop expects, so the transactions post on the first try.

IIF or QBO: which should you import?

Both formats target QuickBooks Desktop, and they behave differently once they land. An IIF file posts transactions directly into the register the moment you import it, with no bank-feed review queue in between. That is fast and predictable, and it is the right call when you are rebuilding history or loading an account QuickBooks does not connect to. A QBO (Web Connect) file, by contrast, routes through the bank-feeds workflow, which adds a review step and FITID duplicate protection but more setup. Pick IIF when you want transactions in the register now with the least friction, and QBO when you want them to flow through bank feeds with matching and duplicate checks. PDFQBO writes either one from the same PDF, so you are not locked into a single path.

Inside a clean IIF file: why ours imports without errors

Most IIF import failures come down to a malformed file: a header row that does not match the data, a stray tab, a date QuickBooks cannot parse, or an amount with a currency symbol baked in. PDFQBO builds the file the way QuickBooks Desktop expects so those errors never appear. The transaction section uses the standard TRNS and SPL header rows, every column lines up with its header, and each row carries a transaction type, a register account, a date, an amount with the correct sign, and a name or memo.

Dates are the single most common reason an IIF import is rejected or posts to the wrong period. PDFQBO parses each statement date no matter how the bank prints it, then writes it in the format QuickBooks Desktop reads, so a 03/04 line is never misread as the wrong month. Amounts are written as plain signed numbers with no dollar sign or thousands separator, which is what the IIF parser needs. Descriptions are kept clean so a payee with an apostrophe or an ampersand does not break a column.

One honest caveat worth knowing: IIF imports do not carry the FITID duplicate-protection that a QBO Web Connect file has, so importing the same statement twice will post the transactions twice. That is a property of the IIF format itself, not the converter. Review the on-screen transactions before you download, import each statement once, and keep a backup of your company file before importing. If you would rather have built-in duplicate detection, convert to a QBO file instead.