QuickBooks 2019 IIF Import

QuickBooks Changes

Intuit has significantly changed how QuickBooks 2019 (and Enterprise 19.0) import IIF files. When importing, QuickBooks now optionally, and by default, imposes many more rules and restrictions in an effort to ensure… something. We are not sure what.

Unfortunately this new error checking imposes many new restrictions and some omissions/bugs – most of which are unhelpful. There are several issues which stop QuickBooks from importing normal and valid IIF files – files that have always worked and continue to work in preceding version years of QuickBooks.

As a result, IIF files that used to work won’t anymore, at least by default.  But there’s a way! Keep reading…

For those using our apps, we’ve released updates to accommodate some of these issues. However, there are remaining QuickBooks issues you may run into. As a result, we recommend the choices below.

Import Options Overview

Luckily, QuickBooks now offers two ways to import: The new default method and the older method you may have have been using with older QuickBooks versions. This second method is hidden behind a scary-looking link.

The two QB 2019 options are seen here:

It is very-tempting blue Import IIF button. Don’t!

The Import IIF button imports using the new and restrictive error checking method. IIF files created with older releases of our apps will not import using this method. There also several bugs and unnecessary restrictions, and we keep finding more of them.

The Import it for me link uses the method  we’ve all been using with IIF files for many years. IIF files created with our applications work best with this option.

You may need to use this option in order to get around bugs with the new method and for a growing list of specific cases.


a. Use the Import it for me option!

Here’s why:

  • This option uses the older, reliable, and more accurate IIF import code.  It is the same as older versions of QuickBooks.
  • The “I’ll fix it later” text suggests you’ll have to fix something, but that misleading and is unlikely to be the case.
  • Avoid the bugs and limitations with the new new method – some noted below.

b. For users of our applications, download and install the latest release of your BRC app(s):

The latest releases of our apps will create IIF files that are a little different than older versions and are more compliant with the new Import IIF option (though we don’t recommend using it.) These releases also contain the latest code, feature changes, and fixes to other unrelated issues.


If you choose to use the new Import IIF option – not recommended – then…

  • Be prepared to be stopped by issues that are not really issues.
  • If there are issues, QuickBooks will create a copy of the IIF file with error notes. You can open it in Excel for review.

Known Bugs we’ve discovered using the new default IIF import

Here are some of the new unwanted restrictions and bugs:

  1. When importing time records, QuickBooks may error and indicate that the related employee address is invalid – even though you are not importing changes to the employee.
  2. Import will fail if class field values on time records are not dates – but the class list is not a list of dates.
  3. The Send Later (email later) status for sales forms is ignored.
  4. QuickBooks will not import reverse/credit lines on transactions. For example, you can’t import a return line item on an invoice, a line that reduces the invoice total.
  5. It will not import 0.00 amount invoices (and perhaps other sales) even if the details of the invoice are non-zero.
  6. Document numbers are incorrectly limited to 12 characters though much larger values are actually allowed in QB.
  7. Phone numbers on name records are incorrectly limited in length which will often cause the extension to be omitted – while much longer values are actually accepted in QB.
  8. If you attempt to include a semi-colon (;) on a record in the IIF file, QB stops reading the line at the semi-colon.  If there are required fields after that, the import fails.  If optional fields, then they are not imported and you will lose data.
  9. If you include any characters with a computer-ascii value a little larger than a tilda (~) QB now imports it as a “?” character – while all other QB versions work as expected.
    1. Characters include “€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ”
    2. Also higher-end characters beyond this range.
    3. QB does support these characters using the old IIF import and the regular user interface.
    4. This means no names with European/international characters will work.  For example,  René Cresté will import as “Ren? Crest?”.
  10. The reconciled status is ignored during import. All transactions are imported as uncleared, which completely defeats the use of the field.
  11. While the reconciled status is ignored, QB still checks the values and will block the entire import if there is a single reconciled status other than Y or N or empty within the file.  But both IIF and QB support a third status, “newly cleared”, the “*” you can see in the register, which is represented in IIF using a third character.
  12. Import fails if you omit the customer on sales receipt transactions.  But QB does not require a customer on sales receipt transactions.  You can record them without a name, which is commonly done when importing daily sales transactions.

Other Notes

Importing now closes all windows on the desktop (there is no way around this).  Which is terrible.

Using the new import method is slow and takes about 10 – 20 times more time than the Import it for me method.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk