Does your timekeeping software make it harder for you to comply with wage and hour laws -- and to defend yourself in a wage and hour lawsuit?
A study recently published in the Yale Journal of Law and Technology says that there are features of certain timekeeping programs that can create wage and hour problems for employers, and result in underpayment* of employees.
*Underpayment is also known as "wage theft," but I don't like that term and will not use it because it implies dishonest intent every time an employee is underpaid. There are lots of reasons employees may be underpaid, including ignorance of the applicable laws, mistake, and underreporting by employees -- not always in collusion with management.
Some of these same software features also make it more difficult for employers to defend themselves even when they paid the employee properly.
The authors of the study, in my opinion, are a little quick to assume that supervisors and managers (and employers) want to cheat employees out of their pay, but they do raise valid points. Here are some timekeeping system features for employers to watch out for:
Is it too easy for supervisors to edit employees' time entries? Some systems "prompt" supervisors when an employee's time entry seems excessive. I don't think that is necessarily a problem. As an attorney, I am a timekeeper, and our system lets me know if I post "too many" hours (in every case it's been because of a typo on my part -- for example, entering 24 hours when I meant to post 2.4 hours). Because I'm doing my own time, I know that I didn't really have 24 billable hours in one day (no lawyer jokes allowed!), so I know how to correct it to make an accurate entry. But when a supervisor is editing an employee's time, the supervisor may reduce the entry without the employee's knowledge or agreement. The authors argue that these automatic prompts may tempt supervisors to reduce employees' actual hours to meet budgetary goals.
Are edits "transparent"? This strikes me as a much more serious concern than the mere ability to edit a time entry. Any supervisor edits of employees' time entries should show up in the software, and the software should require the supervisor to include an explanation for the edit. (It should also show what the original entry was.)
Is there any accountability to the employee? Can a supervisor change a time entry without even notifying the employee? That's not good. According to the authors (citing behavioral studies), the chance of employer cheating (genuine wage theft) is greater if the supervisor isn't required to tell the employee about the change, much less explain it. Even in the majority of cases where the supervisor made an honest and legitimate edit but without notifying the employee, the chance is increased that the employee will later challenge the edit as improper. For all of these reasons, employees should be informed when their time entries are edited. Ninety-nine percent of the time (not an actual scientific figure), the employee is going to agree with the edit. But that one percent can be the acorn from which the oak of a wage-hour class or collective action will grow.
Beware of automatic "rounding." Yes, there have been some good court decisions lately on rounding of employees' time, as our own Sean Kramer has written. If the rounding results in no net loss, or only a minimal net loss, to the employee, it might be all right. But the authors of the study argue that rounding often results in more than a minimal net loss to the employee. Here's how it could happen, according to the authors:
An employer requires employees to be at their work stations and ready to go at their scheduled start times. The employer charges employees under its attendance policy for being tardy. The time clock is a few minutes away from the work station, so employees clock in a few minutes before their scheduled start times so they can be ready to work when scheduled. Their start times would normally be rounded to the "scheduled" start time, meaning they lose a few minutes every day. Employees who clock in a few minutes after the scheduled start time would also be rounded to the scheduled start time (a net gain for the employee), but they'll also be disciplined for being tardy, which means that most employees will not fall into this "net gain" category.
Something similar happens at the end of the day. Presumably, employees would be expected to stay at their work stations until the end of their scheduled work day. Anyone who leaves before the scheduled quitting time would be charged under the attendance policy for leaving early. The employees who work through the scheduled quitting time would actually clock out a few minutes after the end of the scheduled work day. So their time would be rounded back to the scheduled quitting time, resulting in a net loss for the employee. The employees who leave early would clock out a few minutes before the end of their scheduled work day, resulting in rounding up to the scheduled quitting time (a net gain for the employee). But, again, because of the possibility of discipline for leaving early, the authors posit that most employees would be in the "net loss" group.
In other words, according to the authors, most employees in this scenario would be losing several minutes of time a day through rounding, which could create wage and hour liability for the employer.
I've already run on too long, so next week I'll post about some things that employers can do to ensure that employee timekeeping is accurate.
Image Credits: From flickr, Creative Commons license. Time clock by Michael Coghlan; Wite-Out by Max Wei; two guys talking by Daliscar1.
- Partner
Robin has more than 30 years' experience counseling employers and representing them before government agencies and in employment litigation involving Title VII and the Age Discrimination in Employment Act, the Americans with ...
Robin Shea has 30 years' experience in employment litigation, including Title VII and the Age Discrimination in Employment Act, the Americans with Disabilities Act (including the Amendments Act).
Continue Reading
Subscribe
Contributors
- William A. "Zan" Blue, Jr.
- Obasi Bryant
- Kenneth P. Carlson, Jr.
- James M. Coleman
- Cara Yates Crotty
- Lara C. de Leon
- Christopher R. Deubert
- Joyce M. Dos Santos
- Colin Finnegan
- Steven B. Katz
- Ellen C. Kearns
- F. Damon Kitchen
- David C. Kurtz
- Angelique Groza Lyons
- John E. MacDonald
- Kelly McGrath
- Alyssa K. Peters
- Sarah M. Phaff
- David P. Phippen
- William K. Principe
- Sabrina M. Punia-Ly
- Angela L. Rapko
- Rachael Rustmann
- Paul Ryan
- Piyumi M. Samaratunga
- Robin E. Shea
- Kristine Marie Sims
- David L. Smith
- Jill S. Stricklin
- Jack R. Wallace
Archives
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010