I have been on support calls for at least 20 hours.  My case number is [removed].  Payroll is not the only issue.  However, to answer your question, I get this error message when trying to send my payroll and when simply trying to "send payroll data" to see if there is a connection.  I have also received error message 2108.  I have been promised call-backs at least 6 times and no one has called when promised or at all.

I have been on support calls for over 20 hours.  This is not my only problem since converting to QB Desktop Pro 2021.  My case number is [removed].  To answer your question, this error code occurs when I am trying to transmit my payroll.  It also occurs when I hit "send payroll data" to determine if there is a connection.  I have previously received other error messages including 2108. I have been promised call-backs from level 1 and level 2, but the calls never come or come hours later than promised, after hours.  This is obviously a pervasive QB issue.  What is the solution?

I understand how hassle it would be to encounter issues on your file, LawOfficeofLindaB.

You have me to help you isolate what causes the error you received.

First, let's ensure that your QuickBooks Desktop is updated to the latest release.

Second, if it's updated, we'll have to configure the set up of your Intuit Data Protect (IDP). Let me guide you with these steps:

1. On your keyboard, press the Windows key and then type Firewall.
2. Select Allow an app through Windows Firewall.
3. Click Allow another app.
4. Click Browse and then go to Program Files(x86)\Common Files\Intuit\Data Protect.
5. Add each file.
6. The Network Types should be Private.
7. Click Add.

Then, we're good to add the IDP to the list of trusted sites. Here's how:

1. Press the Windows keys on your keyboard.
2. Type Internet Options.
3. Go to the Security Tab and then select Trusted Sites.
4. Click Sites and add IDP and Intuit websites to the list.
5. Click Close.
6. Select OK.

I've also added this guide on how you can send payroll: Before sending payroll to Intuit.

Let me know how these steps work on your end. I want to ensure that this gets resolved. I'll be around.

I had to switch payroll companies.  I am 30 days in and still can not submit my payroll.  I cannot believe a company can get away with this.  I have spent over 70 plus hours on the phone and no one can help.  Absolutely ridiculous.  Shame on your guys.  

There is no solution.  Change companies.

I too have done everything listed above MULTIPLE TIMES.  I have this odd feeling that you guys have been hacked and cannot figure out the virus.  Anyone reading this, find a new company.  There is no other choice.

I have been working on the same issue for over 30 days.  I was just told there is no fix.

I moved to another payroll company.

Not sure if this will work for anyone else but, I was having the same 2107 error when trying to send payroll.  All I had to do was turn off my payroll cloud services and the paychecks transmitted successfully.

I was able to fix this by turning off my payroll cloud services.  Not sure if our issues are the same but I also was getting the 2107 error.

@Jenn1918 wrote:

Not sure if this will work for anyone else but, I was having the same 2107 error when trying to send payroll.  All I had to do was turn off my payroll cloud services and the paychecks transmitted successfully.

---

I think this just worked for me as well! I had already swithced the direct deposits as manual checks, but I had 5 weeks of "0.00" payrolls that would not transmit. I just turned off the Quickbooks Workforce, found in the payroll cloud services and everything transmitted. I will try again next week when I have actual payroll to submit and report back. Thanks!

Thank you for posting this Jenn1918!!!!  I have been working on this error 2107 for about a month, probably spent 20 hours on the phone with QB, was promised call backs from supervisor's which did not happen.  They kept on putting me off...Horrible customer service.

Your fix worked!!!! I turned off the payroll cloud services.

Same here.  SO frustrating.  I have had this happen before where I tried so many times in different ways and then they put a HOLD on the account.  To me this is what needs to happen regardless if they fixed error 2107

NO good support person that deals with HOLDS.  Frustrating.  looking for answers

Thanks for joining this thread, Susanschmeisser.

I recognize the importance of being able to use the direct deposit service. This can save your time since you’ll no longer have to manually pay your employees. Let me route you in the right direction to help you get back on track using the feature mentioned above.

I can see that you’ve already reached out to our Payroll Support Team about the issue. I still suggest contacting them again. They have the necessary tools to find which paychecks are causing the error 2107. Once identified, our specialist will be able to remove the hold on the account.

Let’s open your company file and go to the Help menu to get the support information. Here’s how:

1. Click the Help menu at the top bar and select QuickBooks Desktop Help F1.
2. Scroll down to the bottom of the window and tap the Contact us link.
3. In the Contact Us screen, go to the Tell us more about your question section and enter the issue in the field box (error 2107).
4. Press the Search menu and choose the support options: Call us to speak with an agent or Message Us for real-time support.

I know that my colleague already shared this article on the previous thread: Troubleshoot Payroll Service Server Error or Payroll Connection Error. I’m still adding this one here for additional resources. It outlines the complete instructions on how to resolve any payroll service connection error.

Also, this link contains resources that will guide you on how to easily manage any payroll tasks in QuickBooks: Self-help articles. From there, you’ll learn about processing forms, taxes, account management, etc.

Keep me posted if you still have concerns about direct deposit. I’m always ready to help and make sure this is taken care of for you.

