Skip to main content
V
vikctel
December 5, 2024
Solved

Import employee time using IIF

  • December 5, 2024
  • 2 replies
  • 0 views

I was using an older version of Quickbooks Desktop and was able to successfully import my employee time entries successfully by importing an IIF. But now I've moved to QB2024 and I am getting errors when I am trying to import

 

I get the error: There is already another entity in Quickbooks by this name [11314]; Invalid employee name [15179]

 

But I want to import the time to an EXISTING employee. If I rename the employee in Quickbooks to another name and then try to import, then it imports fine, but it creates a new employee and has that time imported to the new employee.

 

But I do NOT want to import a new employee. I want to import to an existing employee.

There is something clearly wrong with the software as it no longer allows imports to existing entities/employees.

 

Can you help with this?

    Best answer by BigRedConsulting

    @vikctelRE: I get the error: There is already another entity in Quickbooks by this name [11314]; Invalid employee name [15179]

     

    What the intuit employees are trying to say without saying it is that the new and 'improved' IIF import Intuit introduced in 2018 for QuickBooks 2019 is riddled with bugs that Intuit has never bothered to fix, while at the same time they continue to tout the change as an improvement - which it is not.

     

    One of the bugs in it is that it just flatly refuses to import time properly.

     

    To import your time IIF files, use the alternate method, which is the old import code you're used to. Luckily Intuit left the old code in place, probably because they realized how crappy their new code is, while at the same time they refuse to fix it.

     

    See BRC QuickBooks 2019+ IIF Import Changes and Recommendations for more details and steps.

    2 replies

    A
    AnneMariee
    December 5, 2024

    It's important to ensure your data imports smoothly without creating duplicate entries or altering existing records, vikctel.

     

    To keep our conversation cohesive and ensure you receive the most accurate information, I recommend reviewing my colleague's comprehensive response to your initial query. You can access that detailed guidance through the following link: https://quickbooks.intuit.com/learn-support/en-us/employees-and-payroll/re-iif-import/01/1513360#M133981.

     

    I'll also add this article for future reference, which explains how to create a report displaying the total hours worked by each employee: Create a total hours worked by employee report.

     

    Please take a moment to review it at your convenience. If you have any additional questions or require further assistance with importing time or managing employee records in QuickBooks Desktop, please comment below. I'm here to help you streamline this process and ensure the software functions according to your expectations.

    BigRedConsulting
    BigRedConsultingAnswer
    December 5, 2024

    @vikctelRE: I get the error: There is already another entity in Quickbooks by this name [11314]; Invalid employee name [15179]

     

    What the intuit employees are trying to say without saying it is that the new and 'improved' IIF import Intuit introduced in 2018 for QuickBooks 2019 is riddled with bugs that Intuit has never bothered to fix, while at the same time they continue to tout the change as an improvement - which it is not.

     

    One of the bugs in it is that it just flatly refuses to import time properly.

     

    To import your time IIF files, use the alternate method, which is the old import code you're used to. Luckily Intuit left the old code in place, probably because they realized how crappy their new code is, while at the same time they refuse to fix it.

     

    See BRC QuickBooks 2019+ IIF Import Changes and Recommendations for more details and steps.

      V
      vikctelAuthor
      December 5, 2024

      Thank you so much!!! We are heavily invested in the employee time imports that losing this ability was going to hurt us greatly. Your solution worked (and I didn't have to spend hours with Intuit tech support only to get no where).

        Terms & ConditionsAccessibility statement