Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Voided AP Checks
Microsoft Dynamics SL (Archived)

Voided AP Checks

(0) ShareShare
ReportReport
Posted on by Community Member

There appears to be some condition that causes the AP Check Update process to change the checks to void status other than using the void all or select handling process.  My clients run into this from time to time and they all state that they used the Keep All option on that screen.  I have never determine what situation might cause this and was hoping that one of you may have determine the situation that caused this.  The one thing I have noticed is that, when this happens, the vendors involved seem to have a voucher document with a reference number that matches the check number being assigned for the payment but this may just be a misleading clue.

*This post is locked for comments

  • Community Member Profile Picture
    Community Member on at
    RE: Voided AP Checks

    Lisa, thanks for the response.  I will also keep that in mind.  In my last case the client was using SL 2011 and did not use the manual check feature but  I will warn them about a possible bug when doing that in SL 2015 CU1.

  • Cynthia Audain Profile Picture
    Cynthia Audain 1,294 on at
    RE: Voided AP Checks

    Hi, I have a client that has also experienced this on a continuous basis although they claimed that when the AP Check Update appears they click "Keep All".  They are using SL 2015CU1.

    I found this scenario was occurring too often so I decided to send this issue to Microsoft support and was told that if the user processes the check using the Manual check screen, they may encounter the checks being voided even though they click on 'keep all'.  

    They confirm that this is a bug and advise that another screen be used for printing or processing checks.

    I am not sure if you have encountered the same scenario but thought I throw this out on the forum as a possible cause.

    Regards

  • Verified answer
    Mark E Profile Picture
    Mark E 6,437 on at
    RE: Voided AP Checks

    Whenever I see this occurring, it is usually a scenario when the client selects "Keep All", and then (inadvertently/prematurely) clicks the Cancel button, thinking the process has completed (when they think the button has turned to "OK").

    I believe one of the first things that happens in the AP Check Update process is to set the Batch.Status to "V".  Then, assuming the process completes normally, it changes it to "U" for Unposted (and eventually "P" is GL Auto Posting is enabled).  

    If something interrupts the process (whether my above assumption, or other variable), the batch stays in the "V" status, and the APDoc.Status is updated to match.

    I am not 100% on this, but have minimally reviewed the code, and I think I am close.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 293,245 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,925 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans