Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Andrew Jinks]

We went live with 2012 R3 this year and in our Accounts Receivable processes we are using standard AX reversing entry code to do out of the box things like reverse NSF payments and we’ve also created a customization that uses this code around our invoice short-payment process.  We are getting an AX error (currently in our test environment) when a payment is received in one year but the reversal is done in the following year, even if both years and all periods are still set to Open.  The workaround that we know of is to create a General Journal for any transactions which fit this narrow set of criteria to manually adjust.  This isn’t a huge deal for NSF payments as we do not have very many but we do have a significant number of invoice short-payments which will carry over from 2017 into 2018. 

Is this standard AX code to prevent any reversals across years?  Would it be unwise to remove this blocking functionality from our customization so we can reverse across years?  Is there any other workaround besides manual journals?

——————————
Andrew Jinks
Leggett & Platt, Inc.
Carthage MO
——————————

[Ron Clee]

Haven’t gone through Ax 2012 year end yet,  but  it’s probably the same as Ax 2009.  Once you bring balances forward on the General ledger,  the system stops you from reversing entries in the prior year.  If you have access to the balance forward routine, then you can do the reset function to delete the opening balances.  This will allow the reverse entry to process.   When finished,  remember to bring balances forward again.

Ron Clee

A.W. Chesterton Company

Groveland MA

——Original Message——

We went live with 2012 R3 this year and in our Accounts Receivable processes we are using standard AX reversing entry code to do out of the box things like reverse NSF payments and we’ve also created a customization that uses this code around our invoice short-payment process.  We are getting an AX error (currently in our test environment) when a payment is received in one year but the reversal is done in the following year, even if both years and all periods are still set to Open.  The workaround that we know of is to create a General Journal for any transactions which fit this narrow set of criteria to manually adjust.  This isn’t a huge deal for NSF payments as we do not have very many but we do have a significant number of invoice short-payments which will carry over from 2017 into 2018. 

Is this standard AX code to prevent any reversals across years?  Would it be unwise to remove this blocking functionality from our customization so we can reverse across years?  Is there any other workaround besides manual journals?

——————————
Andrew Jinks
Leggett & Platt, Inc.
Carthage MO
——————————

[Shirley Adams]

I saw this and was curious as I had not run across this.   I tested in D365, which should have the same code base as 2012 R3 and was able to reverse the transaction across years.  I’m not sure if this is what you are asking but if so, there doesn’t seem to be any issues with reversing across years.

——————————
Shirley Adams
AKA Enterprise Solutions
New York NY
——————————
——————————————-