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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Void Check range inclu...
Microsoft Dynamics GP (Archived)

Void Check range included checks not in numeric range

(0) ShareShare
ReportReport
Posted on by Community Member

A client last week (03/06/17) had to void some checks in a large range because the printer skipped a check and printed the batch on the wrong checks. When they voided using a numeric range (131570-131658), it pulled in incorrect checks.  The incorrect checks included "1316" in their check numbers.  Please see the image below. We have 6 or 7 vendors that were affected. Can you tell me why it pulls in checks that do not fall in the range?

Voided-checks.jpg

 Next, the big problem is that the transactions on the wrong voided checks are back as open payables, FY 2009 is already closed long ago (GP10).  Client is on GP2013 currently.  I need to check the voided check Table I presume and then proceed from there to clean up all affected Tables.  Each time they print checks they have to go through the batch and remove these old payables.

I am going to check Victoria Yudin's list of Tables and start there.  Can anyone provide any insight as to what may have happened and how to proceed?

thanks!

*This post is locked for comments

  • Verified answer
    HeatherD Profile Picture
    HeatherD on at
    RE: Void Check range included checks not in numeric range

    Phil,

    Unfortunately in computer terms 1316 is between 131570 and 131568.  The numbers are treated as letters sorted left to right not looking at the "place values"

    so

    asparagus

    at

    average

    113

    12

    2

    !

    I always emphasize this goofy type of sort with customers and colleagues in training to explain why I put in leading zeroes in any type of number in a computing system

    I am guessing that if you logged this as a support request - it would be indicated not as a bug, but rather as a feature request.  If I understand you correctly - the customer did the void directly from the Print Payables Check Window selecting the Void Checks option.  To me it is definitely worth a feature request/suggestion to indicate that if the void is done in that window - only checks from the CURRENT batch should be included!

    With six to seven vendors impacted,  I would honestly recommend entering correcting checks against the vendor accounts to clear up the payables (use the current date and make auditing notes).  Then check what corrections need to be made to general ledger - and enter those as a GJ.  The amount of time to research and create corrections in the back-end paired with those fixes not being auditable make me hesitate going that route.

    Heather

  • Community Member Profile Picture
    Community Member on at
    RE: Void Check range included checks not in numeric range

    What I have found is there are only 7 documents unintentionally voided.  They are documents 16157-16165.  The intended range was 161570-161658.  Is this a bug in GP2013 that caused these documents from 2009 to be included?  Not a huge issue but the first time this has happened.

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…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans