Always configure your stop-no-go patterns using thresholds that signify abnormal activity for your membership base. Research typical member activity within different membership groups to base your thresholds on.
When configuring a velocity threshold for a stop-no-go pattern, AuditLink recommends configuring the threshold for a high number of transactions of a lower amount.
Be sure your pattern criteria are reasonable prior to activating the monitoring pattern. When you select to activate your ACH stop-no-go pattern, pay close attention to your ACH exceptions for any exceptions with the ABNL reason code. Adjust your thresholds accordingly until the ABNL exceptions are reasonable for abnormal activity within your membership base.
Note: Only the transaction triggering the pattern, and any additional ACH transactions for that member that day, will except out.