--- title: New Overtime Pay Requirements Released by the Department of Labor description: U.S. Department of Labor DO) announced Notice of Proposed Rulemaking NPRM more than million American workers eligible overtime proposal update salary threshold current wage data projected through January 1st, 2020 result boosting standard salary level from $455 to $679 per week $35,308 per year image: https://blog.proliant.com/hubfs/sharon-mccutcheon-552616-unsplash.jpg --- [![Proliant - Print Logo - No Strokes](https://blog.proliant.com/hubfs/01%20-%20Website/Logos/Proliant%20-%20Print%20Logo%20-%20No%20Strokes.svg "Proliant - Print Logo - No Strokes")](https://www.proliant.com) [Request Meeting](https://www.proliant.com/request-meeting) ** ** **Payroll** **Talent** **Workforce Management** **Benefits** **Platform** **Integrations** **ProLiant Mobile** Your employees can stay connected. **Anytime, anywhere**. ![proliant-mobile-mockup-mega-menu](https://blog.proliant.com/hubfs/01%20-%20Website/4%20-%20Main%20Pages/Home/proliant-mobile-mockup-mega-menu.png "proliant-mobile-mockup-mega-menu") [![Proliant - Print Logo - No Strokes](https://blog.proliant.com/hubfs/01%20-%20Website/Logos/Proliant%20-%20Print%20Logo%20-%20No%20Strokes.svg "Proliant - Print Logo - No Strokes")](https://www.proliant.com) [Request Meeting](https://www.proliant.com/request-meeting) ** ** **Payroll** **Talent** **Workforce Management** **Benefits** **Platform** **Integrations** **ProLiant Mobile** Your employees can stay connected. **Anytime, anywhere**. ![proliant-mobile-mockup-mega-menu](https://blog.proliant.com/hubfs/01%20-%20Website/4%20-%20Main%20Pages/Home/proliant-mobile-mockup-mega-menu.png "proliant-mobile-mockup-mega-menu") Search **Menu** ** ** [Request Meeting](https://www.proliant.com/request-meeting) ![](https://blog.proliant.com/hubfs/sharon-mccutcheon-552616-unsplash.jpg) # New Overtime Pay Requirements Released by the Department of Labor [![ProLiant](https://blog.proliant.com/hubfs/Logos/Color%20Proliant/P%20logo%20Glassdoor.jpg)](https://blog.proliant.com/compliance-updates/author/proliant) Written by [ProLiant](https://blog.proliant.com/compliance-updates/author/proliant) Mar 8, 2019 12:32:19 PM On March 7th, 2019 the U.S. Department of Labor (DOL) announced a Notice of Proposed Rulemaking (NPRM) that, if passed, would “make more than a million more American workers eligible for overtime.” (U.S. Department of Labor, 2019) The proposal would update the salary threshold using the current wage data (projected through January 1st, 2020) with the expected result boosting the standard salary level from $455 to $679 per week, aka $35,308 per year. For some background, the current law for employees with a salary below $455 per week, $23,660 annually, receive overtime pay if they work more than 40 hours per week. This salary threshold was set in 2004. This adjustment comes from a 2017 Request for Information (RFI) from the DOL and includes public input from “6-person listening sessions held around the nation and more than 200,000 comments.” (U.S. Department of Labor, 2019) Secretary Alexander Acosta says, “Our economy has more job openings than job seekers and more Americans are joining the labor force. At my confirmation hearings, I committed to an update of the 2004 overtime threshold, and today’s proposal would bring common sense, consistency, and higher wages to working Americans.” Keith Sonderling, Acting Administrator for the Department’s Wage and Hour Division, adds “Comments on the RFI and in-person sessions overwhelmingly agreed that the 2004 levels need to be updated.” (U.S. Department of Labor, 2019) The NPRM will keep overtime protections for the following: police officers, fire fighters, paramedics, nurses, and laborers including non-management production-line employees and non-management employees in maintenance, construction, and similar occupations such as carpenters, electricians, mechanics, plumbers, iron workers, craftsmen, operating engineers, and longshoremen. This proposal does not apply for automatic adjustments to this salary threshold. You can find more information on the NPRM at [www.dol.gov/whd/overtime2019](https://www.dol.gov/whd/overtime2019) and you can submit comments regarding this proposed rule at [www.regulations.gov](http://www.regulations.gov/).         # Bibliography U.S. Department of Labor. (2019, March 8). *U.S. Department of Labor Releases Overtime Update Proposal*. Retrieved from U.S. Department of Labor: https://www.dol.gov/newsroom/releases/osec/osec20190307     ## A Great Offer, Just a Click Away Lorem ipsum dolor sit amet, consectetur adipiscing elit ![](https://cdn2.hubspot.net/hub/273774/hubfs/mp/themes/Act-Theme/images/act-sample-opa1.jpg?width=900&name=act-sample-opa1.jpg) ### About ProLiant *ProLiant puts the human in human resources. We provide a fully integrated, cloud-based HCM solution that simplifies payroll and HR processes. The company serves small to large clients in multiple industries in all 50 states and is committed to providing the highest quality customer service in the industry.* ### Subscribe to Blog - [Recent](https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor#recent) - [Topics](https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor#topics) - [Archive](https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor#archive) - [Benefits Administration (1)](https://blog.proliant.com/compliance-updates/tag/benefits-administration) - [Compliance (11)](https://blog.proliant.com/compliance-updates/tag/compliance) - [Industry News (2)](https://blog.proliant.com/compliance-updates/tag/industry-news) - [Tax Services (1)](https://blog.proliant.com/compliance-updates/tag/tax-services) [More...](https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor#) - [June 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/06) - [May 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/05) - [April 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/04) - [March 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/03) - [February 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/02) - [January 2026 (1)](https://blog.proliant.com/compliance-updates/archive/2026/01) - [December 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/12) - [October 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/10) - [September 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/09) - [August 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/08) - [July 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/07) - [May 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/05) - [April 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/04) - [March 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/03) - [February 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/02) - [January 2025 (1)](https://blog.proliant.com/compliance-updates/archive/2025/01) - [December 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/12) - [November 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/11) - [October 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/10) - [September 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/09) - [August 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/08) - [July 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/07) - [June 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/06) - [May 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/05) - [April 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/04) - [March 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/03) - [February 2024 (1)](https://blog.proliant.com/compliance-updates/archive/2024/02) - [January 2024 (2)](https://blog.proliant.com/compliance-updates/archive/2024/01) - [December 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/12) - [October 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/10) - [September 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/09) - [August 2023 (2)](https://blog.proliant.com/compliance-updates/archive/2023/08) - [July 2023 (2)](https://blog.proliant.com/compliance-updates/archive/2023/07) - [June 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/06) - [May 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/05) - [April 2023 (1)](https://blog.proliant.com/compliance-updates/archive/2023/04) - [February 2023 (2)](https://blog.proliant.com/compliance-updates/archive/2023/02) - [January 2023 (5)](https://blog.proliant.com/compliance-updates/archive/2023/01) - [December 2022 (3)](https://blog.proliant.com/compliance-updates/archive/2022/12) - [November 2022 (5)](https://blog.proliant.com/compliance-updates/archive/2022/11) - [October 2022 (5)](https://blog.proliant.com/compliance-updates/archive/2022/10) - [September 2022 (3)](https://blog.proliant.com/compliance-updates/archive/2022/09) - [August 2022 (1)](https://blog.proliant.com/compliance-updates/archive/2022/08) - [July 2022 (1)](https://blog.proliant.com/compliance-updates/archive/2022/07) - [May 2022 (2)](https://blog.proliant.com/compliance-updates/archive/2022/05) - [September 2019 (1)](https://blog.proliant.com/compliance-updates/archive/2019/09) - [August 2019 (2)](https://blog.proliant.com/compliance-updates/archive/2019/08) - [May 2019 (2)](https://blog.proliant.com/compliance-updates/archive/2019/05) - [March 2019 (1)](https://blog.proliant.com/compliance-updates/archive/2019/03) - [January 2019 (2)](https://blog.proliant.com/compliance-updates/archive/2019/01) - [December 2018 (1)](https://blog.proliant.com/compliance-updates/archive/2018/12) - [September 2018 (1)](https://blog.proliant.com/compliance-updates/archive/2018/09) - [August 2018 (1)](https://blog.proliant.com/compliance-updates/archive/2018/08) - [June 2018 (2)](https://blog.proliant.com/compliance-updates/archive/2018/06) - [August 2017 (1)](https://blog.proliant.com/compliance-updates/archive/2017/08) - [April 2017 (1)](https://blog.proliant.com/compliance-updates/archive/2017/04) - [July 2016 (1)](https://blog.proliant.com/compliance-updates/archive/2016/07) - [December 2015 (1)](https://blog.proliant.com/compliance-updates/archive/2015/12) - [August 2015 (2)](https://blog.proliant.com/compliance-updates/archive/2015/08) [More...](https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor#) Previous Story [← E-Verify Has Resumed, Here’s What You Need to Know](https://blog.proliant.com/compliance-updates/e-verify-has-returned-heres-what-you-need-to-know) [** ](https://blog.proliant.com/compliance-updates) Next Story [Everything You Need to Know About the New EEO-1 Reporting →](https://blog.proliant.com/compliance-updates/everything-you-need-to-know-about-the-new-eeo-1-reporting) ** ## No Comments Yet Let us know what you think [![proliant-white-logo-no-strokes](https://blog.proliant.com/hs-fs/hubfs/0%20-%20Proliant%20Branding/ProLiant%20Logos/proliant-white-logo-no-strokes.png?width=205&height=40&name=proliant-white-logo-no-strokes.png "proliant-white-logo-no-strokes")](https://www.proliant.com/) **Headquarters** 1100 Abernathy Road, Suite 850 Atlanta, GA 30328 877.896.9523 [Need Help?](https://www.proliant.com/contact-us) [Login](https://www.readypayonline.com/Proliant/Login/Login.aspx?) Copyright © 2022 Proliant, Inc. All Rights Reserved. #### Solutions [Applicant Tracking & Recruitment](https://www.proliant.com/applicant-tracking-recruitment) [Time & Labor Management](https://www.proliant.com/time-labor-management) [HR & Benefits Administration](https://www.proliant.com/hr-benefits-administration) [Employee Onboarding](https://www.proliant.com/onboarding) [Online Payroll Services](https://www.proliant.com/payroll-services) [Payroll Tax Services](https://www.proliant.com/payroll-tax-services) [Performance Management](https://www.proliant.com/performance-management) [ReadyPay Today](https://www.proliant.com/readypaytoday) [Learning Management System](https://www.proliant.com/learning-management-system) #### Who We Serve [Your Industry](https://www.proliant.com/your-industry) [Integrations](https://www.proliant.com/integrations) [Partners](https://www.proliant.com/partners) #### Why Proliant [About Us](https://www.proliant.com/about-us) [News](https://blog.proliant.com/inthenews) [Careers](https://www.proliant.com/careers) [Automation](https://www.proliant.com/payroll-automation) [Workflows](https://www.proliant.com/hr-workflows) [Services](https://www.proliant.com/services) #### Legal [Legal](https://www.proliant.com/legal-notices) [Terms](https://www.proliant.com/terms-of-use) [Privacy](https://www.proliant.com/privacy-policy) [Form 1095-C Notice](https://www.proliant.com/employee-1095c-notice) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "ProLiant", "url" : "https://blog.proliant.com/compliance-updates/author/proliant" }, "dateModified" : "2023-10-25T15:26:32.659Z", "datePublished" : "2019-03-08T17:32:19.000Z", "headline" : "New Overtime Pay Requirements Released by the Department of Labor", "image" : [ "https://blog.proliant.com/hubfs/sharon-mccutcheon-552616-unsplash.jpg" ], "mainEntityOfPage" : { "@id" : "https://blog.proliant.com/compliance-updates/new-overtime-pay-requires-released-by-the-department-of-labor", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.proliant.com/hubfs/00%20-%20Proliant%20Branding/ProLiant%20Logos/Proliant%20-%20Web%20Logo.svg" }, "name" : "ProLiant, Inc." } } ```