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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Computer Checks Batch Total Not Matching Detail

(0) ShareShare
ReportReport
Posted on by

Hello:

I ran Purchasing Reconcile on batches, but it did not fix this.

We have a Computer Checks batch where the batch total is not matching the detail.  In fact, when we print the edit list and look at one of the vendors, the total dollar amounts in the edit list are not adding up to the correct figure.  It's simple elementary school arithmetic, yet, the edit list is wrong.

If the Reconcile utility is not fixing this, what other choice do we have?

A reputable consultant with a blog stated that batch totals do get "out of whack", at times, and that there's nothing to be concerned about.  In fact, this person says to go ahead and post the batch as the totals will calculate correctly during posting.

Truthfully, I'd rather give my end user a fix rather than a leap of faith.

Again, does anyone have any ideas?

Thanks!

John

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Ian Grieve Profile Picture
    22,784 on at

    I'd be concerned if the Edit List was not adding up correctly as this should process the transactions and show a total based on this.

    I'd recommend either doing an analysis of the transactions to see if they are correct (DocAmnt being equal to the sum of distributions for example) or run a Check Links on Payables Transactions (ensuring a good backup has been made first).

  • Community Member Profile Picture
    on at

    Hi Ian:

    You first answer was good and leads you down the correct path!  :)

    What I had our end user do was remove one of the vendors from the batch and put it in a new batch.

    Then, in the smaller batch, I examined the PM10300 APPLDAMT field with the total from the DOCAMNT field of the PM20000 table for that batch.

    As it turns out, several of the documents in PM20000 went beyond two decimal places.  

    This explained why I was seeing, yesterday, the PM10300 table's APPLDAMT going out to five decimal places.

    This accounted for the mathematical discrepancy.

    As it turns out, the end user had imported the documents from an Excel spreadsheet and did not pay attention to the number of decimals formatting.

    That's why documents beyond two decimals where appearing in SQL PM20000 and PM10300.

    Thank you!

    John

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans