AX 2012 R2: Solved. Reversing fixed asset acquisition GL voucher is allowed and causes discrepancies between ledger and fixed asset modules

One of our customers, who is still using AX 2012 R2, came across with an issue regarding Reverse transaction button on the General ledger voucher.

Situation:

Fixed asset acquisition transaction was incorrectly filled in and posted through the Fixed asset journal.

In order to fix that issue, Reverse transaction button was used. You may ask that it’s impossible to use that option if you have any kind of subledgers posted. Unfortunately, if you select main voucher account and click Reverse transaction button, you will get an error message.

“The ledger transaction type Fixed assets, credit for account %1 cannot be reversed”

But if you select a offset voucher account you can successfully reverse the transaction.

Steps to reproduce:

Create and post fixed asset journal (in our case disposal has been created, but Type has not been updated, it was stated Acquisition)

Go to the Voucher transactions form for the posted transaction.

Highlight Credit account transaction.

Click the Transactions button.

Click the Reverse transaction button.

Note: Error message is displayed

Go to the Voucher transactions form for the posted transaction.

Highlight Debit account transaction.

Click the Transactions button.

Click the Reverse transaction button.

Note: No error message is displayed. Transaction can be successfully reversed

Issue:

With this being made, you will have reversed vouchers in GL. In addition to that, you still have an issue in the fixed asset module. For instance, if you open transactions, you will see that no reversal transactions have been made since only GL vouchers have been reversed.

Fix:

This should not be allowed, because you will have discrepancy between subledgers and ledger.

There is already a hotfix available:

KB 4010489, Bug Id 3804873: Reversing a free text invoice GL voucher is allowed and causes discrepancies between ledger and customer modules

The changes in the hotfix correctly set the reversal validity flag in TransactionReversal:: checkPostingType.

If you look at the changes made within this hotfix, you will find out that the following code was added to the TransactionReversal_Ledger class, reversal method

Check this link for the hotfix details:

https://fix.lcs.dynamics.com/Issue/Details/1184060?kb=4010489&bugId=3804873&dbType=2&qc=420705aa60772445e1e37f4eb4eac45737bf9de907a6c1295620ea4e1b7e8b68

That’s it!