has anyones worked on a solution for this? "Looking for a solution to automate the clearing of open debit and credit items on customer accounts that have a $0 overall balance. Currently, this is done manually by applying the open invoice and credit in Accept Payment. We average 1000 of these per month."

AI generated answer (using internal Slack threads):

Based on the conversations, it appears that some users have encountered similar issues with zero dollar invoices and payments. However, there isn't a direct solution provided for automating the clearing of open debit and credit items on customer accounts that have a $0 overall balance. One user suggested creating a zero dollar payment to clear an invoice, but this was not successful as zero dollar invoices do not appear in the "accept payment" section. Another user suggested forcing it through a CSV upload, but this was not further elaborated on. In another thread, a user suggested using journal entries to track uncashed checks, but warned against it due to a defect with journal entries and account reconciliations in NetSuite. The recommended practice was to import checks to a holding account and then reverse with a journal entry in that holding account. In the third thread, a user mentioned creating a journal between A/R and a Bad Debt account, and applying a zero payment by checking off the invoice and the journal. However, this did not clear the invoice from the aging. Another user suggested that any re-saving of the invoice or journal entry, even without making changes, could un-apply the zero dollar payment. In conclusion, while there are some workarounds suggested, none of them directly address the automation of clearing open debit and credit items on customer accounts with a $0 overall balance. It may be necessary to develop a custom script or workflow in NetSuite to automate this process, but this was not discussed in the provided conversations. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******