H.R. 6201 Families First Response Act & Sage 100 Payroll
The Families First Coronavirus Response Act, which includes the Emergency Paid Sick Leave Act and Emergency Family and Medical Leave Expansion Act, took effect in the U.S. on April 1, 2020,
Refer to the following Sage Knowledgebase article to assist you in complying with H.R. 6201: How do I set up to pay employees Emergency Paid Sick Leave and Emergency Family Medical Leave associated with the H.R. 6201 in Sage 100?
Please note, that as stated in the article, you will also need to Download Sage 100 Payroll 2.20.1 Program Fix PR6024T
We have updated the Sage 100 Payroll 2.20.1 Program Fix PR6024T to include a correction for the following:
Employer Expense Summary for the Deposit Liability page does not correctly subtotal the Federal Tax Liability section when using the 3 new tax rules for FFCRA-Emergency Pay earnings codes.
Download Sage 100 Payroll 2.20.1 Program Fix PR6024T
So it sounds like you're saying that PR6024T has been revised and now includes a fix for the Employer Expense Summary, is that correct?
Does this mean the issue where Taxes are incorrect when combining FFCRA earnings with other earnings types on same check and there are fixed deductions is also corrected?
If not, do you expect a fix for that soon? Will you re-issue an existing Hot Fix or publish a new one?
Thanks in advance
Yes you are correct, PR6024T program fix was revised to include fix for the subtotal on Employer Expense Summary.
Regarding issue when combining FFCRA earnings with other earnings on same check is what we are working on now. The issue was in the SPA calculation engine so there should be nothing to install (assuming you have installed the latest Payroll Tax Update). We will post when that update is deployed. ETA is later this week if all testing passes. Please use KB 104288 for the current workaround.
rclowe FYI a SPA tax calculation engine update was deployed yesterday, April 30, 2020 to address the issue when combining FFCRA earnings with other earnings on same check, please see KB ID 104288 for more details.