Finance | Project Operations, Human Resources, ...

Duplicate Entry in ACH file and direct deposit history tables

(0) Share

Report

Posted on by beheiple

For several pay periods a duplicate direct deposit is being created for the same employee in the ACH transmittal file and in the Direct Deposit ACH Items (DD10500) and the Direct Deposit Transaction History Detail (DD30101) tables It is easily fixed by removing the duplicates. I need to determine why this happens and fix the cause of the issue.

Only one employee is being effected by this and I cannot confirm, but it seems the issue began after upgrade to Dynamics GP 18.3. There does not appear to be anything incorrect on the employee setup..

Has anyone ran into this and did you solve it?

Categories:

Microsoft Dynamics GP

All responses (3)

Answers (0)

HT-08101531-0 2 on at

Like (0)

Report

Duplicate Entry in ACH file and direct deposit history tables

Hello - We are experiencing this same issue and do not have a solution after following the suggestions in these posts. Does anyone have a new solution they can share? Thanks!

Update - 10.18.24
I removed the old payroll files from the ACH window - that seemed to fix our issue!
jechegoyen 50 on at

Like (0)

Report

RE: Duplicate Entry in ACH file and direct deposit history tables

Hi Terry - I have a similar issue with a client, but I am not sure what you mean by by the next step. Are you referring to the bank accounts in the direct deposit window or some other account field?

Next for this employee, take a screen shot of the current accounts you have active or want in there.

Then delete all the employee accounts and save out of the window so it is blank.

Now go back in and key your active accounts, run the next payroll and see if this now works for you.

Thank you,

Jackie
Suggested answer

Terry R Heley Microsoft Employee on at

Like (0)

Report

RE: Duplicate Entry in ACH file and direct deposit history tables

Hi Brian, this is not something we typically see, but there could be something stuck in the tables for this one employee.

Here are the steps I would take.

First in the generate ACH window on a week that is a non-payroll week, I would remove all "old" payroll files from this generate window.

Since all the files have been sent to the bank, there is no reason to leave them hanging out there. We have also found with larger payrolls that this could cause performance issues during the posting process, so I would just have 1 week back in this window.

Next for this employee, take a screen shot of the current accounts you have active or want in there.

Then delete all the employee accounts and save out of the window so it is blank.

Now go back in and key your active accounts, run the next payroll and see if this now works for you.

Thanks

Terry Heley

Microsoft