--- title: "New Draft Form W-4 Update: Confusion and Concerns Over Key Points" description: A continued discussion, and update, to the draft Form W-4 proposed changes announced by the IRS. Concern and confusion rise over the IRS's draft Form W-4 for 2019 and on. Reporting of wages earned from other jobs, nonwage income, anticipated item deductions, and more are not clearly defined. image: https://blog.proliant.com/hubfs/03%20-%20Blog%20Images/01%20-%20Proliant%20Blog/01%20-%20Feature%20Images/New%20Draft%20Form%20W-4%20Update-%20Confusion%20and%20Concerns%20Over%20Key%20Points.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/03%20-%20Blog%20Images/01%20-%20Proliant%20Blog/01%20-%20Feature%20Images/New%20Draft%20Form%20W-4%20Update-%20Confusion%20and%20Concerns%20Over%20Key%20Points.jpg) # New Draft Form W-4 Update: Confusion and Concerns Over Key Points [![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) Jun 14, 2018 4:00:00 PM Last week we spoke about the new changes the IRS is bringing to Form W-4 for 2019 and how they will affect payroll going forward. The primary change being discussed today is the elimination of personal exemptions from the tax code due to the new tax reform. Now that employers and employees have had time to read over the Form W-4 draft, many are confused by a number of parameters that are not, “clearly defined” according to Bloomberg Tax. The draft of Form W-4 includes several new fields for employees to report on wages earned from other jobs, additional nonwage income, anticipated itemized deductions, and the value of potential tax credits. The confusion is occurring due to the form not being clear on whether employees should use the new field for their highest paying job, or whether employees can chose to keep that area blank if they didn’t want to share personal financial information with employers. Unfortunately, this could cause major issues for employees if not addressed. Employees who chose to not report their highest wages earned, by leaving the field blank or recording a lower-paying job, “could result in no potential tax deductions applied against taxable wages for withholding purposes.” The IRS has provided an additional draft of rules and instructions for the new Form W-4 which does note that *only *the highest earner of a household is supposed to make use of these new fields in Form W-4. But all this does is raise more questions: employees are instructed to record “if you have more than one job at the same time”, but fails to clarify a time period for these jobs or if an employee is currently holding more than one job. Another point of confusion is based around a potential smaller group of employees, “nonwage income for independent contractors”, specifically those who serve in the position of director for several companies. The new nonwage field asks employees to report interest and dividends as reportable nonwage income, but such income is normally subject to withholding. Mary B. Hevener, a partner with the law firm Morgan, Lewis & Bockius LLP, adds, “A partner or contractor might have the highest paying job in the household. The new fields are only for the highest earner, so the lower-paid employees in such a scenario have no ability to account for additional offset amounts on the form.” Hevener concludes her thought, “The draft form eliminates the ability of married employees to instruct employers to withhold at the higher, single rate.” Add all of the above with the IRS’s decision to use older Forms W-4 with their withholding allowances into account 2019 and onward, and you have a recipe for mass-confusion within the payroll industry. Unfortunately, this confusion could cause employees to inadvertently commit perjury due to delaying withholding until the end of the year. Hevener claims this to be “perfectly acceptable” based on the current draft. She explains that current (before the release of the draft Form W-4) employees were required to project what was to be withheld for the year and report that amount on their W-4. The draft Form W-4 instructs employees instead to include amounts they want to be considered for withholding purposes. Thankfully, this draft Form W-4 is just that, a draft. There is still time for the IRS to make revisions and clarifications in order to help all employees and payroll departments. Has this new draft worried you as an employer or employee? Want to read draft Form W-4 for yourself? You can click [HERE](https://www.irs.gov/newsroom/updated-withholding-calculator-form-w-4-released-calculator-helps-taxpayers-review-withholding-following-new-tax-law) to visit the IRS’s page and [HERE](https://blog.proliant.com/irs-introduces-major-alterations-to-form-w-4-for-2019) to check out our last blog which goes into greater detail on these new proposed changes.     # Bibliography Baer, M. (2018, June 11). *Bloomberg Insight Center.* Retrieved from Bloomberg Tax: https://www.bna.com/irs-draft-withholding-n73014476467/   ## 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-draft-form-w-4-update-confusion-and-concerns-over-key-points#recent) - [Topics](https://blog.proliant.com/compliance-updates/new-draft-form-w-4-update-confusion-and-concerns-over-key-points#topics) - [Archive](https://blog.proliant.com/compliance-updates/new-draft-form-w-4-update-confusion-and-concerns-over-key-points#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-draft-form-w-4-update-confusion-and-concerns-over-key-points#) - [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-draft-form-w-4-update-confusion-and-concerns-over-key-points#) Previous Story [← “Fair Work Week" Laws to Affect Payroll Processes for NYC Fast Food Restaurants.](https://blog.proliant.com/compliance-updates/fair-work-week-laws-to-affect-payroll-processes-for-nyc-fast-food-restaurants) [** ](https://blog.proliant.com/compliance-updates) Next Story [Pay Cards and Their History of Drama in New York →](https://blog.proliant.com/compliance-updates/the-new-york-paycard-cases-thus-far) ** ## 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-11-15T16:46:06.858Z", "datePublished" : "2018-06-14T20:00:00.000Z", "headline" : "New Draft Form W-4 Update: Confusion and Concerns Over Key Points", "image" : [ "https://blog.proliant.com/hubfs/03%20-%20Blog%20Images/01%20-%20Proliant%20Blog/01%20-%20Feature%20Images/New%20Draft%20Form%20W-4%20Update-%20Confusion%20and%20Concerns%20Over%20Key%20Points.jpg" ], "mainEntityOfPage" : { "@id" : "https://blog.proliant.com/compliance-updates/new-draft-form-w-4-update-confusion-and-concerns-over-key-points", "@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." } } ```