No, CU*BASE cannot automatically remove the 08 Payment Stopped code from an ACH distribution record.   ACH stop payments are tricky.  Since an ACH stop payment is only valid for a specific payment, the system would have no way to determine which payment it was applicable for as it’s not easily identified by simply using the posting date.  Often the information needed is located in other optional fields of the ACH record such as company descriptive date.

For instance, if a member is NSF for a payment, he could receive 2 debits in the next period where only one may be covered by the stop payment request. This has always required manual intervention to delete the stop payment when appropriate and verify that the appropriate record is being returned as a stop payment.  Because there is no unique identifying number similar to a check number in the PPD and some other records, some manual intervention will probably always be needed.

In the CU*BASE 9.1 release we implemented some changes to how stop payment orders can be placed using Tool #71 "Stop Payment on Member Check/Draft."  It will allow stop payments to be created with purge dates similar to the draft system when the ACH transaction amount is known.  It won’t necessarily be the answer for those monthly payments that change amount every time.  However, we are attempting to provide a way for a warning or “exception” to check against stop payments whenever possible.

It rare to receive requests for legitimate stop payments on PPD transactions.  Usually the request is to terminate the recurring entry altogether (or more accurately notify you that they DID terminate the authorization with the originator) or stop a one-time payment when they changed their mind or realize they gave out information that they shouldn’t have over the phone, etc.