# What Do Less Common ACH Return Codes Like R11, R13, R16, R20, and R24 Mean?
[ACH return codes](https://securemerchantsolution.com/blog/ach-return-codes/) such as R01 and R10 get most of the attention, but businesses also run into codes they have never seen before. A return marked R13 or R24 can look like a puzzle, and a wrong guess about its meaning can lead to a wrong response. Knowing the less common codes helps you react calmly and correctly when they appear.
This guide explains five of these codes, what usually causes them, and how to respond. Definitions, time limits, and rules can change, so confirm current details with your bank, your processor, and Nacha.
Why Do Rare Codes Matter?
A code you see once a year is easy to mishandle. Staff may retry a debit that should never be retried, or they may ignore a notice that points to a deeper data problem. Each return also affects your return rate, so even unusual codes deserve a quick, careful look.
Keep a short reference sheet, and update it when your processor shares new guidance.
What Does R11 Mean?
R11 generally indicates that the customer advised the entry was not in accordance with the terms of the authorization. In plain terms, the customer agreed to a debit, but the amount, date, or another detail did not match what they approved.
Typical causes include a price change that was not communicated, a debit taken earlier than agreed, or a different amount than the customer expected. The fix is usually better disclosure and cleaner billing rules.
What Does R13 Mean?
R13 means an invalid ACH routing number. The routing number you used does not belong to a bank that can receive the entry. This is almost always a data problem, such as a typo, an old number, or a number copied from the wrong place.
Do not retry with the same number. Collect corrected details securely and update your records.
What Does R16 Mean?
R16 means the account is frozen. A bank may freeze an account for legal, fraud, or compliance reasons, and funds cannot move until it is released. You usually will not learn the reason, and you should not ask the customer to explain details they may not be allowed to share.
Treat it as a pause. Contact the customer politely, offer another payment method, and avoid repeated retries.
What Does R20 Mean?
R20 refers to a non-transaction account. Some account types, such as certain savings or other restricted accounts, do not allow ACH debits. The customer may have given you an account that cannot be used this way.
Ask for a checking or other eligible account, and explain the reason in simple words.
What Does R24 Mean?
R24 indicates a duplicate entry. The receiving bank believes the same payment was sent more than once. This can happen when a file is submitted twice, a retry is mislabeled, or a billing system creates duplicate entries.
Check your batch and retry logs before you contact the customer. If the duplicate was your error, correct it and make sure the customer is not charged twice.
Where Can You Learn the Basics?
Understanding unfamiliar codes is easier with plain language. Resources such as [Secure Merchant Solution](https://securemerchantsolution.com/) publish guides on payment topics for business owners, which can help you prepare questions before you contact your bank or processor.
Treat any guide as background, and confirm exact definitions with your processor.
How Should You Respond in General?
Use a repeatable routine for any unusual code:
Read the exact code and description on the return notice.
Do not retry until you know what the code allows.
Check your own records for errors, such as duplicate files or wrong amounts.
Contact the customer only when needed, using a secure and polite message.
Update your records and note the fix.
Ask your processor if the code is unclear.
A calm checklist prevents costly guesses.
Which Codes Point to Your Own Mistakes?
Some returns are caused by your process, not the customer. R24 can come from duplicate submissions, and R11 can come from unclear authorization terms or changed amounts. When you see these, review your billing system, notices, and file handling first.
Fixing internal causes lowers returns faster than chasing customers.
What Should You Record?
For every unusual return, record the date, code, amount, customer, likely cause, action taken, and outcome. Over time, this log shows which codes appear and why, and it helps you update templates and training.
What Mistakes Should You Avoid?
Guessing what a code means
Retrying without checking the rules
Blaming the customer before reviewing your own files
Asking for bank details through insecure channels
Ignoring a code because it is rare
Conclusion
Less common ACH return codes are manageable when you read them carefully, check your own records, and respond without guessing. Keep a reference sheet, use a simple routine, and ask your processor when a code is unclear. Confirm current definitions and rules with your bank, your processor, and Nacha, and unusual returns will stop being a mystery.
FAQ
1. What does R13 mean?
An invalid ACH routing number. Collect a corrected number securely before trying again.
2. Can I retry after R16?
Be careful. The account is frozen, so contact the customer and offer another method instead of retrying repeatedly.
3. What causes R24?
A suspected duplicate entry, often from double submission or a mislabeled retry. Check your logs first.
4. Who can explain a code I do not recognize?
Your processor or bank, and Nacha’s official resources.