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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP Garnishment taking too much

(0) ShareShare
ReportReport
Posted on by 2,520

I have a client with a Garnishment setup for an employee at $75 per week with a start date of 12/1/2015 and a court date of 11/10/2015.  the system took $286.87 on the first pay check it was active. 12/11/2015.  I can not see why it would do that.  Any ideas.  Screen shot attached of the Deduction setup. Garnishment-taking-too-much.jpg

*This post is locked for comments

I have the same question (0)
  • Lyn Barr Profile Picture
    1 on at

    There is probably something in the DIA (Deductions in Arrears) setup that caused this to happen.

    If you go to the system-level Deduction Setup window (Tools>>Setup>>Payroll>>Deduction), check whether any of the Arrears checkboxes are marked. - They're located pretty much in the middle of the window.

    You can also check the employee-level setup in Employee Deduction Maintenance (Cards>>Payroll>>Deduction). You'll see the same checkboxes, in the same location.

    If possible, I'd recommend voiding the check, clearing these checkboxes, and then reissuing it.

    If that is not possible, the system does allow negative deductions, which essentially repay over-deducted amounts.

  • Brenda Willey Profile Picture
    2,520 on at

    That was my first thought too but neither the employee deduction code setup not the company level deduction code setup have the Deduction in Arrear options on the screen.

  • Lyn Barr Profile Picture
    1 on at

    Is the pay code on a different frequency than the deduction? Does there happen to be anything set up in the Deduction Sequencing (not a likely culprit, but I'm brainstorming)? Does the employee have other garnishments? What do the settings look like in Garnishment Maximum Setup (Setup>>Payroll>>Garnishment Maximum Setup)?

    Also, I've seen instances where inactive employee activity was purged, and then ID numbers re-used for subsequent new hires. In that scenario, there was "false history" for the newly hired employees. Perhaps something like that could have occurred.

    You can potentially either make a one-time adjustment to correct the withholding, or perhaps repay it in its entirety and create a brand-new deduction code, to see if that resolves the problem.

  • Brenda Willey Profile Picture
    2,520 on at

    All of the paycodes and deduction codes have a frequency of weekly.

    Deductions are not sequenced

    Employee has no other deductions

    Maximums are setup but not included on the employees deduction.

    Employee is not new.  hire date 2009.  Garnishment for this employee is new.

    we can refund but I need to know why it happened so it does not happen again.

  • Lyn Barr Profile Picture
    1 on at

    That could be hard to identify, considering that everything within GP appears to be set correctly. I recommend you open a support case with either your partner or with Microsoft. They might be able to look at the records in your database tables, and see something that caused this.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
talty09 Profile Picture

talty09 2

#1
Anthony Beatty Profile Picture

Anthony Beatty 2

#3
CP04-islander Profile Picture

CP04-islander 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans