IIF file format for QuickBooks Desktop bank transactions

Structure

An IIF file starts with header rows beginning with ! that name the columns, followed by transactions. Each transaction is:

• one TRNS line – the bank side (account, date, amount, name, memo),
• one or more SPL lines – the other side, with the opposite amount,
• an ENDTRNS line.

The TRNS amount plus all SPL amounts must equal zero.

Example: one payment and one deposit

Columns are separated by tabs (shown here as spaces):

!TRNS  TRNSTYPE  DATE        ACCNT     NAME            AMOUNT   MEMO
!SPL   TRNSTYPE  DATE        ACCNT     NAME            AMOUNT   MEMO
!ENDTRNS
TRNS   CHECK     01/14/2026  Checking  Hardware Store  -42.50   Tools
SPL    CHECK     01/14/2026  Supplies  Hardware Store  42.50    Tools
ENDTRNS
TRNS   DEPOSIT   01/15/2026  Checking  Customer A      1200.00  Invoice 17
SPL    DEPOSIT   01/15/2026  Sales     Customer A      -1200.00 Invoice 17
ENDTRNS

For credit cards, use CREDIT CARD and CC CREDIT as transaction types.

How to import

1. Back up the company file (IIF imports can't be undone).
2. File › Switch to Single-user Mode.
3. File › Utilities › Import › IIF Files, select the file, OK.

Accounts and names that don't exist are created automatically – which is how typos turn into junk accounts. Check account names first.

Common IIF errors

• Transaction not in balance – SPL amounts don't offset TRNS.
• Columns shifted – the file was saved with commas or with quotes around fields. It must be tab-delimited plain text.
• Wrong dates – use the date format of your QuickBooks/Windows region.
• Imported into the wrong account – the ACCNT name doesn't match exactly, so a new account was created.

Generating IIF from a bank file

Ledgermere writes balanced TRNS/SPL pairs from any CSV, Excel, PDF, OFX, QIF, MT940, camt or BAI2 input, with editable bank and offset account names. Payee rules let you set the payee per pattern. If you want to review transactions before they post, use Web Connect (.QBO) instead.