Microsoft Dynamics GP 2018R2: Shared Maximums for Benefits and Deductions

Microsoft Dynamics GP has added Shared Maximums for Benefits and Deductions for a calendar year in the release of GP 2018R2. 

The enhancement will take the worry and manual intervention out of over-deducting/contributing amounts on things like retirement and HSA accounts.

Here is how to set it up

1. There has been a new window added to GP to allow the setup of this limit. To set this up, navigate to Payroll/HR-->Setup-->Ded/Ben Shared Limit
2. To create a new group of deductions or benefits that share a calendar year maximum in the above window:

1. Enter a group code.
2. Enter a description.
3. Select the type of setup you are doing —Deduction or Benefit.
4. Enter the Calendar Year Max the benefits/deductions share.
5. Highlight and insert the codes that are to be included in this group
    a. A deduction can only be in one group at a time; if a deduction that is
       part of another group is selected, the user will get an error showing the
       other group it is part of.
6. Once all codes are selected, enter Save and this will save the group.

How to operate

Once a group is set up, the yearly maximum will be applied to all employees who are assigned to those deductions. This could mean that you must create different deductions and groups for employees who may have an exception to this calendar amount. For instance, employees over 50 can defer more to retirement plans than those younger employees on the same deductions/benefits.

If an employee is only assigned to one of the listed deductions/benefits, they will still be subject to this shared calendar year maximum.

All deductions included in the pay run will show on the Build Checks report, so no change there.

When the pay run is calculated, and the Calendar Year Max has been met for a group of deductions during the current pay run, GP will:

• Try to take the full deduction amount(s) for all TSA deductions first.
• Next try to take a full deduction amount(s) for sequenced deductions.
• Finally, GP will take the full deduction amount(s) for non-sequences/non-TSA deductions alphanumerically.

When the pay run is calculated, and the Calendar Year Max has been met for a group of benefits during the current pay run, GP will:

• Try to take the full benefit amount for taxable benefits alphanumerically.
• Next try to take the full benefit amount for non-taxable benefits alphanumerically.

Three new tables have been added to the SQL database for this functionality: UPR40950, UPR40852 and UPR40951

For more information

To learn more about what Wipfli can do with Microsoft Dynamics GP, visit our web page. 

To learn more about GP 2018R2, visit Microsoft’s blog.