Import Bank Statement Transactions into QuickBooks Desktop (IIF)

To import a DocuClipper bank statement into QuickBooks Desktop, export the project as a QuickBooks Desktop IIF file (with Source Account and Destination Account set against your uploaded Chart of Accounts), then in QBD use File → Utilities → Import → IIF Files to load it.

Uploading your Chart of Accounts to the DocuClipper project first lets DocuClipper validate every account name in the IIF before download, which prevents the most common "Account Name does not exist" error on import.

If you have not yet uploaded your QuickBooks Chart of Accounts (COA) to your DocuClipper project, do that first. See How to export your Chart of Accounts from QuickBooks Desktop. Once your COA is uploaded under Project Settings → QuickBooks Desktop, DocuClipper validates every IIF download against it and flags account name mismatches before you ever open QuickBooks.

What do I need before importing an IIF into QuickBooks Desktop?

• A QuickBooks Desktop company file (Pro, Premier, Enterprise, or Mac).
• A DocuClipper project with at least one extracted bank statement.
• (Recommended) Your QBD Chart of Accounts imported once per project, under Project Settings → QuickBooks Desktop → Import from QuickBooks Desktop. See the COA export guide.

Step 1. Export the IIF from DocuClipper

1. Open the project that contains your extracted statements.

2. In the left sidebar, click Add Documents and confirm your bank statements have finished processing. (Skip the first-time card picker if you already have documents in the project. Use the Add Documents dropdown for every subsequent upload.)

3. Above the transactions table, click Download Data.

4. In the Output Format dropdown, choose QuickBooks Desktop IIF.

5. At the top of the IIF panel you will see a banner. If no COA is uploaded, a warning banner reminds you that account names must match QuickBooks Desktop exactly and links you to upload your Chart of Accounts. If a COA is uploaded, an info banner reads "Validating against N accounts in your QuickBooks Desktop Chart of Accounts."

6. Fill in the export fields:

   Source Account (required)

   • The account the transactions came from in QuickBooks, for example Checking Account or Wells Fargo 1234.
   • If your COA is uploaded, pick it from the dropdown of your Chart of Accounts. If your company file uses account numbers, each account is listed the way QuickBooks shows it, for example 2100 · Business Visa. If no COA is uploaded, the field is a free-text box. Type the account name exactly, including spaces and capitalization.

   Source Account Type

   • Bank account for checking and savings statements, Credit card for credit card statements, Other (loan, line of credit) for any other kind of account. QuickBooks Desktop only accepts deposits and checks in a bank account and only charges and credits in a credit card account, so this has to match the source account's type in QuickBooks. Any other account type, such as a loan, a line of credit or an other current asset, takes general journal entries.
   • If your COA is uploaded and you picked the source account from it, DocuClipper sets this for you from the account's type in your chart.
   • Without a COA, the type starts on Bank account. When the statement looks like a credit card statement, a note under the choice says so; pick Credit card if the account in QuickBooks Desktop is a credit card account.

   Export as General Journal entries (optional)

   • Tick this to write every transaction as a General Journal entry instead of deposits and checks (bank accounts) or charges and credits (credit card accounts). It works with any source account type, including a bank or credit card account picked from your Chart of Accounts. See General Journal entries.
   • Left unticked, the file uses the source account's own transaction types, shown in the table under What your transactions look like after import.
   • DocuClipper remembers the choice for the project. It is also under Project Settings → QuickBooks Desktop → Default accounts → Bank statements.

   Destination Account Type (choose one)

   • Map to transaction category (recommended). Each transaction's category in DocuClipper becomes the destination account on the IIF split. This is the typical workflow if you have already categorized your transactions. With a COA uploaded, any categories that don't match an account name are listed inline so you can fix them first. A line under the choice names the accounts that transactions with no category post to; its Default accounts link opens the project's bank default accounts without leaving the download. The line shows until you pick your own accounts there.
   • Use a fixed account name. All transactions post to one account, for example a clearing account you recode inside QuickBooks afterwards. A Destination Account field appears: a dropdown from your Chart of Accounts if a COA is uploaded, otherwise a free-text box.

7. Under QuickBooks Desktop Edition, choose United States or Canada to match the company file you are importing into. The Canadian edition labels withdrawals CHEQUE where the US edition uses CHECK, and each edition only accepts its own spelling. DocuClipper pre-selects the edition from your location and remembers your choice for future downloads.

8. Click Download IIF. The line under the button, How to import this file into QuickBooks Desktop, links back to this guide.

If your project has a Chart of Accounts uploaded, DocuClipper validates every Source, Destination, and category name against it before producing the file. Any mismatches are listed inline so you can fix them in DocuClipper rather than discover them in QuickBooks.

Even if you skip the upload, the downloaded IIF file includes a ; WARNING: comment block at the very top listing every account name that DocuClipper could not validate. Open the IIF in any text editor before importing so you know what QuickBooks is about to reject.

