Check Truncation Entry Return: ACH Code R11 Before and After 2020

If a return labeled "check truncation entry" has shown up on your ACH reporting, you are looking at one of the stranger corners of the Nacha rulebook. For years, return code R11 was the check truncation entry return. Then Nacha redefined the code on April 1, 2020, and much of what you will read about it online still describes the old rule. Here is what the code used to mean, what it means now, and what to do when one of these returns lands on your report.

What Is a Check Truncation Entry?

A check truncation entry carried the information from a paper check through the ACH network so the check could be settled electronically. The paper item itself stopped moving — it was truncated — while its data continued through the system. This is different from check conversion (ARC, BOC and POP entries), where a check is used as the source document to create a new ACH debit. That is the whole mechanism. The complications start with how returns of those entries were coded.

R11: The Original Check Truncation Entry Return

Under the original Nacha definition, R11 was the code used to return a check truncation entry, and it was to be used only when no other return reason code applied. It was a narrow catch-all for a narrow category of transaction.

That original definition is the one most payments glossaries still carry, which is why so much of what you will find on the subject is out of date. If a page stops at the check truncation definition, it is describing the pre-2020 rule.

What Changed on April 1, 2020

As of April 1, 2020, Nacha repurposed R11. The code now means "Customer Advises Entry Not in Accordance with the Terms of the Authorization." Nacha's reasoning was straightforward: no forward transactions were being made as check truncation entries, so the old definition had no live use. Rather than retire the code, Nacha gave it a new job as part of differentiating unauthorized return reasons.

If your bank or processor documentation still describes R11 as a check truncation entry return, it predates this change.

What R11 Means for a Merchant Today

Under the current definition, an R11 return is not a customer denying that an authorization exists. It is a customer saying the entry did not match the terms of the authorization they gave. That distinction matters, because the fix is different. You are not rebuilding proof of authorization from scratch — you are comparing the entry you submitted against the terms the customer agreed to, finding the mismatch, and correcting it.

One point matters more than the label: Nacha classifies R11 as an unauthorized return. R11s count toward your unauthorized return rate, which Nacha caps at 0.5%, and since April 1, 2021 they carry the same Unauthorized Entry Fee as other unauthorized returns. A customer may have agreed to pay you, but an R11 still lands in the same bucket as a customer who never did.

Handled well, these returns are a fixable problem, not a crisis - but they are not harmless. Treat them the way you treat disputes: log them, find the cause, and close the gap in your process. Our chargeback management page covers how we help merchants do exactly that.

ACH Return Code R30: Where Check Truncation Returns Live Now

If you are looking for the return code tied to check truncation today, it is R30: the receiving bank is not a participant in a check truncation program. In practice, R30 is rarely encountered. If it does appear, the issue sits with the receiving institution's participation — not with your entry, and not with your customer's authorization.

What to Do When You See One of These Codes

• Confirm which definition applies. Check the date context and your processor's documentation. An R11 on an older report, or in older software, may still carry the check truncation label.
• Pull the authorization. For a current R11, retrieve what the customer agreed to — amount, timing, and terms.
• Compare the entry against it. The return is telling you something did not match. Find it.
• Correct and resubmit. Under Nacha’s rules, once you fix the error behind an R11 — the wrong amount, the wrong date, or the wrong terms — you can send a new entry without getting a new authorization from the customer, as long as it goes out within 60 days of the return’s settlement date. Your processor can confirm the timing and help you resubmit cleanly.

ACH Returns and High-Risk Underwriting

Return codes are not trivia. They feed your return rates, and underwriters read return rates closely — especially for merchants in categories banks already treat cautiously. Understanding what each code means, and responding to it correctly, is part of keeping an account healthy. R11s deserve extra attention here because they count as unauthorized returns, and a rising unauthorized return rate is one of the fastest ways to draw a bank’s scrutiny.

We work with high-risk merchants on ACH and eCheck every day, and you will see our terms in writing before you commit. If you process by ACH, or your business needs a high-risk merchant account behind it, contact us about ACH payment processing and we will give you a straight answer on whether we can help.