Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We have a worker who was exempt from FICA and Medicare taxes through the first half of 2019 and was receiving pay checks throughout this time period. Now this worker is no longer exempt and must pay these taxes starting in July 2019.
In the worker's first check in July - the software is attempting to "catch up" on all of the FICA and Medicare taxes and is causing the worker to have a 0.00 pay statement due to the large tax amounts for FICA and MEDI that are in the pay statement.
The FICA and Medicare tax codes on the worker record had their original "version" expired AND a new version was entered to start on the July pay period. However, this does not seem to have affected the tax "buckets" for this worker within the tax engine.
The only way that I know of to get around this would be to create a brand new worker record which would then reset the tax bucket dates to July. If possible, I would like to avoid creating a brand new worker record but, in my mind, this looks like a bug BUT has anyone experienced this issue and got around it?
Not sure if there are many payroll tax experts active on this forum. You thus might have to consider opening a support case with MS to get some feedback from them.
Business Applications communities