Reversed Payments still causing dtdf error

A payment is triggering a Due To/Due From error even though it is reversed. 

• Accounts Receivable
• Payments Journal (arrctpst)
• Payment Reversals (arrefrev)
• DT/DF
• DTDF
• Due To/Due From

The unposted payment was reversed in the Payment Reversals program instead of in Payment Entry so the GL Journal Posting does not wash out and a Due To/Due From is needed. 

If the payment was reversed in the Payment Reversals program, then the reversal is in a separate batch and the GL Posting for the original payment is not washed out. In these scenarios, the Due To/Due From relationship must be established. Please following this resource to set up the necessary Due To/Due From: Set up Due To Due From for new fund

Once the necessary Due To/Due From is set up, the batch can be posted. Please be sure to post the Payment Entry Batch and Payment Reversals Batch once the Due To/Due From is established.

If desired, the Due To/Due From setup can be deleted once the original batch is posted and any subsequent reversals have been completed and posted as well. 

Typically, a reversed payment will not trigger the need for a Due To/Due From as long as it is reversed in Payment Entry which can be accomplished using these steps: Reversing Unposted Payments

Development is currently considering making it so that the Payment Reversals program cannot reverse unposted payments (which was its previous functionality) or making it so that Payment Reversals will add the reversal to the original payment batch, which is consistent with the way the Payment Batch Reversals program behaves when reversing unposted payments. 

For more information about Due To/Due From errors and the expected functionality in Payments Journal, please see: gljnlpst proofReport Invalid number of dtdf accounts detected for XXXX and XXXX count 0 in Payments Journal