If your Payroll suddenly stops working or sending data to Intuit (for direct deposit, as an example), and you recently restored a Company backup file, your problem could be a failed match between the security ID originally recorded for your Company file when you first installed your Payroll subscription, and the security ID recorded in the Company file you restored from the Backup file.
When you back up your Company File and restore it as your new working file, which could happen for many different reasons, the newly restored Company file may have a situation where the PID (security code) is different.
When you attempt to connect the new Company File (you restored from the Backup) to your Payroll subscription, you could find your Payroll application within QuickBooks will not connect to the Intuit server for payroll updates.
In some instances, you might not be unable to transmit your Company Paycheck to Intuit's server for direct deposit.
Unless you find yourself working with a tech savvy QuickBooks Payroll Technical Support Representative, this issue might go unnoticed. You see, the error will not be displayed at your end of the equation.
What I mean is if you are trying to update Payroll or send Paychecks, the application just stops. It doesn't even display an error code.
I tried looking through QBWin.log files and one of the Payroll update folders that contain transmittal logs and found absolutely no reference to the problem for a client recently experiencing the problem.
Fortunately, I was able to reach a tech savvy Intuit Payroll Tech who went almost immediately to the problem and found it at their end, even though others had failed to do so.
The error or exception message is akin to: Error: Recorded pid ######## does not match the current pid ########.
You need to make good mental or written notations of this potential issue so it will get to the attention of any future support reps you might have to contact should you (or a client) is hit with this issue.
It might save you time going through this, that or the other, like testing internet speed, firewall settings or other internet security protocols, or file too big, and other issues far, far away from the actual cause.
The sooner the error/exception message is found at their end of the equation and sent off to Level 2 or Level 3 support to reset the recorded pin within Intuit's Payroll servers to match the current pid within your Company file, the sooner the problem will be resolved.
Unfortunately, you won’t find this error displayed except on the receiving end of the equation if you find an Intuit QuickBooks ProAdvisor Desktop Payroll Tech Support Rep who knows their stuff, like JaLeisa based remotely in Arkansas.
Like what you're reading?
Subscribe to our FREE newsletter and we'll deliver content like this directly to your inbox.