I recently worked on an issue that I believe is quite similar to this. We're on v9.5.400 currently, but these had been building up for years. My solution (working with the support of our VAR of course) was to create a journal entry to correct the G/L, and delete the transaction that was written...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.