We can use another workaround, tonilynnseff.
If you encounter the error "File not imported", QuickBooks gives you the option to review and resolve the errors found in the .IIF file.
Save the IIF file on the computer. Then, import it. Here's how:
Let us know if you have other questions. We are here to help.
We have found that the changes to import made in QB 2019 and 2020 are far too picky and buggy to be useful in some cases and can sometimes be harmful. The new import will choke on things that are allowed and sometimes ignore what is in the IIF file and instead just record something else.
If you follow our recommendations here then it will likely work: BRC QuickBooks 2019 & 2020 IIF Import Changes and Recommendations
Big Red: Until I upgraded to 2020, I could import time for both employees and vendors (1099 contractors) via IIF upload. Once converted, the employee information uploads successfully, but the contractor time kicks out. I read through your proposed resolution and will try it for next payroll. Do you feel this is Intuit starting to make it difficult to upload time in order to push customers to TSheets?
I am not sure why they made the likely huge effort to half-way replace the import code with new code. Code that was supposed to do the same thing, but doesn't. And also not sure why they haven't fixed all of the many ensuing issues they created, now two years ago.
Intuit has routinely claimed to not support IIF, and then they put all this effort in to try to update it, but IMO they introduced so many bugs it's astounding. I keep finding more, and after two years very little has been fixed. Some of these are glaring issues. I suspect they were unintentional.
Good morning, @Volyza.
Thanks for following the thread.
The improved import .IIF tool is designed to eliminate the possibility of importing bad data by scanning your file for errors. When there are errors found in the tool and your .IIF wasn't imported, you'll need to review the errors and resolve the issues in order to proceed with importing. After you've corrected the errors, you can save the newly corrected .IIF file and import the data.
Check out the details outlined in Improved .IIF Import in QuickBooks Desktop.
You can choose to skip over the portion of the tool that scans your file for errors, as mentioned by brconsultingd2's link provided above. Please be mindful that in doing this, you'll need to resolve the errors once they're imported.
Please note: Always create a local back up before making any changes to the file.
Let me know if you have further questions or concerns. Feel free to reach out to the Community any time. Wishing you and your business continued success. Take care!
I don't want to import without review but my errors read "Invalid line  Expected " ENDTRANS' .  and I don't know what I am supposed to do to correct this. It seems my only option is to use the "Import it for me..." Can you give me some suggestions?
Let's fix the error when importing an IIF file to QuickBooks, VPA1.
You’re getting the [ERROR] Expected ‘!ENDTRNS’. ” because you haven't defined the ENDTRNS row. You need an ENDTRNS definition line that starts with !ENDTRNS just as you have !TRNS and !SPL defined.
Also, note that there is no need to repeatedly redefine the rows. One set of !TRNS, !SPL, !ENDTRNS definition rows at the top of the file is all that is needed.
You can visit again this link: Improved IIF Import in QuickBooks 2019 and later to guide you through importing the file.
Let me know if there's anything else you need, and I'm right here to help ensure you're able to import your data.
Yes there is something between QB Desktop and PayPal. A 3rd party connector is able to reconcile PayPal transactions to QB Online easily, but they didn't support QBD for a reason. Our clients have to use another tool to import the PayPal transactions data in XLS to QB Desktop file.