Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / How long should a payr...
Finance | Project Operations, Human Resources, ...
Unanswered

How long should a payroll run take?

(0) ShareShare
ReportReport
Posted on by howieb 50

Each week we process close to 14,000 payroll checks. They are broken down into groups. Each group is Built, calculated, printed and posted. The timing for a group of 6246 checks is taking 6 hours to from start to completion. Is that normal? Can someone comment on their timings for check runs of similar counts?

I will say we have MEM installed and also saving each check as a pdf image to a shared network drive using Mekorma. 

The posting of the check takes the most time at close to 2.5 hours.

Thanks

Categories:
Microsoft Dynamics GP
  • StefanieC Profile Picture
    StefanieC 432 on at
    RE: How long should a payroll run take?

    I would also run a test of a really small check run, like maybe 10 checks.  If you're having a slowdown with that few, maybe you could look at using PSTL to recreate the GL Index.  A LONG time ago, I saw that be a problem in an environment that had over 15,000 payroll posting accounts.  Of course, make a backup first.

  • Cheryl Waswick Profile Picture
    Cheryl Waswick on at
    RE: How long should a payroll run take?

    It is good to document those benchmarks and get those comparisons, even if it's a product that you cannot remove.

    Keep in mind, that it is going to matter how you 'disable' those products too.  The Customization Status window in GP may not always be good enough for those products with Add-ins.   If you got all users out of GP, renamed the GP code folder, and ran a REPAIR on the Microsoft Dynamics GP installation (Control Panel | Programs and features), it will create a new GP code folder that you can launch and rerun the checkrun without any 3rd party products in the picture.  Then run the checkrun again to get a benchmark of how long core GP is taking.  Then you can add the 3rd party products on to that one at a time and re-test in between to see where it slows down. 

    Hope those tips help. 

    Cheryl 
    Microsoft Dynamics GP 

  • howieb Profile Picture
    howieb 50 on at
    RE: How long should a payroll run take?

    Thank for the reply. We have spoken to Mekorma and they also said to look at the check image process. Unfortunately, it is a necessary 'evil' because that image is taken by another process (not a GP process) and moved to another server where the images are made available to our employee portal. We do not do the 14,000 checks in one run. They are broken down into three groups.

    On a whim, we did replicate a check run in our test environment with the mekorma pdf save process turned off. A check run of 1200 checks(1148 direct deposit and 72 live checks) did not see any appreciable time savings. We did not do a test run without MEM. If it is the culprit, it's something that we cannot remove from the mix.  

  • Cheryl Waswick Profile Picture
    Cheryl Waswick on at
    RE: How long should a payroll run take?

    A lot of factors come into play when processing payruns, so it would be hard for anyone to say or have an equivalent data scenario.   Other processes could be running that slows other processes down, etc.  The size of the data matters, what else is running etc (as you stated you have MEM).  I would assume the bulk of that time is to save each check as a pdf to your shared network.  How fast is your payrun if you do not do that?  You could do some testing and take benchmarks on how fast it is without MEM, how fast it is without Mekorma, etc....  If that is what is slowing it down, it may just take that long in your environment.  You may also want to reach out to Mekorma and post that question to them as well if that is what is taking the most time.   They may have additional information for you.  I know in GP, when you do a process for 'sending emails' for instance, the smaller the batches you do, the faster it goes, because a very large batch takes up so many more resources to accommodate the large batch, the resources get used up very quickly.  The smaller the batches you can do, it will save you lots of time from doing the one big larger batch, so I suspect this may be similar.

    Cheryl

    Dynamics GP Support - Applications

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans