Vendor statistics payment amount issue with voiding checks - Microsoft support case


Here is my response to Microsoft regarding this issue.

Dear Microsoft,

Last week Steve Endow, Henrik Helgesen, and I met to review the issue with the vendor statistics payments amounts. If you recall the issue, I reported was that when a check payment to a vendor was voided through the check ledger entries window that it would still show up in the payment amount within the vendor statistics. Well, we believe we have found the issue and we do believe this is a bug that Microsoft should address rather than asking for this to be an "enhancement". 

Here is a little background. After you told me "this is not qualified as a bug, since it is working as intended" I took the issue to Twitter. There are tons of passionate MSDyn365BC developers worldwide that took notice right away. Steve Endow reached out and asked to dig into it more with me. Last week we met for a live YouTube session where more BC developers took notice. Here is the recording:

Fast forward to later that evening and I found myself on a call with Steve and Henrik to review the issue more. This is when we realized it's truly a bug. Here is how we tested.
  1. Created a new vendor. 
  2. Posted a purchase invoice.
  3. Paid vendor invoice via check.
    1. Payment amount showed in vendor statistics. 
  4. Voided and unapplied vendor check via check ledger entries. 
    1. Voided payment amounts still showed in vendor statistics. This is the issue.
Once we identified the issue, we dug into why it was an issue. This is where we discussed the process of voiding checks using the check ledger entries window vs "reversing" an entry using the bank ledger entries window. We tested reversing an entry through the bank ledger entries window and to our surprise the payment amount on the vendor statistics was updated correctly. 

It's my understanding that outside of the United States most clients would "void" a vendor payment via "reversing" the transaction within the bank ledger entries window. This would mean that this could be a US localization issue only then. 

The other thing we noticed is that when we voided the check through the check ledger entries window and looked at the transaction within the detailed vendor ledger entries window the Document Type field was blank on one of the entries. And if we reversed through the bank ledger it was not blank. We feel like this is where the bug is. The issue with the vendor statistics payment amount needs this field to be populated with "payment" to have the amount correct. 

Here are some of additional notes from our session of testing. 
  1. There is a clear difference between the bank ledger entry "reversing" and the check ledger entry "voiding". 
  2. Document type = "Payment" cannot have a negative amount. We tested this by trying to create a negative entry in the payment journal. 
    1. We added the field "Correction" and "System-Created Entry" to see if we could post a negative and couldn't. 
  3. Henrik mentioned the issue could be within "Code Unit 12".
I hope this all makes sense and if you would like to jump onto a call, please let me know. Please confirm receipt of this and that you will share this with the developers. We are very passionate about BC and truly feel like Microsoft should fix this issue ASAP since it is a bug, and this affects any clients that make check payments and need to void. We would also suggest a way for voided transactions to be corrected in the system with the update so that the payment amounts are correct. 

Written by: Kristen Hosman, Microsoft MVP


Popular posts from this blog

Microsoft Dynamics 365 Business Central: adding new licensed users to BC

Dynamics 365 Business Central - Is this a feature or a bug? Filtering and posting General Journal lines

Invited External Accountant in Dynamics 365 Business Central now what?