Statutory Holiday Pay

QBO "updated" the way the stat pay functions in payroll. It is now dysfunctional There are a couple of other conversation threads about this here in the community. QBO says they are working on a solution...meanwhile we are all stuck having to manually calculate the lump sum for the average day's pay as there seems to be no other way around it.

Hi there 1425306515,

It's important that all your transactions are correctly entered for your books to be balanced. QuickBooks Online Payroll is a great tool able to help you pay your employees by direct deposit or by cheque for the hours they've worked. I can point you in the right direction for assistance with your pay run.

If your pay is incorrectly calculated, I recommend reaching out to the QuickBooks Online Payroll support team outside of the Community. They'll be able to view the pay with you in the system to make sure it's calculated correctly so you can pay your employees the right amount. You can reach them using these options:

Schedule a Callback or start a Chat: click (?)Help in the upper right > type and enter "Contact support" into the QB Assistant > click Contact Us > explain your situation > click Let's Talk > choose Get a callback or Start a Chat.
Social Media direct message: Facebook and X / Twitter

If you have any other questions, feel free to reach out here.

Thanks for your message.  I actually found a way around it for now.  When you go to pay your employee, instead of entering the stat hours (say 8.5), I just filled in the amount it would equal under stat-pay average daily wage.  It comes out to the right amount then - it just doesn't show the hours.  Best I could come up with for now.

Additionally, the hours are not added in for stat pay.  It's a lump sum amount for stat pay, which you have to calculate yourself.  This means ROEs will also be incorrect in calculating the number of hours worked.  

Be aware using the stat pay - average daily wage.  In the past when you put in the employees stat pay hours it would reduce the salary hours by the same amount.  Now when using the average daily wage it says in a pop up that can easily be missed - "Be sure to reduce the salary hours in the salary column to help ensure the pay is correct".  If you don't make the change the employee will get a nice little bonus.  This is such a bad product release.  Is there any user who thinks this is better?  Am I missing something of why this needed to be changed.

Hi SevenClark,

Thanks for joining this thread. It's essential that the statutory holiday pay is correctly recorded in your QuickBooks Online account to keep track of your books. I'd be glad to help.

I can see how important it is to have the right statutory holiday pay. I recommend that you send us Feedback by clicking on the Gear icon at the top. This is sent to our Development Team to consider for future updates.

Let me know if you have questions, I'll be happy to help.

Hi JZ1972,

I appreciate you getting back to us here.  Many QuickBooks Online customers have expressed their concerns with the logic behind the update with the statutory holiday pay.  Your voices have been heard and our Development Team is working diligently on improving and perfecting the payroll platform.  In the interim, as mentioned above, when you run payroll, you'll need to do the calculations and enter it into the Average daily wage field. This will ensure the amount is accurate. Whereas, entering it into the Premium field, will calculate it at 1.5. I hope this helps!

If you have additional concerns or questions, feel free to get back to us here.  We would be glad to assist!

In response to "Your voices have been heard and our Development Team is working diligently on improving and perfecting the payroll platform"... okay, PLEASE put the stat pay back to the way it was before the change.  It worked, it was easy to understand and there was no need to make any changes to it. 

I'm fairly certain I'm not the only user who would really would like the Development Team to start working on things that actually need improvement.  Transparency on what the Development Team is working on and how it affects users BEFORE the changes are actually made would be an awesome thing to consider.  

Thanks Henock K, I have submitted so many 'feedback' posts to the Development team using the gear icon over the years that my folder is full of the token automatic replies thanking me.  For this issue I have provide 2 feedback comments.  I now believe the feedback button is useless compared to my experience with other software providers.  For example, I have made many feedback issues to 'DocuSign' which result in a remote meeting with a Developer or Tester and a webex session where I share my screen to  provide feedback on the issue and DocuSign will follow up usually in a few weeks with an improvement or resolving the issue.  I have never once received an email or callback from Quickbooks.  Calls to the nice support team can be a time consuming waste unless I need a quick yes or no answer.

Trish_T or any other QB team member, 
Why was this change made? Why was the ability to track hours removed from a pay type that requires hours to be tracked? Why was an update that muddles historical pay information allowed to go through? I hope the powers that be at QB are asking these questions and that they reconsider their processes for rolling out updates in the future. After the fact "Give us feedback" and "We're listening to you" is not acceptable for anything other than aesthetic changes. 

This is a terrible update. 

We are required to report hours for statutory holidays, and with this, we can only add a lump sum, or pay premium. Just because someone is working on a stat does not mean that they are entitled to premium pay. That is up to us to determine for each employee. We typically add the hours they're entitled to, and then it correctly calculates. It affects ROEs, which would now require manual calculation and adjustment. Where is the old hour tracking? Why would the hours now be completely lost? 

This is a complete make work project for us, coming at the worst possible time of year. 

Why would this have changed without advising us? If QB wanted to add an average daily calculation, then add a different field for people to use, NOT change the one that works in a different way, to in essence break it. We cannot actually correctly use the payroll. It's so frustrating.

As also noted by someone else, we do not have the ability to edit this to fix it ourselves. Please change it back. ASAP. The stock answers by QB are not enough. 

This is a terrible update. 

We are required to report hours for statutory holidays, and with this, we can only add a lump sum, or pay premium. Just because someone is working on a stat does not mean that they are entitled to premium pay. That is up to us to determine for each employee. We typically add the hours they're entitled to, and then it correctly calculates. It affects ROEs, which would now require manual calculation and adjustment. Where is the old hour tracking? Why would the hours now be completely lost? 

This is a complete make work project for us, coming at the worst possible time of year. 

Why would this have changed without advising us? If QB wanted to add an average daily calculation, then add a different field for people to use, NOT change the one that works in a different way, to in essence break it. We cannot actually correctly use the payroll. It's so frustrating.

As also noted by someone else, we do not have the ability to edit this to fix it ourselves. Please change it back. ASAP. The stock answers by QB are not enough. 

I wonder how many customers haven't noticed this update? I noticed it by pure luck and only did one paycheck this way but I'm still overpaid my employees $1500. I can't imagine companies with more employees. Who wanted this??? I'm on chat with them right now trying to get an answer for it. Right now the answer is "This is acutally based on most of the customer's feedback." Ummm, who is writing in to Quickbooks requesting them to have Stat holiday pay time and a half???

Personally, I would appreciate having a specific "Stat Holiday Premium" pay option so that stats worked don't get lumped in with other overtime (I didn't provide any such feedback though) but that would be in addition to the other one not instead of it and certainly not overwriting it. I can't fathom how anyone thought that was a good idea. 

This is EXACTLY what happened to me.  I didn't notice it, as on my screen the columns are too narrow for the entire heading to be displayed. I noticed after the fact that I overpayed my employees by hundreds of dollars by inadvertently using the stat pay premium column.  It has appeared on more than one occasion now that the people creating the software do not understand the requirements of the law or the ins and out of accounting, and are making things harder for the user.  I hope they reverse this change and listen to their users.