Convert an OFX to a QuickBooks IIF Register
Have an OFX but QuickBooks Desktop won't take it? Convert OFX to IIF for a direct register import, no Intuit FID needed, unlike a QBO Web Connect file.
TL;DR - Quick Summary
An OFX holds clean transaction data, but QuickBooks Desktop cannot import a plain OFX into the register. Converting OFX to IIF maps its structured fields into TRNS and SPL lines for a direct import, and unlike the QBO Web Connect path, IIF needs no Intuit institution ID to be accepted.
An OFX QuickBooks Desktop won't take
An OFX is already structured, dates, amounts, payees, and transaction types in tidy fields, but QuickBooks Desktop still will not import a plain OFX straight into the register. It takes a QBO through the bank-feed screen, or an IIF through direct import. So the data is clean and the door is closed. Converting the OFX to IIF opens the direct-import door, turning those OFX fields into the tab-delimited TRNS and SPL lines Desktop reads.
OFX fields map cleanly to TRNS and SPL
Because an OFX is structured, the mapping is straightforward. Each STMTTRN block, with its posted date, amount, name, memo, and transaction type, becomes a TRNS line carrying the account, date, and signed amount, with the name and memo along for the ride. An SPL line adds the offsetting account and ENDTRNS closes the transaction. Where a scanned statement has to be read first, an OFX already holds the fields, so the conversion is a clean remap into IIF's structure rather than an extraction.
IIF needs no Intuit FID
This is the real reason to choose IIF for an OFX. The QBO Web Connect route requires Intuit's institution headers, chiefly INTU.BID and an FID, and if they are missing or unrecognized QuickBooks throws a verification error and refuses the file. IIF has no such check: it imports directly into the company file without validating an institution. So an OFX that will not go in as a QBO, because its institution is not recognized, can still be brought in as an IIF, which sidesteps the FID requirement entirely.
Offset account, and back up first
An OFX carries no category, so IIF's double entry sends the offset to a single holding account that you recategorize in QuickBooks afterward. And because an IIF writes straight into the company file with no bank-feed review and no easy undo, back up the file before importing. The import itself is File, Utilities, Import, IIF Files, and it is QuickBooks Desktop only, QuickBooks Online does not take IIF.
Accuracy and privacy
Since the IIF posts directly into the books, the amounts and signs pulled from the OFX 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 OFX holds real account activity, it is processed to build the IIF and then deleted automatically, with nothing kept on a server afterward.
How it works
- Start with the OFX: Have the OFX file from your bank or another tool ready.
- Convert to IIF: Convert the OFX to IIF, mapping each STMTTRN into a TRNS line with an offsetting SPL.
- Back up first: Back up your QuickBooks company file, since IIF imports write directly and are hard to undo.
- Import and categorize: Import through File, Utilities, Import, IIF Files, then recategorize the splits.
Comparison
| Aspect | OFX via QBO | OFX via IIF |
|---|---|---|
| Path | Bank-feed Web Connect | Direct register import |
| Institution ID | Needs FID and INTU.BID | None required |
| Handling | Review and match | Posts directly |
| Category | On match | Offset, then recategorize |
| Edition | Desktop and Online | QuickBooks Desktop only |
An OFX file converts to a QuickBooks Desktop IIF in about 20 seconds. Convert your statements now.
See pricing