Bug in preventing duplicate IIF imports containing unique check numbers.

QB warnings and message boxes fail to stop duplicate IIF file entries even though it recognizes duplicate unique check numbers. No matter how you answer the warning box and error messages, the entire IFF file data is put in to the account as a duplicate.

I used Simpleport to generate an IIF (of paypal transactions), each transaction containing a unique check number. I imported it into QB for Mac Version V11.0.7 RB.

I then tried re-uploading the very same IIF with the same unique check numbers. Simpleport representative told me I'd be warned and have the opportunity to cancel the duplicate import. QB gave me a warning, but still duplicated all anyway. Here is what happend:

QB gave me this choice box:

Duplicate Number
Check number 20100415006 has already been used. Continue?
(no) (yes)

I choose NO.

Then this popped up:

Error on Line 28: Can't record invalid transaction.
(No) (Yes) [yes is default]

I choose YES. (It's not clear what to do)

Then I got this message:

Duplicate Number
Check number 20100415007 has already been used. Continue?
(No) (Yes)

I choose "NO"

Then it says:

QuickBooks Information
Your data has been imported.

And indeed, all the information is duplicated (Even though I answered "NO" about continuing twice.

I then deleted every entry from this IIF (duplicates and all) and tried the same thing again. This time the messages came like this:

Duplicate Number
Check number 20100415006 has already been used. Continue?
(no) (yes)

Again, I choose "NO"

Error on Line 28: Can't record invalid transaction.
(No) (Yes) [yes is default]

This time I choose "NO"

Then I get a message that says "Date NOT imported successfully"

BUT, in fact, ALL the data was again imported and duplicated!

So, once you get the warning about a duplicated check number, it's already too later, every transaction in the IIF will duplicate no matter what you do.

So, clearly you have to be very careful to not duplicate the same data twice when importing IIF files, even if they have unique check numbers... if you do, the warnings will do you no good at all.

Intuit needs to fix this bug so that the warnings actually work and prevent data from being duplicated.

Report Abuse

2 Replies

Biscotti

Employee

04/29/10 9:42am PDT

It is possible to create invalid IIF files in many ways.

The transaction record function is probably detecting the error but no provision has been provided at that point to actually bubble that up to IIF import. That's a bug but... QuickBooks requires that the IIF files be valid.

For that reason a backup is requested in 2010 before importing IIF files, just in case there is a problem. You can bypass the backup in later R versions - a lot of users complained about the forced backup - but I wouldn't. If you have a problem with the import, revert to the backup, fix the IIF, and then try again.

I'll put in a bug report about the duplicate however given that IIF is expected to be valid on import SimplePort may need some love as well.

Report Abuse

jdq_xika

New Member

04/30/10 6:26am PDT

Latest post

UPDATE

BISCOTTI: I emailed you the SimplePort IIF file to qbmacforum1@intuit.com on April 30, as an attachment, so that you can include it with the bug report.

-----------------------------------------

Hello Biscotti,

The IIF was proper enough to go in just fine the first time. Can I send you the IIF file that I used to submit with the bug report? This way they can inform Simpleport (who I understand works closely with Intuit) if there is a problem as well -- improving life for everyone.

And yes, clearly it's a bug. If I answer "NO" to the question "Continue?" and it still continues and imports all the transactions (as well as giving me these odd "line number" "yes" "no" responses that don't matter how you anser them) -- that's a bug.

Let me know where to send the IIF file and you can include it with the bug report. I'm happy to help make QB for Mac more fully baked and less half baked (it's come a long way in a year or so -- I'll give that!)

Report Abuse

RSS