web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Massachusetts Sick Law and leave transaction calculations

(0) ShareShare
ReportReport
Posted on by

Microsoft Dynamics GP calculates and limits sick time accrual to 40 hours per year in accordance with Mass Sick Leave (MSL) Law.  The program then carries unused sick time over to the new year.  Where the program falls short is not being able to limit the time taken in the 2nd and proceeding years to the maximum of 40 hours.  For example an employee earns 40 hours in the last sick year, uses 20 hours in that year and carries over 20 hours.  Now the employee has a potential 60 hours that may be available once they earn 40 hours in the next year.  Per MSL the employee cannot take any more than 40 hours in any given year.  I'm told the program could potentially pay the employee 60 hours and the only way to prevent this is to check each employee's leave transaction information before they are paid.  This does not seem practical or cost effective.  As a mater of fact it seems to disregard why one would even have designed such a limited application.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Sherlene Sorenson Profile Picture
    967 on at

    Hi Anodyne,

    I haven't had to work with clients with this type of requirement yet, but it is an unusual requirement for sure. The product options I've seen will limit the amount of the maximum balance allowed in the account, and can limit how much can be accrued in any one year, but the requirement to limit how much actually gets paid out in one year is very different from what I've ever seen. Have you looked at the Integrity Data Comprehensive Leave Product? If any of them would have this feature, that is the one I would guess might do it.

    One way around this might be to grant the 40 hours for the year as a lump sum at a set time, rather than accruing into the account per pay period.  That way, you'd only have 40 hours in the account for the year to work with for payouts.

  • Community Member Profile Picture
    on at

    Hi Sherlene,
     
    We are a temp agency and granting the 40 hours is not viable.  We have over 1,000 employees and many do not earn 40 hours.  We have Integrity for the ACA, dynamics payroll inspector series.  Integrity told me they cannot meet this requirement currently and additionally their current product is calendar year based.  We are on a fiscal year 7/01 - 6/30.
     
    Thank you, I appreciated your suggestions and I welcome any other thoughts!

  • Sherlene Sorenson Profile Picture
    967 on at

    Sounds like you would need to use a report or develop a custom process to verify how many hours have been previously paid out for the fiscal year. I'm not coming up with any great ideas on how to do that, but am interested in what others may contribute!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans