Get 50% OFF QuickBooks for 3 months*

Buy now
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Work smarter and get more done with advanced tools that save you time. Discover QuickBooks Online Advanced.

Reply to message

View discussion in a popup

Replying to:
ChiefBridgeFuser
Level 3

Reply to message

No, I'm not wasting time on a call with you to do something that I will have to wait two weeks to see if it fixes a problem that probably wouldn't have been fixed anyhow.  @tammylucero identified, on her own, the the problem that makes this happen!  Like I've said in this thread already, Intuit support for this horrible product is horrible and robotic.

As Tammy has identified, the problem preventing generating employee paystubs in this case is the presence of curly braces in the employee name.  In her case, removal of the text in the curly braces is possible without creating another problem.

I've tested this by removing the curly braces in this employee's last name field, replacing it with "-Empl" and confirmed that the {}'s are what is causing the failure to generate the PDF/email the PDF.

In our case, a fix for this isn't as simple as just removing those {}'s:

This particular employee was a contractor a long time ago.  As such, he exists in the Vendor List as his legal name.

When he was added as an employee without the {employee} at the end of his last name, a dialog box pops up saying, 'This name is already in use in the Vendor List. To differentiate, after the last name add a space and any character string in curly brackets, e.g., Smith {engineer}.  Note: The name in the "Print on Checks as" field will be used on checks, and the First, M.I., Last Name fields will be used on tax forms, without the curly braces or text inside the curly braces.'

This direction from Intuit QB (probably back in about 2010 or so) is why we have that there.

When I removed the {employee} text and replaced it with "-Empl" as an experiment, I received another warning to "Please make sure that this information matches the employee's current social security card."

As it stands now, with this $800 stinking pile of Poo, I have two choices:

1) Submit information to the IRS with an incorrect name.

2) Generate and send a paystub for this employee.

This is clearly a bug that was introduced sometime after QB 2020 and on/before QB 2023: QB can no longer work with something that it tells you to do with an employee name!

Please proved me with a date as to when I can expect to see an update to correct this bug.

Image file with warning dialog images attached.

 

Need to get in touch?

Contact us