Notifications
Announcements
No record found.
We upgraded a client to GP 18.2 and then to 18.3 last month. Every since the first upgrade they have experienced the batch of checks to hang while posting. What happens is all the checks print and the checks will post with the exception of the checks that require a separate remittance. When this happens i update SY00500.BCHSTTUS to 0 so I can print the edit list. The edit lists never report any errors. They use Mekorma so I am going to pose this same question to them. They do tend to print large check runs. The one last week contained 128 checks. Has anyone else experienced this?
Hello Richard,
In support, we have not seen any issues with 18.3 for Check Runs.
For this type of issue, there are a few things i would try to help narrow it down.
All testing should be done in a test environment.
I hope this helps!
Brandon | Microsoft Support Engineer.
Brandon, the plan right now is to queue up the next check run and then wait for me to perform a backup. Once I have the backup I will load their company database in our data center and then begin processing. First I hope to reproduce the issue. Then I will disable Mekorma.If it turns out to be Mekorma I will bring them on board. If not, I will revert all reports to not use any of the modified versions. Their next check run is scheduled for the 26th.
We are still on GP2018 R2 and we run into this frequently. We have Mekorma approvals in place, so when I reset the BCHSTTUS to 0, they have to resubmit for approval, and reprint the cheques before posting, Sometimes after the cheques have been printed and sent out, or EFT's emailed (Vendors once got three EFT notices - for the same payment).
Looking to see what other Batch Status I can set it to so that the user can simply Post and not have to reprint or resubmit for approval. Mekorma was not helpful.
Rich,
Do they have the checkbook set up to disallow duplicate check numbers? If so, can you change that setting to allow duplicates and try to post again? If that works, then it's the same issue I've seen one of my clients run into because the $0 remittances created re-use the same numbers REMIT00000, REMIT00001, etc. each time. But no reason to keep going down this road if that's not the issue...
-Victoria
They can go and turn on the Duplicate Checks flag as needed. The issue is that the batch has to be re-sent for approval (Mekorma). I wondered if there is a different BCHSTTUS that will just allow us to post (IE. Checks printed, ready to post).
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 544 Most Valuable Professional
André Arnaud de Cal... 450 Super User 2025 Season 2
Sohaib Cheema 250 User Group Leader
