ACH for Collection Agencies: TEL and WEB Entries and Return Limits

On this page 7 sections

1. Why ACH for Debt Collection Agencies Is Cheap but Fragile
2. Pick the SEC Code by How the Debtor Said Yes
3. The Nacha Unauthorized Return Rate in Collections
4. Web Debit Authorization for Collections: Validate the Account First
5. ACH Returns at a Collection Agency: Why R10 and R07 Pile Up
6. Bounced Payment Fees: What a Collector Can Legally Add
7. Keep Your Bank on Your Side With a Monthly Return Review

Key takeaways

• Code each entry by how the debtor authorized it. A phone payment keyed into a web page is still a TEL entry.
• Track unauthorized returns on first debits separately, because a blended rate can hide a problem at intake.
• A stop request that you honor costs nothing. The same request sent to the debtor's bank comes back as an R07.
• Add a returned-payment fee only after counsel confirms the legal basis and your ODFI confirms how the fee has to be sent.

ACH for debt collection agencies works when every debit traces back to an authorization the consumer will recognize and stand behind. A bank account debit is usually the cheapest way to take a payment by phone or through a portal, but it also gives the consumer a long window to tell their bank the debit was unauthorized. Nacha, the organization that writes the ACH rules, limits how often that can happen before your bank has to step in. Keeping your access depends on two habits: code each entry by how the debtor actually authorized it, and check the account before the first debit. When an unauthorized return still comes back, trace it to the step that failed.

Why ACH for Debt Collection Agencies Is Cheap but Fragile

ACH processors usually charge a flat amount per transaction instead of a percentage of the payment. On a settlement payment of a few hundred dollars, a flat item fee typically costs much less than a percentage-based card fee. Pricing differs from one processor to the next, so compare item fees and return fees side by side. In collections, returns are where an ACH program gets expensive. Cards come with their own complications for collectors, including network restrictions on certain debt types, which we cover in network rules for collection agencies accepting credit cards.

The weak point is on the consumer's side of the transaction. Under the Nacha Rules and federal consumer protection law, a consumer has far more time to claim a debit was unauthorized than a bank has to return one for insufficient funds. A debtor who regrets a payment, or who never fully understood what an agent set up, can call their bank weeks later and get the money back. The returned amount comes out of your settlement account, and the return is recorded against you as the originator.

You are the Originator. Your bank, or the sponsor bank behind your ACH processor, is the ODFI (Originating Depository Financial Institution). The debtor's bank is the RDFI (Receiving Depository Financial Institution). The ODFI answers to Nacha for every entry you send, so your return rates are its problem as well as yours.

Pick the SEC Code by How the Debtor Said Yes

Every ACH entry carries a Standard Entry Class (SEC) code that tells the banks how the consumer authorized it. Collection agencies mostly work with three.

The most common coding mistake in collections comes from misreading what the code describes. The SEC code records how the consumer gave authorization. The software your agent used doesn't change it. Suppose an agent takes a debtor's routing and account numbers over the phone and types them into a web-based payment page. That is a TEL entry. Coding it as WEB because it passed through a browser misstates the authorization, and that weakens your position if the debit is disputed.

TEL Entry Rules for Debt Collection Calls

The Nacha Rules list the elements a TEL authorization has to capture. A recurring plan set up on a single call requires more elements than a one-time payment does. Get both current lists from your ODFI and write a fixed script for each, so agents cover every element in the same order on every call. Most agencies keep the call recording and also send the debtor a written confirmation. Ask your ODFI what it expects as a minimum.

Nacha also restricts the use of TEL in some calling situations, depending on your relationship with the consumer and on who placed the call. Ask your ODFI how it treats outbound collection calls before you build your phone payment flow around TEL.

An IVR payment, where the debtor keys in account details on the phone, is also a phone authorization. Confirm the coding with your ODFI, and make sure the IVR script captures everything a live agent's script would. If your agents also take card payments on calls, the recording and screen-capture issues in PCI rules for collection call centers apply to those same calls.

WEB and PPD in Practice

WEB covers anything the debtor authorizes online, such as a portal payment or a payment plan e-signed on a web page. PPD is for paper. A debtor who signs and mails back a plan form has authorized it in writing. Recurring plans carry their own authorization terms under each code, and our guide to Nacha authorization rules for recurring ACH billing explains how they differ from single payments.

The Nacha Unauthorized Return Rate in Collections

Nacha watches unauthorized returns most closely, and that category has the lowest threshold. Nacha also tracks administrative returns, which come from bad account data such as a closed or nonexistent account. A separate overall rate counts every debit return for any reason, insufficient funds included.

Each rate is measured against your debit entries over a set period. Confirm the current thresholds and the measurement period with your ODFI. Ask for the bank's internal trigger as well, because many banks act before Nacha's threshold is reached. If you cross a Nacha threshold, Nacha can open an inquiry with your ODFI. That usually turns into a remediation plan with a deadline for you to meet. If the problems continue, you can lose the ability to originate.

A Worked Example: Where the Returns Come From

The figures below are illustrative.

