Skip to main content
Solved

Prevent Wrong nonsense Year being entered on Documents


Acumatica allows for nonsense years to be entered such as 2222 and 2044 on AP and AR documents. How can this be prevented? 

Best answer by Bbelknap

We had this issue with a payment accidently entered as 2121 instead of 2021. 

Our Support said it must have been due to having the Finanical Periods opened too far in advance. No, it wasn’t. We create our Finanical Periods one Fiscal Year at a time and only open the months up that are needed - usually current and next month.

I was told there was no correction for it However, we recently updated our version to the latest one and now it has a reverse open for it. I reversed it and recreated it with the correct year. 

View original

Kandy Beatty
Captain II
Forum|alt.badge.img+16

Hi @borem 

Will you share an example?

How far out are your financial periods opened for also?


Forum|alt.badge.img+2

  • Freshman I
  • August 17, 2023

 

 

AP Bills Entered into Nonsense Years

 


  • Freshman I
  • August 17, 2023

 

 

AP entered 1/2023 and paid 1/2023 but Dated Far in the past

 


  • Freshman I
  • August 17, 2023

Our Financial Periods are open just through 12/2023. This issue pitches our AP aging out of balance with our AP trial balance total. 


  • Freshman I
  • August 17, 2023

Future dated prepayments cause a variance as well but we haven’t had any dated with nonsense future or past years. 


  • Freshman II
  • August 18, 2023

We had this issue with a payment accidently entered as 2121 instead of 2021. 

Our Support said it must have been due to having the Finanical Periods opened too far in advance. No, it wasn’t. We create our Finanical Periods one Fiscal Year at a time and only open the months up that are needed - usually current and next month.

I was told there was no correction for it However, we recently updated our version to the latest one and now it has a reverse open for it. I reversed it and recreated it with the correct year. 


  • Freshman I
  • August 18, 2023

We just updated last Monday so hopefully that will solve the problem for us as well. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings