Preventing Voucher Duplication in AX 2012
Posted on: February 19, 2016 | By: Jarrod Kraemer | Microsoft Dynamics AX/365
Written by: Dave Occhionero
A couple of months ago a client’s Business Intelligence team noticed that voucher numbers were duplicating in payment journals. The issue arose after the team tried to tie Customer Numbers to vouchers. After gathering the team together to analyze some of the journals we had noticed that there was an issue with the way we were entering journals. We have identified 2 culprits of the issue and wanted to share our results. The second culprit involves the use of Excel import functionality so it may not be applicable in your environment. (Note: This happened with a few accounts, not many.)
1. Create a Payment Journal with an offset account of any type
2. Prior to completing the entry, (do not enter a value) click the down arrow on your keyboard
3. You will notice that the voucher number stays the same for the next entry
a. The voucher number duplicates even after you enter different customer numbers
b. Unfortunately you will be able to post this journal as long as your debits and credits are equal
c. Even though the journal posts, issues may arise while running reports or analyzing data
4. To prevent this from happening we suggest the creation of a debit and a credit line so that there is always a 2 line transaction. This will prevent issues with the duplicate vouchers.
1. We noticed an issue when uploading payment journals through Excel uploads. Vouchers would duplicate throughout the entire journal in AX.
2. These typically occurred because of rounding issues in our Excel spreadsheets. A cell may not have been rounded with the correct decimal precision so during an upload, 2 lines from the same voucher may be off a penny. This will prevent AX’s voucher creation from creating a new voucher. It will continue to believe that every entry is under the same voucher, which causes duplicates.
3. To prevent this issue from happening verify that all entries in your Excel upload are rounded using the correct precision. If the problem persists, contact your partner or have your infrastructure look for any cached data on the server.
Do not hesitate to search our older blog posts to find other troubleshooting techniques we have utilized at other clients.
For additional information please feel free to reach out to us at firstname.lastname@example.org or (312) 345-8817.
All the best!
25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics
Top 10 Inventory & Operations Decisions Distributors Are Making Blind
2020 Nucleus Research Report on ERP Technology