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)

Payables checks getting stuck in the wrong tables after posting

(0) ShareShare
ReportReport
Posted on by 7,365

Here is the scenario.  This happens in multiple companies, a couple of times a month out of a couple thousand checks printing.  We are using MICR.

After a check run with numerous checks in a batch, one check (possibly more sometimes) out of the batch no longer shows up on the transactions by Vendor Inquiry.  The check posted with no errors and hit the GL properly, and hit the Checkbook.  Under "Transactions by Vendor", the three vouchers it paid show up with a Unapplied Amount of 0.  However, drilling into the "Unapplied Amount" returns a blank screen with a message that says "Vendor Not Found."  The invoice Status is "OPEN" (open table) when I expect them to be in History (HIST).  The payment (check) is not even listed on this vendor's record.  Just the 3 invoices.

At this point, the tables look like this.

PM00400 - (PM Keys) The record for this check exists in this table however, the TRXSORCE which would typically be populated with  'PMCHK0000..' is blank for this one record  (I think this is the contributing factor to how this gets messed up.)  The records for the 3 Invoices also show up in this table.

PM10000 - This check transaction does not exist in this table.  Nor do the invoices (as expected)

PM10100 - The distributions for all 3 of the vouchers that were paid with this check still exist in this table (it is Work and Open Distributions).  The Check distributions do not exist in this table

PM10200 -  (Apply to Work/Open) - The 3 invoices are in this table and the Check's "Voucher Number" is the proper voucher number that should be applied to them.

PM20000 - (Open/Posted Transactions) - The three invoices show up here (the distributions are in the PM10100) but no check.

PM30200 - (Historical / Paid Transactions) - Nothing about the 3 vouchers or the Payment show up here.

PM30600 - (Historical Distributions)  - Nothing about the 3 vouchers or the Payment show up here.

My first step (in a test environment) was to Run Checklinks.  All that did was tell me that the Check I was looking for (with the right voucher number) "The Transaction for this Keys record is missing.  The Keys Record has been removed."

So it deleted the record out of the PM00400. Now going into the Transactions by Vendor, these 3 invoices show up as due again, even though the Check has actually been written and the GL Distributions have posted to the GL.

Once I get a restore of this database again, I am going to try to insert the proper PMCHK0000..... into the blank column in the PM00400 Record.  Then I will Run Checklinks again.  I am hoping that Checklinks will then be smart enough to move the appropriate records to the History Tables and I believe it will also have to recreate the Payment Transaction in the PM20000 or PM30200.  But I have doubts that it will be successful at doing so.

After all of that, has anyone seen this before?  It is an error that is virtually impossible to reproduce because it happens randomly, with multiple users, on multiple workstations.

We have asked Microsoft about this and their solution was to back out the journal entry from the GL and delete the record of the check from the PM tables, then issue the check again (turning on the setup that allows us to use the same check number again).  This is to create an audit trail because we are a public company.

Any idea why the record in the PM Keys might be coming through as Blank instead of putting the proper  TRXSORCEwhen the rest of the checks in that batch were fine?

Thanks, and have a nice Thanksgiving.  I may not check back for a few days to see if someone has any suggestions.

Kevin

*This post is locked for comments

I have the same question (0)
  • Victoria Yudin Profile Picture
    22,769 on at

    Kevin,

    First of all - awesome job of documenting and looking up all of this - it should help tremendously with the troubleshooting.  One table I didn't see on your list is the PM10300 table (Work/Unposted Payments) - is the check is there? 

    I have not seen this before with any version of GP, and I imagine this is what Microsoft support told you as well, that this is not a known issue.  Since you're able to successfully print and post the check and it shows up in the GL and Bank Rec, I would deduce that there is a problem during the posting stage, specifically with the PM module when it is looking to move the check from work to history and the invoices applied from open to history.  My top 2 contenders for the cause of this would be connectivity and custom code (or possibly a combination of the 2).  I would try to find some more patterns for this, if possible: are the 'missing' checks always the last check in a batch?  Are the missing checks typically in a large batch?  If the answer is yes to both, that would make me lean towards connectivity as the issue. 

    You said you're using MICR - do you mean a 3rd party application?  If so, can you see if this is a known issue for that application and/or if there are additional 3rd party tables that need to be checked for your transactions?  Do you have any other customizations?

  • Richard Whaley Profile Picture
    25,195 on at

    I agree with Victoria to check into issues with the third party first.  However, it could be related to another issue we were finally (after 5 years of searching) to reproduce.  Try this (on a test company)

    Enter the check and apply it to invoices in a batch.  Once the payment is entered, DO NOT CLOSE the window where the check was created.  Once the save button is clicked, stop typing.  Go to another terminal and post. 

    When you do this with a sales order and then transfer the order to an invoice, the order ends up in history AND work.  See, unless you start another transaction on the original terminal or close the windows, GP keeps the document locked even though you saved it.  You MUST start another transaction or close the window to completely release the document.

    Let us know what you find.

    GP is working the issue on the SOP side but I suspect it is a basic forms handler issue that could affect other transactions.

     

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