1) Classify the Exception (Don’t Treat All NSFs the Same)

Start with a clear exception type. Classification prevents overreacting to a one-off NSF and prevents underreacting to a true payment failure.

• NSF (insufficient funds): often recoverable with timing + communication
• Account closed / invalid account: urgent outreach + updated banking details
• Stop payment: treat as active resistance; escalate faster
• Unauthorized / revoked: compliance-sensitive; follow your required process
• Bank error / technical reject: verify with processor; retry appropriately

2) Apply a Standard Retry Cadence

A consistent cadence improves recoveries and keeps your team aligned. Avoid random retries that annoy merchants and create inconsistent outcomes.

• Retry #1: next viable business day (or next deposit day if known)
• Retry #2: 48–72 hours later (if merchant confirms funds timing)
• Final attempt: one structured “last retry” before escalation

If you have deposit cadence signals (daily deposits vs weekly patterns), align retries with expected liquidity windows.

3) Merchant Outreach: Use a Scripted Sequence

Outreach should be consistent and documented. The goal is not confrontation — it’s resolution with clarity.

• Touch 1 (same day): notify merchant of exception and upcoming retry
• Touch 2 (before retry): confirm timing (“when are funds landing?”)
• Touch 3 (after repeat failure): request updated plan (date + amount)

4) Escalation Triggers (Make Them Objective)

Escalation should not depend on which agent is working the account. Define objective triggers.

• 2+ exceptions in a short window
• Stop payment / revoked authorization indicators
• No response after repeated outreach attempts
• Merchant requests to pause or reduce without a formal plan
• Evidence of stacking or distress signals emerging

Once triggered, route the account to your defined next step: senior servicing, collections, workout, legal review, etc.

5) Create a “Resolution Path” (Not Just Retries)

If exceptions continue, your workflow should move into resolution — not infinite retries.

• Short-term catch-up plan: structured repayment timeline
• Temporary modification: payment adjustment with clear end date
• Bank update: confirmed new account details and authorization
• Escalation: collections/workout path with documentation

6) Weekly Reporting: Track Exception Patterns

Exceptions should roll into weekly visibility reporting so leadership can see risk trends early.

• Exceptions by type (NSF vs stop pay vs closed account)
• Retry success rate
• Top repeat-exception merchants
• Exceptions by broker/source (early quality signal)

Final Thoughts

ACH exceptions are a leading indicator. A strong exception workflow prevents “death by a thousand NSFs” and turns servicing into a structured operating system.

Frequently Asked Questions