Step 2. Import the IIF into QuickBooks Desktop

1. Open your company file in QuickBooks Desktop.
2. Go to File → Utilities → Import → IIF Files.
3. Click Import IIF and select the .iif file you downloaded.
4. QuickBooks shows a summary of the import. Click Done.
5. Open Banking → Use Register, select the source account, and confirm the new transactions appear with the correct dates, amounts, and categories.

What your transactions look like after import

By default, DocuClipper writes each row with the same transaction type QuickBooks Desktop itself uses for downloaded bank activity, so imported statements behave like any other bank transaction in your company file:

Why withdrawals show as "Check" when you didn't write one. In QuickBooks Desktop a Check is any money leaving a bank account: debit card purchases, ACH payments, EFTs, and wires, not only paper checks. It is the same type QuickBooks assigns when it downloads transactions through Bank Feeds.

Because they import as ordinary bank transactions, you can:

• Double-click any row to edit it in the normal Write Checks or Make Deposits window.
• See them in Reports → Banking → Check Detail and Deposit Detail.
• Reconcile them in Banking → Reconcile.

General Journal entries

With Export as General Journal entries ticked, every transaction imports as a General Journal entry (GENJRNL) instead, whatever the source account's type. Each entry has two lines that balance: one on the source account and one on the transaction's category (or the fixed destination account).

Account names, categories and default accounts work exactly as they do for deposits, checks and card charges; only the transaction type changes. You review and edit the entries in Company → Make General Journal Entries, and they appear in the source account's register and in Reports → Accountant & Taxes → Journal.

The choice is saved per project, in the download panel and in Project Settings:

Where uncategorized transactions post

When you map transactions to categories, a transaction with no category posts to the project's Uncategorized withdrawals account (withdrawals, credit card charges and card refunds; default Uncategorized Expenses) or Uncategorized deposits account (default Uncategorized Income). You don't need these accounts in your company file: the IIF file declares the default accounts it uses, so QuickBooks Desktop creates any that are missing during the import.

To post them somewhere else, upload your Chart of Accounts, then pick accounts in either place:

• In the IIF download panel, click Default accounts in the line under Destination Account Type. Your pick is saved as soon as you choose it; click Done to return to the download.
• Under Project Settings → QuickBooks Desktop → Default accounts → Bank statements.

Both places edit the same per-project setting, and the accounts you pick come from your own chart. Choose the (default) option to go back to the built-in account.

The most common error

If your account names do not match, QuickBooks shows this exact error:

Some of your records have errors. Click View errors to fix them.

The Account Name on a distribution does not exist in Quickbooks.

This means one or more category names, the Source Account, or the Destination Account in the IIF do not match an account in your QuickBooks Chart of Accounts.

QBD account name matching is strict:

• Case-sensitive: Office Supplies is not the same as office supplies.
• Punctuation-sensitive: Meals & Entertainment is not the same as Meals and Entertainment.
• Whitespace-sensitive: trailing spaces and double spaces count.
• Sub-account paths must match in full, separated by colons. For example Auto:Fuel, not Fuel.

How to fix it

1. In DocuClipper, open the project, open Project Settings, and click the QuickBooks Desktop tab.
2. Upload your QuickBooks Desktop COA. You can either upload the .iif export directly, or paste the !ACCNT block (or one account name per line) into the textarea on that tab. See How to export your Chart of Accounts from QuickBooks Desktop for the exact steps inside QBD.
3. Return to your transactions and re-run the IIF download. DocuClipper now compares every account name against your uploaded COA and shows a list of mismatches inline. Fix each mismatch by either:
   • Renaming the category in DocuClipper to match QBD, or
   • Adding the missing account in QuickBooks and re-uploading the COA.
4. Re-export the IIF and re-import in QuickBooks. The error should be gone.

You only need to import the Chart of Accounts once per project. DocuClipper reuses it for every future IIF export in that project, and each project keeps its own chart - so a separate project per company file keeps one client's accounts out of another's export.

Other common issues

