Skip to main content
Solved

Ability to void AR payments once deposited


People are voiding payments that have already been deposited to the bank and it makes for A LOT of unnecessary work when reconciling.  In my eyes, there should be no reason to void any transaction that has already been released in a deposit.  If, for whatever reason, you need to void a transaction; you would need to first void the deposit, do what you have to do and recreate the deposit after.  Once a payment is deposited, it should be locked; period.

 

Even Quickbooks had this capability; it’s very simple because the transaction is posted to the ledger when released in a deposit.  But if this is too much to ask, we should at the very least have the ability to restrict certain users from making changes to released payments, especially if they have been deposited.  

 

Does anybody have any thoughts or workarounds to avoid this from happening?

Best answer by meganfriesen37

Would putting an approval map on the Payments and Applications screen prevent these voided items from getting to the posted phase?

i.e. If Payment Type = Voided Payment and (DepositAsBatch = True or  Deposited = True) then it goes to the controller or some other senior employee for approval and then it gets caught before it’s posted and updates the status of the original payment document from “Closed” to “Voided”

I’ve done something similar with our sales guys, because they kept creating sales orders to generate purchase order to purchase stuff internally and then it came to me for approval and it stopped them in their tracks :)

View original
Did this topic help you find an answer to your question?

3 replies

meganfriesen37
Captain II
Forum|alt.badge.img+11

Would putting an approval map on the Payments and Applications screen prevent these voided items from getting to the posted phase?

i.e. If Payment Type = Voided Payment and (DepositAsBatch = True or  Deposited = True) then it goes to the controller or some other senior employee for approval and then it gets caught before it’s posted and updates the status of the original payment document from “Closed” to “Voided”

I’ve done something similar with our sales guys, because they kept creating sales orders to generate purchase order to purchase stuff internally and then it came to me for approval and it stopped them in their tracks :)


Forum|alt.badge.img
  • Varsity II
  • 85 replies
  • January 20, 2023

I was unaware the system allowed this. I agree, no reason that this workflow should be allowed.

I agree with the other comment, when I cannot solve a workflow items that I don’t want the software to allow, I use approval maps. 


meganfriesen37
Captain II
Forum|alt.badge.img+11

FYI - There was a new feature released in 24R1 to help minimize the risk of this occurring:

https://community.acumatica.com/ideas/warn%2Duser%2Dif%2Dthey%2Dtry%2Dto%2Dvoid%2Da%2Dpayment%2Dthat%2Dis%2Dalready%2Din%2Da%2Ddeposit%2D1560 

 


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