ACH payment failures are rarely random. Behind most failed transactions is a preventable problem: an account number that was entered incorrectly at setup, an authorization that was not documented properly, or a retry that was submitted before the account had time to recover.

Businesses that treat ACH failure as an inevitable part of processing tend to absorb the cost and move on. Businesses that examine their return data and adjust their processes at the front end see meaningfully lower failure rates, fewer disruptions to cash flow, and less administrative time spent on resolution.

The difference is largely operational. Here is where to focus.

Start With Bank Account Verification

The single most effective thing a business can do to reduce ACH failures is verify account information before the first transaction is submitted. A significant share of returns come from accounts that were entered incorrectly or no longer exist at the point of collection.

There are three main approaches:

Prenote

A prenote is a zero-dollar test entry submitted to the receiving bank before the first live ACH transaction. If the account information is valid, the prenote settles without issue. If there is a problem with the routing or account number, it returns before any real money is involved.

Prenotes take one to two business days to settle. They are the most thorough option for recurring billing relationships where the first transaction is not time-sensitive. NACHA requires businesses to wait a minimum of three banking days after the prenote settlement date before submitting the first live entry.

Micro-Deposit Verification

Micro-deposit verification works by sending two small deposits (typically a few cents each) to the customer’s account, then asking the customer to confirm the exact amounts. This confirms that the account exists, accepts deposits, and is accessible by the person providing it.

The process takes two to three business days. It is commonly used in self-service enrollment flows where the customer is entering their own account information, adding a confirmation step that catches typos before a larger transaction is attempted.

Instant Bank Verification

Instant bank verification uses real-time connections to financial institutions to confirm account status immediately at enrollment. This is faster than prenotes or micro-deposits and well-suited to digital enrollment flows where the customer expects a seamless experience.

Not all processors include instant verification natively. Discuss with your payment provider whether this is available and what it covers in your specific setup.

Get Authorization Right the First Time

Authorization errors are one of the top drivers of unauthorized return codes (R05, R07, R10, R11, R29), and those returns carry the strictest NACHA threshold: 0.5%. A single wave of improperly authorized transactions can push a business above that limit.

The authorization standard depends on how the transaction is initiated:

• PPD (Prearranged Payment and Deposit): Used for consumer accounts with a recurring or one-time debit arrangement. Requires written authorization, signed or similarly authenticated by the customer.
• WEB: For internet-initiated entries against consumer accounts. Authorization must be obtained electronically, and the business must employ a commercially reasonable fraud detection system.
• TEL: For phone-initiated entries, single or recurring. Oral authorization must be recorded or a written notice sent to the customer before the transaction.
• CCD (Corporate Credit or Debit): For business-to-business transactions. Requires authorization from an authorized representative of the receiving company.

Every authorization must clearly identify the originator, describe the nature of the transaction, specify the account to be debited, state the amount or how the amount is determined, and indicate the frequency. NACHA requires that authorization records be retained for at least two years after the authorization is revoked or the last entry is initiated, whichever is later.

If your authorization documents are vague, verbal-only when they should be written, or stored inconsistently, that gap will surface in your return data.

Validate Routing Numbers Before Submission

A valid-looking routing number is not always a valid ACH routing number. Some routing numbers are valid for wire transfers but not for ACH. Others belong to banks that have merged, been acquired, or closed.

Before submitting any new ACH entry, confirm that the routing number is on the current Federal Reserve routing directory and is designated for ACH processing. Most payment platforms do this automatically. If yours does not, ask your provider how routing validation is handled.

Configure Retry Logic Correctly

Retry logic that is misconfigured causes two problems: it submits transactions at times or frequencies that NACHA does not permit, and it wastes retry attempts on accounts that need more time or a different resolution approach.

The correct framework:

• R01 / R09 (insufficient or uncollected funds): Wait three to five business days before the first retry. This gives the account time to recover. NACHA permits a maximum of two retries after the original entry, within 180 calendar days of the original settlement date.
• R02, R03, R04, R20 (account issues): Do not retry with the same account information. Collect corrected details before resubmitting.
• R05, R07, R10, R11, R29 (unauthorized): Do not retry. Period. A new signed authorization from the customer is required before any further transaction can be initiated.
• R08 (stop payment): Do not retry until the stop payment order has been resolved or the customer provides a new authorization.

Automated retry systems should be configured to distinguish between these categories. A system that retries all failures on the same schedule treats unauthorized disputes the same as insufficient funds, which is both a compliance risk and an operational mistake.

Keep Account Information Current

Even verified account information goes stale. Customers change banks, close accounts, and open new ones. Without a process for keeping payment records current, you will accumulate administrative returns (R02, R03, R04) over time even if your initial verification was solid.

Practical approaches:

• When a return occurs on a previously successful account, prompt the customer to provide updated information through a secure update flow before the next billing cycle.
• Send periodic account review reminders for long-term recurring billing relationships, particularly if there has been no return activity but significant time has passed.
• Make it easy for customers to update their payment information independently through a self-service portal. The fewer steps involved, the more likely they are to do it proactively rather than after a failed charge.

Monitor Return Patterns, Not Just Individual Returns

Individual return codes tell you what happened on a specific transaction. Return patterns tell you whether something systemic needs to be fixed.

A spike in R03 returns may indicate a data entry problem in your enrollment flow. A rising R01 rate concentrated in a particular industry or customer segment may indicate cash flow stress among your clients. Recurring returns from the same accounts may indicate customers who are consistently avoiding payment rather than experiencing a one-time issue.

Tracking return code distribution over time, and comparing it against your overall transaction volume, gives you an early warning system before individual issues become a threshold problem. NACHA’s return rate limits (15% overall, 3% administrative, 0.5% unauthorized) apply on a rolling basis. A business that catches a trend at 1% unauthorized has more options than one that notices at 0.4%.

How ReliaFund Helps SMBs Manage ACH Failure Rates

ReliaFund provides ACH processing with detailed return reporting, giving businesses the transaction-level data needed to identify failure drivers and respond correctly. With U.S.-based support available by telephone, clients can reach a knowledgeable team member when a return situation requires guidance, not a ticket queue.

If your business is seeing higher-than-expected ACH return rates or wants to put stronger preventive practices in place, contact ReliaFund to discuss how your current processing setup can be improved.