• Duplicate transactions. IIF import does not deduplicate. Importing the same file twice creates duplicates. If this happens, delete the extra batch in QuickBooks.
• Date format. DocuClipper writes IIF dates as MM/DD/YYYY; there is no date setting for this format. If a date itself is wrong, correct it in the transactions table and download again.
• A new account showed up in my chart of accounts. That category did not match an existing QBD account and QuickBooks created it on import. Rename it inside QBD or upload your COA in DocuClipper to prevent this on future imports.
• Error 3140: "The specified account is invalid or of the wrong type". The Source Account Type does not match the account in QuickBooks, for example a credit card statement exported as Bank account into a Credit Card account, or a loan account exported as Bank account. Set Source Account Type to match (or pick the source account from your uploaded Chart of Accounts, which sets it for you), download the file again, and import it. General Journal entries are accepted by every account type, so ticking Export as General Journal entries also imports cleanly.
• Account numbers instead of names. The IIF needs the QuickBooks account name. With your Chart of Accounts uploaded, a free-text account entered as a number (6161) or as number and name (6161 Ask My Accountant) is written into the file as the matching account's name.
• Error 15106: "CHECK is an invalid value for field TRNSTYPE". The file was made for the US edition and you are importing it into QuickBooks Desktop Canada. Set QuickBooks Desktop Edition to Canada, download the file again, and import it. QuickBooks imported nothing from the rejected records, so there is nothing to undo.
• Accented letters look different. QuickBooks Desktop reads IIF files as plain ASCII, so DocuClipper converts accented letters to their closest plain form on the way out: CAFÉ MÜNCHEN becomes CAFE MUNCHEN. The Excel and CSV exports keep the original accents.
• Double quotes are missing from descriptions. QuickBooks Desktop reads a double quote in an IIF file as the start of a quoted field, so DocuClipper leaves double quotes out of the IIF. The Excel and CSV exports keep them.

Tips

• Back up your QuickBooks company file before any IIF import. Imports cannot be undone in bulk.
• Always import into a dedicated source account so you can filter and review the batch later.
• For a more modern alternative that supports automatic matching, see QuickBooks Desktop Web Connect (.QBO).

FAQs

How do I import an IIF file into QuickBooks Desktop?

In QuickBooks Desktop, open your company file and go to File, Utilities, Import, IIF Files. Click Import IIF, select the .iif file from DocuClipper, then open Banking, Use Register on the source account to confirm the transactions posted correctly.

Why does QuickBooks show "The Account Name on a distribution does not exist"?

One or more account names in the IIF do not match a name in your QuickBooks chart of accounts. Matching is case-, punctuation-, and whitespace-sensitive, and sub-accounts must use the full colon-separated path like Auto:Fuel.

How do I prevent the account name error before importing?

Upload your QuickBooks Desktop Chart of Accounts once per project under Project Settings, QuickBooks Desktop. DocuClipper then validates every Source, Destination, and category name against your COA and flags mismatches before you download the IIF.

What transaction types does the IIF import create in QuickBooks Desktop?

By default, bank accounts get Deposits for money in and Checks for money out, and credit card accounts get Credit Card Refunds and Credit Card Charges. These are the same types QuickBooks uses for Bank Feeds downloads, so they show up in Check Detail, Deposit Detail, and the Reconcile window. Any other source account, such as a loan or line of credit, gets general journal entries.

Can I import bank or credit card transactions as General Journal entries?

Yes. Tick Export as General Journal entries in the IIF export panel, or in Project Settings, QuickBooks Desktop, Default accounts, Bank statements. Every transaction then imports as a balanced General Journal entry against the source account, for any account type, including a bank or credit card account from your uploaded Chart of Accounts. DocuClipper remembers the choice for the project.

Why does QuickBooks show error 3140 "The specified account is invalid or of the wrong type"?

The transaction type in the file does not fit the source account's type in QuickBooks, most often a credit card statement exported as a bank account. Set Source Account Type to match the account in QuickBooks (Credit card for a credit card account, Other for a loan or line of credit) in the IIF export panel, or pick the source account from your uploaded Chart of Accounts so DocuClipper sets it, then download again and re-import.

Which QuickBooks Desktop edition should I choose?

Choose the edition your company file runs on. If you are not sure, open QuickBooks Desktop and go to Help, About QuickBooks: Canadian editions say Canada or Canadian in the product name. The edition only changes how withdrawals are labeled (Check or Cheque), and DocuClipper remembers your choice for future downloads.

Why does QuickBooks show error 15106 "CHECK is an invalid value for field TRNSTYPE"?

The IIF file was made for the US edition of QuickBooks Desktop and you are importing it into the Canadian edition, which uses the spelling CHEQUE. Set QuickBooks Desktop Edition to Canada in the IIF export panel, download again, and re-import.

Does IIF import deduplicate transactions?

No. Importing the same IIF file twice creates duplicate entries. If it happens, delete the extra batch inside QuickBooks.

Can I undo an IIF import in QuickBooks Desktop?

Not in bulk. Always back up your company file before importing so you can restore from the backup if needed.

What is the difference between IIF and Web Connect for QuickBooks Desktop?

IIF maps each transaction's category to a destination account on import, which is useful if you have already categorized in DocuClipper. Web Connect (.qbo) supports automatic vendor matching and rename rules in the bank feeds queue instead.

Related

• Import invoices into QuickBooks Desktop (IIF)
• Export your Chart of Accounts from QuickBooks Desktop
• Import into QuickBooks Desktop (Web Connect)
• Import into QuickBooks Online
• Customize Date Format