ocrsnip No uploads
.ofx · .qfx · .qbo → .iif

OFX to IIF, in this tab.

The file your bank gave you, turned into the tab-separated import QuickBooks Desktop takes when Web Connect is not an option. You name the accounts, you see what the import will do, and then you download it. Free, and nothing is uploaded.

Free, no row limitYou name the accountsNothing uploaded
Drop an .ofx, .qfx or .qbo file The file your bank offers as “download for Quicken” or “Web Connect”. Opened in this tab — nothing is uploaded. Choose file Try a sample file stays on this device

Why convert a bank file to IIF at all

Because the direct route can be closed. QuickBooks Desktop prefers a .qbo, and a .qbo only opens if it carries an INTU.BID — an institution id QuickBooks checks against its own list of banks before reading a single transaction. If your bank is not on that list, or you cannot find the number, the correct file with correct transactions is still refused. Converting to .qbo is the better road when that number is available; IIF is the road that does not ask for it.

The other reason is categories. A bank file lands transactions in one account and leaves them for you to sort. An IIF carries both sides of every entry, so money in and money out arrive already posted against the accounts you name below.

What you give up, and we would rather say it first

A bank file carries FITID: a unique id per transaction that QuickBooks and Quicken use to recognise rows they already have. IIF has no such field. Import the same period twice and you get it twice — the format has no way to notice. A .qbo import of the same statement would have quietly skipped the duplicates.

So: import each period once, and keep a note of where you stopped. If a re-import is unavoidable, restore the backup first rather than importing on top. This is the real cost of the IIF route, and it is not mentioned by most of the tools that sell it.

What comes across

Date, amount, description and cheque number, exactly as the bank wrote them. Dates are rewritten in the US order QuickBooks Desktop reads whatever its display language is. The description goes into both NAME (trimmed to the 41 characters a list entry allows) and MEMO, in full. A cheque number, when the file has one, becomes DOCNUM — the nearest thing to an id IIF has, and it only exists for cheques.

Every transaction is written as three lines — TRNS, SPL, ENDTRNS — and the two sides cancel exactly. They have to: QuickBooks refuses a transaction whose halves do not balance rather than importing half of it. The summary above the download button shows the count, the split between money in and money out, and the net effect on the bank account, so the import holds no surprises.

Questions

Something else? Write to support@ocrsnip.com.

Is this free?

Yes, with no row limit and no account. It converts a file you already have, and every converter here that does that is free — the paid tools are the ones that read a document and check it, like a PDF statement or an MT940.

Will importing this duplicate transactions I already have?

Yes, if you import the same period twice — and that is a property of IIF, not of this page. The format has no field for the transaction id your bank file carries, so QuickBooks has nothing to recognise a repeat by. If duplicate protection matters more than the categories, convert to .qbo instead: the id survives that route, and a re-import corrects rather than doubles.

Should I use IIF or QBO?

QBO when you can: it keeps transaction ids and imports through the bank feed. IIF when QuickBooks refuses the .qbo because the institution id is missing or unrecognised, or when you want both sides of each entry posted to accounts you choose. The two pages share one engine, so the transactions are identical either way.

QuickBooks created a second account with a slightly different name.

Then the name in the box above did not match your chart of accounts exactly. QuickBooks matches by text and creates silently rather than asking — capitals, spacing and the colon in a sub-account all count. Restore the backup, fix the name, import again.

Can I undo an IIF import?

No. QuickBooks Desktop has no rollback for it and no review step before it commits. The backup you take beforehand is the undo — which is why the order is back up, import, look at the register.

My file is a .qbo already and I need it as a spreadsheet.

That is a different direction and it is free too: QBO to Excel and QBO to CSV read .qbo, .qfx and .ofx and hand back columns. A spreadsheet of transactions can also become an IIF, on CSV to IIF.

Does my statement leave my computer?

No. Reading the file and writing the new one both happen in this tab; there is no upload step and no server on this site that receives files. The network panel of your developer tools stays empty while you convert, which is the only form of this promise worth anything.