General question:
How often do you run the Paid Transaction Removal routine in AR?
*This post is locked for comments
Deanne,
Each customer I have worked with has different requirements for this. For example, I have one customer that constantly needs to go back and unapply/reapply pretty old payments. They use a cut off date that is 6 months prior, so they can easily do this. Other customers move everything to history right away, but then do use the unapply tool once in a while as needed. Yet others issue financials to the board and sometimes the bank that include details of their AR aging. In that case, they really don't want those things to change after the fact and thus don't want to unapply anything for a closed month.
I don't think there is a wrong or right, but I think the important thing is to be consistent and to keep running the Paid Transaction Removal so your open tables are not bogged down with unnecessary data.
Thanks, Victoria! That's what I keep telling accounting to do! We experience issues sometimes when a customer (like GNC) pays 30+ invoices with one check. Their payment is processed normally but then there may be issues and accounting needs to unapply and reapply items (baffles me but that's what they say). When they have to do this and some of the items from that check are 'moved to history', they cannot figure out what to do. I keep telling them to not unapply but issue debit/credit memos. It's a learning process for them.
We run it once a month, to keep consistent and that's what I typically recommend for others.
Thank you! This is exactly the info I need.
This article recommends making it part of your period end process.
community.dynamics.com/.../receivables-management-period-end-closing-in-dynamics-gp
Hi Deanne,
Since this routine is for purging 'fully paid'/matched payments and invoices from the statement, the frequency of running the routine may depend on your volumes, and perhaps how frequently the transaction matching is done. Just remember to tick 'Keep History' under Receivables Setup, to ensure that the transaction history remains (in the system), even as the statements are made lean.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Mansi Soni as our August 2025 Community…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Community Member 2
babubaskaran@outloo... 2
Yng Lih 2