YES!!! Turning off Payroll Cloud Services also worked for me!  Thanks for the help.  QB Customer Service was TERRIBLE!!

I don't understand why QB support can't suggest turning off cloud services as a work around until they get this fixed. I was only on the phone with support for 4 hours and while the agent did some good things, the problem was not resolved. I can't help wondering if this is an effort to push desktop users to online. . .  

Same issue for us. With ours it begin with an updated to Enterprise 22. So far I've been working with customer support for 5 weeks, over 15 hours on the phone.  They keep trying to say it's almost fixed.  At this point the assurances are laughable.  

I do feel like I'm inching closer to a solution.  The turning off the cloud thing didn't work for us.  Neither did updating 87 times with tech support on the phone or any of the other fixes the support agents tried.  Eventually they had to install new PSID number, which reset our account.  After that we could transmit again but the account was locked, so that was another call to support and a form that had to be faxed in.  Once the password issue was resolved, the send payroll data function works but direct deposit is no longer activated.  For some reason the software thinks it is active so the add direct deposit options don't appear in my menu, but the back end says QB (so unhelpfully) deactivated direct deposit as part of their fix.  I'm now in the phase of waiting for the back end to reactivate our bank account.  I was told it would take 2 days to complete, that was 10 days and 7 calls ago.  Who knows if it will ever be done. 

Every time I have to call QB support, I feel like they reach a new low in the support they provide.  My employees and the company CEO are getting pretty annoyed with the broken direct deposit, so we will probably end up switching to another payroll provider if the issue isn't resolved this week. 

Turning off  payroll cloud services worked for us too!!  After being on calls for 2 days and countless hours, I read this thread and recommended your suggestion while on the line with the QB representative.  It worked immediately.  We don't know what issues it may have caused going forward but we are glad to see that the payroll appears to have been sent out.  However, it will be a day or two late getting to our employees. This is something that is unacceptable and will have us looking into other products for payroll services. 

Thank you so much for posting this remedy!! 

This definitely works, just worked for me 🎉

My cloud service was OFF, but all I had to do was turn it ON and then turn if OFF. Who writes software like this? Terrible. Quickbooks is the Roach Motel of all software. 

Hi

I hope the suggest solution steps will surely help to resolve the QuickBooks payroll error 2107. However if still anyone is having payroll error 2107, So that case i would suggest to mentioned solutions steps to resolve error right away.

Comprehensive steps to fix Error 2107 in QuickBooks 

The number to dial is [Removed] for QuickBooks payroll support and support service are available from [Removed]. One of the great things about contacting support that fees you won't have to wait for your turn in queue...

I can see the urgency of getting your issue resolved, @Ben23_1. I'm here to help you so you can send payroll.

The payroll error 2107 happens when you fail to send employee salaries via Direct Deposit (DD). And the most causes of this are the following: 

• General internet connection issues and invalid security certificates.
• Internet security and personal firewall software settings.
• Incorrect system date and time properties.
• Sending in multi-user mode.
• A network time-out prevents QuickBooks Desktop (QBDT) from connecting to the server.

To have the most recent security patches and bug fixes, we need to ensure that your QuickBooks Desktop account and payroll tax table are updated. After that, send payroll again. But if you encounter the same issue, I suggest performing the additional steps indicated in this article: Troubleshoot Payroll Service Server Error or Payroll Connection Error.

However, if you're done performing the above steps, this time, I recommend contacting our Customer Care Team. They have the tools to pull up your account to investigate the root of the problem and why the issue keeps appearing.

Here's how to reach them:

1. On your QuickBooks account, go to the Help menu at the top.
2. Tap QuickBooks Desktop Help.
3. Choose Contact Us.
4. Give a brief description of your issue.
5. Click Let's talk and then choose a way to connect.

For more info about our contact options and support availability, see this article: Contact QuickBooks Desktop support.

Feel free to get back to this thread if you need more help. We're just one comment away. Keep safe!

Hi Ben23_1,

I was finally able to get my payroll submitted, but with no help from QB customer service!  Hopefully this will work for you, go to employees and select Payroll Cloud Services TURN OFF the QB Workforce.  You will have to turn this back on when making updates to QB.

Hope this works, TW787

Ben23_1,

I finally got my payroll submitted with no help from QB customer service!!  I hope this works for you, go to employees and select Payroll Cloud Services TURN OFF QB Workforce.  I believe you will have to turn this back on when making updates.  Hope this works for you!!!

TW787

Thank goodness the other people on here, NOT INTUIT, have the answers because INTUIT hung up on me twice over this exact issue, error 2107. After walking me through their updates and having no answers, they just hung up, twice!! They didn't call me back after my request. I was so lost! I was freaking out that I had to do payroll and Intuit just had no answer. So horrible, worst customer service.  

Yes, the answer is to TURN WORKFORCE OFF (Manage Payroll Cloud Service.)  Problem fixed. Apparently that's not a popular fix for the Intuit customer service people to tell you when you desperately need answers.

Shame on you INTUIT.  I used to think your products and service was good ( 15 years ago ) but your not the same company anymore.