• Debit volume. An agency sends 2,400 debits in a month. Of those, 1,800 are installments on plans set up in earlier months, and 600 are first debits from new payers.
• Unauthorized returns. Fifteen come back that month. Three are installments and twelve are first debits.
• Blended rate. 15 out of 2,400, or one return for every 160 debits.
• Installments only. 3 out of 1,800, or one for every 600.
• First debits only. 12 out of 600, or one for every 50.

First debits return at more than three times the blended rate and at twelve times the installment rate. Convert the blended figure to a percentage and compare it with Nacha's current threshold and your ODFI's trigger. Then look at the segments. In this example, the payment plans perform well and the risk is at intake. Tightening agent scripts, confirmations and account checks for new payers would do more than any change on the installment side.

Web Debit Authorization for Collections: Validate the Account First

Nacha's rules for internet-initiated debits require Originators to screen for fraud. ODFIs commonly read those rules as requiring account validation the first time an account number is used and again whenever the number changes. Get your ODFI's requirement in writing before you launch or change a portal.

Validation confirms that the account is open and can accept debits before you send one. The usual methods are:

• Account validation services, which check routing and account numbers against bank data in real time.
• Instant bank verification, where the debtor logs into their bank through a third-party connection.
• Micro-deposits, small credits the debtor confirms before the first debit goes out.
• Prenotes, zero-dollar test entries. They are slower than the other methods and catch fewer problems.

Collections needs this check more than most industries do. Debtors mistype account numbers when paying by phone or online. Others give a closed account, or one that belongs to a relative, just to end the call. Without validation, each of those becomes an administrative or unauthorized return. The easiest place to add the check is the checkout step of a debtor portal. For other portal features that affect whether payments succeed, see self-service payment portal features for debtors.

ACH Returns at a Collection Agency: Why R10 and R07 Pile Up

The two unauthorized return codes collectors see most are R10, where the consumer tells their bank the debit wasn't authorized, and R07, where the consumer says they revoked an authorization they had given. Both count toward your unauthorized rate.

Most of these returns trace back to a short list of causes:

• The debtor doesn't recognize the name on the statement. Your agency's name may mean nothing to someone who thinks they owe the original creditor. Use a recognizable company name, and add a creditor reference where your processor allows one, to cut down on "I don't know this charge" claims.
• The debit doesn't match what the debtor remembers. An amount or date the debtor didn't expect leads straight to a dispute. Send a written confirmation of every phone authorization and a reminder before each future-dated debit. Ask counsel whether any federal or state notice rules apply to the scheduled debits in your plans.
• The debtor wanted to stop and went to the bank instead of to you. When you cancel promptly on request, nothing comes back as a return. When the debtor has to ask their bank instead, you get an R07. Put a revocation phone number and email address in every confirmation, and process revocations the same day.
• The debtor disputes the debt itself. An unauthorized claim is sometimes a debt dispute in disguise. Run your dispute and validation process separately from your payment flow so a dispute doesn't end up as a bank claim.

Nacha also limits reinitiation. A debit returned as unauthorized generally needs a fresh authorization before you send it again. Re-presentments after an insufficient-funds return are capped in both number and timing. Get the exact limits from your ODFI and build them into your payment system, so a scheduler can't re-run a returned debit on its own.

Bounced Payment Fees: What a Collector Can Legally Add

This section is general information, not legal advice. Confirm your fee practices with a qualified attorney.

Federal debt collection law limits what a collector can add on top of the debt. As a practical matter, a returned-payment fee needs a basis in the original agreement or in applicable state law. State rules on returned-payment fees vary, and some cap the amount. Treat a convenience fee for paying by phone or online the same way, and get counsel's sign-off before you charge one.

The Nacha Rules apply separately from that law. They contain specific provisions for return fee entries, so ask your ODFI how a fee collected by ACH has to be authorized and sent. Don't assume you can roll it into a re-presented payment. If you can't document a basis for the fee under the law and under the ACH rules, leave it off. A fee the debtor didn't expect also gives them one more reason to call their bank.

Keep Your Bank on Your Side With a Monthly Return Review

ODFIs are more patient with Originators who report problems early than with ones they have to chase. A short monthly routine covers most of what a bank wants to see:

1. Break out returns by return code and by intake channel. The blended rate tells you whether you have a problem, and the breakdown tells you where it is.
2. Listen to a sample of the recordings behind each R10 on a TEL entry. Agents who skip parts of the script show up quickly.
3. Confirm that every first-use WEB debit went through account validation, and find out why any skipped it.
4. Send your ODFI a short note with the numbers and what you changed, before it asks.

Don't respond to rising returns by moving volume to a second processor or splitting entries across merchant IDs to dilute your rate. Banks treat that as evasion, and it can cost you origination access entirely. If your card or ACH access has already been cut, why collection agency merchant accounts get declined covers what underwriters look for. For agencies that also take cards, MannyPay provides high-risk merchant accounts and virtual terminals for phone payments.

This week, sort last quarter's returns by code and intake channel to see where your R10s come from. That one sort shows whether to fix your scripts or your account checks first. If you also want to accept card payments alongside ACH, request a free quote, and a MannyPay specialist will respond within one business day.

MB

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.